Discussions specific to the VMware vSphere hypervisor
Post Reply
timmy.olsson@nibe.se
Novice
Posts: 6
Liked: never
Joined: Nov 08, 2011 12:47 pm
Contact:

Corrupt backupjob when running out of storage

Post by timmy.olsson@nibe.se » Nov 25, 2016 3:19 pm

Hello

I've noticed that if you run out of storage your current backupjob will be corrupt and the backupjob fails with:

Rolling back changes made by incomplete job run
Error: Root element is missing.

This has happened to me twice since upgrading to 9.5 and the same error both times. Before upgrading this wasn't a problem, if you run out of space of course the job will fail but run the next time if there where space available.

I've opened a case with the support. Got the expected answer - Create a new backup set.
I tried to explain that I see this as bug introduced in 9.5, but got no understanding in return.
Is this know? Will it be fixed or this is how it will work now?

The strangest in this story is when I today was going to copy the current backupfiles to an other storage and create a new backup set. Now I notice that the job has run during the night, and all old backup files are completely gone?! Only one full backup file left in the folder!

This last thing I haven't been able to recreate.

//Timmy

Gostev
SVP, Product Management
Posts: 24787
Liked: 3516 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Corrupt backupjob when running out of storage

Post by Gostev » Nov 25, 2016 10:39 pm

Hello! Please remember to include support case ID, as requested when you click New Topic. Thanks!

timmy.olsson@nibe.se
Novice
Posts: 6
Liked: never
Joined: Nov 08, 2011 12:47 pm
Contact:

Re: Corrupt backupjob when running out of storage

Post by timmy.olsson@nibe.se » Nov 28, 2016 8:33 am

Sorry, 01985106

//Timmy

foggy
Veeam Software
Posts: 18243
Liked: 1558 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Corrupt backupjob when running out of storage

Post by foggy » Nov 28, 2016 12:32 pm

Hi Timmy, I recommend you escalating the case, since the behavior doesn't look expected, indeed.

Sujith Kumar
Lurker
Posts: 1
Liked: never
Joined: Sep 28, 2019 6:52 am
Full Name: Sujith Kumar
Contact:

Re: Corrupt backupjob when running out of storage

Post by Sujith Kumar » Sep 28, 2019 7:03 am

Anyone got any resolution to this.. i have the same problem..
Dont have space to create another full backup, or create a new backup job. Tried the below but did not work out.

The second option is more involved, has some caveats, and is not guaranteed to work but may save some time.
Verify the job itself is not currently running.
Once verified go into the backup repository and locate the backup files for the job having the issue.
Move the VBM file to another location without deleting it.
After the VBM file has been moved, return to Veeam B&R and run a normal backup operation.

Note: This also works for PerVM and SOBR based backups.

Note 2: When moving the VBM, do so to a path outside the backup repository path. For instance, if the repository path is C:\Backups, move the VBM to either the root of the drive or another path from the drive. If it is placed in another subfolder of C:\Backups, and the repository is re-scanned, Veeam will attempt to import the VBM as a backup.

veremin
Product Manager
Posts: 16875
Liked: 1429 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Corrupt backupjob when running out of storage

Post by veremin » Sep 30, 2019 5:03 pm

Not sure how moving metadata file can fix corrupted backup chain or backup storage lacking free space. So, for anyone affected by the similar problem it's recommended to reach our support team. Thanks!

Post Reply

Who is online

Users browsing this forum: sam.lowry and 30 guests