Using Archive Profile Settings creates a New Archive? IS THIS A SETTING?

Is this a setting that I cannot find? We had users that already had archive databases… and we wanted to turn on profiles to bring them all under a consistent naming convention… so the existing ones we named appropriately… and when it came time to archive… the server created NEW archive databases on its own… WHY??? How do we turn this ‘feature’ off???

Ruth

Subject: Using Archive Profile Settings creates a New Archive??? IS THIS A SETTING?

Ruth, I answered you on other thread, I don’t know if this is the same trouble you mention on that your other post, but please keep just one thread for one trouble.

Subject: Creating new archives… ignoring existing one

No, Eduard… .this is a Different problem.the OTHER thread was asking about archiving ARCHIVES.

THIS thread is asking why the Server Archive feature, when turned on thru Profiels IGNORES the fact that the user already has an archive, and it creates a NEW ONE.

archive/msmith_a.nsf - Already exists

archive/msmith_a_a.nsf - NEW one made by archive routine.

??? Why

Subject: Using Archive Profile Settings creates a New Archive??? IS THIS A SETTING?

Same problem here. was it answered? I am an (unfortunate) end user not an adminstrator.

Also found that regular archive happens to a_username while archive of selected documents happens to a_a_username. So archivied docs are fragemted across two archvies.

Now when you open the two archoves (a_ and a_a_…), the folders can be given two separate names to distinguish. However, after opening they revert back to a common name. So there is no way to distinguish as NEW and OLD or by different names.

Subject: Using Archive Profile Settings creates a New Archive??? IS THIS A SETTING?

Are you running compact -a over the same folder that the archives are in?