LOCAL Contiuous Replication 1

[Zegrounded]

I want to find out the benefits of turning on LOCAL Continuous Replication (LCR). Microsoft recommends LCR is turned on as minimum redundancy protection for the store database(s). My question is how much overhead does this create on server performance and does turning on LCR give a status indicator on the health of the database(s)?

 

[58sniper]

You have to be able to support twice the storage an IO as without LCR. You are essentially creating a replica of the databases, and keeping them up to date at the same time as the production databases. Thus, if you have a nice SAN for your production databases and logs, figure on another for the LCR copies.

LCR doesn't really give a status of the DB. It's a backup solution for database issues. LCR and SCR are traditionally manual failover technologies.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Zegrounded]

Thank you 58sniper for your speedy response the bit i am trying to get my head round is the 'copy status' column on the store's window - does this indicate that the copy status is healthy, or does it indicate that the database is 'healthy' - what would constitute a corrupt database? I want to know if I turn LCR on is there an indicator to tell me that my production database is becoming corrupt or not?

 

[58sniper]

Your users will tell you when you have database issues. The status in EMC is for the copy status.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/