Archiving: documents are not copyied to archive database

Hello:

I’ve “archiving enabled” on my database and 6 month ago everything worked perfectly.

Archive options are:

  1. archiving will be performed on the server;

  2. documents in a certain view have to be copied to the archive database;

  3. in the original database, the size of the documents has to be reduced.

The numbers 1 and 3 are working perfectly but the documents aren’t copied to the archive database. Six month ago it did work! I already tried to change the archive database but still the documents to be archived are truncated in the original database but NOT copied to the archive database.

Has anybody an idea? Has it something to do with the ACL?

Thanks for your time and hopelfully I get som response.

els.verberne@arv-group.com

Subject: archiving: documents are not copyied to archive database

Recently happened to me too with server based archiving, target archive created on a different server. This was a different scenario, however. It was a first time attempt to get an archive of a large file.

The first night that compact -a was run, and the Select Documents to archive “Last Modified” archive parameter was set to 2 yrs, nothing was archived. There are documents going back well over 2 years in the source db. The “Last Modified” archive profile was then set to 1 year and the second night’s compact -a ran, and evidently deleted about 10 times more documents than it copied to the target archive. No errors were logged, the archive log cheerfully reported 300,000 records deleted and 20,000 records copied.

I am wondering if it’s dangerous to change the Select Documents setting between runs, especially when 2 servers are involved. Maybe they got mixed up about which documents were being archived.

Lotus - why is there not some sort of warning about fewer documents copied than deleted?

Subject: RE: archiving: documents are not copyied to archive database

This just happened to me too. Archive db is on the same server. First time I have used this feature, it deleted some 68,000 documents, but only archived 2600! Lucky it was only a test db. Anyone know why this happens?

Subject: RE: archiving: documents are not copyied to archive database

The only clue - not a sensible explanation - I have found is about the Advanced “do not delete documents that have responses” setting. Seems it has unintuitive effects. However, I’m not using that - I am using the document selection by view option.

I’ve also seen references to the mail archiving policies being out of synch with the individual db settings for mail files, but I am not using this for messaging files, it’s for application files.