Hi,
let me first start by saying that I'm not a SQL DBA, I work in infrastructure and am assisting a DBA build a SQL 2012 cluster plus cold stand-by DR.
The configuration that we are building consists of a two node active-active cluster using SAN attached shared disks in our primary site. Currently our SAN has the capability to replicate to another SAN in another city (secondary site), we will be leveraging this to replicate the database and logs (not backup files). At the secondary site I'd like to build a SQL server which houses some active production databases, in the event of a disaster at the primary site I'd like to present the LUNs to this server and start the databases.
As you can tell RPO and RTO aren't important, we just need to know that it will work and possibly prove it once. I know that I can create an AlwaysOn availability group to replicate the DB to the secondary site or even use log shipping or SQL mirroring but due to license and administrative overhead we will not be using these approaches. We also rely on SAN replication for other DR aspects so the architect would like to keep this consistent.
The questions I have are:
Is this possible?
Do I need to create/install the instances first as empty DB's then simply switch out the disks for DR?
I'd prefer to just simply attach the disk and start the DB's rather than restore from backup.
If someone could point me in the direction of an article or provide some dot points that would be great.
Thanks
let me first start by saying that I'm not a SQL DBA, I work in infrastructure and am assisting a DBA build a SQL 2012 cluster plus cold stand-by DR.
The configuration that we are building consists of a two node active-active cluster using SAN attached shared disks in our primary site. Currently our SAN has the capability to replicate to another SAN in another city (secondary site), we will be leveraging this to replicate the database and logs (not backup files). At the secondary site I'd like to build a SQL server which houses some active production databases, in the event of a disaster at the primary site I'd like to present the LUNs to this server and start the databases.
As you can tell RPO and RTO aren't important, we just need to know that it will work and possibly prove it once. I know that I can create an AlwaysOn availability group to replicate the DB to the secondary site or even use log shipping or SQL mirroring but due to license and administrative overhead we will not be using these approaches. We also rely on SAN replication for other DR aspects so the architect would like to keep this consistent.
The questions I have are:
Is this possible?
Do I need to create/install the instances first as empty DB's then simply switch out the disks for DR?
I'd prefer to just simply attach the disk and start the DB's rather than restore from backup.
If someone could point me in the direction of an article or provide some dot points that would be great.
Thanks