-
-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems backing up #65
Comments
Hi, there is no limit on the backup size. Could you try upgrading to the latest version of this package? |
Great, thanks :) I think I might have found the problem. I see that my disk space was 94% full. Is it possible that this package temporarily stores the backup before its transmitted, and that it didnt delete this temp as the transfer failed? Or is there any other way there are backups stored on the server that is not deleted? |
There were some problems regarding the cleaning of temp files in version < 2.8.3. If you upgrade to the latest version the package will clean up after itself :-) |
Okey, I will try that :) Is there anything I need to know before upgrading? Any config that has to be done again? |
Nope, there are only breaking changes when upgrading to a major version. If you're using 2.x now you shouldn't have any problem upgrading. |
Thanks! |
Hi again, sorry to bother you. The backup has run as planned for two days since the last problem, but last night I got the following error:
Do you know the reason of this error? |
Unfortunately not. This package just uses the Laravel Cloud filesystem which using Flysystem under the hood. Best to check there what the source of this error could be. |
Okey, thanks! |
Hi!
This plugin have worked great until January 17th. I get the following error:
[2016-01-17 03:02:34] production.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Call to undefined method Spatie\Backup\Commands\BackupCommand::warn()' in /home/forge/domain.com/vendor/spatie/laravel-backup/src/Commands/BackupCommand.php:44
As I can see on line 44, the error message is "The zipfile that will be backupped has a filesize of zero.". The last backup size is 532MB. Is there a limit on backup size?
I am also running a separate backup job with DB only, and there has not been any problems with this.
The text was updated successfully, but these errors were encountered: