Best practices for copying data (only) back from production site to testing site after exporting views as features to prod? After building/testing a Drupal 7 site, I deployed it to prod server, exporting all views as features. Now the views are all 'in database' on test site, but 'in code' on live site - on the theory that no views editing should be done in prod. Now if I want to copy my prod database (but not code) back to my testing site for a new phase of development, what's the best way to avoid overwriting (or wiping out) views 'in database' on my dev site? 


Should I have renamed the views when creating features?
do I export/import the views, either from/to testing or from prod to testing?
is there some other way to selectively preserve views in the testing db when copying back an sqldump?


Thanks much!
We have the following:


DEV code base. (dev-code)
DEV database. (dev-db)
PROD code base. (prod-code)
PROD database. (prod-db)


Here is a simple dev flow to change a view, deploy to prod and then continue development:


[dev-db] Create a new view or modify an existing view.
[dev-code] Create a feature module out of that view or re-create an existing one.
[dev-db] Enable the feature module on DEV.
[prod-code] Commit the change and push it to PROD or upload the changes to PROD.
[prod-db] Enable or Revert the feature on PROD.
[prod-db] Export database from PROD (and preferably sanitize it to remove sensitive data)
[dev-db] Import the database dump to DEV.
[dev-code] Continue development!


You shouldn't have any problem if you are following this flow.