http://sqlserverpedia.com/wiki/Prerequisites_for_Log_Shipping_(SQL_Server_2005)
- Both source and target instances of log shipping must be running SQL Server 2005 Enterprise Edition, Workgroup Edition or Standard Edition.
- Account(s) running SQL Server service on source and destination instance must have access to the network folder where you will store transaction log backup files.
- Computers hosting primary and standby SQL Servers must be connected to a network.
- SQL Server Agent service must be running on both source and destination servers. Log shipping is implemented as a collection of jobs. If SQL Server Agent service isn't running, none of the jobs will execute.
- Log shipping must be setup at the database level. The database must use either full or bulk logged recovery model. Simple recovery model truncates transaction log during each checkpoint and does not support transaction log backups. Therefore databases that use simple recovery model cannot participate in log shipping. If you want to provide high availability for multiple databases on a single instance of SQL Server, you must setup log shipping separately for each database.
- Although not a prerequisite for log shipping configuration, it is essential to realize that in case of failover the target server becomes your primary database server. If you want to provide acceptable level of service to your user community in case of the primary server's failure, then ensure that the standby (target) server has the same hardware configuration as the primary (source) server.
http://databases.about.com/od/sqlserver/ht/Transaction_Log_Shipping.htm
Log shipping allows you to keep two SQL
Server databases synchronized for high availability. In a log shipping
relationship, the primary server transfers copies of its transaction logs to
the secondary server on a periodic basis. The secondary server receives those
logs and uses them to update its copy of the database so that it is then in the
same state as the database on the primary server
Time Required: One hour
Here's
How:
1. Create the target database on the secondary server by restoring a full backup of the database from the primary server. Be sure to include backups of the transaction logs by using the WITH NORECOVERY option.
2. Create a network file share on the primary server (or another location available to both servers) that will store the transaction log backups.
3. Connect to the primary server using SQL Server Management Studio and expand the Databases folder. Locate the database you wish to replicate, right-click on it and choose Tasks -> Ship Transaction Logs from the pop-up menu.
4. Select the "Enable This as a Primary Database in a Log Shipping Configuration" check box.
5. Click the Backup Settings button.
6. In the network share textbox, enter the path to the share you created in Step Two. If the share is on the primary server, also enter the path in the second textbox.
7. Click OK to close the Transaction Log Backup Settings window.
8. In the Secondary Databases section of the Transaction Log Shipping properties page, click the Add button.
9. Click the Connect button and provide connection details for the secondary server that will receive the transaction log backups from the primary server.
10. Verify that the Secondary Database drop-down box contains the name of the database you created on the secondary server in Step One.
11. Select the Copy Files tab.
12. Provide the destination folder for the copied files on the secondary server. This is a temporary storage location, so you may choose any path you wish.
13. Review the other settings and make any changes you deem appropriate, then click the OK button to continue.
14. Repeat Steps Nine through Thirteen for any additional secondary servers if you wish to configure more than one transaction log recipient.
15. Click OK to close the Database Properties window. SQL Server will then display a status window while it configures transaction log shipping.
How to perform Log shipping
http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx
Hope this weblink may give an idea about log shipping..
http://www.tek-tips.com/faqs.cfm?fid=5754
How to: Enable Log Shipping (SQL Server Management Studio)
http://technet.microsoft.com/en-us/library/ms190640.aspx
