You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
backupSuffix is stored in config, config file only get refresh if you optimize cache, so if you did not optimize laravel time to time, it will get the backupSuffix the last optimized date, so new backup will automatically delete the previous backup since it has the same name or suffix.
I run the backupmanage:create on cron every week and it only backup single file which is the latest.
My suggestion would be, change the backup_file_date_suffix in config file to only date format not the date() itself and in
// backupmanage.php config
backupSuffix is stored in config, config file only get refresh if you optimize cache, so if you did not optimize laravel time to time, it will get the backupSuffix the last optimized date, so new backup will automatically delete the previous backup since it has the same name or suffix.
I run the backupmanage:create on cron every week and it only backup single file which is the latest.
My suggestion would be, change the backup_file_date_suffix in config file to only date format not the date() itself and in
// backupmanage.php config
//BackupManager class
Thank you.
The text was updated successfully, but these errors were encountered: