I am installing EV 2007 SP1 in a new environment, I have 5 EV servers (4 mailbox Servers and 1 Archive Server) in production, I have the same amount of servers at my failover site (DR Site) acting as standby servers. The production site and failover site is in the same domain even though they are physically separated.
The production site using Centera as storage that is replicated to a Centera at the failover site, I have configured one Vault Store for each server, all indexes, Centera collection area and shopping are installed and configured on a SAN drive for each server, the idea is to move the san disks for to the failover site in a DR scenario. The same idea applies to the SQL database.
I have read the Enterprise Vault PDF documentation about block mode configuration that is supplied with the software but cannot figure out how to configure the servers for failover.
When I add the 5 standby servers in VAC by running the configuration wizard, do I have to create a new site in EV (can servers move/failover between sites ) or do I place the 5 standby servers in the same Enterprise Vault site ?
I guess that I do not configure any vault stores for the 5 standby servers as they will use vault stores configured for production when a failover is initiated ?
Do I have to update the Centera ip addresses when I failover ?
Any help will be much appreciated,
Thanks Mark for the overview of the concept, its much appreciated.
Just to clarify, in an active/ passive configuration that you describe with Server 3, when you add server 3 to the site by running the Enterprise Vault configuration wizard you use “Existing Vault Directory ” and then” join the existing vault site” if I understand you correctly ?
If Server 1 fails, its DNS alias can be switched to Server 3, does that mean that Server 3 doesn’t need a DNS alias when added to the site but instead use its FQDN ?
Also does Server 3 require to be configured with its own services like indexes, storage and shopping in this scenario or will Server 3 simply take over the services of Server 1 after USL ?
I have engaged Symantec Professional Services but they have not been able to give a start date as of yet, I just like to understand the process a bit better before we do start.
In a Building Blocks system, all the Enterprise Vault servers operate as self-contained units. They have all the Enterprise Vault services running locally, including a Directory Service and Web Access Application on every server. (By default, only the first Enterprise Vault server installed has a Directory Service; to add Directory Services to other servers, use the Update Service Locations (USL) option in the Enterprise Vault Administration Console).
Each server is responsible for archiving and storing data for a particular set of users (ie a set of Exchange servers), and for servicing all search and retrieval requests for those users. So one Enterprise Vault server is never reliant on any other Enterprise Vault server. If one Enterprise Vault server fails, all the others can carry on working unaffected. There is no single point of failure. Additionally, it is very easy to failover to another Enterprise Vault server, which takes over the duties of the failed server, ensuring continuity of service.
For this to work, the Enterprise Vault servers must all be in the same Vault Site, and must all use a remote SQL Server. Standard SQL high-availability solutions would be used to ensure its reliability. Also, all Enterprise Vault storage must be network accessible (via UNC paths, etc) so that it is visible (and with the same name/address) to every Enterprise Vault server. DNS servers must be being used for all Enterprise Vault servers, and the Web Access Application in the Site Properties should be modified to remove the http: and machine name prefixes, leaving just the virtual folder name (all Enterprise Vault servers must use the same virtual folder name). This forces Enterprise Vault to dynamically generate the URL as needed, with the appropriate server name for each user.