Hey, Also Frank ;-)

Frank

Today at 6:30pm, Terveen, Frank wrote:

Dear also Frank,

Not wanting to crowd the discussion
But it seems to me a legit solve you set
I would say that there should not be too much time between the both cos if the 
safety net backup is done and Joe then creates D:\G you have untill next 
safetynet backup to loose the ceo's mp3s

Regards
Met vriendelijke groet / Kind Regards

Frank Terveen
Senior Systems administrator / Senior Storage Administrator

----- Original Message -----
From: Frank Swasey [mailto:Frank.Swasey AT UVM DOT EDU]
Sent: Tuesday, November 22, 2011 07:24 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
Subject: Re: [Networker] null or skip

Today at 10:06am, bingo wrote:

Directives are also defined on the server and assigned to the client in the 
definition on the server.

----------

NW resources are in fact configured at the server. That was what i was talking 
about.
Local directive files on the client are possible but usually not used because 
their existence will be forgotten. This is especially important for skip/null 
directives.

I am still not clear why you want to backup files by an early group and skip 
them when you run a later group. As the group's major's attribute is the backup 
time, it does not matter when the file was backed up during the day - it will 
be omitted by the send attempt.
It might be a valid configuration but during all my years with NetWorker i 
encounter such one for the first time.

Bingo, allow me to educate you.

I have a client with a single data drive (let's call it D) that has
20TB of data on it.  Now, I can either define that client using "ALL"
and let NetWorker back up that drive D with a single stream, or I can
try to be efficient and break up the directories on the D drive so I
get multiple streams sending the data to NetWorker and hopefully get it
done in less than a week.

For the sake of example, let's say that I break it into 5 sub-trees:
D:\A, D:\B, D:\C, D:\D, and D:\E.  So, I set up my client with the
following save sets:

C:\
D:\A
D:\B
D:\C
D:\D
D:\E

I add this client definition into my Production group.

And all is good until Joe the sys admin creates D:\F on me.  Now, I've
got data that is not being backed up and eventually there is data loss
and Joe or I are gonna get fired (because it was the CEO's music
collection and he can't find all the CD's he stole that music off
again).

So, to protect my own job, I create a second client definition on the
server that has D:\ as its only save set, and I create a server side
directive that I assign to this client definition which says:

<< D:\A >>
  +null: .
<< D:\B >>
  +null: .
<< D:\C >>
  +null: .
<< D:\D >>
  +null: .
<< D:\E >>
  +null: .

I add this second client definition into my Safety Net group.

Now, when Joe creates D:\F, my safety net group which has that second
client definition as its member backs it up, I see that it backed
something up and I go buy Joe a beer and get him to admit what he did,
then I can add D:\F to the original client definition and the server
side directive for the second one.

So, back to my question...  Does the order of the Production and Safety
Net backup groups running make any difference in the goal to get all of
the data on D:\ backed up?

You still have the chance to test the behavior yourself.

I haven't forgotten, I was just hoping someone who has been doing this
for years would speak up and guide me as I am doing this for the first
time myself.

--
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER