DataKeeper for Windows All Documentation - SIOS

Inability to Create a Mirror• Source = ExtMirrSvc – events related to the DataKeeper service.• Source = SteelEye.SDRSnapIn – events related to the DataKeeper GUI connecting to the DataKeepersystems.System Event Log:• Source = ExtMirr – events directly related to mirror creation, mirror manipulation and replication.Note: The System Event Log should always be set to "Overwrite events as needed." If the System EventLog fills up or becomes corrupted, it will prevent DataKeeper from properly recognizing mirror state changes.Inability to Create a MirrorQuestionWhy can't I create a mirror?Answer• The common cause of this problem is that the volume on either source or target is in use by anotherprocess. Stop the process that is accessing the volume and try again. The SteelEye DataKeepersoftware requires exclusive access to the target volume during the creation of the mirror.• The target volume must be as large, or larger, than the source volume. It is recommended that the usercompare the target volume size with the source volume size using the Disk Management utility. If thesizes are not the same, recreate the target partition a little larger. See Volume Considerations for moreinformation.• An error experienced during Create Mirror could indicate that the target volume is corrupt. If this occurs,format the target volume and attempt to create the mirror again.Network DisconnectScenario #1In a 2-Node, non-clustering configuration (1x1) replicating a 100TB volume between Source server and Targetserver over a WAN connection, the network goes down for twenty minutes.QuestionIn this scenario, what would happen to the Mirror State with DataKeeper Standard Edition?AnswerAfter a couple of minutes, the Source server will detect that the network is down and the mirror will go from theMIRRORING state to the PAUSED state.QuestionDataKeeper for Windows Technical DocumentationPage 156