KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : Remote Virtual Standby fails after a warning as - "Virtual Standby job failed because backed-up files are damaged. Please manually submit a full backup to resume Virtual Standby job"

Last Update: 2016-04-25 14:37:24 UTC

Description:

The environment consists of R16.5 Update 1 Central Virtual Standby. A Remote Virtual Standby Policy is being used.
The Recovery points of Central Host Based Backup are being replicated using ARCserve RHA scenario.
The nodes are imported from Virtual Standby using ' Import Nodes from CA ARCserve Replication'

The Remote Virtual Standby fails with the following error seen from the Activity log of that node. These logs will be present on the Convertor node that is defined through the Remote Virtual Standby Policy.

50248f3e-7a28-8df4-acdc-be3b19552e0d.activity.log

2013/12/03  09:16:34 - Information: Job00000170 - VM was created. VM name is VSVM_#######.
2013/12/03  09:16:35 - Information: Job00000170 - Virtual Standby job will convert session(s):S0000000023.
2013/12/03  09:20:04 - Information: Job00000170 - Upload meta data to VM.
2013/12/03  09:32:43 -   Warning: Job00000170 - Virtual Standby job failed because backed-up files are damaged. Please manually submit a full backup to resume Virtual Standby job.
2013/12/03  09:32:43 -     Error: Job00000170 - Failed to convert session[S0000000023] to the host for VM[VSVM_#######

Solution:

From the Convertor node, we will find the following errors in the System Event Logs:

Event Id 16 Volsnap

The shadow copies of volume D: were aborted which contains shadow copy storage for this shadow copy, was force dismounted

To resolve this, one of the solutions recommended is to change the storage area volume defined in the Shadow Copy settings of that volume to a different volume.

For eg: In this case, the volume was changed from D to volume C

Reference Link from Microsoft Technet: http://technet.microsoft.com/en-us/library/cc734315(v=ws.10).aspx

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments