This thread will be used to centralize all backup issues related to CBT: https://xcp-ng.org/forum/topic/9268/cbt-the-thread-to-centralize-your-feedback

Hello,

We'll centralize CBT feedback in here: https://xcp-ng.org/forum/topic/9268/cbt-the-thread-to-centralize-your-feedback

Thanks!

Got it. We might ship that in a patch release if it's bundled in our tomorrow's latest XOA release.

@DustinB I may just be blind or looking at the documentation incorrectly but I am seeing a way to create a health check only job. Anyway you can point me in the right direction? Thanks!

Adding a tag to a replicated backup should be trivial (we need to discuss the entire thing to be sure there's no obvious catch with @julien-f ).

DR automated fallback to the original site (re-sync) is planned for this year.

We have already a branch started with CBT (we had first to store the backup metadata outside the snapshot itself because we'll remove it with CBT). This work is now done and now Florent is directly working on CBT 🙂

According to Microsoft you need to use their built in backup feature or a software that supports AD and VSS which will tell the VM OS that it is going to be backed up.
Unless you do this there might be corruption of the AD Databases according to Microsoft.

ALL THO we've been backing up our AD servers with XOA snapshots (Both normal backup and incremental) and had only 1 issue since we started using XOA in 2016.
Since that issue we also use a guest agent (From Ahsay CBS) that makes a Windows System State backup and Windows System Backup.

More info about that can be found here:

https://wiki.ahsay.com/doku.php?id=public:version_9:client:9447_system_state_backup_vs_system_backup

@rporter and @still_at_work There's actually a super useful guide here. If you have any questions feel free to post back here and I'll try to help.

That's because the XAPI database format changed and only a XAPI restart or host restart would have reload XAPI and make it able to ingest the format you had a backup.

@olivierlambert Indeed, changed from DR to CR and is going without issues, nice. Thank you!

Inexplicably, now it's decided to start working right. I didn't do anything to the existing backup job.
f8c9acb1-b4ca-4486-8dfe-b957b94055f3-image.png

I'm glad it seems to be working now but I wish I understood why it wasn't working previously. That makes me nervous that it could stop working in the future without notice.

The only real difference is that I set up a brand new set of VMs to be backed up in the same way to the same remotes using two new backup plans. I guess this is kinda solved...

@Danp That's the same image I referenced but with everything at a single site. I'm looking for details regarding the hosts and SRs. In the documentation that's all hidden inside that green XenServer XCP-ng box.

My concurrency is only 1 right now because I'm trying to find my bottleneck. Regardless of what it's set to, I'm stuck at ~150MBps for the whole backup job. But that's just what the UI reports. Looking at the network stats I see different things moving anywhere from ~50MBps to over 500MBps.

@Andrew Awesome, thanks

@sshughes When you go to 'Home > Hosts > YourRestoreHost > Tab:Network' in XO, is eth1 shown there? If not, it might need introduction.

@olivierlambert yes those 10 in the previous picture are the hosts from this pool

Can you write exactly what you would expect to be written as a "pre written" text?