Why can't I resize to a smaller server option from a snapshot?

August 5, 2015 1.3k views
DigitalOcean Server Optimization FreeBSD

I made a small FREEBSD 10.1 server (5$/mo plan). I installed FAMP stack manually. I took a snapshot. Now, I KNOW FOR A FACT that a FreeBSD installation isn't even CLOSE to 20gb (more in the range of a 800MB image, maybe a 2GB install MAX). That being said, copying a very minor-ly changed FreeBSD install wouldn't be the difference between 20GB and 30GB. Not even close. So why is it telling me I need a 30GB install to use snapshots that were MADE AND ARE CURRENTLY HOSTED ON a $5/mo plan? This, to me, is charging more for FEATURES and is not advertised anywhere when you initially "sign up for this" type of ecosystem.

By the way, I tried the FreeBSD FAMP premade option and it won't allow me to install it on a 20GB server ($5/mo) just like the snapshots. I'm hoping sincerely that this is an OVERSIGHT and not an intentional money-grab. If you want to restrict features on the $5/mo option, then SAY SO from the get-go, don't make it a nasty surprise to restrict a person's options after the fact.

  • Are 512MB droplets available in the data centre you're attempting to restore the snapshot to?

  • Yes, and I tried it in multiple areas as well (only going between New Yorks 1-2-3, mostly 3, and San Fran). Thank you for your suggestion, though.

1 Answer

If you created your snapshot on a 512MB droplet it should be able to be deployed to another 512MB droplet. Some data centers (AMS1 in particular) do not support FreeBSD droplets.

It is not possible to create a snapshot on a larger droplet (1GB for example) and then deploy it to a smaller droplet (like a 512MB one). This is due to potential data loss when shrinking a partition on the disk image. This doesn't sound like what you are encountering though so I would recommend opening a ticket with our support team so they can investigate.

Have another answer? Share your knowledge.