stewartk2

updated

14 years ago

S

stewartk2

20 Posts

1

6542

February 15th, 2012 06:00

NDMP Backup Wildcards?

NW 7.6.2,  Windows, NDMP running Snapsure option.

I have a filesystem that is too large to snap in 1 hour - which is the limit according to support.  I need to get the filesystem backed up, because we are moving it to Isilon. There are 4 top level subfolders, and I am able to get 3 of them to finish.  The last lab is just too big, and they have about 30 subfolders under their top level folder.  I would like to split the folder up by using wildcards such as A-M and N-Z.  I used to be able to do this with mailboxes in Exchange backups, and I'm hoping I can do the same with NDMP instead of listing out each subfolder in the save set field.

Does anyone have experience with this?

Thanks,

Kathy

  • rmines1

    49 Posts

    2407

    0

    Posted February 21st, 2012 10:00

    Hi Kathy:

    I assume since you mention Snapsure that this is a Celerra.  You can use wildcards but must specify the complete path down to the directory you want to exclude.  Following are the rules:

    The path must start with a forward slash (/) and the file system name

    The path can contain a maximum of 1,023 ASCII* characters

    Supported wildcards are:  question mark (?), which matches any single character and asterisk (*) which matches any sequence of zero or more characters

    valid path= the complete path of the directory (and the specific type of subdirectories, if using wildcards) to exclude from the backup

    For directory filtering, the question mark and asterisk wildcards can appear only at the end of the string

    NOTE:  The question mark wildcard is not accepted when Celerra international character sets are enabled.  A message is sent to the server log when this is attempted.

    The pattern-match algorithm is case-sensitive, by default

    Example:

    To exclude the directory /ufs1/dir1 from the NDMP backup, type:

    EMC_EDIR01=/ufs1/dir1

    To also exclude all directories that begin with "d" under /ufs2, type:

    EMC_EDIR02=/ufs/d*

    Based on your entry above it sounds like you want to exclude all directories under your mountpoint between let's say A-N.  Let's say your mountpoint is /Users....so your entries would be something like the following:

    EMC_EDIR01=/Users/A*

    EMC_EDIR02=/Users/B*

    EMC_EDIR03=/Users/C*

    And so on up to EMC_EDIR50 (50 is the maximum based on default.  It can be increased by modifying the filer.numDirFilter parameter)

    Keep in mind it is case sensitive so if you might have some directories that start with A while others start with a....then you will need a separate entry for each one.

    Last but not least.....please note that in spite of the filtering...you will still see the savesets appear to start but note that NOTHING will be backed up....I think the size will be something like 512KB or something which is basically just the NetWorker start mark for an NDMP backup.

    If you are interested this is also documented in the "Configuring NDMP Backups on Celerra" which is available on Powerlink.

    Hope this helps.

    Regards,

    Rita Mines

  • stewartk2

    20 Posts

    2407

    0

    Posted February 21st, 2012 11:00

    Rita:

    Thanks for the response.  I actually need to do the opposite.  I need to split the backup into smaller chunks, so I was hoping that I could do something like this for the saveset.

    /root_vdm_3/group12/A*

    /root_vdm_3/group12/C*

    so that they would run separately or I could run 2 backups of the same group but with different subdirectories.  There are about 20 directories under the root and I would rather not have to list them all.

    Thanks,

    Kathy

  • stewartk2

    20 Posts

    2407

    0

    Posted February 21st, 2012 12:00

    Rita:

    Thanks!

    Kathy

  • rmines1

    49 Posts

    2407

    0

    Posted February 21st, 2012 12:00

    Hi Kathy:

    This should work fine.  Just keep in mind that it has to be:

    1)  The full path starting from the mountpoint down to the directory (so if you have /root_vdm_3/Users/group12/A*....or /root_vdm_3/group12/A*....but must be exact right down to that A*).

    2)  It is case sensitive

    3)  Maximum of fifty per backup

    4)  Each entry (directory path) is on a separate line in the Application Information section of the Client resource

    5)  Each entry increments the counter by 1....EMC_EDIR01, EMC_EDIR02, EMC_EDIR_03 and so on.

    Let me know if you have any problems.

    Regards,

    Rita

  • Thierry101

    2 Intern

    •

    326 Posts

    2407

    0

    Posted March 12th, 2012 15:00

    Hi

    Good discussion and have checked the guide from powerlink...

    Just a q about :-

    4)  Each entry (directory path) is on a separate line in the Application Information section of the Client resource

    What would be in save set then? just the root share? Thanks

    Thanks

  • Thierry101

    2 Intern

    •

    326 Posts

    2407

    0

    Posted March 12th, 2012 15:00

    ignore my post....got it...

  • Thierry101

    2 Intern

    •

    326 Posts

    438

    0

    Posted March 12th, 2012 19:00

    Hi ahmed

    Thanks

    Saw that in powerlink but we are using 7.6.2

    and this describes (also not applicable but similar issue) as informational but key function is not performed which is to exclude certain shares during backup https://solutions.emc.com/emcsolutionview.asp?id=esg119034    

  • Thierry101

    2 Intern

    •

    326 Posts

    2407

    0

    Posted March 12th, 2012 19:00

    These are in Application and Information

    HIST=Y

    UPDATE=Y

    DIRECT=Y

    OPTIONS=NT

    SNAPSURE=Y

    NSR_NDMP_TMP_DIR=K:\Temp

    EMC_EDIR01=/root_vdm_1/EVAL/P*

    EMC_EDIR02=/root_vdm_1/EVAL/U*

    EMC_EDIR03=/root_vdm_1/EVAL/W*

    but it backs up entire /EVAL and this message seen on daemon..have also tried with exact name and " "

    Failed to process job state change: No save instance found with job id 70010

  • Bebo2k

    544 Posts

    2407

    0

    Posted March 12th, 2012 19:00

    Hi Thierry101,

    I think this is a known bug or issue , please check the following Powerlink article:

    https://solutions.emc.com/emcsolutionview.asp?id=esg118783

    Thanks,

    Ahmed Bahaa

  • Thierry101

    2 Intern

    •

    326 Posts

    438

    0

    Posted March 13th, 2012 12:00

    hi

    in save set = /root_vdm_1/EVAL

    the size is 6.7GB ...that is the size of entire /EVAL

    3/13/2012 3:57:47 PM 6726 MB 4/17/2012 /root_vdm_1/EVAL

    in sg completion

    42617:nsrndmp_save: NDMP Service Log: SnapSure file system creation succeeds

    42617:nsrndmp_save: NDMP Service Log: Processing for filter EMC_EDIR01 successful

      42617:nsrndmp_save: NDMP Service Log: Processing for filter EMC_EDIR02 successful

      42617:nsrndmp_save: NDMP Service Log: Processing for filter EMC_EDIR03 successful

      42953:nsrdsa_save: Performing Non-Immediate save

    42617:nsrndmp_save: NDMP Service Log: server_archive: emctar vol 1, 65272 files, 0 bytes read, 6887570380 bytes written

      42617:nsrndmp_save: NDMP Service Log: Total number of directories matched : 0

      42951:nsrdsa_save: Successfully Done.

    by excluding the P,U and W..the backup size expected is 200MB...

    but still all /EVAL is backed up..