Joshua,
Thanks for the reply. Your explanation is pretty much in line with what I got
from the developers, which is:
Notes agent first check if the database has ever been backup before from a query
to the ADSM server. If the ADSM query failed (means never backup before), then
everything in the database will be backup (timestamp is not checked). After the
initial backup, the backup time will be saved on the ADSM server. During the
next backup, this time the query from the ADSM succeeded since this database has
been backup before and returns the last backup timestamp from the ADSM server.
Notes agent will use this timestamp to query the database to find out which
documents/forms/views has modified (based on modification timestamp) since the
last backup. Lotus Notes API function will use this timestamp and find out a
list of modified documents. Notes agent will then backup this list of ducuments.
This works for almost everything except folders because Lotus doesn't update the
modification timestamp for the folders when the folders are modified. This is a
known problem to Lotus.
So, what I figure is happening is
Night 1, server prod is backed up using Arcserve
Night 2, server prod is backed up using Arcserve and server test is restored
from Night 1's backup. Therefore, the timestamp on ADSM is from Night 2.
Night 3, server test is restored from Night 2's backup. Therefore, the date/time
of the documents on server test is pretty close to the timestamp on the ADSM
server.
Therefore, no backups take place.
Now, I have to figure out how I can work around this, especially since it
appears that the timestamp is being generated on the ADSM server itself, and not
passed up from the client, which means I can't simply roll back the time on the
test machine :-(
Any more help/insights would be greatly appreciated.
Dan Giles
Application Specialist
Manulife Financial, Corporate
Phone: 416-341-7500 x7597 Fax: 416-341-7600
From: Joshua Bassi <jbassi AT GLORYWORKS DOT COM> on 99/03/31 04:07 PM GMT
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: ADSM)
Subject: Re: Attempting to Test Notes Agent
Dan,
I would like to premise this reply with the fact that I am not a Notes guru.
I have worked with many Notes administrators/architects who enlightened me
on the way Notes maintains it's own document versioning though, and we
seemed to have pounded our way through understanding how the notes agent
performs it's backup.
Each document in a notes database has it's own versioning number. So that
when notes replication occurs notes knows which docs are the most recent and
then pushes those out to the replica servers. Each document also has an
internal ctime & mtime. When the ADSM notes agent performs an incremental
backup of a database, I believe that it is looking at those times to verify
where it has the latest version or not.
So as many of us have seen, when we perform a dsmnotes incr type=full, and
when more data is being sent to the client than the server, it is running
thought all the documents in the db comparing what it has in server storage
with what is in the database now. As many of us know, this shouldn't be
happening to the extent that it does; hopefully the notes agent developer
who is monitoring this list will continue to improve upon this "feature" :-)
----------------------------------------------------------------------
Joshua Bassi E-mail: jbassi AT gloryworks DOT com
Joshua Bassi E-mail: jbassi AT gloryworks DOT com
Storage Management Team Lead VM/Pager: (972) 680-6247
Dickens Services Group Internet: www.teamdsg.com
----------------------------------------------------------------------
-----Original Message-----
|
