Hi Jeff,

ADSM does not update the archive attribute during backup. I
just tested this myself by creating a small directory,
E:\TestDir. I populated the directory with 4 files. For two
of those files I turned off the archive attribute. For the
other two, I turned on the archive attribute. I then did an
incremental backup of my E: drive, then checked the files.
The archive attributes had not changed from what I had set
them to originally.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

Sean

We have Quota Advisor as well and I'm wondering if it is to blame for some
of
our NT slow performers.  ADSM really does the archive bit update during a
backup
eh?  What do you plan to do as a permanent fix?

Thanks,

Jeff Connor
Niagara Mohawk Power Corp






Sean Stecker <Stecker.Sean AT ORBITAL-LSG DOT COM> on 03/09/99 06:37:57 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Jeffrey P Connor/IT/NMPC)
Subject:  You learn something new everyday.




All,

For reference only!!!

Thank you for the many responses to my questions of performance and
clustering
issues.  Allow me to shed some light as to why all of this created so many
problems.

On our Cluster, we have some third party software installed from W. Quinn
Associates called Quota Advisor.  Allowing us to set restrictions on our
users
home directories. This only interferes with write operations.  This
software was
creating problems with our Internet Information Server installation.  It
was
decided to uninstall Quota Advisor.  Then we thought, well.... maybe.  So
we ran
another incremental on our R: drive (the problem drive if you've been
taking
notes).  And to what do my wondering eyes should appear?  A backup.
Normal.
Speedy.  It took approximately 6 hours to back up 31.48 Gb.  This is on a
production server, during peak hours. Not bad.  We have 75 Gb total on the
drive,  some of which had already been backed up.

So why then, if the disk quota software only interferes with write
operations,
does it slow down ADSM?  Because as most all backup solutions do,  ADSM
writes
an archive bit to the data that has been backed up.  There you have it.  No
 more
interference, no more painstaking performance bottlenecks.  All told,
681,000
files. ADSM handled the amount of files and data beautifully.  Now if we
could
just get this stuff to be cluster aware, we would be smokin.  Oh well,
right
now I'm pretty happy.  Thanks again for everyone's information and
suggestions.
Have a great day.

Sincerely,

Sean M. Stecker
stecker.sean AT orbital-lsg DOT com