XO backup, is this mess made with intention?
-
So i finaly bite in the apple and fired up a XO instance to perform some backups, my plan was to investigate the possibility for retiring my scripts.
what i found reading about backups in XO made me want to jump in a river head first, its a complete mess!
so we have backup jobs, starts out nice, each job has a planer for running this job called schedule, we can have many schedules, still amazing what!?
so to decide what kind of backups you want, here we have a naming issue, old names, new names, incomplete names, self contradictory names, huh, but not to hard to dig in with the docs. so we further move over to try defining a plan, allready concluded that a backup strategi needs multiple backup jobs, metadata, delta backup, some full ones and XO itself. starting out with the deltas, nice with long term retention policies, needing some daily, more weekly and maybe some monthly, great this gone be nice
so to accomplish this we need a schedule to run this not to complicated, but what is backup retention doing there? and how will that override the long term retention and what about multiple schedules? oooh my, this gona be nice i see! lets look at the docs! nada!so after fidling around a little i see i need some kind of sequence to run all this jobs in, whaat, you are supposed to add schedules to this sequence? i have to admit i starting to get a little warm here, scheduling a sequence to run at intervals, with backup jobs schedules in it at different hours, what the actual f... what is going to run when, and what is going to be backed up with what retention policy?
so here you have it, a complete mess! i think iam leaving this Xen Orchestra as fast as i got it up and running, my dear scripts and xcp center, seems we are going to live a long life together....
-
@Prilly For each it's own
-
I had to just play around with it and see what happens, I feel like I watched videos explaining it fairly good but I you are right. Theres tons of options and they keep adding more which is nice. Just makes understanding whats happening a little more challenging. If you have hardware for it spin up a test lab and try it out.
-
@Prilly Haha, instead of running
️ why not stick it out a bit, figure it out and contribute to the documentation so others don't have this experience?I'll admit, though, I haven't played around with the backup functionality a lot but looking forward to trying it out in my lab.
-
Oh, yes, this is something, I don't understand too. I feel, new things like long term retention etc. could be useful, but... OK, I'm using from sources, no support, learn to swim by yourself. And don't use in production
But why by introducing completely new features, no clue in documentation how it all interacts, what goes first, what overrides.
XO perhaps needs some backups overview page, to see what will be result of all my complex backup schedules, sequences and settings. -
@karlisi Could you please elaborate why you cant use open source in production? do you think the software is any better with a payed support agreement? do you think the vendor you pay actual is liable for any damage if its not working? do you pay for the expertise from someone other than you to service your infrastructure, so you sit there running critical stuff without knowing what it is or how to fix it yourself just waiting for the vendor to EOL your shit and practically force you on to something new because you dont know how it works? you seems to be a microsoft guy, trained in the spirit that you need to dance by the book of your vendor supplying your hardware and software!
stop doing this, you are the customer, if the vendor cant comply and follow your pracises, find something else to use, they are SUPPORT it means they should SUPPORT your way of doing stuff, not placed in a ticket line where you beg to get them fixing your shit you pay for because documentation on in depth product knowledge is not know to you.
so you are practically downgraded to a support agreement contract portefolio manager?
Stop supporting this crap and dont think open source is any problem to run in production!!
when it comes to pay for the development and contribution from Vates into the XCP-ng project for us to use is something else then support, and that i fully agree with!
-
@Prilly Man you need to calm down. Your post(s) with shit here shit there has bad "tone".
I don't think this will get a lot of help/attention from Vates.
And they are more than helpful, even without payed support.
-
@Prilly said in XO backup, is this mess made with intention?:
@karlisi Could you please elaborate why you cant use open source in production?
In short
"If you are considering using Xen Orchestra in production, please subscribe for one of our professional support plans."
https://docs.xen-orchestra.com/support#community-support -
@Prilly Looks like @lawrencesystems has a good explainer video on YouTube at https://youtu.be/weVoKm8kDb4?si=QH93rOKaXLglrIbS
Check it out when you get a chance, thanks.