I have a question regarding safety copies and pending state. The EV configuration I am working with is Version 8 SP3. The SAN that EV is on is not backed up (ridiculous I know), so there will never be the situation to delete safety copies after backup. However, the safety copies are configured to "Remove safety copies After Backup".
Logic tells me that this should probably be set to "Immediately after archive" as there is no backup.
We are also having issues with some users trying to vault mail and having the "stuck in pending" issue. This usually happens with the user manually vaulting a message. Can I assume that changing the safety copies setting might help us to remove this issue?
Firstly, what are you buying EV for? Mailbox management for end users or compliance? Because not backing it up will be disastrous, cos it's not a matter of if you have a DR but when you will have one
That being said, you are correct in your thinking
I wrote more about backups and safety copies here
http://98.129.119.162/connect/articles/changes-backup-procedures-enterprise-vault-8
Firstly, what are you buying EV for? Mailbox management for end users or compliance? Because not backing it up will be disastrous, cos it's not a matter of if you have a DR but when you will have one
That being said, you are correct in your thinking
I wrote more about backups and safety copies here
http://98.129.119.162/connect/articles/changes-backup-procedures-enterprise-vault-8
Moving forward you (in your unique situation) you should set it to remove immediately, however you would need to reset the A attribute on all the older placeholders (attrib -a /s)
I believe EV 8 started to track backups even with this setting so you may want to consider using a trigger file to clear this down too.
Trigger file TN:
http://www.symantec.com/docs/TECH35610
That said if the SAN goes bang your EV data is gone forever, which is terribad
Yup you're correct, if you have immediately after archive, by default EV will still add items to the watchfile table and await for items to be backed up, so you can either use the trigger file and have it scan the partition every so often or you can change a database column in the directory database, it's all in the article I posted
