Data & Storage - Public Cloud [EN]
- 1 Q1. I was on a Storage Optimized plan. What if the new plan has less storage?
- 2 Q2. How do additional volumes work? How much do they cost?
- 3 Q3. Will all my files be preserved after migration?
- 4 Q4. Will the amount of available storage on my VM change?
- 5 Q5. Can I increase or decrease storage after migration?
- 6 Q6. What happens to my backups?
Q1. I was on a Storage Optimized plan. What if the new plan has less storage?
On the new platform, instead of fixed Storage Optimized tiers, you can flexibly expand storage by attaching additional volumes. Your VM's total storage depends on the size of the boot volume and any attached additional volumes.
If the base storage in your new plan isn't enough, you can attach one or more additional volumes of the size you need via the control panel or, if required, through Terraform.
Q2. How do additional volumes work? How much do they cost?
An additional volume is a separate virtual disk you attach to your VM for storing data (databases, media files, backups, etc.).
Pricing depends on the storage type and size:
Fast NVMe SSD - for frequently accessed data and high-load workloads
Cost-effective HDD - for less critical, less frequently accessed data
Storage included in each plan and additional storage pricing can be found on the pricing page.
Q3. Will all my files be preserved after migration?
During migration, we transfer the entire block storage contents to the new server exactly as-is.
This means technical artifacts such as old log files or auxiliary service data will also be migrated.
If you know your server has old logs, temp directories, or other unnecessary data, we recommend cleaning those up before migration. It'll speed up the process and reduce downtime.
Q4. Will the amount of available storage on my VM change?
No, it won't. When our team performs the migration, a volume of the same size you had before will be created on the new platform.
Q5. Can I increase or decrease storage after migration?
Volumes can only be expanded - shrinking a disk is not possible. This is an architectural limitation: the filesystem inside the VM already occupies space, and reducing the block device from the outside would almost certainly cause data loss or filesystem corruption.
You can increase both the boot volume (used for the OS) and any additional volumes.
If you need to free up space or get rid of an oversized volume, the workaround is to create a new, smaller volume, move the data you need to it, then delete the old one.
Q6. What happens to my backups?
Websa snapshots will not be transferred to the new platform.
If backups were stored on your server, they’d be migrated along with the entire VM filesystem.
You can set up automated backups on the new platform if needed.
If you're using external backup systems, make sure they're correctly pointed at the new server (by IP/domain and credentials) after migration.