Backup to Object Storage or Network Drive

When the local backup file has been generated and you want to continue saving to the object store or to an S3/WebDAV-compatible disk destination, follow the steps below. The specific available destinations are the current version configuration and ppk --help.

Steps to follow

1. Verify that the local backup file has been generated.
2. Confirm that the object storage related information has been written in the configuration, including bucket, prefix, endpoint, region.
3. Perform the upload:

peppykeep backup upload-artifact --apply --input-file /path/to/backup.ppke --config-home /path/to/conf

4. When remote files need to be sampled, perform a download:

peppykeep backup download-artifact --apply --remote-key project-a/backup.ppke --output-file /tmp/backup.ppke --config-home /path/to/conf

5. When the remote history file needs to be cleaned, execute the clean command separately. The upload action itself does not automatically clean up the remote history file.

results verification

• The remote object is already visible.
• The object naming is consistent with the project identity, prefix settings.
• Downloaded files can be decrypted or reverted directly.

Order Details:

• backup upload-artifact
• backup download-artifact
• Remote History Cleanup