For certain groups, I have a schedule that calls for running a level
full at the end of the first week of each quarter: Jan, Apr, Jul, Oct
and incrementals and level backups at all other times, typically three
weeks of incrementals, followed by a lower level backup at the end of
the third week like 5, 4, 3, etc. each month until hitting the full
again. I never schedule a level backup the week before a full, though,
so there might be a strech where there's 4 contiguous weeks of
incrementals, followed by the full.
Can I get by with a 2month browse policy on the clients since I thought
it went one cycle beyond that to previous full?
At what point does information in the index get truncated? I thought, in
this case, it would be at least anything older than 2 months plus one
cycle. I want to make sure that fulls are not forced because NetWorker
can't figure out how to do an incremental or level since it deleted the
previous full info?
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu