Friday, October 17, 2014
on my local machine
Today the lesson is to have a plan to restore your local machine in the least intrusive way. I had a drive failure this week. I was able to back up files before replacing a single drive with 2 smaller SSD drives. I put all user files on the second drive and all install filed and progs on the C drive. I have some options ahead of me with respect to a backup plan for files. I can add a mirror drive or schedule backups to a network drive or both. That's the easy part. The harder part is to reinstall all the software. The desktop team will install the OS and all the basics, and I get to add all the dev tools. That takes at least a day. option is to use virtual machines. The whole team would benefit from that strategy since the image would have all the software installed. If anyone needs a vm with the developer image, there it is. Tough part is to keep the image maintained with all the updates and new tools. Yet another option is to install via a script. With a script install the latest versions of all the goodies would be kept on a file share. The script would point to the latest (rename latest-whatever-setup.exe or .iso or .msi). Or the script would read a config file located on the share. The script would compare already installed software against the config and install/update as necessary. This approach would be slower, bit less maintenance than an image. Why not combine the last two? Maintain the central list for updates and keep a clean image vm somewhere that runs the script (or do that manually after every update has been tested). This way, any catastrophic failures can be recovered from, and all devs can update to the latest and greatest with a click of a button.