Has anyone encountered an issue with failback where it takes significantly longer if quick rollback is enabled?
We're testing CDP on a 1.6TB machine, and a regular failback takes between 1.5 to 2 hours, however with quick rollback enabled it goes between 5 and 6 hours. All of the extra time is calculating the digest (CBT is enabled in both original and replica machine). It's so bad that it's faster to do a permanent failover, re-sync from the secondary site, and do another permanent failover.
I'm at a loss and we're in the process of opening a case, but if anyone has a guess of what it could be meanwhile it'd be greatly appreciated.
-
- Novice
- Posts: 3
- Liked: never
- Joined: Mar 20, 2024 8:40 pm
- Full Name: Sebastian Guajardo
- Contact:
-
- Chief Product Officer
- Posts: 31964
- Liked: 7435 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Failback with quick rollback extremely slow
Just a guess: perhaps it's a very lively VM? As with most of the disk blocks changed, full VM restore is of course going to be much faster than updating each disk block one by one (streaming I/O vs. random I/O).
Who is online
Users browsing this forum: No registered users and 41 guests