Forum Discussion
rafaelbn_176840
Altocumulus
AltocumulusViprion. Multiple blades and vCMP. Mirroring options.
Hello Devs!
I read on the oficial training guide that when you use vCMP, you do the mirroring on a guest basis. That makes sense to me.
But what if you have like a c2400 with 4x2150. Does the mir...
Hello rafaelbn,
If you configure Mirroring "within Cluster", it means that objects requiring mirroring (connection, persistence, apm, session tables, ...) will be synched between all blades configured for the Guest. This setting is for Mirroring only, it doesn't affect Sync and Failover features.
It means that in case of a crash of blade 1 (hardware failure), your guest will continue to run on blade 2, then blade 3, etc.
But be carreful, in case of a software failure (bug, memory leaks, ...), all blades can be affected. By experience, I recommand to run a Guest on 1 blade only and define a Sync/Failover cluster with another Guest on another Chassis.
Hope it helps
Yann
Yann_Desmarest
Cirrus
CirrusHello rafaelbn,
If you configure Mirroring "within Cluster", it means that objects requiring mirroring (connection, persistence, apm, session tables, ...) will be synched between all blades configured for the Guest. This setting is for Mirroring only, it doesn't affect Sync and Failover features.
It means that in case of a crash of blade 1 (hardware failure), your guest will continue to run on blade 2, then blade 3, etc.
But be carreful, in case of a software failure (bug, memory leaks, ...), all blades can be affected. By experience, I recommand to run a Guest on 1 blade only and define a Sync/Failover cluster with another Guest on another Chassis.
Hope it helps
Yann
rafaelbn
Cirrostratus
CirrostratusI just confirmed that vCMP guest will behave just like you described. I thought that vCMP guest were not affected by "sys db statemirror.clustermirroring". This is bad.