Greetings,
We are currently testing EVault for Exchange archiving.
I archived a user's entire mailbox by creating a policy that is based upon age only...and selecting 0 days old for archiving. The archive tasks ran fine...and archived the entire mailbox successfuly.
Since this was a test, I then proceeded to delete the just created archive via the admin GUI.
I disabled the mailbox...then re-enabled the mailbox...thus creating a new empty EVault archive. I then re-ran the archive task for this one user...however, even though the original archive was deleted normally....it now only archives new items.
Running a DTrace revealed that the other itmes were not being selected for archive becasue they have "not been modified"....here are my questions:
1) What is EVault comparing with the Exchange mailbox item's modified date to make the decision that the item has not changed. It wiould seem to me that when an archive is deleted...all of its archived content would also be deleted from EVault's data tables...thus, it would not be aware of an existing archive date for these items.
2) What can be done to override this inherit logic and force a re-archive of the entire mailbox contents? I have tried setting the IgnoreEVDates registry value to 3 without success.
Any help would be appreciated. This just seems too difficult for a relatively easy operation. I'm sure I am not the first user to test the product by archiving something...deleting the test archive...and then want to re-archive the same content in production.
Thanks,
Dr Gary
