About server-directed restores
A NetBackup user with the Administrator role or similar permissions can perform restores from the NetBackup primary server. This type of restore is available in the web UI for the following policy types:
BigData | Hypervisor - Nutanix | NDMP |
Cloud-Object-Store | Lotus-Notes | Nutanix-AHV |
Datastore | Standard | |
FlashBackup | MSDP-Object-Store | Universal-Share |
FlashBackup-Windows | NAS-Data-Protection | VMware (agent-based recovery) |
Hyper-V | NBU-Catalog |
BigData | Hyper-V | NBU-Catalog |
Cloud-Object-Store | Hypervisor - Nutanix | NDMP |
Datastore | MS-Windows | Standard |
FlashBackup | MSDP-Object-Store | Universal-Share |
FlashBackup-Windows | NAS-Data-Protection | VMware (agent-based recovery) |
Restore types in addition to "Normal backups" are available for certain policy types.
Restore type | Supported policy typed |
|---|---|
Archived backups | MS-Windows, Standard |
Optimized backups | MS-Windows |
Point-in-time rollback | MS-Windows, NAS-Data-Protection, Standard |
Raw partition backups | FlashBackup, FlashBackup-Windows, Standard |
True image backups | MS-Windows, NAS-Data-Protection, NBU-Catalog, Standard |
Virtual disk restore | VMware |
Virtual machine backups | Hyper-V, Hypervisor-Nutanix, Nutanix-AHV |
By default, NetBackup clients are configured to allow NetBackup administrators on a primary server to direct restores to any client.
To prevent server-directed restores for a client do the following:
On Windows clients:
Open the interface.
Select , then clear the check box.
On UNIX clients:
Add DISALLOW_SERVER_FILE_WRITES to the following file on the client:
/usr/openv/netbackup/bp.conf
Note:
On UNIX systems, the redirected restores can incorrectly set UIDs or GIDs that are too long. The UIDs and GIDs of files that are restored from one platform to another may be represented with more bits on the source system than on the destination system. If the UID or the GID name in question is not common to both systems, the original UID or GID may be invalid on the destination system. In this case, the UID or GID is replaced with the UID or GID of the user that performs the restore.
On UNIX, no progress log is produced if the bp.conf file of the requesting server does not contain an entry for the restoring server. Without that entry, the restoring server has no access to write the log files to the requesting server. (A progress log is an entry in the Task Progress tab of the Backup, Archive, and Restore client interface.)
Consider the following solutions:
To produce a progress log, add the requesting server to the server list.
Log on to the requesting server. In the NetBackup web UI, open the host properties for the primary server. Then click . Add the restoring server to the server list.
Log on to the restoring server. Go to the Activity monitor to determine the success of the restore operation.
To restore a UNIX backup that contains soft and hard links, run the Backup, Archive, and Restore client interface from a UNIX machine.