Skip to main content

 

Druva Documentation

inSync Log and Configuration Files

Overview

The inSync Server log files contain details of requests to the inSync server. You can use these log files to analyze and troubleshoot issues that you might encounter when the inSync server does not behave as expected.

Note: If you need assistance with resolving your issues, share these log files with the Druva Support team.

inSync Log files

The following table contains the details of the master server log files:

Name Location Includes
CPortal.log

Windows

  • C:\inSyncCloud\logs
  • C:\inSyncCloud\logs\inSyncCloudServer.log
  • C:\inSyncCloud\logs\inSyncSyncServer.log
  • C:\inSyncCloud\inSyncServer4\inSyncSharePanel.log

Linux

  • /var/log/inSyncCloud
inSync Admin Console activities. This file is generated by the inSync master control panel service.
inSyncCloudServer.log

Windows

  • C:\inSyncCloud\logs

Linux

  • /var/log/inSyncCloud
Configuration changes to master server. This file is generated by the inSync Master Config service.
inSyncSyncServer.log

Window

  • C:\inSyncCloud\logs

Linux

  • /var/log/inSyncCloud
Backup and restore requests addressed by master server. This file is generated by the inSync Master Sync service.
inSyncSharePanel.log

Windows

  • C:\inSyncCloud\inSyncServer4

Linux

  • /var/log/inSyncCloud
Share activities of inSync users when port 443 is used for accessing inSync Web.

The inSyncStorageServer.log file, created on each storage node, contains information about storage node activities. On Windows, the file is present at C:\inSyncCloud\logs. On Linux, it is present at var/log/inSyncCloud (Linux). This file is generated by the inSync Storage Node service.

Note:  (Ubuntu) inSync Monitor Master Service and inSync Monitor Storage Service write entries to the syslog file. (RHEL) inSync Monitor Master Service and inSync Monitor Storage Service write entries to the messages file.

inSync Configuration files

Note: Druva recommends not modifying the configuration files except when required. In scenarios where you must modify these configuration files, should you need assistance, contact the Druva Support team.​Druva recommends 

The following table contains the details of the master server configuration files:

Name Location Includes
inSyncCloudServer.cfg

Windows

  • C:\inSyncCloud

Linux

  • /etc/inSyncCloud
MySQL configuration details.
inSyncServer.cfg

Windows

  •  C:\inSyncCloud\inSyncServer4

Linux

  • /etc/inSyncCloud/inSyncServer
SMTP settings, ports and server IP lists.

The following table contains the details of the storage node configuration files:

Name Location Includes
inSyncStorageServer.cfg

Windows

  • C:\inSyncCloud

Linux

  • /etc/inSyncCloud
Node authorization key details.
inSyncServerStorage.cfg

Windows

  • C:\inSyncCloud\inSyncServer4

Linux

  • /etc/inSyncCloud/inSyncServer
 Web restore port, synchronization port, and so on.

inSync Services

Note: Stopping the inSync Services pauses all synchronization and restore operations.

inSync Services for Windows

This following table contains inSync Services that run on a Windows computer.

Name Associated with Description
Druva inSync Master Config Server master server inSync Master config service
Druva inSync Master Sync Server master server  inSync Master sync service
Druva inSync Master Control Panel master server inSync Master Control Panel service
Druva inSync Client Service master server Manages backups to Master Server
Druva inSync Storage Node storage nodes inSync Storage Node service

inSync Services for Linux

This following table contains inSync Services that run on a Linux computer.

Name Location Description
inSyncMasterAll

Master server

/etc/init.d/inSyncMasterAll 

To run this service, run the following command:

/etc/init.d/inSyncMasterAll
[inSyncCloudSrv|inSyncCPortal|inSyncMonitorMasterSvc]
Manages all Master Server services.
inSyncMonitorMasterSvc

Master server

/etc/init/inSyncMonitorMasterSvc.conf

The Linux operating system runs inSyncMonitorMasterSvc as a service.

Monitors the inSyncCloudSrv and the inSyncCPortal services.
inSyncCloudSrv

Master server

/etc/init.d/inSyncCloudSrv 

Controls the Config Server and Sync Server processes.
inSyncCPortal

Master server

/etc/init.d/inSyncCPortal

Controls the inSync Master Control Panel.
inSyncStorageAll

Storage server

/etc/init.d/inStorageAll

To run this service, run the following command:

/etc/init.d/inSyncMasterAll
[inSyncStorageSrv|inSyncMonitorStorageSvc]
Manages all Storage Node services.
inSyncMonitorStorageSvc

Storage node

/etc/init/inSyncMonitorStorageSvc.conf

The Linux operating system runs inSyncMonitorStorageSvc as a service.

Monitors the inSyncStorageSrv services.
inSyncStorageSrv

Storage node

/etc/init.d/inSyncStorageSrv

Controls the storage node.

Notes

  • The inSyncMonitorMasterSvc service acts like a "watchdog" for master server installed on Linux (Ubuntu and RHEL). It ensures that inSyncCloudSrv and inSyncCPortal services are always running. The inSyncMonitorMasterSvc checks the status of inSyncCloudSrv and inSyncCPortal every minute. If either one of these services is not running, inSyncMonitorMasterSvc starts the service and writes an entry to syslog (Ubuntu) or the messages (RHEL) file.
  • The inSyncMonitorStorageSvc service acts like a "watchdog" for storage nodes installed on Linux (Ubuntu and RHEL). It ensures that inSyncStorageSrv is always running. The inSyncMonitorStorageSvc runs a check on inSyncStorageSrv every minute. If this service is not running, inSyncmonitorSvc starts the service and writes an entry to syslog (Ubuntu) or the messages (RHEL) file.
  • If you stop inSyncCloudSrv or inSyncCPortal manually, inSyncMonitorMasterSvc cannot start the service. You must start the service manually.
  • If you stop the inSyncStorageSrv manually, inSyncMonitorStorageSvc cannot start the service. You must start the service manually.
  • Was this article helpful?