Closed (fixed)
Project:
Backup and Migrate
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
22 Feb 2011 at 13:01 UTC
Updated:
25 Jun 2025 at 15:20 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedIt has been pointed out to me that this is probably just a configuration problem. The solution is to create a different destination for each schedule and specify a unique directory in each. This is not immediately obvious, but is no doubt intentional by design.
Closing.
Comment #2
j0rd commented@imonemus I've run into this problem as well. I believe most users will run into this problem. I've been using backup_migrate with Drupal since D5 and I've just realized this problem.
If you plan on leaving the module to function like this, please provide a warning, otherwise users (like me) will experience data loss.
I also believe the default is to store them into scheduled/ folder, thus creating this problem for users by default. It would be smart perhaps, when a new schedule is created, to auto create/assign a sub-folder for them, thus negating additional configuration and data loss.
Comment #3
ronan commentedThe 3.x branch fixes this by tagging each backup with the schedule that created it.