NVMe Block Storage
with triple-copy redundancy

No, the three copies protect against hardware failure. If a node dies, your data is intact on the others. But this does not protect against a mistake, a bad deploy or corruption, because that change replicates to every copy. The two included snapshots give you a point to roll back to, and offsite backups keep a separate copy for anything the platform itself can't cover.

Each disk comes with two snapshots, point-in-time copies you can roll back to. The usual pattern is to take one right before something risky, an OS upgrade, a schema migration, a config change, so you can return to a known-good state quickly if it goes wrong. For longer retention or a copy on separate infrastructure, add offsite backups.

Yes. You can increase a volume's size at any time and your data stays in place. Once the volume has grown, you must extend the filesystem inside the VM to use the new space.

Yes. The boot disk is a Block Storage volume, and you can attach more volumes to the same VM. Keeping application or database data on a separate volume from the OS makes it easier to resize and snapshot that data independently.

Yes. It's NVMe-backed and built for low-latency access from the VM it's attached to, which suits database files, busy application data and boot volumes. Unlike a single local disk, every block is written three times, so you get that performance with durability built in.