Showing posts with label Backup&Restore. Show all posts
Showing posts with label Backup&Restore. Show all posts

Tuesday, July 7, 2015

Farm configuration Restores in Sharepoint 2013.



Farm configuration Restores in Sharepoint 2013.

You can use Windows Power Shell to restore a farm’s configuration.

To restore a farm's configuration by using Windows Power Shell 

1.    Verify that you have the following memberships:
o    securityadmin fixed server role on the SQL Server instance.
o    db_owner fixed database role on all databases that are to be updated.
o    Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

2.    On the Start menu, click All Programs .
3.    Click Microsoft SharePoint 2013 Products.
4.    Click SharePoint 2013 Management Shell.
5.    At the Windows Power Shell command prompt, type the following command:
Restore-SPFarm -Directory <RestoreShare> -RestoreMethod Overwrite -ConfigurationOnly

<RestoreShare> is network location where the backup file is stored
 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Monday, November 3, 2014

Your backup is from a different version of Microsoft SharePoint" - Error while restoring the site



Your backup is from a different version of Microsoft SharePoint" - Error while restoring the site

Error: Restore-SPSite: Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '4.2.7.0' or later.

Resolution: First check the patch level of  your source and destination environment. Make sure your destination environment is not at lower version than the source. If so , you may need to patch your environment as same as your source.

Steps to Check Database Schema Versions :

Central Administration application Management à Manage content databases Select your database where you want to restore click on the DB name à  under “Database Versioning and Upgrade” you can see something like below

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 4.1.30.0, Maximum Schema Version: 4.2.7.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 4.1.7.0, Maximum Schema Version: 4.1.7.0
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: 14.0.6137.5002, Maximum Schema Version: 14.0.7105.5000

If the Current Schema Version is less than the Maximum Schema Version, then the database should be upgraded as soon as possible.

To Upgrade content database, Execute the below command in powershell.

Upgrade-SPContentDatabase <Content_db_name>”

After executing the command,

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 4.2.7.0, Maximum Schema Version: 4.2.7.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 4.1.7.0, Maximum Schema Version: 4.1.7.0
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: 14.0.7105.5000, Maximum Schema Version: 14.0.7105.5000

Now the database is upgrade to the version 4.2.7.0 and you can restore without any issues.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Monday, October 20, 2014

Is possible to attach the same Content DB in two sites in Same farm



Is possible to attach the same Content DB in two sites in Same farm.

Issue: I am getting many questions from the SharePoint community that” Is possible to attach the same Content DB in two sites in Same farm”

Solution: I say answer as Yes and No.

1)   We can attach but, The expected behavior as the Site Collections have the same GUID, so the second website which has same content attached  will not be able to see all data of them. In this case we can consider the below steps to overcome this.
2)   Restore the Content Database to a Web Application on another farm
3)   Use Backup-SPSite/Restore-SPSite which assigns a new GUID to the Site Collection so you can 'duplicate' it within the same farm
4)   Use Export-SPWeb/Import-SPWeb

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.
Related Posts Plugin for WordPress, Blogger...

ShareThis

X