how to write network path in log shipping

Though not absolutely necessary, as you could use a shared network path, I find putting these on the secondary is much more efficient. As indicated, this folder usually resides on the secondary server. Here you will need to specify the destination folder for the copied log files.

Though not always necessary, it prevents you from having to go move them later.įor the next step, click the Copy Files tab. If you choose the first option you can also click on Restore Options… to manually set the folder where the data and log files will reside on the secondary server. This option covers pretty much any scenario that could exist and is definitely the safest bet. However, I find it is generally a better idea to select the first option to Generate a full backup of the primary database and restore it to the secondary database (and create the secondary database if it doesn’t exist). If the database exists and is already populated from a recent backup you should be able to select the option No, the secondary database is initialized.

Now, depending on whether the database exists on the secondary server will determine which option you should select on the Initialize Secondary Database tab. To put the database in the Full recovery model use this script, though you will need to change the database name to match the one you are using. Though you can change the recovery model from the Options page of the database properties window, I find it is easier to do by using one of the following scripts. Most importantly, you need to make sure the database on the primary server (the server from which the transaction logs will be shipped) is set to the Full or Bulk-Logged recovery model.įor the purposes of this guide I will be working with a newly created database that I have named LogShipTest. You’ll also want to make sure the SQL Server Agent service is running on both servers. For starters, you’ll need a directory that is accessible to both servers for copying the transaction log backup files. There are a couple things that need to be in place before you begin configuring log shipping. For that reason I have decided to provide a step by step guide to help anyone out there who is looking to configure log shipping between two SQL Servers. However, there are a few steps that can be a little confusing if you’re new to log shipping. In reality, it’s actually pretty straight forward. If you’ve never configured log shipping within SQL Server it can seem to be a bit of a challenge.

How to write network path in log shipping