cancel
Showing results for 
Search instead for 
Did you mean: 

why can i backup via cli using bpbackup but cant from the same netbackup Admin Console policy

bc1410
Level 5

Hello

Netbackup 8.2 RedHat linux 7.9  one master/media server

The netbackup policy named Archival-test which has a type = Standard; schedule types are User Backup(named Archival), Full backup(named Archival Full), Cumulative Inc backup(named Archival Cumulative). The linux netbackup client is listed

So I have a file set of data that resides on a nas - lets say the directory is mounted on the linux client as follows: /nas1.test.com/Processing_Gen

The data needing backed up is under /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_Test_Junk_Point_

If I use the following netbackup cli syntax on the Linux client the backup is successful:

/usr/openv/netbackup/bin/bpbackup -p Archival-test -s Archival -S pgrid-1 '/nas1.test.com/Processing_Gen/ARCHIVE/Archive_\[01172022134535PM\]_
Test_Junk_Point'

So if I try to use the Admin console GUI with same policy and add the Backup Selection of /nas1.test.com/Processing_Gen/ARCHIVE/Archive_\[01172022134535PM\]_
Test_Junk_Point I get a status 71 when running a manual bkup

here is a snip from the bpbkar:

22:02:41.821 [57106] <2> create_backup_data_list: name: /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_
Test_Junk_Point, Backupid: arch-1.test.com_1642561360
22:02:41.821 [57106] <4> bpbkar expand_wildcards: start to backup filelist /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_
Test_Junk_Point ,nb_fscp_enabled is 0
22:02:41.821 [57106] <4> bpbkar expand_wildcards: INF - Processing /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_
Test_Junk_Point
22:02:41.825 [57106] <8> bpbkar expand_wildcards: WRN - Found no matching file system for /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_
Test_Junk_Point
22:02:41.825 [57106] <4> bpbkar expand_wildcards: end backup for filelist /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_
Test_Junk_Point
22:02:41.826 [57106] <4> bpbkar main: INF - Client completed sending data for backup
22:02:41.826 [57106] <2> bpbkar main: INF - Total Size:0
22:02:41.826 [57106] <2> accl_post_nbfeds_backup_list: Posting Accurate Licensing data
22:02:41.826 [57106] <4> accl_post_nbfeds_backup_list: Master server name: pgrid-1.test.com
22:02:41.826 [57106] <4> post_nbfeds_backup_list: Json String value: [{"virtualName":"","jobid":"","backupId":"arch-1.test.com_1642561360","backupSelectio
n":"/nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_
Test_Junk_Point","frontEndDataSizeMb":0.0}]
22:02:41.826 [57106] <2> post_nbfeds_backup_list: Post data URL: netbackup/catalog/frontenddata
22:02:41.843 [57106] <2> getCrlCheckLevelFromConfig: crlCheckFlag value read from bpconf : 1
22:02:41.901 [57106] <4> NBClientCURL::performCurlOperation: HTTP response header : HTTP/1.1 200 OK X-Connection-ID: {44749530-78D4-11EC-AFF9-8B78C02926AA} X-Targe
t-Master: master1.test.com X-Target-Master-ID: 0188bef7-0a09-441c-84a6-355b6c802378 HTTP/1.1 201 Strict-Transport-Security: max-age=31536000;includeSubDomains
X-Frame-Options: DENY X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block X-Request-ID: D555B28E4C19FFC3 Content-Length: 0 Date: Wed, 19 Jan 2022 03:0
2:41 GMT
22:02:41.903 [57106] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 71: None of the files mentioned in the file list exist or may not be accessible
22:02:41.903 [57106] <4> bpbkar Exit: INF - EXIT STATUS 71: None of the files mentioned in the file list exist or may not be accessible
22:02:41.903 [57106] <2> bpbkar Exit: INF - Close of stdout complete
22:02:41.903 [57106] <4> bpbkar Exit: INF - setenv FINISHED=1

 

9 REPLIES 9

davidmoline
Level 6
Employee

Hi @bc1410 

The backup selection in the policy is not correct. Refer to the following article which should explain what is required to use wildcards:  https://www.veritas.com/support/en_US/article.100038824

One question is the backup selection  meant to target a single folder or multiple folders? As you can see in the error messages, NetBackup is attempting to process the brackets as a wildcard selection.  Which might match Archive_1_Test_Junk_Point and Archive_P_Test_Junk_Point

If it is only a single folder, then you may need to change the backup selection in NetBackup to something like this:

/nas1.test.com/Processing_Gen/ARCHIVE/Archive_?01172022134535PM?_Test_Junk_Point

Also you may need to tick the "Follow NFS" box in the policy atttributes (it may not be as your selection is within the NFS volume, but if the above selection cchange still produces status 71, then look to this). 

Cheers
David

 

the users used the " [  "  and " ] " characters as part of the data path around a time stamp.   

Im able to do this via the command line using "\" backlash in front of the [ which is usually a wildcard character.  Per a Veritas tech note:

To use special or wildcard characters literally (that is, as nonwildcard characters), precede them with a backslash (\). For example, assume the brackets in the following are to be used literally:
/home/abc/fun[ny]name
In the exclude list, precede them with a backslash as in
/home/abc/fun\[ny\]name

A backslash (\) acts as an escape character only when it precedes a special or wildcard character as in the above example. This means that NetBackup normally interprets a backslash literally and it is a legal character to use in pathnames

There are multiple folder under the Archive_[01172022134535PM]_Test_Junk_Point directory /nas1.test.com/Processing_Gen/ARCHIVE/Archive_[01172022134535PM]_Test_Junk_Point

I also do have the "follow NFS" checked within the attributes.    The command line uses the backup schedule type "User Backup" but when using the admin console to kick off the backup manually the "User Backup" type is not an option.  ONLY the FULL and Cumulative types.  So not sure if I can only use the backslash to act as an escape charater in a User Type schedule of a backup??

backslash (\) acts as an escape character only when it precedes a special or wildcard character as in the above example. This means that NetBackup normally interprets a backslash literally and it is a legal character to use in pathnames

Hi @bc1410 

Interesting -  I've tried on a 9.1 system and using your backup selection works as you expected (but not what you are seeing). I created a couple of folders (local, but I don't see that as being relevant) with a similar name to what you provided including the "[" and "]" in the name. My backup selection added one using the format you provided and the backup worked. If I removed the "\" character from the backup selection the backup failed similarly to what you were seeing. 

Can you find the includes file from the policy as you created and examine the contents (/usr/openv/netbackup/db/class/<policy>/includes). On my 9.1 Linux test system the file contains the line:
/var/tmp/archive/Target_\[12341234PM\]_Test_Point

The behaviour must be slightly different with 8.2. It appears that the backslash is being eaten before the selection is made on the client. You could try adding a second backslash to your backup selection and seeing if this works
e.g.  /nas1.test.com/Processing_Gen/ARCHIVE/Archive_\\[01172022134535PM\\]_Test_Junk_Point).
Or else use the "?" wildcard character where the "[" and "]" goes (this also works on my NBU 9.1 system).
/var/tmp/archive/Target_?12341234PM?_Test_Point

David

Hey David - 

We should have already upgraded to 9.1.0.1 but it just hasn't happened yet.   Supposedly next week we will be doing that.. 

Thanks for you help with this..  I just think its odd that the backup works from the command line on the linux client server using /usr/openv/netbackup/bin/bpbackup but doesnt work on the master server admin console under the same policy.

 I tried using the double backslash "\\" before the brackets "[" "]" within the data path for the backup selection of the policy but it doesnt work..  Also tried the ? but not sure why I would do this..  As the brackets are part of the actual data path that the user created.     Didnt matter as both still gave me the same error.

The includes file from the policy is as follows - I had to "x" out some sensitive info.:

/xxxxxxx.com/Processing_General/ARCHIVE/xxx_Archive_\[01172022134535PM\]_xxx_xxxx_Point_xxNS002-xxNS003

As you are probably questioning this is a different data set and path..   But same scenario.  Worked on the command line with bpbackup but not with the policy on Admin Console when running it manually.  

The only difference its that the bpbackup cli uses the "User Backup" type of schedule where as when I use the Admin Console and manually try to kick off the backup it uses the "FULL Backup" type schedule as the User Backup type isnt even an option on a manual bkup. 

 

Hi @bc1410 

The difference between the command line and via the policy, is how wildcards are being interpreteed. From the command line you are passing a file specification to bpbackup, so the path you provide works from the Linux shell. When running via the GUI, the backup specification is treated somewhat differently. I was surprised (once I understood the actual path name) that your specification didn't work.

The "?" character is a single character wildcard (like the *, but matches a single character only). As I indicated it worked fine for me on a 9.1 system, so they must have changed something in the logic behind using the file specification from the policy. 

What is the OS and NetBackup version on the client? I have now spun up a NetBacup 8.2 server and I can successfully backup an NFS mounted folder using the file specification (or similar) to yours. In my case the backup client is also the master/media server (with a NFS mount from another Linux client).

Regards
David

Hey David - sorry for the really bad delay in responding..   my apologies

Im trying to circle back to this..  We just upgraded to 9.1.0.1 and I will try this on the 9.1.0.1 environment but I have the feeling that I will still have the same issue..  maybe?

 

I will run some tests and reply back to the thread.   

Thanks again for your support and knowledge..

 

BC

hha_mea
Moderator
Moderator
   VIP   
Hello,
I’m kind of interested in this.. were you able to solve this?
Thanks.

Hi @davidmoline 

We are on v9.1.0.1 and I still get same results..  

I was thinking maybe its the way that the share is mapped on the linux client that we are trying to back data up from..  But after running some tests with backing up data that do not contain these character "[" or "]" within the main directory path those backups where successful via the Admin console.

Do you think it could be something that may be lingering via an exclusion file on our netbackup master/media server that is throwing it off?

So I tried again via the admin console and still get a status 71 

Mar 2, 2022 4:55:18 PM - Error bpbrm (pid=24346) socket close failed, Bad file descriptor (9)
Mar 2, 2022 4:55:18 PM - Info bpbkar (pid=16635) done. status: 150: termination requested by administrator
Mar 2, 2022 4:55:20 PM - Info bpbkar (pid=16635) done. status: 71: None of the files mentioned in the file list exist or may not be accessible
Mar 2, 2022 4:55:20 PM - end writing
none of the files in the file list exist  (71)

 

So I tried what you did buy replacing the [  and ] with a question mark  "?" with in the backup selection data path via the admin console and I still get same result...

Mar 2, 2022 5:05:11 PM - Info bpbkar (pid=18290) Backup started
Mar 2, 2022 5:05:11 PM - Info bpbrm (pid=29847) bptm pid: 29902
Mar 2, 2022 5:05:11 PM - Info bpbrm (pid=29847) from client s01-parch-1.kbs-caci.com: TRV - Found no matching file system for /omeganas.XXXXXXXX.com/Processing_General/ARCHIVE/_RESTORE-TEST/XXX_Archive_[01172022133457PM]_XXX_XXXXXX_XXXXX_XXX001
Mar 2, 2022 5:05:11 PM - Error bpbrm (pid=29902) socket close failed, Bad file descriptor (9)
Mar 2, 2022 5:05:11 PM - Info bpbkar (pid=18290) done. status: 150: termination requested by administrator
Mar 2, 2022 5:05:12 PM - Info bpbkar (pid=18290) done. status: 71: None of the files mentioned in the file list exist or may not be accessible
Mar 2, 2022 5:05:12 PM - end writing
none of the files in the file list exist  (71)