Search <book_title>...

Product Documentation

Last Published: 2024-08-30

Product(s): Resiliency Platform (10.3)

Troubleshooting: NetBackup issues

The following table lists some of the issues that you may come across while restoring backup images using NetBackup.

Table: Troubleshooting NetBackup

Description	Solution
Recover operation fails at the Restore virtual machine image step.	In the Recent Activities panel, check the details of the failed step. Details such as Job ID and NetBackup primary server name are displayed. These can be used to retrieve the failure reason using bperror command on the NetBackup primary server.
After completion of the Recover operation, the NICs attached to the virtual machines are not displayed.	Ensure that port group or VLAN mapping is complete at the production data center. If multiple network interface cards (NICs) are assigned to a virtual machine, then you need to apply IP customization to all the NICs.
Recover operation fails	Check the log file on the Infrastructure Management Server (IMS) for errors. Log file location: /var/opt/VRTSsfmh/logs/mhrun.log
Recover operation fails. The activities monitor on NetBackup primary server shows the following error. NetBackup VMware policy restore error (2820)	When you add a VMware access host or a recovery host to the NetBackup primary server, ensure that you add only the NetBackup client. Else the recover operation performed using the Resiliency Platform console may fail.
Recover operation is paused for a prolonged period at the Restore subtask	Do the following: Go to Settings > Infrastructure, in the details view of the recovery data center > Copy Manager. Check the connectivity of NetBackup primary server. If it is disconnected, refresh the NetBackup primary server. Ensure that there are no time sync issues between Resiliency Platform and NetBackup primary server. Check the restore status in the NetBackup primary server using the Job ID provided in the details view in Recent Activities panel. If the Job is still running on the NetBackup console, then wait for the task to complete. If the job is completed on the NetBackup console, abort the recover operation using Resiliency Platform web console. Retry the operation.
Recover operation fails at the Restore virtual machine image step with error: 'NetBackup API failed with response: {"response":null}'	As the NetBackup Primary server times out while responding to the Resiliency Platform's request to restore the virtual machine, even then the restore job is initiated successfully. Check the status of running restore job in the Activities page in the NetBackup console for the virtual machines which are members of the current resiliency group being restored.
After adding the NetBackup primary server, if you immediately perform the 'Configuring the assets for remote recovery using the Copy service objective' operation, then the operation may fail.	Discovery of NetBackup primary server by Resiliency Platform takes some time. If there are no configuration issues, then you may perform the 'Configuring the assets for remote recovery using the Copy service objective' operation after some time.
Deleted NetBackup policies	Resiliency Platform does not validate deactivated NetBackup policies but displays RPO risks if the assets are protected.
Reissuing NetBackup certificate	Consider the following scenario: You have integrated Veritas Resiliency Platform with NetBackup 8.1. For some reason if you have had to redeploy the IMS and you have replicated the previous asset configuration, then you need to reissue the certificate on the IMS that is associated with NetBackup primary server. To reissue the certificate, do the following: Run the following Klish commands on the IMS on which NetBackup primary server was added: utilities > troubleshoot run-tools manage-nbu-primary-certificates --add --primary <primary_server_hostname> --token <copied_token> See Klish menu options for IMS. On the NetBackup primary server console, under Security Management > Certificate Management, click Generate reissue token to obtain the token.
The NetBackup primary server goes into disconnected state after upgrading the Resiliency Manager - IMS server to 10.3.	If NetBackup primary server was added in previous version of Resiliency Platform using the registration URL and Resiliency Platform is upgraded to10.3, the primary server state displays as Reconfiguration required. You must edit the NetBackup primary server to bring it back to the connected state. See Editing the NetBackup primary server.
If NetBackup primary servers lower than version 8.1.2 are added in Resiliency Platform, and if these primary servers are upgraded to version 8.1.2, the primary servers are displayed as Disconnected in Resiliency Platform.	Remove the primary server from the Resiliency Platform configuration and re-add it to resolve the issue. See Adding NetBackup primary server.
Restore task may fail with error "The user does not have permission to perform the requested operation."	Contact NetBackup support.
Restore task fails for some virtual machines and succeed for other virtual machines in a resiliency group	List of solution: Check the Restore Job Id by double clicking on the failed task in the Activities page. Login into Netbackup console and check the status or reason of job failure. After correcting the problem that caused the failure, you can issue the same recover operation in Resiliency Platform. This time, you can choose not to recover the previously restored virtual machines by unchecking them in the Recover wizard. Once this operation completes, the resiliency group will be in Partial state as the unchecked virtual machines will not be started. To start all the virtual machines, you can start the resiliency group and select the option Refresh storage, network, compute and customizations. This will start all the virtual machines in the resiliency group.
Recover operation fails at the Restore virtual machine image step.	Perform the following steps: Login into the NetBackup console and navigate to Activities panel. Check the status of the failed restore job. You may correct the errors if any and retry the same operation to continue restoring the resiliency group. Or else, you may start the resiliency group in the same data center where it was online before the operation failed. In this case, you need to select the option presented in the start operation, to refresh the storage, network, compute and customizations. The start operation will register the virtual machines from their copies on the datastores instead of restoring them from the backup.
Add NetBackup primary server or cloud recovery server fails with SSL/TLS verification error.	If the error or risk description indicates an SSL/TLS verification error. Refer the Secure communication issues section See Troubleshooting: Secure communication issues.
Edit or refresh cloud recovery server fails with SSL/TLS verification error.	If the error or risk description indicates error as SSL/TLS handshake has failed. Install valid CA certificates of {0} in theResiliency Platform. Refer the Secure communication issues section See Troubleshooting: Secure communication issues.
Start Virtual Business Service task may fail with error "A specified parameter was not correct: path".	To resolve this, just restore the resiliency group again. You may select only the virtual machines for recovery which had failed earlier. This can happen if the backup image being restored has a different vmx path than the path recorded by Resiliency Platform at the time of creating resiliency group. One possible cause for this discrepancy is that the backup image has a timestamp older than the resiliency group creation time.
Number of backup images in Resiliency Group details page or in the Recovery wizard is less than expected.	In the Recent Activities panel, check the details of the failed step. Details such as Job ID and NetBackup primary server name are displayed. These can be used to retrieve the failure reason using bperror command on the NetBackup primary server. The Resiliency Platform keeps a certain number of records of backup images for a resiliency group. The number of images depends on the RPO defined for the service objective of the resiliency group. It is typically 10 times the RPO and the multiplier can be changed using a configuration tunable. If some backup images discovered by older versions of theResiliency Platform (version 3.5 or older), these backup images are not be available after upgrading to version 10.0 or later. If these images are required for operation, you must edit the resiliency group which will re-fetch the images again.

Table: Troubleshooting NetBackup recover to cloud

Description	Solution
Cloud Recovery Server is disconnected	In such a situation, a risk is raised on the resiliency group if one is configured. Also, the Cloud Recovery Server (CRS) will show as disconnected on the Copy Manager page of the cloud data center. Ensure that the CRS running and you can connect to it from the Resiliency Manager. If the error or risk description indicates an SSL/TLS verification error. Refer the Secure communication issues See Troubleshooting: Secure communication issues.
Rehearsal or recover operation fails at the Restore virtual machine image step	The issue can be caused due to the following reasons: The recover operation has been interrupted. Attempt a retry of the operation. Network issues. Ensure connectivity between the CRS and Resiliency Manager and retry the operation. The CRS is already processing maximum requests that it can handle. You must wait for the active recover operations on the CRS to complete and retry the operation. Maximum simultaneous AMI import limit for the AWS account has been exceeded. AWS imposes certain limits on maximum simultaneous AMI import operations per account per region. You must either extend the limit by talking to the AWS customer support, or wait for any active AMI import operations to complete and then retry the operation. . Another way is to limit the number of workloads in the resiliency group as per the AMI import API limitation.
Rehearsal or recover operation fails after the Restore virtual machine image step on the cloud data center.	The issue occurs because of transient failures to provision network interfaces or to register and start the provisioned cloud instances. To attempt recovery again, invoke the Start resiliency group operation and ensure that you select the option to Refresh storage, network, compute and customizations. If the issue persists, retry the recover operation to delete any registered cloud instances on the target data center and recreate them.
Deep start on cloud data center failed at 'Register VM task' with error 'Internal error. No image found to create the instance'.	The Deep start fails because there is no AMI available for creation of instance. Execute the Recover operation and select the cloud data center to recreate or restore the cloud instance back to cloud data center.