We are testing a async volume replication with 2 open-e by stopping the replication task during the day and starting it up after working hours. This way we are able to create a disaster recovery for 1 of our customers.
(We will first disconnect al the iscsi targets before we start de replication task zo als the bocks of the iscsi target will not change during the replication.)
This works well. The only problem we do not get enough logging from the open-e's the only logging we get back is a mail when the job started and when it ended.
See below.
Our source send us the following mails the moment we start the replication task:
2012/06/15 20:00:16 Replication:Volume Replication: Device lv0004: Connection (from StandAlone to WFConnection).
2012/06/15 20:01:02 Replication:Volume Replication: Device lv0004: Connection (from WFConnection to SyncSource). Mode local/remote (from Primary/Unknown to Primary/Secondary). DataStatus local/remote (from Consistent/DUnknown to Consistent/Inconsistent).
Our destination sends us the following mails the moment the job started:
2012/06/15 19:57:39 Replication:Volume Replication: Device lv0100: Connection (from WFConnection to WFBitMapT). Mode local/remote (from Secondary/Unknown to Secondary/Primary). DataStatus local/remote (from Consistent/DUnknown to Outdated/Consistent).
2012/06/15 19:58:17 Replication:Volume Replication: Device lv0100: Connection (from WFBitMapT to SyncTarget). DataStatus local/remote (from Outdated/Consistent to Inconsistent/Consistent).
Around: 2012/06/15 14:00:00 the destination had become consistent but we didn't receive a message of this.
When the task is stopped we got following message in our mail:
Source:
2012/06/16 20:00:15 Replication:Volume Replication: Device lv0004: Connection (from SyncSource to StandAlone). Mode local/remote (from Primary/Secondary to Primary/Unknown). DataStatus local/remote (from Consistent/Inconsistent to Consistent/DUnknown).
Destination:
2012/06/16 19:57:28 Replication:Volume Replication: Device lv0100: Connection (from SyncTarget to WFConnection). Mode local/remote (from Secondary/Primary to Secondary/Unknown). DataStatus local/remote (from Inconsistent/Consistent to Consistent/DUnknown).
I know there are lines in syslog.log which show the task is complete in x seconds with an average speed of x kb/s.
Questions:
1. Is it possible to setup a syslog server where open-e will send its logs?
2. Is it possible to let open-e send a email on the change from inconsistent to consistent for volume replication tasks?
Logging
Reply With Quote