Continuous Replication Schedul backup Error: Expected values to be strictly equal: 430 !== 512

polyaks

@olivierlambert
Server XOA behind the proxy

olivierlambert

So please configure your proxy in the update view.

polyaks

@olivierlambert
Proxy settings are already persists on the Updates tab

olivierlambert

Please check:

/etc/resolv.conf to be able to resolv tunnel.xen-orchestra.com
that your proxy settings are OK and you can ask for updates on your XOA

Without that, we won't be able to take a look remotely.

polyaks

@olivierlambert
add tunnel.xen-orchestra.com 159.69.135.93 to /etc/resolv.conf and /etc/hosts

But error exist
Warning: Failing to resolve tunnel.xen-orchestra.com, falling back to 212.129.28.35

Update - OK

olivierlambert

We changed the DNS record from the old IP to the new one 1 week ago. So please check your internal DNS to be sure they are refreshed correctly.

polyaks

@olivierlambert
According to information from proxy admins, the XOA server does not connect to the proxy during the creation of the support tunnel.
The netstat command showed that the server is creating a NAT connection.
tcp 0 1 10.44.71.176:43312 159.69.135.93:443 SYN_SENT

This means that the Support tunnel does not use proxy settings.

olivierlambert

Ping @julien-f

polyaks

@olivierlambert
[06:08 15] xoa@xoa:~$ ping tunnel.xen-orchestra.com
PING shelter.vates.fr (159.69.135.93) 56(84) bytes of data.

julien-f

@polyaks Hi, at this moment, xoa support tunnel does not use the proxy configuration defined for the update, you will need to also set the configuration in /etc/xo-server/config.toml.

polyaks

@julien-f @olivierlambert
The support tunnel has been created.

Do not stop this command before the intervention is over!
Give this id to the support: 41699

olivierlambert

Thanks, we'll take a look when we can

julien-f

@polyaks FYI, it looks like a corrupted (truncated) file issue.

You can take a look at this post where I explain succinctly how to check XO backup files

polyaks

@olivierlambert
"Expected values to be strictly equal: 430 !== 512" is not the result of using a GFS2 drive.
On an XOA (non-source) server, the delta backup on the GFS2 drive completed with a successful result

Clarification
During the backup process, I can edit and crate Backup tasks, only to display information about VMs and SRs I need to wait about 5 minutes.

olivierlambert

Delta will fail as soon you'll make a delta. So only the first delta backup on GFS2 will work. Not any other.

See https://xen-orchestra.com/docs/delta_backups.html#continuous for how it works.

polyaks

@olivierlambert
I was able to reproduce the problem on the lastest XOA server.
Give this id to the Support tunnel : 41699

Backup Task settings:

XOA work correct if vCPU settings are 1socket= 1 core

If I change vCPU to 1 socket = 2 cores or 1socket= 4 core

Received error when starting the same task

olivierlambert

As I said, it's normal you can't do delta on GFS2. It's not possible, technically speaking, because GFS2 is using a storage stack that doesn't support delta

polyaks

@olivierlambert
I run the same task all the time without any changes.
How is it determined that the task must be run as full or as a delta?

olivierlambert

Have you read https://xen-orchestra.com/docs/delta_backups.html ?

Use normal backup it will work. Or stick with delta and advanced option, a full every 1 backup.