If you think about the agent as you do the normal backup/archive client, this
does make sense. If you restore an inactive file us the b/a client (which is
what you are doing when you lay down the full LN database), then restoring all
active files on top will not re-delete the files that are "supposed" to be
deleted. I don't think you would really want the agent to say "hey, this file
ain't supposed to be here" and then delete it!
As for your second item, this is noted in the documentation. Restored items are
marked as unread so that you can tell what has been restored. This is actually
handy since you cannot select specific documents to restore, only a time range.
Hope this helps.
From: Trevor Foley <Trevor.Foley AT BANKERSTRUST.COM DOT AU> on 02/24/98 10:30
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: ADSMconnect Agent for Lotus Notes on WindowsNT
Hi,
We've been doing some testing of the Lotus Notes Agent on NT and have
come across two issues and I am wanting to find out if we are doing
something wrong, or these are limitations with the current version.
Our intended strategy is to do file level backups weekly, and daily
Notes Agent incremental backups. We performed the following test.
1. Backup database (mail file) with ADSM backup/archive client
2. Created some new folders, moved some documents into those
folders, deleted some documents, marked some previously read documents
as unread and created some new documents
3. Performed an incremental backup of the database with the Notes
Agent
4. Deleted the database
5. Restore the database using the backup/archive client
6. Rebuilt the database using the Notes Agent gui to bring it up to
date
Everything worked as expected except for:
1. Documents that were deleted in step 2 reappeared after step 6.
It appears that the Agent is not correctly handling deleted documents
2. All documents were unread after step 6
thanks,
Trevor
|
