Storage Location and Retention Rules

PeppyKeep does not offer cloud or other managed storage. You will need to select and manage your own local disks, S3 compatible object storage, or other storage scenarios; the storage service’s capacity, availability, retention policies, and issues arising therefrom are not covered by PeppyKeep.

Backup files can be saved locally only, or they can continue to be saved to the object store. Which one to choose depends on recovery speed, retention time and far-end retention requirements.

Local save is better for:

• Rapid recovery required
• Keep only historical files for a shorter period of time
• Check the local file before deciding whether to proceed with the upload

Object storage is better for:

• Need to save offsite
• Needs to be kept longer
• Local retention and remote retention need to be disassembled

When configuring object storage, focus on checking:

• bucket
• prefix
• endpoint
• region

Retention rules need to look at two things at the same time:

• How many historical backups to keep locally
• When to clean up the remote history files separately

backup run --upload does not automatically clean up remote history files.
Remote history files need to be cleaned up separately.