Hi David, You should use:
include.systemstate all <managementclassname> where <managementclassname> is the name of the desired management class. New backup objects will appear bound to the specified management class. Older objects will still show up as bound to the older class, but the system state as a whole will be managed to the new management class criteria. Best regards, - Andy ____________________________________________________________________________ Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | [email protected] IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home "ADSM: Dist Stor Manager" <[email protected]> wrote on 2014-08-28 12:06:26: > From: David Ehresman <[email protected]> > To: [email protected] > Date: 2014-08-28 12:08 > Subject: Systemstate backups > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > Are systemstate backups always bound to the default management class? > > I added a "include * mgmclass" statement to my client options. As > expected, on the next backup the files were rebound to the new > mgmclass. But all of the systemstate entries in the backup table > (select ... from backups) still show the class_name as DEFAULT not MGMCLASS. > > David Ehresman >
