When using this module, the number of backups drops by half.
It looks like BU & M counts the number of archives regardless they are db or files.

Comments

Neil Adair’s picture

Yep! I just double the setting if I use files and triple it if I have 2 databases (eg. for CiviCRM).
You need to do this in each schedule.
I usually keep 2 of each so set it to 4 for Drupal db + files and 6 for Drupal db + CiviCRM db + files

inascon’s picture

Actually, I found out that BU&M keeps the most recent number of files in a certain directory, regardless the type or name of those files. So if you use this module for more than one schedule and save the backups in the same directory, e.g. Scheduled Backups Directory (uploads/backup_migrate/scheduled), then each schedule will remove half the files of the other schedule.
I've created a separate directory (Destination) for each schedule and then it works as expected.

Hope that helps.

PS. This is also true for version 6.x-2.x.

jvieille’s picture

Maybe worth telling in module's help

ronan’s picture

Project: Backup and Migrate Files » Backup and Migrate
Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Active » Postponed

This is true, and is being fixed currently. The next major version of B&M will save metadata with the backups so schedules will be able to delete only their own backups. Stay tuned.

jorditr’s picture

Hi ronan,

you said on Apirl 25 that the next release would solve that trouble. I'm using version 2.6 which is from May 7 and having several backup configurations and everyday all the previous ones are completely deleted. Was it solved or it is still pending?

Thanks.

Balbo’s picture

Version: 6.x-2.x-dev » 6.x-2.6
Component: Miscellaneous » Code
Category: task » bug

I'm using 2.6 too and I can tell the issue is still pending.

ronan’s picture

Version: 6.x-2.6 » 7.x-3.x-dev
Status: Postponed » Fixed

The 3.x branch adresses this.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.