In this situation, DELETE BACKUP can also be used to delete individual
backup objects.
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2006-01-11
07:30:56:
> Perhaps I misunderstood Guenther's need, but I interpreted the scenario
> to be like this:
>
> 1. Files a, b, c are all created & backed up on day 1
> 2. File a gets deleted on day 5
> 3. File b gets deleted on day 25
> 4. File c gets deleted on day 49
>
> They want a, b, c all to expire from TSM on day 50, regardless of when
> they were deleted (which as far as I can see, can only be accomplished
> by using archive, leading to 15GBx50day=750GB stgpool). Of course,
> nowadays, 750GB is not that big a deal, so maybe this is an ok solution
> for them.
>
> Guenther - please correct as needed
>
> Steve Schaub
> Systems Engineer, WNI
> BlueCross BlueShield of Tennessee
> 423-752-6574 (desk)
> 423-785-7347 (cell)
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Andrew Raibeck
> Sent: Wednesday, January 11, 2006 8:38 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] A requirement ..
>
> Why won't these backup copygroup settings work?
>
> VEREXISTS=NOLIMIT
> VERDELETED=NOLIMIT
> RETEXTRA=50
> RETONLY=50
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
> Raibeck/Tucson/IBM@IBMUS Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorag
> eManager.html
>
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2006-01-11
> 01:00:12:
>
> > Hello *SMlers,
> >
> > yesterday i was faced with a requirement that i don't know how to
> > handle.
> >
> > We are in the need to back up a bunch of files (approx. between 5 and
> > 15 GBytes/day) for 50 days after hey where created on the underlying
> > file system.
> >
> > Problem: each file may stay for up to 50 days on the filesystem, may
> > be deleted after one day or something in between. The backed up file
> > in TSM has definitively to expire after 50 days.
> >
> > My first thought was to use archive instead of backup, but i am afraid
>
> > this would blow up the storage pool in terms of size.
> >
> > Any suggestions on this ?
> >
> > TIA
> >
> > regards Guenther
> >
> > --
> > Guenther Bergmann, Am Kreuzacker 10, 63150 Heusenstamm, Germany
> > Certified Service Manager Guenther_Bergmann at gbergmann dot de
> > http://www.gbergmann.de
> Please see the following link for the BlueCross BlueShield of Tennessee
E-mail
> disclaimer: http://www.bcbst.com/email_disclaimer.shtm
|
