Since database backups are not managed via management classes &
copygroups, and the only way to manage them is through the Delete
Volhist command, I don't see a way for you to do what you want.  Even
if you gave them seperate device classes, you would still have the same
problem.

It would be nice to be able to assign database backups to a management
class & copygroup, and have the ability to assign backups to different
classes.  To me, this would be more consistent with the way the rest of
the product works.  A new copygroup type of DBBACKUP could possibly do
the trick. This would allow you to take seperate backups and assign
each to a different management class.   This is only a wish and a
dream, I can't be held responsible if this is a ridiculosly bad idea.


Elvin Peterson