Team - XO Backend group | XCP-ng and XO forum

pierrebrunet

@gsszuber Hi,
Yes indeed, you need to preserve the root of the bucket from Lifecycle. We just had a customer with a similar issue.
Can you help us by giving a small screenshot of the field to filter out the root (or filter in the three folders) please?

pierrebrunet

@bogikornel are you talking about another issue? We are on an issue specifically on "pool metadata backups". It seems you are talking about VM backups. If yes, can you send the backup log please?

pierrebrunet

@acebmxer ok, too bad... I thought we had it...
@majorp93 this can be a lead. I will ask xapi team if they changed something in pool metadata export.

pierrebrunet

@MajorP93 Hi,
Thank you, thank you! I think you found it! It seems to be SMB, @acebmxer can you confirm that you also use smb please?
If this is the case, the bad news is I think we will need to update our docs to not advise SMB at all: it was already said for delta but maybe we will have to extend this to all kind of BR

florent

@JB this really looks like a network issue

are the host/xoa remotes ?

florent

@JB this looks like an issue while reading the export part. Did you configure a default backup network in the pool ?
is there any firewall/sdn controller that can filter out some reading ?

note that we have removed several point that where hiding some errors this month.

MathieuRA

@acebmxer Thank you for your quick feedback.

MathieuRA

Hi @acebmxer,

Can you test if the branch: fix_cloudinit_import fix your issue?
Edit: It is available on the master branch.

florent

@Andrew @probain
XO was hiding some error message and fell back silently ( or fail later) , this onth updates gives us more information

are you using NBD ( it is mandatory for qcow2 disks) ?
is NBD enable on at least one network per pool ?
can XO access this network ?
is there a default backup network on the pool ? with NBD ? accessible by XO ?

any more logs on journalctl ( I am expecting some nbdinfos )

Team - XO Backend

Posts

Member List