@BRRABill I like use refurb parts for that, like https://www.servershop24.de/en/components/controller/sas/hp-smart-array-p400-raid-controller-256-mb-sas-pci-e-447029-001-low-profile/a-105422/

Unbeatable price/perf ratio.

@DustinB3403 No that was real ^^

@DustinB3403 That's exactly what I've done with one client, and I'm stopping there.

@scottalanmiller said in What You Need to Know About XenServer:

@olivier An aside, have you considered selling general XS support? Even for those not necessarily running XO? Just wondered if it was ever considered as a lower cost alternative to inclusive support from Citrix might be a valuable market offering.

@DustinB3403 said in What You Need to Know About XenServer:

Also @olivier I think it would be a great opportunity as well for you to offer general XS support as well.

I don't think you really imagine the colossal amount of work needed to do that. I got ONE customer with XS support included, and during the XS7 disk bug, I spent almost an entire week helping him. Multiply this by more or less 100, and you see the problem. It's not doable with our current size: we can't sell something we can't be sure to deliver. Plus we'll need a team able to be up 24/7, which needs around 8 people dedicated to at least having someone covering a time slot.

@scottalanmiller That would:

• trigger a support shitstorm with people filling XOA disks
• we have no control inside customer infrastructure to know which XS host can access it and on which IP, eg in case of various DCs (cause of lot support ticket obviously) -> FYI, 90% of our support requests are for misconfigured XS or NFS/SMB mount.

Ideally, streaming the ISO would be great, but it's not really possible with how XS deal with this.

Main reason to have not thin pro by default is the quality of code for working on files rather than blocks (with LVM).

In file situation, XenServer has to write metadata twice (like in NFS situation by the way). Historically (and today until SmapiV3), the code managing files is a mess.

Personally, I never encountered problems using files (in fact I encountered less issues using NFS).

About ISOs repo: design pattern to work with ISO is shit. And that's really hard to do anything like this on our level (ie with XAPI calls). I hate this because people without XS knowledge often blame us for that We can't stream ISOs, those repo are read only and everything you can imagine to be complicated to workaround. If you want to read more, see https://github.com/vatesfr/xo-web/issues/288 for discussion.

Open an issue and ideally send a PR with the fix: that would be your first (easy) contribution to the project

@Fetakungen see my previous post too, I would like to have it at text, not an image

edit: to have a bit before and after too.

It's xo-server-transport-email (not auth). No need to install it globally.

I don't get what you don't get about this ^^

Clicking on those link won't destroy the universe: go click and see where are you going

One send you to a Pull Request (PR), a piece of code written by someone and send "sent for review". Julien (lead dev) checked the diff (code modified) and then merged it in the next-release branch.

The other link directly to a commit fixing the issue

edit: a PR can embed multiple commits

@Fetakungen xo-server output when the issue is triggered.

Closed means the issue is "finished": without extra comment or specific tag (like duplicate, invalid or won't fix), it means that's solved.

You can follow links to see what fixed the issue (in the "via #1347" or the commit hash).

TL;DR: issues fixed. Will be released in the "next wagon".

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.

@BRRABill I guess depends of Samba config

Report any issue

@Fetakungen I would like to see the logs (in text format please). I bet on a broken SMB protocol thing (either on the lib we use or the SMB server). We tested it against Windows Server SMB, not Samba. The issue is probably there. NFS should work better.

@BRRABill Everything should be reported there: https://github.com/vatesfr/xo-web/issues

Feel free to report!

Oh ok. No that's good, whatever schedule, not enabling the job and that's it

Why not make a manual run? (the "play" button) without enabling the job.