BRRABill's Field Report With XenServer
-
@BRRABill said in BRRABill's Field Report With XenServer:
@DustinB3403 said
Yes you can do that. As the Boot USB is what is running the hardware, the hardware doesn't store any of the boot info.
And none of the VM info/data is altered with an upgrade?
So, in theory you could try going to 7 from 6.5, it could bomb, and you could just go back to your 6.5 USB?
That's the theory.
-
Of course, testing in a LAB would be ideal.
-
@DustinB3403 said
Of course, testing in a LAB would be ideal.
What, no one has ever tested this?
Once I get all the production stuff up I will give it a shot.
-
Testing is for losers.
-
@scottalanmiller said in BRRABill's Field Report With XenServer:
Testing is for losers.
Or for people who prefer to not play with production.
But YOLO!
-
-
@olivier said
Indeed, you can't live migrate a VM from a recent version of XS to an older one.
What about move and copy? Can you do that to a stopped VM?
What about export? Could i export the VM from XS7 and import it to XS6.5?
-
@BRRABill said in BRRABill's Field Report With XenServer:
@olivier said
Indeed, you can't live migrate a VM from a recent version of XS to an older one.
What about move and copy? Can you do that to a stopped VM?
What about export? Could i export the VM from XS7 and import it to XS6.5?
I don't believe you can move a VM backwards to an older version of XS7.
-
@BRRABill You should be able to export / import from XS7 to an older version. Not sure about moving a stopped VM.
-
@DustinB3403 said
I don't believe you can move a VM backwards to an older version of XS7.
I admit I am still unclear (as are a lot, I think) as to how much the VMs get touched in various operations.
For example, my question yesterday about a botched upgrade. If you can theoretically go back to 6.5 from a botched 7 upgrade, it can't be touching the VMs, right?
-
@BRRABill said in BRRABill's Field Report With XenServer:
@DustinB3403 said
I don't believe you can move a VM backwards to an older version of XS7.
I admit I am still unclear (as are a lot, I think) as to how much the VMs get touched in various operations.
For example, my question yesterday about a botched upgrade. If you can theoretically go back to 6.5 from a botched 7 upgrade, it can't be touching the VMs, right?
Well if the install was botched, then perhaps the upgrade to the VM's hadn't happened yet.
The only thing I recall changing when moving from ESXi version to version was the ESXi tools inside the OS, the outside (the VM container) didn't seem to change.
-
@BRRABill said
Ah, OK.
Can you perhaps invent a little paper clip that comes up on the bottom of the XO windows that tells you to click that button again?
I AM KIDDING, OF COURSE.
BTW, I know you guys watch Silicon Valley. What a coincidence I mentioned this, haha.
-
So, for reasons I am not going to discuss to protect my stupidity, I reinstalled XS7 today.
I started from scratch, and this is how things got partitioned on my fancy new 64GB USB stick.
Just FYI...
1 46139392 83888127 18G Microsoft basic
2 8390656 46139391 18G Microsoft basic
3 83888128 84936703 512M BIOS boot parti
5 2048 8390655 4G Microsoft basic
6 84936704 87033855 1G Linux swap -
Doubled the RAM in my production XS today, and finally migrated the production mail server off the desktop that was running XS to the DELL server running XS7.
I used the live migration, and it worked like a dream.
Awesome...
-
@olivier said
It's always a trade off. At least, it will be a quiesce snapshot if your Windows VM support it.
But ideally, to avoid any risk, shutdown THEN copy is the safest solution.
Depends of risk level (and downtime!) you can accept (eg live migration is still possible, but you could possibly reboot at destination if CPU instructions are not correct)
Would the only risk be the server crashing?
AKA, it would copy over OK< but might not just keep running.
XS7 did not fix my issue. I'm debating buying a second server to have just for redundancy, but not sure if it's really prudent with my smaller shop.
-
XO question for fellow XO users.
If I want to do a onetime backup of a VM, I simply set up a future schedule (say a month out), then just run the job. Is there another way everyone does this?
I guess you could just make a copy of it, as well. But I mean purely from the backup section.
-
Why not make a manual run? (the "play" button) without enabling the job.
-
@olivier said in BRRABill's Field Report With XenServer:
Why not make a manual run? (the "play" button) without enabling the job.
That is what I am doing. But I have to make a schedule. I guess I am saying ... is there a way to just totally skip the scheduling part?
I am sure I am just missing it.
-
Oh ok. No that's good, whatever schedule, not enabling the job and that's it
-
@olivier said in BRRABill's Field Report With XenServer:
Oh ok. No that's good, whatever schedule, not enabling the job and that's it
Yeah that's what I was doing. Thanks!
BTW: is there a typo in the month box? Or do you already know that?
Is ther e a way to search for known bugs so I do not keep telling you the same ones!?!?!
