After contact IBM this morning we find out the problem:This is a 6.5.4 client issue. It’s not present on 6.53 and earlier version. It’s also fixed on Notes client 7
Workaround is create the archive database manually directly on the server (or create it on local and them replicate it to the archive folder on the server). No Hot fix available for 6.5.4.
I’ve just tested using client 6.5.3 and it works fine.
Excerpt from IBM response
Title:
Server-to-server Archive Initiated Using Notes 6.5.4 Client Creates the Archive on Client Instead of Server.
Product: Lotus Domino > Lotus Domino Server > Version 6.5.4
Platform: Platform Independent
Date: 05/31/2005
Doc Number: 1206402
Problem
You use a Notes client to archive from a local or server-based mail file to a server-based archive that has not yet been created. However, instead of creating the destination database on the archive server, it is created locally. You cannot access this local archive from within the source mail file because the archive profile is still pointing to the archive server. Any subsequent attempt to perform archiving overwrites this local database with a new instance and you lose any documents that were previously archived.
Earlier releases (6.5.1, 6.5.3) did not exhibit this behavior. If you configured your archive profile to archive to a server (and not local), and if the destination database did not exist, then it would be created.
Content
This issue was reported to Quality Engineering as SPR # JRAN6BG36W and is under investigation.
If the archive database has already been created, archiving works as expected. You can work around this issue by creating the archive database, either manually or by using compact -a, on the archive server.