More info on my problem:
Once the files are deleted by the application and an incremental backup runs,
the backup become inactive. The only backup is now inactive. How can I get it
to rebind to a new management class?
Sue
___________________________________________________________________________________________________
ADSM-L AT VM.MARIST DOT EDU on 01/27/98 02:22:24 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ Internet
To: ADSM-L AT VM.MARIST DOT EDU @ Internet
cc:
Subject: Re: Rebinding Inactive Versions - ADSM V2.1.5.12
Sue,
If the file backed has a different name everytime ADSM backup will in turn
only have active backup versions for each one of those files. Every file is
seen as a different one. That explains why your changed mgmtclass did not
cause a rebind of the inactive files. You're are not performing versioning
for these files. If you inadvertently speak of ARCHIVING here then that
behaves correctly as rebinding only happens for backup versions.
Regards
Campbell Esplin
Excalibur Business Solutions
----------
> From: Sue Tull (email: suetull AT smed DOT com) <Sue.Tull AT SMED DOT COM>
> From: Sue Tull (email: suetull AT smed DOT com) <Sue.Tull AT SMED DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Rebinding Inactive Versions - ADSM V2.1.5.12
> Date: Tuesday, January 27, 1998 12:54 AM
>
> I have an application that backs up Sybase databases using Sybase's
tools. The
> backups are written to disk, with the date and timestamp in the file
name. The
> backup files are backed up by ADSM, and then deleted by the application
the
> next night. When the next incremental backup runs, the backups are
marked as
> inactive. I implemented a new management class for these backups, but
the
> inactive backups (since there is no active copy) did not rebind to the
new
> management class. Do I have to create a new file with the same name,
back it
> up and then delete it, to force the inactive version to rebind to the new
> management class?
>
> Sue Tull
> SMS
> sue.tull AT smed DOT com
>
>
>
> *
*
|
