Hi Mihir, Years ago i thought also around how to handle the ESX(i) to get back once crashing. i could circle in every Direction, but i come to the End that "Trying to backup some configs" ...
See more...
Hi Mihir, Years ago i thought also around how to handle the ESX(i) to get back once crashing. i could circle in every Direction, but i come to the End that "Trying to backup some configs" > theire is the Single Point of Failure following. - Getting 100% every file which is necessary to get the config back once crashing - At a Major relase change > maybe this dependend files are changing or extending - Restore/Backup Configs, maybe causing a Kind of Instability,............ - Not sure if Vmware is supporting it 100% backuping config and to restore it Anyway, my own Solution is following. Instead of Backuping config and trying to restore it > i kill 2 flys with 1 Slap. - Fast Restore (But from Mind that's an Fresh install and pushing the scripts,....) - Update Processes. (Fresh install with new Build Number) i use PXE Kickstart solution. The Server is much more stable . What i have done: - Windows 2012 R2 with IIS + WDS - Using 2 Shares 1x for WDS 1x for IIS IIS Share = 1: Hostcfgs (Kickstart Files for each Host) 2: Patch (placed the latest Update file) 3: Scripts (Host file, ntp file, advanced settings, portgroups,.....) WDS Share = default windows deployment share where i place the extracted iso binary and the pxelinux.cfg menu files,.... So at all. once i have a strange problem. i push the kickstart stuff and have following - Full fresh installed with ALL Configs as before And once a new Major Relase is out > it's easy to integrate it into PXE. So you have only an initially effort and you need to maintain the Patches (or creating everytime new Source). PS: Don't forget, you have to be sure that the System is Stable. And with a Kind of Backup/Restore > you never 100% could be sure that's the Case. Because you know theire lot of Object ID's in background,....... . Only with such kind of Solution i could be 100% sure that i have everything covered. "vicfg-cfgbackup" is a nice idea > but never i would rely completely on it. Just a Feedback to think in other Direction. Best regards Max