0

I try to migrate site collection from SharePoint 2010 to 2013. But I can't see my site in the new URL, I have a default SharePoint site.

PS C:\Users\svc-bpm-sysadmin> Test-SPSite -Identity http://dv55udb01/
Test-SPSite : SPSiteHealthChecker: The element 'Rule' cannot contain child
element 'RegexExclusionFilters' because the parent element's content model is
empty.
 SPSite="http://dv55udb01"
 ruleId=00000000-0000-0000-0000-000000000000
 repair=False
 CompatibilityLevel=15
 registrationFolderPath="C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\CONFIG\SiteHealthCheck"
 registrationFileName="sitehealthofficeserverrules.xml"
At line:1 char:1
+ Test-SPSite -Identity http://dv55udb01/
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...PCmdletTestSite:
   SPCmdletTestSite) [Test-SPSite], SPSiteHealthCheckerException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletTestSite

I am have same error when I try to Repair-SPSite.

Thanks for help.

  • can you elaborate on how you migrated the site? – Marek Sarad Sep 23 '19 at 10:48
  • hello, 1- create a new web application and new site collection in the new server 2- export the features (Add-SPSolution and Install-SPSolution ) 3- backup restore the wss_content database 4- Test-SPContentDatabase and Mount-SPContentDatabase – abdé mekni Sep 23 '19 at 15:13
0

I don't think you are using the right cmdlet for migrating the Site collection .

The First step would be to take a backup of your existing site collection using the PowerShell below-

Backup-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak

This will create a .bak file which is a backup of you site collection. Copy this file to a directory in the server where your SharePoint 2013 farm is present.

Now use the Power shell below to restore the .bak file to a new content database.

Restore-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak  

The only thing is that yoou must have a new content database created at the SP 2013 farm where you will restore the .bak file .

Simple !!

| improve this answer | |
  • 1
    Hello, im not in the same server the 2013 server is a new server – abdé mekni Sep 23 '19 at 15:17
  • code PS C:\Users\svc-bpm-sysadmin> Move-SPSite alcorg2-dev.finance.*.fr/ -DestinationDatabase WSS_Content_new_80 Move-SPSite : Cannot find an SPSite object with Id or Url: alcorg2-dev.finance.francetelecom.fr. At line:1 char:1 + Move-SPSite alcorg2-dev.finance.*.fr/ -Destination ... + CategoryInfo : InvalidData: (Microsoft.Share...PCmdletMoveSite: SPCmdletMoveSite) [Move-SPSite], SPCmdletPipeBindException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletMoveSite code – abdé mekni Sep 23 '19 at 15:21
  • Got it . Let me edit and change the answer . – Yash Kamdar Sep 23 '19 at 15:21
  • I hope you got what to do . Run the first powershell in the SP2010 environment . You will get a .bak file which is the backup of your site . Now create a content database (new and blank) in your SP2013 environment . Copy the .bak to the SP2013 server . Run the second powershell that picks up the .bak obtained earlier and restores it to the newly created content database. This way your site collection gets migrated. Let me know in case of any issues. – Yash Kamdar Sep 23 '19 at 15:28
  • thanks for your comment i have this error in restore: Restore-SPSite : <nativehr>0x80070003</nativehr><nativestack></nativestack> At line:1 char:1 + Restore-SPSite dv55udb01 -Path \\DVEDVK87.rouen.*... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (Microsoft.Share...dletRestoreSite: SPCmdletRestoreSite) [Restore-SPSite], DirectoryNotFoundException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletRestoreS ite – abdé mekni Sep 23 '19 at 15:42

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.