Description

This article describes how to remove Storage Disks from a Cloud Server

Note: Removing local storage is a destructive process!

You will not be able to retrieve data from removed disks or "undo" their removal. Please be absolutely sure that you wish to remove a disk before doing so, and make sure you've identified the correct disk for removal.

Also be sure the guest O/S is configured to deal with the removal of the disk prior to initiating the removal. For example, you wouldn't want the disk configured as part of a partition the guest O/S is set up to use. For Servers with a Windows guest O/S please see: How to Identify Additional Local Storage on a Windows Virtual Server

You can not decrease the size of a storage disk. You must create a new disk of the appropriate size, and delete the old disk.

Important Note

This article does not cover how to remove ISO and FLP files. For instructions on removing ISO and FLP Files, see How to Remove ISO / FLP Files from a Cloud Server

Prerequisites:

  1. Only the Primary Administrator or a Sub-Admin with the Server role can remove additional storage from a Cloud Server
  2. Removing an IDE disk requires shutting down the Cloud Server if it is running.
    1. Note: It is NOT necessary to shut down the Cloud Server when removing SCSI or SATA disks. 
  3. You can not remove a disk if it would put the total number of disks less than the Minimum Disk count or the total storage less than the Minimum Total Server Size limits for the Data Center or Cluster. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
    1. IDE and SATA disks count towards this minimum but ISO and FLP files do not count
      1. For information on removing ISO and FLP Files, see: How to Remove ISO / FLP Files from a Cloud Server
  4. You cannot delete a disk located in the 0 slot of an IDE controller/channel if the 1 slot of the same IDE channel is occupied by:
    1. A local disk
    2. A CD-ROM drive with or without an attached ISO.
  5. You cannot remove additional local storage from a Cloud Server if the Server is the Source Server in a Consistency Group. See What happens to a Source Server when it is added to a Consistency Group?
  6. You cannot remove additional local storage from a Cloud Server if the Server is in a state which requires it to be restarted. See How do I determine if my Server Requires a Restart Using REST API?

Content / Solution:

  1. From the Home page, select the Data Center where the Cloud Server from which you want to remove Additional Local Storage is located:


  2. The Data Center dashboard will be displayed. Click on the Network Domain (MCP 2.0) or Network (MCP 1.0) where the Cloud Server from which you want to remove Additional Local Storage is located:


  3. The Network Domain (MCP 2.0) or Network (MCP 1.0) Dashboard will be will be displayed. Click on the Server from which you want to remove Additional Local Storage:


  4. The Server dashboard will be displayed. Click the Storage tab and locate the Disk you want to remove. Click on the Manage gear next to the disk, and select Remove Disk from the drop-down menu:


  5. The system will display the Remove Disk confirmation dialog. Click Remove:

    Note: This action can not be reversed and will result in total loss of data on that disk!
    Note: This process will take several minutes.
    Note: You cannot remove storage when a System Snapshot is in progress. This will cause the Snapshot to fail.
    There is no way to know 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 deletion of storage around the window

     

  6. The system will display a message indicating that the operation is in progress:


  7. The system will display the progress of the operation in the Status section of the Server dashboard:


  8. Once complete, the system will display a success message:


  9. The Disk will be removed. The changes will be reflected in the Storage pool, and the Server Details tab will be updated to show the updated amount storage: