Tag Info

Hot answers tagged

8

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


6

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


5

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


5

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


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


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

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


3

In your example you are backing up the root site collection of machine1 and restoring it under a managed path on machine2. You may want to make those consistent. Emad is correct about step #2, as long as the application is setup on the server you will not need to create a content db. One last tip, make sure that you have any customizations or solutions ...


3

The way I would do this is to move the site collection into its own content database. Then copy that database and attach it to the new farm. In Central Admin add a new content database to the web application Use the Move-SPSite CMDLET in PowerShell to move the site collection to the new content database Make a SQL backup of the content database Restore ...


3

Backup-SPSite will move all your data and rights and create corresponding records in the content DB. Import-Export is not so good way for you, you can use it only for web, not for site collection, but it also will move all your data and security, if you will set corresponding flags, it has a lot of options. Previous approach is also possible, you can attach ...


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

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.


3

Using the SharePoint PowerShell console Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <WebApplicationName> [-Verbose] See this MSDN article: Use Windows PowerShell to back up a Web application in SharePoint Server. Use this command to restore a content DB: Restore-SPFarm -Directory <Backup folder ...


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

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


2

I think this was fixed in SP2, but in SP1 I noticed that when I restored a site, if I didn't have the url correct, it would think i'm talking about the root site instead of the one I was referring to. so stsadm -o restore -url http://machinename/sites/siteabc -filename c:\backup\siteabc.bak would work, but stsadm -o restore -url ...


2

I eventually figure this out. The reason I was getting the error message above was I had only enabled MMS service application. (trying to be too memory thrifty). Not sure which service did the trick because I enabled all of them (default). The "Manage Publishing for this Content Type" screen didn't through an error now, ...well not until I click Publish. I ...


2

A couple of things here: Using backup/restore to move a site between environments is only supported under specific circumstances. For publishing sites, you need SP2 and the April 2009 Cumulative Update or later (not sure without checking version numbers if you have this). Stefan discusses this for publishing sites here, but I'm not sure how this applies to ...


2

Are you able to take a backup of the content database that holds the site collection? If you do so you can then restore the SQL Content DB to your dev sql instance and attach it to a development web application, the attach will perform an 'upgrade' on the content db and should take care of your issue.


2

Don't be fooled by the "have sufficient free space" message...I think that's just part of a higher level generic error message. I had this same exact error about a month ago and the only way I was able to get around it was going into Central Admin, create a new content database on the web app, and then use the databasename argument on the Restore-SPSite ...


2

I would remove the contentdb from SharePoint. And then add the contentdb back using stsadm. I think that might perform the upgrade needed. http://technet.microsoft.com/en-us/library/cc263422(office.12).aspx


2

This sounds like some patches (probably Service Pack 1) have been applied to the servers since the backup was made. However, you may want to open up a dev or test machine and only build to the version prior to whatever patch was made, then restore from that location to find your file and put it back into the correct location on the server.


2

Instead of using the unattached contentdb method (which is used only for when the version of the db is the same version of SP that is installed), you will need to use powershell or stsadm to upgrade your database. See here: http://technet.microsoft.com/en-us/library/cc263299.aspx I would use this command in powershell if it were me: ...


2

You can configure Schedule Task, which is feature in Windows Server 2008 and then execute this PowerShell code: http://gallery.technet.microsoft.com/scriptcenter/9b99c435-8831-4c9e-a70b-1f13158ef22a Or http://social.technet.microsoft.com/wiki/contents/articles/how-to-sql-server-databases-backup-with-powershell.aspx You must document your Disaster Recovery ...


2

Creating a DR plan for SharePoint depends a lot on the business needs. I would first start off with defining what my RPO and RTO are. Based on that, next is to design it. A very basic plan that many follow is SQL Mirroring with Log Shipping. To optimise the performance, the backups can be performed from the mirrored sql server. Dpending on your business ...



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