Thanks very much - it worked very well. One further question: Without doing another full backup, how can we change the management class of previously backed up objects? We need to reduce the size of a collocated copy pool but can't move the objects off the collocated pool because they are still bound to a class that specifies that pool and its predecessors. Consequently we have tapes in both our collocated and non-collacated copy pools with objects from the same node. We've tried doing a MOVE DATA tapevol STG=non-collocated-pool but it won't work. We assume this is because of the management class to which these objects are bound - hence my question.
Thanks for any help. -----Original Message----- From: Mark Stapleton [mailto:stapleto@;BERBEE.COM] Sent: Monday, 4 November 2002 9:57 AM To: [EMAIL PROTECTED] Subject: Re: Data rebinding to non-default management class. From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of David Fosdike > We created two new MCs in POLICYSET STANDARD > 1. STANDARD_NC to backup to diskpool DISKPOOL_NC > 2. STREAMING_NC to backup to sequential pool LTOPOOL_NC > > We validated the policyset and activated it. > > We scheduled a backup for a server which should have used the default MC - > no overrides were specified in DSM.OPT or in the client option set. It > started to rebind and then failed because there was no space in pool > LTOPOOL_NC. Unless you declare a DIRMC (directory management class), all directory entries will bind to the management class with the longest duration. If one of your new management classes has durations longer than your default mgmtclass, all directory entries will rebind to the new class. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
