DisabledRAM : 7.8 GiBSwap : 0.0 KiBDisk : 503.9 GiBDistro : Debian GNU/Linux 13 (trixie)Kernel : 6.12.90+deb13.1-amd64VM Type : KVMIPv4/IPv6 : ✔ Online / ✔ OnlineIPv6 N

DM me and we can adjust the disk space.

RAID 1 for that profile makes sense, and the reason lines up exactly with your worry about a full-day restore: RAID 1 is really about shrinking the restore window, not about data safety. A single disk

100 GB High-Speed ​​SSD Storage

EnabledRAM : 967.9 MiBSwap : 2.0 GiBDisk : 9.7 GiBDistro : Debian GNU/Linux 13 (trixie)Kernel : 6.12.86+deb13-cloud-amd64VM Type : KVMIPv4/IPv6 : ❌ Offline / ✔ Onlinefi

The VM6 guarantee: No overselling on RAM or disk. Generous CPU policy and a concrete compensation clause in our SLA for unexpected downtime. What you buy is what you get — backed by 24/7 UK-based supp

🚀 500Mbpps Connection (After Bandwidth Allowance used, speed decreased)

(Quote)

And I orfered a 7950x server on UT, please help me double the disk (12TB -->22TB) and double the traffic (330TB --> 660TB)

Basically for transparency if we give you 2TB NVME we would be giving you our entire server disk space for $80, therefore we can't allocate anymore users on the server, and the rest of the CPU and RAM

And I didn't find something comparable anywhere else, even for clearly more money — usually it was same or even worse on some things (disks for example, which here are also very good).

know how the format is constructed, virtual disk is nothing but a fancy term for file, partition and so on, so i don't really see why it shouldn't be possible to shrink it. Just truncate the file, sh

You CAN shrink the partition, if you're careful enough about the boundaries (the risk of dataloss is still there have to be extremely careful), but you wouldn't be able to shrink the virtual disk itse

Well, i'm pretty sure you can. It just needs cooperation from the guest's side and is a little hairy (tbh i don't know if that would work on qcow2 backed disks but for anything using raw images it sho

@Homwer You cannot shrink a disk on a KVM machine.

(Quote)

For example that starting plan has 12GB of (DDR5) RAM, 40GB of NVMe disk, includes a dedicated IP, 3 off-site (duplicated) backups, and 5 MySQL Databases. Plus advanced application filtering and Sourc

If you have a good backup strategy and 24-48 hr downtime is not an issue for u, then u can go with a singe disk.

If a few hours of downtime while you re-provision and restore is acceptable (personal projects, dev boxes, anything non-customer-facing), a single NVMe is genuinely fine and lots of people run exactly

Small pro tip for lazy people: You should be able to shrink your root partition (including the fs) to something that fits your new dedi/vps (do it from rescue) and then just copy the disk image (somet