Druva inSync Storage Migration

From inSync 3.1 to inSync 4.1

Technical Guide

www.druva.com

Druva inSync Storage Migration Technical Guide

Copyright Notice Copyright 2007-2011 Druva Software Pvt. Ltd. All Rights Reserved. Any technical documentation that is made available by Druva Software is the copyrighted work of Druva Software and is owned by Druva Software. NO WARRANTY. The technical documentation is being delivered to you AS-IS, and Druva Software makes no warranty as to its accuracy or use. Any use of the technical documentation or the information contained therein is at the risk of the user. Documentation may include technical or other inaccuracies or typographical errors .Druva reserves the right to make changes without prior notice. No part of this publication may be copied without the express written permission of Druva Software. Trademarks Linux is a U.S. registered trademark of Linus Torvalds. Windows is a U.S. registered trademark of Microsoft Corporation. Other brands and product names mentioned in this manual may be trademarks or registered trademarks of their respective companies and are hereby acknowledged. DISCLAIMER The information contained in this document is subject to change without notice. Druva Software Pvt. Ltd. shall not be liable for errors contained in this document for any damages in connection with this document.

Page | 2

Druva inSync Storage Migration Technical Guide

Contents
Introduction........................................................................................................ 4
Overview.................................................................................................................................. 4 Prerequisites............................................................................................................................ 5 Before You Begin ..................................................................................................................... 6

Minimum Disk Space Requirement ..................................................................... 7

Data Disk Space ....................................................................................................................... 7 Database Disk Space................................................................................................................ 7 Log Disk Space ......................................................................................................................... 7

Step by Step Migration Procedure ...................................................................... 8

Storage Migration Procedure for Windows ........................................................................... 8 Storage Migration Procedure for Linux ................................................................................... 9 Monitoring the Storage Migration Progress ......................................................................... 10
For Windows........................................................................................................................... 10 For Linux ................................................................................................................................. 10

Verifying Successful Storage Migration................................................................................. 10

For Windows........................................................................................................................... 10 For Linux ................................................................................................................................. 10 Verify the following ................................................................................................................ 11

Dealing with NAS Data Folders .............................................................................................. 11

Installing inSync 4.1 .......................................................................................... 12

Installing the inSync Server 4.1 ............................................................................................. 12
For Windows .......................................................................................................................... 12 For Linux ................................................................................................................................ 12

Upgrading the Existing Clients to 4.1 .................................................................................... 12

Troubleshooting ............................................................................................... 14

Page | 3

Druva inSync Storage Migration Technical Guide

Introduction
This migration document describes the procedure of upgrading from inSync 3.1 to inSync 4.1. We offer a significant increase in performance and scalability in 4.1, which now uses an embedded, high-performance Oracle Berkeley DB for storing metadata. In order to benefit from the new performance and scalability in inSync 4.1, we require an upgrade from the old database to the new embedded database. As a rule of thumb, you should expect 24 hours for every 500GB of data that needs to be migrated but it is advisable to check the logs or time estimates while running the upgrade package. Before starting the storage migration process, read this document carefully. If you have any questions or queries, please contact Druva support.

Overview
This upgrade package is provided for the limited purpose of migrating storage from inSync 3.1 to 4.1. You will then need to install inSync 4.1 to achieve full functionality.

Install

inSync 4.0.4 upgrade package

Migrate

Storage

Install

inSync 4.1

Upgrade

inSync clients

Remember the following notes before starting the storage migration. You cannot install inSync 4.1 on top of 3.1. This has to be done by installing the upgrade package, migrating the storage, and then installing inSync 4.1. You cannot connect any clients or perform any backups when you install upgrade package. You need to install inSync 4.1 for working with inSync clients. During migration, inSync services are disabled by default. Make sure you do not enable the services until you finish the migration process.
Page | 4

Druva inSync Storage Migration Technical Guide

Prerequisites
Following are the minimum requirements for inSync server and client to go forward with the storage migration. If you have an older Druva inSync 3.1 packages then make sure to upgrade up to minimum requirements given below. inSync Server/Client (Windows) inSync Server

Release 3.1.2 r-2317 minimum 3.1.2 r-2338 3.1.2 r-2468 3.1.3 r-2536 3.1.3 r-2721 3.1.3 r-2932 3.1.3 r3166 3.1.3 r-3075 3.1.3 r-3395 3.1.3 r-3550 3.1.3 r-3816 3.1 r-2048 onwards

inSync Client inSync Server/Client (Linux) inSync Server

Release 3.1.3-r2243.deb 3.1.3-r2243.rpm 3.1.3-3554_i386.deb 3.1.3-3554.i386.rpm 3.1.3-3600_i386.deb 3.1.3-3600.i386.deb 3.1.1-r2243.deb 3.1.1-r2243.rpm

inSync Client

NOTE: This migration process is not applicable for plain storage in both Windows and Linux versions so do not upgrade if you want to continue with the plain storage. If you still want to migrate other than plain storages then first delete the plain storage and then proceed with the migration.

Page | 5

Druva inSync Storage Migration Technical Guide

Before You Begin

The storage migration process is defined in the following diagram. There are five main steps to be followed.

Page | 6

Druva inSync Storage Migration Technical Guide

Minimum Disk Space Requirement

Before starting the storage migration make sure that the inSync sever has enough disk space to perform the migration.

Data Disk Space

The upgrade package does optimal usage of available disk capacity. If a new storage uses the same volume to store data as old storage then only 10% (of existing data size) free disk space is required on the existing volume. If a new storage is going to use the different volume than the old storage, the new volume requires at least 110% free disk space of current data size. For example, if the Server has a single storage having Data folder size 100 GB on D drive then the free space on D drive should be 10 GB or total disk space should be at least 110 GB and for a new volume, it requires minimum 110 GB free disk space.

Database Disk Space

The database migration requires 20% free space of the existing data size (blocks + blobs). For example, if the existing data size is 200 GB in size, then storage migration needs minimum 40 GB free space irrespective of the drives it is going to migrate.

Log Disk Space

The storage related to log path requires minimum 4 GB free disk space. If the Data and Database paths are sharing the same volume then free space requirement adds up for the volume correspondingly.

Page | 7

Druva inSync Storage Migration Technical Guide

Step by Step Migration Procedure

Storage Migration Procedure for Windows
To migrate storage on an inSync server, follow the steps given below. 1. Archive the existing inSync Server, for more information; refer the Archival and Restore of InSync Server article in Druva Knowledge base. 2. Download the inSync Server 4.0 upgrade package from the Druva Website (www.druva.com/download) and install it. 3. Launch the storage migration utility from the Windows command prompt. This utility can be found in the inSync Server folder. For example, - in 32-bit Windows OS: C:\Program Files\Druva\inSync Server\inSyncMigrate.exe - in 64-bit Windows OS: C:\Program Files (x86)\Druva\inSync Server\inSyncMigrate.exe 4. Enter the details required to perform the storage migration. - Data path for new storage (default is same as old storage path). For more information see Dealing with NAS Data Folders in this document. - DB path for new storage (default is same as DB path of old storage) - Log path for new storage (default is same as old storage path) - DB cache size (default is 1024 MB maximum) 5. Verify the details. Repeat the 4th step for each storage. 6. The storage migration process starts. For information see Monitoring the Storage Migration Progress in the document. The following message is displayed after completing the migration process. Storage Migration Completed for Storages Press enter to exit 7. Migrated server can now be verified. See Verifying Successful Storage Migration in this document. 8. Install the inSync 4.1 server. See Installing inSync 4.1 for more information 9. In case of NAS storages, start the Druva inSync server and Druva inSync Server Control panel services as a NAS user. This user must have admin privileges and should be part of the Administrator group.

Page | 8

Druva inSync Storage Migration Technical Guide

10. Upgrade the inSync clients to 4.1 manually or by scheduling upgrade from the server. For more information see Upgrading the Existing Clients to 4.1in this document.

Storage Migration Procedure for Linux

To migrate storage on an inSync server, follow the steps given below. 1. Use the package management tool for the distribution (rpm or dpkg/apt-get) to uninstall the existing Druva inSync Server, see Prerequisites for more information. Note that the server configuration will not be deleted after uninstalling the existing version. 2. Download the inSync Server 4.0.4 upgrade package from the Druva Website (www.druva.com/download). 3. Now upgrade the existing the server using the following the command. Debian based installation:
dpkg i druva-insync-server_4.0.4-<version>_i386.deb

RPM based installation:

rpm ivh druva-insync-server-4.0.4-<version>.i386.rpm

4. Run the storage migration utility at the command line.

inSyncMigrate u insyncserver g insyncserver

5. Enter the path details that the upgrade package requires. You can keep the existing path values or enter the new values for the following: - Data path for the new storage (default is same as old storage path). - Database path for the new storage (default is same as DB path of old storage) - Database Log path for the new storage (default is same as old storage path) - Database cache size (default is 1024 MB maximum) 6. Verify the details. Repeat the 5th step for each storage. 7. The storage migration process starts. For information see Monitoring the Storage Migration Progress in this document. The following message is displayed after completing the migration process.
Storage migration succeeded for Storages Press Enter to Exit:

8. Migrated server can now be verified. See Verifying Successful Storage Migration. 9. Install the inSync 4.1 server. See Installing the inSync Server 4.1for more information.
Page | 9

Druva inSync Storage Migration Technical Guide

10. Upgrade the inSync clients to 4.1 manually or by scheduling upgrade from the server. For more information see Upgrading the inSync clients in this document.

Monitoring the Storage Migration Progress

For Windows The storage migration progress is displayed on the command shell. It is also logged in respective inSyncStorage*.log files located at c:\inSyncServer4\ For Linux The storage migration progress is displayed on the command shell. It is also logged in respective inSyncStorage*.log, inSyncMigrte.log files located at /var/log/inSync/ A brief about migration work-flow: Performs storage compaction on existing storage Performs data format conversion for data folder Migrates restore points for individual users This is repeated for each storage one after the other

Verifying Successful Storage Migration

The logs will indicate if storage migration was successful. Follow the procedure to verify storage and users have successfully migrated: For Windows 1. After storage migration, the Druva inSync Server and Druva inSync Server Control Panel are in disabled state. Start these services from the Windows Services. In case of NAS storages, the Druva inSync server /Druva inSync Control panel services should be run as NAS user and it must have admin privileges (The NAS user should be part of the Administrator group). 2. You can now access the web Console (Start All Programs Druva inSync Server inSync Server Management Console) using the PosgresSQL username and password. Alternately, you can create a new Administrator account from the inSync Server Management console. For Linux 1. Start the inSync server service as follows
Page | 10

Druva inSync Storage Migration Technical Guide

/etc/init.d/inSyncSrv start

2. Open the URL for the inSync Web console (http://127.0.0.1:6065). If you have specified an e-mail address in Settings -> Email -> Administrator email then use it as a username otherwise use insyncserver as a username and then enter your password. Verify the following Verify the storage status from Dashboard. Verify the migrated users list from Users option. Similarly Profiles, restore points and so on can be verified.

Dealing with NAS Data Folders

Launch the inSyncMigrate.exe with the same credentials as NAS handling. 1. Right-click the inSyncMigrate.exe file. 2. Select the Run as option. 3. Select the following user option. 4. Enter the Domain user credentials for NAS, click OK. 5. Continue with the migration process.

Page | 11

Druva inSync Storage Migration Technical Guide

Installing inSync 4.1

After the migration process completed successfully, install the inSync 4.1 server and upgrade its clients.

Installing the inSync Server 4.1

For Windows Download inSync Server 4.1 Professional or Enterprise package on the server. Follow the installation procedure for the respective editions. inSync 4.1 Professional Edition: Install the downloaded package. You do not need to uninstall any of the existing packages. inSync 4.1 Enterprise Edition: Uninstall the existing package. Click Start All ProgramsDruva inSync ServerUninstall Druva inSync Server. This Uninstall step does not delete your existing configuration and data. Now install the inSync 4.1 Enterprise edition. After successful installation, the existing license will not be valid, get the new license from the Druva support. For more information contact support@druva.com. Please note clients can't be upgraded or synchronize their data unless the 4.1 Server package is installed. For Linux Download the inSync Server 4.1 Professional or Enterprise package on the server. Now uninstall the existing package before installing the downloaded package. This will not delete your existing configuration and data. inSync 4.1 Professional Edition: Install the inSync 4.1 Professional edition and follow the procedure mentioned in the inSync Administrators Guide. inSync 4.1 Enterprise Edition: Install the inSync 4.1 Enterprise edition. After successful installation, the existing license will not be valid, get the new license from the Druva support. For more information contact support@druva.com.

Upgrading the Existing Clients to 4.1

Existing 3.x clients cannot synchronize to inSync 4.1 server so clients need to be upgraded from 3.1 to 4.1. Client configuration is automatically carried out without reissuing the client keys.

Page | 12

Druva inSync Storage Migration Technical Guide

Schedule upgrade for the clients from 4.1 server Web Console. Alternatively, clients can be manually upgraded to 4.1 by installing the 4.1 client package on client machines.

Page | 13

Druva inSync Storage Migration Technical Guide

Troubleshooting
If the migration procedure is aborted accidentally or due to any system errors, it can be just restarted. It resumes the incomplete storage migration intelligently. In case of any other errors, please send an email to support@druva.com.

Page | 14