how to avoid down time during maintenance activity

I have a stand-alone droplet, how can I avoid downtime during scheduled maintenance.

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Hello, @kapahimansi0

There are different kinds of maintenances that we sometimes need to do that have differing maintenance windows and allowed time for action.

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.

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.

Hope that this helps! Regards, Alex

Hi there @kapahimansi0,

This would really depend on the type of maintenance that you would be performing. For example if you are upgrading your Droplet’s Kernel and then rebooting, you can’t avoid downtime unless you add a second Droplet and a load balancer.

I would recommend reading this tutorial on what Load balancing is:

It is a great introduction and will give you useful information on how to get started.

Let me know if you have any questions. Regards, Bobby