Xen Orchestra Backup, Single VM Failing

dafyre

More to the point -- did you figure out if there was a fix for this issue? I am having the same problem on my freshly installed XO setup.

Alex Sage

@dafyre Did you remove it and re-add it? or did you want a better solution?

olivier

Any log output?

dafyre

@anonymous said:

@dafyre Did you remove it and re-add it? or did you want a better solution?

I did remove and re-add it, but that did not fix it.

dafyre

@olivier said:

Any log output?

Where can I look to find the logs for it?

olivier

@dafyre Depends of how do you install it. It's the output of xo-server.

dafyre

@olivier said:

@dafyre Depends of how do you install it. It's the output of xo-server.

I found xo-server and xo-server-logs in /opt/bin (this is installed using @DustinB3403 and @scottalanmiller 's install script.

It worked the first time with the pretty green "Terminated" logo.... but every time after that , it give me the sad red ones. This is a Windows 2012 R2 server if that matters... I just installed the xen-tools a few minutes ago.

The backup is running from my XO VM which is also on the same XenServer as the Windows server if that matters.

coliver

Is Terminated a good thing in this case?

DustinB3403

@coliver said:

Is Terminated a good thing in this case?

If it's red, no.

Green yes.

dafyre

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

Edit: Dustin beat me to it.

coliver

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

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