Are there any downsides to using CBT when doing backups?
-
I moved over to using CBT this past weekend. It seems much, much, faster and I didnt have a single error. In the past about 20% of my nightly incremental backups had errors like "can't compute delta OpaqueRef:blah-fba0-ced3-7653-blahblah from OpaqueRef:blah-b53d-3935-1af0-blahblah, fall back to a full"
I have this option "Purge snapshot data when using CBT" set to yes.
I have both of these options set to no as I don't really fully understand the implications (other than the info bubble
"Merge backups synchronously "
"Synchronize snapshots"With that said, are there any downsides to using CBT when doing backups?
Thanks!
-
One potential downside is that CBT makes live-migrations between SRs alot more difficult.
-
P poddingue marked this topic as a question
-
@jr-m4
What would you need to do if that were needed?? -
Last time I tested CBT enabled backups the backup job would sometimes create a full backup for a given VM instead of an incremental one.
This bug got triggered by live migrations. When a VM got live migrated it got processed as full backup by backup jobs even after "normal" live migrations (no storage live migration).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login