Xen Orchestra Backup, Single VM Failing
-
Is Terminated a good thing in this case?
-
-
When it is green, yes. That means the backup finished, I think.
Edit: Dustin beat me to it.
-
@DustinB3403 said:
@coliver said:
Is Terminated a good thing in this case?
If it's red, no.
Green yes.
Ah, that is a bit confusing (I understand the lights.) I saw that when I did my first backup and assumed terminated means something failed.
-
We'll have to bug @oliver if it doesn't change after they get the new UI in place, lol.
-
@olivier -- the xo-server-logs and xo-server are only outputting generic information and don't display anything useful for me to debug this on the screen. Is this written to a file anywhere?
-
You should see something in the
xo-serveroutput right when you trigger the backup job.I'm removing the word "Terminated" by "Finished" ASAP.
-
@olivier said:
You should see something in the
xo-serveroutput right when you trigger the backup job.I'm removing the word "Terminated" by "Finished" ASAP.
Perfect thank you. I don't know why when I see terminated I think "this is bad"... especially when it basically means finished.
-
Yea, terminated has a bad connotation to it... i know i immediately equate it to "fired"
-
There is maybe a notion of "unexpected finish" for "terminated" word. In French, "Terminé" means "finished". That explains why one of the dev use this word
-
-
@olivier said:
Done: https://github.com/vatesfr/xo-web/commit/f9028cb366e6a102a5a0fd54755c7c0163e62a3c
Re job 9: Personally, I would not say finished here. Simply state error or Failure or something.
I know it IS finished. but say you eventually setup an email on job status. how will I route it with rules if both success and failure say finished?
This is how I handle my veeam backup stuff now.
So, all my notices are filtered away unless it has some other status.
Well except this warning. These are success too. The damned HP recovery partition always fires a warning on space.
-
I'll need to hire 50 lads to release all those ideas/features
-
I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).
When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.
This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.
Is this a bug in XO, by any chance? @olivier ?
If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?
-
@dafyre How does it even know what the public IP is?
-
@dafyre said:
I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).
When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.
This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.
Is this a bug in XO, by any chance? @olivier ?
If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?
You're running XO in a vm on the XenServer?
-
@johnhooks said:
@dafyre said:
I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).
When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.
This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.
Is this a bug in XO, by any chance? @olivier ?
If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?
You're running XO in a vm on the XenServer?
Yes.
That is normal.
-
@DustinB3403 said:
@johnhooks said:
@dafyre said:
I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).
When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.
This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.
Is this a bug in XO, by any chance? @olivier ?
If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?
You're running XO in a vm on the XenServer?
Yes.
That is normal.
I just wanted to make sure I understood how he set it up.
-
Now it wouldn't hurt to have a separate host, but on the primary host is also normal.
-
@dafyre said:
I'm having a similar issue, but different, lol. I am unable to backup any of my XenServer VMs. I am using an XO Machine built with @DustinB3403 's instructions. I am connecting to my XenServer using it's inside IP address (192.168.15.1/24) from my XO Server (192.168.15.2/24).
When the backup jobs try to run, my XO Server tires to connect to the PUBLIC IP address of my XenServer.
This poses a problem this is a hosted XenServer instance with a single public IP address... I am using ports 80 and 443 to run an Nginx proxy as a VM.
Is this a bug in XO, by any chance? @olivier ?
If the answer to that question is "NO", then what can I do to fix XenServer so that it only listens on my inside IP addresses?
Another question, is this a bridge for an internal network? Or did they give you a local network for your server?
