Server 2008 w Hyper-V infrastructure: needs upgrades!!
-
@fateknollogee said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Maybe I'll keep both 2950 & use 1 as a spare.
The 2900 for sure is going bye-bye, it's got problems & for some reason, hard drives keep failing.
I even replaced the Perc controller & same thing still happensI'd guess a bad power supply then. Getting rid of it sounds good in this case.
-
Has a reminder Hyper-V 2016 is not supported on the 2950s because Hyper-V requires processors to support SLAT.
https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/26
http://www.nodefinity.net/post/hyper-v-on-poweredge-2900-2950-the-end-of-the-road-is-windows-server-2012-r2 -
@dashrender said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@jaredbusch said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@tim_g said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
DASs make great backup locations, too, if buying a whole new server doesn't make sense.
I'm not sure what you're referring to here?
Direc Attached Storage
yeah, I know was DAS is.. how is that a good place to put a backup, unless it's attached to a different server that's not running the VMs.
Who cares is the storage is attached to which server. It is not dependent upon it unless you do something wrong.
So it Is a super fast backup target.
Then you off-site from there.
If the server is dead you have to repair/replace before you can restore whether the backup is a DAS or a NAS.
-
@dashrender said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@eddiejennings said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
- Buy Server 2016 Standard license - use for new DC vm.
- Upgrade Directory Services level from 2008 to 2016.
Why only upgrade the DC? If the DC is the only thing you're going to upgrade, you might consider saving that money and installing linux with SMB instead.
Dash beat me to it.
The lob apps are Windows only & require AD.
Linux SMB provides AD - most things can't tell the difference unless there is a specific feature of AD 2016 the LOB needs.
SMB and AD are unrelated things. SMB is SMB, no matter what platform it is on. I think you are using SMB as a term for AD here?
AD and SMB are things provided.
-
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@tim_g said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
How many CALs are you going to need, roughly?
Let's see, I need a CAL for every user & server that connects to the "new 2016" DC?
CALs are always by user (or connecting device), never by server.
-
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
Second server is for failover. Backups would just go to cloud, disk, or tape. No need for another server for backups.
-
@dashrender said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@jaredbusch said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@tim_g said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
DASs make great backup locations, too, if buying a whole new server doesn't make sense.
I'm not sure what you're referring to here?
Direc Attached Storage
yeah, I know was DAS is.. how is that a good place to put a backup, unless it's attached to a different server that's not running the VMs.
I don't understand. How is it not a good place to put the backups? A second server is more complex, expensive, and fragile as a backup target goes.
-
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@tim_g said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
How many CALs are you going to need, roughly?
Let's see, I need a CAL for every user & server that connects to the "new 2016" DC?
CALs are always by user (or connecting device), never by server.
Thanks for the heads up. I'll need just 10.
-
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
Second server is for failover. Backups would just go to cloud, disk, or tape. No need for another server for backups.
Where would I store my local backup copies if not on the 2nd server?
-
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
Second server is for failover. Backups would just go to cloud, disk, or tape. No need for another server for backups.
Where would I store my local backup copies if not on the 2nd server?
The DAS in the example that Tim gave.
-
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
Where would I store my local backup copies if not on the 2nd server?
The DAS in the example that Tim gave.
Yes that is one option, a second server housing my Veeam repository is probably my preferred choice.
-
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
Where would I store my local backup copies if not on the 2nd server?
The DAS in the example that Tim gave.
Yes that is one option, a second server housing my Veeam repository is probably my preferred choice.
It's an option, but is there a significant benefit?
-
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
Where would I store my local backup copies if not on the 2nd server?
The DAS in the example that Tim gave.
Yes that is one option, a second server housing my Veeam repository is probably my preferred choice.
The fastest and cheapest option is to hook up a DAS to your main Hyper-V Server. It works well, I'm speaking from experience.
I can always insert the HBA into another server and hook it up if needed, but it looks like this:
Server --> DAS --> Tape
There's also Shadowcopies of the Windows fileservers (located on separate .VHDX) for quick "ooops" recoveries... those aren't backups, just an easy handy way to revert a file. It very often saves time from having to restore from a backup, as these shadowcopies are done twice daily.
-
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@jaredbusch said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@tim_g said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
DASs make great backup locations, too, if buying a whole new server doesn't make sense.
I'm not sure what you're referring to here?
Direc Attached Storage
yeah, I know was DAS is.. how is that a good place to put a backup, unless it's attached to a different server that's not running the VMs.
I don't understand. How is it not a good place to put the backups? A second server is more complex, expensive, and fragile as a backup target goes.
So it would be acceptable to have one server hosting all you LoB VMs plus a VM running Veeam or something of the like, and the backup data stored on X (DAS, cloud, etc.), correct?
-
@eddiejennings said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@scottalanmiller said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@jaredbusch said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@tim_g said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@fateknollogee said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
@dashrender said in Server 2008w Hyper-V infrastructure: needs upgrades!!:
Right, so in this case, instead of that second server, purchase a single server, and spend the extra money on more Windows licenses.
And do what about no backups?
DASs make great backup locations, too, if buying a whole new server doesn't make sense.
I'm not sure what you're referring to here?
Direc Attached Storage
yeah, I know was DAS is.. how is that a good place to put a backup, unless it's attached to a different server that's not running the VMs.
I don't understand. How is it not a good place to put the backups? A second server is more complex, expensive, and fragile as a backup target goes.
So it would be acceptable to have one server hosting all you LoB VMs plus a VM running Veeam or something of the like, and the backup data stored on X (DAS, cloud, etc.), correct?
Of course, it's just media. Having the backup software on another machine doesn't do very much in a one server environment.
-
@scottalanmiller I thought as such. This thread made me think about my own environment and what I'm planning for it. As this (doing backups right) is still new territory for me, I wanted a sanity check.
-
@eddiejennings said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@scottalanmiller I thought as such. This thread made me think about my own environment and what I'm planning for it. As this (doing backups right) is still new territory for me, I wanted a sanity check.
Now if you have multiple servers, this can easily change. But when you have only one, keeping things simple is often best.
-
@eddiejennings said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
So it would be acceptable to have one server hosting all you LoB VMs plus a VM running Veeam or something of the like, and the backup data stored on X (DAS, cloud, etc.), correct?
For me the, the most important thing is not the location of the vm running Veeam.
I care about where my Veeam repository is, for me, it'll be on the second server. -
@fateknollogee said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
@eddiejennings said in Server 2008 w Hyper-V infrastructure: needs upgrades!!:
So it would be acceptable to have one server hosting all you LoB VMs plus a VM running Veeam or something of the like, and the backup data stored on X (DAS, cloud, etc.), correct?
For me the, the most important thing is not the location of the vm running Veeam.
I care about where my Veeam repository is, for me, it'll be on the second server.If the repo is what is important, then the DAS is the most logical place. I'm confused by your priority being one thing, but the result of that priority seemingly being the opposite of what you'd expect given that priority. It's specifically because we assumed that priority that Tim and I mentioned the DAS approach.
-
A DAS is a great option, a second server is more work, but is also a good choice.
You cannot temporarily failover to a second server without SA.
