The article uses screenshots and examples to describes how to use Microsoft Ntbackup for inSync Server archival and restore. This may be useful for tape archival or server/storage migration.
Archival using NTBackup
Please follow the following steps (in exact given order)
- Stop “Druva inSync Server” service
- Stop “PostgreSQL Database” service
- Launch
NTBackup utility from Start > All Programs > Accessories>
System Tools > Backup. This will open up a window with options for
backup and restore (See Figure below)
4. Select Backup wizard (Advanced). This will launch a wizard. Click on next to proceed.
5. Select the option “Backup Selected Files, Drives or Network Data”. Click on next to proceed.
6. Select the items to be backed up -
- C:\inSynServer
- C:\Program Files\PostgreSQL\8.3\data
- The Base folders for the storages.
- Select the Backup Type (File/Tape), Destination and Backup Name. Click on next to proceed.
7. Click on Finish to start the Backup.
Restore Using NTBackup
The archived data can be restored to an existing setup or to an setup from scratch.
Restore on Existing inSync Server
Please follow the given steps to restore the inSync server archive on an existing active server -
- Stop “Druva inSync Server” service
- Stop “PostgreSQL Database” service
- Launch the NTBackup from Start > All Programs > Accessories> System Tools > Backup
- Select Restore wizard (Advanced). This will start the restore wizard.
5. Click on next to continue. Select
what to restore, which in our case would be the location of the backed
up file. Please click on "browse" to locate the file.
6. Select the folders to be restored by expanding the file tree in the left panel. Select the following folders to be restored -
- C:\inSynServer
- C:\Program Files\PostgreSQL\8.3\data
- The Base folders for the storages.

7. Click on "Next" to proceed.
8. Click on the “Advanced” button for selecting the restore parameters.
9. Select from the Drop down where you would like to restore the data. In our case please select “Original Location”.

10. Select “Replace Existing Files” from the list of options. This will overwrite the old files with new ones.

11. Please keep the default settings for next options.
12. Click on “Finish” to start the restore
Restore on a New Server
Please follow the given steps to rebuild a new inSync server using an existing archive -
- Install the latest version of Druva inSync Server
- Stop “Druva inSync Server” service
- Start the Restore process using the NTBackp utility (Please refer the Steps 3 to 11 for “Restore on Existing inSync Server” )
- Towards the end ignore the status “Completed with Skipped files". Click on close and proceed.
- Start “Druva inSync Server” service
- Open the Druva inSync Server configuration. This will display a license error. Click on “Ok” to proceed.
- Again
a warning related to PostgreSQL database server will be displayed as
the PostgreSQL is not installed yet. Click on “Ok” to proceed for
PostgreSQL installation.
- Uncheck
the “Create PostgreSQL Database cluster” and provide the password for
windows “postgres” user and “postgres” database user.
- This will start the PostgreSQL installation.
- Install the new license on the Druva inSync Server. (Contact Druva support for a new license).
- In the configuration console, change the “Published IP addresses” under server settings to reflect the changed IP address (if any).
- To notify the client about IP address change, either –
- Re-generate keys for the users and ask them to load the new key or
- Change the client configuration. Under the “Advance” Tab add the new server IP address and remove the old one.
To verify a successful restore, please try to sync the inSync client with the new inSync Server.