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
Copy file name to clipboardExpand all lines: articles/azure-fluid-relay/how-tos/container-recovery.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,27 +8,27 @@ ms.service: azure-fluid
8
8
ms.topic: reference
9
9
---
10
10
11
-
# Recovering Fluid data
11
+
# Recovering container data
12
12
13
13
In this scenario, we'll be exploring data recovery. We consider data to be corrupted when container reaches an invalid state where it can't process further user actions. The outcome of corrupted state is container being unexpectedly closed. Often it's transient state, and upon reopening, the container may behave as expected. In a situation where a container fails to load even after multiple retries, we offer APIs and flows you can use to recover your data, as described below.
14
14
15
15
## How Fluid Framework and Azure Fluid Relay save state
16
16
17
-
Fluid framework periodically saves state, called summary, without any explicit backup action initiated by the user. This workflow occurs every one (1) minute if there's no user activity, or sooner if there are more than 1000 pending ops present. Each pending op roughly translates to an individual user action (click, text input etc.) that wasn't summarized yet.
17
+
Fluid framework periodically saves state, called summary, without any explicit backup action initiated by the user. This workflow occurs every one (1) minute if there's no user activity, or sooner if there are more than 1000 pending ops present. Each pending op roughly translates to an individual user action (select, text input etc.) that wasn't summarized yet.
18
18
19
-
## Azure Client APIs
19
+
## Azure client APIs
20
20
21
21
We've added following methods to AzureClient that will enable developers to recover data from corrupted containers.
`copyContainer` allows developers to generate a new detached container from a specific version of another container.
30
30
31
-
## Example Recovery Flow
31
+
## Example recovery flow
32
32
33
33
```typescript
34
34
@@ -65,9 +65,9 @@ async function recoverDoc(
65
65
66
66
```
67
67
68
-
## Key Observations
68
+
## Key observations
69
69
70
-
### We are creating a new Container
70
+
### We're creating a new Container
71
71
72
72
We aren't recovering (rolling back) existing container. `copyContainer` will give us new instance, with data being copied from the original container. In this process, old container isn't deleted.
0 commit comments