Networker

[Networker] Advice needed on staging policy values

2009-09-08 15:01:19
Subject: [Networker] Advice needed on staging policy values
From: Len Philpot <Len.Philpot AT CLECO DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 8 Sep 2009 13:56:37 -0500
We've just implemented 7.5.1 in our first production environment, which is 
magnitudes larger than the test environment before it. We have 11 roughly 
500 GB disk volumes we're backing up to, knowing that at some point we 
will probably have to stage to tape (and the pools, tapes, policies, etc. 
are all in place for that). Right now, three of those volumes are about 
20-25% used and that's it.

However, the *default* Max Storage Period on our staging policy is 7 days, 
which is waaaayyy too soon, causing our first test backups to already 
stage to tape. I know what the values all mean, but I've not yet spent a 
lot of time in thought as to what the best combination of max storage 
period, recover space interval and file system check interval is. But, 
blindly staging after only 7 days is clearly much too soon. We'd rather 
have a reasonable high water mark trigger staging than time.

Question: Given that we currently have the adv_file space available and 
don't need yet to stage, are there any hidden gotchas we'll run into if we 
push the max storage period to, say, a month, and just keep an eye on disk 
volume usage?

Any advice / tips / traps?

Thanks!
--
   Len Philpot 

   Cleco IT Network Services, PGO3 - ext 7167
(318) 484-7167    

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