EV Archiving

[andrewa]

We are a new customer deploying EV (ver 10) for file and email archiving.

We have noticed that the ingestion rate for files is very slow (max 100GB a day) and then once a file has been archived therd is a significant time delay - several days -  before the original file on the server is converted to the stub file.

When the archive process is being run, if EV does not complete an archive run within its allotted time, then the next day when the archiving process starts again, it reverts back to the start of the file server (where it has already archived the files) instead of carrying on from where it left off.

Has anyone else had similar experiences?

[RahulG]

Check the Vault store settings, If the vault store is set to" remove safety copies after backup " the stubs would not be created untill you take a backup of the Enterprise vault server. To be more specific you need to backup your vault store location and the indexes .

It might be that your backups are scheduled  to backup ev server weekly so the archvied files remain on the actual server untill the backup is done  for the ev server

[Maverik · Accepted solution]

Hi, 

As Rahul mentions, depending on Vault Store Backup settings, will affect when the items are converted to placeholder.  

In addition to that how are you measuring the ingestion rate/amount? How do your ingestion rate figures compare with the Enterprise Vault performance guide in comparison?  Are they well off the rate specified for hardware you have? 

EV has a checkpointing mechanisim so it should always start from the point it was at last, not from the beginning unless of course it got through everything.  

Have you logged a case with EV support with any of these concerns?