In this week’s post, I’d like to address a few important questions pertaining to the hardware specifications required by Enterprise Vault 10, and offer up some info on how it can help with server migrations.
What OS and hardware should I use for Enterprise Vault 10?
I’ve been asked a few times what the minimum OS and hardware specification should be for an EV 10 server. The OS is simple, EV 10 requires at least Windows Server 2008 R2. When it comes to hardware we’ve found that EV10 will continue to provide better performance the more CPU cores and memory you provide (which is great news!)
The minimum for EV 10 is a server with 4 CPU cores running at least 2.8GHz with 8GB RAM, we’re recommending a server with 8 CPU cores running at least 2.8GHz with 16GB RAM.
Does it matter what form factor the CPU cores are packaged? Nope, dual quad core, quad dual core or a single eight core CPU would be fine! The more cores the better the performance…
Does Enterprise Vault 10 help with hardware or OS refreshes?
With the new pre-requisite of running EV 10 on Windows Server 2008 R2 and our recommendation of using a server with 8 cores and 16GB RAM we’re predicting a fair few customers will want to replace their servers OS or move to new hardware.
Along with the release of EV 10 we’re making available a new 'Server Migration Wizard', which will help guide the migration. The wizard will move any server specific configuration, registry keys or log files to the new server, easing the previous DR method. If required, all data migrations i.e. SQL Server Databases, Index Locations & Vault Store partitions will need to be moved separately (although the Wizard will check that you’ve moved them correctly!)
To run the wizard you’ll need to be running EV 9.0.1.
Disclaimer: Any forward-looking indication of plans for products is preliminary and all future release dates are tentative and are subject to change. Any future release of the product or planned modifications to product capability, functionality, or feature are subject to ongoing evaluation by Symantec, and may or may not be implemented and should not be considered firm commitments by Symantec and should not be relied upon in making purchasing decisions.