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
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.
Copy file name to clipboardExpand all lines: src/content/docs/r2/data-migration/super-slurper.mdx
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,10 @@ This setting specifies the prefix within the source bucket where objects will be
45
45
46
46
#### Overwrite files?
47
47
48
-
This setting determines what happens when an object being copied from the source storage bucket matches the path of an existing object in the destination R2 bucket. There are two options: overwrite (default) and skip.
48
+
This setting determines what happens when an object being copied from the source storage bucket matches the path of an existing object in the destination R2 bucket. There are two options:
0 commit comments