Welcome! » Log In » Create A New Profile

[EMC-DataProtection-L] How to do this directive?

Posted by Anonymous 
[EMC-DataProtection-L] How to do this directive?
October 20, 2016 03:35PM
Hi,

I have a Linux file system: /data/base/data

with the standard lost+found sub-directory and another sub-directory
named extra_data. The extra_data sub-directory contains the following
six sub-directories:

EXTRA_1
EXTRA_2
EXTRA_3
EXTRA_4
EXTRA_5
EXTRA_6

These directories are rather large so I want to break the backups into
three NSR client resources wherein one resource captures the first three
directories, the second captures the last three and the third captures
any residual data that might be under extra_data (e.g. a newly added
directory, top-level file, etc.), but outside of those six directories,
as well as anything else under /data/base/data (e.g. lost+found). I want
all backups of anything under /data/base/data/extra_data to be based on
mtime, not ctime (default), but anything above that level, i.e. directly
under /data/base/data, but not under extra_data, can use the default
ctime change. I'm unsure if I'm doing this correctly, but here's what I
have:

NSR client resource 1 (group=extra_data1) lists the following save sets:

/data/base/data/extra_data/EXTRA_1
/data/base/data/extra_data/EXTRA_2
/data/base/data/extra_data/EXTRA_3

and uses the following directive (extra_data1):

<< /data/base/data/extra_data/EXTRA_1 >>
+mtimeasm: .?* *
<< /data/base/data/extra_data/EXTRA_2 >>
+mtimeasm: .?* *
<< /data/base/data/extra_data/EXTRA_3 >>
+mtimeasm: .?* *

NSR client resource 2 (group=extra_data2) lists the following save sets:

/data/base/data/extra_data/EXTRA_4
/data/base/data/extra_data/EXTRA_5
/data/base/data/extra_data/EXTRA_6

and uses the following directive (extra_data2):

<< /data/base/data/extra_data/EXTRA_4 >>
+mtimeasm: .?* *
<< /data/base/data/extra_data/EXTRA_5 >>
+mtimeasm: .?* *
<< /data/base/data/extra_data/EXTRA_6 >>
+mtimeasm: .?* *

NSR client resource 3 (group=extra_data_residual) lists the file system
itself:

/data/base/data

and uses the following directive (extra_data_residual):

<< /data/base/data/extra_data/EXTRA_1 >>
+null: .?* *
<< /data/base/data/extra_data/EXTRA_2 >>
+null: .?* *
<< /data/base/data/extra_data/EXTRA_3 >>
+null: .?* *
<< /data/base/data/extra_data/EXTRA_4 >>
+null: .?* *
<< /data/base/data/extra_data/EXTRA_5 >>
+null: .?* *
<< /data/base/data/extra_data/EXTRA_6 >>
+null: .?* *
<< /data/base/data/extra_data >>
+mtimeasm: .?* *

Question 1: For the above directive, I'm unclear if that last entry
should be at the end or the beginning of the directive. I put it last
because I thought it would be better to have it see everything that's
being nulled first before it sees what it's supposed to back up which,
of course, is anything else other than the six, but then it's to use the
mtime directive. Again, if its directly under /data/base/data, but not
under data_extra, then ctime is fine. Maybe I could just instead have:

<< /data/base/data >>
+mtimeasm: .?* *

If so, should that be last or first? Does order matter here?

Question 2: For the first two directives, can I instead have one line:

<< /data/base/data/extra_data >>
+mtimeasm: .?* *

in which case both resources can then use the same directive? I thought
it might be better to have the entries in the directive match their
associated save sets in the respective client resource. That's why I
enumerated each separately rather than just one entry. Not sure, though?

Anyway, I ran a full backup estimate for each of the three groups, and
the numbers that are reported agree with what I would expect, but the
mtime asm in the last directive (for the residual data) concerns me here
since I have no way of knowing if it's placed where it needs to be to
work as expected once we hit incrementals. I think the first two
directives should work although it may be unnecessary to enumerate all
three lines when maybe one will do. Hmm ...

--
George Sinclair
Voice: (301) 713-4921
- The preceding message is personal and does not reflect any official or unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -

--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l < at > listserv.temple.edu
Sorry, only registered users may post in this forum.

Click here to login