Changing SQL Server Cluster Members
Updated: November 1, 2013
Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager
When you make changes to a server cluster that is protected by System Center 2012 – Data Protection Manager (DPM), DPM takes the following actions:
When a new server is added to a cluster, DPM issues an alert to install a protection agent on the new cluster node and protection fails.
When a server is removed from a cluster, DPM detects that a node has left the cluster and the server now appears separate from the cluster with no data protected on it.
For example, assume you have a server cluster that contains four computers: Node1, Node2, Node3, and Node4. You need to replace computer Node4 with a new computer named Node5.
You use the administration console for your cluster service to add Node5 to the cluster and configure the resources that can be failed over to Node5.
DPM issues an alert that protection of the server cluster will fail until a protection agent is installed on Node5. You install the protection agent on Node5.
You fail over the resources from Node4 to other nodes in the cluster. When no resources remain on Node4, you remove it from the cluster. DPM detects the failovers and continues protection of the cluster.
DPM detects that Node4 has left the cluster – it appears as a stand-alone node now. If it no longer exists on the network, you can remove the record for this server in DPM Administrator Console.
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.