First, create an encrypted repository. Encryption is required by default in Cloudstic.
1
Choose your storage location
Decide where to store your backups. For this example, we’ll use a local directory, but you can also use S3, B2, or SFTP.
# Local storage (default)export CLOUDSTIC_STORE=local:~/backups# Or for S3# export CLOUDSTIC_STORE=s3:my-backup-bucket# export AWS_ACCESS_KEY_ID=your-key# export AWS_SECRET_ACCESS_KEY=your-secret# Or for Backblaze B2# export CLOUDSTIC_STORE=b2:my-bucket-name# export B2_KEY_ID=your-key-id# export B2_APP_KEY=your-app-key
2
Initialize the repository
Create the repository with password-based encryption. We strongly recommend also creating a recovery key.
Write down your recovery key immediately! It will only be displayed once. If you lose your password, this 24-word phrase is your only way to recover your backups.
You’ll see output like this:
╔══════════════════════════════════════════════════════════════╗║ RECOVERY KEY ║╠══════════════════════════════════════════════════════════════╣║ ║║ word1 word2 word3 ... word24 ║║ ║║ Write down these 24 words and store them in a safe place. ║║ This is the ONLY time the recovery key will be displayed. ║║ If you lose your password, this key is your only way to ║║ recover your encrypted backups. ║║ ║╚══════════════════════════════════════════════════════════════╝Repository initialized (encrypted: true).
3
Store your credentials safely
Save your encryption password in a secure location:
Use a password manager (1Password, Bitwarden, etc.)
Write down your recovery key phrase on paper and store it in a safe place
Never commit passwords to version control
For convenience, save your password as an environment variable:
The first backup is always slower because all files must be uploaded. Subsequent backups are much faster due to incremental processing and deduplication.
