Xen Orchestra Backup, Single VM Failing

dafyre

When it is green, yes. That means the backup finished, I think.

Edit: Dustin beat me to it.

coliver

@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.

dafyre

We'll have to bug @oliver if it doesn't change after they get the new UI in place, lol.

dafyre

@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?

olivier

You should see something in the xo-server output right when you trigger the backup job.

I'm removing the word "Terminated" by "Finished" ASAP.

coliver

@olivier said:

You should see something in the xo-server output 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.

brianlittlejohn

Yea, terminated has a bad connotation to it... i know i immediately equate it to "fired"

olivier

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

Done: https://github.com/vatesfr/xo-web/commit/f9028cb366e6a102a5a0fd54755c7c0163e62a3c

JaredBusch

@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.

https://i.imgur.com/MPZJ1hR.jpg

https://i.imgur.com/D1whu9s.jpg

Well except this warning. These are success too. The damned HP recovery partition always fires a warning on space.

https://i.imgur.com/vztYv2R.jpg

olivier

I'll need to hire 50 lads to release all those ideas/features

dafyre

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?

Alex Sage

@dafyre How does it even know what the public IP is?

stacksofplates

@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?

DustinB3403

@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.

stacksofplates

@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.

DustinB3403

Now it wouldn't hurt to have a separate host, but on the primary host is also normal.

stacksofplates

@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?

dafyre

@anonymous said:

@dafyre How does it even know what the public IP is?

This is what I'd like to know, lol. I am expecting it is something in the XAPI or something with XenServer configs somewhere... It should be noted that this is a Dedicated machine rented from KimSufi in France. I have exactly 1 public IP that I can use for this server.

Dashrender

I was wondering if the XO VM has external DNS servers instead of internal ones. Or maybe both, and it's failed over to the external one.

I've found that I can never have internal and external DNS servers if I have a split-brain/split-horizon DNS situation. I can only use internal DNS or I WILL end up with problems.