07-15-2011 08:00 AM
We are in the testing / lab phase of the EV product and I am tyring to get the following configuration working. We had a consultant breifly help with the design, but based on my research thus far I cant find out how to impiment it properly.
We have two physical sites and want to have redudancy between the two sites. SiteA and SiteB, At our Primary Location aka SiteA we have two EV servers for various functions, these servers (in the lab) are already up and running , all storage is pointing to a shared disk (NAS) that will be replicated to SiteB, SQL is configured so that all DB's are mirrored from SiteA to SiteB. SiteB which is our DR has ONE EV server that has nothign configured on it .
We were under the impression we can have a 2 + 1 configuration sort of as defined in this article (http://www.symantec.com/business/support/index?page=content&id=HOWTO31760#id-SF390536875) without using a cluster. The consultant (who is no longer available) inidcated that failing over would just require some registry and DNS changes etc .
I found a article that explains how to move EV to a new server http://www.symantec.com/business/support/index?page=content&id=TECH55377 but this assums that the server we want to move from, is online. The DR solution does not have to be immediate, as this is a archive server, and one of the sites failed we would have more important things to be worried about.
How can we acheive this with our current configuration.
Solved! Go to Solution.
07-15-2011 09:13 AM
Read this post from Mark Barefoot:
https://www-secure.symantec.com/connect/forums/block-mode-configuration
It will not be fully automated ever without a true clustering technology, howerver building blocks is only a right click and go.
07-15-2011 09:13 AM
Read this post from Mark Barefoot:
https://www-secure.symantec.com/connect/forums/block-mode-configuration
It will not be fully automated ever without a true clustering technology, howerver building blocks is only a right click and go.
07-15-2011 09:50 AM
Building blocks is a manual failover. Basically you point the alias of the EV server that is down to the DR EV server that must be up and running. Once you did the change in the DNS, from the EV console you performe an "Update Service Location". As in the Enterprise Vault database we store both the alias an the host name, the Update Service Location will detect that the alias does not correspond with the hostname (as it is pointing to the new machine).
The only "but" it is that it is a manual process, but you say that this is not an stopper.
Building blocks works very well indeed.
http://www.symantec.com/business/support/index?page=content&id=HOWTO37984