When creating a backup profile, the module by default sets the following tables to have their data excluded according to issue #209647: Exclude advice:

  • cache
  • cache_filter
  • cache_calendar_ical
  • cache_menu
  • cache_page
  • cache_views
  • sessions
  • search_dataset
  • search_index
  • search_keywords_log
  • search_total
  • watchdog
  • accesslog
  • devel_queries
  • devel_times

When the backup is reloaded, those tables are dropped, recreated, and left empty. This is a sane default, but doesn't work well if the module is used to migrate data from a development site to a production site. I would recommend that the module come with a couple of default profiles based on different use cases, and the user could then customize one of the defaults for their circumstances.

For a "site migration" default, I would recommend that these tables be excluded altogether (because I wouldn't want to lose the production data):

  • watchdog
  • node_counter
  • accesslog

and these tables would have just their data excluded:

  • cache
  • cache_block
  • cache_calendar_ical
  • cache_content
  • cache_filter
  • cache_form
  • cache_location
  • cache_menu
  • cache_page
  • cache_reptag
  • cache_update
  • cache_views
  • cache_views_data
  • devel_queries
  • devel_times
  • search_dataset
  • search_index
  • search_keywords_log
  • search_node_links
  • search_total
  • sessions

Comments

ronan’s picture

ronan CreditAttribution: ronan commented
Status: Active » Closed (won't fix)

I don't want to complicate the out of the box experience more than I have already and since this can already be done with the module if desired I'm going to mark this 'won't fix'