I would like to know:
in case you have to do planned/scheduled maintenance (reboot, replace hw, etc) on a physical host, do you:
a) notify the owners of the droplets? b) shutdown the droplets and reboot - or do you use some save-and-restore-vm-state-to-disk feature of the hypervisor - or do you move the vm’s to another physical host?
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.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hello, all
I know this is an old question but it’s still something that people quite often ask so I want to update it.
The same question was recently answered from member of our support here:
https://www.digitalocean.com/community/questions/what-will-happen-to-a-droplet-when-the-host-machine-needs-maintenance
I will also post the original answer as well:
Generally if it is Droplet maintenances, we generally tend to perform Live migration , where there is no downtime on the Droplet. If in case, there is an issue with Live migration, then we opt for offline migration.
Refer to below link:
https://www.digitalocean.com/docs/platform/live-migration/
If it is a network maintenance, then there would be a small latency issues on the network packets but the Droplets should work as expected.
Hope that this helps! Regards, Alex
There are different kinds of maintenances that we sometimes need to do that have differing maintenance windows and allowed time for action. <br> <br>In each case customers are notified by email regarding the maintenance listing the affected droplets, the reason for the maintenance, what the possible impact may be, and whether or not any action will be taken on the specific virtual servers. <br> <br>Some maintenances, such as network, do not require the virtual servers to be shutdown in anyway, while others like migrating to a new hypervisor do. On occasion this means that the VM will be powered down and then migrated to another hypervisor - we also do port checking before and after, to make sure that the open listening ports prior to the migration are once again open and listening after. <br> <br>
I’ve been notified of maintenance by email which is good enough for me. Not sure about the second one.