New answers tagged

0

Ideally the mirror db instance acts as the backup for the principal. So you already have a hot standby for the data in your principal in the form of the mirror dbs You cannot take backups of the Mirror databases as they are in restoring mode..obvious..ain't it? As of Principal, you can take continue to take your full backups.


3

No, you still need to take backups including FULLs and LOGs (DIFFs work too, just depends on your set up). Make sure you are taking LOG backups as well, or your log file will get full and things go breaky. All mirroring does, depending on what mode (async or sync), is keep data in sync between your primary and secondary. Synchronous means the ...


3

But now it needs upgrade to 2012 I would suggest you to go with SQL Server 2014, unless you have a compelling reason to stick with SQL Server 2012. AlwaysON is getting a lot of fixes back ported from SQL Server 2016. we like to do AlwaysON but its mirroring behind AlwaysON so will it work or is there any other way ? This is not true. The ...


1

So it seems that the issue was actually related to certificates. Once the certificate was backed up and shared to the mirrored server, everything worked as intended. I just wanted to swing back around and let those who were reaching out to help know where I landed.


3

As detailed in this MSDN document, the port number must be unique within any given computer: Note that if more than one server instance on a given computer requires a database mirroring endpoint, specify a different port number for each endpoint. TCP ports can only be served by a single process. When you try to create two endpoints with the same ...



Top 50 recent answers are included