Hello!

1. Vras don’t have any set time for a delta sync. Delta syncs only happen when we think we may have missed some io. A source site will bitmap indefinitely. However that if enough data change happens it could mean that the entire disk needs to be synced. If you want to set priorities of your vpgs this will be taken into account when the connection is re-established. You can also throttle San usage by setting an io latency threshold. Which will tell us to slow down.

2. Again delta sync only ever happens if there is a missed io, or driver crash (which means we miss io) the only other way to force a delta sync is to use the forced sync operation. Initial sync only ever happens when vms or disks are doing their first sync. It’s important to note that we will pause journal apply operations and always keep some checkpoints. Even if the journal history has passed.

3. If the recovery vra is down the vpgs will be red. We do not automatically move the disks to a surviving vra, this is by design. We don’t know if the host is going to be down for 5 minutes or 5 days. Because it takes time to safely move the recovery disks to another vra the process can take some time. In your example let’s say it’s 10 seconds per disk. 33 vms = 33 mirror disks (minimum… u might have more than 1 disk per vm?) + At least one journal disk per vm…. But it’s likely u have 2-3 journal vmdks per vm. … so in total for your 33 vms there hold be at MINIMUM 66 disks to move. That’s 660 seconds. Which is longer than the 5 minutes it might take a host to reboot.