We have a nightly warm spare backup setup to copy everything over to our secondary server. Recently we had some updates on our primary server, and I’m wondering if major updates could break the warm spare if certain files are copied over via the backup instead of actually running updates on that secondary server.
What is the best practice here? Should I always run updates on both systems? I’d like to have a way to “test” updates to make sure I don’t have any problems in production.
My thinking was that I could run updates on the primary first thing one morning (or after hours). Do a basic sanity check, and if all seems well, let business run on it that day. Then if still no issues, the warm spare backup would synchronize the changes to the secondary server.
But if we encountered unrecoverable errors (for some odd reason) during that day, I would have the “warm spare” as a failover option. Just preparing for worst-case scenarios.
Exactly how I do it except that after that day of testing updates on the primary. If everything goes well I do the update on the warm spare before I synchronize it with the primary. This way all modules etc are on the same ver before synch occurs.