Here is my scenario:
My current dev sharepoint 2013 environment is using a former backup of Production (which is 2010). We need to restore the latest backup from production into the dev environment. I restored the production backup to a new database under a different name. When I use "Mount-spContentDatabase" and point towards the latest production backup under a new name it gives me the error:
"
Mount-SPContentDatabase : The attach operation cannot continue because another
object in this farm already contains the same ID. Each object in a farm must
have a unique ID. In order to proceed with the attach operation you must
assign a new ID to this database. To attach this database with a new ID, use
the Mount-SPContentDatabase command with the -AssignNewDatabaseId parameter.
Note that if this new database and an existing database contain the same site
collections, attaching this database will likely result in orphaned site
collections due to conflicts between the two databases."
I realize mounting the same content db's in one farm leads to a duplication of database and site collection GUIDS in the sql database. I guess my question is what is the easiest way to restore a content db with the same site collections and ID.
Should I "disconnect" the current dev content db, take a backup of it, delete it from sql server, and then mount the newest production backup or will that still give me the same "orphaned" site issue?
Should I do the above, delete the web application, create a new one and then try to mount latest production backup?
If someone could give me specifics on how this can be accomplished short of installing on a new farm that would be much appreciated!