You are on page 1of 12

Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Log Shipping is a basic level SQL Server high-availability technology that is part of SQL Server. It is an
automated backup/restore process that allows you to create another copy of your database for failover.

Log shipping involves copying a database backup and subsequent transaction log backups from the
primary (source) server and restoring the database and transaction log backups on one or more
secondary (Stand By / Destination) servers. The Target Database is in a standby or no-recovery mode on
the secondary server(s) which allows subsequent transaction logs to be backed up on the primary and
shipped (or copied) to the secondary servers and then applied (restored) there. No second license is
need it for the Secondary Server. To setup a log-shipping you must have sysadmin rights on the server.

Primary Licensed SQL Server Secondary Non Licensed SQL Server

Main DB Second DB
D Database D Database
Main LG Second LG
L Database
L Database
Local Data Local Data
Backups
K K
Backups

Backup Log Restore Log


Log Backups are created in a Copy and restore performed by
folder that is also a network SQL Server Agent jobs on the
share accessible by the Secondary Server keeps Full
Secondary Server Backup of Main Server

Agent Jobs

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |1
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Previous to start the configuration performance a total backup on main database to be restore in a
secondary server in order to save time and resources. Please follow the pictures to configure the log-
shipping by steps

1. Configuring Transaction Log Backup in a main server

The hard K is usually uses for daily full backup and transaction logs. Please provide sysadmin rights to
the destination folder.

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |2
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

2. Schedule a transaction log is define by the minimal time that can be lost in case of a database
crash or the intensity of use of the application.

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |3
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

3. Configure the Secondary database by steps please follow the pictures

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |4
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |5
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |6
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |7
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |8
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 Page |9
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

This are the administrative right that must be granted in a folders where SQL agent will performance the
savings:

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 P a g e | 10
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

4. Now is time to restore the database to the secondary server

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 P a g e | 11
Configuring SQL Log-Shipping for GN4 or GnWeB by GSI

5. Finally perform a schedule job is the best way to be sure all works

Rafael Riera

Project Manager

Phone 7x24: 1 305 477 9998 GSI Media Group: 3331 NW 82 Ave Miami FL 33122 P a g e | 12

You might also like