@florent increasing the timeout value was the solution. Thank you.

@olivierlambert Thanks yet again.

Pardon me if this has been asked elsewhere but.. The documentation states:

In Xen Orchestra, Metadata backup is divided into two different options:

Pool metadata backup
XO configuration backup

What is the difference between these?

The documentation for the backup health check states:
An example in bash is shown in @xen-orchestra/backups/docs/healthcheck example/wait30seconds.sh
I'm not clear on where this is actually located nor have I been able to find it.

@olivierlambert Thanks yet again.

Pardon me if this has been asked elsewhere but.. The documentation states:

In Xen Orchestra, Metadata backup is divided into two different options:

Pool metadata backup
XO configuration backup

What is the difference between these?

@florent increasing the timeout value was the solution. Thank you.

@florent Thank you, I will try this.

@DustinB XOCE commit 9b6d1, XCP-ng 8.3.0, backup remote is NFS on Synlology.

I started a restore yesterday, and it said it was going to take some hours so I left it running.. When I came back to XO today, there are no pool tasks listed for importing, there is a API call: backupNg.importVmBackup task that is "started," and under Restore shows as started as well but there is no traffic between the system and the remote. It seems this backup will never complete, and I can't cancel it either. The raw data for the restore shows "transfer" is "pending."

Additional info:

uuid ( RO) : 127a8a7b-e277-27dc-802f-7f779676e18e
name-label ( RO): Async.VBD.eject
name-description ( RO):
subtask_of ( RO): <not in database>
subtasks ( RO):
resident-on ( RO): 74e89397-c334-43f5-8322-5331c31ae368
status ( RO): pending
progress ( RO): 0.000
type ( RO): <none/>
result ( RO):
created ( RO): 20251106T19:44:14Z
finished ( RO): 19700101T00:00:00Z
error_info ( RO):
allowed_operations ( RO):
current_operations ( RO):
other-config (MRW): debug_info:cancel_points_seen: 1

@acebmxer Will try at the next opportunity.

@olivierlambert Yes it is. I currently have one eject task at 0% for 19 hours...