I'm trying to migrate content from one MOSS farm to another. Specifically a web application. The web application data is fully contained within a single content database. My process for doing this is as follows.
SQL backup content db from source sql server
Copy bak file over to destination sql server
Restore database from bak file on destination sql server - WSS_Content_DB
Create new web application on dest MOSS farm (http://newmoss:1234/)
Create root site collection
Via central admin remove the content database from new web app
Via stsadm add the content db (WSS_Content_DB) to http://newmoss:1234
As far as I can gather from online guides this process should work and result in the content from my source MOSS web app duplicated on the new MOSS web app.
The problem is, when I now browse to http://newmoss:1234 there is no content. If I manually add /_layouts/viewlsts.aspx to see the "View all content" page I see a few core libraries but nothing from the source web app. If I query the database though the content is there, it's just not wired up correctly.
Can anyone tell me where I am going wrong or offer me some guidance.
The database is around 600GB so fairly large. I've tried doing this backup/restore via STSADM as well but that failed during the restore process.
EDIT
I think I can see something strange when looking at the actual contents in the content database. The number of sites reported by central admin in the content database is 1. That matches what I see in the site collection list for this web app - one single root site collection.
When snooping around in the content database I can see several records in the "sites" table. This is strange as I would only expect to see a single site as per what Central Admin is telling me. Also when looking at the site ids in the database, and the site id of my broken restored site, it actually looks like the site that has restored is not the site I want! There are 5 records in the sites table and the restored site id matches the first record. The site I actually want (based on the column "Disk Used") is the third.
Any ideas what these other sites are and how I can restore a specific site?
According to https://sharepoint.stackexchange.com/questions/22150/content-db-restore-returns-0-sites, you cannot restore a content database from a site to a different site on the same farm.
Related
There are two SharePoint sites, each based on its own SharePoint installation.
Both are in the same domain.
The first site is for a document flow.
The second site is for a knowledge base.
I need to put a set of web parts (search, search results, indexed document library) from the second site in the master page of the first site.
The services and data will stay on the second site but they would be available in the first site.
I tried to apply the Page Viewer Web Part but it’s impossible to avoid using the second site’s master page layout.
Question
What other ways exist to solve this task?
You can index content of first SharePoint farm with search service application in another SharePoint farm.
You should configure search service application and add new website content source in search service application setting.
In this scenario you dose not need to move any thing and SharePoint crawl your content periodically.
I just moved my tfs 2013 in one server to tfs 2015 update 1 on another server, and I also changed the DB server behind.
Everything worked perfectly fine on the migration except for the sharepoint integration, unfortunately during the migration, the sharepoint content database where it was pointing to had physical errors on its content database (wss_content).
However I created another webapplication http://portaltfs, where I want to make the integration with tfs.
However, when I click on change or add, I get this error
Check this blog to see whether your upgrade process is correct. And try try to remove SharePoint extension and re-configure it.
Also, since you would attach the content database which migrated from TFS 2013, after creating new web application with the web site name and port number, go to
Manage Content Database from Central Administrator site, and select the web application created and check Remove content database. Then open SharePoint 2013 Management shell and use Mount-SPContentDatabase to attach the old content database. Refer to the blog for more details.
The DBA's want to know which databases I'm supporting. I haven't found what database servers these are on.
I have tried the following approaches:
I have read that the default is the directory, C:\Program Files\MS SQL\Data, according to this blog Content Database – Changing Default Location. I didn't find an mdb file.
I have looked in Sharepoint Central Administration > Application Management > Content Databases and found a content database name, but I couldn't find that in SharePoint's Central Configuration Web.config.
If it's in the instance's Web.config, I haven't found it.
The DBA's think that I have a different database for each site, but I cannot confirm this. Thanks in advance for any direction you can give me.
The default location you are referring to is the default location for SQL databases.
Go to Sharepoint Central Administration > Application Management > Content Databases
Change the Web application (on the right hand side of the screen) to the site you are looking for
Click on the Database Name
This page should tell you the database name and the database server. Copy both the Database server and the SQL server database name.
This should be the information the DBA's are looking for.
At a minimum you will have a Database per Web Application, but you can also have more than one, depending on how your SharePoint environment has been configure. You will see how many content databases you have per site on the "Manage Content Databases" site from step 2.
These steps show you the Content Databases, but SharePoint also uses additional databases for config and shared services.
Hope this helps!
UPDATE:
PROD_APPNAME_Search - I think this is your serach DB. To confirm go
to Central Administration > Operations > Services on Server > Windows
SharePoint Services Help Search
PROD_APPNAME_SharePoint_Config - Config DB for sharepoint. See this in the SharePoint Products and Technologies Configuration Wizard on the SharePoint server
PROD_APPNAME_SSP_DB - SSP Database (should be able to confirm this
from the step below)
PROD_APPNAME_SSP_Search_DB - Search Database
(should be able to confirm this from the step below)
PROD_APPNAME_SSP_WEB_APP - probably the content DB for the SSP
(should be able to see this in the steps from my original reply)
PROD_APPNAME_WEB_APP - content DB? (should be able to see this in the steps from my original reply)
PROD_APPNAME_MY_SITES - content DB? (should be able to see this in the steps from my original reply)
It looks like whoever setup your farm setup the DBs with the naming format PROD_APPNAME_, which is recommended.
To see the SSP DB's go to http://[servername]/_admin/managessp.aspx. For each SSP (you will probably only have one) click edit properties.
You most likely have one Content Database per Web Application.
Too see them, go to http://CENTRAL_ADMIN/_admin/CNTDBADM.aspx and choose the Web Application you want the info for. When you click the Content Database name, you get details such as:
Database server
SERVER_NAME
SQL Server database name
WSS_Content_WEBAPPDATABASE
With that info, you can trace the physical files from SQL Server, go to Properties > Files on the SQL Management Studio.
You can tell which database server your databases are on by
Opening Central Admin > Application Management > SharePoint Web Application Management > Content Databases
From the Web Application drop-down choose the web application you are interested in
Click the database you are interested in
Take not of the Database server and SQL Server database name
You can tell where the files for this database is located by
Opening SQL Server Management Studio
Connect to the Database server you identified in Step 4 above
Right-click the SQL Server database name you identified in Ste 4 above and choose Properties
In the Database Properties windows choose Files from the Select a page section
Take not of the Path and FileName for each of the files listed
If I use an existing web application's content database for a new web application, Will that import all lists,sites and libraries into the new web application being created ?
Or
The normal backup and restore is required ?
A content database contains one or more site collections and all the websites, documents etc inside that database.
This means you can take a copy of a content database from your production environment and use it in your dev environment. However you will not be able to attach two copies of the same content database to a web application.
It may be possible to use it again for a second web application on the same SharePoint farm, but I strongly recommend against doing that in a production environment.
A content database does not store custom code and other customisations, these have to be installed before the restored sites will work correctly.
For more:
http://community.bamboosolutions.com/blogs/sharepoint-2010/archive/2010/11/02/sharepoint-2010-cookbook-migrate-a-sharepoint-2007-site-to-sharepoint-2010.aspx
I want to perform the data migration between two SharePoint farms located on the same active directory. I don't know on how to migrate the data from one SharePoint from to another new SharePoint Farm
Several ways of doing this:
1) Backup content database on source farm and restore in target farm, then attach to a web application.
2) Create (i.e. export) a content migration package on the source farm and import on the target farm
3) Set up a content deployment path between the source and target farms (probably not appropriate in this case)
All of these are documented extensively on Technet. If you have custom or third-party code you will need to deploy these to the target server also.
The fundamental processes will be like this:
Create a new web application in your new WSS server.
Follow the instructions in Move content databases between instances of SQL Server.
However you may not be able to perform all of the steps exactly as written if your previous server farm is not available. The main thing is that you get the most recent backup of the databases restored on your SQL Server, then follow these steps from the linked article:
In Central Administration, on the Application Management page, in the SharePoint Web Application Management section, click Content databases.
On the Manage Content Databases page, click Add a content database.
On the Add Content Database page, type the exact name of the transferred content database, and then click OK.
Repeat steps 14 and 15 for each database you are adding. Be sure that you select the correct Web application from the Web Application menu for each database.
I don't know your farm topology but if you are sharing the same SQL Server used for the dead server farm, make sure that the dead farm is completely powered off. You don't want two different SharePoint farms accessing the same data (especially if one is in an inconsistent state).
If the old farm is alive and not in inconsistent state then you will be better off using a migration tool even if the versions of new and old are same.
The reason is that service packs, patches as well as order of their installation causes differences in SharePoint instances which can mess backup-recovery mechanism.
Migration is much more forgiving as it pre-assumes that differences exist between source and destination.
Several migration tools are available with Sharegate being my favourite.