VBK is missing from host

KB ID:
1300
Product:
Veeam Backup & Replication
Version:
4.x, 5.x
Published:
Last Modified:
2014-08-05

Challenge

The Replication job fails with the following error message:

"Initializing target session\nStorage file '[Datastore] VeeamBackup/vmname(vm-xxx)/yyyy-mm-ddxxxxxxx.vbk' is missing from host 'esx.host'. 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."

 Check the ReplicaJob_jobname.log file for the following entries:

 [timestamp] <01> Info Task operation result: 'Storage file '[Datastore] VeeamBackup/vmname(vm-xxx)/yyyy-mm-ddxxxxxxx.vbk' is missing from host 'esx.host'. 

Cause

The replica destination has changed in the job properties, or the replica files have been moved to another location.

Solution

To fix the issue, make sure to follow the instructions below:

1. Unregister the replica VM in its current location (remove from inventory).

2. Copy the VeeamBackup folder with the replica VM files to the new datastore

3. Register the VM (right click the *.vmx file and choose "Add to inventory")

4. Ensure that the new destination path is specified  in the job properties

More Information

If the replica location did not change, check whether the target location contains the *.vbk file specified in the error message. If the file is not present, it should be recreated new to fix the replica. Use the Delete from Disk option on this replica to clear up entries in the database and files from target storage. The next job run will successfully and recreate the replica from scratch.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
2.3 out of 5 based on 18 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit