This article describes how to add additional local storage disks to a Cloud Server.
Recommended reading: Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds
Related Article on Adding SCSI Controllers
You can add SCSI controllers to allow additional disks to be added. You cannot add SATA or IDE controllers to a Cloud Server
Special Notes Regarding Adding a Disk to a Server in a Powered On State
In most cases (see preconditions below) Local Disks can be added on a Cloud Server while the Server is in a Running State. However, there are some important risks to be aware of if the new disk uses Provisioned IOPS Disk Speed or a Disk Speed on a Burstable IOPS architecture. See the Restart Required Due To vMotion Failure Related to a Disk Change on a Running Server section at the bottom of the page for more details.
- Only the Primary Administrator OR a User with the Server role assigned by the Primary Administrator can add storage to an existing Cloud Server
- Ensure that your proposed disk expansion will not exceed the maximum limits of the Data Center See: How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- Note: All SCSI/SATA/IDE and ISO/FLP count towards the limit
- Note: If you intend to create Client Images from the Cloud Server, ensure your proposed disk addition will not cause the server to exceed the maximum limit for a Client Image in the Data Center.
- If you do not manually select the Controller and position of the disk, it will be added sequentially to the next available SCSI controller and position, assuming such a controller exists and has an open position
- If you wish to select which Controller and which position on the Controller to add a disk by checking the 'Advanced Disk Configuration' box as shown in step 7 below, the following conditions apply:
- You cannot add a disk to a controller and position where either a local disk or a CD-ROM drive already exists
- SCSI ID 7 is reserved for use by the system on all SCSI Controllers. Available SCSI IDs are 0-6, 8-15.
- Addition of Disk to IDE Slot 1 in either channel cannot be done unless either a disk or CD-ROM drive resides in Slot 0 of the same channel
- If you want to add a disk that utilizes the Provisioned IOPS Disk Speed, the requested IOPS must fall within the rules for the disk speed set for the data center location. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
- If adding a disk to an IDE Controller only, the server must be powered off
- Pre-Requisites related to Servers with Cloud Server Snapshot feature (see Introduction to Cloud Server Snapshots)
- You cannot add a disk if the Server is in Snapshot Preview mode. You must first migrate the Snapshot Preview Server to a Normal Server.
You cannot add a disk when a System Snapshot is in progress. This will cause the process to fail. The failure will show up in the Administrator Log. There is no reliable way to identify if a System Snapshot is in progress, but you can check the Snapshot Window in the Snapshot Tab of the Server Dashboard and plan the change around the current Snapshot window.
Pre-Requisites related to DRS for Cloud service (see Introduction to DRS for Cloud)
You cannot Add a Disk on a Server in a DRS Consistency Group, regardless of whether it is Source or Target.
Adding a Disk to a Server
From the Home page, select the data center where the Cloud Server on which you want to add Additional Local Storage is located:
The Data Center dashboard will be displayed. Select the Network Domain (MCP 2.0) or Network (MCP 1.0) on which the Cloud Server on which you want to add Additional Local Storage is located:
The Network Domain (MCP 2.0) or Network (MCP 1.0) dashboard will be displayed. Select the Server on which you want to add Additional Local Storage:
The Server dashboard will be displayed. Click the Storage tab:
Click on the Actions button, then select Add Disk from the drop-down menu:
The Add Disk to Server dialog will be displayed:
To manually select which Controller and position to add the disk to, click on the Advanced Disk Configuration button:
Note: Adding Local Disks on different controller types (SCSI, IDE, SATA) will result in a Server that cannot be imported as a Guest OS Customization Client Image. All local disks must be on the same controller type for a Guest OS Customization Image import.
Note: If you do not manually select the Controller and position of the disk, it will be added sequentially to the next available SCSI controller and position.
Note: For instructions on how to add additional SCSI Controllers to a Cloud Server, see How to Add a SCSI Controller to a Cloud Server
Select the Disk Type from the Disk Type drop-down menu:
Select the desired Controller from the drop-down menu:
If multiple Controllers are added to the Server, select the desired SCSI ID (disk position on the SCSI Controller) from the drop-down menu:
Note: SCSI ID 7 is reserved for use by the system. Available SCSI IDs are 0-6, 8-15.
Select the size of the Disk you want to add to the Server by:
Manually entering the desired size in the Disk Size drop-down:
By using the up / down arrows:
By using the sliding button to select the desired size:
Choose the desired Speed for the Additional Storage from the Speed drop-down menu:
Note: Hovering your mouse over the info iconwill display more information about Disk Speeds
Once you have selected the desired size, Speed, (and if using Provisioned IOPS Disk Speed, the IOPS Value) of the Additional Storage, click the Add Disk button:
Note: If the disk you are proposing to add to the Server is on a different controller type than the rest of the disks, you will see the following error:
The system will display a message indicating that the operation is in progress:
The system will display the progress of the operation in the Status section of the Server dashboard:
Once complete, the system will display a success message:
The Additional Disk will be added to the Storage pool, and the Server Details tab will be updated to show the additional storage:
In the rare case an attempt to add additional local storage fails, details of the failure will be added to the Administrator Logs. See How to View an Administrator Logs Report.
There are two types of potential errors:
- REASON_10 indicates a non-recoverable failure occurred when attempting to add the disk. If this situation occurs, you must open a Support Case to address the issue. Until the issue is addressed, you may not take any further actions against the server. Any additional attempts to add or delete networks will receive a REASON_601 response.
- REASON_11 indicates a potentially recoverable failure occurred when attempting to add the additional disk. Upon receiving this response, the system will “reset” the server back to normal again, allowing you to attempt to add the disk again. Open a Support Case if repeated attempts to add the disk are unsuccessful.
If you need to open a support case, please reference the error from your Administrator Logs.
Restart Required Due To vMotion Failure Related to a Disk Change on a Running Server
When adding a disk with a Disk Speed of Provisioned IOPS or a disk speed that uses Burstable Architecture, the system needs to vMotion the Server in order for the change to take effect. If the relocation between ESXi hosts fails, the Cloud Server will be flagged with a status of "Requires Restart" as seen in the screenshot below. Users will not be able to take any action against this Server until the server is either restarted via CloudControl or shutdown.
This is an unlikely event. The system will prevent changes on a running server if it does not appear it has enough spare capacity to successfully vMotion the server.
For more details, see the Adding and Modifying Disks section at the bottom of the page of Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds.