Managing a disaster condition

[marius roma]

Imagine the following scenario:
There is a Veeam server whose name is VeeamServer
The backup job Job001 creates a reverse incremental backup on NAS001.
On Monday night Job001 updates the backup on NAS001.
On Tuesday morning VeeamServer is backed up using a Symantec backup tool.
On Tuesday night Job001 updates the backup on NAS001
On Wednesday morning VeeamServer crashes and is restored from the Symantec backup token on Tuesday morning.
At that point the restored VeeamServer does is unable to read the backup produced by Job001 on NAS001 that is updated to Tuesday night.
I attempted to import the backup produced by Job001 but VeeamServer says that Job001 already exists.
How can I import the backup produced by Job001 (and updated to Tuesday night) without deleting the data on NAS001?
The backup job contains critical data and I cannot risk to loose it…
Is there a procedure for such kinf of situations?
Can anybody please help?
Regards
marius

[Gostev]

To avoid these issues, you should do a Veeam configuration restore > https://helpcenter.veeam.com/backup/vsp ... onfig.html

[marius roma]

I do understand, but the problem occurred and I have no configuration backup...
Given NAS001 contains a valid backup but (the restored) VeeamServer does not recognize the file names, how can I import it in VeeamServer ?
Can I simply delete the backup job and re-import it?
Is there any risk to damage the backup files on NAS001 while deleting the backup on VeeamServer and re-importing it from the files?
Can I simply rename the folder on NAS001, delete the job on VeeamServer and try to re-import it?
Is there any other possible solution?
Regards
Marius

[foggy]

Mario, have you tried to rescan the repository after restoring Veeam B&R server?