We had started compact -a task on a server. The Archive setting is to copy document to archive and to leavy summary data to original database. Archiving is done on a basis for expiration date (archive documents that have been expired). We have been using and testing that in a test environment and everything worked and went fine. Of course the amount of documents to be archived was very small in the test environment.Now when using this in a real environment where over 70 000 documents should be archived (each of which have 1 to 10 Office attachments), archiving process started fine and server tasks showed that archiving is going on. After 36 hours now errors appeared but none of the documents were archived!
I have not found any documentation of this server based archiving how this should work. Should it be so that archiving process if it works fine archives documents in a way that you can immeadiately see if it is working or not? How fast this process is - how to estimate archiving time - what is reasonable and what is not? The database we are archiving from is very huge (over 60 GB) and we are reaching the maximum database size very soon.
I do not know what to do differently now to get this working. First step is to archive manually. Have some of you experience on this? I had also another question concerning compacting task - is it enought to use compact -a or should I use also compact -a -c -i?