Hot answers tagged

20

I got this error when trying to do Restore-SPSite on a SharePoint Farm that did not match the schema version of the backed-up Site Collection. After installing the correct CU to my target environment the Restore-SPSite worked without issues. Found this in the ULS log to pinpoint the issue : Microsoft.SharePoint.SPException: Schema version of backup ...


12

I've had this discussion with Microsoft Support in June 2014. They told me that backups are performed on all site collections on a daily basis and kept for 14 days. In order to get a restore to happen you need to add a service request from your Office 365 tennant admin center (support link in the left navigation). Unfortunately they can only restore on site ...


8

Just look at the code snippet below and try to imagine the scenario of what will happen: using(SPSite site = new SPSite("http://somesite")) { using (SPWeb web = site.OpenWeb(SameGuid)) { return web.Url; } } The above code can raise an exception because two web objects would be returned, there are infinite scenarios where GUID is used to ...


7

There are a couple of things you can try... such as 1. Get-SPDeletedSite & Remove-SPDeletedSite You may already have restored this site before. In that process you also deleted the site first (automatically), which you can find running the command... >Get-SPDeletedSite You'll see the site (or sites) listed, like this: WebApplicationId : ...


7

Backup-SPFarm not only backs up the databases, but also exports configuration settings from the Config database (which cannot be restored). This would include things like Web Application objects. In addition, it backs up various Search settings. That said, most companies I deal with go just for database backups (sans Config, Admin, Usage). It's usually ...


6

I recently ran into the exact same issue in SP 2013 where my Dev machine had the RTM install and the target server the June CU. We ended up copying the Content Database from SQL directly, reattaching and associating it to a Web Application and it worked flawlessly. It seems the Restore command is no longer backwards compatible and can't be relied to restore ...


6

Granular restore operations require the use of Powershell as no UI in Central Administrator exists. This cmdlet is used to restore sites, list, and libraries exported with “export site or list” option in central administrator or using export-spweb cmdlet. For Example: import-spweb -identity http://contosoweb/ -path \\appserver\bu\list.cmp Note: You can’...


6

The use of $site = Get-SPSite "http://sharepoint" $site.usage.Storage only includes SPSite.UsageInfo's Storage. The UsageInfo-class also includes DiscussionStorage-field which might differ from 0, i.e. its size is also added to the backup. What's even more likely is that the size of the backup grows because of Audit logs. Audit logs increase the site ...


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()


6

we have site collection backup, which is created with Backup-SPSite cmdlet: Backup-SPSite http://example1.com -Path C:\Backup\example1.bak We copied it on local environment and want to restore it with Restore-SPSite http://example2.com -Path C:\Backup\example1.bak –Confirm:$false (Here I intentionally used different urls for source and target sites in ...


6

Yes it's correct, you can't restore a content database to another web application on the same farm because the Content Database GUID is already existing. So to overcome this issue, you have to do the following: Create your new web application Create the root site collection. Backup and restore the site collections from source content database to new one ...


5

Check in the Event Viewer if there are SQL permission error. Open Event Viewer (click start and search it) Expand Windows Logs and than click Application (in the left side) Check if there are critical error like this with the following details SQL Database DATABASE_NAME on SQL Server instance SQL_INSTANCE not found. Additional error information from SQL ...


5

I found an answer, just for site collection created on web application root. Use this command to backup a site collection Backup-SPSite -Identity "http(s)://your-site-collection-url" -Path "C:\backups\your-site-collection-backup.bak" It's important to use an absolute path as -Path parameter. Then create a new web application and then run the following ...


5

I can't see that you have run the SharePointBAC.ps1 in your script, which is downloaded from the Codeplex page SharePoint Backup Augmentation Cmdlets. The scripts Get-SPBackupCatalog Set-SPBackupCatalog Remove-SPBackupCatalog Export-SPBackupCatalog is not out-of-the-box native cmdlets in SharePoint Management Shell or PowerShell ISE with the reference of ...


5

If it is a SQL backup (content database), you can create a new web app -> site coll and then attach the database. Refer: https://technet.microsoft.com/en-us/library/ff628582(v=office.14).aspx


5

Go the central admin > Monitoring > Check Job status on this page look for the backup job(Site Collection Backup ). If it is still running, stop/ delete it. Another way is on the server go to service console and stop the SharePoint Timer Service and start it.


5

There are a couple of useful articles that spell out the reasons not to use snapshots for SharePoint in production, and things you MUST do if you actually go ahead to do so: Best practices for virtualization (SharePoint Server 2010) - I know that this says SharePoint 2010, but what it says about snapshots applies to 2013 as well. Virtual Machine Snapshots ...


5

Backup-SPFarm does a few things: Backups all applicable databases. This also updates the Last Database Backup entry Exports information from the configuration database (which cannot be restored) Backups the search index This is why you see smaller files along side your database backups.


4

I ran into this error when restoring a site collection from another farm that was an older CU/patch version. An optional work around if you don't want to upgrade the other farm: Create a test web application in the newer farm From SQL, restore the original db with the site collection you plan to restore. Upgrade-SPContentDatabase -ID <id guid> Backup-...


4

You may already have restored this site before. In that process you also delete the site first, which you can find running the command... >Get-SPDeletedSite You'll see the site (or sites) listed, like this: WebApplicationId : 009c1289-392b-43a6-8222-146117074738 DatabaseId : 88efc46f-5a2b-4171-81cb-7577da65bac3 SiteSubscriptionId : 00000000-...


4

Yes, You can move it. But one thing you keep in mind if you hard coded the URL in your sites then those will cause the issue and you have to manually adjust it. Couple of options to move it. 1) Moving using the PowerShell tool. Move-Spsite Move-SPSite http://servername.com/sites/sitename -DestinationDatabase ContentDb2 Only catch in this case, you have ...


4

The Backup-SPFarm command should use a network share where The service accounts, Farm accounts and SQL Server service accounts have Full Control access to the share. This is because SharePoint uses SQL commands for running parts of the backup and these execute in SQL Server's context. More information: Prepare to back up and restore farms in SharePoint ...


4

Two easy options i am thinking about. Method # 1 Make the changes on the AAM and Update the IIS bindings. Yo may need to IIS reset at then end. Method # 2 Detach the Content Database from web App A & web App B Now attach Content DB from Web app A to Web App B & From web B to Web App A.


4

PowerShell for SharePoint Online has really limited capabilities at the moment. There is no one liner to automate this task. But you can use CSOM inside your scripts. [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SharePoint.Client') | Out-Null $login = 'test@test.onmicrosoft.com' $password = ConvertTo-SecureString 'password' -AsPlainText -...


4

This is a common pitfall and a good reason to look into your backup routines, especially before patching as there is no way to uninstall a patch. Sadly, the only easy way would be if you have a test/staging farm where you have the same patch level as the site collection were at during the backup, restore it there and then move it to a separate content ...


4

There is no powershell command available for backup and restore in SharePoint Online(office 365). For backup, you have to rely either to MSFT as they keep the backup for 14 days or you have to use the 3rd party tools to take the backup of your online sites. https://threewill.com/the-4-options-you-need-to-know-about-sharepoint-online-backup-and-restore/ ...


4

Follow these steps: Decide on a name for the list, it will be the URL and name of the list. Go to the ‘cog’/Settings and select Add an app You will now see a list of all available apps (installed) Search for Import or scroll down until you find the app called Import Spreadsheet Click on Import Spreadsheet Type in the Name of the new list Type in a optional ...


4

It is really tough to agree on single point as backup & restore requirement vay customer to customer. But their are many options to choose from, you can pick one which is really suitable and fullfill all your requirement. There are 3 common method SharePoint Backup SQl backups 3rd Party Tools ( MicroSoft System Center DPM) All method having their prons ...


4

2 things I can think off hand: Tell users to start purging content that is no longer necessary. Use Move-SPSite to move some site collections to a new content database. Based on your comment and making some assumptions, it isn't going to be that easy. You'll need to fracture off some of your subsites and make them their own site collections and then you ...


4

One of the main features of SharePoint online vs on-prem is decreasing the overhead of operations tasks like backup-restore plans and patching ...etc. Meanwhile, if you need to take a backup, you can achieve that via the below options: Using 3rd party tools that can back up your Data like AvePoint. Open a service request with Microsoft to request a site ...


Only top voted, non community-wiki answers of a minimum length are eligible