Weave Code
Laravel Backup Server Laravel Package
spatie/laravel-backup-server
Securely store and manage backups from multiple Laravel apps on a dedicated backup server. Built on spatie/laravel-backup, it automatically receives and organizes incoming backups, with setup and docs tailored for Laravel deployments.
Backup multiple applications
Frequently asked questions about Laravel Backup Server
- How do I set up a dedicated Laravel backup server to handle backups from multiple Laravel applications?
- Install the package via Composer (`composer require spatie/laravel-backup-server`) on your Laravel backup server. Configure the server to receive backups by defining sources (remote Laravel apps) and destinations (storage disks) in the `config/backup-server.php` file. Use SSH keys for secure authentication between source servers and the backup server. Detailed setup instructions are available in the [official documentation](https://docs.spatie.be/laravel-backup-server/).
- Does spatie/laravel-backup-server support Laravel 10, and what are the minimum Laravel version requirements?
- The package is compatible with Laravel 9 and 10. Check the [Packagist page](https://packagist.org/packages/spatie/laravel-backup-server) or the [CHANGELOG](https://github.com/spatie/laravel-backup-server/blob/main/CHANGELOG.md) for the latest version and its supported Laravel versions. Always ensure your Laravel version aligns with the package’s requirements to avoid compatibility issues.
- Can I back up databases alongside file backups using this package?
- No, this package does not natively back up databases. It focuses on file backups via rsync. For database backups, you’ll need to integrate custom scripts (e.g., `mysqldump`, `pg_dump`) as `pre_backup_commands` or use third-party tools like Percona XtraBackup. Ensure these scripts are synchronized with your file backup workflows to maintain consistency.
- How do I secure SSH credentials for backup sources in a production environment?
- Use SSH key pairs for authentication between source servers and the backup server. Store private keys securely using Laravel’s environment variables or a secrets manager like HashiCorp Vault. Avoid hardcoding credentials in configuration files. For added security, restrict SSH access via firewall rules and disable password authentication on the backup server.
- What storage destinations are supported, and how do I configure cloud storage like S3 or Google Cloud Storage?
- The package supports any filesystem disk configured in Laravel’s `filesystem.php`, including S3, Google Cloud Storage, and local disks. Configure your storage destination in `config/backup-server.php` under the `destinations` array. For cloud storage, ensure your Laravel application has the appropriate SDK (e.g., AWS SDK for S3) installed and credentials properly set in `.env`.
- How can I monitor backup jobs and receive alerts for failures or completed backups?
- The package emits events like `BackupCompletedEvent` and `BackupFailedEvent`, which you can listen to using Laravel’s event system. Subscribe to these events in an event service provider to trigger notifications (e.g., Slack, email) or log backup statuses. Integrate with monitoring tools like Datadog or Sentry for observability in production environments.
- Will this package work if my Laravel applications are hosted across different cloud providers (e.g., AWS and GCP)?
- Yes, but you’ll need to manage SSH access and network latency between cloud providers. Ensure SSH keys are properly configured for cross-cloud access, and consider the egress costs of transferring data over WAN. For hybrid setups, test backup performance and reliability, as rsync over high-latency networks may impact speed.
- How do I handle large backups efficiently, and can I compress or chunk them to reduce transfer time?
- The package uses rsync for transfers, which is efficient for incremental backups but doesn’t natively support compression or chunking. For large backups, consider pre-compressing files on the source server before transfer or using tools like `tar` with compression flags. Alternatively, explore third-party solutions for chunked uploads if rsync performance becomes a bottleneck.
- Is there a way to automate cleanup of old backups to manage storage costs?
- Yes, configure retention policies in `config/backup-server.php` under the `retention` section. Define rules to keep backups for a specific number of days or versions. For automated cleanup, schedule a Laravel command or cron job to run the `spatie::backup-server-cleanup` command periodically. Monitor storage usage to adjust retention policies as needed.
- What are some alternatives to spatie/laravel-backup-server for centralized Laravel backups?
- Alternatives include **Laravel Forge’s built-in backup tools**, **Veeam Backup & Replication** (for broader infrastructure support), or **custom solutions using rsync + cron**. For database-heavy backups, consider **Percona XtraBackup** or **AWS Backup** (if using AWS). Evaluate alternatives based on your need for Laravel-specific features, ease of setup, and support for multi-cloud or hybrid environments.
Weaver
How can I help you explore Laravel packages today?