I have a site that needed maintenance that took longer than expected. None of the tables changed from Live version to test version, except I had several new users sign up.

I just want to backup the user table and import it, and then do full backup to port back to live site.

Is this as simple as selecting only the user table in advanced backup? Or would this replace my entire database with just the user table?

Thanks!

Comments

AjitS’s picture

I too have such requirement. Did you find the solution to this? I'll really appreciate if you share it here.

ronan’s picture

Status: Active » Closed (works as designed)

This will override the entire table. Also there may be other tables that are needed for each user (profile fields, etc.). That's why B&M is not suited for slicing and dicing your data in this way. It's designed to do snapshot backups.

Gastonia’s picture

Status: Closed (works as designed) » Needs work

I appreciate the response, but really I would like more detail in the answer.

The reason being is that there is explicitly an 'Advanced backup options' link that takes you to a specific area where tables can be included and excluded.

Why would this option be here if all this module was suited for was a quick 'snapshop' of the database at the moment?

After waiting almost a year for an answer, I still need the ability to migrate my users' accounts irrespective of content.

If this is not possible with this module, then perhaps we can change this to a feature request, or start a new thread as a feature request, to have this section removed from the module, as to have complex functionality that is of no use anyway is needlessly confusing.

It would just be nice to see that if this Advanced area really can help people with more advanced needs that there be support in place, examples, etc.., which, is what I was thinking to begin with when I asked.

ronan’s picture

Status: Needs work » Closed (won't fix)

The exclude table features are there because not all db data needs to be backed up (cache tables, search index, etc) and not all tables in a db are necessarily drupal tables (you might have wordpress installed in the same db and not want to back up those tables). You'll notice that there is no option to backup just part of a table. There is no way to backup all users with uid > x for example.

That's because cutting up a db like that is complicated and requires a deep knowledge of the table structures and relationships of not only Drupal, but also of every contributed module you have installed. Users are stored across multiple tables.

I will not be adding the abilities you are describing to the module because there is no way for me to support that functionality for every possible drupal set up. If you want to chop up your db, why not use phpMyAdmin or the command line mysql command? Those are much more flexible and general purpose db tools.

Thanks
Ronan