加载中
On this page

Storage and backup ​

When to use these options ​

This tool treats project storage and backup recovery as two separate capabilities. Project creators can choose where daily submissions are stored and run an independent backup workflow when they need an additional protection copy.

Project storage ​

A project can connect to your own S3 bucket. Collected files remain in the space you control, so your organization can apply its own security policies, retention rules, lifecycle settings, and cost controls.

This tool works with widely used S3-compatible services, including:

  • AWS S3
  • MinIO
  • Cloudflare R2
  • Alibaba Cloud OSS

Storage is selected per project. You can set the display name and order shown to submitters. External links are also available when files already live in another system and the project only needs to register, organize, or share those files.

Using your own storage gives you:

  • Clear ownership because collected data stays in your space.
  • Flexible migration and independent object lifecycle management.
  • Compatibility with existing access control, audit, and compliance policies.
  • Freedom to change providers without locking a project to one service.

Configure project storage ​

  1. Open storage settings in the project editor.
  2. Choose a configured S3 bucket or external link.
  3. Set the display name and order shown to submitters.
  4. Confirm the project workflow matches the available storage choices.
  5. Save and test submission, viewing, and download with a small file.

Backup and recovery ​

Backup is an independent protection workflow, separate from daily project storage. Configuring project storage does not create a backup; a backup record is available only after a backup task completes successfully.

This tool supports:

  • Backing up all projects or selected projects.
  • Saving a backup locally or to a configured S3 target.
  • Reviewing the backup time, scope, and possible conflicts before recovery.
  • Checking projects, tags, files, and versions after recovery.

Create a backup ​

  1. Open backup and recovery.
  2. Select all projects or a specific project.
  3. Review the time range, scope, and file count.
  4. Choose local backup or a configured S3 target.
  5. Wait for completion and retain the generated backup file or record.

Restore a backup ​

  1. Select an available backup.
  2. Confirm its creation time, included scope, and target location.
  3. Review content that may conflict or be overwritten, then start recovery.
  4. Check projects, tags, files, and versions after completion.

Notes ​

  • Keep a backup before and after important project changes, and periodically verify that it can be used.
  • Configuring an S3 bucket handles daily storage; it does not mean a backup has been completed.
  • Check for conflicting names or versions before recovery.
  • Test a new storage mode with a small file before opening the workflow widely.