Implement an MDaemon cluster based on an SQL server storage account

Welcome to the Windows community forum and interact with 3 million technical staff? This chapter provides an overview of MDaemonServer (MDaemon) redundancy solutions with multiple options. This chapter uses the SQLServer2005 Simplified Chinese Enterprise Edition (SQL2005) developed by Microsoft as the storage database for MDaemon accounts, in Microsoft cluster (MS

Welcome to the Windows community forum and interact with the 3 million technical staff> enter? This chapter provides an overview of MDaemon Server (MDaemon) redundancy solutions with multiple options. This chapter uses the SQL Server 2005 Simplified Chinese Enterprise Edition (SQL2005) prepared by Microsoft as the MDaemon account storage database, in Microsoft cluster (MS

Welcome to the Windows community forum and interact with 3 million technicians>

? Overview

MDaemon Server (hereinafter referred to as MDaemon) has a variety of options for redundancy solutions, this chapter will use Microsoft's SQL Server 2005 Simplified Chinese Enterprise Edition (hereinafter referred to as SQL2005) as the MDaemon account storage database, deploy the SQL2005 virtual server cluster on the Microsoft cluster (MSC) to realize automatic failover of MDaemon and achieve high availability as required by users.

This chapter focuses on the implementation of MDaemon clusters. For details about the deployment of MSC and SQL2005 clusters, see:
1. Create and configure a Windows Server 2003 Cluster
Http://www.microsoft.com/china/technet/prodtechnol/windowsserver2003/technologies/clustering/confclus.mspx

The MDaemon version used in this experiment is v7.23 in English. We recommend that you use the English version regardless of the test environment or the actual production environment to avoid unnecessary errors. If possible, the best operating system should also select the English version, in actual situations, it is found that the English version of MDaemon is compatible with the Chinese system, and the menu display is incomplete.

　　? Test Environment
Host:
Hardware configuration: PIV2.4G/1.5g-ddr400/80G-7200pm/8139C-NIC
Operating System: Windows XP Pro With SP2 ENU
Virtual Platform: VMware GSX 3.2.1

NodeA:
Hardware configuration: PIV2.4G/512 M/10G + 0.5G (Qdisk) + 4G (Sdisk)/vlance-NIC + vmxnet-NIC
Operating System: Windows Server 2003 EE With SP1 CHS
Network Information: vlance-NIC: 10 M full speed half duplex/Heartbeat/IP192.168.236.250
Vmxnet-NIC: 1000 M full speed full duplex/Public/IP192.168.199.250
Bearer information: DC + DNS + IIS + SQL2005 + MSC

NodeB:
Hardware configuration: PIV2.4G/512 M/10G + 0.5G (Qdisk) + 4G (Sdisk)/vlance-NIC + vmxnet-NIC
Operating System: Windows Server 2003 EE With SP1 CHS
Network Information: vlance-NIC: 10 M full speed half duplex/Heartbeat/ip192.168.236.large
Vmxnet-NIC: 1000 M full speed full duplex/Public/ip192.168.199.20.
Bearer information: DC + DNS + IIS + SQL2005 + MSC

MSC:
MSC: IP192.168.199.200/HostName: CLUSTER
SQL2005 VirtualHost: IP192.168.199.201/HostName: SQL2005

　　? Theoretical Concept & ultimate goal

Use SQL2005 to store databases as MDaemon accounts and use the cluster mode to ensure that MDaemon can still provide domain and Account Verification and management after any node server fails.

The resource disk (Sdisk) is used to store user data of MDaemon, to ensure that after a fault occurs on any node server of MDaemon, after the verification is passed, the user logs on to MDaemon and obtains the same email as the data.

At last, MDaemon redundancy is realized through automatic failover of MnS.

Therefore, create a database in SQL2005 to save the MDaemon domain and account information and name it MDaemonUsers. Configure the storage mode of the MDaemon account as ODBC, create a connection with the MDaemonUsers database in SQL2005, and import it to the account database for query. Modify the storage path of the default MDaemon account template. In the Cluster Manager, configure MDaemon as a "common service" resource in the cluster.

　　? Implementation and deployment

First, install MDaemon on the node server that receives the active resources. Record the Administrator name and password when installing MDaemon. After MDaemon is installed, we strongly recommend that you restart the system once, make sure that the MDaemon service is running properly. Then, perform the following operations:

1. Open the Database Manager and create a new database named MDaemonUsers.

2. Open the Service Manager, find the MDaemon service, and change the Startup Type to "Manual ".

3. Because MDaemon is currently only bound to 192.168.199.20.and the cluster IP address is not in the binding range, access failure may occur. To this end, open the MDaemon manager, click "Setup" in the navigation bar, and select "Primary domain ...".

4. Go to "Primary Domain", change "Primary Domain IP" to "127.0.1.1" on the "domain" page, and then exit.

5. To save the user data of MDaemon under Sdisk, You need to modify the default configuration of new users. To this end, click "Accounts" in the navigation bar and select "New account defaults ...".

6. On the "Account ults" Page, change "Mail directory" to "S: \ MDaemon Users \ $ DOMAIN $ \ $ MAILBOX $ \" and configure other items as needed, confirm to exit.

7. An administrator is created during MDaemon installation. To ensure the consistency of the MDaemon administrator in each node, You need to migrate the Administrator data to the Sdisk. To this end, click "Accounts" in the navigation bar and select "Account manager ...".

8. Select the Account "Admin", go to "Account Editor", switch to the "Mailbox" page, and change "Message directory" to "S: \ MDaemon USERS \ maytide.net \ admin \", confirm and exit.

9. Modify the storage mode of the MDaemon account and change it to the SQL Server storage mode in ODBC. To this end, click "Accounts" in the navigation bar and select "Account database ...".

10. Go to "Account Database Options", change the option on the "Account database" page to "Store account data in a ODBC accessible store", and click "Configure" to start configuration.

11. Go to the configuration page and click "New DSN" to create a data source.

12. In the "Select data source" configuration, switch to "machine data source" and select "new ".

13. In the "Create a new data source" configuration, set the data source type to "System Data Source (only for the current machine)" and click "Next ".

14. Select "SQL Server" as the data source driver and click "Next ".

15. At this point, the creation of a system data source with SQL Server as the connection type has been completed. Click "finish ".

16. The ODBC Data Source Creation wizard for connecting to SQL Server is displayed automatically. Enter the information as prompted. For ease of management, I name the ODBC Data Source "MDaemonUsers". Note that the server should be "SQL2005" as the host name, because "SQL2005" is the SQL2005 cluster virtual host in this experiment.

17. In the authentication and connection configuration, I use the default configuration.

18. Change the default database to the Database "MDaemonUsers" in SQL2005, because this database will be used to save the domain and user information of MDaemon.

19. If other options are set to default, click "finish ".

20. The prompt is displayed. You can select "Test Data Source" to test the connection.

21. At this point, an ODBC machine data source connected to the SQL Server named "MDaemonUsers" is established on the current node Server.

22. After completing ODBC configuration, go back to "ODBC Selector Wizard" in MDaemon. You can see that "MDaemonUsers" is already in the data source list, select it, and click "Next ".

23. Because the Database "MDaemonUsers" in SQL2005 corresponding to the "MDaemonUsers" data source in ODBC does not have the table required by MDaemon, we run the script that comes with MDaemon to create it. To this end, click "Run a script to created the necessary tables ...".

24. The Wizard will automatically go to the SQL scritps location where there are multiple script options, because we are using SQL Server, so select the script file named "AccountsDB-SQLServer. SQL, select "open ".

25. "Tables created successfully!" is displayed !" If it fails, re-check the previous steps to ensure that the data source is successfully created.

26. Return to the "ODBC Selector Wizard" interface. We will see the two successfully created tables "domains" and "userlist", and click "finish ".

27. MDaemon starts to convert data and provides a prompt.

Okay. You can take a rest. This completes the establishment of MDaemon's account storage method using SQL Server. I felt tired enough. In fact, it would be very easy to operate, and it would take a long time. It was very smooth to choose the best way. But I am really tired enough. It is already, and I decided to continue writing my work after 12 minutes from work.

Basically, most of the work has been completed. Close this node and switch to another node for MDaemon installation and configuration. The MDaemon installation configuration on the second node will no longer be repeated.

Note that the Administrator name and password for MDaemon installation on the second node should be the same as that on the first node. At the end of the installation, there is an option "Start MDaemon ", do not select this option, because we need to manually configure MDaemon on this node to use the database storage account.

To this end, open "Data Source (ODBC)" in the system management tools program group and refer to the data source installation steps of the first node to create the same data source as before for the second node. Then, open the "MDaemon. ini" file in the App directory where MDaemon is installed in the text editor, and add the following Configuration:

Code

[Advanced] UserDllType = ODBC [USER_ODBC] DSN = MDaemonUsers User = Password =

Note: DSN is the database source used by the server ODBC to configure MDaemon. User and Password are the access accounts and passwords for the specified data source. Similarly, if mdaemon is used. if the ini configuration file does not contain the [USER_ODBC] configuration field, add it.

Change the MDaemon service on the current node to the "Manual" mode (refer to 2 ). Run MDaemon to modify the default bound IP address (refer to 3 ~ 4). Modify the default account path to be the same as the first node (see Figure 5 ~ 6 ). Go to account management and you can see that the Administrator data on this node is located on Sdisk, because the database storage account information has been manually configured before MDaemon is started for the first time, therefore, after the first startup, MDaemon directly obtains account information from the database. Now, you can test whether the post office works properly! Access http: // IP_Address: 3000 and log on to WorldClient for test.

28. After completing the above steps and tests, MDaemon's redundant deployment preparations are complete. To achieve automatic failover, you also need to configure MDaemon to MDaemon, we strongly recommend that you disable the MDaemon service to avoid unnecessary errors before starting the configuration, because after MDaemon is configured, its monitoring and control has been transferred to MSC. Next, configure the cluster for MDaemon. Open "Cluster Manager" on the current node and create a "resource" in "group 0" in the cluster group where SQL Server is located ".

29. Fill in related information in "New Resource". Here I name the resource "MDaemon Server" because MDaemon itself does not support clusters, the cluster implementation of MDaemon relies solely on DIY. To make MDaemon supported by MSC, select "General Service" in "resource type ", click "Next ".

30. Add the servers in "available nodes" to "possible owners" in "possible owners", and click "Next ".

31. In the dependency relationship, add the resources that the MDaemon cluster depends on to resource dependency. Then, click "Next ".

32. In "General Service Parameters", "service name" is "MDaemon", and "Startup parameter" is "C: \ MDaemon \ APP \ MDAEMON. EXE, and then click "Next ".

33. After the resource is added, "MDaemon Server" appears in "group 0". After it is online, the system automatically starts MDaemon.

At this point, the MDaemon cluster is implemented based on the SQL Server storage account. Then, we can create an email account for webmail login to check whether the connection between MDaemon and the SQL Server cluster is normal.

　　? End

After the MDaemon cluster is created, we can start the first node for Disaster simulation to verify the effectiveness of the MDaemon redundancy solution implemented in this deployment. After testing, when one node stops, the other node quickly takes over cluster resources and starts the MDaemon service. Note: When only one node is left, it is invalid to stop the service through MDaemon itself. After testing and disabling the MDaemon service, the system will automatically enable the MDaemon service again, if you are performing MDaemon downtime maintenance in this environment, you need to take MDaemon Server offline through the cluster manager.

The MDaemon cluster is intended to be a series, and the name of this series is based on requirements. It is called "MDaemon Server redundancy solution series". in the future, multiple MDaemon redundancy methods will be available for your reference. However, I personally think that the redundancy achieved by the implementation of this cluster may be applied only in the big environment. If MDaemon redundancy can be achieved without Microsoft cluster (MSC), there will be a large application market.

You are welcome to discuss the MDaemon redundancy implementation technology with me. I hope you will participate in the discussion.

Author: gOxiA