Managing NetBackup
215
5
server or client bilbo.dvlp.null.com
In this example, the peername is bilbo.dvlp.null.com.
2. After determining the peername, create the file
install_path
\NetBackup\db\altnames\
peername
on the NetBackup master server.
In our example, the file is:
install_path
\NetBackup\db\altnames\bilbo.dvlp.null.com
3. Edit the peername file to include the desired client names.
For example, if you leave the file
install_path
\NetBackup\db\altnames\bilbo.dvlp.null.com
empty, clients alf, cheech, and chong can all access the backups
corresponding to their NetBackup client name setting. See “Allowing a
Single Client to Perform Alternate-Client Restores” on page 211.
If you add the names cheech and chong to the file, you give these two
clients access to NetBackup file restores, but exclude alf. See “Allowing
Alternate-Client Restores of Specific Client’s Files” on page 212.
Note that this example requires no changes on the clients.
Example 3
If the files cannot be restored by using the method in Example 2, perform the
following steps:
1. On the master server, set the NetBackup configuration option,
VERBOSE
.
2. Create the activity log directory for the NetBackup Request Manager service
in:
install_path
\NetBackup\logs\bprd
3. On the master server, stop and then restart the NetBackup Request Manager
service. This ensures that this service is running in verbose mode and logs
information regarding client requests.
4. On restore-client, attempt the file restore.
5. On the master server, identify the peername connection used by
restore-client.
NetBackup 3.2 System Administrator's Guide for Windows NT
NetBackup 3.2 System Administrator's Guide for Windows NT