Storage Destinations

Storage destinations define where FireBackup stores your backup data. FireBackup supports multiple cloud storage providers, allowing you to choose based on cost, compliance, or redundancy requirements.

Supported Storage Providers

Provider	Type	Best For
Amazon S3	Object Storage	AWS-centric infrastructure
Google Cloud Storage	Object Storage	GCP integration, Firebase alignment
DigitalOcean Spaces	S3-compatible	Cost-effective, simple setup
Firebase Storage	Object Storage	Firebase ecosystem
Custom S3-compatible	S3-compatible	MinIO, Wasabi, Backblaze B2

Adding a Storage Destination

Navigate to Storage Settings

1. Go to Settings in the sidebar
2. Click Storage tab
3. Click Add Storage Destination

Amazon S3 Setup

Step 1: Create IAM User

1. Go to AWS IAM Console
2. Create a new IAM user
3. Attach the following policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:PutObject",
        "s3:GetObject",
        "s3:DeleteObject",
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::your-bucket-name",
        "arn:aws:s3:::your-bucket-name/*"
      ]
    }
  ]
}

4. Create access keys and save them securely

Step 2: Configure in FireBackup

1. Select Amazon S3 as provider
2. Enter configuration:

Field	Description
Name	Display name for this destination
Access Key ID	AWS access key ID
Secret Access Key	AWS secret access key
Region	AWS region (e.g., us-east-1)
Bucket Name	S3 bucket name
Path Prefix	Optional folder path within bucket

3. Click Verify Connection to test
4. Click Save

See AWS S3 Setup Tutorial for detailed instructions.

Google Cloud Storage Setup

Step 1: Create Service Account

1. Go to Google Cloud Console
2. Navigate to IAM & Admin > Service Accounts
3. Create a new service account
4. Grant Storage Object Admin role
5. Create and download JSON key

Step 2: Configure in FireBackup

1. Select Google Cloud Storage as provider
2. Enter configuration:

Field	Description
Name	Display name for this destination
Service Account JSON	Upload or paste JSON key
Bucket Name	GCS bucket name
Path Prefix	Optional folder path within bucket

3. Click Verify Connection to test
4. Click Save

See GCS Setup Tutorial for detailed instructions.

DigitalOcean Spaces Setup

Step 1: Create Spaces Access Keys

1. Go to DigitalOcean Control Panel
2. Navigate to API > Spaces Keys
3. Generate new key pair

Step 2: Configure in FireBackup

1. Select DigitalOcean Spaces as provider
2. Enter configuration:

Field	Description
Name	Display name for this destination
Access Key	Spaces access key
Secret Key	Spaces secret key
Region	Spaces region (e.g., nyc3)
Space Name	Name of the Space
Path Prefix	Optional folder path

3. Click Verify Connection to test
4. Click Save

See DigitalOcean Spaces Tutorial for detailed instructions.

Firebase Storage Setup

Configuration

1. Select Firebase Storage as provider
2. Enter configuration:

Field	Description
Name	Display name for this destination
Project ID	Firebase project ID
Bucket	Storage bucket (default: project-id.appspot.com)
Path Prefix	Optional folder path

Firebase Storage uses the same OAuth credentials as the connected Firebase project.

Custom S3-Compatible Setup

For MinIO, Wasabi, Backblaze B2, or other S3-compatible storage:

Field	Description
Name	Display name for this destination
Endpoint	Custom endpoint URL
Access Key	Access key ID
Secret Key	Secret access key
Bucket	Bucket name
Region	Region (if applicable)
Path Prefix	Optional folder path
Force Path Style	Enable for MinIO and some providers

Managing Storage Destinations

Viewing Destinations

The storage page shows all configured destinations:

Column	Description
Name	Display name
Provider	Storage provider type
Bucket	Bucket/container name
Status	Connection status
Backups	Number of backups stored
Size	Total storage used

Default Destination

Set a default destination for new backups:

1. Click the star icon next to a destination
2. This destination becomes the default for:
   • New schedules
   • Manual backups (unless overridden)

Testing Connection

Verify a destination is working:

1. Click Test Connection on the destination
2. FireBackup will:
   • Verify credentials
   • Test read/write access
   • Check bucket permissions

Editing Destinations

To modify a destination:

1. Click Edit on the destination
2. Update configuration
3. Click Verify Connection
4. Click Save

Changing Destinations

Changing bucket or credentials may make existing backups inaccessible. Ensure you have copies of important data before changing configuration.

Deleting Destinations

To remove a destination:

1. Click Delete on the destination
2. Choose whether to delete stored backups
3. Confirm deletion

Backup Deletion

If you choose to delete stored backups, this action is permanent and cannot be undone.

Browsing Stored Files

View files stored in a destination:

1. Navigate to the storage destination
2. Click Browse Files
3. Navigate the folder structure
4. View backup files and metadata

File Actions

• View Details - See file metadata and properties
• Download - Download backup file
• Delete - Remove individual files

Storage Statistics

Per-Destination Statistics

Each destination shows:

Metric	Description
Total Backups	Number of backups stored
Total Size	Storage consumption
Oldest Backup	Date of oldest backup
Newest Backup	Date of most recent backup
Growth Rate	Storage growth over time

Organization Storage Overview

View aggregate storage across all destinations:

• Total storage used
• Storage by provider
• Storage by project
• Growth trends

Retention Policies

Configure automatic cleanup of old backups:

Setting Up Retention

1. Navigate to storage destination
2. Click Retention Policy
3. Configure retention rules

Retention Options

Option	Description
Keep All	Never auto-delete
Keep Last N	Keep only N most recent backups
Keep N Days	Delete backups older than N days
Keep N GB	Delete oldest when size exceeds N GB

Retention Execution

• Retention runs daily at midnight UTC
• Oldest backups are deleted first
• PITR data follows its own retention settings

Compliance Consideration

Ensure retention periods meet your compliance requirements before enabling auto-deletion.

Storage Sync

Synchronize metadata between FireBackup and storage:

When to Sync

• After manual file operations in storage
• If backup counts seem incorrect
• After storage provider issues

Running Sync

1. Navigate to storage destination
2. Click Sync Storage
3. FireBackup will:
   • Scan storage for backup files
   • Update metadata in database
   • Report any orphaned files

Orphan File Management

Files in storage without corresponding database records:

• Keep - Leave files in storage
• Delete - Remove orphaned files
• Import - Add to FireBackup database (if valid backup format)

Multi-Region Redundancy

For disaster recovery, configure multiple destinations:

Setting Up Redundancy

1. Add primary storage destination (e.g., US-East)
2. Add secondary storage destination (e.g., EU-West)
3. Configure schedules to backup to both

Redundancy Strategy

Primary Destination: AWS S3 (us-east-1)
  - All backups

Secondary Destination: GCS (europe-west1)
  - Daily full backups only
  - 30-day retention

This provides:

• Local access with low latency
• Geographic redundancy for disaster recovery
• Cost optimization by limiting secondary storage

Security Considerations

Encryption in Transit

All data transferred to storage is encrypted using TLS 1.2+.

Encryption at Rest

FireBackup encrypts backup data before upload:

• AES-256-GCM encryption
• Per-backup unique encryption keys
• Keys derived from organization master key

Storage Provider Encryption

Most providers offer additional encryption:

Provider	Default Encryption	Options
AWS S3	SSE-S3	SSE-KMS, SSE-C
GCS	Google-managed	Customer-managed keys
DO Spaces	Server-side	N/A

Double Encryption

FireBackup encryption + provider encryption provides defense in depth.

Service Account Management

Manage service accounts used for storage and Firebase access:

Viewing Service Accounts

1. Go to Settings > Storage
2. Scroll to Service Accounts section

Adding Service Account

1. Click Add Service Account
2. Upload JSON key file
3. FireBackup validates:
   • JSON format
   • Required fields present
   • Scopes available
4. Click Save

Service Account Usage

Service accounts can be used for:

• Storage destinations - GCS access
• Firebase projects - Backup operations
• PITR monitoring - Audit log access

Removing Service Account

1. Click Remove on the service account
2. Confirm deletion
3. Associated destinations will need reconfiguration

Dependency Check

Before removing a service account, ensure no active destinations or projects depend on it.

Troubleshooting

"Connection Failed" Error

Possible causes:

1. Invalid credentials
2. Bucket doesn't exist
3. Insufficient permissions
4. Network issues

Solution:

1. Verify credentials are correct
2. Confirm bucket exists and is accessible
3. Check IAM/permission policies
4. Test from your network

"Access Denied" Error

Possible causes:

1. Missing IAM permissions
2. Bucket policy restrictions
3. Service account revoked

Solution:

1. Review required permissions for provider
2. Check bucket policies allow access
3. Regenerate service account key

"Storage Full" Error

Possible causes:

1. Storage quota exceeded
2. Billing issues with provider

Solution:

1. Check storage quotas in provider console
2. Clean up old backups
3. Configure retention policy
4. Upgrade storage plan

Next Steps

• AWS S3 Setup Tutorial
• GCS Setup Tutorial
• DigitalOcean Spaces Tutorial
• Security & Compliance Reference