Unsolved
This post is more than 5 years old
2 Posts
0
1001
September 6th, 2012 06:00
Any known issues with RecoverPoint and Microsoft SQL Server
We just recently started using RecoverPoint to replicate our data from our local data center to a remote data center for disaster recovery purposes. Last week we performed a test in which a couple of our SQL Server 2005 databases failed the recovery process at the remote site and were put in suspect mode. Looking at the sql server log it indicated the crash recovery on these databases failed with the message "Could not redo log record". We also performed DBCC's on several other databases and noticed several table errors. We performed the DBCC's on the same databases locally and these errors didn't exist. Has anyone encountered anything like this before? Could we possibly have something configured incorrectly within RecoverPoint? I don't have many details about our RecoverPoint setup/configuration because I'm not in the group responsible for it. Any info or help would be appreciated.
0 events found
etaljic81
1K Posts
0
September 6th, 2012 07:00
I never ran into this issue and have failed over SQL with RecoverPoint many times. Can you ask the people in charge of RecoverPoint how the SQL consistency group is set up? Are the SQL databases and logs located in the same consistency group for that particular SQL server you are trying to failover?
etaljic81
1K Posts
0
September 6th, 2012 07:00
I'm not a SQL expert by any means so I don't know what the suspect mode really does. Maybe someone with better SQL experience can comment on this as well.
speja01
2 Posts
0
September 6th, 2012 07:00
Thanks Ernes! I'm following up with the appropriate group to check on the consistency groups. This was our second attempt at failing over SQL using recoverpoint. The first one was successful without any databases being left in suspect mode. As far as the table errors go though, we didn't perform any DBCC's during the first test so I'm not sure if they existed or not.