To change the retention without running a new backup, the management class the files are bound to can be changed. (ie: change the retention period of inactive files for the management class the files were bound to). I believe that the management class still controls the expiration of the inactive files when the expiration runs to purge the ADSM database.
In extreme circustances, you can also 1. Create a backupset 2. Rename the nodename to nodename.old (the active versions will remain in active status because a client backup is never run to access this name and tell the server the files no longer exist). After re-register the old nodename and run a full backup. 3. Rename the filespace to filespace.old (same as above) Jeff > -----Original Message----- > From: Seay, Paul [SMTP:[EMAIL PROTECTED]] > Sent: Friday, February 01, 2002 9:28 AM > To: [EMAIL PROTECTED] > Subject: Re: URGENT: Rebinding > > This was discussed recently. Create a new management class and set it as > the default or put a management class definition in your incl/excl for > each > line and run the backup again. Remember it will not backup anything that > has already been backed up but it will rebind everything. If you would > like > to change the name back to the original management class then you will > have > to do it again, but it is pretty fast. Now, there is one caveat, any > deleted files will not be rebound. > > -----Original Message----- > From: Vazquez Vegas, Sergio [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 01, 2002 4:12 AM > To: [EMAIL PROTECTED] > Subject: URGENT: Rebinding > > > Hi people! > > I've done a very large backup from a node with a determined > Management Class. Is there any way to rebind all the files in that backup > to > another one? > I mean, can I change the retention of that backup without doing the backup > again? > > Thanks in advance > > Este mensaje de correo electr�nico y sus documentos adjuntos est�n > dirigidos > EXCLUSIVAMENTE a los destinatarios especificados. La informaci�n contenida > puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente > refleja la opini�n de ENDESA. Si usted recibe este mensaje por ERROR, por > favor comun�queselo inmediatamente al remitente y ELIM�NELO ya que usted > NO ESTA AUTORIZADO al uso, revelaci�n, distribuci�n, impresi�n o copia de > toda o alguna parte de la informaci�n contenida. Gracias. > > This e-mail message and any attached files are intended SOLELY for the > addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY > PRIVILEGED information and may not necessarily represent the opinion of > ENDESA. If you receive this message in ERROR, please immediately notify > the > sender and DELETE it since you ARE NOT AUTHORIZED to use, disclose, > distribute, print or copy all or part of the contained information. Thank > you. ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **********************************************************************
