Reasons why Client side restores might not work in NetBackup

From World History Wiki
Jump to: navigation, search
World History Wiki is Brought to you by:
S.J.'s Adventures

Permissions issues

The 1st reason will typically appear as an error message saying something to the affect that permission is denied (at login, when initiating the restore, or any time in between), or the restore will immediately fail with a number of different status codes and/or messages. This is because the account you are logged in as isn’t configured in the appropriate local system accounts (i.e. Local Admin). Even if you can login, you may have issues with limited access to some components within NetBackup due to this issue, and may not be allowed to restore because of limited permissions.

  1. Make sure you are using an account with Admin privileges.
  2. Contact the security team, and have them correct the permissions problem by adding you or the appropriate groups on the local system(s) (such as Local Admin) that will give you the access you need to restore the files in question.


These usually show up us as a long delay in the restore process, with times when the “Backup, Archive, and Restore” console will be non-responsive, eventually followed by a timeout or error message. The hostname being reported to NetBackup is not recognize this name as a valid client name. This may be due to it being reported in UPPERCASE, or as a Fully Qualified Domain Name (FQDN). In clustered environments the physical server name will not match the virtual client name, which requires that the Altnames Configuration for NetBackup is done properly.

WARNING: having too complex of an "Altnames" configuration can also cause slowdowns as it may take many minutes to complete the comparison.

Note: You can check the computer properties on client, to see how the computer name is entered, (upper or lower case), or get/request the output from the ""C:\Program Files\VERITAS\NetBackup\bin\bpclntcmd.exe" -self"

  1. To see how it’s being reported to NetBackup, check the “bpdbm” log file to see what the system is connecting as.
    It may also shows up in the activity monitor and you can use the name that appears there as well.
  2. Use this command (or a similar one):
    “tail -f /usr/openv/netbackup/logs/bpdbm/log.MMDDYY | grep -i [client]”
  3. This will give you output similar to the following (it may take up to 20 minutes for the log to show this information):
    : 16:15:31.277 [5845] <2> hosts_equal: Comparing hosts <> and <dfs11>
    : 16:15:31.278 [5845] <2> hosts_equal: host1 dfs11 addr (0xac154165)
    : 16:15:31.278 [5845] <2> hosts_equal: host2 dfs11 dfs11 addr (0xac154165)
    : 16:15:31.278 [5845] <2> hosts_equal: hostnames DO compare (2)
    : 16:15:31.278 [5845] <2> configured_client_name: matches configured dfs11
  4. Configure NetBackup to see the reported name as a client by Doing a quick backup of the physical node using the name found in the bpdbm log (or activity monitor) as the client using a “Test” policy to make sure the name stays configured as a known client until it is retired.
  5. Run a manual backup on this policy using the client name you just added, making sure it is kept for as long as it will be needed.
  6. if what you found was an UPPERCASE FQDN you also want to add it to the Altnames Configuration for NetBackup in UPPERCASE.

Communication issues

Due to the complex nature of some Network designs, there are occasions when a client cannot reach the NetBackup Master server to get a list of what backups it can restore from. This is typically a firewall issue with not allowing communication between the client and the Master server; however it can also sometimes be due to an improper configuration within the NetBackup client software. Such as using "REQUIRED_INTERFACE" setting for a network interface that will not rote to the Master Server, or having an improper client name in the configuration.

These issues should be resolved with a well designed Backup Network Example Configuration.

OST Related

Some common OST issues may be found here:

Sometimes you may need to use the bprestore command with '-disk_media_server' option to force which media server to use (one that the client communicate with).

For Oracle RMAN backups, use the send parameter NB_ORA_DISK_MEDIA_SERVER to specify the desired media server.

Back to NetBackup