Aar
Verified User
Opinions are divided, yet I was curious about how you handle server updates. First and foremost, of course, critical updates are executed immediately or temporarily mitigated.
But in general, I was wondering how you handle updates? It is, after all, a process that can cause brief downtime in some cases. Do you do this during the day or at night, or do you have special maintenance windows during which this is performed? How often do you perform the general system update?
And how often, in what manner, and according to what pattern do you update DirectAdmin and its components? And do you perform the updates one by one, or all at once with ./build update_versions? Or sometimes a ./build all d? And did you use scripts?
I have my own server for myself and a few clients, and normally I perform the standard system update every week, and the DirectAdmin components a few times a month via the custombuild ('da' command now), and monthly the ./build update_versions. And in case of severity, as soon as possible.
I am curious about your strategy. Maybe we'll learn from it someday.
But in general, I was wondering how you handle updates? It is, after all, a process that can cause brief downtime in some cases. Do you do this during the day or at night, or do you have special maintenance windows during which this is performed? How often do you perform the general system update?
And how often, in what manner, and according to what pattern do you update DirectAdmin and its components? And do you perform the updates one by one, or all at once with ./build update_versions? Or sometimes a ./build all d? And did you use scripts?
I have my own server for myself and a few clients, and normally I perform the standard system update every week, and the DirectAdmin components a few times a month via the custombuild ('da' command now), and monthly the ./build update_versions. And in case of severity, as soon as possible.
I am curious about your strategy. Maybe we'll learn from it someday.