Vault store design and cab files
Dear Experts! Our customer is planning to introduce EV 12 with FSA archiving. He has 5 file servers and has approx 20 billion files. We can implement one EV server with an SQL database which is reside on the same host.Everything is virtual in that envionment.Veeam is the backup sw and we use the trigger file.Customer preference: file retrieval should be fast, backup of the EV server is the second thing. We are planning the Storage layout for the EV server. Our initial plan is: 1. One Vault store group 2. 5 Vault store, which is sharing level: share within a vault store For example: - Server01 Store1 - Server02 Store2 ... etc 3. Collections are not used on the VS 4. All data on the Ev server ntfs disk which has a big partition. (E: ) 5. The ntfs dedup or compression not using Questions: 1. What do you think, it is a good plan? What do you suggest? Please share your ideas. 2. Collection (CAB files) should we use or not? 3. How can we improve the overall perfomance? BR: Pal SzaboSolved1.1KViews0likes3CommentsVault store partition for a selected group of users
Hi Everybody, is there a way to use a Vault partition or partition group to store data only for a specified group of people ? for example, let's say you have vault store group 1 and group2 on vsg 1 mail of sales on vsg2 mail of logistics Is this possibile ? Thanks Mike623Views0likes2Comments