cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Hi,

i've problem with BPCD_WHITELIST_PATH on master server Netbackup 8.2 with this error:

 

May 22, 2020 11:42:51 AM - Warning bptm (pid=148157) failure logging message to client nbmasterna-01 in log /usr/openv/NBU_Test_Restore/recover_logs/recover_log_SILK24:  file open failed (12)
May 22, 2020 11:42:51 AM - begin reading
May 22, 2020 11:42:52 AM - Info bptm (pid=148157) waited for empty buffer 0 times, delayed 0 times
May 22, 2020 11:42:52 AM - end reading; read time: 0:00:01
May 22, 2020 11:42:52 AM - Info bptm (pid=148157) completed reading backup image
May 22, 2020 11:42:52 AM - Info bptm (pid=148157) EXITING with status 0 <----------
May 22, 2020 11:42:52 AM - Info nbapplna (pid=148157) StorageServer=PureDisk:nbapplna; Report=PDDO Stats for (nbapplna): read: 8083 KB, CR received: 16548 KB, CR received over FC: 0 KB, dedup: 0.0%
May 22, 2020 11:42:52 AM - Error bpbrm (pid=147907) cannot open progress file /usr/openv/NBU_Test_Restore/recover_logs/recover_log_SILK24 on nbmasterna-01
May 22, 2020 11:42:52 AM - Error bpbrm (pid=147907) client open errno = 6000
May 22, 2020 11:42:52 AM - Error bpbrm (pid=147907) Access to /usr/openv/NBU_Test_Restore/recover_logs/recover_log_SILK24 denied: The provided path is not whitelisted
May 22, 2020 11:42:52 AM - Info tar (pid=268) done. status 0

 

I configured whitelist path for progress log in order to use bprestore command, but above error still present.

[root@nbmasterna-01 NBU_Test_Restore]# bpsetconfig
bpsetconfig> BPCD_WHITELIST_PATH = /usr/openv/NBU_Test_Restore/
bpsetconfig> BPCD_WHITELIST_PATH = /usr/openv/NBU_Test_Restore/recover_logs/recover_log_SILK24

Please someone may assist me?

Thanks and Regards

Tags (2)
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Hi @albatroz19 

On further digging internally it appears that the behaviour is by design (post 8.1). The /usr/openv folder is protected in general from logging irrespective of the contents of the whitelist. Specific folders within that structure are allowed of course, so the standard log folder (/usr/openv/netbackup/logs) is okay as it is automatically allowed/whitelisted.

The bpcd logs can show clues to this behaviour:

If you see from the bpcd logs the "/usr/openv" location is treated as a protected location by NetBackup being its core location.

15:44:27.476 [45023] <4> initialize_NetBackupProtected_whitelist: Adding /usr/openv to NetBackup Protected list
15:44:27.476 [45023] <2> NBWhiteList::expand_path: expanded_path: /usr/openv

So the solution to your problem is to choose a progress log folder outside /usr/openv and add that to the whitelist directoive. Or log to the more standard location that doesn't require whitelisting (/usr/openv/netbackup/logs).

Cheers

View solution in original post

6 Replies
Highlighted

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Have you verified the permissions on those directories and made sure they are correct?

Could you list the permissions on the following

/usr/openv/NBU_Test_Restore/
/usr/openv/NBU_Test_Restore/recover_logs/

Highlighted

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Hi

permision were 777 for path

drwxrwxrwx 5 root root 1024 May 21 17:48 NBU_Test_Restore
drwxrwxrwx 2 root root 7168 May 21 17:18 recover_logs

Regards

Tags (2)
Highlighted

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Is any part of /usr/openv/NBU_Test_Restore/recover_logs/recover_log_SILK24 a softlink pointing elsewhere, such as /opt/openv/NBU_Test_Restore/recover_logs/recover_log_SILK24 or such ?

If so you might try authorizing the actual path and see if it works better than the softlinked version.

Another possibility - how long as it been since you authorized that path ? Is it possible NBU just hadn't read the new configuration in yet ? It's been 9 hours since your post, did it automagically start working since then ? =)

Highlighted

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

I think the problem may be that NetBackup is being too clever and you haven't whitelisted the actual path you are writing to. 

Try adding /usr/openv/NBU_Test_Restore/recover_logs  to the whitelist (yau have added the parent directory and the logfile itself, but not the target directory). 

Worth a try.

Highlighted

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Hi,
problem still present


@jnardello: No softlink but simple directory under /usr/openv. Path configured by some days so i'm expecting do it.

@davidmoline: I added these paths:

BPCD_WHITELIST_PATH = /usr/openv/NBU_Test_Restore/
BPCD_WHITELIST_PATH = /usr/openv/NBU_Test_Restore/recover_logs/

Error occours, on other master server v 8.1 or 7.7.3 it's ok.

Thanks & Regardss

 

Highlighted
Accepted Solution!

Re: Netbackup 8.2 BPCD_WHITELIST_PATH not ok

Hi @albatroz19 

On further digging internally it appears that the behaviour is by design (post 8.1). The /usr/openv folder is protected in general from logging irrespective of the contents of the whitelist. Specific folders within that structure are allowed of course, so the standard log folder (/usr/openv/netbackup/logs) is okay as it is automatically allowed/whitelisted.

The bpcd logs can show clues to this behaviour:

If you see from the bpcd logs the "/usr/openv" location is treated as a protected location by NetBackup being its core location.

15:44:27.476 [45023] <4> initialize_NetBackupProtected_whitelist: Adding /usr/openv to NetBackup Protected list
15:44:27.476 [45023] <2> NBWhiteList::expand_path: expanded_path: /usr/openv

So the solution to your problem is to choose a progress log folder outside /usr/openv and add that to the whitelist directoive. Or log to the more standard location that doesn't require whitelisting (/usr/openv/netbackup/logs).

Cheers

View solution in original post