I have read these links which talks about using
and they both mentioned that restoring a copy of a site collection's back-up file file using
Restore-SPSite will mainly create a new GUID for the site but will reserve the GUID for the site collection's components such as its subsite, content type, etc... so they mentioned that we should do the
Restore-SPSite on a new Content Database to avoid GUID conflict..
so I did the following test:-
- I have the following site collection "
- I backup it.
- then I restore a new site collection (
http://..../testsite) using the backup file inside the same content database (Actually I only have one content database).
- and I did not get any exception,, or any error message about any GUID conflict..
so now I have 2 site collections (
/testsite), that have the same GUIDs for their; subsites, content types, etc... but I am able to work on these 2 site collections without having any problem.
So can anyone adivce why all the links which talk about
Restore-SPSite mentioned that we need to restore on a different content database to avoid duplicate or conflict in GUIDs ??? In other words where I will face problems if I have for example 2 subsites that have the same GUIDs ,and their site collections are inside the same content database??
Here is a screenshot of the scripts which I perform:-