I recently decided my home server was a little much for my needs. While the dual Xeon and 48GB of memory was ample for me years ago, I find I spend less time at home and more time at work in regards to testing. Because of that, I of course got excited and delved into looking at new hardware.
I liked the ML150 G6 I had been using, so I opted into purchasing two ML110 G6, same design and build, however only a single Xeon and capped at 16GB of memory. With SSD so cheap, disk isn’t and shouldn’t be a concern for anyone.
Of the two I purchased, one was the “main” machine, holding the 16GB of memory I needed for a few VM’s and a single build of SP. The other held disk resources, admin and the replica partner… aw, they are getting married! The replica housed much more disk space and way less memory. In the event of a failover, it would keep the lights on, relatively speaking, albeit slow due to the RAID5 and 6TB volume the VM’s were sitting on. I wasn’t too worried as it would only take a few hours to rebuild it all anyways.
After installed Windows 2012 R2 and getting Hyper-V up and running with the exact same configuration. Replication setup was relatively simple, painless and easier than I expected since my time with VMware had shown it shouldn’t be “that easy”. The steps to configure a partner in the same domain involved a few simple steps, selecting a server and some easily understood configuration options. They were in the same domain, plus, I used CredSSP, plus plus, all other settings were best recommendation and made sense to me, plus plus plus.
And now on to the not-so-fun-parts.. Some things I didn’t like…
- Because I am picky about paths being the same between servers, I ended up completing the following list so that all the disks and configuration was in the same path. I know… why do I do this, I blame the internet or too many cartoons as a kid.
- replicating to replica server
- removing replication on replica server
- re-setup replication to original primary server
- replicate from replica to primary
- removed replication
- cleanup up replication on initial replica server
- Re-setup replication
Overall, a good and quick experience. Now my VM’s are relatively safe (meh, who needs backups) from disaster.