Disk failure with disabled backup jobs

[teh1tn1nj4]

Hello,

We had a disk array failure that held our backup jobs for vmware esxi. We are running version 6.5. First thing I did was to disable our nightly backup jobs. (We still have replicas that are running separate of this disk array)

I'm in the process of rebuilding a new array as a repository for our backups. After this rebuild is complete, can I simply re-enable the disabled backup jobs? Will they realize that they have no previous restore points and start a fresh job? Is it necessary to clean up the jobs of any previous restore points so they are all starting fresh? I'm trying to avoid having to rebuild all my jobs again.

[Gostev]

Hi, if you are using reversed incremental backup mode, you can avoid re-creating the jobs with the ForceCreateMissingVBK registry key. Otherwise, I am afraid you will have to create new jobs, as the existing ones will be failing due to not being able to find earlier backups. Thanks!

[tsightler]

Or you can just go to Backups...Disks, right click, and choose "Remove from backups" (no need to pick "Remove from disk" since the files are already gone). This removes the old backup chain from the database, but leaves the job intact. On the next job run the job will start from scratch. No registry key needed, no job recreation needed. Note that you can even multi-select in this screen so this is easy even if you have a lot of jobs.

[Gostev]

I did not know this would work, thanks Tom.

[larry]

Clone the job and use the clone, new files are made. painless.

[Gostev]

Yep, that will work too

[veremin]

As to cloning jobs/removing jobs, this process can be automated using PS. Something like this should help:

Code: Select all

asnp VeeamPSSnapin
Foreach ($Job in (Get-VBRJob | where {$_.Jobtype -eq "Backup"})
{
$Job.disablescheduler()
Copy-VBRJob -Job $Job
Remove-VBRJob -Job $Job
} 

Thanks.