Reg hack to ForceCreateMissingVBK not working v5

[withanh]

I had enabled the Reg hack to ForceCreateMissingVBK set for my v4 and that has been working great, but after installing to v5 it has stopped working. Should this still work, or is there an alternate method?

Code: Select all

Publishing catalog session
Storage file '\\disk02\backups\DR_Copy\DR_Copy2010-11-06T060038.vbk' is missing from host 'My Computer'. If you are using initial replica seeding, please follow the instruction from the readme.txt file in the chosen seeding location. If you changed replica destination in the replication job settings, please make sure you have moved all replica files to the new destination correctly.

If I delete the backups from the backup manager then restart the job it completes properly.

Thanks,

Darhl

[Vitaliy S.]

Hi Darhl,

All registry keys including ForceCreateMissingVBK should be created under Veeam Backup and Replication subkey and not under Veeam Backup and FastSCP as they previously were.

Please make sure you've specified it in the right place and re-run the backup job, should help.

Thanks!

[withanh]

Thanks Vitaliy! I made that change. I won't know until next week if it works or not because I already removed the weekly backups from the backup manager. I'm sure it will be fine.

Appreciate the fast reply!

Darhl

[bctirado]

Did applying this change work for you? I've applied it to the new location and have rebooted the backup server but I'm still getting the same error message at multiple sites.

Brian

[withanh]

Hi Brian,

It's working fine for me.

Darhl

[bctirado]

Cool thanks for the reply and just to confirm the following is what you're using right?

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication]
"ForceCreateMissingVBK"=dword:00000001

[withanh]

Yep, looks the same as mine

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication]
"ForceCreateMissingVBK"=dword:00000001

[bctirado]

Ok thanks for checking.

Brian