This time I use MS Virtual Server 2005, the reason is that the MS's things management interface is good, and the other product compatibility of MS is good. (I prefer to use VMware Unix or Linux, which can also be installed) The other Virtual Server has a place to attract me to define CPU resource allocation, which will be useful for our limited resources.
First look at my hardware environment: AMD Athlon 1.3G, 384MB RAM, 8139 network card pick HUB
First, play the cluster to have a domain, the operating system of this machine itself is a 2003 Enterprise version, which is DC yourself.
Installing Virutal Server 2005, its management interface is http: // localhost: 1024, of course, you can also use other machines on the network. The management of Server and virtual machines is all here. The operation is simple, you can also find help in the start menu.
Before adding a virtual machine, set the default path of all files, which is for future convenience. Click Server Properties in the lower left corner to appear the following interface, write the file path created after Server.
Then configure the network, you need to create a Virtual Network, do not connect to the physical network card, just virtual one. Because the static IP is used later, I ban DHCP.
Next, you can create virtual machine Virtual Machine, we need 2 machines that are configured as follows:
Memory: 128MB, lower than this cannot be installed 2003, and then changed to 96MB.
2 SCSI cards, pay attention to select Share Bus for Clustering
3 blocks of hard drives: 1 Dynamical Expanding virtual hard drive, used as IDE operating system and application software, dynamic increase is more provincial places, and the capacity is written on a few g. 2 Fixed Size virtual hard drives, which are connected to two SCSI are on the attachment, which is a pre-allocated space, I am divided.
500M
. 2 SCSI makes a clustered shared disk, a piece of branch, another block, such as the SQLServer library that will be mentioned below. Note that the SCSI hard drive used by the two virtual machines is the same file, and it is not called a shared hard disk.
2 blocks, a connection physical hard disk, can provide services to other machines on the network in the future, and another piece of Virtual Network is a heartbeat.
The optical drive does not use it, support the mapping of physical optical drives and ISO mirror files, and the virtual machine can also change the disc.
After the configuration, the machine is as follows:
This can be installed. The virtual machine switch is controlled by the following image. Start menu -> Microsoft Virtual Server-> Virtual Machine Remote Control Client, this program is equivalent to the "display" of the virtual machine, and the mouse point can control the virtual machine, and the system with the ALT back itself. Pack 2003 is an old set, but only the enterprise version supports the cluster, pay attention. After installing, configure the machine's interface to click Add ... .tool (forgot), it will insert a disc inserted into the virtual machine, after installing the software inside, let the mouse free to enter and exit the virtual screen and your actual desktop No longer use ALT.
Here is a tip, you can first match a virtual machine, install 2003, and copy the IDE hard drive file .vhd and virtual machine file. VMC can make the second virtual machine. Add a second place to the manager, modify the IDE hard drive, point to the newly replicated .vhd file.
Then turn it on the basic configuration of 2003
The first machine name Virtual1, and the virtual network card connected to the physical network card is equipped with the IP address of the same network segment (I am 192.168.0.6/24, and the card 10.1.0 "10.1.0
.1 / 8
The second machine name Virtual2, two network cards are equipped with 192.168.0.7/24 and
10.1.0
.2 / 8
View two virtual machine disk managers, see who controls the shared disk, makes two SCSI hard drives into basic disk partitions into primary partitions (not dynamic disks, dynamic volumes!). Two hard drives and volume quasios Q: QDisk, s: sharedisk.
Add both machines to the domain. Ready to work.
All of the following work is operating on virtual machines with shared disk control.
Click Cluster Manager in the Management Tool, we create a virtual cluster called Cluster
Next step is the name of the first node, the default is the virtual set you are now controlled. My experience is at this point here, select the minimum configuration. I found that he automatically searches and then configures easy errors and does not get the results we want, it is better to manually configure it after simply simply.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step. Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation. Here is a tip, you can first match a virtual machine, install 2003, and copy the IDE hard drive file .vhd and virtual machine file. VMC can make the second virtual machine. Add a second place to the manager, modify the IDE hard drive, point to the newly replicated .vhd file.
Then turn it on the basic configuration of 2003
The first machine name Virtual1, and the virtual network card connected to the physical network card is equipped with the IP address of the same network segment (I am 192.168.0.6/24, and the network card for jumping "
10.1.0
.1 / 8
The second machine name Virtual2, two network cards are equipped with 192.168.0.7/24 and
10.1.0
.2 / 8
View two virtual machine disk managers, see who controls the shared disk, makes two SCSI hard drives into basic disk partitions into primary partitions (not dynamic disks, dynamic volumes!). Two hard drives and volume quasios Q: QDisk, s: sharedisk.
Add both machines to the domain. Ready to work.
All of the following work is operating on virtual machines with shared disk control.
Click Cluster Manager in the Management Tool, we create a virtual cluster called Cluster
Next step is the name of the first node, the default is the virtual set you are now controlled. My experience is at this point here, select the minimum configuration. I found that he automatically searches and then configures easy errors and does not get the results we want, it is better to manually configure it after simply simply.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation. As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it. Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation. Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Before adding a virtual machine, set the default path of all files, which is for future convenience. Click Server Properties in the lower left corner to appear the following interface, write the file path created after Server.
Then configure the network, you need to create a Virtual Network, do not connect to the physical network card, just virtual one. Because the static IP is used later, I ban DHCP.
Next, you can create virtual machine Virtual Machine, we need 2 machines that are configured as follows:
Memory: 128MB, lower than this cannot be installed 2003, and then changed to 96MB.
2 SCSI cards, pay attention to select Share Bus for Clustering
3 blocks of hard drives: 1 Dynamical Expanding virtual hard drive, used as IDE operating system and application software, dynamic increase is more provincial places, and the capacity is written on a few g. 2 Fixed Size virtual hard drives, which are connected to two SCSI are on the attachment, which is a pre-allocated space, I am divided.
500M
. 2 SCSI makes a clustered shared disk, a piece of branch, another block, such as the SQLServer library that will be mentioned below. Note that the SCSI hard drive used by the two virtual machines is the same file, and it is not called a shared hard disk.
2 blocks, a connection physical hard disk, can provide services to other machines on the network in the future, and another piece of Virtual Network is a heartbeat.
The optical drive does not use it, support the mapping of physical optical drives and ISO mirror files, and the virtual machine can also change the disc.
After the configuration, the machine is as follows:
This can be installed. The virtual machine switch is controlled by the following image. Start menu -> Microsoft Virtual Server-> Virtual Machine Remote Control Client, this program is equivalent to the "display" of the virtual machine, and the mouse point can control the virtual machine, and the system with the ALT back itself. Pack 2003 is an old set, but only the enterprise version supports the cluster, pay attention. After installing, configure the machine's interface to click Add ... .tool (forgot), it will insert a disc inserted into the virtual machine, after installing the software inside, let the mouse free to enter and exit the virtual screen and your actual desktop No longer use ALT.
Here is a tip, you can first match a virtual machine, install 2003, and copy the IDE hard drive file .vhd and virtual machine file. VMC can make the second virtual machine. Add a second place to the manager, modify the IDE hard drive, point to the newly replicated .vhd file.
Then turn it on the basic configuration of 2003
The first machine name Virtual1, and the virtual network card connected to the physical network card is equipped with the IP address of the same network segment (I am 192.168.0.6/24, and the card 10.1.0 "10.1.0
.1 / 8
The second machine name Virtual2, two network cards are equipped with 192.168.0.7/24 and
10.1.0
.2 / 8
View two virtual machine disk managers, see who controls the shared disk, makes two SCSI hard drives into basic disk partitions into primary partitions (not dynamic disks, dynamic volumes!). Two hard drives and volume quasios Q: QDisk, s: sharedisk.
Add both machines to the domain. Ready to work.
All of the following work is operating on virtual machines with shared disk control.
Click Cluster Manager in the Management Tool, we create a virtual cluster called Cluster
Next step is the name of the first node, the default is the virtual set you are now controlled. My experience is at this point here, select the minimum configuration. I found that he automatically searches and then configures easy errors and does not get the results we want, it is better to manually configure it after simply simply.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step. Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation. Here is a tip, you can first match a virtual machine, install 2003, and copy the IDE hard drive file .vhd and virtual machine file. VMC can make the second virtual machine. Add a second place to the manager, modify the IDE hard drive, point to the newly replicated .vhd file.
Then turn it on the basic configuration of 2003
The first machine name Virtual1, and the virtual network card connected to the physical network card is equipped with the IP address of the same network segment (I am 192.168.0.6/24, and the network card for jumping "
10.1.0
.1 / 8
The second machine name Virtual2, two network cards are equipped with 192.168.0.7/24 and
10.1.0
.2 / 8
View two virtual machine disk managers, see who controls the shared disk, makes two SCSI hard drives into basic disk partitions into primary partitions (not dynamic disks, dynamic volumes!). Two hard drives and volume quasios Q: QDisk, s: sharedisk.
Add both machines to the domain. Ready to work.
All of the following work is operating on virtual machines with shared disk control.
Click Cluster Manager in the Management Tool, we create a virtual cluster called Cluster
Next step is the name of the first node, the default is the virtual set you are now controlled. My experience is at this point here, select the minimum configuration. I found that he automatically searches and then configures easy errors and does not get the results we want, it is better to manually configure it after simply simply.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation. As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Next, analyze software and hardware conditions, we choose to manually configure the arbitration plate, so there will be an exclamation mark, do not pay attention.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it. Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
After that, it is divided into cluster, I chose 192.168.0.10. When the domain administrator password is added, the configuration wizard ends the next step.
Let's start manual configuration. Right click on the resources in the left tree, add two hard drives, s and q, and then completed as shown below.
Right click on Cluster and change the arbitration disk to Q. Then delete the local arbitration in the resource.
Next, modify the two local connection properties, one only allows the outer network, one only allows the intranet. You can add another node after you have no problem. The process is the same as the first node above, it is best to configure it.
Now we can test the two-storey hot standby function of the cluster. Now constructed by the Virtual2 control cluster, right -> mobile group can hand over control to Virtual1. If successful, the cluster is working properly.
The next task is to install SQLServer2000, the Enterprise Edition used.
Normal, the installer recognizes the cluster and installs the virtual server, and the name is VirtualSQL.
Similarly, virtual SQLSever also requires a separate IP to provide services.
Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation. Put the data on the shared disk S.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
As long as you ask what you answer, the installer will automatically install it on both nodes.
Return to the cluster manager, there is a good strategy to build a resource group and put all the SQL-related. If there are other applications, it is best to create a group separately and will not affect each other. Moreover, the two nodes can be controlled different applications according to the actual situation.
