Troubleshooting : Collecting Zerto Virtual Replication Logs : Understanding the Logs
  
Understanding the Logs
 
If problems arise with Zerto Virtual Manager, you can view the Zerto Virtual Manager logs to see what is happening.
The current log is called logfile.csv and resides in the <Zerto_Install_Dir>\Zerto Virtual Replication\logs folder, where Zerto_Install_Dir is the folder specified during the installation.
When the log reaches 10MB its name is changed to log.nnnn.csv, where nnnn is a number incremented by one each time logfile.csv reaches 10MB. Up to 150 log files are kept.
The log file has the following format:
FFFF, yyyy-mm-dd hh:mm:ss, ####, LVL, Component, API, Message
where:
FFFF: A HEX code. For internal use.
yyyy-mm-dd hh:mm:ss: Timestamp for the message.
####: Number for internal use.
LVL: Severity level of the message. The more messages written to the log the bigger the impact on performance. The number of messages written to the log decreases from Debug to Error. The level can be one of the following:
Debug: All messages are written to the log. This level should only be specified during testing.
Info: Information messages.
Warn: Warning messages such as a reconnect ion occurred.
Error: Error messages that need handling to find the problem.
Component: The specific part in the Zerto Virtual Manager that issued the message.
API: The specific API that issued the message.
Message: The message written in the log.
The following is a sample from a log:
07f4c878,2010-12-01 19:54:41.4237,Debug,5,
Zerto.Zvm.RemoteZvmConnector.ResyncingRemoteZvmConnector,
TestConnectivity,TestConnectivity returning true,
07f4c878,2010-12-01 19:54:41.7362,Info,11,
Zerto.Zvm.ZvmServices.Protection.PromotionMonitor,
PromotionMonitoringThreadFunc,Promoting protection groups: ,
07f4c878,2010-12-01 19:54:42.7987,Info,9,
Zerto.Infra.ZvmReaderWriterLock,LogLock,Synchronizer: Enter Writer,
07f4c878,2010-12-01 19:54:42.7987,Info,9,
Zerto.Zvm.ZvmServices.ReconnectingConnectorProxy,
GetConnector,"Connecting IP=106.16.223.86, PORT=4005, attempt (1/3)",
07f4c878,2010-12-01 19:54:42.7987,Debug,9,
Zerto.Zvm.VraConnector.VraNetworkConnector,
Connect,try to connect 106.16.223.86:4005 ...,
07f4c878,2010-12-01 19:54:43.0643,Debug,17,
Zerto.Zvm.ZvmServices.CrossSiteService,Ping,Ping,
07f4c878,2010-12-01 19:54:43.0643,Debug,17,
Zerto.Zvm.ZvmServices.PingService,Ping,Ping called,
07f4c878,2010-12-01 19:54:43.8612,Error,9,
Zerto.Zvm.VraConnector.VraNetworkConnector,
ClearAndThrow,connection is closed: No connection could be made because the target machine actively refused it 106.16.223.86:4005,
07f4c878,2010-12-01 19:54:43.8612,Warn,9,
Zerto.Zvm.ZvmServices.ReconnectingConnectorProxy,GetConnector,failed,