Re: Mitigating Risk with TSM's incremental backups

2002-01-27 Thread Steve Roder
. > -Original Message- > From: Steve Roder [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 26, 2002 7:22 PM > To: [EMAIL PROTECTED] > Subject: Re: Mitigating Risk with TSM's incremental backups > > > > That tells me what is coming back soon. You can get

Re: Mitigating Risk with TSM's incremental backups

2002-01-26 Thread Seay, Paul
Justin, We are in the same boat as you, more or less. We want to use a cycle retention that the courier can support and reclaim the tapes coming backup. I posted an example of how to do this about a week ago, but probably did not garner much respect because it seems like a really dumb thing to do

Re: Mitigating Risk with TSM's incremental backups

2002-01-26 Thread Seay, Paul
Risk with TSM's incremental backups > That tells me what is coming back soon. You can get elaborate and select > only the volume name and pipe the stuff into the commands necessary to issue > the commands dynamically, but I just do them manually right now. We are > heading down t

Re: Mitigating Risk with TSM's incremental backups

2002-01-26 Thread Steve Roder
> That tells me what is coming back soon. You can get elaborate and select > only the volume name and pipe the stuff into the commands necessary to issue > the commands dynamically, but I just do them manually right now. We are > heading down the automated path soon. > > The command that I use t

Re: Mitigating Risk with TSM's incremental backups

2002-01-25 Thread Zlatko Krastev/ACIT
ot; <[EMAIL PROTECTED]> on 24.01.2002 16:32:06 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Re: Mitigating Risk with TSM's incremental backups I'd suggest using TSM to back the data up to LTO, then back

Re: Mitigating Risk with TSM's incremental backups

2002-01-25 Thread Zlatko Krastev/ACIT
Do not forget about DB backup sent off-site. Most probably you are moving them but did not mentioned. The reusedelay and DB backup retension should set that only after a DB backup with information about the new volume where data is copied as result of copy pool reclamation the old reclaimed tape c

Re: Mitigating Risk with TSM's incremental backups

2002-01-24 Thread Kelly Lipp
: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Kauffman, Tom Sent: Thursday, January 24, 2002 7:32 AM To: [EMAIL PROTECTED] Subject: Re: Mitigating Risk with TSM's incremental backups I'd suggest using TSM to back the data

Re: Mitigating Risk with TSM's incremental backups

2002-01-24 Thread Bill Mansfield
Justin, TSM isn't really designed for a regular offsite rotation. The intention is to send the copy storagepool tape offsite each day, regardless of how full it is. You then perform offsite reclamation, which uses primary storage pool tapes (or optical) to recombine the data from several partial

Re: Mitigating Risk with TSM's incremental backups

2002-01-24 Thread Kauffman, Tom
I'd suggest using TSM to back the data up to LTO, then back up the LTO storage pool to a copy pool and send the copies off-site. Run reclaims and only bring back empty or pending empty off-site tapes. My worst case sends off a tape that is 5% full daily. The reclaim actually kicks in just after th