On Tue, 2 Mar 2004, Mike Bantz wrote:

> I believe that's the fix - ran an incr right after I changed that to a
> single * and it applied the new DBDUMPS mgt class. But from your email, it
> would seem that "all existing backup versions will be rebound to the DBDUMPS
> management class". However, I just ran that incr, and opening up the BA GUI
> shows that all previous dumps are bound to the DEFAULT mgt class.
>
> Mostly, I just don't want those 30+ copies of a 15gig database sitting out
> there on tape taking up room if they don't need to be...

I've found that if there's not an active version of a given file when the
'rebinding' backup runs, then the inactive version(s) of that file are not
rebound.  To rebind those, you have to create on the client's hard drive a
tiny dummy version of the file with the same name as the inactive
version(s), run the incremental backup, then get rid of the dummy version.

The 'q b -ina' command can be useful for building a list of the files you
need to fiddle with in this manner.

Hope this helps,
Bill

Bill Kelly
Auburn University OIT
334-844-9917