Failed to repair VM '<VMNAME>'

Availability for the Always-On Enterprise

Failed to repair VM '<VMNAME>'

Veeam Logoby B.F. » Mon Jun 13, 2016 2:00 pm

For reason's I'm not sure yet, we have a backup to disk that failed:
Full backup file merge failed Error: Insufficient system resources exist to complete the requested service. Failed to write data to the file [<FILEPATH .vbk>]

Not sure what resources were insufficient since there's still boat loads of space available on the disk.

Now when I try to run or retry the backup:
Error: Failed to repair VM '<VMName>' in backup '5/24/2016 1:05:43 PM'. Unknown algorithm 'TransformForeverIncremental'

Any suggestions on how to repair this?

Thanks
B.F.
Expert
 
Posts: 130
Liked: 6 times
Joined: Tue Jan 28, 2014 5:41 pm

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby PTide » Mon Jun 13, 2016 2:54 pm

Hi,

Please contact our support team so they can investigate the error and post your case ID here.

Thanks
PTide
Veeam Software
 
Posts: 3147
Liked: 262 times
Joined: Tue May 19, 2015 1:46 pm

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby B.F. » Mon Jun 13, 2016 3:21 pm

Ticket #01825333 opened.
B.F.
Expert
 
Posts: 130
Liked: 6 times
Joined: Tue Jan 28, 2014 5:41 pm

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby electricd7 » Wed Jul 06, 2016 7:42 pm

We are seeing this exact same behavior. Are you by chance backing up to a scale-out repository? We didn't start seeing these until we started using the new scale-out repositories. I have had a case open (#01813976) since 5/31 and still no resolution. At first they pointed to my repository as we were using 2012 storage spaces to span disks into a large volume to use as the repository. They had me change to just a single large disk (we are using VMware so we just created a large VMDK) and started a new chain at that new repository (a member of a new scale-out repository as the only member.) We just crossed the retention period where a merge needed to happen and have the same error again on the new storage!
electricd7
Expert
 
Posts: 103
Liked: 5 times
Joined: Tue Mar 27, 2012 10:13 pm
Full Name: Chad Killion

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby B.F. » Thu Jul 07, 2016 2:03 pm

Our repository is quite basic and had been used for a while now. The error only happened once and ended up needing to start a new chain of backups as well as added some more system memory to the backup server. So far so good.
B.F.
Expert
 
Posts: 130
Liked: 6 times
Joined: Tue Jan 28, 2014 5:41 pm

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby ccatlett1984 » Mon Aug 15, 2016 1:27 pm

I just upgraded last week (from v8) and am seeing the same thing on a few jobs, but not all.

I have opened case # 01880151
ccatlett1984
Enthusiast
 
Posts: 83
Liked: 9 times
Joined: Thu Oct 31, 2013 5:11 pm
Full Name: Chris Catlett

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby prabhash.jena » Thu Oct 06, 2016 9:27 am

B.F. wrote:Our repository is quite basic and had been used for a while now. The error only happened once and ended up needing to start a new chain of backups as well as added some more system memory to the backup server. So far so good.


Hi,

Were Veeam able to fix this or you ended up creating new job?

Regards
Prabhash
prabhash.jena
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Fri Jan 16, 2015 1:32 pm
Full Name: Prabhash Kumar Jena

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby v.Eremin » Thu Oct 06, 2016 10:15 am

A new backup chain was started. Most likely, a new active full backup was created. Besides that, system resources available for a backup server were increased. Thanks.
v.Eremin
Veeam Software
 
Posts: 13563
Liked: 1007 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby prabhash.jena » Thu Oct 06, 2016 12:27 pm

Hi,

I applied some fixes such as removing backup from configuration, rescan of scale out repository, run an active full, exclude the VM in question from backup job, perform a quick backup of the VM in question reboot of repository server but nothing worked. I created new job and am keeping the data from old job for restoration. I have plenty of resources on the servers so I am sure that's not the issue.

This is not a pleasant experience, 1 VM backup file corruption leading to corruption of whole job. I believe there can be a database fix for this.

Regards
Prabhash
prabhash.jena
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Fri Jan 16, 2015 1:32 pm
Full Name: Prabhash Kumar Jena

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby v.Eremin » Thu Oct 06, 2016 12:33 pm

I believe there can be a database fix for this.

And have you tried to reach our support team to check the availability of the said fix? Thanks.
v.Eremin
Veeam Software
 
Posts: 13563
Liked: 1007 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby dpatel » Tue Nov 15, 2016 8:51 am

Hi,

We are facing same problem on our one of the backup job. We are using Veeam 9.0.0.1715 with scale-out repository.

On same repository other backups are working fine without any error.

Thanks,
Daxesh
dpatel
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Nov 14, 2016 10:35 am

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby foggy » Wed Nov 16, 2016 1:19 pm

Please contact technical support for troubleshooting. Thanks.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby Steen » Sat Dec 03, 2016 12:07 pm

I have same problem on several job.
Tha backup-chain is destroyed and forced to make new backup-job.
Sadly this seeams to be an widely spread problem and no fix
Regards Steen
Steen
Enthusiast
 
Posts: 45
Liked: 3 times
Joined: Fri Mar 13, 2015 1:20 pm
Full Name: Steen

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby Gostev » Sat Dec 03, 2016 8:29 pm

The fix is to add some RAM to a repository server (or whatever server runs the target data mover for the corresponding backup repository).
Gostev
Veeam Software
 
Posts: 21517
Liked: 2383 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Failed to repair VM '<VMNAME>'

Veeam Logoby Steen » Sat Dec 03, 2016 9:07 pm

Hi.
How much memory?
We have 32GB on B&R and 32 GBV on all ours repositories so i dont think that is the problem.
Regards Steen
Steen
Enthusiast
 
Posts: 45
Liked: 3 times
Joined: Fri Mar 13, 2015 1:20 pm
Full Name: Steen

Next

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google Feedfetcher and 52 guests