Forum Discussion

aor_manuel's avatar
aor_manuel
Level 4
9 years ago

Standard Policy restore error 2800

Hi,

I am having an error when i try to restore information in another server, my platform is like this:

         Master Server --> Windows Server 2012 R2 Std

         Linux Server 1 --> Media Server

         Linux Server 2 --> Media Server

I have done this tests:

1. I have runned a backup job on the Linux Server 1 --> ok

2. I have restored this information on the same Linux Server 1 --> ok

3. When i try to restore this information on the other server (Linux Server 2) i am getting this error --> Standard Policy restore error 2800

 

This is the detailed Job status:

05/20/2016 11:34:15 - begin Restore
05/20/2016 11:35:03 - Info bprd (pid=10732) Found (21) files in (1) images for Restore Job ID 738.xxx
05/20/2016 11:35:12 - restoring from image Server-Test
05/20/2016 11:39:01 - Info bprd (pid=10732) Searched (21) files of (21) files for Restore Job ID 738.xxx
05/20/2016 11:39:01 - Info bprd (pid=10732) Restoring from copy 1 of image created 05/20/16 09:53:35 from policy Server-Test
05/20/2016 11:39:37 - Error bpbrm (pid=27428) bpcd on Server-Test2 exited with status 48: client hostname could not be found
05/20/2016 11:39:37 - Info tar (pid=0) done. status: 48: client hostname could not be found
05/20/2016 11:39:37 - Error bpbrm (pid=27428) client restore EXIT STATUS 48: client hostname could not be found
05/20/2016 11:39:39 - restored from image Server-Test; restore time: 0:04:27
05/20/2016 11:39:44 - Warning bprd (pid=10732) Restore must be resumed prior to first image expiration on 20/06/2016 9:53:35 a. m.
05/20/2016 11:39:49 - end Restore; elapsed time 0:05:34
Standard policy restore error  (2800)

 

Anyone could help me?

 

Thanks a lot.

 

7.7
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • sdo's avatar
    sdo
    Moderator
    9 years ago

    The client is unable to resolve its own name.

    $ bperror -S 48 -r
client hostname could not be found
The system function gethostbyname() failed to find the client's host name.

Verify that the client name is correct in the following:
* The NetBackup policy configuration on the master server.
* The General tab in the following dialog boxes: NetBackup Client Properties and Specify NetBackup Machines and Policy Type (on Microsoft Wi
ndows non-target clients). To display these dialog boxes, start the Backup, Archive, and Restore interface on the client. For the General ta
b, click NetBackup Client Properties on the File menu; click Specify NetBackup Machines and Policy Type on the File menu.
* The bp.conf file on UNIX, Linux, and Macintosh clients.
* On clients and servers, verify that the name service is set up to resolve the NetBackup client names correctly.
On UNIX clients, verify that the client's host name is in the /etc/hosts file or the YP hosts file or NIS maps.
Click here to view technical notes and other information in the Symantec Knowledge Base about this status code.

    You need to add a hosts file entry for the client on the client itself, or setup DNS or NIS.

    Also check the clients own hostname.

    # hostname
# cat /etc/hosts
  • sdo's avatar
    sdo
    Moderator
    9 years ago

    Probably best to add hosts file entries for both client and master/media servers - to all of client and master/media servers.

  • sdo's avatar
    sdo
    Moderator
    9 years ago

    If you don't have a No.Restrictions file in place, then you may need to setup some altnames entries so that both test clients can each browse and restore from each/one another's backups:

    On the master server do:

    # cd /usr/openv/netbackup/db

# mkdir ALTNAMES

# cd ALTNAMES

# echo Server-Test>Server-Test

# echo Server-Test2>>Server-Test

# echo Server-Test2>Server-Test2

# echo Server-Test>>Server-Test2

    .

    My advice is... get out of the habit of using mixed case server and client names... because you'll only get yourself in a pickle.  Choose either ALL UPPERCASE, or all lowercase.  BTW, most backups admins will use all lowercase.

  • Marianne's avatar
    Marianne
    Level 6
    9 years ago
    So, Linux Server 1 is a media server that has backed up itself, and Linux Server 2 is also a media server that has backed up itself, right? When you restore Linux Server 1 data to Linux Server 2, the master server sends the restore instruction to Linux Server 1 to restore data to Linux Server 2. Linux Server 2 is now a client of Linux Server 1. As others said - add hosts entries on both Linux servers for one another. Also add SERVER entries for one another in bp.conf.