Weave Code
Laravel Backup Server Laravel Package
spatie/laravel-backup-server
Laravel Backup Server lets multiple Laravel apps automatically send backups to one dedicated server, building on laravel-backup for secure, centralized storage and management.
Laravel Backup Server extends spatie/laravel-backup by letting multiple Laravel projects automatically send their backups to one dedicated server. Instead of scattering archives across projects, you get a single, secure destination for storing and managing them.
- Centralized storage for backups from many Laravel applications
- Seamless integration with your existing laravel-backup setup
- Secure transfer and management of backup archives
- Monitor and organize backups from one place
- Full setup guide on the documentation site
Frequently asked questions about Laravel Backup Server
- What is spatie/laravel-backup-server used for?
- It is a dedicated Laravel application that receives backups from multiple Laravel projects using spatie/laravel-backup. It stores and manages those archives centrally with its own database, storage, authentication, and UI. It is not a drop-in library for an existing app; you stand up the server and configure each client app to ship backups to it. Its value scales with fleet size, so it pays off once you have several Laravel apps with a shared backup story.
- How do I install and set up laravel-backup-server?
- Run composer require spatie/laravel-backup-server on the dedicated server host, publish the config and migrations, then define sources for each client app with credentials. Each client's spatie/laravel-backup destination is pointed at the server. Full setup guidance is available on the documentation site. Per-app onboarding is small but repeated and is a security-relevant change because it involves credentials.
- Which Laravel and PHP versions does laravel-backup-server support?
- The package has tracked Laravel 9 through 13 and requires PHP 8 or higher on both the server and client sides. It has dropped PHP 7 support. Check the changelog and tagged releases before upgrading major versions. Pin versions in production so upgrades are deliberate.
- How is laravel-backup-server different from spatie/laravel-backup?
- laravel-backup runs inside each application and creates and ships backups to a destination such as S3. laravel-backup-server is a separate server application that aggregates backups from many apps and manages them in one place. You still use laravel-backup on every client app. For a single app, plain laravel-backup to S3 is simpler and cheaper.
- Does laravel-backup-server handle restoring backups?
- The available material confirms that backups arrive and are stored, but restore depth is not verified from the overview. Restore risk is the dominant risk: the package proves backups arrive, not that restores work. You should own a restore drill and may need to script restores yourself. Validate RPO and RTO claims before relying on it.
- Is there a known issue with backup retention or pruning in laravel-backup-server?
- Yes, release 4.3.1 fixed oldest() deleting recent backups instead of old ones. That is a data-loss-class defect in the retention path and it was present in a released version. Pin versions, read changelogs before upgrades, and never let pruning run untested. Test pruning in staging before enabling it in production.
- Is laravel-backup-server secure enough for production database backups?
- The server accepts uploads and holds full database dumps, which frequently contain PII and secrets. You need explicit design review for token handling, TLS, host exposure, at-rest encryption, and key custody. This is the single largest compliance conversation for adoption. Self-hosting must be acceptable to your security and compliance stakeholders.
- When should I use a dedicated backup server instead of per-app S3 backups?
- Use it when you have several Laravel apps with a shared backup story and want central storage and management. For a single app, plain laravel-backup to S3 is simpler and cheaper. Value scales with fleet size. Polyglot estates also need a parallel mechanism for non-PHP services.
- Can I automate onboarding of client apps or manage laravel-backup-server with infrastructure as code?
- The evaluation notes that onboarding is per-app configuration and whether it is automatable via API or IaC is unverified from the available material. Mechanically it involves requiring the package, publishing config and migrations, defining sources, and pointing client destinations at the server. Treat each onboarding as a credentialed security-relevant change. Check the documentation for any API support.
- What are the maintenance concerns and alternatives to laravel-backup-server?
- It is MIT licensed and Spatie-maintained with a small set of named maintainers, so bus factor is real though abandonment is mitigated by licensing and a well-scoped codebase. Low stars and zero dependents mean few third-party eyes and few Stack Overflow answers. Alternatives include per-app laravel-backup to S3, managed backup platforms, or building your own aggregation. Consider the upgrade commitment when Laravel 14 ships and this package lags.
Weaver
How can I help you explore Laravel packages today?