November 17, 2012 at 2:36 am
Hi,
Database have been configured High availability in same datacenter by using database mirroring..
For the anohter requirement the same principal database wants to be configure another datacenter for Disaster recovery purpose, please suggesstion me how to configure?
rgds
ananda
November 17, 2012 at 4:43 am
A mirrored database can also be log shipped, so you have that option open to you for your replication to the DR site.
http://msdn.microsoft.com/en-us/library/ms187016(v=sql.100).aspx
---------------------------------------------------------------------
November 17, 2012 at 4:43 am
With mirroring there can only be a single mirror database. You'll need to either use log shipping to the secondary datacentre, upgrade to SQL 2012 and use availability groups or consider some other method of DR.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 17, 2012 at 4:45 am
well looks like I finally learned to type faster than you!
😉
---------------------------------------------------------------------
November 17, 2012 at 4:56 am
Thanks for reply...
1. Principal database - Primary server
2. Mirror database - secondary server
These two servers data has been synchronized between two servers with HIGH SAFTY mode mirror operations.
I have doubts.
From Mirror database - secondary server, can able to configure logshipping to DR site? or I need to remove mirror setup in primary server after that configure HA (same datacenter) and DR (another datacenter)?
November 17, 2012 at 5:07 am
the link i posted should answer your questions but you dont need to remove mirroring to set up logshipping.
---------------------------------------------------------------------
November 17, 2012 at 6:03 am
No, you cannot set up log shipping from the secondary, no you do not need to remove mirroring.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 19, 2012 at 12:34 am
Hi Gila,
Can it is possible with replication (primary server)?
Satish
November 19, 2012 at 1:45 am
saidapurs (11/19/2012)
Hi Gila,Can it is possible with replication (primary server)?
Satish
A simple search of the Microsoft site produces this link
http://msdn.microsoft.com/en-us/library/ms151799.aspx
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 26, 2012 at 11:33 pm
I have tested only LOG SHIPPING with Test server, it was working fine after 2 days watching and monitoring logshipping activity then going to configure production servers.
Please verify and suggestion need to be modify the LSRestore logs in secondary servers and database standby mode..
Microsoft (R) SQL Server Log Shipping Agent
[Assembly Version = 10.0.0.0, File Version = 10.50.1600.1 ((KJ_RTM).100402-1540 )]
Microsoft Corporation. All rights reserved.
2012-11-27 11:16:00.86----- START OF TRANSACTION LOG RESTORE -----
Date11/27/2012 11:15:00 AM
LogJob History (LSRestore_PrimaryServer_DEV)
Step ID1
ServerSecondaryServer
Job NameLSRestore_PrimaryServer_DEV
Step NameLog shipping restore log job step.
Duration00:01:01
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
2012-11-27 11:16:01.04Starting transaction log restore. Secondary ID: '5c3dbdb3-ccb7-41d8-9d2b-1cceedb2b59c'
Message
2012-11-27 11:16:01.16Retrieving restore settings. Secondary ID: '5c3dbdb3-ccb7-41d8-9d2b-1cceedb2b59c'
2012-11-27 11:16:01.18Retrieved common restore settings. Primary Server: 'PrimaryServer', Primary Database: 'DEV', Backup Destination Directory: '\\SecondayServer\d$\LAB', File Retention Period: 4320 minute(s)
2012-11-27 11:16:01.21Retrieved database restore settings. Secondary Database: 'DEV', Restore Delay: 0, Restore All: True, Restore Mode: Standby, Disconnect Users: False, Last Restored File: <None>, Block Size: Not Specified, Buffer Count: Not Specified, Max Transfer Size: Not Specified
Message
2012-11-27 11:16:01.46Searching through log backup files for first log backup to restore. Secondary DB: 'DEV'
Message
2012-11-27 11:16:01.67Found first log backup file to restore. Secondary DB: 'DEV', File: '\\SecondayServer\d$\LAB\DEV_20121127053101.trn'
Message
2012-11-27 11:16:04.43Restored log backup file. Secondary DB: 'DEV', File: '\\SecondayServer\d$\LAB\DEV_20121127053101.trn'
2012-11-27 11:16:04.50The restore operation was successful. Secondary Database: 'DEV', Number of log backup files restored: 1
Message
2012-11-27 11:16:04.56Deleting old log backup files. Primary Database: 'DEV'
2012-11-27 11:16:04.59The restore operation was successful. Secondary ID: '5c3dbdb3-ccb7-41d8-9d2b-1cceedb2b59c'
Message
2012-11-27 11:16:04.64----- END OF TRANSACTION LOG RESTORE -----
Exit Status: 0 (Success)
Message
Executed as user: IN\domain_ID The step succeeded.
November 27, 2012 at 2:53 am
ananda.murugesan (11/26/2012)
Please verify and suggestion need to be modify the LSRestore logs in secondary servers and database standby mode..
Sorry, i dont understand what it is you require!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 27, 2012 at 3:14 am
1. For the logshipping configuration, Should I remove the existing Tlog backup Job in sql agent? I have deleted existing backup jobs due to mismatch LSN.
if remove existing Tlog backup jobs, does LS backup job will take care transaction log?
2. I have posted Logshipping Resotre agent logs, Just i want to confirm if anything missing during the Tlogs restorations.
November 27, 2012 at 3:30 am
sorry, but you have totally lost me here. The out put you posted shows the restore with 1 file found and 1 file restored, what is the issue you are having?
If you want to remove the log shipping secondary, delete it via the log shpping page on the primary database it will remove the LS agent jobs on the secondary.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 27, 2012 at 4:37 am
If you have logshipping set up those are the ONLY log backups you should have. It fully takes care of your transaction logs
---------------------------------------------------------------------
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply