ADSM-L

Re: TSM DBBackup

2002-07-08 21:54:49
Subject: Re: TSM DBBackup
From: Michael Benjamin <MBenjamin AT BUNNINGS.COM DOT AU>
Date: Tue, 9 Jul 2002 09:52:49 +0800
Hi Alex,

If you've tarred the file to LTO, how do you utilise it quickly? It's almost
easier to let TSM perform the dbbackup to LTO, and then you have a dbbackup
volume you can utilise straight away.

The dbbackup takes a few minutes to complete, time is a non-issue here.

Yes it's a shame you have to waste a lot of space on the dbbackup volume,
but
it's the same type of volume and that's worth a lot...

I guess you have to work out how much your data is worth, if it's more than
about
$1000 AU then it's definately worth buying some more tape volumes to rotate
your
DB offsite. The DB is simply too important to mess around with and lose...
that single
volume represents the entire contents of your server, if you lose that and
your db/mirrors
on the filesystems your 10,000 tapes aren't worth a thing to you come
recovery time they
are just a massive collection of ones and zeros...

Mike.

> -----Original Message-----
> From: Alex Paschal [SMTP:AlexPaschal AT FREIGHTLINER DOT COM]
> Sent: Tuesday, July 09, 2002 1:26 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: TSM DBBackup
>
> You can do a dbbackup devc=file_class, which will put the dbbackup into a
> file on disk.  The only thing is you'd then have to script a process that
> somehow backs up that file, or do it manually.  Possibilities include:
>
> FTP to remote site
> tar to 4mm tape
> tar to LTO
>
> Personally, I'd rather not run so tight on scratches that I don't have 7
> tapes I can spare for dbbackups.
>
> Alex
>
> -----Original Message-----
> From: Bill Wheeler [mailto:Bill.Wheeler AT LA-Z-BOY DOT COM]
> Sent: Monday, July 08, 2002 6:30 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM DBBackup
>
>
> Currently we run our archive to a Magstar 3570 tape subsystem.  Once the
> archive is complete we run the DBBackup to a new 3570 scratch tape.  The
> issue is that the DBBackup is so small at this point; we are looking at
> options to find a way to back it up differently.  On an LTO tape we might
> us
> 1 to 2 GB, and cannot see wasting 98 GB (uncompressed).  If we could put
> both the archive and DBBackup on one cartridge that is the way we would
> go.
> If not, can the DBBackup be put to a flat file where it can be restored
> from?  We would like to make sure it is the same type of tape volume that
> we
> are using, we just want to make sure that it is cost effective.
>
> Bill Wheeler
> PDM Administrator
>
> -----Original Message-----
> From: Michael Benjamin [mailto:MBenjamin AT BUNNINGS.COM DOT AU]
> Sent: Sunday, July 07, 2002 9:23 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM DBBackup
>
> At the end of the day, sometimes it's easier to go to the same type of
> tape
> volume.
>
> For example, if you have a DR situation, you will need to source another
> library/tape drive
> if your DB exists on another form of tape volume. This is a very poor
> approach when time
> is of the essence in the recovery situation. Same goes if your secondary
> drive/library fails,
> you will need to start backing up to the LTO anyway, multiple points of
> failure.
>
> Secondly, the LTO will write the DB very quickly to tape and continue on
> it's merry way.
> You can also track these tapes with the same library, and rotate say 7
> dbbackups offsite and
> expire them for maximum safety, how cool is that?
>
> Cutting corners to save a couple of bucks makes no sense at all when the
> aim
> is the security
> of your data. A few hundred bucks of tape is worthwhile.......
>
> Mike.
>
> > -----Original Message-----
> > From: Bill Wheeler [SMTP:Bill.Wheeler AT LA-Z-BOY DOT COM]
> > Sent: Friday, July 05, 2002 10:22 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      TSM DBBackup
> >
> > Hello *SMers,
> >
> >
> >
> >             I have a couple of questions.  We are possible moving to an
> > LTO
> > drive in the near future.   I am trying to determine how to do a TSM
> > backup
> > without sending it to a separate cartridge.  Our DBbackup is small and
> do
> > not see a reason to use such a large cartridge, do anyone have an idea?
> >
> >
> >
> > Can it be sent to the same cartridge?
> >
> > Can I create a flat file and back that up?
> >
> >
> >
> >
> >
> > These are the few questions that I need an answer for, if any one could
> > help
> > me out.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Bill Wheeler
> >
> > PDM Administrator
> >
> > La-Z-Boy Incorporated
> >
> > (734) 242-1444 x 6170
> >
> > bill.wheeler AT la-z-boy DOT com <mailto:bill.wheeler AT la-z-boy DOT com>
>
> **************************************************************************
> Bunnings Legal Disclaimer:
>
> 1)      This document is confidential and may contain legally privileged
>         information. If you are not the intended recipient, you must not
> disclose or use the information contained in it. If you have
>         received this e-mail in error, please notify us immediately by
>         return email and delete the document.
>
> 2)      All e-mails sent to and sent from Bunnings Building Supplies are
>         scanned for content. Any material deemed to contain inappropriate
>         subject matter will be reported to the e-mail administrator of
>         all parties concerned.
>
> **************************************************************************

**************************************************************************
Bunnings Legal Disclaimer:

1)      This document is confidential and may contain legally privileged
        information. If you are not the intended recipient, you must not        
                                                disclose or use the information 
contained in it. If you have
        received this e-mail in error, please notify us immediately by
        return email and delete the document.

2)      All e-mails sent to and sent from Bunnings Building Supplies are
        scanned for content. Any material deemed to contain inappropriate
        subject matter will be reported to the e-mail administrator of
        all parties concerned.

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