Skip to main content


 

 

druva_logo.pngDruva
|
Documentation

How can we help you?

Trending articles:

 

Druva Documentation

Archiving and restoring an inSync Server 5.4.x on Linux (Embedded DB)

  1. Last updated
  2. Save as PDF
Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

Summary

The article describes how to archive and restore an inSync server running on Linux to an existing inSync server or a new server. This may be useful for tape archival or server/storage migration.

Archiving an inSync Server

 To archive an inSync server to Disk/Tape Media:

1. Stop the inSync Service using the command:

    # /etc/init.d/inSyncMasterAll stop

 2. Use the tar utility to backup the inSync server configuration and inSync storage folders.

Command for CentOS/Redhat/Fedora Core

 # tar -cf /path/to/new/tarball/insync-backup.tar /etc/inSyncCloud /var/log/inSyncCloud /<Path to storage base  folders for storage1> /<Path to storage base folders for storage2 (if you have any)>

Note: Storage base folders stands for Data, Database, and Database log folders for storage. You need to backup  all the folders.

Command for Ubuntu

 # tar -cf /path/to/new/tarball/insync-backup.tar /etc/inSyncCloud /var/log/inSyncCloud /<Path to storage base  folders for storage1> /<Path to storage base folders for storage2 (if you have any)>

Note: Storage base folders stands for Data, Database and Database log folders for storage. You need to backup  all the folders.

 Once the tar utility exits successfully, the backup is available as a single tar file. 

For MySQl Dump

  Map the library files, use the below commands:

 #export       LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib64:/lib:/opt/Druva/inSyncCloudServer/lib:/usr/lib64:/usr/lib:/opt/Druva/inSyncCloudServer/lib/inSyncServer

From command prompt run the following commands:

  #/opt/Druva/inSyncCloudServer/embeddedDB/bin/inSyncConfigDBServer --defaults-    file=/opt/Druva/inSyncCloudServer/embeddedDB/inSyncDB.cnf -- basedir=/opt/Druva/inSyncCloudServer/embeddedDB

From another command prompt run the following command: 

#/opt/Druva/inSyncCloudServer/embeddedDB/bin/inSyncConfigDBDump –h 127.0.0.1 –P6075 –uroot –pinSyncConfigDB > output.sql

Restoring the inSync Server

 The restore has two possible scenarios:

    a) Restoring data over existing, active setup.
    b) Rebuilding an inSync server from scratch.

 This is outlined in the next two sections.

Restoring on an existing inSync Server

 To restore the inSync server over an existing active server:

1. Stop the inSync Server service using this command.

    # /etc/init.d/inSyncMasterAll stop

2. Change path to ‘/’ and restore from the archive created earlier. Replace existing files if asked.

   #tar -xvpf /path/to/new/tarball/insync-backup.tar

For MySQL restore

Map the library files, use the below commands:

#export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib64:/lib:/opt/Druva/inSyncCloudServer/lib:/usr/lib64:/usr/lib

From command prompt run the following commands:

#/opt/Druva/inSyncCloudServer/embeddedDB/bin/inSyncConfigDBServer --defaults-file=/opt/Druva/inSyncCloudServer/embeddedDB/inSyncDB.cnf --basedir=/opt/Druva/inSyncCloudServer/embeddedDB

From another command prompt run the following command: 

#inSyncConfigDBClient –h 127.0.0.1 –P6075 –uroot –pinSyncConfigDB < output.sql

3. Start the inSync Server service with the following command:

   # /etx/init.d/inSyncMasterAll start

Restoring on a New Server

 To rebuild an inSync server from scratch:

1. Install the inSync Server.

2. Stop the inSync Server service.

   # /etc/init.d/inSyncMasterAll stop

3. Change path to ‘/’ and restore from an existing archive.

   #tar -xvpf /path/to/new/tarball/insync-backup.tar

For MySQL restore

Map the library files, use the below commands:

#export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib64:/lib:/opt/Druva/inSyncCloudServer/lib:/usr/lib64:/usr/lib

From command prompt run the following commands:

#/opt/Druva/inSyncCloudServer/embeddedDB/bin/inSyncConfigDBServer --defaults-file=/opt/Druva/inSyncCloudServer/embeddedDB/inSyncDB.cnf --basedir=/opt/Druva/inSyncCloudServer/embeddedDB

From another command prompt run the following command:

#inSyncConfigDBClient –h 127.0.0.1 –P6075 –uroot –pinSyncConfigDB < output.sql

4. Start the inSync Server service with the following command:

   # /etc/init.d/inSyncMasterAll start                                                                                                                                                                              

Post restoration tasks

 After restoring an inSync server, you need to re-install the license and re-configure the Published IP Address settings on the Web Control Panel. Once you open the configuration console you will be prompted for an invalid license. Click OK, and proceed.

The path to the License page on a 5.4.x severs GUI is: Server GUI -> Manage -> Settings -> inSync License

Install a new license provided by Druva support.

Setting the public IP addresses

In the inSync Server Web Console, change the Published IP/FQDN addresses to reflect the changed IP address of the new server (if any).

To set the Published IP Address:

1. Launch inSync Server Control Panel, click Manage > Settings > Network >Network settings section and Server IP/FQDN section.

2. Click Edit and enter the new IP address of the new server for both the fields.

3. Delete the old IP address.

Note: It is recommended to retain the IP address of the archived inSync Server by assigning the old static IP address to the new Server, because it will not require reissuing the key to all inSync clients.

If you want to provide the restored inSync Server with a new IP address, you need to notify the clients. You can do this by re-generating keys or resetting password for the users and asking users to re-authenticate.                      

Verifying the restore

 To verify a successful restore, try to sync the inSync client with the new inSync Server.