Sign In

Search <book_title>...

NetBackup™ for Nutanix AHV Administrator's Guide

Last Published: 2024-09-30

Product(s): NetBackup & Alta Data Protection (10.5)

Error run into while backing up AHV virtual machines

The following table describes the problems that might occur when you back up AHV virtual machines:

Table: Error while backing up AHV virtual machines

Error message or cause	Explanation and recommended action
After a NetBackup backup operation, the VM snapshot on the AHV cluster is not deleted.	If a disk attached to the VM is in an inactive state, then the AHV cluster does not delete the VM snapshot after a backup operation is complete. Workaround: Before the backup operation, verify the state of the disks that are attached to the VM and ensure that they are active. Ensure that the disks are not attached while the VM is running, thus preventing the disk to be in an inactive state.
MSiSCSI service is disabled. Enable the MSiSCSI service on the backup host.	Enable the Microsoft iSCSI Initiator Service (MSiSCSI) service on the windows backup host and re-run the job.
Unable to establish a connection. Verify that the iSCSI service is installed and running.	For Windows: Enable the Microsoft iSCSI Initiator Service on the backup host. Note: An error displayed only for windows OS. For Linux, this error is displayed in the form of a warning and it falls back to use the NFS for backup/restore. If you use segmented iSCSI data services backup/restore fails. Ensure that the backup host is added in an `Filesystem Whitelists` option in the Nutanix UI for backups to work by NFS transport. For Linux to use iSCSI: Install / Enable iSCSI Initiator package on backup host and re-run the job. Validate connectivity using the following command on a Linux host:iscsiadm -m discovery -t sendtargets -p correct IP as per configured iSCSITargetType Use following IP address based on your iSCSI transport type: For iSCSI Data services: iSCSI Data services IP from cluster details page For segmented: Use segmented iSCSI Data from cluster details page SEGMENTED_SPECIFIC. For specified segmented: Use Virtual IP specified while you configure a cluster in NetBackup. Validate connectivity using the following command on the Windows host: Click Server Manager -> Tools -> iSCSI initiator. This opens the iSCSI initiator properties dialog. Click Discovery > Discovery portal and provide the IP address as per the configured iSCSI Target Type for the AHV cluster. Default: iSCSI Data services IP from cluster details page SEGMENTED: Segmented iSCSI Data from cluster details page SEGMENTED_SPECIFIC: Virtual IP specified while you configure a cluster in NetBackup. If you get mentioned error when flex or flex scale appliance used as Backup/Recovery host: Edit the configuration to use default option that uses the NFS transport. Use different Backup/Recovery host which has required iSCSI and network configuration. Update the protection plan to use specific Backup host. Use Recovery host with required iSCSI and network configuration.
Authentication failed. Verify whether the provided initiator CHAP is correct.	Either the provided CHAP key is invalid or the iSCSI initiator name is not unique for each backup or recovery host. Set the iSCSI initiator name uniquely for each backup/recovery host.
Failed to get an external data service IP address for iSCSI. Re-run the job after setting IP address on the Nutanix cluster: {Nutanix AHV clusterName}.	Set the external data service IP address for iSCSI on the Nutanix AHV cluster. More details See Prerequisites to configure Nutanix AHV cluster. Note: For Linux it falls back to use the NFS for backup/restore.
NetBackup version is not supported for one or more backup hosts. Use NetBackup version 9.1 or later on all Linux or Windows backup host to use the Automatic backup host option in the Nutanix protection plan.	This error occurs when the Automatic option is selected for backup hosts in the Nutanix protection plan. Upgrade backup host to latest NetBackup version.
For NetBackup media server load balancing, ensure that the backup hosts have either Red Hat Enterprise Linux, SUSE Linux Enterprise Server, or Microsoft Windows operating system.	This error occurs when the Automatic option is selected for backup hosts in the Nutanix protection plan. For Nutanix AHV, supported media servers are: Red Hat Enterprise Linux SUSE Linux Enterprise Server Microsoft Windows operating system
The existing version of NetBackup on the media server does not support the incremental backup schedule.	Upgrade NetBackup to the latest version on the backup host.
Unable to set resource limits for specific Nutanix clusters.	If the clusters for which the resource limit is set are deleted from the NetBackup environment, in some cases, the + Add option is disabled to set the resource limit. Recommended action Delete the resource limit for the deleted clusters and then set the resource limit for the rest of the clusters.
Snapshot jobs fail with error code 156 with the following job details: Critical bpbrm (pid=30139) from client 9c5dcb07-65d2 -4761-b861-9e517edcf5b6_ <Nutanix-cluster> abc.cbus.com FTL - Value 2 that specifies GUID is not supported for the nameuse	If a protection plan is created using Backup option > Select server or host to use for backups > Automatic and the selected storage unit is configured with media servers with both NetBackup 9.1 or previous versions. And when this protection plan is used to back up the AHV VMs or Intelligent VM group, the snapshot job might fail. Recommended action All the media servers, which are configured in the selected storage unit, must be upgraded to NetBackup 9.1. To avoid job failures as upgrades for other media servers are in progress, in the Protection > Customize Protection > Backup options option, manually select a specific media server or backup host as a server or host to use for backups instead of the default Automatic option. It is recommended to use already upgraded media server. Once upgrade of all media servers completes, use Protection > Restore Original Settings to go back to original settings.
Error 1 iscsiadm: Could not login to [iface: default, target: iqn.2010-06.com.nutanix: nbubackup -2d29da9d-f964- 4157-9595-f0319090bb01-tgt0, portal: xx.xx.xx.xx,3260] iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) iscsiadm: Could not log into all portals Error 2 iscsiadm: Could not execute operation on all records: encountered iSCSI database failure Error 3 iscsiadm: could not read session targetname: 5 iscsiadm: could not find session info for session28	These errors are seen in the successful job details tab of backup/restore jobs. These errors are the output of iscsiadm command execution. These errors are intermittent and may occur due to heavy load on the iSCSI network. NetBackup does a retry operation to fix these errors. Once the retry operation is successful, the backup/restore job is also successful. Recommended action No action is required on the NetBackup side. User can still troubleshoot the iscsiadm and ensure correct iSCSI installation/configuration to avoid such errors.
iscsid: Ignoring CHAP algorithm request for MD5 due to crypto lib configuration iscsid: Couldn't set CHAP algorithm list	See, In FIPS enabled environment, NetBackup backup/restore of Nutanix AHV VMs (Virtual Machines) using iSCSI fails
Error code: 4798 Use Prism Central server for this cluster option is not selected for AHV cluster.	Discovery job during backup may fail with the error for Nutanix Intelligent VM group. Look and fix the following possible causes for Intelligent VM group: Created with category filter as one of the filter queries AND One or more Nutanix clusters are updated after the intelligent VM group is created to use the Use Prism Central server for this cluster option unchecked AND Backup now operation is triggered on such IVMG.
Error message: Unable to find the Prism Central for AHV cluster, server = Server details	Backup job fails with the given error. Look and fix the following possible causes: In an Intelligent VM group consisting of one or more clusters from same Prism Central server and category as one of the filter, when IVM group protection is triggered, Prism Central server is deleted/not accessible. In an Intelligent VM group consisting of two or more clusters from different Prism Central servers and category as one of the filter, when an Intelligent VM group protection is triggered, one or more Prism Central servers are deleted/not accessible.
Error message: Protection plan subscription should fail with error. An invalid API request is encountered error message: backupHost: Backup host with a NetBackup version earlier than 10.4 is not supported for IntelligentVM group Category filter.	If a category filter is used in the Intelligent VM group, subscribing it to a protection plan may fail with the given error. Ensure that the Backup host mentioned in the protection plan must have NetBackup version 10.4 or later.
Backup job fails with error code 800. Error nbjm(pid=113200) NetBackup status: 800, EMM status :Use NetBackup media server version 10.4 or later to protect Nutanix Intelligent VM groups with category filters. . Error nbpem(pid=113293) backup of client MEDIA_SERVER exited with status 800 (resource request failed).	Description If a protection plan is created using Backup option > Select server or host to use for backups> Automatic and the selected storage unit is configured with media servers with earlier than NetBackup 10.4 versions. And when this protection plan is used to backup the Intelligent VM group with category attribute as filter, the backup job will fail. Recommended action: At least one of the media server, which is configured in the selected storage unit, must be upgraded to NetBackup v10.4 or later.
Backup job fails with following error messages: Error 1 Begin Application Resolver:Resolver Discovery Error 2 Error nbpem(pid=98395) Invalid URI. Error 3 Error nbpem (pid=98395) backup of client falcna12c3.abcus.com exited with status 4232 Invalid Discovery Query URI).	Description When the Intelligent VM group is subscribed with a protection plan that have a backup host version 10.3 or older, and the Intelligent VM group is modified with the category filter. Then, once the backup job runs, it fails with an error message. As the category filter is not known to the older versions of backup hosts. Recommended action: Upgrade the backup host to 10.4 or later by customizing the protection plan. More details See Customize protection settings for an AHV asset.