Automatic Backup in Laravel not working

[Cyrille09]

scheduling 'backup:clean' and 'backup:run' not working in Laravel 5.7

This is the code I have in Kernel
protected function schedule(Schedule $schedule)
{
$schedule->command('backup:run')
->everyMinute();
}

[freekmurze]

It seems to work in my applications. Could you create a demo app for me to look at where this does not work?

[Cyrille09]

login.zip
Hi Freekmurze
I have uploaded a demo project

[freekmurze]

Could you create a repo for me to look at?

[Cyrille09]

Well, I follow the instruction until the end. However, the backup system is properly working but it does not work with schedule.
These are steps I follow

1. composer require spatie/laravel-backup

2. php artisan vendor:publish --provider="Spatie\Backup\BackupServiceProvider"

3. I add the following code into database.php file in Mysql section
   'dump' => [
   'dump_binary_path' => 'C:\xampp\mysql\bin',
   'excludeTables' => [
   'table_to_exclude_from_backup',
   'another_table_to_exclude'
   ]
   ]

4. Then I run the following code for backup (php artisan backup:run)
   Note: from step 1 to step 4 are working.

5. I run this code: cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1

6. Then I set this code into kernel.php:
   protected function schedule(Schedule $schedule)
   {

    $schedule->command('backup:run')
             ->everyMinute();
   

   }

[FrankFlow]

Hi FreekMurze,
in Laravel 5.8 it returns:
no scheduled commands are ready to go.

In App\Console\Kernel.php

protected $commands = [];

protected function schedule(Schedule $schedule)
{
  $schedule->command('backup:run')->daily()->at('18:42');
}

If I run

php artisan backup:run

everything goes fine

[smartsyncio]

I'm having issues too, manually running the command is fine but the schedule isn't working anymore.

My last scheduled backup was 26th March 19. did laravel have an update that broke things maybe? hmmm

[StanBarrows]

Same problem here:

If i run it with "php artisan backup:run" everything works thine. But not with the Scheduler.

[yagogak]

Same problem here after updating from 6.0.3 to 6.0.7

[tcnjr]

If i run it with "php artisan backup:run" everything works thine. But not with the

Scheduler.

Same problem here php 7.3.3 and laravel 5.8. Has anyone found a solution or another plugin to solve this issue?

[kallekulp]

Same problem here. Any updates?

[stevecrossuk]

This is a problem for me too. I can run "php artisan backup:run" but it won't run to the schedule.

[buiquangduc]

I am facing the same problem too.

I noticed the PHP CLI version when I run php -v on the terminal and the PHP CLI version when the cronjob is run is different.

With php -v on the terminal, PHP output version 7.3.1

With php -v on the cronjob, PHP output version 7.1.23

spatie/db-dumper will only work with version PHP version 7.3 or above, so you will need to make sure you run PHP 7.3 on the cronjob. Below is how I do it:

Get the current PHP path on your terminal:

Change your PHP path on the cronjob:

[kallekulp]

Okay so... I fixed my issue.

If you have this issue make sure to check your kernel file.

The thing was that I was running Laravel's "queue:work" in the Kernel.php so when I ran schedule:work then all the commands only ran once since the queue was the last command and it got stuck there. After I removed the queue:work from the kernel and created a separate cron for it, everything started working as expected!

Awesome package and the issues was on my side.
Thanks

[jorgeirun]

Facing the same problem as above, when I run manually all works perfect but scheduler never fires.

[Cyrille09]

Okay so... I fixed my issue.

If you have this issue make sure to check your kernel file.

The thing was that I was running Laravel's "queue:work" in the Kernel.php so when I ran schedule:work then all the commands only ran once since the queue was the last command and it got stuck there. After I removed the queue:work from the kernel and created a separate cron for it, everything started working as expected!

Awesome package and the issues was on my side.
Thanks