Re: [Networker] Browse and Retention planning/question
2006-11-30 13:37:40
> Do you mean that the Auto Media Management attribute for the device does not
> have to be set to 'Yes' for the device to re-use eligible media that is in
> the device?
No. I was assuming AMM on a jukebox. That is not needed for Networker
to relabel a recyclable volume automatically.
AMM on a standalone drive is different as Davina pointed out. I'm not
certain which you're referring to.
> The 20 tape pool will be a full and 2 incrementals each M-F for 4 weeks I
> guess I may need to make that a 26 or 27 day retention to ensure that the
> media is eligible for recycling by the time it rolls around again.
The full referred to by an incremental must be retained for the
incremental to be usable. So the actual retention time for the full is
the retention period plus the length of the cycle (assuming you don't
have an error and skip a full). Your pool must be able to handle that
much time. If you do fulls every week, then that would add 6 or 7 days
to the length of time the data remains.
> The Monthly will be a single Full with 20+ year retention. Index sizes are
> not a problem the number of files on this system is only 10K or so. The
> full will go offsite the day after it's completed.
Unless something has changed recently, Networker does not maintain
separate cycle tracks. A full in one group/instance affects the entire
client.
So you probably want to immediately schedule a full in your onsite pool
after the full in the offsite pool. Otherwise incrementals done would
refer to the offsite full (complicating any restores).
--
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
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>
|
- Re: [Networker] 7.3.x, (continued)
- [Networker] 7.3.2 list of known problems, King, David
- [Networker] Browse and Retention planning/question, Shawn Cox
- Re: [Networker] Browse and Retention planning/question, Randy Doering
- Re: [Networker] Browse and Retention planning/question, Darren Dunham
- Re: [Networker] Browse and Retention planning/question, Davina Treiber
- Re: [Networker] Browse and Retention planning/question, Darren Dunham
- Re: [Networker] Browse and Retention planning/question, Shawn Cox
- Re: [Networker] Browse and Retention planning/question,
Darren Dunham <=
- Re: [Networker] Browse and Retention planning/question, Davina Treiber
- Re: [Networker] Browse and Retention planning/question, Maarten Boot
- Re: [Networker] Browse and Retention planning/question, Coty, Edward
- Re: [Networker] Browse and Retention planning/question - SOLVED., Shawn Cox
- [Networker] 7.3.2 list of known problems, King, David
- Re: [Networker] 7.3.2 list of known problems, Jeff Kelly
Re: [Networker] backup of / failing, Landwehr, Jerome
Re: [Networker] backup of / failing, Tim Mooney
Re: [Networker] backup of / failing, Charles Heynig
|
|
|