Hello Again!
I'm looking to get some more information about your experience with the Enterprise Vault collector that creates CAB files, I haven't used it before and I wanted to get some feedback on what you guys have been seeing.
Some background information:
For better or for worse, we moved our Enterprise Vault(11) environment to a Data Domain (DD2500). We're getting reasonable performance from a recall performance perspective right now, but our backup speeds aren't great at all. (200MB/Minute on average) We're thinking that switching to the CAB files might really help the backup situation, but we're worried about the possible performance penalty for accessing the CAB files down the line.
If anybody can throw in their two cents about using CAB files and answer some or all of these questions, that would extremely helpful!
1. Does anybody have any "best practice" guidelines on how large the collection file size should be? I know the default is 10MB, but I want to know if people have had any luck with other values and the tradeoff between backup performance and retrieving archived files.
2. After selecting the "Use collection files" checkbox on a vault store (our vault stores are ~800GB in size), should I worry about the data being unaccessible during the collection process? I'm totally okay with it taking a long time for the collection process to complete, but I want to be sure that the data will be generally accessible during the collection process. If anybody has ballpark figures for how long their collection process took, that would be helpful as well.
3. Did anybody see a dramatic improvement in backup times after switching to a CAB file setup? I've seen some symantec blogs that cite up to 33% improvement, but I'd love to get some additional feedback from others.
4. Has anybody switched to CAB files and noticed any noticeable performance degredation in rehydrating archived files?
Thanks in advance for all of your help!
Adam