June 12, 2024 at 3:20 pm
Hi
We have logshipping which get out of synch in night due to purging process of production but iy eventually gets synhced by morning .But now its taking time to get in synch.I want to check how much time its takes to copy log backup files and then how much it take to restores and further why it took high amount of time for restoration .
I know i can see duration in agent history but it get purged so its it possible to get data from system tables ? if yes then which one should i look for
and how to find log restore duration time ?
It purely dr server with database in recovery mode
June 12, 2024 at 6:55 pm
June 13, 2024 at 10:42 am
Hi
We have logshipping which get out of synch in night due to purging process of production but iy eventually gets synhced by morning .But now its taking time to get in synch.I want to check how much time its takes to copy log backup files and then how much it take to restores and further why it took high amount of time for restoration .
I know i can see duration in agent history but it get purged so its it possible to get data from system tables ? if yes then which one should i look for
and how to find log restore duration time ?
It purely dr server with database in recovery mode
You can also get the log shipping status report from server right click report --> Transaction Log Shipping Status.
also can get the backup file and restore files with timestamps from tables msdb..log_shipping_monitor_primary and msdb..log_shipping_monitor_secondary in respective servers
June 13, 2024 at 5:27 pm
Hi
So actual issue is log restoration is taking time . Need to debug it.Can anybody provide pointers why ist taking time to restore log backup files
Its dedicated dr server so no other query runs and database is in norecovery mode. Its not disk latency issue as it eventually catches up but durning morning time when purging and index executes at same time in prod then size of log files get increased and its those which are taking tome to get restored .So need to dug up and provide some solution
June 14, 2024 at 7:25 am
This was removed by the editor as SPAM
June 14, 2024 at 3:21 pm
How often does the log backup agent job run?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 19, 2024 at 10:11 am
Hi
So actual issue is log restoration is taking time . Need to debug it.Can anybody provide pointers why ist taking time to restore log backup files
Its dedicated dr server so no other query runs and database is in norecovery mode. Its not disk latency issue as it eventually catches up but durning morning time when purging and index executes at same time in prod then size of log files get increased and its those which are taking tome to get restored .So need to dug up and provide some solution
The purging is causing the log file to grow--> Increases the backup & restore operation duration
Same is the case with index manipulation.
June 19, 2024 at 9:46 pm
Try beefing up your DR with more CPU and RAM so it can restore faster. Some companies setup DR servers on lower resources from PRD in order to save costs. Also check and store the transaction logs in Premium SSD disks for faster restore performance.
Tung Dang
Azure and SQL Server DBA Contractor / Consultant
DataZip
June 19, 2024 at 10:08 pm
Will be disk issue most likely
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply