Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Hello Matt,
Full disclosure I run a product called SnapShooter which takes backups of DigitalOcean servers.
I have noticed this issue with a couple of my customers over the last couple of months. They were getting bigger and bigger backups. We have contacted DigitalOcean to find out more information.
From Support Essentially, it’s not unheard of for a Snapshot’s size to vary and not reflect the used disk space amount on the Droplet. For instance, if you’re written a lot of data but later deleted it, that space isn’t automatically zeroed out in the disk.
Now one of my customers was getting the same issue with 10gb of diskspace working its way to 85gb. He got the same answer from support, but discovered on his own that a system reboot fixes the issues.
We are still working with DO to get an answer on this as it never used to happen. If I hear any more I will reply again.
Regards
Simon
Sounds like it might be a good idea for DigitalOcean to add the suggestion of rebooting the droplet before creating the snapshot, to their snapshot instructions.
Wayne Sallee Wayne@WayneSallee.com
Check your logs. I have seen instances where log files are huge in size.