Veritas-bu

Re: [Veritas-bu] Offsite tapes

2007-06-11 13:50:29
Subject: Re: [Veritas-bu] Offsite tapes
From: "Wolters, Keith" <Keith.Wolters AT level3 DOT com>
To: "Jeffrey Dykzeul" <Jeffrey_Dykzeul AT raytheon DOT com>
Date: Mon, 11 Jun 2007 11:30:47 -0600
 Would this work even if the disk storage and the tape library are on
different media servers? If so, it looks like it might work.

-----Original Message-----
From: Jeffrey Dykzeul [mailto:Jeffrey_Dykzeul AT raytheon DOT com] 
Sent: Monday, June 11, 2007 1:04 PM
To: Wolters, Keith
Subject: Re: [Veritas-bu] Offsite tapes

Keith:

If you are using a tape library with multiple tape drives I recommend
NOT using bpduplicate. Instead, modify the relevant policy/schedule to
create an additional copy on tape, simultaneously with the primary copy.
Yes, it ties up an extra tape drive, but it takes barely more time than
creating the first tape copy.

I went through the whole bpduplicate learning curve and testing, only to
find that it took way too long in our environment, since you lose
multiplexing, as Mr. Preston pointed out. So I moved to creating
simultaneous copies on tape, which works out much better for us. Luckily
we have a fair sized ADIC tape library with six LTO3 drives, but you can
use this approach effectively even if you only have two drives. You just
need to schedule jobs appropriately given your resource availability.

There is no scripting involved, just look at the "attributes" tab for a
given schedule. Click on "multiple copies" then the "configure" button.
This allows you unique properties per copy for storage unit, volume
pool, retention period. I specify a "full" pool for copy 1 and an
"offsite" pool for copy 2. When the resulting backup actually runs, you
will see multiple job IDs per backup stream. In my case I now see 3 per
backup stream - one is sort of a general info job, another shows writing
to the "full" pool, and the third shows writing to the "offsite" pool.
When all of the backups are done, just pull all the volumes in the
"offsite" pool and send them offsite.

Your staging to disk may complicate matters if you are using NBU to
perform the staging. We also utilize some staging to disk, but
independently of NBU (we use ufsdump, and are moving to rsync). After
the staging completes we use NBU to backup the staging disks to tape on
a daily basis, either full, cumulative or incremental. Once per month
the backup of the staging disks is a full with two copies, as described
above.

jd




 

 

             "Wolters, Keith"

             <Keith.Wolters@le

             vel3.com>
To 
             Sent by:
<VERITAS-BU AT mailman.eng.auburn DOT edu> 
             veritas-bu-bounce
cc 
             s AT mailman.eng DOT aub

             urn.edu
Subject 
                                       Re: [Veritas-bu] Offsite tapes

 

             06/08/2007 09:52

             AM

 

 

 

 





We do have a relatively small set of backups being sent offsite and
since the company's assets are being migrated to the parent company I
only need a short term solution.

Since bpduplicate will detect if it already has a second copy of a
backup is there any drawback to a simple script which runs daily and
blindly attemps to duplicate every backup in the past 7 days for any
client on my list? I figure that way I won't have to worry when my
script runs compared to when staging takes place and on Monday I don't
need to alter the script to duplicate the past three day's backups.

I can keep track of the tapes in my offsite pool and when they expire in
a spreadsheet since there should be no more than 20 or 30 tapes out at
any point in time.

From: Curtis Preston [mailto:cpreston AT glasshouse DOT com]
Sent: Friday, June 08, 2007 2:33 AM
To: Wolters, Keith; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Offsite tapes

NBU has a number of copies field (Master Server properties in your GUI,
I'm on a plane right now and don't have access to a server)  If it's set
to 2 (your case), it will only make two copies of a given backup.  What
I think is happening is that your disk staging setup has duped your disk
backup to tape, but hasn't yet expired it from disk.  Now there are two
copies and you're trying to make a third.  So you can fix your problem
by setting the number of copies to 3.

Or....

You can leave it at 2 and use the feature of bpduplicate that
automatically figures out which backups to copy.  If you say you want
two copies, and then just run bpduplicate without specifying backup
image names.  You can specify the name of the policies and clients you
want it to look at.  Then it will look at all the backups that don't
have two copies, select them, and dupe them for you.  If you've got some
images that are on disk staging and on tape, they won't dupe at that
time. As soon as they expire off disk, they'll get duped the next time
you run bpduplicate without specifying image names.  This method will
only work if you're a relatively small shop that can do all your dupes
with one dupe session, as there's no multistreaming/multiplexing this
way.

Finally, I'd have to say that my opinion is that the best way to do
anything like this is to use NBU Vault.  Feel free to do a proof of
concept before you pay for it, but my opinion is that whatever you're
saving by not paying for it is more than lost by the time you'll spend
writing a script.

---
W. Curtis Preston
Author of O'Reilly's Backup & Recovery and Using SANs and NAS VP Data
Protection GlassHouse Technologies


From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Wolters,
Keith
Sent: Thursday, June 07, 2007 12:30 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Offsite tapes

I'm trying to develop a procedure for duplicating backups for offsite
using NBU 6.0 (master and media servers are Solaris). There are about 8
machines whose backups I want to duplicate. Some backup go directly to
tape and some are staged to disk. I use automatic staging. When I run a
script to use bpduplicate I notice I sometimes get errors like this:

nbdup.log:11:06:54 INF - Skipping backup id amamed_1181109602, it
already has 2 copies.

I assume that has to do with whether or not my script runs after the
backup has already been staged to tape. What I need to know is how best
to deal with that and get a copy whether or not a backup has been
migrated to tape or not._______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>