![]() The problem with full backups arises when the checkpoints are large.įor example, a replica that has 16 GB of state will have checkpoints that add up approximately to 16 GB. Since it has the checkpoints and the log, a full backup can be restored by itself. There are two backup options: Full and Incremental.Ī full backup is a backup that contains all the data required to recreate the state of the replica: checkpoints and all log records. The restore APIs allow a service partition's state to be restored from a chosen backup. The backup APIs provided by the platform allow backup(s) of a service partition's state, without blocking read or write operations. The Backup/Restore feature allows services built on the Reliable Services API to create and restore backups. It might be convenient to have offline processing of data for business intelligence that happens separately from the service that generates the data. In such a case, both the code and the data may have to be reverted to an earlier state. For example, this may happen when a service code upgrade starts writing faulty data to a Reliable Collection. Bugs in the service that cause data corruption.For example, this may happen if an administrator with sufficient privilege erroneously deletes the service. Administrative errors whereby the state accidentally gets deleted or corrupted.Permanent loss of a majority of the replicas of a service partition.In the event of the permanent loss of an entire Service Fabric cluster. ![]() Microsoft recommends to use Periodic backup and restore for configuring data backup of Reliable Stateful services and Reliable Actors.įor example, a service may want to back up data in order to protect from the following scenarios:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |