Introduction
Clustering technology have become a common standard hygiene part of any organization that required high availability for their services. The question is how many of them does practice and have this to be implemented. What I would like to cover in the following will be a scenario when there is a site down on production network and how it can failover to any of the remote location with less effort on configuration. I will cover more detail as you sail through thru the blogs.
Configuration
The above will be the actual configuration on the entire site, each of the site will have a different set of IP address.
Production site:
- installed with Hyper-V server
- 2 running VMs
- installed with Hyper-V server
- Quorum shared
As on the screen above, we will start creating the cluster by adding the required node into the cluster.
Since we are not using any storage that is required, you can choose the no option and click next.
You will required to create a clustername for it. Please take note , when you configure on a multisite cluster node configuration. The VM ip might need to be change.
This would be the confirmation of the cluster configuration.
Configuring the cluster
A report of the cluster confirmation, you can click on finish to proceed
The next step is to create the quorum. In short quorum is the cluster configuration database, and choosing the type it is also very important to get the right setup.
For the above configuration, I have found a very good link that shown on each of the area what it does and etc. It also explain on each node how it behave and etc.I would recommend you to read thru it first to have a better understanding.
You will need to have one server which is hosted as file server that hosted the share.
This would be the cluster confirmation
Summary of the quorum setting is shown as below, if you would like to view the detail information. You can click on the view report option.
This is how it look ,after the configuration.
Reference
Part 6 : Configure high availability VM(Live migration without shared storage)
Summary
No comments:
Post a Comment