3

I am working on a Team site collection inside SharePoint enterprise server 2013. and the publishing infrastructure site collection and site features are enable. now i want to move the site collection from being on the root to be under a new managed path.

The site collection i want to move have the following properties:-

  1. It is defined on the root http://servername/

  2. It have one direct sub-site http://servername/Dept/

  3. the above sub-site have another sub-site http://servername/Dept/DeptA

now i want to move the site collection to be under different url which is http://servername/Area/<current site collection>... where "Area" will be a Explicit managed path.

so i am planning to do the following to move the site collection from being on the root to its new URL.

  1. back up the current site collection using BackUp-SPSite

    Backup-SPSite http://servername/ -Path C:\Backup\A.bak

  2. remove the current site collection permanently

  3. create the new managed path named "Area"

  4. Restore the site collection on the new url

    Restore-SPSite http://servername/Area/A -Path C:\Backup\A.bak

so are the above 4 steps valid ? and could i result in having duplicate GUIDs?

6

Above scenario should work, as you are deleting the existing site collection then you will not see the Duplicate GUID problem.

You may need to refresh the config db, in order to update the record ( very less chances)

$db = Get-SPDatabase | where {$_.Name -eq "DatabaseName"}
$db.RefreshSitesInConfigurationDatabase()
  • not sure about the RefreshSitesInConfigurationDatabase what will it do exactly? second question if you were in my place which approach you will follow, will you consider the same appraoch as mine ? – john Gu Nov 28 '16 at 16:37
  • 1
    if i am your situation, yes i will. I did this before and it worked well. Refresh update the Config database with new information, like you are creating the site on managed path...it will update it and also remove the deleted site from his list. – Waqas Sarwar MVP Nov 28 '16 at 16:39
  • so if i follow this approach should i be safe against any GUID conflicts for new site collections? – john Gu Nov 28 '16 at 16:40
  • 1
    Should be safe, Again as good SharePoint admin always test the scenario in lower environment. – Waqas Sarwar MVP Nov 28 '16 at 16:41
  • 1
    its upto you, if you want you can create in advance then use the -force parameter in your command otherwise it will create one – Waqas Sarwar MVP Nov 28 '16 at 17:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.