@davealex8 Are you trying to pass a PCIe device into your XOA system rather than a guest on your XCP-ng host?

@kagbasi-ngc I think you'd have to configure some kind of log shipping ahead of time, I don't know that you'll be able to migrate the logs from one XO to another to keep things consistent.

@davx8342 That's a ton of storage, holy cow!

So two pools currently, 6 Servers 31TB Shared, and then 16 servers and 400TB Shared. I honestly don't know if there is an upper or lower limit to the amount of storage supported with XOStor, I'd imagine it would work but someone else would have to confirm.

@davx8342 All servers are Hyperconverged, every server for the entire history of servers.

To ask, how much storage is on your VXRail system today that is shared?
Could this not be better managed using your standard NAS/SAN providers like Synology, 3PAR etc?

I've not used XOStor, but since it's not fully supported on 8.3 yet I don't know that I would consider it feasible until it's fully supported.

Do you have a lot of VMs with more than 2TB of disk attached to each (just curious). I too would love for this to be gone lol.

@nim81 said in Support licensing structure update:

but there's no way I can possibly justify the levels of increase being asked here.

As Olivier has said, your comparing paying for XOA with no support, to XOA and XCP-ng supported in a package deal. I don't know that the Vates team has specifically cancelled the XOA only package, but that is a bit germane to the conversation.

Just use XO from Source, or one of the scripts and move on with your day. If your business grows you can always sign up for support again.

@nim81 said in Support licensing structure update:

to my mind I don't think I've ever even put a single support ticket in

Then you're a perfect candidate for the source edition, no?

@kagbasi-ngc said in How Best to Achieve Higher Transfer Speeds for Backup Jobs:

@lawrencesystems Yes sir I agree, as that is my experience with XOCE. But with XOA (Airgapped), in my PoC Lab, I've received my first upgrade and it was a completely new appliance. So I'm now figuring out how to handle that. I did reach out to Vates support about this and got a response that they are looking into perhaps doing the XO updates kinda like how they handle it now for XCP-ng (i.e., allow us to download the entire repo offline and then do the upgrade that way).

I'm sure you've dealt with many customers who are in my kind of environment, where security/compliance requirements are strict.

Wouldn't you export the configuration from your existing XOA and import it into the new one before it's finalized and "onsite"? That would get you a full working config, from which you may only have to adjust the cpu/ram.

@nim81 said in Price Increases:

I'm out, I'm afraid. With the new pricing structure we're looking at a 550% price increase over last year. I understand that everything's going up in price but there is no possible way I can justify that level.

Just use XO from Source, or https://github.com/Jarli01/xenorchestra_installer or ronivoy's script.

Obviously you're not able to afford the product and support, yet you feel as if you should be given the product for free. Which in that case, build it yourself or use a community provided solution to getting the solution for free.

@ItsAlwaysDNS said in Migrated Linux machine won't start:

@DustinB

I can try to give that a go. Is there any particular reason as to why we think this will work? I'm totally fine with the thought of "its worth a try". I'm just curious if there is some known compatibility issue that is leading you to suggest trying this as a solution.

Normally these older systems were required to use the ESXI drivers, these drivers are also normally very out of date and cause issues.

Most of the time, when these issues occur, it's because of incompatible drivers. Cloning the VM and removing the drivers from the clone and then trying to migrate the VM is the safest way to confirm the issue is with the drivers without impacting your production system.

@ItsAlwaysDNS said in Migrated Linux machine won't start:

When the VM is running on the Vmware host, it reports the tools are running. Looks like its running CentOS 6 (32bit).

CentOS 6 is very out of date, but I can relate to keeping something around longer than it really should be.

Can you make a copy of the VM on your ESXi host, remove the guest tools from the VM and try to migrate the VM without the guest tools?

@KPS this would be for the session, the question I have is what issues are you experiencing?

@eswaran The setting he displayed was within a given VM, not at the host/pool level.

@ItsAlwaysDNS Have you checked your DNS?

No but seriously is the VMWare guest tool installed on this system? What version of linux is it using?

@frank-s You might have no choice but to delete your backup chains and reduce the retention.

It seems like you're really too constrained by your backup repo's capacity.

@frank-s Wouldn't it be easier to adjust your job so you're not keeping so many backups? This way the system will automatically clean up any jobs and help to keep your SR sufficiently freed up?

@frank-s This depends on what type of backup you're running, if you're using Delta or CR then you could cause issues.

If you're using full backups, then each would be distinct from each other.

@Chico008 You'll need to use the "Self Service" options to create a set of permissions that allows your "guest" user to be able to create VMs on the pool.

ACL's are applied separately.

I personally think the permissions configuration needs some serious work, and it seems like the Self Service configuration is the way to go, albeit this is only available in the higher tiers of XOA or XO (Community Edition or from source).

@techjeff said in Invalid Health Check SR causes Bakup to fail with no error:

but I hadn't made any changes to the shares or the underlying storage on that host so I really wasn't sure what could have caused it.

But you did make a change to the pool, you

@techjeff said in Invalid Health Check SR causes Bakup to fail with no error:

So I recently moved my vm disks to a new SR, made the new SR the pool default, and removed the previous SR.

So the issue is that a change was made and that there wasn't some sort of safety net on the home page to warn you to this blunder.

If you're modifying your SRs in any way shape or form, check that your backups are still "healthy" before you move on.

Could there be some sort of main-page or cookie-trail alert that something is off, certainly, maybe just a Yellow Triangle alert on the backup context menu..

@mguimond Could be a bug in a recent release, @Danp are you aware of anything?

@mguimond said in Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.:

master. 221 commits behind

The version that is 221 updates behind works, but your current version does not?