Make sure services don't start after update (failover server)

[CloudAware]

Hi all,

We are doing our own failover with two servers. One server has the active DNS record with a very short TTL. This works perfectly. The only thing we need to do to failover is change the DNS, restore the latest backup (already sftp-ed to the backup server every night) and activate all services.
For too many reasons (not only technical) we are unable to use 3CX's failover system.

Monday we found out that the services on the failover server had started after an update. This was quickly fixed, but how can we make sure that the services on the failover server are not started, but updates are installed periodically (so turning it off is not an option).
Thank you very much!

 

[NickD_3CX]

Hi all,

We are doing our own failover with two servers. One server has the active DNS record with a very short TTL. This works perfectly. The only thing we need to do to failover is change the DNS, restore the latest backup (already sftp-ed to the backup server every night) and activate all services.
For too many reasons (not only technical) we are unable to use 3CX's failover system.

Monday we found out that the services on the failover server had started after an update. This was quickly fixed, but how can we make sure that the services on the failover server are not started, but updates are installed periodically (so turning it off is not an option).
Thank you very much!

Hi!

Short version is, if you are running on Debian, I don't think you can.
I am assuming that you are basically stopping all services and have them ready to start when you need it.
Debian on update I believe overwrites the .service files, which I think in turn overrules any "disabled" services you may have set.

Windows on the other hand, if you set a Service to "Disabled", that will "stick" across Service Pack updates because Windows is a bit weird with executables editing their own services (partially the reason why major updates need a re-install on Windows...).

Your best bet if you are on Debian is to try the "disable" or some variation of it, but at this point I have to say that this is not something tested and, although I *don't think* it should cause a problem, I can in no way guarantee it.


Safe Choice Alternative...
Just don't automate updates... Now that you are aware of this, disable auto-updates on your "passive" server and do them at a controlled time and environment.