Server-directed restores

By default, NetBackup clients are configured to allow NetBackup administrators on a master server to direct restores to any client.

To prevent server-directed restores, configure the client accordingly as follows:

Windows clients

Open the Backup, Archive, and Restore interface on the client.

Select File > NetBackup Client Properties > General, then clear the Allow server-directed restores checkbox.

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.

Consider the following solutions:

To produce a progress log, add the requesting server to the server list.

To do so, log into the requesting server. In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers > Double-click on the master server > Servers. Add the restoring server to the server list.
Log on to the restoring server. Check 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. Only the Java version of the client interface contains the Rename hard links and Rename soft links restore options. Windows users can install the Windows display console to access the Java version of the Backup, Archive, and Restore interface from a Windows computer.