May 5, 2017 at 6:28 am
Hi
In Local IDC High availability Database mirroring already configured since 5 years back with manual failover with no witness server. Now management decided to configure this DR setup with existing database mirroring setup.
TLOG backup configured every 15 min in principal database for controlling LDF file size growth and point in time recovery
we can 't extent one more 3rd node due to DB mirroring limit and support only tow nodes. And 3rd party vendor application restrictions I can't upgrade higher version SQL 2012 or 2016 for choosing alwayson HA new feature
I need to choose option Log shipping only for fulfill this DR requirement. So I want to know what is the time interval to be setting in TLOG backup setting in Log shipping scenario due to already TLOG backup configured every 15 min in principal database.
So, Can we choose two different timing custom TLOG backup and TLOG backup in log shipping setup
1. Custom TLOG backup at every 30 min
2. Log shipping TLOG backup at every 15 min
Will it cause of LSN chain brake in log shipping if above two backup times? Please suggest.
Thanks
May 5, 2017 at 6:50 am
Yes, if you have two processes backing up the transaction log it will cause a break in the LSN sequence and thus impact logshipping.
Setup logshipping to meet your companies RTO and RPO schedules, then disable anything else that could be doing TX log backups.
Note - If your using Ola Hallengren's backup solution it will automatically not backup a database that is configured for logshipping.
May 5, 2017 at 6:57 am
Please this Microsoft knowledge base article for more on mirroring and log shipping combined together
https://technet.microsoft.com/en-us/library/ms187016(v=sql.110).aspx
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 5, 2017 at 7:16 am
Thank you Mr. Perry and Mr. Anthony. for yours valuable comments
I will disable custom TLOG backup in Principal database server during configuration of log shipping.
Does Log shipping technique will take of LDF growth size? So normal TLOG backup will truncate unused log space in LDF file and reuse it again, that will be managed log growth rate. Please suggest.
RPO and RTO are 4 hours defined and approved by business side. for recovery server and database both.
My assumption data bit loss duration of 15 min because log shipping TLOG backup schedule at every 15 min.
If primary principal database server failure, then data available on both the location Mirror server as well as DR setup server with 15 min gap.
Thanks
May 8, 2017 at 11:42 am
SQL Galaxy - Friday, May 5, 2017 7:16 AMI will disable custom TLOG backup in Principal database server during configuration of log shipping.
No!
Do not disable the backup job created by the log shipping configuration, remove the database backup from any other jobs that may run apart from the configured job.
SQL Galaxy - Friday, May 5, 2017 7:16 AM
Does Log shipping technique will take of LDF growth size? So normal TLOG backup will truncate unused log space in LDF file and reuse it again, that will be managed log growth rate. Please suggest.
Log truncation on the Log shipping Primary will be handled by the Log shipping configured log backup job.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 8, 2017 at 10:41 pm
Thanks Mr. Perry.
I have gone through Microsoft Link and documents which is suggested by you.
In that architecture backup share server introduced and this backup share folder storing TLOG backup files which is access restoring TLOG files in stand by server.
Feature of backup share folder Log shipping will continue work if primary server down or planned downtime.
Please suggest as below points:
1. Should be backup share folder should be access on SQL service account?
2. where I have to create backup share folder in Primary location or remote location?
Thanks
May 11, 2017 at 7:21 am
SQL Galaxy - Monday, May 8, 2017 10:41 PM1. Should be backup share folder should be access on SQL service account?
The sql server service accounts should have access to the fileshare, as the jobs typically run under the agent service account
SQL Galaxy - Monday, May 8, 2017 10:41 PM2. where I have to create backup share folder in Primary location or remote location?
Thanks
It depends on your preference, a network fileshare accessible to all nodes makes sense too though
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply