This makes absolute sense because rebinding process is driven by a scan of the current filesystem image on the client and matching against the database. During that match if the management class does not match the active version management class everything is rebound not just the active backup.
-----Original Message----- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 23, 2002 4:46 PM To: [EMAIL PROTECTED] Subject: Re: Rebinding Just tested this to be sure. Inactive versions are rebound when the active version is rebound. But in the case where there is NO active version, the inactive versions won't be rebound at all. (These would be inactive backup versions of files that have been deleted from the client.) -----Original Message----- From: Jack Musselman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 23, 2002 2:48 PM To: [EMAIL PROTECTED] Subject: Re: Rebinding Jeff, I found an explanation for your question in the TSM Admin Guide for AIX, pages 244-250. In general, rebinding is done for backup versions if any of the following applies: 1. The user changes the management class specified in the include-exclude list and does a backup. 2. An admin activates a policy set in the same policy domain as the client node and the policy set does no contain a management class with the same name as the management class to which a file is currently bound. 3. An administrator assigns a client node to a different policy domain, and the active policy set in that policy domain does not have a management class with the same name. The inactive versions will be rebound to the associated management class of the next backup. Hope this helps. Jack Musselman -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Bach Sent: Wednesday, January 23, 2002 1:17 PM To: [EMAIL PROTECTED] Subject: Re: Rebinding Kelly, For active files, I have seen this is the case. I was not aware that after a file was marked inactive by the client that the inactive file was examined or changed by the client? What process on the server then would change the management class for inactive files? I am not indicating that it does or does not, but I would like to better understand this aspect or rebinding a management class. Jeff Bach > -----Original Message----- > From: Kelly Lipp [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, January 23, 2002 10:59 AM > To: [EMAIL PROTECTED] > Subject: Re: Rebinding > > Yes. > > Kelly J. Lipp > Storage Solutions Specialists, Inc. > PO Box 51313 > Colorado Springs, CO 80949 > [EMAIL PROTECTED] or [EMAIL PROTECTED] > www.storsol.com or www.storserver.com > (719)531-5926 > Fax: (240)539-7175 > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Gianni Garda > Sent: Wednesday, January 23, 2002 12:59 AM > To: [EMAIL PROTECTED] > Subject: Rebinding > > > Hello, > > I have a node associated to a policy domain named XXX with only one policy > set(active),one Mgmclass and a backup copy group with verexist=5 and > retextra=30. > If I update my node to a new policy domain YYY with same configuration but > with verexist=4 and retextra=90 and start a backup are my old backups > rebound to new mgmclass or not ? > > Thanks in advance > > ------------------------------------------ > Gianni Garda ********************************************************************** 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. **********************************************************************
