We recommend creating VDisks according to data store configuration and spread stripe sets (replicas) over different compute resources so that if a compute resource goes down another should be able to run the content after the VS is migrated (if it was hosted on the compute resource). Create several data stores and group the disk drives based on performance levels (e.g. keep SSD separate from SATA to avoid wasting IO throughput for synchronous writes).
To add a new disk to the integrated storage data store in case your compute resource does not support hotplug::
- Make sure that all VDisks are fully synced. Perform repair if it is required.
- Migrate all virtual servers from the compute resource to which the drive(s) will be added.
- Shut down the compute resource and connect the disk drive(s). Some VDisks will degrade - this is the expected behavior.
- Start up the compute resource.
- Once the compute resource boots, ensure that the drive is ready for use in the Storage platform.
- Assign new drive to the free storage controller via OnApp User Interface. If you are assigning a new drive, the drive should be formatted. The drive's SCSI identifier parameter indicates if the drive has been previously identified.
Enable the new drive(s) via OnApp User Interface, for more information refer to Manage CloudBoot Compute Resource Devices.
Repair all degraded disks:
Migrate virtual servers back to compute resource.
In case your compute resource supports hotplug, simpy install the new storage drive to the server and assign the new drive(s) via OnApp User Interface. For more information refer to Manage CloudBoot Compute Resource Devices.