Skip to content

Commit b1abced

Browse files
committed
Relocating migration strategies chapter.
1 parent cf33ab9 commit b1abced

File tree

2 files changed

+29
-19
lines changed

2 files changed

+29
-19
lines changed

src/content/docs/r2/data-migration/index.mdx

Lines changed: 1 addition & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -55,22 +55,4 @@ Quickly and easily migrate data from other cloud providers to R2. Explore each o
5555
</tbody>
5656
</table>
5757

58-
## Migration strategies
59-
60-
You can use a combination of Super Slurper and Sippy to effectively migrate all objects with minimal downtime.
61-
62-
### When the source bucket is actively being read from / written to
63-
64-
1. Enable Sippy and start using the R2 bucket in your application.
65-
- This copies objects from your previous bucket into the R2 bucket on demand when they are requested by the application.
66-
- New uploads will go to the R2 bucket.
67-
2. Use Super Slurper to trigger a one-off migration to copy the remaining objects into the R2 bucket.
68-
- In the **Destination R2 bucket** > **Overwrite files?**, select "Skip existing".
69-
70-
### When the source bucket is not being read often
71-
72-
1. Use Super Slurper to copy all objects to the R2 bucket.
73-
- Note that Super Slurper may skip some objects if they are uploaded after it lists the objects to be copied.
74-
2. Enable Sippy on your R2 bucket, then start using the R2 bucket in your application.
75-
- New uploads will go to the R2 bucket.
76-
- Objects which were uploaded while Super Slurper was copying the objects will be copied on-demand (by Sippy) when they are requested by the application.
58+
For information on how to leverage these tools effectively, refer to [Migration Strategies](/r2/data-migration/migration-strategies/)
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Migration Strategies
3+
pcx_content_type: how-to
4+
learning_center:
5+
title: Migration strategies
6+
sidebar:
7+
order: 5
8+
---
9+
10+
import { Render } from "~/components";
11+
12+
You can use a combination of Super Slurper and Sippy to effectively migrate all objects with minimal downtime.
13+
14+
### When the source bucket is actively being read from / written to
15+
16+
1. Enable Sippy and start using the R2 bucket in your application.
17+
- This copies objects from your previous bucket into the R2 bucket on demand when they are requested by the application.
18+
- New uploads will go to the R2 bucket.
19+
2. Use Super Slurper to trigger a one-off migration to copy the remaining objects into the R2 bucket.
20+
- In the **Destination R2 bucket** > **Overwrite files?**, select "Skip existing".
21+
22+
### When the source bucket is not being read often
23+
24+
1. Use Super Slurper to copy all objects to the R2 bucket.
25+
- Note that Super Slurper may skip some objects if they are uploaded after it lists the objects to be copied.
26+
2. Enable Sippy on your R2 bucket, then start using the R2 bucket in your application.
27+
- New uploads will go to the R2 bucket.
28+
- Objects which were uploaded while Super Slurper was copying the objects will be copied on-demand (by Sippy) when they are requested by the application.

0 commit comments

Comments
 (0)