Summary: How backup space instance recovers its data when started or after a fail-over.
IntroductionThis page describes how a space instance running in a backup mode recovers its data when started, relocated or recovers from a failure. The flow is very similar for all these scenarios and mostly depends on the cluster topology and the space cache policy mode. There is special handling for Transient Entries (persist=false), since they can't be persisted - they are always recovered from the primary. Central Database Topology w/o MirrorWith this scenario - The IMDG is the system of record. The data is usually persisted through the Mirror service. LRU Cache PolicyA backup instance recovers only transient entries from the primary instance. Data is not loaded from the database. Since primary and backup use the same database instance, the data will be loaded to the backup on demand. All In Cache PolicyA backup instance recovers all its data from the primary instance - data is not loaded from the database. This is done so that any data changes on the primary during the recovery process are consistent on the backup once recovery finishes. Distributed Database TopologyPrimary and backup keep and manage their data in a different database instance. With this scenario:
For further info and configuration options see Distributed Databases Backup Instance Recovery Failure HandlingIf a backup space instance recovery process fails, it is handled in the following way: |
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |