| SYSTEM INFORMATION | |
|---|---|
| OS type and version | AlmaLinux 8.8 |
| Webmin version | 2.021 |
| Usermin version | 1.861 |
| Virtualmin version | 7.7 Pro |
| Theme version | 20.21 |
| Package updates | All installed packages are up to date |
Just wanted to give credit where credit is most certainly due!
Last night my main server running virtualmin lost upstream connectivity for what turned out to be about 10 hours.
When I couldn’t get a reliable restoration timeframe from our datacenter I decided to restore all critical sites to my development/hot spare vm that was running the same OS (Almalinux 8.8) as our primary server.
The process was absolutely seamless and fantastic! It has been a few years since something catastrophic like this has happened so was a good exercise in seeing first hand the most recent virtualmin updates in this area.
- All virtual servers were restored perfectly and magically the shared ip’s from the original server were updated to the new.
- No external ip’s were changed.
- The primary name server ip was also magically updated to the new server. I note this as I remember a few years back having to do some manual intervention here – that is a thing of the past.
- All I really had to do post restore was update the glue record at my name server domain registrar and within the ttl time of that zone traffic was flowing to the new server.
All in all, virtualmin was bloody brilliant and I could not be happier with its current state of functionality and reliability. Now I should probably figure out how to automatically sync updates from the primary to backup server so I could have skipped the uploading backups from the cloud to the vm. Probably should also spring for a pro license on that backup/development vm.
Cheers virtualmin team!