Networker

Re: [Networker] Cloning Backups

2008-02-12 13:52:26
Subject: Re: [Networker] Cloning Backups
From: "Werth, Dave" <dave.werth AT GARMIN DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 12 Feb 2008 10:45:19 -0800
As far as your script goes I have no comment since all of or groups are
set to automatically clone.  On the rare occasions when I need to do a
manual clone I just use the GUI.

I practically never remove anything from the Networker index manually.
I just let Networker handle that automatically.

Our regular rotations is to do incrementals 6 days a week and a full
every weekend.  We send the clones from these off-site 5 days a week.
We have enough tapes (both backup and clone) in the rotation for about 8
weeks of backups and when we reach the end of that period I just
manually re-label the oldest regardless of their "expired" status.  So
every work day I take the clones from the previous days backup out and
our off-site provider picks them up.  Every day they bring back the
clones I sent off 5 weeks before.  Every week I re-label enough backup
and clone tapes for the next weeks worth of backup (with some cushion in
case of extraordinary demand).

At our fiscal month end (we do a 4-4-5 so it's almost always a Friday)
we do a special full backup with databases and the e-mail server shut
down.  For this we send the original backup off-site and keep the clone.
The reason for this is that this backup is kept as an archive and the
fact that a clone was made from it is confirmation of the readability of
the tapes.

Hopefully I answered your questions but feel free to ask for
clarification.

Dave

David Werth
Garmin AT, Inc
Salem, Oregon
dave.werth<at>garmin.com

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Weiner, Michael
Sent: Tuesday, February 12, 2008 7:02 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Cloning Backups

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

-------------------------
This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.
Thank you for your cooperation

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>