Restore a .vbk file?

[davek0974]

Hi

I need to restore a .vbk file with a new name and location etc, i follow through the options on the restore form but the job fails with a file not found on V:\backups\clones......vbk

We are still running V6.1 but will update soon to 8 but i need to get this VM running in the mean time and this is not giving me any confidence in the restore function at all.

Can anyone help please???

Many thanks

Dave

[Shestakov]

Hi Dave and welcome to the forums!

What kind of restore do you perform? What is the error message?

By the way, have you contacted Veeam technical support? If no, please do, if yes, please include the support case number.
Thanks!

[davek0974]

Hi

i am trying to do a full restore but to new location, new name, new datastore etc.

This is the error log

Code: Select all

11/11/2015 15:20:05          Starting restore job
11/11/2015 15:20:05          Locking required backup files
11/11/2015 15:20:15          Queued for processing at 11/11/2015 15:20:15
11/11/2015 15:20:16          Preparing next VM for processing
11/11/2015 15:20:15          Required resources have been assigned
11/11/2015 15:20:16          Using target proxy VMware Backup Proxy [nbd]
11/11/2015 15:20:25 Fail     Starting restore agents on server "10.0.0.1"
11/11/2015 15:20:25 Fail     Restore job failed Error: Client error: File does not exist. File: [V:\Backups\Clones\Backup_2008r2_Spare_2012-06-07T110343.vbk].
                             Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://Tar2Text]. CHMOD mask: [0].

This is a backup of a new install image.
The vbk file does exist and is on the backup machine and in the backup catalogue
We are still on v6.1 but are working on getting a new server to allow us to move up to v8, i tried to open a ticket but they no longer support 6.1

[foggy]

Try to rescan the repository. If that doesn't help, try the extract.exe utility.

[veremin]

If extract utility doesn't help, request v7 bits from support team. Update your installation and let engineers investigate it directly. Thanks.

[davek0974]

Try to rescan the repository. If that doesn't help, try the extract.exe utility.

Brilliant, the Rescan Repository did the trick

Thanks