Hello Grant,

from the readme.old file:

======================== cut =============================

ADSM Version 3 clients can restore or retrieve data backed up or archived
by Version 2 clients.  However, Version 2 clients cannot access data backed
up or  archived by a Version 3 client, regardless of the ADSM server
version.  This is because Version 3 backup-archive clients store files with
different attributes than previous version clients.

After installing a Windows-32 bit Version 3 client where a Version 2 client
was used, ADSM will update the attributes only (not data) for all of the
client's active files on the ADSM server during the first incremental
backup or archive.  A Version 2 client will not be able to access any
active files after this attribute update.
======================== cut =============================

and....

======================== cut =============================

ADSM incremental backups and attribute updates

When file meta-data changes but the file itself does not, ADSM may do an
attribute update instead of another full file backup. On UNIX, for example,
if only the access permissions are changed on a file that has already been
backed up, then on the next incremental backup, only the file's attributes
are updated on the ADSM server. The file data is not backed up again.  On
the client doing the incremental, the message for a file backup is:

Incremental backup of volume '/home/test'
Normal File-->                97 /home/test/file1 [Sent]

On an attribute update, the message is:

Incremental backup of volume '/home/test'
Updating-->                   97 /home/test/file1 [Sent]

In the attribute update case, the active copy of this file is left active,
and the insertion date is not changed.  The benefit of this is that another
copy of the data is neither transmitted to nor stored in a storage pool,
saving network and storage resources.

The "original" meta-data associated with this file (as of the insertion
date), however, are gone.  The "new" meta-data are associated with the
active copy and are locked to this copy when the file goes inactive. A
point-in-time restore or a pick option will use the "new" meta-data. Use a
selective backup or an absolute incremental backup to transmit the file
data to a new active copy and change the insertion date when only the file
meta-data changes.

======================== cut =============================

CU/2,
                Dirk Billerbeck


Dirk Billerbeck
CompuNet Kiel
Network and Systems Management
Am Jaegersberg 20, 24161 Altenholz (Kiel), Germany
Phone: ++49-431/3609-117, Fax: ++49-431/3609-190,
Internet: dirk.billerbeck @ gecits-eu.com




Grant.Cohn AT SAPREF DOT COM on 09.07.99 06:41:39

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:     mailbox.dekelnsm
cc:
Subject:  UPDATING in dsmsched.log.........


 -------------------------------------------------------------------------





Good morning all
We have recently upgraded our ADSM clients from V2 to V3.1.0.3.
Can anyone tell me what the meaning of 'UPDATING..........' is in the
dsmsched.log on our NT clients.
Server is on AIX (4.1.5) Version 3.1.2.20

Many thanks

Grant Cohn
Shell & BP Petroleum Refinery
Prospecton
DURBAN
South Africa