The Stack Overflow podcast is back! Listen to an interview with our new CEO.

Hot answers tagged

19

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 ...


16

There are lots of point to discuss before coming to a conclusion here. But I will just explain the different possible ways you could do backup in SharePoint in an order of good to best. Central Admin Backup - This is a default UI option that comes within Central Administration. It allows to take full and differential backups. You have the additional ...


13

I'm glad you included an image of the operation in progress, because it makes it easier to clear up some confusion and answer your question. I think previous respondents missed the fact that you're actually working in SharePoint Designer 2007 -- not Central Administration or the command line. First, let me clear up some confusion: the operation you're ...


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 ...


10

As of now, there is no out of the box facility to backup an entire SharePoint site and restore it to another farm as you do for on premise SharePoint applications. The only option currently available would be to use the "Save site as template" option for sites, which would take a backup of max 50 MB. Visit this blog for more details. You can check out for ...


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

To back up a site collection, you must use the following stsadm command. stsadm –o backup –url <URL of the site collection> -filename <Name of the backup file> To restore a site collection, you must use the following Stsadm command. stsadm –o restore –url <URL of the site collection> -filename <Name of the backup file> -overwrite ...


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 don't think it was intentional, but this is actually something of a trick question. Let me explain. There are basically two different types of backups that you can perform: farm-level (catastrophic) backups and site collection backups. The former is used to back up components such as the entire farm, a Web application, a content database, etc. The latter,...


6

The biggest determining factor here between SharePoint Backups and SQL Server backups is going to be how much content you have in your farm. Based on what I could find on TechNet, SharePoint backups are not supported for content databases over 200 GB in size (http://technet.microsoft.com/en-us/library/cc262787.aspx) and site collections over 100 GB in size (...


6

You would only need to backup your 14 folder if you made added files or changed files in the 14 folder manually (meaning not through a deployed package). I would, however, make a backup of your web.config files if you have any custom connection strings, app settings, or service bindings.


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

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

You can use PowerShell to do that, check Restore-SPSite cmdlet. Restore-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak


5

You can also do Implicit Remoting, which allows you to import all of the SP10 Powershell commands into a local session. The method described above works as well, but you are essentially running the commands from the server, so if you are on a server with different modules (such as Exchange 2010) you will have a difficuly time running those on the SharePoint ...


5

There is just a subtle difference: Workflows are included when you use the Backup-SPSite cmdlet. If you backup a root web of a site collection the site collection recycle bin will obviously not be included.


5

Backup-SPSite is generally used when you want to replicate the entire site collection (including all subsites) to an existing web application. Export-SPWeb is generally used when you want to replicate just a single subsite to an existing site collection. Also below links are worth to read for other major differences: http://blogs.msdn.com/b/yvan_duhamel/...


5

For Powershell, try skipping the quotes around the site URL: Backup-SPSite http://something1:6060/ -Path "C:\site.bak" The same goes for stsadm


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

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’...


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

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

The regular SharePoint backups will grab content, and configuration (when doing the farm backup). This does not backup any changes made to the SharePoint files on the server(s) such as images, templates, etc. Any customizations or third party tools that were deployed; note all should be deployed via a WSP. Some manual web.config changes may not be saved ...


4

As you need to move your SQL servers, this can and will be treated as a simple SQL server move, which requires a farm migration. This is because the domain name of the SQL server changes. For farm migration, you can find instructions at http://technet2.microsoft.com/Office/en-us/library/42511e01-ecdd-4dc5-b06f-35aaada8a5d81033.mspx?mfr=true. Make sure you ...


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