Backup Continuous Replication hängt!

x-rayd

You mean my backup setup?

Danp

Hard to say what would cause this issue. What version of xo-server / xo-web are you currently running?

x-rayd

@Danp said in Backup Continuous Replication hängt!:

Hard to say what would cause this issue. What version of xo-server / xo-web are you currently running?

xo-server 5.57.3
xo-web 5.57.1

Danp

You are out-of-date again. Latest is 5.59.x, and there will likely be another release around EOM.

x-rayd

@Danp said in Backup Continuous Replication hängt!:

You are out-of-date again. Latest is 5.59.x, and there will likely be another release around EOM.

my pool have two nodes, but only master node have this problem!

x-rayd

I do not understand!
Every day have pool-master orpharned disks and I delete it.
Why does that happen?

karlisi

I have the same problem since... I don't remember, a year perhaps. Orphaned snapshots are some way related to continuous replication, they appears randomly sometimes on almost all VMs, sometimes none. For me this is not a problem, I delete them as part of daily routine.
I am using XOCE, xo-server and xo-web 5.59.0.

x-rayd

@karlisi said in Backup Continuous Replication hängt!:

I have the same problem since... I don't remember, a year perhaps. Orphaned snapshots are some way related to continuous replication, they appears randomly sometimes on almost all VMs, sometimes none. For me this is not a problem, I delete them as part of daily routine.
I am using XOCE, xo-server and xo-web 5.59.0.

This problem have only pool-master node, other node does not have the problem.

karlisi

@x-rayd said in Backup Continuous Replication hängt!:

This problem have only pool-master node, other node does not have the problem.

Perhaps. I have 2 pools with one node each.

x-rayd

that means every pool-master has this problem

x-rayd

@karlisi said in Backup Continuous Replication hängt!:

Orphaned

must delete every day orphaned snapshots!
No solution for this Problem?

olivierlambert

We don't have any other report of this issue elsewhere. Double check you are on the completely latest XO version, and alternatively, try with XOA on latest channel.