Error run into while backing up AHV virtual machines — NetBackup 9.1 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

Error run into while backing up AHV virtual machines — NetBackup 9.1 | Cohesity Documentation

NetBackup™ Web UI Nutanix AHV Administrator's Guide

Error run into while backing up AHV virtual machines

The following table describes the problem 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 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 Microsoft iSCSI Initiator Service on backup host. Note: This is displayed as an error only for windows OS. For Linux, this error is displayed in form of a warning and it falls back to use the NFS for backup/restore. Ensure that the backup host is added in `Filesystem Whitelists` option in Nutanix UI for backups to work via NFS transport. For Linux to use iSCSI: Install / Enable iSCSI Initiator package on backup host and re-run the job.
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/recovery host. Please set iSCSI initiator name unique 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 Configure Nutanix AHV cluster. Note: For Linux it will fall back to use the NFS for backup/restore.
Backup hosts that have Linux or Windows OS with existing NetBackup version are not supported for media server load-balancing. Upgrade backup host to the latest version.	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 server are: Red Hat Enterprise Linux SUSE Linux Enterprise Server Microsoft Windows operating system
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 limit for specific Nutanix clusters.	If the clusters for which the resource limit is set are deleted from NetBackup environment, in some cases, + Add option is disabled to set the resource limit. Recommended Action Delete the resource limit for deleted clusters and then set the resource limit for 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> vxindia.veritas.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 prior 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 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 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 retry operation is successful, backup/restore job is also successful. Recommended action No action is required on NetBackup side. User can still troubleshoot the iscsiadm and ensure correct iSCSI installation/configuration to avoid such errors.

Feedback

Was this page helpful?

Feedback

Was this page helpful?