cancel
Showing results for 
Search instead for 
Did you mean: 

backup selection list--why is it backing this dir up?

spitman
Level 5

I'm really hoping this is something simple... because I just don't get it...

I am backing up a directory called /data/frozen_archive/pan_logs/db_12345 in another thread (with the NEW_SELECTION option).

In the thread below, I tried to set it up so it would back up all but the /data/frozen_archive/pan_logs/d* directories/files.

However, when you look at the second screenshot, the "current file" shows to be just what I don't want this thread to back up. Is the "current file" shown misleading? Or--what am I doing wrong? --because it has to be something simple, I'm sure...

Thanks in advance.

1.jpg

 

2.jpg

1 ACCEPTED SOLUTION

Accepted Solutions

CRZ
Level 6
Employee Accredited Certified

This is a pretty old TechNote, but perhaps it still applies...  What is your LOCALE?

DOCUMENTATION: The file list specified for backups may not be treated as case sensitive if the LOCALE is not set to C
 http://symantec.com/docs/TECH33696

EDIT: It might actually be LC_COLLATE handling this, so let's look at that one, too.  (Internal doc TECH144621)

View solution in original post

6 REPLIES 6

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Everything seems fine from your explanation.

Curious to see the Backup Selection part of the policy config (bppllist <policy-name> -U)

There are a couple of reasons I can think of:

  • Policy was changed and then started without nbpem getting refreshed.
  • Policy was changed but old STREAMS... file in Client's image folder on master is still present.
    I have seen how this file can override newer Backup Selection.
    No documentation for this - just personal experience. 
    Only solution was to delete all STREAMS... files before next Full backup. New Streams file will be created when new Full backup runs.

If above does not apply, we will need client's bpbkar log (level 1 should be fine) to see how the Backup Selection is interpreted by the client. 

CRZ
Level 6
Employee Accredited Certified

This is a pretty old TechNote, but perhaps it still applies...  What is your LOCALE?

DOCUMENTATION: The file list specified for backups may not be treated as case sensitive if the LOCALE is not set to C
 http://symantec.com/docs/TECH33696

EDIT: It might actually be LC_COLLATE handling this, so let's look at that one, too.  (Internal doc TECH144621)

spitman
Level 5

Good morning, Marianne :)

I tried restarting nbpem. I cleaned out the STREAMS files in that host's images directory. I reran the backup; and the same thing happened. Here's the backup selections list:

  Include:  NEW_STREAM
            /data/[A-Z]*
            /data/[a-e]*
            /data/[g-z]*
            /data/frozen_archive/[a-o]*
            /data/frozen_archive/[q-z]*
            /data/frozen_archive/[A-Z]*
            /data/frozen_archive/_*
            NEW_STREAM
            /data/frozen_archive/pan_logs/[A-Z]*
            /data/frozen_archive/pan_logs/[a-c]*
            /data/frozen_archive/pan_logs/[e-z]*
            NEW_STREAM
            /data/frozen_archive/pan_logs/d[A-Z]*
            /data/frozen_archive/pan_logs/da*
            /data/frozen_archive/pan_logs/d[c-z]*
            /data/frozen_archive/pan_logs/db_1[0-3][0-8]*
            NEW_STREAM
            /data/frozen_archive/pan_logs/db_139*
            NEW_STREAM
            /data/frozen_archive/pan_logs/db_1[4-9]*
            /data/frozen_archive/pancountdaily
            /data/frozen_archive/perfmon
            NEW_STREAM
            /data_splunk/data/[A-Z]*
            /data_splunk/data/[0-9]*
            /data_splunk/data/[a-r]*
            /data_splunk/data/[t-z]*
            /data_splunk/data/splunklogs/_*
            /data_splunk/data/splunklogs/[A-Z]*
            /data_splunk/data/splunklogs/[0-9]*
            /data_splunk/data/splunklogs/[a-o]*
            NEW_STREAM
            /data_splunk/data/splunklogs/pancountdaily
            /data_splunk/data/splunklogs/perfmon
            /data_splunk/data/splunklogs/persistentstorage
            /data_splunk/data/splunklogs/pan_logs/[0-9]*
            /data_splunk/data/splunklogs/pan_logs/[A-Z]*
            /data_splunk/data/splunklogs/pan_logs/[a-c]*
            /data_splunk/data/splunklogs/pan_logs/[e-z]*
            NEW_STREAM
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/[A-Z]*
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/[a-z]*
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/[0-3]*
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/4[0-8]*
            NEW_STREAM
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/49[0-4]*
            NEW_STREAM
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/49[5-9]*
            /data_splunk/data/splunklogs/pan_logs/datamodel_summary/[5-9]*
            NEW_STREAM
            /data_splunk/data/splunklogs/pan_logs/d[b-z]*
            NEW_STREAM
            /data_splunk/data/splunklogs/[q-z]*

...and I'm attaching the log to this post. Thanks :)

 

spitman
Level 5
> locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Both the client and the master server look like this.

spitman
Level 5

Well I'll be darned. It looks like the locale thing was the issue. For a test, I took out all my cap options, and the issue seems to have gone away. Thanks folks--

CRZ
Level 6
Employee Accredited Certified

Thumbs up emoji!  (Where'd our smileys go?)

We'll add 7.x to that TechNote.