Overview and Prerequisites of Database Mirroring In SQL Server
About Mirroring:
Similar to logshipping mirroring is also implement on per database basis, mirroring is mainly implemented for increasing the database availability. Database mirroring maintains two copies of a single database that must reside on different instances. Depending on the mode of operation Mirroring provides minimal data loss. In the event of a disaster, in high-safety mode with automatic failover, failover quickly brings the standby database online with no data loss and Improves the availability of the production database during upgrades like service packs installation or any patch installation on Principal server which requires downtime, on that situation the standby database comes into picture.
Prerequisites for Database Mirroring:-
Similar to logshipping mirroring is also implement on per database basis, mirroring is mainly implemented for increasing the database availability. Database mirroring maintains two copies of a single database that must reside on different instances. Depending on the mode of operation Mirroring provides minimal data loss. In the event of a disaster, in high-safety mode with automatic failover, failover quickly brings the standby database online with no data loss and Improves the availability of the production database during upgrades like service packs installation or any patch installation on Principal server which requires downtime, on that situation the standby database comes into picture.
Prerequisites for Database Mirroring:-
1. Make
sure that both principal server and mirror server are running on the
same edition of Microsoft SQL Server 2005 or 2008. The partners require
either Standard Edition or Enterprise Edition or Developer Edition.
2. If you are using a witness, make sure that SQL Server 2005 or 2008 is installed on its system. The witness can run on any edition either Standard Edition, or Enterprise Edition, or Workgroup Edition, or Developer Edition or Express Edition.
3. If you are configuring on SQL Server 2005 then SQL 2005 SP1 or later version is required for Mirroring.
4. The principal database must be in the FULL recovery mode.
5. All of the server instances in a mirroring session should use the same collation. Differences can cause a problem during mirroring setup.
6. The mirror database must have the same name as the principal database.
7. The mirror database must be initialized from a restore of the principal database with NO-RECOVERY, followed by restores in sequence of principal transaction log backups.
8. Prior to configuring mirroring ensure that at least one Tran log is restored in addition to full backup with NORECOVERY mode.
2. If you are using a witness, make sure that SQL Server 2005 or 2008 is installed on its system. The witness can run on any edition either Standard Edition, or Enterprise Edition, or Workgroup Edition, or Developer Edition or Express Edition.
3. If you are configuring on SQL Server 2005 then SQL 2005 SP1 or later version is required for Mirroring.
4. The principal database must be in the FULL recovery mode.
5. All of the server instances in a mirroring session should use the same collation. Differences can cause a problem during mirroring setup.
6. The mirror database must have the same name as the principal database.
7. The mirror database must be initialized from a restore of the principal database with NO-RECOVERY, followed by restores in sequence of principal transaction log backups.
8. Prior to configuring mirroring ensure that at least one Tran log is restored in addition to full backup with NORECOVERY mode.
No comments:
Post a Comment