Backup File Server to DAS
-
dear @DustinB3403, what makes me not moving to virtualization is a long story, lol
license issue and the P2V process (cuz the system itself is not very good) -
therefor i decided to keep everything as it is and just thinking of a solution to recover myself in case of disaster (and just keep this legacy of bare metal servers, only 2 DELL poweredge T310)
-
@IT-ADMIN said:
dear @DustinB3403, what makes me not moving to virtualization is a long story, lol
license issue and the P2V process (cuz the system itself is not very good)No licensing for a hypervisor (or at least none you have to worry about). Look at Hyper-V or XenServer. Both are free to use for everyone. The only licensing you will need to worry about are your Windows licensing (if you have them).
-
@coliver said:
@IT-ADMIN said:
dear @DustinB3403, what makes me not moving to virtualization is a long story, lol
license issue and the P2V process (cuz the system itself is not very good)No licensing for a hypervisor (or at least none you have to worry about). Look at Hyper-V or XenServer. Both are free to use for everyone. The only licensing you will need to worry about are your Windows licensing (if you have them).
yes this is what i'm talking about: my windows server license
-
i think that i'm in a good position now with this veeam, it really save my ass, lol
-
@IT-ADMIN said:
dear @DustinB3403, what makes me not moving to virtualization is a long story, lol
license issue and the P2V process (cuz the system itself is not very good)Licensing I understand, meaning you have cracked licenses. The P2V process is really quite simple on any hypervisor you use.
Only in rare circumstances should you consider not virtualizing. One being extremely rare/custom hardware that doesn't work on any hypervisor.
-
ok let's suppose that i P2V, if the P and V is online what will happen ??
i think both version will be blacklisted, isn't it ??? -
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.
