Replies: 4 comments
-
Hmm do see cleanup fails
and
Seems the host is not accepted by database server as we use 127.0.0.1 and 10.0.0.3 . Strangely enough our
|
Beta Was this translation helpful? Give feedback.
-
Used Sequel Ace to add user |
Beta Was this translation helpful? Give feedback.
-
post addition of [email protected] to database forge I did another cleanup test that passed:
and email with
But still seeing unreachable and no backups.
I think I need to change the disk from |
Beta Was this translation helpful? Give feedback.
-
Think we need to update this ...
'monitor_backups' => [
[
'name' => env('APP_NAME', 'laravel-backup'),
'disks' => ['local'],
'health_checks' => [
\Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumAgeInDays::class => 1,
\Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumStorageInMegabytes::class => 5000,
],
],
/*
[
'name' => 'name of the second app',
'disks' => ['local', 's3'],
'health_checks' => [
\Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumAgeInDays::class => 1,
\Spatie\Backup\Tasks\Monitor\HealthChecks\MaximumStorageInMegabytes::class => 5000,
],
],
*/
... |
Beta Was this translation helpful? Give feedback.
-
We have just set up this amazing package on a new Ploi provisioned Hetzner server. We keep Digital Ocean Spaces for now for storage of our backups. We just ran another round of backups last night and they seem to run well.
But we do a check we get the indication there are issues
I think this is a configuration issue on our side. Perhaps the wrong disk is checked or something. Any pointers on how to make this health check work better?
Beta Was this translation helpful? Give feedback.
All reactions