Andy's VMware vSphere tip#12:BACKUP Not matter how simple, or quick you think a change will be to a production machine, in service, First STOP! Ensure you have a Full Backup or CLONE (not a Snapshot) before you proceed changing any VMware Virtual Machine in production, and should any change fail, you can quickly rollback to the working VM. e.g. today a simple change to defragment a VM, which was causing performance issues, caused the NTFS file system to become corrupted, and the VM failed to boot with a BSOD.
Simply, rolled back with a CLONE, that was taken before the change!
Good IT Practice...Don't look like a cowboy to your peers! IT has a bad enough reputation as it is!
If you would like to discuss this post further please post a question to the VMware Topic area.
Simply, rolled back with a CLONE, that was taken before the change!
Good IT Practice...Don't look like a cowboy to your peers! IT has a bad enough reputation as it is!
If you would like to discuss this post further please post a question to the VMware Topic area.
1 Comment
Recommended Posts
Exchange Server Roadmap Update.
MS have moved the release date for the next version of Exchange Server to the second half of 2025.
It requires Server and CAL licenses and will be accessible only to customers with Software Assurance,
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-roadmap-update/ba-p/3421389
MS have moved the release date for the next version of Exchange Server to the second half of 2025.
It requires Server and CAL licenses and will be accessible only to customers with Software Assurance,
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-roadmap-update/ba-p/3421389
