Troubleshooting - Xen Restore

REstore of VDI Objects Fails

Cause

The restore of VDI objects may fail when the configuration files required for VDI objects are not selected for restore.

Solultion

When you select a VDI object for the restore, select all the configuration files required for the VDI object and then perform the restore.

Restore Fails with error: "Failed to plug in new VBD: --- SR_HAS_NO_PBDS"

This failure occurs when the storage repository selected is not visible to the Xen Server on which the Agent is installed.

In addition to the above-mentioned error message, the following Job Pending Reason will appear in the CommCell Console:

Unable to write data to the Virtual Disk. Please ensure that the proxy is able to communicate with the Virtual Machine Host and that there is sufficient disk space available

To resolve this issue, ensure the storage repository selected is visible to the Xen Server on which the Agent is installed.

Virtual Machine NICs are not visible after a restore

After a restore operation, NICs are not automatically restored. You must manually restore NICs, and then all of the old settings will automatically inherit.

Virtual Machine Does not Turn on Automatically after the Restore

A Production Citrix License is required to automatically turn on the virtual machine. If you are using the evaluation license or free edition of Citrix XenServer, you must manually set the memory usage for the virtual machine, and then turn on the virtual machine.

Recovering Data Associated with Deleted Clients and Storage Policies

The following procedure describes the steps involved in recovering data associated with the following entities:

• Deleted Storage Policy
• Deleted Client, Agent, Backup Set or Instance

Before you Begin

This procedure can be performed when the following are available:

• You have a Disaster Recovery Backup which contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup which was performed before deleting the storage policy.
• Media containing the data you wish to recover is available and not overwritten.
• If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:
  • IP Address Change license
  • CommCell Migration license

  See License Administration for more details.

• A standby computer, which will be used temporarily to build a CommServe.

Recovering Deleted Data

1. Locate the latest Disaster Recovery Backup which contains the information on the entity (Storage Policy, Client, Agent, Backup Set or Instance) that you are trying to restore.
   • You can check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.
   • If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.
   • If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:

     If you regularly run and have copies of the Data on Media and Aging Forecast report you can check them to see if the appropriate media is available.

2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see CommServe Deployment.
3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See Restore a Disaster Recovery Backup for step-by-step instructions.)
4. Verify and ensure that the Bull Calypso Client Event Manager Bull Calypso Communications Service (EvMgrS) is running.
5. If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.
6. Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.

   When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.

7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

   This will bring back the entity in the CommServe database and the entity will now be visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

8. If you have additional data that was backed up after the disaster recovery backup and before the deletion of the entity, use the procedure described in Import Metadata from a Tape or Optical Media to obtain the necessary information.
9. You can now browse and restore the data from the appropriate entity.

   As a precaution, mark media (tape and optical media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.

File level restore fails

Symptom

While restoring files and folders from a virtual machine, you may get following error:

Volume name not found in the restore source path <source_path>, this is a volume restore.

Cause

This error appears when you have selected all files and folders in a virtual machine for the restore.

The file level restore of entire contents of the VM is not supported.

Solution

If you want to restore entire contents of a VM, perform a full VM restore.

Back to Top