What is the difference between scaling up an EVS and creating a new one?
You can scale up the EVS space by scaling up the EVS or creating a new one when space on a cloud server is insufficient. The following shows the difference between them. You can select either of these two method according to your business needs.
· Scaling up EVS refers to expanding the capacity of the existing EVS. After scaling up, you must scale up the partitions and file system for the original EVS.
· Create a new EVS and mount it to a cloud server. This EVS resides in the same cloud server as the original EVS, but the two EVS disks have no direct relationship.
Can an EVS be scaled down or temporarily scaled up?
No.
EVS disks including system disks and data disks can be scaled up. A system disk can be scaled up to 2048 GB and a data disk can be scaled up to 32 TB. But an EVS cannot be scaled down or temporarily scaled up.
Will data be lost when an EVS disk is scaled up?
Data will not be cleared when system and data disks are scaled up. Data error may occur due to misoperation during scaling up. Therefore, please exercise caution with this action. We recommend that you back up data before scaling up. You can back up data using the following two methods.
· For more information on the usage of VBS, see Volume Backup Service (VBS).
· For more information on the usage of VBS snapshot, see Creating VBS Snapshot.
Why does the capacity of the EVS on the cloud server remain unchanged after scaling up?
Only the storage capacity of the EVS is expanded after you scale up the capacity in the console. You must log in to the cloud server to scale up the partitions and file system. Newly added capacity becomes available only after these operations are done.
For more information on how to scale up the partitions and file system, refer to:
What if the EVS capacity is insufficient?
If the EVS capacity is insufficient and services may be affected, see the following to address the problem:
· Purchase an EVS disk as a data disk, mount it to an elastic cloud server, and then initialize it. For more information, see Creating EVS.
· Scale up the existing EVS. Both system disks and data disks can be scaled up. For more information, see Scaling up EVS.
· Clean up unwanted programs or files in the current EVS to release the space. For more information, see Addressing the Problem with Insufficient Space of Linux-based Cloud Server and Addressing the Problem with Insufficient Space of Windows-based Elastic Cloud Server.
What if scaling up fails? Will the service be charged?
EVS is charged based on the actual usage duration, subscription cycle, and capacity.
When scaling up an EVS fails, the capacity change fails, the capacity that is being charged remains that before scaling up. Capacity that is expected to be added but is not added will not be charged.
If scaling up fails, contact the eSurfing Cloud customer support and submit a ticket as soon as possible.