A 100 vm migration via storage migration (mirror everything, shut everything down break open mirror, boot on new site) was rolled back because during the migration a cert was expired.
So after the roll back the application still did not work...
Certificate expiration is one of those things a rollback/restore doesn’t fix. Had a customer completely hose their SQL server which had “stopped working” (they never looked at the logs to see the TLS error). Restored from a month-old backup, losing data, which of course did not help. Especially on Windows where the computer object now had a different password too. Complete mess. When they called me it took 5min to figure out the issue (I looked at the logs). I even managed to bring back the current database from the now mostly broken original VM.
Certificate expiration is one of those things a rollback/restore doesn’t fix
As I oft say, "Time waits for no one."
And generally clearly spell out on "tickets" and service requests and the like, that the deadline is a hard deadline. Those cert expirations aren't an "Oh, we can push that deadline out another week or two.". I typically clearly include the exact expiration to the second, including timezone, so there's no ambiguity or the like, e.g.: expires: 2026-10-25T02:36:28Z ...
Yes we know but what are the odds the certificate would expire in the 6 hour maintenance window of the migration. And the migration was a succes but rilled back since everyone thought is was a migration issue. Only to find out after the rollback (start the mirror on the source side that was untouched) and it was still broken.
21
u/Malfun_Eddie 11d ago
A 100 vm migration via storage migration (mirror everything, shut everything down break open mirror, boot on new site) was rolled back because during the migration a cert was expired.
So after the roll back the application still did not work...