Couple of questions:

o Is each of your clients in only one group?
o Do you let Networker automatically recycle your tapes?  You mention
that you use a script to recycle tapes that are on site, but what about
the off site tapes?

Thanks.
Teresa



>
> This is how I do it...
>
> I create several sets of groups like below.
>
> 1800_B30DaysR30Days
> 1800_B30DaysR1Year
> 1800_B30DaysR7Years
>
> These groups start at 6:00PM have a browse period of 30 days and
> retention of 30days/1year/7years respectively(I have these groups setup
> for every hour).  The above groups backup to the below pools
> respectively.
>
> OffsiteB30DaysR30Days
> OffsiteB30DaysR1Year
> OffsiteB30DaysR7Years
>
> Then I clone all the ssids in those backup pools to a clone pool called
> OnlineCloneB30Days.  After the cloning is done I send the original
> backup tapes offsite.  Then all recover requests use the
> OnlineCloneB30Days pool to recover from.  I run a script that checks the
> savetime of the ssids on the OnlineCloneB30Days volumes, and once all of
> the savetimes are older than "30 days ago" I recycle the volume(actually
> I use 37 days just for some slush time).
>
> Hope this helps,
>
> Joel
>
> -----Original Message-----
> From: Teresa Biehler [mailto:tpbsys AT RIT DOT EDU]
> Sent: Monday, April 21, 2003 2:05 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Merits of cloning versus dual backups?
>
> Ok, based on this, it sounds like sending original tapes off site is a
> good idea since their data is "verified".  I can't figure out how to get
> our retention scheme to work well with this idea, however.
>
> Here's what I want to accomplish:
> o Daily backups with browse/retention period of 5 weeks (dailies are
> incr, level 1 or full depending on the client type)
> o Weekly backups with browse/retention period of 3 months
> o Monthly backups with browse/retention period of 1 year
>
> Here's one way to do it with clones going off site:
> o Weekly and monthly clones are created to go off site.
> o Weekly clones have the same browse/retention as weekly backups, but
> they are in off site storage rather than being online for fast
> recoveries.
> o Create clones called either weekly or monthly depending on when they
> are written.  Monthly tapes are created the first full week of the
> month.  This is done with a script in cron.
> o Daily backups, weekly backups, weekly clones and monthly clones are
> all written to different pools.
>
> So, how do I do this same retention scheme but have my clones stay on
> site and the original backup tapes go off site?
>
> OR
>
> Is there some other way to verify that the data written on the clone
> tapes is good/readable?
>
> Thanks.
> Teresa
>
> Joel Fisher wrote:
> >
> > I started full scale cloning just about 2 months ago and it has
> already saved my butt.  It turned out we had a firmware issue with our
> drives, but I never got any errors until we attempted to read the data.
> Now, because of the cloning we are attempting to read every single
> saveset we back up so I started seeing a bunch of media errors.  After a
> couple of weeks of trouble shooting we wound up putting the latest
> firmware on the drives, now all is well.  Moral of the story is... if I
> hadn't been cloning I wouldn't have known I wasn't getting good backups
> until someone needed a restore.  Not a good time to find that out.
> >
> > Joel
> >
> > -----Original Message-----
> > From: Teresa Biehler [mailto:tpbsys AT RIT DOT EDU]
> > Sent: Friday, April 18, 2003 3:45 PM
> > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > Subject: Re: [Networker] Merits of cloning versus dual backups?
> >
> > Cloning verifies that the original copy is good, but not that the
> clone
> > is.  So, which copy do you send off site?  Do you send the original
> > because you know that copy is verified?
> >
> > -Teresa
> >
>
> --
> 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=