Configuring inSync for Linux

Configuring inSync for Linux

In this post I walk through the nuances of running the Linux version of Druvaa inSync client as well as server.

The Linux release is finally here and is aimed at most Linux platforms that use the Debian or Redhat package managers. We provide generic .deb and .rpm packages. This, being the first release for Linux, should be considered beta. The packages we release should work on most Linux distributions that came out in the last 2-2.5 years. A 64-bit port of the server as well as the client for both Linux and Windows is already in the pipeline.

So far, Linux has been lacking a good backup mechanism. Especially one aimed at client desktop machines. Many shops are now multi-platform with Windows, Mac and Linux desktops as well as laptops. Most backup systems are either too complicated to use or don’t provide multi-platform support. With support for Linux, we hope to help organizations make the transition to an enterprise-class backup mechanism that works for Windows as well as Linux.

The Linux client works exactly as the Windows counterpart. So I suggest, please [watch the installation demo] first. This post will discuss only the parts of the configuration/management process different from the windows counterpart.

So let’s look at the server first. I ‘m using a Ubuntu 8.10 box.

Install inSync Linux Server

root@snowflake:i386# dpkg -i druvaa-insync-server-ver-2.2.1-beta2.deb Selecting previously deselected package druvaa-insync-server (Reading database … 160747 files and directories currently installed.) Unpacking druvaa-insync-server (from druvaa-insync-server-ver-2.2.1-beta2.deb) … Setting up druvaa-insync-server (2.2.1-1079) … Starting Druvaa inSync Server: Daemonizing …

Run and Configure inSync

root@snowflake:~# inSyncSrvCfg

This will open the server configuration GUI just like windows:

 Configuration Console

Storage Configuration

With Linux version, the PostgreSQL 8.3 needs to be manually installed. Before creating the first encrypted SIS, install the postgres package and run the following command –

root@snowflake:i386# /usr/sbin/ No insyncserver user found in postgresql. Creating a new account with the username ‘insyncserver’ Please enter a password for this account. Enter a password: Re-enter the password: CREATE ROLE Created a postgres user for inSync Server. ******************************************************************************** When configuring a SIS storage, please use ‘insyncserver’ as the username and use the password you just entered here as the password. ******************************************************************************** Using [/etc/postgresql/8.3/main/pg_hba.conf] as the postgres host-based-authentication configuration file. Is this correct ? (Y/n) y .. <snip> .. PostgreSQL configured. Now you can go ahead and configure SIS storages as needed

Now, attempt to create the new store:

 Storage configuration

Once the storage is configured, please configure profile and add backup users.

Druvaa inSync Client

The client is no different from the windows version. Install the RPM or the DEB package, and the client would get loaded in the system tray:  inSync in System Tray Click on the icon to launch the management screen:

 Main Screen

Start the configuration by loading the authentication key, configure folders and start your first backup.

Backup Status

Differences with Windows version

The only major difference being the shadow-copy on Windows which is needed to backup locked files. On Linux, as long as you have permissions to read a file, you can back it up.

One thing you need to watch out for is if you sync up your entire home directory, you might need to set file permissions specifically for certain files when you restore, as inSync currently doesn’t store file modes. Files are restored using the current “umask“.


Jaspreet Singh

Jaspreet bootstrapped the company while defining the product, sales and marketing strategies that have resulted in Druva's early and impressive success. Prior to founding Druva, Jaspreet was a member of the storage foundation group at Veritas.