New answers tagged mirroring
If you are complying with all the RPO and RTO requierments by having database mirroring in place, with daily full backups then there are no data consistency issues with making backups to NUL. So the answer to your question is No. But (there is always a but) you are not having a secondary restore path if a full backup is corrupted and both the servers go ...
"Cannot alter database because database is not in the correct state to become the principal" 4 years later, but - This error occurs for two reasons: Database is not in Full safety mode. To fix: ALTER DATABASE dbname SET PARTNER SAFETY FULL Principal SQL DB can still be reached by SQL mirror, perhaps because the principal SQL instance is glitching but ...
Actually, I've solved it. The problem was with account for SQL Server in both server. I was using local account. Changed to domain-account, the same on both server, and everything worked
The answer is in the error - you will need to make sure that both servers i.e. the new db server and the witness can communicate using the certificate in question. There will be a certificate for each individual server and must exist on witness as well. So witness cert on the p/m servers and vice-versa
What you are telling is possible. Since you are running Standard Edition of SQL Server you have to bear following things : Standard edition supports mirroring ONLY in full safety mode. You have to be careful about number of databases your are configuring mirroring for, since it is recommended not to have more than 10 databases mirrored to secondary server. ...
Top 50 recent answers are included