Backup error with space available
-
@Bane Hi Bane.
Could you display the result of a df -h from your dom 0 please?
-
This is a different error from your initial post on Discord. You had
SR_BACKEND_FAILURE_44(, There is insufficient space, )and now it'sENOSPC: no space left on device.So this time, it's an issue on backup storage.
-
df -h output
Filesystem Size Used Avail Use% Mounted on devtmpfs 1.3G 8.0K 1.3G 1% /dev tmpfs 1.3G 248K 1.3G 1% /dev/shm tmpfs 1.3G 9.9M 1.3G 1% /run tmpfs 1.3G 0 1.3G 0% /sys/fs/cgroup /dev/sda1 18G 1.9G 15G 12% / xenstore 1.3G 0 1.3G 0% /var/lib/xenstored /dev/sda5 3.9G 194M 3.5G 6% /var/log tmpfs 250M 0 250M 0% /run/user/0The drive (EXT-USB) I'm backing up to shows 7.2TiB available.
-
And what about the "remote" configuration in XO? Do you know that backup storage are mounted in XO and not XCP-ng, right?
-
@olivierlambert I don't see the drive I'm backing up to when I run mount -l, I do see it under remotes in settings.
-
You can spot it here, it's very obvious.
Can you see the amount of Total disk available? The path you entered is used inside Xen Orchestra virtual Appliance, not from the host/XCP-ng perspective.
There's no such device as
/dev/sdf/backupin your XOA.You need to mount it INSIDE your XO VM, then to create a mount point, and finally point to this mountpoint.
This is a kind of advanced scenario, ideally, you should rely on a NFS share (the easiest thing).
-
-
You are welcome, let us know if you need more assistance on setting the "remote"/backup repo
-
I have the backup setup now for my NFS share. The NFS remote tests fine and the backup job has some success. I am getting the below failures though on 5 VM's. I am posting one example, let me know if I should post the entire log.
Security Onion (gamakbase) Snapshot Start: Apr 22, 2022, 04:03:48 PM End: Apr 22, 2022, 04:03:58 PM xcp-ng-backup transfer Start: Apr 22, 2022, 04:04:02 PM End: Apr 22, 2022, 04:38:03 PM Duration: 34 minutes Error: HTTP connection has timed out Start: Apr 22, 2022, 04:03:58 PM End: Apr 22, 2022, 04:38:03 PM Duration: 34 minutes Error: HTTP connection has timed out Start: Apr 22, 2022, 04:03:48 PM End: Apr 22, 2022, 04:45:18 PM Duration: 42 minutes Error: HTTP connection has timed out Type: full -
@Bane See this thread for solution to HTTP timeouts -- https://xcp-ng.org/forum/topic/5769/keep-getting-http-connection-has-timed-out-on-my-delta-backup?_=1650710290869
-
I applied the fix mentioned in that thread, and now I have more VM's that succeed. However I still have a few that fail with the same HTTP timeout. Is there anything else I should look at?
-
Maybe the huge number of DNS requests could also cause issues. What about testing it? (it's merged on
mastersince recently, be sure to be on the latest commit!) -
@olivierlambert Can you point me to instructions for that?
Thanks
-
If you installed XO from our doc, then it's trivial: https://xen-orchestra.com/docs/installation.html#updating
-
@olivierlambert I updated to the master as you mentioned and I still get the http timeout error on 4 of my VM's.
-
Okay so you are on latest commit? (the commit should be
3ecf099)
-
I'm using the trial with pro support included right now. So, I don't see the commit string in my about section. Is there another way to verify the commit string?
-
Okay, so go on
latestrelease channel and wait for tomorrow's release to make the update
-
When I run the below, I get destination 'xen-orchestra' already exisits.
git clone -b latest https://github.com/vatesfr/xen-orchestra
I'm not an expert so forgive me if this seems like a basic question.
-
-
If you use XOA, then you just have to click on "Update" by using the "latest" release channel. No command line.
-
If you use XO from the source, then please follow the instructions: https://xen-orchestra.com/docs/installation.html#fetching-the-code
-
