Skip to main content
Druva Documentation

How to migrate Linux-based On-Premise Druva inSync Server

This article applies to:

  • OS: CentOS Server 6.6, 6.7, 6.8, 7.0, 7.1 (64-bit) , Ubuntu Server 12.04, 14.04 (64-bit), RHEL Server 6.6, 7.1
  • Product edition: inSync On-Premise 5.8 and later
  • Feature Category: Installing and configuring  Druva inSync Master server


This article describes how to migrate Linux-based On-Premise Druva inSync Server.

Prerequisites for migration

  • Check the  OS and Kernel logs and message, storage issues, all the active alerts, and the health of the current Linux-based Druve inSync server.
  • Resolve any hardware issues, OS-related errors, and storage corruption if detected on the server.
  • Verify whether the current hardware can support Druva inSync upgrade and can be upgraded to at least inSync 5.8.3 version and above before performing the migration. 
  • Ensure the storage is healthy and keep a record of the data, DB, DB log folder location of the current storage.
  • Keep ports 6061 and 443 open on the new (target) server.
  • Check the network accessibility between the new server and the storage node server if additional storage nodes are configured.
  • Ensure the disk partitions on the new server are same as that on the old server.
  • Verify whether the Hardware and Software prerequisites, port and network settings meet Druva recommendations on the new server. See Prerequisites to install inSync Master for more information.
  • If the IP address of the inSync server changes, update the new IP address in the existing setup and allow backups to complete from all the devices. (See Manage IP address or FQDN of inSync Master)


  • Stop/disable Druva inSync services and storage nodes (if any) on the old server until the old server is disposed off or removed from the network.  This will prevent changes to Druva configuration files and folder before the migration completes and the new server becomes active.
  • Enable the firewall to prevent the inSync Client from connecting to the new server before all the configuration is complete and network settings are restored on the new server. Communication with the new server from inSync Client must be blocked until the activity is complete.

Migrate the server

Stop all Druva services on old inSync Druva server and make sure no inSync related process is running by below commands. If any inSync process is still running, manually stop it using kill command.

Step 1: Stop all inSync services on the old Druva inSync server

  1. Check the current status of Druva inSync services.

    systemctl status inSyncMasterAll  or /etc/init.d/inSyncMasterAll status

  2. Stop all inSync related processes with the following command. 

    systemctl stop inSyncMasterAll or /etc/init.d/inSyncMasterAll stop
  3. Recheck the status of Druva inSync services

    systemctl status inSyncMasterAll  or /etc/init.d/inSyncMasterAll status

  4. Check if any background process is still running and verify if the output is same as the image below.

    ps-ef  | grep -i insync

  5. Kill any inSync process forcefully if required.

    kill -9 <pid>



Step 2: Copy Druva inSync folders and install inSync Master

When the new server is ready with OS installation and IP address/FQDN:

  1. Copy the following Druva inSync folders to the new server.  The folder paths on the new server must be exactly same as that on the old server. Even the disk partitions on the new server must be the same as that on the old server.
    • Configuration Folder : /etc/inSyncCloud
    • Local Storage Folders:  Data, DB, DBLogs 
    • Logs Folder: /var/log/inSyncCloud
      Example: If the data path of the inSyncStorage folder on the old server was /Disk1/inSyncStorage,  then the path on the new server must also be /Disk1/inSyncStorage.
      Tip: The size of /Disk1 on the new server can be more than that of the old partition.
  2. On the new server, rename /etc/inSyncCloud and  /var/log/inSyncCloud to /etc/inSyncCloud_old and /var/log/inSyncCloud_old respectively with the following commands:
     mv /var/log/inSyncCloud /var/log/inSyncCloud_old
     mv /etc/inSyncCloud /etc/inSyncCloud_old
  3. Download inSync Master Server setup of the same version as installed in old server. See Download links for more information or contact Druva Support for the appropriate download link.
  4. Install the inSync Master on the new server. See Install inSync Master on Linux for more information.


Step 3: Stop Druva inSync processes on the new server and rename the inSync folders

Once inSync Master is installed:

  1. Use the commands described in Step 1 to stop all the Druva inSync services on the new server. 
  2. Verify all the inSync services are stopped and rename the following folders as described in the commands below:
    Folder name Rename to Command
    /etc/inSyncCloud /etc/inSyncCloud_new mv /etc/inSyncCloud /etc/inSyncCloud_new 
    /etc/inSyncCloud_old /etc/inSyncCloud mv /etc/inSyncCloud_old /etc/inSyncCloud
    /var/log/inSyncCloud /var/log/inSyncCloud_new mv /var/log/inSyncCloud /var/log/inSyncCloud_new
    /var/log/inSyncCloud_old /var/log/inSyncCloud mv /var/log/inSyncCloud_old /var/log/inSyncCloud


Step 4: Change the owner of Druva inSync folders and assign appropriate permissions

Change the owner of the configuration files, logs, and all storage directories to insyncserver and provide appropriate permissions to the owner.

chown -R insyncserver:insyncserver /etc/inSyncCloud

chown -R insyncserver:insyncserver /var/log/inSyncCloud
chown -R insyncserver:insyncserver <Storage Data directory path>
chown -R insyncserver:insyncserver <Storage DB directory path>

chown -R insyncserver:insyncserver <Storage DBlogs directory path>

chmod -R 764 /etc/inSyncCloud

chmod -R 764 /var/log/inSyncCloud
chmod -R 764 <Storage Data directory path>
chmod -R 764 <Storage DB directory path>

chmod -R 764 <Storage DBlogs directory path>


Step 5: Start Druva inSync services on the new server

  1. Start the Druva inSync services on the new server and verify their status.

    systemctl start inSyncMasterAll or /etc/init.d/inSyncMasterAll start
    systemctl status inSyncMasterAll or /etc/init.d/inSyncMasterAll status
  2. Verify that Firewall is disabled to allows inSync Client to communicate with the new inSync Master.

  3. Use inSync Administrator credentials to login to the inSync Management Console and verify the inSync setup. See Log on to inSync Master Management Console for more information. 
  4. Delete /etc/inSyncCloud_new and /var/log/inSyncCloud_new with the following commands.

    rm -rf /etc/inSyncCloud_new
    rm -rf /var/log/inSyncCloud_new