Backup File Server to DAS
-
@IT-ADMIN said:
but any way i will try, but before that i will inform the management that the physical server may be blacklisted and damaged (because when the VM authorize itself against windows with the physical server Key, there is a risk to damage also the physical server )
if they are ready for this risk i will try the VM, if they just said leave the server as it is then i will leave everything physical
i'm right with my plan ??Think about it this way. If trying to activate that CD Key on your VM caused your other server to stop working, then all of the servers around the world running that key would stop working.
Remember the process, Run the P2V to create the OVA files. Then shut off the old server. Now import the OVA files into XenServer, then start the VM. Try to authorize. If it works, great!
If not, turn the VM off and turn the old server back on.You are never at risk of deactivating the old server from this process.
-
Good example of why not to worry there. Otherwise any of us could Google that key, use it and shut you off.
-
yes you are right guys, thank you for this encouragement to do this project,
now that my concern to deactivate the physical server was not true, i can try P2V -
i have a technical question here
you said that if i keep my physical server and in case of disaster and backup my server using a previous system image then this system image will reauthorize itself again, right ??
but in this scenario there is no hardware change, so why the system will try to activate himself again ??? -
@IT-ADMIN The system will attempt to reauthorize it's self because your changing the underlying hardware.
From a physical motherboard, cpu, memory etc to a virtual one.
-
@IT-ADMIN said:
i have a technical question here
you said that if i keep my physical server and in case of disaster and backup my server using a previous system image then this system image will reauthorize itself again, right ??
but in this scenario there is no hardware change, so why the system will try to activate himself again ???I tend to disagree with that above listed statement. If you restore your system to the exact same hardware it was on before, it's very unlikely that you would need to re authorize the system.
But as Scott already mentioned... This is another great reason to use a VM. VMs can move between platforms and rarely if ever re authorize themselves because the VM doesn't see the hardware change.
-
@DustinB3403 said:
@IT-ADMIN The system will attempt to reauthorize it's self because your changing the underlying hardware.
From a physical motherboard, cpu, memory etc to a virtual one.
His question this morning would be about restoring his backup onto the same hardware it's always been running on, nothing to do with VMing.
-
Using a Bare metal restore to identical hardware?
Then what causes the host to fail? OS Failure? Then you shouldn't have an issue unless your well outside of a normal restore point. Like Service Pack differences.
-
@DustinB3403 said:
Using a Bare metal restore to identical hardware?
identical meaning the SAME hardware? As in the same exactly one? When would you do that?
-
I'm replying to @Dashrender and @IT-ADMIN so I don't know why you'd be restoring to identical hardware.
Unless you were backing up a physical host, expecting the physical host to die because of something software related, not hardware related.
I'd expect you to more likely restore to different hardware. Which is why I raised the point.
-
@scottalanmiller said:
@DustinB3403 said:
Using a Bare metal restore to identical hardware?
identical meaning the SAME hardware? As in the same exactly one? When would you do that?
Granted it would be rare, it was just a question though.
it is more likely that you would be restoring to a server with at least different motherboard, and that will typically trigger a re authorization.
-
@coliver said:
@DustinB3403 said:
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
@IT-ADMIN said:
when i first type the first letter of the key google bring the rest of it, then i found that so many website share that damn key,
does this mean that my key is not genuine and will not activate my VM ??
Unfortunately, it is likely that the key no longer works. But it might, there is no way to really tell.
but any way i will try, but before that i will inform the management that the physical server may be blacklisted and damaged (because when the VM authorize itself against windows with the physical server Key, there is a risk to damage also the physical server )
if they are ready for this risk i will try the VM, if they just said leave the server as it is then i will leave everything physical
i'm right with my plan ??You're only "right" if the company doesn't understand that they are putting them selves at a larger risk by your physical server dying.
What will the company do once this server does die? Likely they'll blame you for not doing something.
This. Even with a proper backup you will probably have to re-authorize your key when you restore to the same (or similar) hardware.
i said that because our friend @coliver said the above
-
@IT-ADMIN said:
@coliver said:
This. Even with a proper backup you will probably have to re-authorize your key when you restore to the same (or similar) hardware.
i said that because our friend @coliver said the above
He's absolutely right on the similar, but probably not if it was the same.
@scottalanmiller and @DustinB3403 are right though, when would you ever do a full restore to the same hardware?
I suppose if you needed to completely redo the underlying harddrive setup on a server that could be the case, that's so rare as to not even be considered. If you get a replacement motherboard put into the same server, from a software perspective that's no longer the same hardware, so you'd most likely get a re authorization.
-
@DustinB3403 said:
I'm replying to @Dashrender and @IT-ADMIN so I don't know why you'd be restoring to identical hardware.
Unless you were backing up a physical host, expecting the physical host to die because of something software related, not hardware related.
I'd expect you to more likely restore to different hardware. Which is why I raised the point.
ah ok, thank you for clarifying that, so in this case i can restore my physical server in case of software failure with a previous system image without triggering any activation process (no hardware change)
-
@Dashrender said:
@IT-ADMIN said:
@coliver said:
This. Even with a proper backup you will probably have to re-authorize your key when you restore to the same (or similar) hardware.
i said that because our friend @coliver said the above
He's absolutely right on the similar, but probably not if it was the same.
@scottalanmiller and @DustinB3403 are right though, when would you ever do a full restore to the same hardware?
I suppose if you needed to completely redo the underlying harddrive setup on a server that could be the case, that's so rare as to not even be considered. If you get a replacement motherboard put into the same server, from a software perspective that's no longer the same hardware, so you'd most likely get a re authorization.
ah ok in case of hardware change (cpu, RAM, HD, motherboard) otherwise the backup would be made without activation
-
@IT-ADMIN said:
ah ok, thank you for clarifying that, so in this case i can restore my physical server in case of software failure with a previous system image without triggering any activation process (no hardware change)
Depends It always can trigger it. For example if a computer dies our technicians here many times will just pull the HDD out of the dead computer and put it in a spare of the exact same model, specs etc. until the replacement gets here. Often times windows and office will want to be re-activated.
-
@IT-ADMIN said:
i have a technical question here
you said that if i keep my physical server and in case of disaster and backup my server using a previous system image then this system image will reauthorize itself again, right ??
but in this scenario there is no hardware change, so why the system will try to activate himself again ???You ONLY avoid re-authorizing if you virtualize. Physical machines are new machines anytime that you move the system or change the hardware.
-
@DustinB3403 said:
I'm replying to @Dashrender and @IT-ADMIN so I don't know why you'd be restoring to identical hardware.
Unless you were backing up a physical host, expecting the physical host to die because of something software related, not hardware related.
I'd expect you to more likely restore to different hardware. Which is why I raised the point.
In which case the backup is likely not any good.
-
@IT-ADMIN said:
@Dashrender said:
@IT-ADMIN said:
@coliver said:
This. Even with a proper backup you will probably have to re-authorize your key when you restore to the same (or similar) hardware.
i said that because our friend @coliver said the above
He's absolutely right on the similar, but probably not if it was the same.
@scottalanmiller and @DustinB3403 are right though, when would you ever do a full restore to the same hardware?
I suppose if you needed to completely redo the underlying harddrive setup on a server that could be the case, that's so rare as to not even be considered. If you get a replacement motherboard put into the same server, from a software perspective that's no longer the same hardware, so you'd most likely get a re authorization.
ah ok in case of hardware change (cpu, RAM, HD, motherboard) otherwise the backup would be made without activation
How will you do a restore without one of those things changing?
-
@IT-ADMIN said:
@DustinB3403 said:
I'm replying to @Dashrender and @IT-ADMIN so I don't know why you'd be restoring to identical hardware.
Unless you were backing up a physical host, expecting the physical host to die because of something software related, not hardware related.
I'd expect you to more likely restore to different hardware. Which is why I raised the point.
ah ok, thank you for clarifying that, so in this case i can restore my physical server in case of software failure with a previous system image without triggering any activation process (no hardware change)
Sure, but is that really what your backup is for? This is a very edge case. You have a backup system that's only purpose is to handle the scenario where the software has died and you want to fall back to an older version of the system? What will stop it from dying again right away? Is software "dying" a real concern (other than patching?)
