I am working on a project that is a migration from Drupal 6 to Drupal 8. We ran a backup of an environment that had run the migration and when we restored it on a different environment local -> remote dev, the users had not been restored.

Backup and Restoration were done with the UI.

Comments

frob created an issue. See original summary.

couturier’s picture

Status: Active » Closed (outdated)

Are you saying that none of your users were migrated from D6 to D8? Or that they were migrated to D8 the first time and that when you then ran a backup using D8 that you were unable to restore correctly? I'm sure there is a way to pull this database information and import it manually if needed.

Also, we would need to know which dev version of Backup and Migrate you were using. I'm not seeing a version of Backup and Migrate available for D6. With the module branches currently available, you would need to do a backup from a D7 site and migrate to D8 at the very least. Also be aware that there are a lot of bug fixes about to be pushed to a new, stable D8 release. Please be looking for the new release and try again to see if this resolves your problem.

frob’s picture

Status: Closed (outdated) » Active

I don't use this project for migration. I use the drupal 8 migration api for migration. I have a migration that worked from D6 to D8 (using the drupal 8 migration api), however after I ran migrate, when I used backup_migration on the D8 site to backup everything and move it to my local install, none of the users where on my local instance.

Alex Andrascu’s picture

Umm, can you remember what settings have you used while taking the backup ? For example the Zip compression currently doesn't work at all. A little more info would be really useful.

Alex Andrascu’s picture

Status: Active » Postponed (maintainer needs more info)
frob’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I posted this for a colleague. I don't know if it is still an issue for him.

I did walk through the steps with him and it was almost as though the queries weren't being run on his db.