|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 11:19 PM
Points: 823,
Visits: 2,405
|
|
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
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 3:17 PM
Points: 5,270,
Visits: 11,212
|
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 4:11 PM
Points: 37,741,
Visits: 30,020
|
|
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 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 3:17 PM
Points: 5,270,
Visits: 11,212
|
|
well looks like I finally learned to type faster than you!
---------------------------------------------------------------------
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 11:19 PM
Points: 823,
Visits: 2,405
|
|
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)?
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 3:17 PM
Points: 5,270,
Visits: 11,212
|
|
the link i posted should answer your questions but you dont need to remove mirroring to set up logshipping.
---------------------------------------------------------------------
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 4:11 PM
Points: 37,741,
Visits: 30,020
|
|
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 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 2:46 AM
Points: 167,
Visits: 413
|
|
Hi Gila, Can it is possible with replication (primary server)?
Satish
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 1:45 AM
Points: 5,204,
Visits: 11,163
|
|
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"
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 11:19 PM
Points: 823,
Visits: 2,405
|
|
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 -----
Date 11/27/2012 11:15:00 AM Log Job History (LSRestore_PrimaryServer_DEV)
Step ID 1 Server SecondaryServer Job Name LSRestore_PrimaryServer_DEV Step Name Log shipping restore log job step. Duration 00:01:01 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message 2012-11-27 11:16:01.04 Starting transaction log restore. Secondary ID: '5c3dbdb3-ccb7-41d8-9d2b-1cceedb2b59c'
Message 2012-11-27 11:16:01.16 Retrieving restore settings. Secondary ID: '5c3dbdb3-ccb7-41d8-9d2b-1cceedb2b59c' 2012-11-27 11:16:01.18 Retrieved 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.21 Retrieved 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.46 Searching through log backup files for first log backup to restore. Secondary DB: 'DEV'
Message 2012-11-27 11:16:01.67 Found first log backup file to restore. Secondary DB: 'DEV', File: '\\SecondayServer\d$\LAB\DEV_20121127053101.trn'
Message 2012-11-27 11:16:04.43 Restored log backup file. Secondary DB: 'DEV', File: '\\SecondayServer\d$\LAB\DEV_20121127053101.trn' 2012-11-27 11:16:04.50 The restore operation was successful. Secondary Database: 'DEV', Number of log backup files restored: 1
Message 2012-11-27 11:16:04.56 Deleting old log backup files. Primary Database: 'DEV' 2012-11-27 11:16:04.59 The 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.
|
|
|
|