No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The Restoration Task Implemented on a Different Client Fails After Files on the NetBackup Client Are Encrypted and Error Message "Standard policy restore error (status 2800)" Is Displayed

Publication Date:  2015-07-28 Views:  38 Downloads:  0
Issue Description
After encryption is enabled on a NetBackup client, file backup is implemented for client A that runs the Linux system. Then, a restoration task is implemented on client B that runs the Linux system using the data backed up on client A. The restoration task fails.



The detailed information about the failed restoration task in the Activity Monitor is as follows:

02/04/2012 00:44:38 - begin Restore
02/04/2012 00:44:39 - restoring from image linux-35om_1328334104
02/04/2012 00:44:39 - Info bpbrm (pid=4090) linux is the host to restore data
02/04/2012 00:44:39 - Info bpbrm (pid=4090) reading file list from client
02/04/2012 00:44:40 - connecting
02/04/2012 00:44:40 - Info bpbrm (pid=4090) starting bptm
02/04/2012 00:44:40 - Warning bpbrm (pid=4090) expected start message from linux; read: EXIT STATUS 11: system call failed
02/04/2012 00:44:40 - Error bpbrm (pid=4090) client linux didn't start
02/04/2012 00:44:40 - Info tar (pid=0) done. status: 49: client did not start
02/04/2012 00:44:40 - Error bpbrm (pid=4090) client restore EXIT STATUS 49: client did not start

02/04/2012 00:58:40 - restored from image linux-35om_1328334104; restore time: 0:14:01
02/04/2012 00:58:40 - Warning bprd (pid=4080) Restore must be resumed prior to first image
expiration on Sat 18 Feb 2012 12:41:44 AM EST
02/04/2012 00:58:40 - end Restore; elapsed time 0:14:02
Standard policy restore error  (2800)
Handling Process
Cause 1: Check whether the NetBackup service is enabled on client B. If the NetBackup service is not enabled, enable it.

Cause 2: Check the encrypted files on client B.


1.  In /usr/openv/netbackup/logs/ on the master server, create the bpbrm directory. In /usr/openv/netbackup/logs/ on client B, create the bpfilter directory. Set the directory properties to 777.
2.  Perform the restoration.

3.  Check the collected bpbrm and bpfilter process logs. For example, the process logs are as follows:


The bpbrm process log is as follows:

00:44:40.029 [4090] <2> bpbrm main: received bpcd success message
00:44:40.056 [4090] <8> bpbrm main: expected start message from linux; read: EXIT STATUS 11: system call failed

00:44:40.056 [4090] <2> set_job_details: Tfile (22): LOG 1328334280 8 bpbrm 4090 expected start message from linux;
read: EXIT STATUS 11: system call failed
00:44:40.057 [4090] <4> db_error_add_to_file: expected start message from linux; read: EXIT STATUS 11: system call failed
00:44:40.057 [4090] <2> bpbrm readline: EOF detected on NAME socket
00:44:40.057 [4090] <16> bpbrm main: client linux didn't start
00:44:40.057 [4090] <2> set_job_details: Tfile (22): LOG 1328334280 16 bpbrm 4090 client linux didn't start
00:44:40.057 [4090] <4> db_error_add_to_file: client linux didn't start
00:44:40.057 [4090] <2> bpbrm kill_child_process: start
00:44:40.057 [4090] <2> set_job_details: Tfile (22): LOG 1328334280 4 tar 0 done. status: 49: client did not start
00:44:40.058 [4090] <16> bpbrm Exit: client restore EXIT STATUS 49: client did not start
00:44:40.058 [4090] <2> set_job_details: Tfile (22): LOG 1328334280 16 bpbrm 4090 client restore EXIT STATUS 49: client did not start
00:44:40.058 [4090] <4> db_error_add_to_file: client restore EXIT STATUS 49: client did not star


The task and bpbrm logs show that the tar process on client B is not enabled. As a result, the restoration task fails.

The bpfilter process log (from client) is as follows:


00:44:40.051 [2335] <2> bpfilter: 0 = close(5) errno = 9 mode = 0x0000c1ff
00:44:40.051 [2335] <4> bpfilter: INITIATING bpfilter
00:44:40.051 [2335] <4> bpfilter: argv[0] = bpfilter
...
00:44:40.053 [2335] <4> filter: invoking CRYPT filter for decryption
00:44:40.053 [2335] <4> crypt_filter: building tar command ...
00:44:40.053 [2335] <4> crypt_filter: cargv[0] = /usr/openv/netbackup/bin/tar
00:44:40.053 [2335] <4> crypt_filter: cargv[1] = tar
...
00:44:40.054 [2335] <2> log_cipher_name: cipher type = 0, cipher name = AES-128-CFB
00:44:40.054 [2335] <4> read_keys: using default key file pass phrase
00:44:40.054 [2335] <16> read_keys: no key file
00:44:40.054 [2335] <2> filter_exit: EXIT STATUS 11: system call failed


The bpfilter log shows that the system reads the encryption key file before enabling the tar process. The encryption key file does not exist on client B. As a result, the tar process fails to be enabled. After the file encryption is enabled on the source client, the target client requires the corresponding encryption key file when restoration is performed on a different client.

4.  Run the following command to generate an encryption key file on the target client (client B).


linux:/usr/openv/netbackup/bin # ./bpkeyutil
Enter new NetBackup pass phrase: ******
Re-enter new NetBackup pass phrase: ******


CAUTION:
Ensure that the entered key is consistent with that used on the source client (client A).


Perform the restoration again.
Root Cause
1.  The NetBackup service is not enabled on client B.

2.  Encrypted files do not exist on client B or encrypted files do not match.

END