Hello,
I am confused about this text, especially the first sentence:
*The mirror requires a backup since it does not maintain any state. The actual state of the latest committed database transaction is stored within the primary and the backup space instances, not in the Mirror. Essentially, the Mirror acts as a dispatcher and pushes the changes done in the space (all primary partitions) into the Database (or any other data source) in an asynchronous reliable manner. In case of a failure of the Mirror, it will be restarted automatically and the primary instances will playback the un-committed transactions while the Mirror was down.*
from this page: http://docs.gigaspaces.com/xap102/asynchronous-persistency-with-the-mirror.html
Does the mirror require a backup?
Thanks.
-Dan
↧