I am using EMC Autostart to monitor and mirror an application that uses a SQL 2000 DB. All worked well until I incorporated replication to keep certain tables synchronized with 2 other servers. The Autostasrt uses virtual names and IP's for clients to connect no matter which server is acting as Primary. Autostart stop services and freezes drives on secondary while mirroring.
Problem happens when failed over to secondary.
1. Since all the tables are copied to the secondary, the server name is Primary (server1) in the tables. It retains the name of server1 as it's property, so this causes an error even if I try to setup Replication on secondary (server2). I know there is a script I could run, but hope there is a better way.
2. I've read there is a limitation of not using an alias or virtual ip, but is there a workaround?
Replication is transactional.
Application is defining having to use old 2000 version.
Requirements are to have two physically separate locations for server, sharing of a common storage or quorum not possible.
Thanks for any input. Hopefully there is a solution so I can continue to use replication over the DTS packages I had been previously using.
Software/Hardware used: propriety software, SQL 2000, EMC Autostart, Windows server 2003
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!