Jump to:
| Project: | Backup and Migrate |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
First of all, this is an amazing module, especially with the changes that have been made in version 2!
I have a single drupal installation running multiple sites including some shared tables between several of the sites. I was looking at the database destinations and the ability to use these as backup sources and it would make my backups a lot more simplified because I could centralize them and work with them all at one site, rather than having to maintain a bunch of destinations and profiles in multiple sites. If you have other suggestions let me know.
As I was playing with the database destinations I noticed a few issues:
1. In the newest version profiles do not allow you to select a backup source. On my production system I am running a version from July 8, 2009 which does allow this.
2. In the July 8 version - when you edit a profile the backup source always gets set back to the default database and you need to select the other source each time.
3. In the July 8 version - when you select a different backup source it would be nice if the database tables listings could be updated to show the tables listed in the selected backup source. All of the databases that I'm working with are drupal databases, but not all have the same modules installed, so I'm not able to see all of the tables that are in some of these databases.
Also, more as just a question about how destination databases work. I noticed that you can set your backup destination to a database destination. How does this work? If I choose a database as my destination will it restore the new backup over that database? If it does, would there be a way to disable this so that it doesn't accidentally get selected causing the loss of one of the databases?
Again, thanks so much for this module, it is saving me hours of work every day.
Comments
#1
Hi there,
no. 1 is a deliberate change. It was an attempt to simplify the user interface of the module but the changes did come with a downside. Basically now profiles are independent of the source. That means if you create a profile called 'no-cache-zipped' for example, you can use it with any of the available sources. You can chose the source and the profile independently on the quick backup screen and in your schedules.
The downside of this, as you've noticed, is that the table exclude settings cannot be tuned to the specific tables in each source. I'm still trying to find a clever way to solve both of these needs. I'll keep you posted on what I come up with.
Backing up to a database works as you expect, but I probably do need to make that an opt-in feature as it is quite confusing and dangerous.
Thanks
Ronan
#2
Ok the default db can no longer be used as a destination which should clear up the last concern you mention. I'm still trying to figure out the most elegant way to handle profiles with multiple sources.
#3
Thank you. I'll look forward to what you can come up with. Let me know when you have something out that you need someone to test with.
I'll try to remember to keep trying the latest dev versions. Great module!
#4
Work on this ticket will now be at #793240: Unable to exclude tables from non drupal db