NetGovern Archive 6.x
In some cases, NetGovern Support engineers may apply a <fastprelude> tag to the jobs via an LDAP browser. This can result in performance benefits, but with some caveats. This article will attempt to explain this parameter in more depth.
Without the <fastprelude> parameter the software will function as follows:
By enabling the <fastprelude> option on the job the software will function as follows:
As you can see from the above, the speed-up is gained from:
<fastprelude> may not be wise in every situation. Let's examine cases where this safe to use and where it's not.
|Open to using <fastprelude>||NOT recommended for <fastprelude>|
|Using en-US culture on all your mailboxes||Mailbox culture is international (not always en-US)|
|On a recent version of Exchange (2010 SP1+)||On version of Exchange 2010 pre-SP1|
|Archive, LiveMail indexing, and (usually) Remediation jobs||Migration jobs|
|Job has a little data to process (eg. daily incremental archive)||Job has a lot of data to process (eg. initial archive of a mailbox)|
Assuming your scenario does not meet any condition in the 2nd column (above), then it's probably safe to use the <fastprelude> tag.
If there is end-user access to the archives via OWA in your environment, there must be at least one archive job that runs without the <fastprelude> parameter. This is because OWA access to the archives is done via inbox folder ID, which is fetched via Powershell during the beginning of the archive job. If all archive jobs implement the <fastprelude> parameter then this information is never populated in LDAP, and thus the users will not receive an archive link in OWA.
The <fastprelude> tag is applied by inserting the tag into the maParameters of the relevant job in LDAP. Values for this tag can either true or false.
The tag is implemented at the connector level, so all jobs which leverage EWS to connect to the mailbox are eligible for this tag.