- Veeam ProPartner
- Posts: 158
- Liked: 20 times
- Joined: Jun 09, 2009 2:48 pm
- Full Name: Lucio Mazzi
- Location: Reggio Emilia, Italy
On the first successful SB run, it appeared that one VM of the job would not start, due to a "ntoskrnl.exe missing or corrupt" error. An Instant Recovery of this VM confirmed that its backup was corrupt. The backup job is configured as reverse incremental with no active fulls (incremental forever), so the buggy blocks in the backup file would never be refreshed. I see that without a SureBackup run this would have gone unnoticed, as the daily jobs go just fine. As for the cause of the corruption, this might very well be caused by some storage issue, as no problem was logged at backup time by VBR. So it is very clear now that checking every backup with SB is at least as vital as it was the "verify backup" option in the old-style backup applications.
To correct the corrupt VM image an active full is in order. An active full for the whole job takes too long and exceeds the standard backup window. My question is, is it possible to force an active full for just one VM or selected VMs of the job? Would this be a desirable feature for a future release?
If I delete the faulty VM from the backup file (not from the backup job) using the "remove from disk" option from the Backups->Disk pane, would this force an active full for that VM only on the next job run?
- Product Manager
- Posts: 22747
- Liked: 1519 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Yes, that should force our job to create a new full backup of this VM.Moebius wrote:If I delete the faulty VM from the backup file (not from the backup job) using the "remove from disk" option from the Backups->Disk pane, would this force an active full for that VM only on the next job run?
- Posts: 226
- Liked: 28 times
- Joined: Jan 27, 2012 11:31 am
- Full Name: Hani El-Qasem
You could try this handy powershell script:
http://vpowercli.wordpress.com/2012/01/ ... -in-a-job/
On line 18 add the switch -FullBackup to the Start-VBRjob cmdlet. That should force a full instead of incremental.
Users browsing this forum: Baidu [Spider] and 26 guests