Every time I run a backup, the file gets created on the server, naturally. However, when a new backup is run, either manually or automatically, another new file is created on the server, as well as the old one. After a week, I have 7 files in the backup folder. If it's relevant, the folder permissions are 777.
Is there some way of making the plugin remove older files when newer one's are created?
Are you emailing the backups to yourself (as opposed to downloading)? In that case, there's a bug, which will be fixed in the next version, that may cause the backups not to be deleted.
Yeah, they're being email to me. The emailing part works fine, either when it's done manually or automatically. It's just that once the email has been sent, the files are left on the server.
"Save to server" causes the backup file to be written to the backup folder, and it stays there, so I can download it at leisure. Any backups created by this method are always left on the server.
"download to computer" causes the backup to be made, and a download prompt is opened in my browser. Once the file has been downloaded, the copy on the server is automatically deleted.
"email backup to:" no longer works. The file is (apparently) deleted before the email can be sent. Clicking the link in "Backup complete, sending backup via email..." just makes Wordpress throw an error, saying the file cannot be found. The file is created, because I can see it (via FTP) while the backup process is running.
It's almost as though the file is being deleted too quickly now.
Disregard my last comment regarding the emails. I've just had 4 delivered simultaneously, each with a different backup attached, so it seems to be working fine.
I'm using WP 2.6.1, and wp-db-backup 2.2.
Every time I run a backup, the file gets created on the server, naturally. However, when a new backup is run, either manually or automatically, another new file is created on the server, as well as the old one. After a week, I have 7 files in the backup folder. If it's relevant, the folder permissions are 777.
Is there some way of making the plugin remove older files when newer one's are created?
Are you emailing the backups to yourself (as opposed to downloading)? In that case, there's a bug, which will be fixed in the next version, that may cause the backups not to be deleted.
Yeah, they're being email to me. The emailing part works fine, either when it's done manually or automatically. It's just that once the email has been sent, the files are left on the server.
Should be fixed in 2.2.1 which I've now released.
Using 2.2.1:
"Save to server" causes the backup file to be written to the backup folder, and it stays there, so I can download it at leisure. Any backups created by this method are always left on the server.
"download to computer" causes the backup to be made, and a download prompt is opened in my browser. Once the file has been downloaded, the copy on the server is automatically deleted.
"email backup to:" no longer works. The file is (apparently) deleted before the email can be sent. Clicking the link in "Backup complete, sending backup via email..." just makes Wordpress throw an error, saying the file cannot be found. The file is created, because I can see it (via FTP) while the backup process is running.
It's almost as though the file is being deleted too quickly now.
Disregard my last comment regarding the emails. I've just had 4 delivered simultaneously, each with a different backup attached, so it seems to be working fine.
Thank you very much for this plugin.
RSS feed for this topic
Reply
You must log in to post.