У нас вы можете посмотреть бесплатно Reatime Reverse Logshipping Scenario with2nodeVMware или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
In this video, we will see Reverse Log Shipping in SQL Server with a real-time practical example. First, we configure normal log shipping between Node1 (Primary) and Node2 (Secondary). Then we perform a planned failover, and finally, we configure Reverse Log Shipping to make Node2 the new Primary and convert Node1 into a standby readable secondary. This complete activity is very useful in DR Switchover, Disaster Recovery Testing, Data Center Migration, and Maintenance operations. The same steps are followed in real-time production environments.
Below are the exact steps followed in this session for Reverse Log Shipping:
1) Disable backup job in primary Node1
2) Run copy/restore job on secondary Node2
-- Make sure all pending logs are restored
3) Take final log backup in primary with NORECOVERY
-- BACKUP LOG DB_NAME TO DISK = 'path\Final_LS_Reverse_log.trn' WITH NORECOVERY;
4) Restore this final log backup on Node2 with Recovery:
RESTORE LOG DB_NAME FROM DISK = 'path\Log_Name.trn' WITH RECOVERY;
5) Configure Log Shipping in Node2 (New Primary) in Standby mode, adding Node1 as target
6) Select option: No, the secondary database is initialized
7) Take log backup on Node2 (new Primary) and manually restore that log on Node1 using standby undo file
-- RESTORE LOG DB_NAME FROM DISK='path
ew_log.trn' WITH STANDBY='path\undo_file.TUF';
8) Now database in Primary Node1 becomes Standby (Read-Only)
Reverse Log Shipping completed successfully
Notes:
If database is corrupt, backup using NO_TRUNCATE
-- BACKUP LOG DB_NAME TO DISK = 'path\Final_LS_log.trn';
-- BACKUP LOG DB_NAME TO DISK = 'path\Final_LS_Corrupt_log.trn' WITH NO_TRUNCATE;
-- Finally, remove outdated Log Shipping configuration from old Primary Node1 (jobs get auto deleted) and clean up old log files from shared folders.
Conclusion:
Reverse Log Shipping, SQL Server Log Shipping, Log Restore, SQL Server DR, Failover, Undo file, Standby mode, SQL DBA, High Availability, SQL Server disaster recovery, Log Shipping jobs, Production DR, Copy Restore workflow, DR drill, SQL Server switchover, Final log backup NORECOVERY.
#logshipping #sqldba #reverselogshipping #sqlserver #sqlserverdba #disasterrecovery #highavailability #failover #drill #sqltutorial #sqltraining #databaseadministration #ha #dr #demosql