Skip to content

Commit 56f25dc

Browse files
author
Sasha Simic
committed
FRS corruption recovery: minor edits.
1 parent 1fd30bc commit 56f25dc

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/azure-fluid-relay/how-tos/container-recovery.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,27 +8,27 @@ ms.service: azure-fluid
88
ms.topic: reference
99
---
1010

11-
# Recovering Fluid data
11+
# Recovering container data
1212

1313
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.
1414

1515
## How Fluid Framework and Azure Fluid Relay save state
1616

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.
1818

19-
## Azure Client APIs
19+
## Azure client APIs
2020

2121
We've added following methods to AzureClient that will enable developers to recover data from corrupted containers.
2222

23-
[`getContainerVersions(id, options)`](https://fluidframework.com/docs/apis/azure-client/azureclient/#azure-client-azureclient-getcontainerversions-Method)
23+
[`getContainerVersions(ID, options)`](https://fluidframework.com/docs/apis/azure-client/azureclient/#azure-client-azureclient-getcontainerversions-Method)
2424

2525
`getContainerVersions` allows developers to view the previously generated versions of the container.
2626

27-
[copyContainer(id, containerSchema)](https://fluidframework.com/docs/apis/azure-client/azureclient/#azure-client-azureclient-copycontainer-Method)
27+
[copyContainer(ID, containerSchema)](https://fluidframework.com/docs/apis/azure-client/azureclient/#azure-client-azureclient-copycontainer-Method)
2828

2929
`copyContainer` allows developers to generate a new detached container from a specific version of another container.
3030

31-
## Example Recovery Flow
31+
## Example recovery flow
3232

3333
```typescript
3434

@@ -65,9 +65,9 @@ async function recoverDoc(
6565

6666
```
6767

68-
## Key Observations
68+
## Key observations
6969

70-
### We are creating a new Container
70+
### We're creating a new Container
7171

7272
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.
7373

0 commit comments

Comments
 (0)