SSD in Standalone, non RAID Server
-
@scottalanmiller said:
HDs have not been more reliable for many years. SSDs are generally way more reliable (when talking enterprise, server drives.) Sometimes by an order of magnitude.
For shame @scottalanmiller ! HDD != HD
-
SSDs are far more reliable, and have been for some time now.
-
@garak0410 said:
Were you talking about turning in my 2008 Box into a host and then work on adding a second drive?
This is your only option. Your OEM license locks that system to that old host. There is no option to ever move it. That is the limitation agreed to when OEM is purchased. That's what you trade for the discount. It's never worth it. But it is what it is. You are stuck. You can make this piece of hardware part of your HyperV infrastructure but you can't move this VM to another server.
-
@thanksaj said:
For shame @scottalanmiller ! HDD != HD
HD = hard drive. That's what I'm talking about as opposed to SSDs. Hard drive has been a standard term for Winchester drives since long before you were born. It is the alternative to a FD, floppy drive. You can add the "disk" to either of them or not. They are the same thing. Not sure what you are picturing as the difference, but they are actually the same thing (HD and HDD.) HDD is a new term just made up recently and should not be needed as it is redundant. Really, they are all Winchesters and that is the correct term.
-
@garak0410 said:
@scottalanmiller said:
@garak0410 said:
I will look into this then...would love to get it on our Hyper-V infrustrcture...it has been a godsend...
Yup, just install the HyperV role and you are virtualized. But you REALLY need to deal with that single disk problem! That is huge.
Question so I understand what you said...I want to move my 2008 R2 license over to my Hyper-V host, then I don't need to worry about that single disk anymore as I'll then retire that server. Were you talking about turning in my 2008 Box into a host and then work on adding a second drive?
The answer depends on exactly what license you have. If it is an OEM Server 2008 R2 license, then you need to virtualize it on the existing box. It cannot be moved.
If it is a volume license or a retail key, then you can move it to your existing infrastructure, no questions asked. -
@scottalanmiller said:
@thanksaj said:
For shame @scottalanmiller ! HDD != HD
HD = hard drive. That's what I'm talking about as opposed to SSDs.
HD = High Definition. HDD = hard drive, or hard disk drive more correctly. Come on Scott!
-
@scottalanmiller said:
This is your only option. Your OEM license locks that system to that old host.
I do not believe that he stated the license was OEM.
-
@JaredBusch said:
The answer depends on exactly what license you have. If it is an OEM Server 2008 R2 license, then you need to virtualize it on the existing box. It cannot be moved.
Oh, maybe he didn't.
-
@thanksaj said:
HD = High Definition. HDD = hard drive, or hard disk drive more correctly. Come on Scott!
HDD = Hard Disk Drive
HD = Hard Drive
SSD = Solid State Drive -
@JaredBusch said:
@scottalanmiller said:
This is your only option. Your OEM license locks that system to that old host.
I do not believe that he stated the license was OEM.
Sorry for the confusion... that was my fault. I brought up the OEM license out of curiosity more then anything else. I don't know if he has the retail or OEM license.
-
@JaredBusch said:
@thanksaj said:
HD = High Definition. HDD = hard drive, or hard disk drive more correctly. Come on Scott!
HDD = Hard Disk Drive
HD = Hard Drive
SSD = Solid State DriveI'm not gonna argue it any further at this point. Not worth it.
-
@thanksaj said:
@scottalanmiller said:
@thanksaj said:
For shame @scottalanmiller ! HDD != HD
HD = hard drive. That's what I'm talking about as opposed to SSDs.
HD = High Definition. HDD = hard drive, or hard disk drive more correctly. Come on Scott!
I think it has more to do with context then the actual abbreviations.
-
@JaredBusch said:
HDD = Hard Disk Drive
HD = Hard Drive
SSD = Solid State DriveIndeed that is what the acronyms stand for. HD and HDD are the same physical thing, though. There is no need to state the "disk" and HDD should really never be used as it is just a silly, new term that is redundant.
-
@thanksaj said:
I'm not gonna argue it any further at this point. Not worth it.
It's important that you understand that HDD is not a useful term. Just because someone was recently confused and made a new term for something that has had a term and an acronym (HD) for 30 years doesn't mean that the new term has a useful place in the industry. HD already covers that base, HDD is just confusing. HDD is not really an industry term. No idea where it came from or why, but it is very recent that anyone has used it and it is just used out of confusion.
HD meant hard drive 20+ years before anyone used it for high definition.
-
@scottalanmiller said:
You have no licensing for restoring or failover. It's a pretty useless license in a disaster recovery scenario.
You could simply buy a new OEM licence in the case of a disaster. I don't believe Microsoft would have an issue with this as long as the licence was ordered in a timely manner, but what do I know.
With standard licences (without SA) are you allowed to test your DR plan by temporarily restoring to a separate server? And if so, why can't you do the same with OEM?
-
@Carnival-Boy said:
@scottalanmiller said:
You have no licensing for restoring or failover. It's a pretty useless license in a disaster recovery scenario.
You could simply buy a new OEM licence in the case of a disaster. I don't believe Microsoft would have an issue with this as long as the licence was ordered in a timely manner, but what do I know.
With standard licences (without SA) are you allowed to test your DR plan by temporarily restoring to a separate server? And if so, why can't you do the same with OEM?
Oh sure, you could run out and buy another one, but that is a lot of money and takes time.
Standard licenses can move between devices, OEM cannot. So there is no reason to test something with OEM that you aren't licensed to do.
-
I just checked the key on the server...it shows the following:
Windows Server 08 R2 Std. 1-4 CPU 5 CLT
Physical Key
Virtual KeyNo indication of OEM on this sticker...
-
@scottalanmiller said:
Standard licenses can move between devices, OEM cannot. So there is no reason to test something with OEM that you aren't licensed to do.
Standard licenses can move but there are restrictions. Like only once in 90 days? If your server failed, you couldn't temporarily move your OS to another server whilst it was being repaired and then move it back again? Or could you?
-
@garak0410 said:
I just checked the key on the server...it shows the following:
Windows Server 08 R2 Std. 1-4 CPU 5 CLT
Physical Key
Virtual KeyNo indication of OEM on this sticker...
Dell verified this is OEM but didn't verify if I can use that "virtual key" to turn this into a 2008R2 Hyper-V host and use the virtual key for a single Virtual VM (which will be our SQL Server eventually).
Regardless, will now look at setting up a RAID drive setup when I go to upgrade the drive. I've just been using the free Macrium Reflect image maker. It has worked for us in everything I do...should I use something more robust?
-
@garak0410 said:
Dell verified this is OEM but didn't verify if I can use that "virtual key" to turn this into a 2008R2 Hyper-V host and use the virtual key for a single Virtual VM (which will be our SQL Server eventually).
That's not for Dell to verify. That's none of their business and there is no question on that. Server OEM can be virtualized. It's not a question.
