Almost every time I am doing a manual backup I am checking if there is any changes to the database that needs to be added to the backup profile, such as new cache tables needed to be amended and so on. This is mainly due to that it is not easy to know everything that goes on with the Drupal tables.

Then I thought, wouldn't it be possible for Backup and Migrate to automatically check this for me? After all, it already have the db settings for each profile and it could then compare that and check if any tables have been added/removed, as well as be able to suggest changes needed for each profile.

For manual, Quick Backup, this could be done when I open the admin/structure/backup_migrate page. There it could tell me if the current profile is up to date or if tables have been added or remove. If there are changes it could give me a link to edit the profile and on that page it will also list the differences as well as suggested changes I should make to the profile, especially which cache tables to not backup the rows for.

For scheduled backups it could use the message area, and Status Report page, to notify me when I am in /admin, as well as optionally send an email notification to an administrator that the scheduled profiles needs to be changed.

In the profiles list there can be an indicator for each profile that needs to be changed.

Something like this would save me time from having to manually check any changes, which I normally do by creating a new profile and comparing the tables that should not have its rows backed up with the current profile.

Comments

ronan’s picture

This would be a nice feature but it's not as simple to implement as it sounds since B&M only stores the tables to excluded, not a list of all tables. This is going to stay low on my priority list because of that and because most use cases don't involve installing modules all that frequently except during development, and even then it's not terribly critical that you exclude every new cache table.

couturier’s picture

Version: 7.x-2.x-dev » 7.x-3.x-dev
Status: Active » Postponed (maintainer needs more info)

Updating version since the 7.x-2.x branch will be deprecated soon. See this issue: Verify 7.x-2.x -to- 7.x-3.x upgrade path, mark 7.x-2.x as unsupported.

I am also setting to postponed due to the limited developmental resources for this module right now, most of which are being directed to the port to D8.

couturier’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing after more than two weeks with no activity.