About restoring data in a cluster
When you restore files to the shared disk drives, restore those files to the virtual server name. When you restore individual database files, restore those files to the virtual server name that corresponds to the client where the database application is installed.
Note:
Since a computer can have multiple virtual names in a cluster environment, files can be backed up in the context of more than one client name. If you carefully plan your backup policies, you can avoid this problem. However, it may be necessary to browse more than one client name to locate a backup image. And you may need to perform more than one restore to restore all of the files that you need.
The Backup, Archive, and Restore console operates in the context of that client's name. You must perform a redirected restore to restore the files on the shared disk that were backed up with the virtual server name. NetBackup allows a redirected restore operation only if the necessary configuration is performed on the NetBackup primary server. See the information on how to allow redirected restores in the NetBackup Administrator's Guide, Volume I.
There may be other situations that require the appropriate altnames directory entries to be created on the primary server. While NetBackup tries to restore files from the client, the operation may fail with this error message:
131 client is not validated to use this server
If you see this message, you must set up the altnames directory to allow the operation to succeed. For example, the required network interface parameter may be set to a valid network name for the client. But this name may not match the NetBackup parameter for that client. This situation often happens for NetBackup clients in a cluster. Alternatively, you can perform a server-directed restore and avoid the need to set up the altnames directory.
See Example: Performing a user-directed restore in a NetBackup cluster.