Networker

Re: [Networker] best practices for jukebox

2011-11-14 19:36:26
Subject: Re: [Networker] best practices for jukebox
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 14 Nov 2011 18:35:03 -0600
In regard to: [Networker] best practices for jukebox, andyman said (at...:

A quick question.  I currently have legato networker stream client data
to disk.  I've assigned those disk to a pool called localpool.

I was wondering.  What is the best practice to put those copies to tape?
The goal is to store incrementals nightly, fulls weekly, and off site
monthly.

Ok those goals can be modified.  Just wondering, what are the best
practices?  And what media pools do people use for their tapes?

Part of the answer to that is going to depend on how often you have to
stage to tape, which is going to be dependent on how much you're backing
up and what your retention is.  If you have enough space in your local
disk to keep *all* of your backup data on disk, then you really only need
to copy (in NetWorker parlance: clone) data to tape for your monthly
offsites, so in that case you probably only need one additional pool
("Offsite").

If you don't have enough local disk to keep all of your backup data on
disk, then you may (or may not, it depends) need an additional pool.  In
this situation, you're occasionally going to need to stage (that's a clone
+ deletion of the original savesets, which mostly makes sense only when
the source savesets are on disk, though there are times when staging from
tape to tape is useful) from disk to tape, which might mean you have a
pool for staged data.

One mistake that I made when starting with NetWorker, and that the experts
frequently caution against, is using too many pools.  It's tempting to
create all sorts of pools to segregate your data, especially if you have
data from multiple different types of clients -- not just types of hosts,
but how the clients themselves are run, or if they're run by different
groups within your enterprise.

Having lots of pools frequently just complicates things and it also often
means that you have tapes in pools that don't need them, but you're short
in pools that do need them.

The big reason to have different pools is retention time.  You don't want
to mix savesets that should only be retained for a week on the same tape
volumes that have savesets that need to be retained for a quarter.  It
*might* be ok to mix savesets if their retention times are relatively
close; say two weeks vs. 1 month, but if they're wildly different, you
probably want a separate pool.

Note also that there are a limited number of criteria that NetWorker uses
to determine what pool a saveset should go to.  See Media->Media
Pools->Properties in the NetWorker Administration GUI, specifically the
Basic and Selection Criteria Tabs.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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

<Prev in Thread] Current Thread [Next in Thread>