Unsolved
This post is more than 5 years old
15 Posts
0
433
SQL2005 and not replicating the SQL Temp Logs via RecoverPoint
This is the scenario:
We have two CX380's for local replication "CDP" along with one CX4 at a remote site making "CLR" replicating all SQL Database information except for SQL Temp Logs. Each Cluster has its own Consistency Group sending all data from local CX3's and then to the CX4.
The question I have is since now we took the SQL Temp Logs out of RecoverPoint replication what is the best way to get these logs over to the Second CX3 "Local One Only" if there was a failure of the Primary CX? Since RecoverPoint can recover the database LUNS, but it knows nothing of the SQL Temp Logs how do we get those blocks and signatures over to the Second CX to be able to bring the entire SQL environment up with no issues?
I thought about getting a hold of either MirrorView or SanCopy to at least replicate the SQL Temp Logs without the need of RecoverPoint or is the best to create additional Consistency Groups "Local Only" for the SQL temp Logs, so this way the signatures will be on both CX3's?
Any help would be appreciated.
Thanks
Freddie @Clean Harbors
We have two CX380's for local replication "CDP" along with one CX4 at a remote site making "CLR" replicating all SQL Database information except for SQL Temp Logs. Each Cluster has its own Consistency Group sending all data from local CX3's and then to the CX4.
The question I have is since now we took the SQL Temp Logs out of RecoverPoint replication what is the best way to get these logs over to the Second CX3 "Local One Only" if there was a failure of the Primary CX? Since RecoverPoint can recover the database LUNS, but it knows nothing of the SQL Temp Logs how do we get those blocks and signatures over to the Second CX to be able to bring the entire SQL environment up with no issues?
I thought about getting a hold of either MirrorView or SanCopy to at least replicate the SQL Temp Logs without the need of RecoverPoint or is the best to create additional Consistency Groups "Local Only" for the SQL temp Logs, so this way the signatures will be on both CX3's?
Any help would be appreciated.
Thanks
Freddie @Clean Harbors