Veeam errors after about 72 hours into running a backup job

Hyper-V specific discussions

Veeam errors after about 72 hours into running a backup job

Veeam Logoby Squeezer » Tue Apr 16, 2013 7:36 pm

I am running Veeam 6.5 for Hyper-V. I am attempting to backup some rather large virtual servers over a T-1 line. After about 72 hours the backup jobs always fails. Is there a limitation within veeam that a job cannot run more than 72 hours? Here is the error:

Image
Squeezer
Influencer
 
Posts: 23
Liked: 1 time
Joined: Mon Jan 14, 2013 3:50 pm

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby Gostev » Tue Apr 16, 2013 8:40 pm

I am not aware of such limitation. Please open a support case for investigation, and include support case ID in this topic for further reference.
Gostev
Veeam Software
 
Posts: 21396
Liked: 2350 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby ravelin » Mon Apr 22, 2013 2:38 pm

I have the exact same error. 72 hours and a couple of minutes.

Code: Select all
METZFIL   Error   14:08:39   14:10:55 (+3)   1,2 TB   27,1 GB   12,2 GB   72:02:15    Error: Client error: The device is not ready. Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1519\Hyper-V\Virtual Hard Disks\METZFILE_D.vhd]. Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1519\Hyper-V\Virtual Hard Disks\METZFILE_D.vhd]." Unable to retrieve next block transmission command. Number of already processed blocks: [4704744].

Then tried Again on NeXT Schedule:
METZFIL   Error   02:46:44   02:49:03 (+3)   1,2 TB   27,1 GB   12,2 GB   72:02:18    Guest is still being processed by the previous session
Error: Client error: The device is not ready. Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1533\Hyper-V\Virtual Hard Disks\METZFILE_D.vhd]. Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1533\Hyper-V\Virtual Hard Disks\METZFILE_D.vhd]." Unable to retrieve next block transmission command. Number of already processed blocks: [4562044].
ravelin
Veeam ProPartner
 
Posts: 44
Liked: 3 times
Joined: Mon Apr 30, 2012 9:37 am
Full Name: Kenneth Westergaard

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby Squeezer » Mon Apr 22, 2013 2:58 pm

Gostev wrote:I am not aware of such limitation. Please open a support case for investigation, and include support case ID in this topic for further reference.


I have opened support case 00199309.
Squeezer
Influencer
 
Posts: 23
Liked: 1 time
Joined: Mon Jan 14, 2013 3:50 pm

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby Gostev » Mon Apr 22, 2013 11:42 pm

To me, both errors look like dropped network connection between proxy and repository.
Gostev
Veeam Software
 
Posts: 21396
Liked: 2350 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby Amyd » Tue Jul 09, 2013 7:22 am

Any progress on this issue, maybe a workaround? I have (almost) the same behaviour: long backup of a large VM (in my case 24 TB with 17 TB used), on a CSV, fails regularly at about 72 hours with a similar error to those mentioned above.

OE-VM-DATEN-02Error17:39:5517:41:59 (+3)23,6 TB0,0 KB0,0 KB72:02:04 Error: Client error: Der Datentr�ger einer Datei wurde extern so ge�ndert, dass die ge�ffnete Datei nicht mehr g�ltig ist. Error code: 1006 Failed to read data from the file [\\?\GLOBALROOT\Device\CSV{890ba7f8-1a2c-4473-99ff-e4652ed9bb2c}\HyperV\Virtuelle Computer\OE-VM-Daten-02\OE-VM-Daten-02-LW_D.vhdx]. Failed to read data from the file [\\?\GLOBALROOT\Device\CSV{890ba7f8-1a2c-4473-99ff-e4652ed9bb2c}\HyperV\Virtuelle Computer\OE-VM-Daten-02\OE-VM-Daten-02-LW_D.vhdx].') Unable to retrieve next block tra


From a previous run:

OE-VM-DATEN-02Error19:11:1819:18:03 (+3)23,6 TB0,0 KB0,0 KB72:06:44 Error: Client error: Der Datentr�ger einer Datei wurde extern so ge�ndert, dass die ge�ffnete Datei nicht mehr g�ltig ist. Error code: 1006 Failed to read data from the file [\\?\GLOBALROOT\Device\CSV{8754bc4c-d5e1-4221-853d-313c143d484e}\HyperV\Virtuelle Computer\OE-VM-Daten-02\OE-VM-Daten-02-LW_D.vhdx]. Failed to read data from the file [\\?\GLOBALROOT\Device\CSV{8754bc4c-d5e1-4221-853d-313c143d484e}\HyperV\Virtuelle Computer\OE-VM-Daten-02\OE-VM-Daten-02-LW_D.vhdx].') Unable to retrieve next block tra


I doubt it is network connectivity, in my case it is not a WAN backup, but a local LAN backup.
Amyd
Influencer
 
Posts: 11
Liked: 1 time
Joined: Fri Dec 14, 2012 6:42 pm

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby ravelin » Tue Jul 09, 2013 7:32 am

I moved my backup server to the lan of the big machine, and got a full backup in less than 72 hours.
I then moved it back to the original location. I never got it fixed, and renegotiation of the VPN tunnel takes place much more often than 72 hours. I doubt it was a connectivity problem.
If it is, than it must be Veeam or MS. Maybe max of a SMB session?
ravelin
Veeam ProPartner
 
Posts: 44
Liked: 3 times
Joined: Mon Apr 30, 2012 9:37 am
Full Name: Kenneth Westergaard

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby v.Eremin » Tue Jul 09, 2013 10:01 am

According to the OP’s ticket, support team has developed a fix for him that increases this interval from 72 to 168 hours. So, I strongly recommend you contacting them in order to get the aforesaid solution.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13291
Liked: 973 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby ravelin » Tue Jul 09, 2013 11:10 am

Ok, would have been nice of him to inform the thread viewers of a fix :(
I will ask for it, if we get the problem on other customers.
ravelin
Veeam ProPartner
 
Posts: 44
Liked: 3 times
Joined: Mon Apr 30, 2012 9:37 am
Full Name: Kenneth Westergaard

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby v.Eremin » Tue Jul 09, 2013 11:30 am

I believe the reason that OP has never come back was that the proposed solution didn’t work for him, since in his case a given job couldn’t finish even in 168-hour period. Thanks.
v.Eremin
Veeam Software
 
Posts: 13291
Liked: 973 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby Squeezer » Sun Jul 14, 2013 10:00 pm

Veeam technical support sent me a patch which increased the backup timeout to 168 hours. That still was not enough time. Veeam support replied that a limitation in Microsoft C# prevented them from creating a job that could run more than 168 hours.

So, instead I am using Microsoft DFS to push the data to the off-site servers for disaster recovery.
Squeezer
Influencer
 
Posts: 23
Liked: 1 time
Joined: Mon Jan 14, 2013 3:50 pm

Re: Veeam errors after about 72 hours into running a backup

Veeam Logoby Gostev » Sun Aug 04, 2013 9:44 pm

It is quite scary to run VM off snapshots for over 168 hours in the first place.
However, this seems like a perfect use case for Backup Copy functionality of v7.
Gostev
Veeam Software
 
Posts: 21396
Liked: 2350 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 3 guests