05-06-2012 10:10 AM
Is it OK to export Compliance/Discovery Accelerator searches directly to a network share? I seem to remember reading that best practice is to export to local disk. Is there any issues doing this? e.g. is the export just a bit slower?
Thanks
Solved! Go to Solution.
05-06-2012 10:18 AM
I think the reason is because of performance
DA will export the item to an MSG File then after all the MSG files have been exported, it will put them in to a PST File.....
So what happens is you just end up utilizing a lot network resources , you just get these extra hops
1. EV Server -> DA Server memory or Temp location (Dependant on size)
2. DA Server Memory -> export location
3. Export Location -> DA Server memory/disk to put in to a pst file
4. DA Server -> Export location
So you could infact be using 300-400% more than necessary bandwidth to do the export
Plus you then have things such as Virus Scanners that could intefere with the export, so if its on local disk, you can pretty much control what scans the location on the disk, but on a network share, any number of processes, servers etc could be scanning.
Also you then have to make sure that things like DisableOpsLocks and other opportunistic locking mechanisms are disabled etc
05-06-2012 10:18 AM
I think the reason is because of performance
DA will export the item to an MSG File then after all the MSG files have been exported, it will put them in to a PST File.....
So what happens is you just end up utilizing a lot network resources , you just get these extra hops
1. EV Server -> DA Server memory or Temp location (Dependant on size)
2. DA Server Memory -> export location
3. Export Location -> DA Server memory/disk to put in to a pst file
4. DA Server -> Export location
So you could infact be using 300-400% more than necessary bandwidth to do the export
Plus you then have things such as Virus Scanners that could intefere with the export, so if its on local disk, you can pretty much control what scans the location on the disk, but on a network share, any number of processes, servers etc could be scanning.
Also you then have to make sure that things like DisableOpsLocks and other opportunistic locking mechanisms are disabled etc