15308555518/ seafile-admin-docs
1
0
Fork 0
mirror of https://github.com/haiwen/seafile-admin-docs.git synced 2025-12-26 02:32:50 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Add warning for migrating from S3 to other storage. (#435)

This commit is contained in:
Jiaqiang Xu 2025-01-07 10:28:51 +08:00 committed by GitHub
parent 73a7fe4f2c
commit b65cf70bc6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
manual/setup/migrate_backends_data.md
View File

@ -14,6 +14,10 @@ Data migration takes 3 steps:
3. Run final migration
4. Replace the original seafile.conf
!!! warning "Migration from S3"
Since version 11, when you migrate from S3 to other storage servers, you have to use V4 authentication protocol. This is because version 11 upgrades to Boto3 library, which fails to list objects from S3 when it's configured to use V2 authentication protocol.
## Create a new temporary seafile.conf
We need to add new backend configurations to this file (including `[block_backend]`, `[commit_object_backend]`, `[fs_object_backend]` options) and save it under a readable path.

4
manual/setup/setup_with_multiple_storage_backends.md
View File

@ -280,6 +280,10 @@ Then you can add option `for_new_library` to the backends which are expected to
## Multiple Storage Backend Data Migration
!!! warning "Migration from S3"
Since version 11, when you migrate from S3 to other storage servers, you have to use V4 authentication protocol. This is because version 11 upgrades to Boto3 library, which fails to list objects from S3 when it's configured to use V2 authentication protocol.
Run the `migrate-repo.sh` script to migrate library data between different storage backends.
```