Restore all items
We are moving to Exchange online in a few months. We currently archive from Exch2016 without shortcuts, on EV 12.5.1. The plan was to disable the users for archiving, and export a users archive back to their orginal mailbox, then migrate to the cloud. Any concerns with that approach? A user had a question, if they move items from their mailbox in to Virtual Vault, would it restore the item back to the original folder? I assume if it's named the same, say Inbox to Inbox then it would work, but if they moved from Inbox to Inbox\reports it would create the folder structure Inbox\reports if it didn't already exist? Thanks.
Slow file retrieval from archive
Dear EV experts! Our customer has a test env with EV 12 and FSA archiving. We have that problem: - If we click a file which is archived and if we click a placeholder or shortcut file the retrieval from the archive is very-very slow. For a 4 Gb file it takes from approx 20 minutes. If we copy one file from archive share to the Prod share it takes 1-2 minutes maximum. Question: --------- 1. How can we tune this retrieval speed, which setting should we check on EV side? 2. How can we fix this issue? BR: PalEV FSA sizing question
Dear EV experts! Our customer want to implement EV 12 with FSA archiving. Customer has 60Mrd (60 x 1000 Million) files on 10 file server.(2-8Mrd file on each server) The data is approximately 20-30 Tb. We are design and size the architecture.The initial goal to reduce the number of files on the file server and the users doesnt suffer too much performace reductions. Questions: ---------- - Do you suggest to implement one big EV server or multiple servers? - Do you suggest to implement one SQL server or multiple SQL servers ? I read that one SQL server can host multiple EV server database.(8) Which basic architecture do you suggest? On the EV server i plan the following disk layout: C: os D: EV app binaries E: index, sql, staging area F: vault archive data I am thinking about E: drive which has an index: sequential read/write and sql: random read/write which may not good to mix a different io pattern on same drive. - What do you think about and wh at do you suggest? BR: PalEV search retrieves the whole archive
Dear EV experts! Our customer has a test env with EV 12 and FSA archiving. We archived test 50 Gb data. We have that problem: - If we run the search process running with wildcard (for example: *.*) on the EV server it retrieves the whole archive for the customer. It takes a long time to retrieve the whole archive. Question: --------- 1. How can we prevent users to retrieve the whole archive? 2. How can we prevent that queries from the users? BR: Pal
