After building a protoype Sharepoint site for the client I am now looking to export it for the client's eyes.
I'm looking for the best solution for exporting, sharing or moving a Sharepoint 2013 site for the client to see on their server. The site is currently only on one server so no server farms are involved.
The site is built using Sharepoint 2013.
I've been running through this guide, but could anyopne clarify if this process creates a back-up of the entire site or just the database: http://technet.microsoft.com/en-us/library/ee428301(v=office.15).aspx
Any help would be greatly appreciated - Thanks!
There is a great video on how to do a backup and restore in SP10.
This does work for SP13 except the backup needs to be done with PowerShell.
How Do I: Backup and Restore a SharePoint 2010 Site Collection?
The backup and restore is not guaranteed to give you the exact result as some features could be activated and some CSS could change the look of the imported site.
Related
We have planned to migrate our SharePoint server 2010 to SharePoint Online (Office 365). Before we migrate our production site, we have tried to create a test environment in SharePoint server 2010 using the backup data of our production sites. We have tried the below steps to create a Staging environment as like our Production environment. Can anyone suggest the steps for migration or the steps we have followed is good.
Steps :
I have backup the content database.
Created a new web application and restored the backup database to this web application.
As the site is not loading and hence we created a new site
collection.
Once the new site collection is created, the site is able to load but the site and content of production site is not restored as like in our testing site.
Will restoring the database is enough to restore the site collection in the application in SharePoint or need to restore the site separately to the web application. Any suggested solution will be grateful for me to proceed.
Thank you and Best Regards,
Ragunaathan M P
If you are creating a test environment to use for SharePoint online your best bet is to use the 2016 bits. When you move your content over you need to do make sure you have upgraded the content.
So you would do some flavor of the following:
1) Backup the existing database
2) Restore the DB to the new farm
3) Mount the DB (Mount-SPContentDatabase xxx)
At this point (this is very overly simplified you should be able to render the sites.
Lots of other factors will be involved (InfoPath, Full Trust Code, Workflows, etc). However if your content is pretty vanilla this is what I would do. Dp not use the nob2bsiteupgrade option on mount or you will have an upgraded database schema, but your sites won't work.
To validate your upgrade check the logs and look at the versions table in the database. You should see a 16.x.x.x version. The other numbers are the upgrader actions and won't tell you much.
Here are some references:
Upgrade Content
Upgrade-SPContentDatabase
Mount-SPContentDatabase
Our company has a SharePoint server where we have to store all of our documents, our TFS 2013 has links to this SharePoint server. We have been told that the company is getting a new SharePoint server which will have a different url
This means that all links within our TFS need to be repointed to the new SharePoint site
Does anyone know of a way to change the links without someone having to go in to each PBI; see if it has any links; if it does then remove the old link and add a new one?
We have 100's of documents and would rather not have to do this manually so any help will be much appreciated
This is all beyond my control, all I've been told is they are migrating our SharePoint site to another server...
You can write a PowerShell script that will open all PBIs and change the links to the new SharePoint. In order to get access to TFS from PowerShell scripts you have to install Team Foundation Server 2013 Power Tools and check the PowerShell Cmdlets option during installation.
I was unable to work out how to do this using the PowerShell Cmdlets but I have been able to write a program to do this using Team Foundation Work Item Tracking Client
I have looped through each of the work items and their external links, if the link is to our old SharePoint site then:
I remove the old link
Add a new link with location of the same document on the new SharePoint
I have restored a content database to SharePoint 2010 (which we completely broke after upgrading TFS to 2013).
When I open the content site, all the sub-sites are listed, but clicking one of these "sub-sites" goes to page not found. (The sub sites were created from TFS 2012 when new team projects were created).
How do I get the team project sites to work again?
You likley do not have a managed path configured for your SharePoint sites. If you look at the URL of the sites that you can't see you should be able to figure out the managed paths to add.
http://technet.microsoft.com/en-us/library/cc261845(v=office.15).aspx
You are kinda defining mount points for site collections here. Without that mount point SharePoint will not render your sites.
I have taken a back up of sharepoint 2010 site using central admin & have .cmp file.
Now I would like to restore the site in a sharepint 2013 site.
ie, I want to import this site to a 2013 subsite.
Is it possible to restore 2010 site back up to 2013 site?
Please share your thoughts.
Regards
Vishnu
please lookup this link as the answer is pointing out, it doesn't work that way. Try to use Move-SPSite to move your site into a seperate database. That way you could upgrade that database to SP2013.
If you're talking about an SPWeb there seems to be an other solution described here.
I'm looking for a way to duplicate the content of a SharePoint 2010 server in order to work against it without taxing the main (production) server. I would need the backup server to update as needed, but I'm not looking for a failover solution. It looks like 2010 includes replication features for failover, but I can't tell if this is appropriate for my solution as well (simply not configuring the switchover feature). Can someone with SP 2010 experience tell me if this feature would work for my needs?
You could attach a restored backup of your production content database. See this MSDN documentation for more info: Attach or detach content databases (Sharepoint Server 2010).
There is also a GUI tool http://sushi.codeplex.com/ which should help you. You could backup production and restore to dev site whenever you needed to.
You could also use either stsadm.exe and the backup/restore option OR the powershell cmd backup/restore.
In addition, there is a built in interface in Central Admin to backup/restore sites. I've generally found either the command line or the SUSHI tool to be quicker and easier.
In most cases, the taxing work is on the sharepoint side, not the SQL side. You could attach another front end to the farm but reserve it for only your traffic. Otherwise you're looking at some form of backup/restore to copy everything to a 2nd duplicate farm.