Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion src/content/docs/r2/data-migration/super-slurper.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Migration jobs:
- Do not delete any objects from source bucket.
- Use TLS encryption over HTTPS connections for safe and private object transfers.

## When to use Super Slurper
## When is Super Slurper useful?

Using Super Slurper as part of your strategy can be a good choice if the cloud storage bucket you are migrating consists primarily of objects less than 1 TB. Objects greater than 1 TB will be skipped and need to be copied separately.

Expand Down Expand Up @@ -136,3 +136,10 @@ Objects stored using AWS S3 [archival storage classes](https://aws.amazon.com/s3

- Files stored using S3 Glacier tiers (not including Glacier Instant Retrieval) will be skipped and logged in the migration log.
- Files stored using S3 Intelligent Tiering and placed in Deep Archive tier will be skipped and logged in the migration log.

## FAQs
### What happens if I add files to my source bucket mid-migration?
If files are added to your source bucket while a migration is in flight, it is possible that these files will be skipped. To migrate files that were added during a migration, you may need to run migrations multiple times.

### Can I use Super Slurper at the same time as [Sippy](/r2/data-migration/sippy)?
Yes, you can use both simultaneously. Using Super Slurper and Sippy simultaneously is a good solution to migrate buckets which you are actively serving data out of.