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
Remote Cleanup on Dropbox #175
Comments
There are some files missing in the PHAR file. I'll try to figure out which ones and fix it ASAP |
In order to make the dropbox collections work some class aliases and helper function have to be loaded.
I just release version 5.1.8 |
Hello, However, I have about 1000 backups in the Dropbox folder (but, I want only the last 240 -- per the XML cleanup option). In my local web server, I have the correct number of backups. After running it with the cleanup options added in the XML from my previous message, I noticed that it did not clean up the old files in Dropbox. I ran version 5.1.8, with the debug switch and here's the log (sensitive info removed):
|
Thanks for the detailed feedback, I will try to reproduce this |
OK I found the cause for this issue DropboxRemoteCollector is collecting "all" remote backups ;) 'limit' => 100, So we will only search for 100 Backups and will never delete any because 100 is always below 240 :) |
I removed the limit. The default API limit is 1000. |
I see! Perfect. Thank you for the quick update. The 1000 files were there because I wasn't doing cleanups on a regular basis. For me, and my use case, I do hourly backups, and keep them for 10 days in case need to go back due to some human error that wasn't detected in time. (24 hours * 10 days = 240) :-) Again thank you for your quick help in resolving this! |
Hello,
When using the latest version, phpbu-5.1.7.phar. It works fine, with a dropbox sync, but the dropbox cleanup does not work. I downloaded the .phar from the releases link.
My PHP Version:
When I add these lines:
to the DropBox section (entire block here):
I get the following error:
Am I missing something?
Thanks,
The text was updated successfully, but these errors were encountered: