NetBackup status codes related to VMware

Article:HOWTO70948  |  Created: 2012-02-08  |  Updated: 2013-10-02  |  Article URL http://www.symantec.com/docs/HOWTO70948
Article Type
How To


Subject


NetBackup status codes related to VMware

This topic provides assistance for NetBackup status codes relating to NetBackup for VMware.

Table: NetBackup status codes related to VMware

NetBackup status code

Explanation and recommended action

1, the requested operation was partially successful

This error may occur during restore, when the virtual machine cannot be imported into vCloud. In the Activity Monitor, the Detailed Status tab of the job details includes messages from vCloud Director that indicate the reason for the error.

The restored virtual machine is present on the destination vCenter: you must manually import it into vCloud.

5, the restore failed to recover the requested files

For a virtual machine restore that uses Instant Recovery, this error can occur for the following reasons:

  • A name was specified incorrectly for the resource pool or temporary datastore.

  • The virtual machine cannot be mounted or activated in vSphere.

Ensure that the names for the required parameters are specified correctly. Also, check for known issues in the vSphere tasks or events.

For detailed debugging, consult the bpVMutil logs on the restore host:

install_path\NetBackup\logs\bpVMutil

6, the backup failed to back up the requested files

This error can occur for the following reasons:

  • The virtual machine and the alternate client virtual machine may contain too many disks. If the total is too great for the alternate client SCSI controllers, a backup with the hotadd transport mode fails. The following appears in the job status log: ERR - Error opening the snapshot disks using given transport mode: Status 23.

    Add more SCSI controllers to the alternate client virtual machine.

  • If the VMware backup host cannot access the datastore over the selected transport mode, the backup fails. The detailed status log on the backup host may contain the following:

    12/4/2009 1:12:34 PM - Error bpbrm(pid=21376) from client vm4: ERR -
     Error opening the snapshot disks using given transport mode: Status 23.
    

    Select a different transport mode and retry the backup.

  • Storage vMotion migrated the virtual machine's files when NetBackup performed a backup of the virtual machine directly through the ESX server. To avoid conflicts with Storage vMotion in vSphere 5.0 or later, NetBackup should conduct backups through the vCenter server.

    See Conflict between NetBackup and VMware Storage vMotion with vSphere 5.0 or later.

  • For the backups that use the hotadd transport mode: The backup host was unable to resolve the host name of the ESX server. This error may occur if DNS is not correctly configured on the virtual machine where the backup host is installed. On the virtual machine, you can enter the IP address of the ESX server into the hosts file: \Windows\System32\drivers\etc\hosts

  • For the backups that use the hotadd transport mode: If the virtual machine to back up and the virtual machine that contains the hotadd backup host do not reside in the same datacenter: The backup fails. For a successful hotadd backup, the two virtual machines must be in the same VMware datacenter.

  • A previous hotadd backup of the virtual machine may have failed. Certain mount directories or cloned disks must be manually removed to allow hotadd backups to succeed, as follows:

    • During a hotadd backup, VMware creates a linked clone of the virtual machine's disks and attaches the cloned disks to the backup host. (The attached disks can be seen in the vSphere Client interface.) If a hotadd backup of the virtual machine fails, NetBackup may be unable to remove the cloned disks from the backup host. In the backup host, the presence of the cloned disks prevents subsequent backups from completing.

      Remove the cloned disks from the VMware backup host and retry the backup.

    • During a virtual machine backup, VMware creates mount directories in the C:\Windows\Temp folder on the backup host. After the backup, VMware automatically removes the mount directories. In some cases, such as when the backup uses the hotadd transport mode, NetBackup may be unable to remove the mount directories.

      Remove the mount directories from the \Temp folder and retry the backup. The folder name contains a string such as VMware-System.

16

For a virtual machine restore that uses Instant Recovery, the recovery host was not Windows. Virtual machine Instant Recovery currently requires a Windows recovery host. (Linux support is planned for a future release.)

20, invalid command parameter

For the Backup Media Server option, the storage unit that is specified in the policy must be unique to your media servers. If the storage unit is also available on another media server, the snapshot job cannot succeed.

21, socket open failed

The NetBackup media server may not have the Services for Network File System (NFS) installed. As a result, the media server cannot contact the Portmapper service. The attempt to manually start the NFS services fails because the Network File System is not installed.

Install the Services for Network File System on the media server.

See About installing and configuring Network File System (NFS) for Granular Recovery Technology (GRT).

156, snapshot error encountered

A number of different issues can cause this error.

See Snapshot error encountered (status code 156).

227, no entity was found

To restore selected files (not the entire virtual machine) to the original location, you must specify the host name of the virtual machine. Do not specify the display name or UUID as the destination.

2817, 2820

A virtual machine restore may fail in the following cases:

  • If an .ISO file was presented to a virtual machine as a virtual CD or DVD during backup, note: The ISO file must be available on the destination host. If the ISO is not available on the host where you restore the virtual machine, the restore fails. The vCenter interface may include the message Invalid configuration for Device '1'.

  • For a restore that uses the hotadd transport mode: If the virtual machine to restore and the virtual machine that contains the hotadd restore host do not reside in the same datacenter: The restore fails. For a successful hotadd restore, the two virtual machines must be in the same VMware datacenter.

  • The restore host cannot access the VMware datastore over the selected transport mode. The job log on the restore host may contain messages such as the following:

    FTL - Virtual machine restore: VxMS initialization failed
    

    Select a different transport mode and retry the restore.

  • You attempted to restore a file that has a path name longer than 1023 characters.

    Note that a backup of a Linux virtual machine backs up all files, including those with path names longer than 1023 characters. A restore of the entire Linux virtual machine recovers all files. But you cannot restore the long path-name files individually.

  • If the ESX servers are configured with short host names (not fully qualified), NetBackup may not find the ESX server for the restore.

    See The restore fails if ESX servers use short host names and backups and restores use a vCenter server.

  • For the restore, the virtual machine's hardware version (such as 7) is later than the hardware version that the target server supports. If VMware Tools cannot convert the virtual machine's hardware version to an earlier version, the restore fails. Messages similar to the following appear in the detailed status log:

    Info bpVMutil(pid=6268) INF - vmwareLogger: 
    WaitForTaskCompleteEx: The virtual machine version is not
    compatible with the version of the host <hostname>.
    

    If possible, restore the virtual machine to a VMware server that supports the virtual machine's hardware version.

2848

During the restore, NetBackup cannot create the virtual machine. This error can occur for a variety of reasons such as the following:

  • Credentials for the VMware server do not have sufficient permissions to create a virtual machine.

  • Insufficient space on a datastore.

  • Incompatible virtual machine or vmdk configurations.

  • Error or task cancellation on the VMware server.

The Job Details tab should contain additional information. The VMware server logs may also have information on the error.

See Notes on troubleshooting NetBackup for VMware


Legacy ID



v37089086_v71073983


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


Terms of use for this information are found in Legal Notices