SQL Log Shipping
Last updated
Last updated
A secondary SQL Server database, also known as a log shipping target, is regularly updated from a primary database copy. SQL Log Shipping is a commonly used technique to keep a secondary database up-to-date. However, native tools can often require manual configuration steps. Rubrik automates all the config steps, which creates a synchronous copy of a DB for Disaster Recovery.
You can now configure SQL Server Log shipping to create a synchronous copy of StandAlone_AdvWorks and explore how you can prepare for DR.
To get started, first navigate to Inventory > All > SQL Server Databases.
Navigate to sql1.rubrik.lab > MSSQLSERVER > StandAlone_AdvWorks.
Click (...) ellipse and select Add Log Shipping Secondary.
Select sql2 as the compatible host.
Click NEXT.
Select MSSQLSERVER as compatible instances.
Add StandAlone_AdvWorks as the secondary database name, select Advanced Export and choose the default export path.
Click ADD.
From the desktop taskbar at the bottom, double-click the Microsoft SQL Management studio.
Select SQL2 as the Server name.
Click Connect. Expand Databases and verify that StandAlone_AdvWorks is listed as one of the databases.
Under Object Explorer, click Connect Object Explorer next to Connect. Select SQL2 as the server name and click Connect.
Expand Databases for SQL2, and you will find the StandAlone_AdvWorks is now in a (Restoring...) State.
Rubrik automates the configuration tasks on the primary and secondary SQL Servers.
You now have all the recovery options in your armor to ensure your critical data is always available!
Congratulations on completing the migration of your MS SQL database to RSC!
