NetBackup status code: 2824

Message: Cloud policy restore error.

Explanation: Unable to restore the data that was backed up using the cloud policy. Multiple issues can cause this error.

Recommended Action: The following tables list the nbcs level error messages which are displayed in Job Details on the Activity Monitor and the action you need to take to fix the issue.

Table: Restore failed as the pre-requisites for restore operation were not satisfied for the asset

Message	Recommended action
Disk `Resource group <RG>` does not exist.	The resource group in the disk destination path does not exist. Select the resource group which is present in the cloud.
Disk `subscription ID <>` must be the same as the host subscription ID.	Ensure that the given subscription ID as part of the disk destination path, match with subscription ID from VM destination path.
VM with `name <>` already exists.	Retry the operation after changing the display name.
VM `display name <>` is unsupported.	Ensure that the VM name is compliant with the cloud provider's naming convention.
`DestinationPath <>:` is not configured for selected config.	The provided subscription is not configured in the given destination configuration. Provide a subscription that exists in the configured cloud provider.
`Subnet <id>` does not exist.	The destination network that is selected does not exist in the selected subscription. Select a network which is present on the cloud. Ensure that discovery has run after the creation of a new subnet.
Destination `Resource group <RG>` does not exist.	The resource group in the VM destination path does not exist. Select a resource group which is present on the cloud.
`Region <>` is not configured.	Ensure that the selected region is part of the destination configuration.
Failed to find `sqlpackage` client utility on a given host.	Install the required `sqlpackage` utility on the media server.
Configure and mount Universal Share Accelerator failed.	For VM-based deployment if an external disk is attached to the NetBackup Snapshot Manager host and mounted as `/datamover_storage` then ensure at least 500GB of disk space is available. For VM-based deployment, if no external disk is attached to the NetBackup Snapshot Manager host or if it is not mounted as `/datamover_storage`: then ensure that the root partition has at least 500GB of disk space available.
Failed to get export path and vpfs server.	In Cloud Scale deployment ensure that all MSDP pods have at least 500GB of disk space available. In VM-based deployment ensure that the storage server should have at least 500GB of disk space available at the configured storage path.
The following are only applicable for Azure Stack restore from backup. Restore failed due to the staging location not correctly specified. Verify that the `/cloudpoint/azurestack.conf` has a correct entry for the staging location.
Failed to get a staging location for the `subscription: {id}`.	Ensure that staging location details (for example: storage account and container) are added in the file `/cloudpoint/azurestack.conf` for the selected target subscription.
The `storage account:<account name>,` does not exist.	Ensure that the storage account is present in the target subscription.
The `container: {container name},` does not exist in the `storage account: {account name}`.	Ensure that the storage account container is present in the storage account.

Table: Failed to perform a recovery operation for the asset

Message	Recommended action
Failed to create an asset `<disk/host>`.	One of the probable reasons can be that the quota limit has exceeded. Check if the required resource limit is available.
`Asset <>` not found.	Ensure that the asset is present in the cloud and it is discovered.

Table: Restore failed due to SSL certificate issues or connectivity issues between Snapshot Manager and Azure or Azure Stack

Message	Recommended action
Unable to retrieve the certificate CRL. If you have configured the `ECA_CRL_PATH`, ensure that valid CRLs are present at the location. Check if the CRL URL is accessible from the Snapshot Manager.	Copy the latest CRL into the `ECA_CRL_PATH` path or ensure the CRL distribution point URL, from the respective host certificate, is accessible from the Snapshot Manager.
The Azure or Azure Stack servers' certificate is revoked. Ensure that the certificates are not revoked by certificate authority.	The certificate of the server has been revoked. Contact your security administrator for assistance.
The certificate revocation list (CRL) is expired. Ensure that the `ECA_CRL_PATH` is updated with the latest CRL.	Ensure that the latest CRL's are uploaded at the `ECA_CRL_PATH` path. You can update the NetBackup CRL cache manually by using the following command on Snapshot Manager: docker exec -i flexsnap-certauth bash -c '/usr/openv/pdde/pdopensource /nbcertcmdtool/nbcertcmdtool -atLibPath /usr/openv/pdde/pdopensource/nbcertcmdtool -updateCRLCache'
The certificate revocation list (CRL) is not yet valid.	Review your Snapshot Manager's system time or provide a valid CRL.
The date of the last update of the certificate revocation list (CRL) is not in a valid format.	Check the CRL using the openssl command or contact your Security Administrator.
The date of the next update of the certificate revocation list (CRL) is not in a valid format.	Check the CRL using the openssl command or contact your Security Administrator.
The Azure or Azure Stack server certificate is expired. Ensure that the server has a valid certificate.	Review the certificate and ensure the validity of it by checking the certificate to make sure that the end date is valid. Check if the Snapshot Manager's clock is in sync with the specified server. Correct the time on the host, if necessary, and rerun the operation. If the problem continues, save all of the error log information and contact Cohesity Technical Support.
The Azure or Azure stack servers certificate is not yet valid.	Check if the Snapshot Manager's clock is in sync with the specified server. Correct the time on the host, if necessary, and rerun the operation. If the problem continues, save all of the error log information and contact Cohesity Technical Support.
Unable to find the public root and intermediate certificates of the Azure Stack server.	Ensure that the certificate file is configured correctly at the `ECA_TRUST_STORE_PATH` located in the `bp.conf` file on the Snapshot Manager. Rerun the operation. If the problem persists, save all of the error log information and contact Cohesity Technical Support.
Failed to load the Certificate Revocation List (CRL) from the CRL cache. Ensure that the valid CRL file is configured on the Snapshot Manager for Azure or Azure Stack by `ECA_CRL_PATH`.	Ensure that the valid CRL file is configured on the Snapshot Manager for Azure or Azure Stack by the `ECA_CRL_PATH`.
Failed to connect to the Azure or Azure Stack server. Ensure network connectivity between Snapshot Manager and the Azure or Azure Stack server.	Ensure network connectivity between the Snapshot Manager and the Azure or Azure Stack server.
Cannot use the specified SSL cipher for Azure or Azure Stack server.	Contact Cohesity Technical Support.
Operation failed with cURL error:	Rerun the operation. If the problem persists, save all of the error log information and contact Cohesity Technical Support.

Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.

NetBackup status code: 2824

Feedback

Feedback