Skip to main content

 

Druva Documentation

inSync log files, configuration files, and services

inSync log files

Location of log files

The location of the log files depends on the operating system on which you have installed the inSync Master or the inSync Storage Node. The following table lists the location of the log files.

Operating System Location of log files
Windows C:\ProgramData\Druva\inSyncCloud\logs
Linux /var/log/inSyncCloud

Log files

inSync log files are used to analyze and troubleshoot the issues that you might encounter with your inSync setup. For assistance in resolving your issues, you must share the log files with the Druva Support team.

The following table lists the different log files created on inSync Master and inSync Storage Nodes and the type of information they contain.

Log file name Available on Contains information about
CPortal.log inSync Master inSync Master Management Console activities
inSyncCloudServer.log inSync Master

Configuration changes to the inSync Master

User assignment details related to storage pools

Tasks started for user migration related to storage pools

inSyncSyncServer.log inSync Master

Backup and restore requests addressed by the inSync Master

Migration task logs or traceback in case of errors related to storage pools

Detail logs of fsck activity that run as part of the user migration related to storage pools

inSyncConfigDBDump.log inSync Master Dump of inSyncConfigDB from the embedded MySQL database. This log file is also part of the server diagnostics files.
inSyncStorageServer.log inSync Storage Node

inSync Storage Node activities

Migration task logs or traceback in case of errors related to storage pools

Detail logs of fsck activity that run as part of the user migration related to storage pools

inSyncMigration.log Remote inSync Storage Node, inSync Master, or Local Node Node Detail logs of data migration process related to storage pools

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.

inSync Master configuration files

The following table contains the details of the inSync Master configuration files:

Name Location Includes
inSyncCloudServer.cfg

Windows

  • C:\ProgramData\Druva\inSyncCloud

Linux

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

Windows

  •  C:\ProgramData\Druva\inSyncCloud\inSyncServer4

Linux

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

inSync Storage Node configuration files

The following table contains the details of the inSync Storage Node configuration files:

Name Location Includes
inSyncStorageServer.cfg

Windows

  • C:\ProgramData\Druva\inSyncCloud

Linux

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

Windows

  • C:\ProgramData\Druva\inSyncCloud\inSyncServer4

Linux

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

inSync services

inSync services on Windows

This following table contains the list of inSync Services when the inSync Master, inSync Storage Node, or inSync Edge Server is installed on a Windows server.

Service Name Associated with Description
Druva inSync Master Config Server inSync Master Manages the configuration changes to the inSync Master
Druva inSync Master Sync Server inSync Master Manages backup and restore requests
Druva inSync Master Control Panel inSync Master Manages inSync Master Management Console activities
Druva inSync Storage Node inSync Storage Node Manages activities on the inSync Storage Node
Druva inSync EdgeServer inSync Edge Server Manages activities on the inSync Edge Server

inSync Services on Linux

This following table contains the list of inSync Services when the inSync Master, inSync Storage Node, inSync client, or inSync Edge Server is installed on a Linux server.

Service Name Associated with Description
inSyncMasterAll inSync Master Manages all inSync services on the inSync Master
inSyncMonitorMasterSvc inSync Master Monitors inSyncCloudSrv and inSyncCPortal services
inSyncCloudSrv inSync Master Manages the configuration changes to the inSync Master and the backup and restore requests
inSyncCPortal inSync Master Manages inSync Master Management Console activities
inSyncStorageAll inSync Storage Node Manages all inSync services on the inSync Storage Node
inSyncMonitorStorageSvc inSync Storage Node Monitors inSyncStorageSrv service
inSyncStorageSrv inSync Storage Node Manages the inSync Storage Node
inSyncEdgeAll inSync Edge Server Manages all inSync services on the inSync Edge Server
inSyncMonitorEdgeSvc inSync Edge Server Monitors inSyncMonitorEdgeSrv service
inSyncEdgeSrv inSync Edge Server Manages the inSync Edge Server

Start and Stop inSync services

On Windows operating system, use the Services administrative tool to start and stop the required inSync service.

On Linux operating system, run the following command on the Terminal to start or stop the service:

/etc/init.d/[service] [start|stop]

For example, if you want to start the inSyncCloudSrv service, run the following command on the Terminal:

/etc/init.d/inSyncCloudSrv start

Similarly, if you want to stop the inSyncCPortal service, run the following command on the Terminal:

/etc/init.d/inSyncCPortal stop
Note: Stopping inSync services pauses all backup, restore, and sync operations.

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?