What do you mean "how it works"? It's the same thing than before, just "isolated" from the rest, working in a... worker. And yes, the long run objective is the ability to run it as a service on the remote directly, reducing a lot the merge time (because latency is the worst enemy of merging).

@olivierlambert said in Backup does not work if one host in the pool is offline: When you connect to a working, machine, yes it does But XAPI connection isn't persistent: it means, when the pool is disconnected, XO has no recollection whatsoever on who was the "real" master the last time it was connected. The only info we store is the IP address you entered in Settings/server. I agree, functionally speaking, it can be limiting in your case. A viable option would be to save all existing hosts IPs in the XO database, as fallback if we can't connect to the IP you entered. This is not a very common case, that's why it wasn't done before Looks like a good suggestion. Thanks. In my case I migrated everything from the poolmaster to the second host, then changed the second host to pool master, waited an hour and then shut down the old pool master (now just a pool member). XOA was online during the entire process and I had forgotten to check the server list.

That's because the effort to change this will be taken into account in XO 6 Alternatively, you can indeed contribute, this will be very welcome!

Hi ! We are experiencing these kind of problems because we activated Continous Replication and frequency was way too low. Now I want to eliminate all those files in the chain, can I do it manually from XCP-NG Center or XOA ? Thanks !!! [image: 1635327169557-c2aa1fb3-2ed2-41cf-b242-e2a23e6832e4-image.png]

Ping @julien-f and/or @fohdeesha

@pdonias I did an update to Netbox 2.11.12 and it works now, so I don't need to tamper with my XOA.

It can't be done by XO, because XO is using XAPI to make all calls (there's no XAPI command to rename a file on the SR, also XO isn't connected via SSH, so there's 0 change it was caused by XO). So it was done manually at some point (check your host bash history).

Thanks @cookie-eater2000, we'll take a look.

There's no issue nor restriction to replicate a shutdown VM. CR will work as long as the destination VM never booted (otherwise destination blocks will be modified, so you understand now why we should block boot except if you really know what you do )

@julien-f said in Error: footer1 !== footer2: @markhewitt1978 In that case, please open a support ticket there and then, open a support tunnel for us to investigate Thanks. I shall run it one more time manually to make sure. And if it fails I’ll open a ticket Thanks.

@stormi Awesome! Thanks again for your help stormi.

Correct, no problem to do that No other limitation. Yes, space will be reclaimed thanks to coalesce after that.

@ninghe Are A and B identical servers? No shared storage? Does it work if you use normal snapshot mode?

Hi, It doesn't' work that way. XCP-ng is not capable of pushing any data by itself, it has to be pulled. That's exactly why we manage to build XO Proxies to solve this kind of common "enterprise" issue, when you have remote sites

Doing a bit more hunting it seems like if we could get Arcserve to use the nolock option then that would likely solve the problem, but there's nowhere to add any options and the Arcserve Proxy itself uses the Windows NFS client behind the scenes. Right now we've worked around the problem by creating a separate, read-only SMB share pointing to the same location and using that for Arcserve instead. Our only concern now is what could happen if XO starts a job while Arcserve is still doing its own backup. Edit: I did a bit more Googling after posting the above and came across this thread: https://www.truenas.com/community/threads/nfs-the-process-cannot-access-the-file-because-another-process-has-locked.12644/ ... which suggests that it's actually a long-standing TrueNAS bug. Buried within the comments is this suggestion: If you're having trouble with the NFS locking mechanism, and you would like to use the "NET USE" command, or the [WNetAddConnection] function to mount a NFS share without locking, there's an undocumented registry entry hidden in the NFSNP.DLL: "HKLM\Software\Microsoft\Client for NFS\CurrentVersion\Users\Default\Mount" REG_DWORD "Locking" If the value is "0x0" then locking will be disabled globally. If the value is "0x1" then locking will ben enabled globally. We'll test it and report back.

@cbaguzman hi, you could try a hard mount instead of soft, then it should constantly retry until it sees the mount again https://www.ibm.com/docs/en/spectrum-protect/8.1.6?topic=considerations-nfs-hard-soft-mounts

@gskger thank you a lot. I'll try again.

@tsettle I'm using a cloud to save regularly my full backup, but otherwise i'm only using a Truenas with ZFS.

@olivierlambert said in XO console keyboard on iOS and iPadOS - no input possible: No but it doesn't mean this won't be solved with a virtual keyboard anyway It would need to be able to trigger the built in iPad / iPhone keyboard for it to be properly usable.