Networker

Re: [Networker] Cloning Backups

2008-02-12 10:05:20
Subject: Re: [Networker] Cloning Backups
From: "Weiner, Michael" <weinerm AT CCF DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 12 Feb 2008 10:02:13 -0500
>>> "Werth, Dave" <dave.werth AT GARMIN DOT COM> 19/Dec/2007 1:17 pm >>>
Michael,

We've always used automatic cloning without a problem*.  I like it
because it immediately verifies the readability of the original backup.
If your "monthly fulls" are in their own group is will be easy to turn
cloning on for them.  We automatically clone every backup and send the
clone tapes off-site (some one other than Iron Mountain) every working
day.

If you are going to manually clone I would think cloning by Save Set is
the way to go since there may be other save sets on a volume rather than
the ones you are interested in.  In the GUI (7.2.2 but there must be
something similar in later versions) under Save Set Clone you can query
save sets by date, pool, client, maximum level, etc. so getting the list
of save sets shouldn't be a problem.  Set your dates appropriately and a
maximum level of "full" (level 0)and you should have a list of save
sets.  I believe there's an "mminfo" query behind the Save Set Clone
that produces the information but I'm not familiar enough the mminfo
command to write it off the top of my head and can't take the time right
now to research it.
--
Dave - 

Thanks for the response, sorry for the huge delay in getting back with
you on this but I had a follow-up question or two in regards to the
cloning. We are doing the same thing - taking a monthly full and then
doing a clone, and sending that clone set off-site with Iron Mountain.
Is it necessary or even desired to remove the clone set from the index
at all?

We will be rotating a set of clone tapes monthly 1 - keeping one set at
Iron Mountain while the other set resides in the tape library getting
ready to be used in the cloning process.

For what its worth I am basically using the following to get things
moving, script-wise:

/usr/sbin/nsr/mminfo -s localhost -r "ssid" -q
"level=full,pool=MCarray,savetime>=4 weeks
ago,name=/export/array,name=/export/local" > $SSIDLOG

/usr/sbin/nsr/nsrclone -vvv -s localhost -b "MCarray Clone" -S -f
$SSIDLOG

This is 6.1.Build.186 Solstice Backup just for completeness.

Thanks for all the help from all who responded earlier.

Michael

===================================

P Please consider the environment before printing this e-mail

Cleveland Clinic is ranked one of the top hospitals
in America by U.S. News & World Report (2007).  
Visit us online at http://www.clevelandclinic.org for
a complete listing of our services, staff and
locations.


Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank 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>