New Server Migration Adventure
-
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
VM1: Active Directory / DNS / DHCP
Easy. Make a 2016 AD DC, add it to the pool, move roles, shut the old one(s) down.
Excellent...note - my file server also has an alias so it will help. There are a few things in our network (copiers and Docuware) that would only work with the primary DNS name, so will need to be aware of that.
-
@garak0410 said in New Server Migration Adventure:
VM2: File Server / VPN
Remove VPN from that. That doesn't belong there.
File servers are pretty easy. Normally the shares are trivially easy. Script that out and just do a file transfer.
-
@garak0410 said in New Server Migration Adventure:
VM4: SQL Server 2014
Script a fresh install. Then just restore a backup of the old database.
-
@garak0410 said in New Server Migration Adventure:
VM3: Backup Server (just runs backup software and copies to NAS...runs Veeam / Backup Assist)
Fresh install might be all that is needed here.
-
@scottalanmiller said in New Server Migration Adventure:
So an example, let's say you have a simple Windows Web Server... Just 2012 R2 running IIS for a .NET application or something like that.
I'd want to create a clean 2016 build and have a script that sets up absolutely every aspect of the system without any human intervention (other than running the script, obviously) and either builds the entire system 100% or builds it to a point that all you have to do is restore the application files.
I know when adding roles, you eventually will have an opportunity to save an xml config to use for redeployment.
-
Is your file server set up with two virtual disks? one for OS and the other for data only? Because will be one easier move.
-
Is there a possibility of doing a live migration or configuring Hyper-V Replication to the VRTX setup? Then you can upgrade to 2016 at your leisure.
That being said, if your other plans include any down time I would go ahead and spin everything up a 2016 as part of that.
-
@garak0410 Assuming everything is staying on the same hypervisor platform, I would simply move your existing workloads and shutdown the old hardware.
Then you can migrate the workloads as a separate project.
Mixing projects is generally a bad idea IMO.
-
Thanks for all of the tips thus far. I may have to rush this migration now...
I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.
I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.
-
@garak0410 said in New Server Migration Adventure:
Thanks for all of the tips thus far. I may have to rush this migration now...
I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.
I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.
Moving from two physical machines down to one, seems like an odd move. When this one starts to die, a migration off of it will be even more dramatic.
-
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
Thanks for all of the tips thus far. I may have to rush this migration now...
I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.
I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.
Moving from two physical machines down to one, seems like an odd move. When this one starts to die, a migration off of it will be even more dramatic.
Moving to a Dell VRTX with 2 nodes...not that makes it easier to migrate off of that one day but very glad to have it.
-
@garak0410 said in New Server Migration Adventure:
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
Thanks for all of the tips thus far. I may have to rush this migration now...
I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.
I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.
Moving from two physical machines down to one, seems like an odd move. When this one starts to die, a migration off of it will be even more dramatic.
Moving to a Dell VRTX with 2 nodes...
Exactly, one system to fail instead of two.
-
@garak0410 said in New Server Migration Adventure:
...not that makes it easier to migrate off of that one day but very glad to have it.
Your glad to have a VRTX inverted pyramid? Why? I'd think you'd be livid that someone bought that for your environment. Why are you not upset?
http://www.smbitjournal.com/2015/11/understanding-the-role-of-the-dell-vrtx/
Edit: Livid within the scope of understanding it isn't your money or your risk, so not really your problem. But still, not happy. The VRTX is fun to work with, so that's a positive regardless of its applicability to the SMB space.
-
I assume this for your main infrastructure. A VRTX in a ROBO for capacity needs is different, where reliability isn't important. The VRTX has a bad track record of being unreliable even within the scope of being an unreliable inverted pyramid design.
-
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
...not that makes it easier to migrate off of that one day but very glad to have it.
Your glad to have a VRTX inverted pyramid? Why? I'd think you'd be livid that someone bought that for your environment. Why are you not upset?
http://www.smbitjournal.com/2015/11/understanding-the-role-of-the-dell-vrtx/
I'd have to be upset at myself. I made the final decision after months of negotiating on cost and features. I really tried for a good R730 with Azure as our DR but they didn't want to pay the yearly license. Add this to the Dev projects they push me on, I had had to juggle many things but also try to make the best decision I could.
-
@garak0410 said in New Server Migration Adventure:
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
...not that makes it easier to migrate off of that one day but very glad to have it.
Your glad to have a VRTX inverted pyramid? Why? I'd think you'd be livid that someone bought that for your environment. Why are you not upset?
http://www.smbitjournal.com/2015/11/understanding-the-role-of-the-dell-vrtx/
I'd have to be upset at myself. I made the final decision after months of negotiating on cost and features. I really tried for a good R730 with Azure as our DR but they didn't want to pay the yearly license.
Why did you compare a VRTX with no DR against a cloud DR alone? Why not just a R730, or two R730? That's not an apples to oranges comparison with the single device VRTX.
Any why Azure for DR? Azure is, even within the cloud space, extremely expensive. You can do DR for a fraction of the cost without that annual fee.
But given that the result is not to have DR, the proper comparison would have been other "non-DR" solutions.
-
@garak0410 said in New Server Migration Adventure:
Thanks for all of the tips thus far. I may have to rush this migration now...
I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.
I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.
You are making a huge mistake by mixing the tasks. You new hardware can run everything twice or more, I would assume.
So just migrate the VMs to stable (I won't call it good) hardware that will not up and suddenly die (most likely).
Then, next weekend, worry about building Server 2016 and migrating roles.
-
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
...not that makes it easier to migrate off of that one day but very glad to have it.
Your glad to have a VRTX inverted pyramid? Why? I'd think you'd be livid that someone bought that for your environment. Why are you not upset?
http://www.smbitjournal.com/2015/11/understanding-the-role-of-the-dell-vrtx/
I'd have to be upset at myself. I made the final decision after months of negotiating on cost and features. I really tried for a good R730 with Azure as our DR but they didn't want to pay the yearly license.
Why did you compare a VRTX with no DR against a cloud DR alone? Why not just a R730, or two R730? That's not an apples to oranges comparison with the single device VRTX.
Any why Azure for DR? Azure is, even within the cloud space, extremely expensive. You can do DR for a fraction of the cost without that annual fee.
But given that the result is not to have DR, the proper comparison would have been other "non-DR" solutions.
Stop beating a dead horse.
-
@jaredbusch said in New Server Migration Adventure:
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
@scottalanmiller said in New Server Migration Adventure:
@garak0410 said in New Server Migration Adventure:
...not that makes it easier to migrate off of that one day but very glad to have it.
Your glad to have a VRTX inverted pyramid? Why? I'd think you'd be livid that someone bought that for your environment. Why are you not upset?
http://www.smbitjournal.com/2015/11/understanding-the-role-of-the-dell-vrtx/
I'd have to be upset at myself. I made the final decision after months of negotiating on cost and features. I really tried for a good R730 with Azure as our DR but they didn't want to pay the yearly license.
Why did you compare a VRTX with no DR against a cloud DR alone? Why not just a R730, or two R730? That's not an apples to oranges comparison with the single device VRTX.
Any why Azure for DR? Azure is, even within the cloud space, extremely expensive. You can do DR for a fraction of the cost without that annual fee.
But given that the result is not to have DR, the proper comparison would have been other "non-DR" solutions.
Stop beating a dead horse.
It's not dead if he was unaware of it. If it was a dead horse, he'd have been aware of the issues.
-
@garak0410 said in New Server Migration Adventure:
Add this to the Dev projects they push me on, I had had to juggle many things but also try to make the best decision I could.
I realize this is now a post mortem situation, but I'd say that this is a really important time to take a moment and dig into decision making processes as this is, like any port mortem, an important learning exercise to look at how the process was done, what could be improved, where things went wrong, etc.
Some thoughts:
- You posted about having bought a VRTX and how to use it, but didn't post about considering buying one. We'd have stopped you instantly as it is a known "never for use in the SMB" product that has been heavily vetted for years. We could have sped up your decision process around that from months to seconds. It has been covered, as Jared pointed out, quite a lot. We have lots and lots of resources about it ready to go, both research and discussions. And in multiple communities.
- How did a VRTX or an IPOD get on your consideration list, why was it on the short list?
- Why did totally different solutions get put on the short list, but not normal ones (like hyperconvergence, stand alone servers, etc.?) While common solutions aren't for everyone, the standard approaches are generally worth at least a brief consideration if only as a comparison point or a "stick in the ground" so that you have a cost and complexity guideline to work against. In this case, you had two extremely disparate and non-standard solution paths that were very difficult to compare directly, and none of the ones more similar to either to see if those were good representatives of their "style".
