SQL Server log shipping is a high-availability technology that allows you to create another copy of your database for failover. It involves three steps: generating the log backup on the primary database, copying the backup to the network location or the specific directory on the secondary server, and restoring the log backup on the secondary server.
To configure SQL Server log shipping, you need to have sysadmin rights on the server, and the database must use the full recovery or bulk-logged recovery model. You also need a shared folder for copying the transaction log backup files, and SQL Server Agent Service must be configured properly. You can use SQL Server Management Studio (SSMS) or Transact-SQL (T-SQL) to set up log shipping.
For a step-by-step guide on how to configure SQL Server log shipping using SSMS, you can refer to this article. How to Configure Log Shipping in SQL Server It explains how to enable the database for log shipping, how to configure the backup settings, how to add secondary servers and databases, and how to monitor the log shipping status.
For a step-by-step guide on how to configure SQL Server log shipping using T-SQL, you can refer to this article. How to configure SQL Server Log Shipping - SQL Shack It shows how to create a backup share, how to create a backup job on the primary server, how to create a copy and restore job on the secondary server, and how to verify the log shipping configuration.