Before you can begin the log-shipping deployment process, you need to do some initial configuration. Then you have a choice regarding how you want to deploy: using the SQL Server 2008 Management Studio or using T-SQL scripts. Typically, a DBA uses SQL Server 2008 Management Studio to configure log shipping and then generates SQL scripts for future redeployment. We cover both procedures here.
To configure your network for log shipping, first create a backup folder that the primary server can access; share it, and ensure that it is accessible by the secondary server. For example, you could use the folder c:\primaryBackupLog, which is also shared as a UNC path: \\primaryserver\primaryBackupLog. The primary server's SQL Agent account must have read and write permission to the folder, and the secondary server's SQL Agent account or the proxy account executing the job should have read permission to this folder.
Next, create a destination folder on the secondary server, such as c:\secondaryBackupDest. The secondary server's SQL Agent account or the proxy account executing the job must have read and write permission to this folder.
The recovery model for the log-shipped database must be set to either Full or bulk_logged There are two ways to set the recovery model: with Management Studio or with a T-SQL command. Using Management Studio, open the Database Properties window and select Options. From the Recovery model drop-down, ...