Hi Andrew.

Thanks. Luckily RETEXTRA is only 30 days while RETONLY is 5000. But I guess
I could have set RETONLY for the new mgmt class lower than RETEXTRA with no
consequence right? Never done that before.

Regards,

Hans Chr.

On Tue, Nov 22, 2016 at 1:51 PM, Andrew Raibeck <stor...@us.ibm.com> wrote:

> Hello Hans,
>
> Before moving the directory OLD to NEW, you can:
>
> 1. Create a new (special) management class for OLD that is similar to the
> current management class, but has the desired RETONLY setting (for example,
> maybe it should match RETEXTRA?)
>
> 2. Add an INCLUDE statement to bind all files in OLD to the new management
> class
>
> 3. Next incremental backup will rebind all files in OLD to the new
> management class that has the lower RETONLY setting
>
> Best regards,
>
> Andy
>
> ____________________________________________________________
> ________________
>
> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
>
> IBM Tivoli Storage Manager links:
> Product support:
> https://www.ibm.com/support/entry/portal/product/tivoli/
> tivoli_storage_manager
>
> Online documentation:
> http://www.ibm.com/support/knowledgecenter/SSGSG7/
> landing/welcome_ssgsg7.html
>
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2016-11-22
> 05:38:38:
>
> > From: Hans Christian Riksheim <bull...@gmail.com>
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2016-11-22 05:39
> > Subject: Rename directory
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
> >
> > A customer wants to move a lot of data from directory OLD to NEW. A new
> > incremental will then backup all files under NEW and the files under OLD
> > deactivated.This will then cause the former active files under OLD to
> stay
> > on tape until RETONLY effectively doubling the cost for the customer.
> >
> > Any method to get rid of the active backup data under OLD while still.
> >
> > 1. Keeping the other inactive versions.
> > 2. Not deleting the Active date before the move which is a risky
> solution.
> >
> > Regards,
> >
> > Hans Chr.
> >
>

Reply via email to