NetBackup status code: 2850

Message: Restore error

Explanation: An error caused the restore to fail.

Recommended Action: This status code can appear for multiple workloads. Please review the following information for your particular workload.

For general troubleshooting, try the following possible solutions in the order presented:

Ensure that the client-server list contains entries for the master server and any media servers that can be used during a backup or restore.
Examine the status or the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server.
Check ownership and permission on directories where files are restored.
Correct the problems that you find and retry the restore.

In the case of Hadoop and HBase:

This error is encountered when an import of an image is used to create a catalog entry and then afterwards a restore is triggered. To troubleshoot this error, refer to the following procedure:

To troubleshoot the restore failure:

Create a rename file with the ALT_APPLICATION_SERVER as the application server name. Provide the primary name node only (instead of alternate name node). Ensure that the credentials for primary name node are already present.
Perform the restore using the bprestore command.

In the case of Azure Stack and OpenStack:

If the error occurs for an AIR restore scenario, restore the catalog before you restore the AIR images.

In the case of Hadoop with Kerberos:

This issue arises if the HDFS owner does not set ownership for files and directories or if there are issues with Kerberos configuration. Before restoring, ensure the following:
- Ensure that the HDFS owner user is used for Kerberos backup.
- Ensure that with the current Kerberos user, it is possible to set the owners/ACLS manually using HDFS commands, such as chown and setfacl.

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