Question on How to plan disaster in SQL Server.

I have Server A primary Server(with 20 databases,Logins, Jobs,Alerts,DBmail)where all client applications connect to A. Server B act as Mirrored(all dbs in restoring Mode) with no witness(Manual Fail over) also Replication set up From Server A to Server C(subscriber).

My question is:
Should Server B have same Logins, Jobs,Alerts,DBmail and replication setup (from B to C)correct? so that when Server A goes down i manually fail over all DBS to B and B should be up and running and client connect to B and B serve applications ...

Please provide your thoughts on how u plan DR..

Thanks

yes you need same logins, replication jobs on the server B.

when server A goes down your server B will become primary and able to continue.

• Marked as answer by coolguy123SQL 15 hours 38 minutes ago

Question on How to plan disaster in SQL Server.

I have Server A primary Server(with 20 databases,Logins, Jobs,Alerts,DBmail)where all client applications connect to A. Server B act as Mirrored(all dbs in restoring Mode) with no witness(Manual Fail over) also Replication set up From Server A to Server C(subscriber).

My question is:
Should Server B have same Logins, Jobs,Alerts,DBmail and replication setup (from B to C)correct? so that when Server A goes down i manually fail over all DBS to B and B should be up and running and client connect to B and B serve applications ...

Please provide your thoughts on how u plan DR..

Thanks

I agree with Kumar; but, I'd sooner look at the big picture. Manual failover in a disaster can be a disaster. What if the people responsible for failover cannot be reached? How long will you be down?

Depending on the version of server you are running, you may want to consider using Database Mirroring, which is deprecated but still in SQL 2016 and probably in SQL 2018 since 2016 does not currently throw final support warnings.

If you're running Enterprise Edition with 2012 or later then Availability Groups would be a great option.

Both of these technologies offer automatic failover and there is less to keep in sync.

Please note mirroring is database level DR its not server level so yes as you suggested server B should have same login as server A. Consider a scenario where login A exists on server A and not on Server B and this login is used by application to connect or may be a job to perform some operation. Now when failover happens to B the application/job would start failing out.

Thanks Kumar

Thanks Daniel

Thanks Shanky