EVA CA question

[Chetan_5]

During failover testing for our Metrocluster, we saw a full copy had been triggered. Any idea what conditions triggered it?

We have seen this a couple of times so far ..

[IBaltay]

Hi,
a) is it the XP, EVA or EMC DMX-4 Metrocluster pls?
b) are you using the synchronous or assynchronous mirroring?
c) what OS are you running?
d) are you using the HP-UX Service Guard?
etc.

[IBaltay]

I have mised that it is the EVA Metrocluster, but all other questions are valid :-)

[Víctor Cespón]

Most common reasons for a full copy to be launched:

- The DR link has been down or suspended long enough so that the local log disk has been filled
- The source EVA has run out of space on the diskgroup where the log file is, so it cannot grow more.

[IBaltay]

Some additional details regarding the ASYNC replication mode:
a) If an unplanned site failover occurs and the DR group is in ASYNC mode, the DR group is put in SYNC mode and a full copy is created. The replication mode returns to ASYNC once the full copy completes.

b) When performing a planned site failover, you must put DR groups in SYNC mode before performing the actual failover activity. Omitting this mode change before performing the site failover results in performing an unplanned site failover (and the resulting full copy). Once the site failover has finished, you can change the replication mode to ASYNC mode again.