ADSM-L

Re: TSM DB backup question

2006-04-06 14:35:05
Subject: Re: TSM DB backup question
From: Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 6 Apr 2006 14:31:21 -0400
Is the DB backup of any use after the next db backup is taken. The data
on the volumes changes, and data is expired and tapes reclaimed...so
what is the value of older db backups?

We back up the db to disk and ftp a copy over to a remote site.

Our backup data is kept in one tape library and the copypool in a
separate library, both at separate sites. So if our main site has a
fire, the backup data is available from the separate site. If that
backup site has a fire, the copypool in the main site can be used to
recreate the backup storage pools.



>>> rajeshoak AT LYCOS DOT COM 04/06/2006 2:05:53 PM >>>
For our local sites we vault daily, i.e we send copypool tapes to the
vault daily. For our remote sites since we do not any local vault
person, we have a contract with a company and the copypool tapes are
sent to the vault once a week.
The DR tapes should be sent evry day if possible else in case of a real
disaster you would lose over a weeks data if you send DR tapes once a
week.

Rajesh

> ----- Original Message -----
> From: "Vats.Ashok" <Ashok.Vats AT FTB.CA DOT GOV>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM DB backup question
> Date:         Wed, 5 Apr 2006 14:25:06 -0700
>
>
> hi Rajesh,
> WHat do you mean by not vault daily ? We send DR tapes once a week.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
Of
> Rajesh Oak
> Sent: Wednesday, April 05, 2006 2:20 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TSM DB backup question
>
>
> Ashok,
> For our remote sites where we have a small library and do not vault
> everyday, we backup the database to disk. You have to be a little
> careful here because with your 161 DB database you would need a lot
> of diskspace to keep the db backup for a number of days.
> The device class has to be file and you have to make the size big
> enough when you define it.
>
> Let me know if you have any issues.
>
> Rajesh
>
> > ----- Original Message -----
> > From: "Remeta, Mark" <MRemeta AT SELIGMANDATA DOT COM>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: TSM DB backup question
> > Date:         Wed, 5 Apr 2006 14:05:28 -0400
> >
> >
> > The other factor to consider is that you should have the delay
period for
> > volume reuse on your tape storage pools set equal to the length of
time you
> > keep your database backups. Depending on how often you perform
reclamation
> > of those pools, these could add up too!
> >
> > Mark
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
Behalf Of
> > Prather, Wanda
> > Sent: Wednesday, April 05, 2006 1:53 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: TSM DB backup question
> >
> >
> > The factor to decide:
> >
> > If you somehow had a TSM data base crash, or corruption in the TSM
data
> > base, how far would you be willing to restore your data base
backwards
> > in time?
> >
> > If you think you would never use that 30 day old TSM DB backup,
you
> > don't need to keep it.
> > I think a DB retention of 5-10 days is more common.
> >
> > And no, you can't put the TSM DB backups in a storage pool.
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of
> > Vats.Ashok
> > Sent: Wednesday, April 05, 2006 1:39 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: TSM DB backup question
> >
> >
> > Hi List,
> > We have tsm 5.3.00 on AIX. We run TSM database backup which runs
once /
> > every day  consumes media from scratch pool. We keep these backups
for
> > at least 30 days. consuming almost 30 *200 GB tape media. Our data
base
> > is about 161 GB so my question is can we reduce the retention time
of
> > TSM db backup to 7 days. I am not sure what are the factors which
> > decides how long we need to keep these volumes around. Also Does
anybody
> > have a storage pool defined for TSM DB backups. is it possible to
do
> > that ?
> >
> > Thanks,
> > Ashok
> >
> > Confidentiality Note: The information transmitted is intended only
for the
> > person or entity to whom or which it is addressed and may contain
> > confidential and/or privileged material. Any review,
retransmission,
> > dissemination or other use of this information by persons or
entities other
> > than the intended recipient is prohibited. If you receive this in
error,
> > please delete this material immediately.
> > Please be advised that someone other than the intended recipients,
including
> > a third-party in the Seligman organization and government agencies,
may
> > review all electronic communications to and from this address.
>
> >
>
>
> --
> _______________________________________________
>
> Search for businesses by name, location, or phone number.  -Lycos
Yellow Pages
>
>
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10


>


--
_______________________________________________

Search for businesses by name, location, or phone number.  -Lycos
Yellow Pages

http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10


The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain information that is confidential, privileged, and/or otherwise exempt 
from disclosure under applicable law.  If this electronic message is from an 
attorney or someone in the Legal Department, it may also contain confidential 
attorney-client communications which may be privileged and protected from 
disclosure.  If you are not the intended recipient, be advised that you have 
received this message in error and that any use, dissemination, forwarding, 
printing, or copying is strictly prohibited.  Please notify the New York State 
Thruway Authority immediately by either responding to this e-mail or calling 
(518) 436-2700, and destroy all copies of this message and any attachments.

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