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
6, the backup failed to back up the requested files
This error can occur for the following reasons:
Taken together, the virtual machine and the alternate client virtual machine may contain too many disks. If the total is too great for the alternate client's SCSI controllers to handle, a backup or restore using the hotadd transfer type fails. The following message appears in the job's detailed status log:
ERR - Error opening the snapshot disks using
given transport mode: Status 23.
Add more SCSI controllers to the alternate client virtual machine.
For vStorage backups: If the VMware backup host cannot access the VMware datastore by means of the transfer type that was selected for the job, the backup fails.
The job's detailed status log on the backup host may contain messages such as the following:
12/4/2009 1:12:34 PM - Error bpbrm(pid=21376) from
client moneevm4_clone: ERR - Error opening the snapshot
disks using given transport mode: Status 23.
12/4/2009 1:12:39 PM - Error bpbrm(pid=21376) could not
send server status message
12/4/2009 1:12:40 PM - end writing; write time: 00:00:28
the backup failed to back up the requested files(6)
Select a different transfer type and retry the backup.
For the backups that use the hotadd transfer type: 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:
For the backups that use the hotadd transfer type: If the virtual machine to back up and the virtual machine that contains the hotadd backup host do not reside in the same VMware 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 transfer type, 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.
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.
2805 (MS-Windows policy restore error), 2817 (FlashBackup-Windows policy restore error)
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, the ISO file must be available on the destination host. If the ISO file is not available on the host where you restore the virtual machine, the restore fails. Note that the Virtual Infrastructure interface on the VirtualCenter may include the following message:
Invalid configuration for Device '1'
The VMware restore host is on Windows Server 2008 but the SAN LUNs are offline.
The detailed status log that is in the NetBackup Activity Monitor includes the message Virtual machine restore: file write failed.
If the restore host is on Windows Server 2008 and you use the SAN transfer type, you must manually change the SAN LUNs to be online.
For restores that use the hotadd transfer type: If the virtual machine to restore and the virtual machine that contains the hotadd restore host do not reside in the same VMware datacenter, the restore fails. For a successful hotadd restore, the two virtual machines must be in the same VMware datacenter.
For vStorage restores: The restore host cannot access the VMware datastore by means of the transfer type that was selected for the job. The job's detailed status log on the restore host may contain messages such as the following:
3:26:43 INF - Beginning read-blockmap on server luebeck
of client moneevm4, reading file h:\dstu\moneevm4_1259284475_C1_F1.
13:27:21 (19400.001) INF - TAR STARTED
13:27:23 (19400.001) INF - Beginning restore from server lub
to client lub.
13:27:36 (19400.001) FTL - Virtual machine restore: VxMS initialization
13:27:37 (19400.001) FTL - Virtual machine restore: file create failed
13:28:42 (19400.001) INF - TAR EXITING WITH STATUS = 5
13:28:42 (19400.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY
13:28:42 (19400.001) INF - TAR KEPT 0 EXISTING FILES
13:28:42 (19400.001) INF - TAR PARTIALLY RESTORED 0 FILES
13:29:54 (19400.xxx) INF - Status = the restore failed to recover
the requested files.
Select a different transfer type 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.
See Notes on troubleshooting NetBackup for VMware