Description
This article describes how to move a Cloud Server to a different User-Manageable Cluster. The Server can be running or stopped.
Note: This function is available only in locations with User-Manageable Clusters available. For more details, see Introduction to User-Manageable Clusters.
Prerequisites:
- Only the Primary Administrator or a User with the Server role can move a Server between User-Manageable Clusters
- Cloud Server is in an MCP 2.0 data center
- Data Center Location is not in maintenance
- Cloud Server must not have any actions pending
- Cloud Server is in a data center location with User-Manageable Clusters
- Target Cluster to which Cloud Server is being moved supports the configuration of the Cloud Server in terms of:
- Number of vCPU
- Amount of RAM
- CPU Speed
- Disk Speed
- The system enforces the Minimum Disk Count, Maximum Disk Count, and Maximum Total Storage properties in the Target cluster when taking Disks on IDE/SATA/ISO/FLP controllers into account.
- IDE and SATA local disks count towards ALL of these values
- ISO and FLP do NOT count towards Minimum Disk Count or Maximum Disk Count
- ISO and FLP DO count towards Maximum Total Storage
Moving Cloud Servers to a different cluster is blocked if the Cloud Server is a Target Server in a DRS Consistency Group.
You cannot move a Server between Clusters if the Server is in Snapshot Preview. You must first migrate the Snapshot Preview Server to a Normal Server. See Introduction to Cloud Server Snapshot Feature
- The target Cluster to which Cloud Server is being moved must support the configuration of the Cloud Server in terms of:
- Number of CPU
- CPU Speed
- Amount of RAM
- Disk Speed
- Disks meet Target cluster's Minimum Disk Count, Maximum Disk Count, and Maximum Total Storage (GB)
- If the Server has Advanced Virtualization Settings:
- If Nested Hardware Virtualization is set to True, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- If CPU Latency Sensitivity is set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- If Numa Autosize is set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- If Enable Host Info to VM Tools is set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- For more information on Advanced Virtualization Settings, see Introduction to Advanced Virtualization Settings
Content / Solution:
From the Home page, select the Data Center where the Cloud Server you want to manage is located:
The Data Center dashboard will be displayed. Select the Network Domain where the Cloud Server you want to manage is located:
The Network Domain dashboard will be displayed. Click on the Server tab to expand the list of Servers:
Identify the Server that you want to move to a different Cluster. Click on the Manage gear of the Server you want to move, and select Move to Another Cluster from the drop-down menu:
The Move Server to Another Cluster dialog will be displayed:
Select the New Cluster from the Destination Cluster drop-down menu, then click Move:
Note: If the Server is part of an Anti-Affinity Rule, the Anti-Affinity rule no longer applies since the servers will be on separate clusters, so the below message will be displayed in the dialog:
The system will display a message indicating that the operation is in progress:
The system will display the progress in the Server bar:
Once complete, the Servers tab will be updated to reflect the change:
The system will display a success message: