What is Management Server List and how to configure Failover between replication partners using embedded database.

Created: 22 Jul 2009 • Updated: 22 Jul 2009
Login to vote
+6 6 Votes

What is Management Server List?

Management server list is responsible for communication setting on the client machine. It shows the list of server to which clients can connect. The default management server list is generated automatically by Management server.

The client will connect to the management server with a higher priority. Lower the number higher the priority. Management server list can also be used to create secure https communication.

Important Note: -
Before you configure failover using embedded database make sure that you network is capable enough to handle the traffic. For that what I mean is if you have a WAN link and you have Large number of client who would failover to other site, entire traffic would be routed to WAN link which might increase activity over WAN link.

How to configure Failover between replication partners using Embedded Database?

Steps to configure Failover between replication partners using Embedded database.

We would assume that the replication partner has been successfully configure between two sites.
1. On the Main site go to Policies tab expand Policy Components.
2. Select Management Server List.
3. On the Right Pane you would find two management server list already created due to the replication partner.
4. Note the you will not be able to change the Default management server lists.
5. Click on Add Management server List under Tasks.
6. Specify the name for the management server list e.g. Management server list of Site A.
7. Under the Management server you would find Priority 1 listed.
8. Click on Add button and select New Priority.
9. Select Priority 1 from the list and click on add button and select New Server.
10. It will pop up Add Management Server window.
11. Specify the server name of Site A and the IIS port which is been used by Symantec Web Server. e.g. 8014, 80 etc.
12. Click on OK.
13. Click on Add button again without changing the priority and select New Server.
14. Specify the server IP address of Site A and the IIS port which is been used by Symantec Web Server. e.g. 8014, 80 etc..
15. Click on OK.
16. Select Priority 2 from the list and click on add button and select New Server.
17. Specify the server name of Site B and the IIS port which is been used by Symantec Web Server. e.g. 8014, 80 etc.
18. Click on OK.
19. Click on Add button again without changing the priority and select New Server.
20. Specify the server IP address of Site B and the IIS port which is been used by Symantec Web Server. e.g. 8014, 80 etc..
21. Click on OK.
22. The management server lists are now created however they are not yet assigned to the groups.
23. Make sure that in order to Assign these Management server list you have to uncheck the Policy inheritance from the parent group.
24. Right click on the Management server list and click on Assign.
25. Select the group which belong to Site A and click on OK.
26. Which will allow the clients to failover to Site B in case Site A is down.
27. We need to repeat the same process for Site B Starting from Creating Management server list of Site B.
28. Repeat the process from Step 6 to Step 26 by change the servers in priority 1 and priority 2.
29. Assign the policy to Group which belong to Site B.
30. Failover is configured successfully.

 

Filed Under

Tags:

Comments

12
Aug
2009

Hi step # 14. Specify the

Hi

step # 14. Specify the server IP address of Site A and the IIS port which is been used by Symantec Web Server. e.g. 8014, 80 etc..
Would this be Site A or Site B?