Backup System For 5 PC SMB
-
I think that the big take aways are....
- Don't think of desktops as servers. Normally this would not occur to people to do but as all of the data is being stored on them it is causing you to think of them as little file servers.
- Think of replacing a desktop as either fixing the old one or replacing (in which case a new one has its own OEM license.)
-
Using enterprise server backup software, which on its own is a good thing but huge overkill for desktops, is leading you towards odd thinking as well. Those vendors had no intention of their products being used for backing up desktops. Sure you can, it works and they are happy to support that but fundamentally no thought is put into getting that working because it's not an intended or assumed use case. So all of their processes and features are designed around the intention of there being server licenses involved.
-
Sounds like just having a spare machine available might be the way to go.
-
Most of my thinking has been on the server level.
I just don't get the concept of having to buy a whole new server license if my motherboard dies. I guess that's what makes Hyper-V such an attractive option.
And I was certainly told that you can call Microsoft and explain the situation and often they will reissue the license, which is in direct contradiction to what @Chris has said.
-
@scottalanmiller said:
Using enterprise server backup software, which on its own is a good thing but huge overkill for desktops, is leading you towards odd thinking as well. Those vendors had no intention of their products being used for backing up desktops. Sure you can, it works and they are happy to support that but fundamentally no thought is put into getting that working because it's not an intended or assumed use case. So all of their processes and features are designed around the intention of there being server licenses involved.
But server licenses have the same issue, no? Can you move a server open license from one machine to another? I know you can't do it with OEM.
-
@BRRABill what I posted was for Windows desktop OS, not server.
-
@BRRABill said:
I just don't get the concept of having to buy a whole new server license if my motherboard dies.
You don't have to, for anything. You can always replace your motherboard.
-
@BRRABill said:
Most of my thinking has been on the server level.
This is all desktop though
Gotta pull away and think about a five user, all desktop workgroup and system design around small business, not big business. Requires a different approach than when you have big businesses with centralized authentication, storage, etc.SOHO setups lean to very simple setups. Always an exception, of course, but in general.
-
@scottalanmiller said:
it is only OEM licenses that cannot do a BMR recovery.
OEM can BMR to the original hardware it was sold with, but not to replacement hardware, technically not even identical replacement hardware.
-
@BRRABill said:
But server licenses have the same issue, no? Can you move a server open license from one machine to another? I know you can't do it with OEM.
Of course, server licenses are totally mobile. Everyone does that all of the time. If you couldn't, you couldn't have things like VMware or HyperV clusters or load balancing or failover.
-
@Chris said:
@BRRABill what I posted was for Windows desktop OS, not server.
What are the rules for a server OS?
For OEM licenses, and also spinning up a VM for disaster recovery purposes. Are you saying that is allowed?
Thanks!
-
@BRRABill said:
And I was certainly told that you can call Microsoft and explain the situation and often they will reissue the license, which is in direct contradiction to what @Chris has said.
No, actually it agrees with it 100%. If you can convince Microsoft to grant you a new license that suggests extremely strongly that you did, indeed, not have a license for what you wanted to do and needed to get a new one.
Now, I've never heard of Microsoft ever granting a new license in that case. Literally, never heard of anyone pulling that off. But it is not impossible, just unlikely. Banking on it, though, would be very foolish.
-
@scottalanmiller said:
Of course, server licenses are totally mobile. Everyone does that all of the time. If you couldn't, you couldn't have things like VMware or HyperV clusters or load balancing or failover.
I was under the impression that OEM server licenses were not mobile.
-
@scottalanmiller said:
Banking on it, though, would be very foolish.
That's why I am here. To not look foolish!
-
@BRRABill said:
I was under the impression that OEM server licenses were not mobile.
OEM = Not Mobile. Anytime OEM comes up in Microsoft terms it means "stuck to the hardware."
OEM Server licenses are not something you would ever buy or talk about, they simply should not exist. When you talk server licensing, no one means OEM. It's a standard best practice to never have OEM servers and no serious business does.
-
@scottalanmiller said:
OEM Server licenses are not something you would ever buy or talk about, they simply should not exist. When you talk server licensing, no one means OEM. It's a standard best practice to never have OEM servers and no serious business does.
That is definitely something I agree with.
-
@BRRABill said:
For OEM licenses, and also spinning up a VM for disaster recovery purposes. Are you saying that is allowed?
Server (outside of OEM) does exactly what you would expect. You can move to different hardware in a DR scenario once every 90 days. With certain SA licensing I believe that you can move as often as you like.
-
So getting back to the OP, where are you leaning on this backup solution?
-
My take is that given the revelations about the intent of the cloud option and now understanding how either costly it would be to go with VDI as well as how long it would take to pull down a back, that either local NAS or local AetherStore storage of backups is probably ideal.
-
Things that I would consider:
- Separate the OS from the data in backups. This makes backups smaller and faster both to make and to restore and, of course, reduces the needed storage for the backups over time allowing you to retain more of them.
- Standardize on an OS version and image with software packages.
- Get VL imaging rights.
- Create a base installation image to use, pop it onto DVD and have it ready to rebuild. This will get you to a clean "base" very rapidly with your OS, drivers and all standard applications ready to go.
- Do a file restore of data.
