well, EmailXtract is a task based tool. You can archive (existing old data on the mail server or import PST-files), shortcut the files, etc. You would run it on pre-defined times and yes you could shortcut e.g. mails for 2004 only.
With "journaling", you receive a copy for each mail that was sent/received by the mail server (on Exchange it's configured for each information store). This is recommended for compliance since the users cannot change/delete the items until it's archived. Ingestion is also much quicker... and preferred by EMC. So journaling is just a method to ingest data. Shortcutting would still be done by EmailXtract with all the options available.
You would configure the storage for each EmailXtender server. You can't separate the storage location on one EX server for journaling (compliance partition) and old data (to another partition). So importing old data (e.g. from 2004) to a compliance partition, the retention will be 3 years shorter than a message archived today!
This is different for a feature called "user archived folders" (see installation or admin guide).
Hope, this helps to clarify (hopefully) some design questions you might have.
And I think we don't need journalling for EmailXtract tasks.
Infact, if I go by simple logics, on-line or real time archiving is also not required. You won't archive mails the same day when you receive them. So journalling is never required.
vladislav1
5 Posts
1
October 25th, 2007 23:00
Look in EX AdminGuide for EmailXtrack Task...
Hope this help !
Vladislav
amediratta
2 Intern
•
2K Posts
0
October 26th, 2007 11:00
jskoecher
2 Intern
•
204 Posts
1
October 26th, 2007 12:00
well, EmailXtract is a task based tool. You can archive (existing old data on the mail server or import PST-files), shortcut the files, etc. You would run it on pre-defined times and yes you could shortcut e.g. mails for 2004 only.
With "journaling", you receive a copy for each mail that was sent/received by the mail server (on Exchange it's configured for each information store). This is recommended for compliance since the users cannot change/delete the items until it's archived. Ingestion is also much quicker... and preferred by EMC. So journaling is just a method to ingest data. Shortcutting would still be done by EmailXtract with all the options available.
You would configure the storage for each EmailXtender server. You can't separate the storage location on one EX server for journaling (compliance partition) and old data (to another partition). So importing old data (e.g. from 2004) to a compliance partition, the retention will be 3 years shorter than a message archived today!
This is different for a feature called "user archived folders" (see installation or admin guide).
Hope, this helps to clarify (hopefully) some design questions you might have.
Best regards,
Jochen.
amediratta
2 Intern
•
2K Posts
0
October 28th, 2007 23:00
Infact, if I go by simple logics, on-line or real time archiving is also not required. You won't archive mails the same day when you receive them. So journalling is never required.
I am understand this correctly.