What is suggested for a clustering/fall-over solution for Content Manager?
What is suggested for a clustering/fall-over solution for Content Manager?
Preferred method:
Using two Windows Server 2003 or Windows Server 2008 R2 Servers of appropriate capacity. If you intend this for hosting multiple Content Manager VMs, then 64 bit is suggested. VMwareServer has "free" license for up to two CPU's. "EMCReplistor" to replicate the VM's between the two hosts. For large scale use VMware ESX Server with "esxRanger" as the duplication software. Scala Sales can issue this customer a dongleless dongle because the VMWare does not support USB. A Standard install, and configuration of Content Manager without any particular"knowledge" of the nature of the VM environment.
Have the Content Manager's DNS names configured under DynDNS or a similar service. We like DynDNS.com because they are responsive and appear to be technically competent. If the servers are at geographically separate sites, then appropriate bandwidth will be required for the data sync operation of the Replistor software. Security can be implemented via VPN-tunnel/gateway appliances.
Basic scenario:
Both host servers are up and running all of the time. Only one VM of a "Fall-over Cluster pair" is running at any one time. The Replistor rule: Mirror the running Content Manager 5 VM to the not-running Content Manager 5 VM. If Replistor heartbeat interval fails: Scripted start the Secondary VM. It wakes up, runs CHKDSK/DB-dirty-shutdown-recovery to clear up whatever files that were in the process of being written to prior to the failure of the Primary VM. After it fully wakes up, the DynDNS client updates the global DNS system with the new IP#. Some Players/Designers might not be able to reach the "Secondary" in it new role as "Primary" for up to 20 minutes--due to DNS caching--this can be adjusted--then all of their requests will go to the "Secondary" machine. When the original "Primary" is restored, the options are: Reverse the roles. Take both machines down for the short period required to reverse sync.
Costs:
Two machines of appropriate capacity; Four Microsoft Win03WE or (Win03STD Server + CAL's) licenses; Two Replistor Licenses, (USD$700 per server); DynDNS domain name hosting--USD$15/year; However Scala elects to structure "Stand By" Content Manager 5 licenses/backupDongles/SW-Dongles.
Regards,
Scala Technical Support
