2.2 Transaction Log Shipping Tips and Tricks (45m)
In theory, log shipping is easy: just restore your transaction log backups. In reality, you need to understand how to deal with unplanned failovers, reversing log shipping the other direction, and fixing a lagging secondary.
5 Comments. Leave new
Leave a Reply Cancel reply
- 1.1 Intro and DBA Skills Quiz (33m)
- 1.2 Building and Testing Reliable SQL Servers Part 1 (25m)
- 1.2 Building and Testing Reliable SQL Servers Part 2 (21m)
- 1.3 Architecture for HA and DR Part 1
- 1.3 Architecture for HA and DR Part 2
- 1.4 Design Quorum for Failover Clusters (23m)
- 1.5 Triaging Failure in Availability Groups (32m)
- 1.6 Recovering from Failover Part 1 (40m)
- 1.6 Recovering from Failover Part 2 (12m)
- 1.7 Building an Inventory and a Support Matrix (39m)
- 2.1 Database Mirroring Field Medic Guide (40m)
- 2.3 Troubleshooting Backup and Restore Problems (35m)
- 2.4 Optimizing DBCC CHECKDB (53m)
- 2.5 Availability Group Backup and CHECKDB Part 1 (8m)
- 2.5 Availability Group Backup and CHECKDB Part 2 (32m)
- 2.6 Cloud for the Senior DBA (38m)
- 2.7 Homework: Deciding Between Availability Solutions Part 1 (11m)
- 2.7 Homework: Deciding Between Availability Solutions Part 2 (27m)
- 3.1 Shared Storage Part 1 (28m)
- 3.1 Shared Storage Part 2 (32m)
- 3.2 Advanced SAN Features – Storage Tiering and Snapshots (31m)
- 3.3 Virtualization Management and Troubleshooting (61m)
- 3.4 Server Hardware Sizing (36m)
- 3.5 Homework Part 1 (11m)
- 3.5 Homework Part 2: Answers (28m)
- 3.6 Index Maintenance for Enterprise Environments (43m)
- 3.7 Recap and Q&A (28m)
You mention the secondary database should be in NORECOVERY mode during backup restore, and can be in STANDBY mode if we want to allow users read only access. Is it because the restore would fail?
I tried to leave the database in STANDBY mode while running log restore, and it seemed to complete OK, and the new data is visible in the read-only copy of the database (SQL 2017). I did try to switch between the two modes without any issues, and the database would still restore fine. Is that the normal behavior for SQL 2017, or am I missing something in the process?
Thank you Walter (Vladislav).
The problem is that the restore will be blocked while users have open queries, and then the request to do a restore will subsequently block OTHER user queries, so you end up with a blocking disaster.
I was testing the restore with no users querying, makes sense now 🙂
At about 8:50 you mention that you have a blog post about how to sync to Google cloud. Is that still relevant in 2020? Can you provide a link to that, or a relevant blog post related to the idea? Google, Azure, AWS, or something like that? I did Google “Google database sync site:brentozar.com” and found some good articles, but not the one you mentioned.
Kevon – sure, they’re in the First Responder Kit. Download that, and we have PDFs in there.