After creating an ODBC connection to your LifeKeeper for Windows cluster via the protected IP address, the connection fails after switching the SQL resource to the backup server.
- Take each instance out of service and bring it back into service on the PRIMARY. Examine the application event log to determine which IP:PORT that particular SQL Server instance is listening on.
- Bring each hierarchy In Service on the SECONDARY server and note the IP:PORT each SQL instance is listening on.
- To insure your clients can connect via ODBC to either server, make sure the PORT each instance is listening on is the same on both the PRIMARY and SECONDARY servers.
- To do this, use the Microsoft SQL Server Network Utility. Select the SQL instance (it must be running on that machine), highlight the TCP/IP protocol and look at the properties to determine the current default port it is listening on.
- Change this value so the default PORT is the same on both systems for this instance.
- Create your ODBC connections for each instance using the protected IPs:PORTs you just set up in Step 5.
Thanks for your feedback.
Post your comment on this topic.