Unsolved
This post is more than 5 years old
2 Posts
0
297
December 26th, 2007 03:00
autostart with replistor for high availability for sql 2000
Dear Sir,
We are doing a lab test for EMC Auto start With Replistor for SQL high availability. We have 2 machines with win2k3 sp2 and SQL 2000 loaded. The machines has 3 nics with IP address in the following series 192 , 172 , 10. The 192 series is used for accessing SQL database accessing, the 172 series is used for auto start heartbeat which is connected by a cross cable. The 10 series is used for replication and mirroring between the system , it is also connected by cross cable. Both the systems are in domain. We have configured a virtual IP for both the system and created a node aliases for the same. We have created a resource.we have created a data source for SQL. When we do a manual fail over like shutting down the primary system , auto start does not start the services on the secondary system. When we manually transfer the services from auto start console. The secondary system get started properly . We are trying to do a automatic failover but the process is not taking place. Can u guide us for doing the same .....?
thanks
We are doing a lab test for EMC Auto start With Replistor for SQL high availability. We have 2 machines with win2k3 sp2 and SQL 2000 loaded. The machines has 3 nics with IP address in the following series 192 , 172 , 10. The 192 series is used for accessing SQL database accessing, the 172 series is used for auto start heartbeat which is connected by a cross cable. The 10 series is used for replication and mirroring between the system , it is also connected by cross cable. Both the systems are in domain. We have configured a virtual IP for both the system and created a node aliases for the same. We have created a resource.we have created a data source for SQL. When we do a manual fail over like shutting down the primary system , auto start does not start the services on the secondary system. When we manually transfer the services from auto start console. The secondary system get started properly . We are trying to do a automatic failover but the process is not taking place. Can u guide us for doing the same .....?
thanks
0 events found
No Events found!
ecervant
63 Posts
0
December 27th, 2007 08:00
In order for automatic relocation to occur when a node is no longer online, the isolation detection addresses must also be configured in the environment. The isolation detection addresses may be entered globally by going to the isolation tab under the domain name. To configure the isolation detection IP addresses at the node level you would expand nodes and select the "Failure Detection and Mirroring" tab for each node. The isolation IP addresses must be on the same subnet as the node and should be available at all times. For redundancy at least two Isolation IP addresses should be specified, but only one is required.
The second thing I would suggest is also making the 192 an AutoStart domain line. Typically the main domain line should be over the public interface and the secondary domain line may be over the crossover cable. By just having the domain line over a crossover cable, it may cause problems when the partner node goes down due to Windows media sensing on the surviving node. Windows media sensing can cause the base IP address of the surviving node to be lost and therefore causing AutoStart agent failures.
Emilio Cervantes
EMC Technical Support