The package can check the health of backups for every application where it is installed. A backup is considered unhealthy if the date of the latest backup is too far in the past to be useful or if the amount of storage space required for all backups is not available.
We recommend setting up a separate Laravel installation to do the monitoring, preferably on a separate server. This ensures you will be notified of unhealthy backups even if one of the applications you are monitoring is broken.
We also recommend to use a central storage disk, like s3, for your backups when using the monitoring. You can still use monitoring for local disks but you'll have to add the monitoring to the app which runs the backups.
To install the monitor follow the regular installation instructions.
Instead of scheduling the
backup:clean commands, you should schedule the monitor command.
protected function schedule(Schedule $schedule)
If you want, you can still schedule
backup:clean to backup the monitoring application itself.
Specifying which backups should be monitored
This is the part of the configuration where you can specify which applications should be monitored and when the monitor should consider the backups of a particular application unhealthy.
'monitorBackups' => [
'name' => env('APP_URL'),
'disks' => ['s3'],
'newestBackupsShouldNotBeOlderThanDays' => 1,
'storageUsedMayNotBeHigherThanMegabytes' => 5000,
name of a monitor should match the value you have specified in the
backup.name-key of the config file in
the application that is being backed up.
0 means the monitor will consider that the backup can use unlimited storage.
Get notifications of (un)healthy backups
You can receive notifications when the monitor finds an (un)healthy backup.
Read the section on notifications to learn more.
Checking all backups
To see the status of all monitored destination filesystems, use this command
php artisan backup:list