Backup File Server to DAS
-
@Dashrender said:
@Dashrender said:
once you have the key, you could search google and see if anything comes up on that key. MS sometimes releases blog posts about keys they have killed due to piracy.
take the last 4 sections of the key and put it into google and see if you get any results that match your full key.
you mean : xxxx-xxxx-xxxx-xxxx
-
yes, but your actual code, don't type a bunch of x's into google.
-
hhhhhh, when i first type the first letter google bring the rest of the key, when i see the website having my key, i found that so many website share that damn key
-
what do you think guys ??
-
Yeah, if the machine won't automatically re authenticate, you're out of luck.
but you should still try.
-
summary: i will P2V, shutdown the P, move the V to a hypervisor, start the VM, in this stage 2 possible situation can occur :
1- the VM reauthorize itself automatically
2- enter the key (which was retrieved from the P) and submit it (the activation can succeed or fail)
in case of activation fail, delete the V, start the P and forget about virtualizationi'm right with this summary ????
-
Looks good to me.. though what do you mean move the V to the hypervisor? Normally the P2V tools do that for you, at least they do with ESXi, don't know about Hyper-V or XenServer
-
@Dashrender said:
Looks good to me.. though what do you mean move the V to the hypervisor? Normally the P2V tools do that for you, at least they do with ESXi, don't know about Hyper-V or XenServer
i mean by that after virtualizing the P, it will gave me a VM, then i will import the VM to my Xenserver
as far as i'm concerned VMware vCenter Converter who perform the P2V, is there any other tool that import the VM directly from the P to XenServer ?? -
You can't use VMWare's tool to create the VM. You have to use Xen's tool to create the image.
@DustinB3403 - Help!
-
really, i though all VM has the same extension and can be imported into all hypervisors no matter how they were P2V,
@scottalanmiller ,@DustinB3403 , @JaredBusch help ...lol -
it looks like our IT pros having a rest
enjoy -
So with XenServer (and specifically NAUBackup) the files that are created are VM_Name.xva which are specific to Xen.
The other hypervisors I'm uncertain of what they create.
Sorry I can't be more help.
-
Can you explain the P2V process for XenServer?
-
@Dashrender said:
Can you explain the P2V process for XenServer?
Well its not P2V for XenServer.
It's P2V for what ever server OS your using.
We've used and had success with VMWare's P2V tool to an open format. Which is usable on XenServer.
We didn't have much luck with XenServers P2V tool on XenServer oddly. Generally the recommendation is to just build a new VM server, reinstall your applications, and move any required files onto it.
-
Sure, but it's likely @IT-ADMIN can't do that because of his licensing issue. So doing an actual P2V is kinda important here.
-
The P2V process is dependent on the OS he's using.
I'd recommend trying VMWare's P2V Tool first to build an .OVA and import that into XenServer. (Or whatever his hypervisor is)
-
why there is such limitation, is it because i'm using xenserver ??
what about using Hyper-v or ESXI, does the P2V would be easier ??? -
OVA files are an open-format.
Meaning every Hypervisor should support importing them into your Hypervisor.
The backup tool I use, creates a backup file for the type of Hypervisor I'm using. Which is XenServer.
So it's much simpler to import a file that is designed for that system( .XVA), rather than a generic one (.OVA) when importing into XenServer.
Does it make sense?
-
@DustinB3403 said:
OVA files are an open-format.
Meaning every Hypervisor should support importing them into your Hypervisor.
The backup tool I use, creates a backup file for the type of Hypervisor I'm using. Which is XenServer.
So it's much simpler to import a file that is designed for that system( .XVA), rather than a generic one (.OVA) when importing into XenServer.
Does it make sense?
it make sense for me,
so .OVA is designed to be imported into EXSI not XenServer, isn't it ?? -
@IT-ADMIN No that's not correct.
Described here is the description:An OVF is a collection of items in a single folder. Most commonly this is a description file (.ovf) a manifest file (.mf), and virtual machine state files (*.vhd or *.vmdk)
An OVA is a single file. The OVA is the OVF folder contents all zipped into a single file. The purpose of the OVA is when you want to take an OVF and share it, or give it as a download. The OVA needs to be opened into the OVF before it can be consumed.
