Veeam server is crashed

[jamerson]

Hi Guys.
Veeam server is crashed after we updated to version 9. the backup and sql backup are on a different storage.
we have the backup files like 3 TB and the VBR Catalogue.
we have installed a new OS now and also VEEAM V9.
when I went to restore the configuration backup veeam cant seem to update which files to restore .
on the VBR Catalogue folder have : Import, Index,Journal..... folder

which folder do I have to chose to restore the configuration backup ?
have followed the next instruction but can't seem to understand which fieles to select.

http://helpcenter.veeam.com/backup/80/f ... aunch.html

thank you

[dellock6]

First of all, since it's v9 you should refer to this user guide:
http://helpcenter.veeam.com/backup/vsph ... e_vbr.html

Then, for a migration from v8 to v9, you should have created the configuration backup on the v8 installation. The resulting backup file should be accessible by the v9 installation in order to proceed with the restore in v9.

If there are issues and the procedure cannot be completed, I suggest to open a support ticket, one of our engineer could help you in completing the restore.

[jamerson]

I don't see that the tutorial is different than one of V8. both are looking for .bco files which I don't have .
I see we imported the cataloges and not the Veeamconfigbackup folder.
to clear this up, veeamconfigbackup and backup files are enough to restore the veeam server in case of failure ?
both of them saved on a SAN / NAS storage outside the Veeam server . is the safest way right ?
After we reinstall the VEEAM server, do we need to do the CBT reset or no need ?
we are on ESXI 6.0 latest build 3380124
just to make sure we wont face the same problem again.

[Gostev]

No need, a single reset is enough.

[jamerson]

what do you mean with a single reset ?

[Gostev]

If you did CBT reset recently (for example, due to the most recent VMware CBT bug), then you do not need to reset it again after reinstalling Veeam server.

[jamerson]

Thank you.
new VEEAM server is up and running.