You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to VM fault tolerance. I'm not sure if Cuju guarantees the shared storage state or not. Some fault-tolerance solutions use either storage snapshot, or a private storage for the secondary VM, to preserve the storage state while checkpointing. How does Cuju handle this issue? Alternatively, is there any best practice for using shared storage? Thanks.
The text was updated successfully, but these errors were encountered:
Actually, we use shared storage for primary and secondary VM and only primary VM can write the storage. And we buffered disk write operations when the memory state was not fully backed up to the secondary side.
In other words, when backed up finished, we release the buffered disk write operations to the shared storage. So it can make the shared storage state consistent with backed up state
Hi,
I'm new to VM fault tolerance. I'm not sure if Cuju guarantees the shared storage state or not. Some fault-tolerance solutions use either storage snapshot, or a private storage for the secondary VM, to preserve the storage state while checkpointing. How does Cuju handle this issue? Alternatively, is there any best practice for using shared storage? Thanks.
The text was updated successfully, but these errors were encountered: