Backup Target wiped - restore from tape, but job fails

[egroeg]

dear community.

Veeam San based backup to disk including 20 vms reversed incremental.

My backup SAN died and following a recovery, I restored the backup files from the last tape backup.

The destination is now populated with a range or vrb files, but when I try to connect my job it fails looking for a file (which is not present).

I believe my last tape backup of the backup files is OLDER than the last run backup conducted by Veeam, so it's looking for a file that doesnt exist.

Is there a way to get veeam to just now write to the backup respository that has been restored and just make the delta changes as opposed to conducing a new FULL backup (which will take a couple of days?)

Error message below:

Details
Publishing catalog session
Failed to delete oib '[vmname=SVR99.DOMAIN.co.uk:creation_time=24/06/2011 00:37:40:alg=Syntethic:id=a5e3ad63-315e-49b8-82cd-4e91e3b753f5:point_id=986191c1-ba43-43ea-ab21-9f0f879c1598:storage_id=c79d14d2-fd75-425c-9105-e543cc7142f7]' from '\\domain\veeam$\Domain_Regular_Backup_T1\Domain_Regular_Backup_T12011-06-24T105148.vbk', redo '\\domain\veeam$\domain_Regular_Backup_T1\domain_Regular_Backup_T12011-06-22T145333.vrb'
Dir failed, storageFileName "\\domain\veeam$\domain_Regular_Backup_T1\domain_Regular_Backup_T12011-06-22T145333.vrb"
The system cannot find the file specified
Failed to open file [\\domain\veeam$\domain_Regular_Backup_T1\domain_Regular_Backup_T12011-06-22T145333.vrb] in readonly mode.

[Vitaliy S.]

George,

If you have a missing VBK/VRB file in the backup chain then you should run a full job pass. There is no possibility to "map" existing job to older backup files.

Thanks.

[egroeg]

Ok, this makes sense.

However, I have now cleared my target folder so it is empty and have submitted the job again "Start full backup" and sadly the job still errors looking for the file.

I dont really want to re-create the new job, I can live with it re-writing the data for another 48 hours, but is there a way I can make the job kick off fresh again (as if for the first time) without it seeking it's previous historic backup file data.

[Vitaliy S.]

In order to achieve that just navigate to backups node and remove the corresponding restore points records from the SQL database by clicking to "Delete from Disk" option while standing on the backup job name. This should allow you to re-start the backup job successfully.