Hi,We are configuring log shipping for MOSS 2007 SP1 databases on SQL Server 2005 SP3.
I going through the link http://technet.microsoft.com/en-us/library/dd890507.aspx and I have question here.
Question: Are the below mention steps for the INITIAL setup of Log shipping setup for both MOSS & SQL Server or the steps that need to performed on DR day? Because I/m confused with the heading "The failover phase is composed of the following procedures" .
I'm assuming it's an initial setup. Please correct me if I'm wrong.
Prepare the primary farm
The steps to prepare the primary server include the following:
Set the application pool identity on the Web applications to a domain account that is available on both farms. For more information, see Change the application pool identity for a Web application (Office SharePoint Server) .
Document all of the configuration settings so that they can be applied to the secondary farm. For more information, see Prepare to back up and restore a farm (Office SharePoint Server 2007) . Make sure, especially, to document the alternate access mapping settings by exporting them to a text file; use the command stsadm -o enumalternatedomains to export the settings.
Document all of the customizations. The customizations will be easiest to reapply to the secondary farm if they are packaged as solutions. For more information, see Deploy customizations .
Prepare the secondary farm
Install and configure Office SharePoint Server on the secondary farm. For more information, see Deploy Office SharePoint Server 2007 in a server farm environment .
We recommend that if you have enough equipment, you configure the same number of front-end Web servers and databases as the primary farm. If you have insufficient equipment, you can use fewer servers in the secondary farm, but it may be unable to handle the same load as the primary farm.
Ensure that the version number and patching level is the same on both the primary and secondary farms. For more information, see Updates Resource Center for SharePoint Products and Technologies (http://go.microsoft.com/fwlink/?LinkID=106182).
Apply all configurations and customizations that you have made to the primary farm. For more information, see Deploy customizations .
Create duplicates of all Web applications that exist in the primary farm. Be sure to use the same application pool identity as the Web applications in the primary farm. For more information, see Creating and managing Web applications (Office SharePoint Server) .
Disable the following timer jobs. For more information, see Manage SharePoint timer jobs (Office SharePoint Server) .
Bulk workflow task processing
Site Collection: Delete
Quick Profile Synchronization
Records Center Processing
Variations Propagate Page Job Definition
Dead Site Delete
Variations Propagate Site Job Definition
Disk Quota Warning
Windows SharePoint Services Watson Policy Update
Scheduled Page Review
Hold Processing and Reporting
Workflow Auto Cleanup
Search and Process
Information management policy
Shared Services Provider Synchronizing Job
Configure log shipping
You can configure log shipping by using either SQL Server Management Studio, or Transact-SQL.Validate that log shipping was successful
Start Management Studio on the database server in the secondary farm.
In the Object Explorer navigation pane, verify that all log-shipped content databases have Standby or Read-Only status.
Determine how long average log shipping jobs take to run on the secondary farm, by running the jobs and timing their duration. For more information, see Monitoring Log Shipping (http://go.microsoft.com/fwlink/?LinkId=151682).
Attach the log-shipped databases to the secondary SharePoint farm
On the SharePoint Central Administration Web site, on the Quick Launch, in the Central Administration section, click Application Management . The Application Management page opens.
In the SharePoint Web Application Management section, click Content databases .
The Manage Content Databases page opens.
In the Database Name column, click the content database that you want to remove. The Manage Content Database Settings page opens.
In the Remove Content Database section, select the Remove content database check box, and then click OK .
On the Manage Content Databases page, click Add a content database . The Add Content Database page opens.
Enter the appropriate database server and database name of the log-shipped content database, and then click OK .
Repeat this procedure for all databases that you are log shipping.
At this point, you can browse to the content on the secondary farm.
Configure search and profiles for the secondary farm
Configure search in the secondary farm to meet the business objectives for the disaster recovery scenario. Initially, you may want to search the same databases, with the same crawl settings and crawl rules as the primary farm. If you determine that you cannot schedule crawls and log shipping so that they avoid overlapping, we recommend that you adjust the content that you include in crawls. For example, before failover, you might crawl only those databases that contain content of high business impact, and then crawl other content only after failover. For more information, see Limit or increase the quantity of content that is crawled (Office SharePoint Server) .
Stop the SQL Server Agent job on the secondary farm to disable log shipping while you configure search.
Configure search on the secondary farm.
Determine how long search crawls take on the secondary farm. You can use data collected from the primary farm to estimate the time required on the secondary farm.
Start the SQL Server Agent job on the secondary farm to enable log shipping.
If you are using profiles, the profiles on the failover SSPs are not synchronized to the profiles on the primary SSPs — they will be in the state they were in when first imported. To keep the profiles on all SSPs synchronized, use the User Profile Replication Engine that is included in the 32-bit version of the Microsoft SharePoint Administration Toolkit x86 (http://go.microsoft.com/fwlink/?LinkId=151962) or in the 64-bit version of the Microsoft SharePoint Administration Toolkit x64 (http://go.microsoft.com/fwlink/?LinkID=142035). For more information, see User Profile Replication Engine (Office SharePoint Server) .
Create a script to refresh the list of sites in the secondary farm configuration database (refresh script)
Use the following example as a model to create a refresh script that you can run on the secondary farm when site collections have been added or deleted on the primary farm.
In the example script replace <db_name 1>, <URL >, and <db_name2 >, <URL > with the names of the log shipped databases.
Add detach and attach sections to the script for each of the log shipped databases.
and also at the bottom of the above link, it again describes the different steps with the same heading The failover phase is composed of the following procedures, which include the below steps (I belive, these are the steps need to be performed on DR day)
- Edited by Mike Walsh FIN Wednesday, March 10, 2010 6:45 PM Question made out of Title that was a statement.
This is the CONFIGURATION part of the process. The actual disaster recovery part, (after a server fails) starts at the section after this section titled "FAILING OVER".
I trust that answers your question...
- Proposed as answer by Walt Whitman [MSFT]Microsoft employee Wednesday, January 05, 2011 3:28 PM
Please in future do not quote so much of a document.Either only refer to the URL of the document; or quote heavily reduced extracts (of the essential parts) from it.(Moderator)
FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
Complete Book Lists (incl. foreign language) on each site.