On Jan 17,  4:45pm, Martha McConaghy wrote:
> Subject: Status update and question
> Here's my dilemma.  Once ADSM is back on its feet, we won't know what data
> has been lost due to the incompleteness of the database.  I suspect that
> just running new incrementals on each machine won't be adequate.  Files that
> have been flagged as having been backed up before the head-crash will not
> get backed up again, even though the server copy no longer exists.  Is this
> true?  How does ADSM flag a file as being ready for backup?  We are using
> OS/2 clients and the VM server.
  Just perform another incremental backup. It will rebackup any file which has
been removed at the server during audit.  ADSM "flags" a file for back based on
a number of criteria, the primary being whether or not it already exists on the
server.  Others being whether or not the file has changed since last backup and
a number of other management class criteria.

>
> I would like to be able to re-back up those files that have been lost (or are
> new) without forcing a full backup on each machine.  I thought about doing
> this by comparing the files on the hard drive with the list ADSM maintains
> (QUERY BACKUP) and turning on the attribute for those files that do not
> appear on the latter.  Any other ideas?
  That would be a bit of work, just do the incremental.  OS/2 has an archive
bit on each file that can be disabled and which gets reenabled by OS/2 after
the file is changed. ADSM does not use nor modify that archive bit.

> Martha
Stefan Steiner
Member of the ADSM client team
ssteiner AT almaden.ibm DOT com