Backup File Server to DAS
-
by the way i didn't crack anything, i found this preexisted
-
What you do is you do the P2V... and then shut down the Physical machine and boot up the Virtual Machine... Ideally, your end users would only see a short blip as things have been rebooted. If you do this in the Off-hours, your users shouldn't notice a thing.
-
@IT-ADMIN said:
by the way i didn't crack anything, i found this preexisted
Being properly licensed is just a cost of doing business. You should really try and resolve that... Either way though aren't you already breaking your licensing? Why does moving it to a different server matter?
-
As part of your move to virtualization, I'd recommend getting your OS Licensing up to snuff as well. Don't want any legal troubles from Microsoft or other companies.
-
His licensing concerns were covered in another thread. In his part of the world, they simply don't care about licensing and won't pay for it.
That whole concept went on for about 2-3 hours.
-
@Dashrender I musta missed it.
-
@Dashrender said:
His licensing concerns were covered in another thread. In his part of the world, they simply don't care about licensing and won't pay for it.
That whole concept went on for about 2-3 hours.
Ah... I must have missed that one?
-
lol, @Dashrender is up to date, thank you for clarifying that, i'm not ready to spend 3 hours again to say that here they don't care about licensing, in brief this is another story
-
@IT-ADMIN said:
lol, @Dashrender is up to date, thank you for clarifying that, i'm not ready to spend 3 hours again to say that here they don't care about licensing, in brief this is another story
It's all good. We got the short, short version.
That may actually be a valid concern though, as I have seen a few P2V tools actually make Windows request another activation.
-
so you told me that if i P2V i must disconnect the P from internet, isn't it ?? otherwise the system will be blacklisted ??
-
@IT-ADMIN said:
so you told me that if i P2V i must disconnect the P from internet, isn't it ?? otherwise the system will be blacklisted ??
Completely shut the P off. If the P and V are on at the same time with the same IP address, it will cause network problems.
-
@dafyre said:
@IT-ADMIN said:
so you told me that if i P2V i must disconnect the P from internet, isn't it ?? otherwise the system will be blacklisted ??
Completely shut the P off. If the P and V are on at the same time with the same IP address, it will cause network problems.
yes i know about the IP conflict, i'm talking about the licensing, if both are online windows will detect that there are 2 computers using the same license, isn't it ??
-
@IT-ADMIN said:
@dafyre said:
@IT-ADMIN said:
so you told me that if i P2V i must disconnect the P from internet, isn't it ?? otherwise the system will be blacklisted ??
Completely shut the P off. If the P and V are on at the same time with the same IP address, it will cause network problems.
yes i know about the IP conflict, i'm talking about the licensing, if both are online windows will detect that there are 2 computers using the same license, isn't it ??
The big issue you are going to have is that your underlying hardware is going to change, dramatically. Generally when Windows sees the hardware change like this it will try and re-authorize with the Microsoft licensing servers.
-
great this is what i want to know, i will have a licensing issue in the P2V process, i was sure i have this limitation since i don't have the windows key
in this case i will keep my physical servers, i don't want to have issues with the management
veeam + physical server = solve all problems -
wow i feel confortable now, can you imagine that for 2 years now i didn't have any backup plan except for one (daily incremental data backup in the same HD : D---> E)
now i can store my data in a NAS far away from my file server and furthermore i can even store daily incremental system images of my server, wow very good improvement -
@IT-ADMIN said:
@dafyre said:
@IT-ADMIN said:
so you told me that if i P2V i must disconnect the P from internet, isn't it ?? otherwise the system will be blacklisted ??
Completely shut the P off. If the P and V are on at the same time with the same IP address, it will cause network problems.
yes i know about the IP conflict, i'm talking about the licensing, if both are online windows will detect that there are 2 computers using the same license, isn't it ??
No, this really isn't an issue. Typically, once a machine is registered, assuming the underlying hardware doesn't change to much, it won't check the license again.
Here's what I'd do. I'd P2V, then turn off the P, and turn on the V. If the V won't re-authorize, then shut it off and delete it, and turn the P back on. If the V does re-authorize, or not even bother to check, then you are fine, and you and format the P.
-
do you know a P2V tool that do not ask for the key for the V after finishing the P2V ??
-
It has nothing to do with the tool. It's up to Windows to decide if it will ask or not.
For example, you could replace the motherboard in the server you have now, and it might ask you to re-authorize. It's completely up to Windows.
-
@Dashrender said:
It has nothing to do with the tool. It's up to Windows to decide if it will ask or not.
For example, you could replace the motherboard in the server you have now, and it might ask you to re-authorize. It's completely up to Windows.
You could add RAM and windows would ask you to re-authorize... or replace a CPU, which did happen to me.
-
You asked about restoring your backup onto an identical server, that too could trigger a re-authorization prompt.
All those things said, you weren't worried about them yesterday, I wouldn't be worried about them today (and by you I mean your company).
I'd do the P2V following the general steps I mentioned above. The worst that happens is you spent some hours and gained the knowledge that it wouldn't work.. .but at best, you've migrated everything to a VM, and freed up a server for something else.
