mysql view isn't standard for Drupal

In what way is the backup failing?

I haven't tried this module yet (but it really looks interesting so thanks for drawing my attention to it).

My first reaction would be that since views do not contain any data them self, they do not need to be backed up as such - they would need to be recreated after the backup is completed though.

I think this is an issue that should be handled by the backup_migrate module though. When I get the time to do it, I will look into making a path for it.

I have made a patch for backup_migrate that solves this problem. I hope they accept and apply it, other than that I can't do much I am afraid.

The patch is included in the issue mentioned above.

By the way - if you exclude the views (the ones named '[something]_vw'), using the selection box of the backup_migrate user interface, then your db restore will not fail - but your views will not be created either.

There might be an underlying issue with backup and migrate, but i can confirm that using phpmyadmin also causes the same issue. When uc_views is enabled you can not export and import the .sql file. After disabling, and uninstall the export/import worked fine.

My knowledge of the how/why is limited, I just wanted to pass on that even phpmyadmin export/import will not work.

Subscribing. I'll follow up with more details