Hot answers tagged

10

This is a known issue[citation needed] and unfortunately restoring to a new content database is the only workaround (I refuse to call it a solution since you now have a new problem). Once restored, you can't move the site back either; the error it returns is about how the site used to exist in the content database. If you can, avoid deleting site ...


9

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


8

I just randomly came across this post and although its old I wanted to give the solution since I recently ran into this issue. To "reinstall" the built-in fields (and this should fix the field issues in the ctypes) just run the following command for each of your affected site collections: stsadm -o deactivatefeature -name Fields -url http://sitecoll -force ...


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

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


5

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


5

there are couple of ways. Run the Test-spcontentDatabase command against the content DB to get the list use this SharePoint Feature Administration and Clean Up Tool to identify and remove them You can use the powershell to get this done. http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html


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

When you delete a Site Collection, it will still remain in the Content database until the "Gradual Site Delete" Timer job is run (by default, it runs once daily). So, once you delete the site collection and run the timer job, then you can again restore the same site collection in the same content database.


4

You cannot restore a content database to a prior version (major or minor). You also cannot restore a site collection. This is by design, and any attempt to change that can lead to instability and you will not be supported by MS. You will need to upgrade the destination system to the same version; SP1 and any CUs if installed. If the patch failed to ...


4

Your CSS file wouldn't be in the config db anyway, all site content (when unghosted, ie: saved through the browser or SharePoint Designer) is stored in the content database. I would check out the file, and restore each version until you get what you think is the most recent version. Do this through the UI, as SharePoint Designer is laggy when referencing a ...


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


4

I think you will need to have some algorithm for it. Below is one which may help: Maintain the deleted sites Url and GUID in a list.You can do it using SPWebEventReceiver.WebDeleted.Also,Before it gets deleted, modify its home page to a new html like page that says "Under Construction". Create a job and monitor the list for deleted site restoration. To do ...


4

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


4

Saumil, that is not possible. What you coud do: * restore the content database to another sitecollection * synchronize the permissions between the two sitecollections with some custom written powershell. I don't think there's an easier way.


4

Nope, it won't work that way. You should do a backup and restore in your SP 2010 environment and put the site collection into it's own database. Then do a sql backup and restore of the database into the 2013 farm and content db attach it for it to upgrade correctly.


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


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

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


3

things are as simple as you mentioned in your question. Here are the steps. You have to perform the SQL backup of the Content Database from Source Farm Move the back file to destination server(sql) Restore the Database on destination SQL Server now you have two options over here if you overwrite the destination dB while restoring, then no need to attach ...


3

there are couple of options you can try to remove the orphan in the databases. Did you try to run the restore with force parameter? Detach the content DB wait for couple of min and re attach it try to repair the Content DB if you have site id (returning while running get-spsite) then you can forcefully delete it from SharePoint via powershell or stsadm ...


3

Is it the front/app servers we are concerned about, or is it the SQL? You could create a farm where all roles (web app, application, crawl, index) are distributed to at least 2 servers (and where SQL is mirrored on two servers). I'm not sure about "within seconds", but if you configure mirroring correctly the SharePoint databases will know of the ...


3

Couple of things to check: Make Sure Farm admin accounts having the write permission on the path. try to use different path Make sure the site is not locked check the ULS / Application Logs for clue. Also try to take the backup from powershell to isolate the issue. Backup-SPSite -Identity <SiteCollectionGUIDorURL> -Path <BackupFile> Some IIS ...


3

You try to restore a site collection backup to the same content database from which the site backup was taken , there will be a GUID conflict. GUID for a site collection is unique and it gets stored along with the site collection backup.


3

Check if you're having sufficient permissions in SQL server to perform restore Double check the managed-path try restoring to different paths like http://servername.com/sites/yousitecollection Ensure all the customizations (WSPs) are deployed to destination (if any). Check ULS logs for additional pointers


3

Making a backup of the site collection is best used when you need to restore it on the same environment It's nearly like a content database backup. Exporting a site collection will allow you to import it on a different environment. It's working in a similar fashion than content deployment jobs. It will include in an environment agnostic way all the assets ...


3

There are (at least) two ways to get the content of an old version of a file, both go through the SPFileVersion from item.File.Versions. If you want to use the content in your code, then you can call SPFileVersion.OpenBinary (or OpenBinaryStream) If you want to allow the user to download the content then you can provide a link based on SPFileVersion.Url ...


3

Hi I had the very same issue after restoring. The accepted solution by user879 to this question seems to help: I can't login to SharePoint 2010, what's wrong? (answer here). You can give it a try, but be aware that disabling the loopback could pose a threat as per the article posted by James in the comment - disable loopback check & sharepoint


3

The farm you received the database from is most likely at a different patch level than the farm you are trying to mount it to. Get the systems to the same patch level and then try mounting the database again. Also, you will most likely want to remove the root site collection from your development environment because if you are trying to restore a root site ...


3

Open SharePoint 2010 Management Shell and run the following PowerShell: $docSize = 50000000 $webservice = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $webservice.MaxTemplateDocumentSize = $docSize $webservice.Update() Accroding to MSDN, it should be between 0-500MB, but you can go beyond 500MB AFAIK.



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