Mark, Data Protection for SQL does not support ARCHIVE. It only supports BACKUP.
You can use a second NODENAME like you suggested.... or... you can also look into using SET type backups which get a unique name and can be bound to a separate management class. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 06/29/2004 12:24:56 PM: > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of Moses Show > >Have been asked to backup SQL servers daily using TSM . The > >details and instructions for how these backups are performed and any > >characteristics are contained in the respective management class of the > >policy set in the policy domain. I also need to backup these servers at > >monthend and some every five weeks. What I am trying to find > >out is if it > >is possible to have more than one backup copygroup under this > >management > >class. The reason is because the period backups will have different > >retention times to the dailys and possibly different retain > >only version values. > > > >Is it feasible to create two separate backup copygroups to > >manage this ? > >If so how would you get the server to differentiate between if > >a backup is run daily or at the end of periods. > > No, you can't have multiple active copygroups for a given management > class. What you'll need to do is create a second nodename (with its > corresponding option file which points at a non-default management > class). > > However, you might want to consider short-term archives of data, rather > than backups. With that, you can use the ARCHMC flag to control archive > destinations and retention. > > -- > Mark Stapleton
