- Overview - Oracle Data Guard vs SQL Server Log Shipping - Log Shipping Architecture - Environment Details - Prerequisites - Step-by-Step Configuration - Verification & Testing

Overview Log Shipping copies transaction log backups from the Primary server to one or more Secondary servers and restores them, keeping databases synchronized for Disaster Recovery (DR) or Read-Only Reporting scenarios.

> Oracle Data Guard Redo transport is internal, continuous, and process-driven (LGWR → RFS → MRP). Oracle Data Guard Redo transport is internal, continuous, and process-driven (LGWR → RFS → MRP). > SQL Server Log Shipping Log transport is external, file-based, and job-driven (Backup → Copy → Restore). SQL Server Log Shipping Log transport is external, file-based, and job-driven (Backup → Copy → Restore).

Log Shipping is a disaster recovery (DR) solution where: - Primary Server takes transaction log backups and saves them to a shared network path. - Secondary Server copies and restores those logs (STANDBY or NORECOVERY mode). - No shared storage is required — only T-Log backups over a network share .

- SQL Server 2022 Standard or Enterprise - Same database name (collation recommended to be same) - Database must be in FULL recovery model - SQL Server Agent must be running on Primary & Secondary - Service accounts must have Read/Write access to the shared folder

Right-click database → Properties → Options → Set Recovery Model = FULL . Take a full database backup.

Database → Properties → Transaction Log Shipping → Enable this as a primary database.

- Network path - Local backup folder (if you are storing Tlog Backups in local drive ) - Backup job schedule (e.g. every 5 minutes)

Initialize Secondary → Restore from backup (recommended). Configure Copy and Restore jobs.

Click OK. SQL Server will automatically create all required jobs.

Jobs will be created automatically: - Primary: LSBackup_SALES, LSAlert_SGMSQL1 - Secondary: LSCopy, LSRestore, LSAlert_SGMSQL2 Secondary database should be in Standby / Read-Only mode.

Create a table on Primary and verify it appears on Secondary after restore. On Primary : On Standby : (After 5 Minutes) Caution: Your use of any information or materials on this website is entirely at your own risk. It is provided for educational purposes only. It has been tested internally, however, we do not guarantee that it will work for you. Ensure that you run it in your test environment before using.