BRRABill's Field Report With XenServer
-
@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!?!?!
-
@BRRABill Everything should be reported there: https://github.com/vatesfr/xo-web/issues
Feel free to report!
-
@olivier said in BRRABill's Field Report With XenServer:
@BRRABill Everything should be reported there: https://github.com/vatesfr/xo-web/issues
Feel free to report!
Done.
My first ever.
You never forget your first!
-
Another thing I noticed...not sure if this is a bug or something that is supposed to be...
If you go back into a backup job without compression to edit it, the "USE COMPRESSION" switch is set to on.
Is that a bug? If so I will add that as well.
-
Report any issue
-
@olivier said in BRRABill's Field Report With XenServer:
Report any issue
My new nickname will be ... the phantom menace.
-
Last one for the day!
Can you explain what these log items on the backup mean? I think I may have found a bug there, too.
vm.rollingBackup: tag: test with compression _reportWhen: never depth: 2 remoteId: remote-10 onlyMetadata: compress: VM: XenOrchestra (xenserver-MAIN) true
-
Basic backup with tag "test", compression enabled, never report any failure or success by email, retention of 2. Saving on "remote10". All of this on vm XO hosted on xenserver-MAIN.
-
@olivier said in BRRABill's Field Report With XenServer:
Basic backup with tag "test", compression enabled, never report any failure or success by email, retention of 2. Saving on "remote10". All of this on vm XO hosted on xenserver-MAIN.
How did you know compression was enabled?
-
@BRRABill said in BRRABill's Field Report With XenServer:
@olivier said in BRRABill's Field Report With XenServer:
Basic backup with tag "test", compression enabled, never report any failure or success by email, retention of 2. Saving on "remote10". All of this on vm XO hosted on xenserver-MAIN.
How did you know compression was enabled?
Just guessing that "with compression"
-
@travisdh1 said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
@olivier said in BRRABill's Field Report With XenServer:
Basic backup with tag "test", compression enabled, never report any failure or success by email, retention of 2. Saving on "remote10". All of this on vm XO hosted on xenserver-MAIN.
How did you know compression was enabled?
Just guessing that "with compression"
That was the name of my job.
"test with compression"
