Restore notes and restrictions

Article:HOWTO44420  |  Created: 2011-03-15  |  Updated: 2011-03-22  |  Article URL http://www.symantec.com/docs/HOWTO44420
Article Type
How To


Environment

Subject


Restore notes and restrictions

This topic relates to restores from a NetBackup backup of a VMware virtual machine.

Before you begin the restore, note the following:

  • Unless a NetBackup client is installed on the virtual machine, you must do the restore from the NetBackup master server.

  • To restore files to the original virtual machine location, the destination must be specified as the virtual machine's host name (not display name or UUID).

  • Cross-platform restore is not supported. You can restore Windows files to Windows guest operating systems but not to Linux. You can restore Linux files to supported Linux guest operating systems but not to Windows.

  • If the virtual machine was backed up by its display name or UUID, and the display name differs from the host name, note: You must specify the correct destination client for the restore. Use the Specify NetBackup Machines and Policy Type dialog in the NetBackup Backup, Archive, and Restore interface.

    See Invalid client error when you restore files using NetBackup BAR interface installed on the virtual machine.

  • Restore of individual files from a backup of the full virtual machine is not supported if the virtual machine contains Storage Foundation Volume Manager volumes.

  • To restore Windows NTFS-encrypted files individually, you must install a NetBackup client on the virtual machine.

    See NetBackup for VMware best practices.

  • For virtual machine restores, VMware supports the NBDSSL transfer type only for vStorage backups of vSphere 4.1 and later environments. Backups of VMware systems that are earlier than vSphere 4.1 cannot be restored using the NBDSSL transfer type.

  • If the attempt to restore a full virtual machine fails while using the SAN transport type, try the NBD transport type instead.

  • For the SAN transfer type, the job may be slow when you restore to a vCenter Server. For greater speed, designate an ESX server as the destination for the restore.

    Note that you can set up an ESX server to be used for restores. You can add NetBackup restore credentials for that ESX server by means of the VMware restore ESX server server type.

    See Adding NetBackup credentials for VMware.

  • A restore by means of the SAN transfer type may be slow in other circumstances. The following VMware article provides details:

    Best practices when using SAN transport for backup and restore

  • If the restore host is on Windows Server 2008 and you use the SAN transfer type for the restore, the SAN luns must be online. Refer to the information on status code 5 in the following section:

    See NetBackup status codes related to VMware.

  • When restoring large files, make sure that no snapshots are active on the destination virtual machine. Otherwise, the files are restored to the VMware configuration datastore, which may be too small to contain the files you want to restore. In that case, the restore fails.

    The configuration datastore (sometimes called the vmx directory) contains the configuration files that describe the virtual machine, such as *.vmx files. Note that active snapshots of vmdk files are also stored on the configuration datastore.

  • If you cancel the virtual machine restore before it completes, the not-fully-restored virtual machine remains at the target location. NetBackup does not delete the incomplete virtual machine when the restore job is canceled. You must manually remove the incomplete virtual machine.

  • If the virtual machine display name contains non-ASCII characters, the backup may succeed but the restore fails. To restore the virtual machine, you must change the display name to contain ASCII characters only and retry the restore.

  • During a virtual machine restore, VMware Tools can add a disk controller prefix to the name of each restored .vmdk file. The prefix can be useful when debugging problems with the restore.

    See Adding a disk controller prefix to the restored vmdk file name.

  • See NetBackup for VMware: notes and restrictions.

See Restore notes and restrictions on Linux

See If the recovery host is not at the same NetBackup release level as the backup host


Legacy ID



v19545942_v54266490


Article URL http://www.symantec.com/docs/HOWTO44420


Terms of use for this information are found in Legal Notices