Take a snapshot without shutting down
Find a way to enable snapshots to be taken without shutdown. It causes a lot of issues, especially with production projects.
You should provide this especially user need to shut down their server to take this.
If you can't provide specific time, you also can provide the queue number to tell us if I shut-down now, how many user behind me to taking snapshot.
Because I have clients who pay me to not bring down their websites multiple times a day. Because my DB server hasn't seen 5minutes of downtime in the last 6 months.. never mind 6x/day for 4hr snapshots.
Samuel Lewis commented
It takes like 5 minutes... why worry?
Michael Hicks: You're combining two separate operations. On AWS you can snapshot an EBS volume or create an AMI. Snapshotting is a low-level storage operation that doesn't affect the machine.
Creating an AMI _can_ reboot the machine in the process, but it isn't required. They recommend it but give you the option to do it w/o reboot if you're prepared to deal with possible data inconsistencies yourself.
Michael Hicks commented
FWIW, I've noticed that my EC2 instance always reboots after I snapshot to AMI. I don't have to shut down beforehand, but I assume they are making that happen automatically as part of the AMI snapshot process.
Mikhail Emelchenkov commented
Shutting down, seriously? Wow, I did not expect to find so much reefs in Digital Ocean :)
Alex Pole commented
Agree that this should be top priority! Especially today where I find myself coming up on 2 hours of downtime waiting for a snapshot to process due to scheduler issues. Refunding downtime is one thing, but there is no way to refund time wasted when your customers are supposed to be working and can't bring their site back up or even cancel the snapshot!
I want to give you my business but can't until this happens... shutdown for snapshots != production ready.
We're going to be working towards that in the future so that all snapshots and backups are processed from running droplets with minimal impact and while still retaining disk consistency on the taken snapshots.
There is no queuing system to the snapshots the issue with the variable amount of time it takes is due to the difference in amount of content that users may have placed on the server.
The more files, smaller files, etc that a server has the longer the snapshot takes to complete.
Dirk Postma commented
+1 Nobidy wants *downtime*, esp. when the reason is making a backup!
Temporarily running another droplet is no easy option because... you need fresh data (a snapshot?) for that.