Migrating from version 2.3 to 2.3.5

You can install StoreGrid v2.3.5 on top of the existing version 2.3 and StoreGrid will automatically migrate to 2.3.5 release.

Versions older than v2.3 cannot be migrated directly to v2.3.5. You will have to first migrate them to v2.3 and install v2.3.5 on top of it. For versions older than v2.2.1, first migrate them to v2.2.1 and then to v2.3. You can download the v2.2.1 from http://www.vembu.com/storegrid/storegrid-221-downloads.php and version v2.3 from http://www.vembu.com/storegrid/storegrid-23-downloads.php?edt=sp

If you login into the web console when the migration process is in progress, you will be directed to a page which indicates that migration is in process. The migration might take up to 20 minutes depending upon the amount of data to be migrated. Wait for some time and then try re-logging in. Please don't shutdown and restart StoreGrid as this will only further delay the migration.

Migrating from version 2.2.1/2.2.5 to 2.3

You can upgrade StoreGrid v2.2.1 and v2.2.5 to v2.3 by just installing v2.3 on top of the current installation. Versions older than v2.2.1 cannot be migrated directly to v2.3. You will have to first migrate them to v2.2.1 and then migrate v2.2.1 to v2.3. You can download the v2.2.1 from http://www.vembu.com/storegrid/storegrid-221-downloads.php

Migration might take some time depending upon the amount of data to be migrated. Please don't restart StoreGrid as this will only further delay the migration. If you log into the StoreGrid web console during migration, you will be directed to a page indicating that the migration process is in progress. Wait for sometime and then try logging back in. In the backup server. migration could take about 5 minutes for every 100,000 files backed up. Migration in the client should not take much time.

Migrating from version 2.2.1 to 2.2.5

There is no special migration procedure if you are updating from 2.2.1 to 2.2.5. You can just install StoreGrid 2.2.5 on top of the existing 2.2.1 version and StoreGrid will automatically migrate to the 2.2.5 release. StoreGrid will not be functional while the migration is in progress. The migration on the StoreGrid may take some time based on the number of files backed up to/from the StoreGrid installation, as StoreGrid performs indexing on the internal databases to improve performance of backups during migration. For example, migrating 1,000,000 files will take about 10 minutes and 2,000,000 files will take about 20 minutes. While you update from Version 2.2.1 to 2.2.5 please note that:

1. StoreGrid will not be able to schedule any backups while the migration is in progress.

2. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.

Migrating from version 2.0/2.0.1/2.1/2.1.1 to 2.2/2.2.1

Migrating to StoreGrid 2.2/2.2.1 is completely automatic except for the case where a backup server has multiple clients (under different customers) with the same StoreGrid id.

All you have to do is to install StoreGrid 2.2.1 on top of your existing (2.0/2.0.1/2.1/2.1.1) StoreGrid installation.

Please migrate your Backup Server & Replication Server first. Thereafter, you can migrate your clients in a phased manner. Clients running version 2.0/2.0.1/2.1/2.1.1 will continue to backup to your backup server running v2.2.1 ! Section 1 below covers Server Side Migration, and Section 2 covers Client Side migration.

1. StoreGrid Server-side Migration

While updating a StoreGrid server installation to version 2.2, most of the migration procedures are internal and automatic. The migration on the StoreGrid Backup Server and the StoreGrid Replication Server may take some time based on the number of files backed up on the StoreGrid Server. For example, migrating 100,000 files will take about 10 minutes and 200,000 files will take about 20 minutes.

1.1. StoreGrid 2.2 customer and license (MSPEU) migration

From StoreGrid 2.2, all client licenses are managed from the backup server and there is no need to apply license keys to the StoreGrid clients backing up to the backup server. The client license unit in StoreGrid 2.2 is called an MSPEU (monthly SPEU). The pre-2.2 license units were called SPEUs. 1 SPEU is simply 12 MSPEUs. When you update your existing installation to StoreGrid 2.2, StoreGrid will automatically migrate all the pre-2.2 licenses added under customers to the new MSPEU license scheme. The number of migrated MSPEUs are calculated based on the expiry date of each of the SPEU licenses (pre-2.2), license type (Desktop/Server) of each of the clients backing up to the server. The following points are to be noted on how the customer and license migration is done in 2.2:

1. The licensed (therefore, paying) clients under the 'Trial Customer' in existing StoreGrid versions (2.0/2.0.1/2.1/2.1.1) will be migrated to the 'Default Customer' in StoreGrid 2.2 ; 'Default Customer' is a new group in v2.2 to accommodate paying/licensed clients that are not categorized under any specific customer.

2. The (non paying / unlicensed) trial clients under the 'Trial Customer' in existing StoreGrid versions (2.0/2.0.1/2.1/2.1.1) will continue to be retained under the 'Trial Customer' in StoreGrid 2.2.

3. The pre-2.2 licenses which were added under different customers (in the StoreGrid Server) will be migrated to MSPEUs in StoreGrid 2.2 and they will be automatically assigned to the respective customers.

4. The licenses (for licensed clients) added under the 'Trial Customer' will be migrated to MSPEUs and will be automatically assigned to the 'Default Customer'. By default, after 2.2 migration, all customers, except 'Trial Customer', will be configured to "Automatically use MSPEUs as required". This way, the clients under each of the customers will automatically use MSPEUs from the global MSPEU pool as and when required.

1.2. StoreGrid 2.2 invoice migration

StoreGrid 2.2 has the concept of invoice plans wherein you can create multiple invoice plans and assign an invoice plan to one or more customers. The following points are to be noted on how the invoice module is migrated to StoreGrid 2.2.

1. Customer Invoice Configurations for each Customer in StoreGrid 2.1.1 will be migrated as Invoice Plans in 2.2. The migrated Invoice Plans will be automatically assigned to the respective Customers. For example, if the Customer name is 'Test Customer', then a Invoice plan with a name 'Test Customer-Plan' will be created and will be assigned to 'Test Customer'.

2. By default, the 'Default Invoice Plan' will be assigned to the 'Trial Customer' after 2.2 migration.

1.3. Migration of clients with duplicate StoreGrid Id to StoreGrid 2.2

One big change in StoreGrid 2.2 is that, from StoreGrid 2.2, all the clients backing up to a StoreGrid server across all customers should have a unique StoreGrid Id. If there are multiple clients with the same StoreGrid Id across different Customers in 2.1.1, then these clients cannot be migrated 'as is' to StoreGrid 2.2. In this case, except for one of the clients, all other clients with the same StoreGrid Id will have to be manually renamed or completely deleted from the StoreGrid server.

During migration StoreGrid 2.2 will automatically detect clients with same StoreGrid Id. After the migration is done, when you login to the StoreGrid server webconsole, you will be given options to individually handle the migration of clients with the same StoreGrid Id (if at all any exist). The clients with the same StoreGrid Id will be listed with their Customer Name in the webconsole. And you can do one of the following for each of the clients:

1. Rename the client and continue migration - If this option is selected, then the client will be migrated with the new client name provided.
2. Delete this client and continue migration - If this option is selected, then the client & their data will be deleted from the Backup Server.
3. Leave this client as it is and continue migration - If this option is selected, then the client will be retained with the same name. Note that you can choose this option for only one of the clients, i.e., if one client is being retained 'as is', other clients with the same name will need to be deleted/renamed.

Note that you will not be able to login to the webconsole until the migration of the duplicate clients in StoreGrid 2.1.1 is completed. You can view the status of the clients' migration after clicking the 'Migrate' button. You will be able to login to the StoreGrid Webconsole only after successful migration of the duplicate clients.

VERY IMPORTANT: You should ensure that the StoreGrid clients whose StoreGrid Ids have been renamed should not be started until they are updated to StoreGrid 2.2 and their StoreGrid Ids changed to the same Id (as renamed to) in the server. Please ensure that this is done as otherwise you may have multiple clients (with the same name) continuing to backup to 1 client account in the StoreGrid Server.

1.3.1. Renaming StoreGrid Id in the StoreGrid client side

After doing the duplicate client migration (if you did indeed have duplicate clients in the first place) on the Backup Server, you will need to change the StoreGrid Identity in the StoreGrid client. To do this, update the client to StoreGrid 2.2 by installing StoreGrid 2.2 on top of the existing installation. After installation, do not start the StoreGrid client until the client's StoreGrid Id is changed to the same name configured in the backup server.

To change the StoreGrid Identity of the client, please follow the below steps :

1. Open a terminal (or) command prompt.
2. Go to the <STOREGRID_HOME> directory.
3. In case of Windows client, execute the command 'bin\StoreGrid.exe ChangeIdentity <Old StoreGrid Identity> <New StoreGrid Identity>'.
4. In case of Linux client, execute the command './bin/StoreGrid ChangeIdentity <Old StoreGrid Identity> <New StoreGrid Identity>'.

This will migrate the StoreGrid Identity of the client with the new client name. After changing the StoreGrid Identity you can start StoreGrid normally.

2. StoreGrid Client-side Migration

IMPORTANT: You should ensure that the StoreGrid clients whose StoreGrid Ids have been renamed in the server-side should not be started until they are updated to StoreGrid 2.2 and their StoreGrid Ids changed to the same Id as in the server. Follow the steps in 1.3.1 above to change the client's StoreGrid Id before you start the StoreGrid client.

NOTE: The Email Filtering configurations are not migrated from 2.1.1 to 2.2.1. Hence, please reconfigure the Email filtering options after upgrading to StoreGrid 2.2.1 Release.

Migrating from version 2.0/2.0.1/2.1 to 2.1.1

There is no special migration procedure if you are updating from 2.0/2.0.1/2.1 to 2.1.1. You can just install StoreGrid 2.1.1 on top of the existing 2.0/2.0.1/2.1 version and StoreGrid will automatically migrate to the 2.1.1 release. StoreGrid will not be functional while the migration is in progress. But the migration itself will take only a few seconds. While you update from Version 2.0.1/2.1 to 2.1.1 please note that:

1. StoreGrid will not be able to schedule any backups while the migration is in progress.

2. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.

Migrating from version 1.6 to 2.0

Vembu StoreGrid 2.0 is a major upgrade release over the StoreGrid 1.6 release. StoreGrid's architecture and infrastructure have been revamped and improved significantly keeping in mind scalability, performance and flexibility in terms of evolution of future versions of StoreGrid. Towards that end, StoreGrid 2.0 completely leverages an embedded RDBMS both in the client and the server side. Except for the backup files, which uses the native file system itself, every other information StoreGrid generates or uses like configurations, file meta-data, file signatures, events, version information, backup reports, restore reports etc. are all driven from the RDBMS. Leveraging an RDBMS gives StoreGrid the capability to evolve rapidly in terms of new features and user-interface improvements etc. without compromising on scalability and performance. With this major re-design of StoreGrid with the 2.0 version, we expect to deliver customer focused features at a more rapid pace than before.

Whether StoreGrid installation is a Client, Server, Or Client-Server Installation, the first time it runs, StoreGrid 2.0 automatically migrates all the file meta-data and configurations maintained in flat files or the 1.6 database to the newly created 2.0 database. The StoreGrid Client side migration is quite fast. Even for 1000s of files, the client side migration will take only a few minutes. On the StoreGrid server side, where the backup data is present, depending upon the number of files you have backed up earlier, the migration may take some time. The time taken for the migration on the server side depends upon the total number of files that were earlier backed up with StoreGrid 1.6. Migrating 10,000 files will take about 4 minutes and 100,000 files will take about 40 minutes.

StoreGrid will not be functional while the migration is in progress. While you upgrade from Version 1.6 to 2.0, please note the following points:

1. StoreGrid 2.0 will automatically migrate your 1.6 data to 2.0 formats when it runs first time after the upgrade.

2. StoreGrid 2.0 is not interoperable with StoreGrid 1.6. Hence make sure you upgrade and migrate both your client and server installations before you resume your backups. The recommended procedure is to update and migrate your StoreGrid servers first. StoreGrid 2.0 will put all the backup schedules in the client in suspended mode after the migration process.You need to resume them manually after making sure the backup servers also have been upgraded and migrated to 2.0.

3. StoreGrid will not be able to schedule any backups while the migration is in progress.

4. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.

5. StoreGrid Migration process may use high CPU cycles and may slow down other processes on the machine/PC. Hence it is advisable to upgrade to StoreGrid 2.0 when you are not using the machine/PC for CPU intensive tasks.

Advanced Users

The following points should help you understand the internal migration process when you run StoreGrid 2.0 for the first time after upgrading from 1.6.

1. StoreGrid 1.6 to 2.0 Client Side Migration

The operations performed in client side migration are as follows:

1. User Account Migration: Read the user lists from userfiles.lst and write to Client DB.

2. Backup Configuration Migration: List the *.sbf, *.imm & *.scc files from <STOREGRID_HOME>/conf & add backup configuration to DB. After migration, the backups will be in suspended status. User has to resume the backup schedule manually only after making sure the backup servers the client was backing up to are also upgraded to the StoreGrid 2.0 version and the migration has taken place in those servers.

3. Discovered Peer List Migration: Read the discovery.log (if not present, discovery.tmp) file from <STOREGRID_HOME> and add them to Discovery DB.

4. Discovery Configuration Migration: Read the discovery.conf file from <STOREGRID_HOME>/conf and write to Discovery DB.

5. Delete Configuration & Reports Migration: List the *.sdf files from <STOREGRID_HOME>/conf & write them to Client DB.

6. File Meta Data Migration: Attach the 1.6 DB to 2.0 DB and copy the file meta-data information and signature data.

7. Backup Reports Migration: Attach the 1.6 DB to 2.0 DB and copy the backup reports information.

8. Restore Reports Migration: List the *.rpt files from <STOREGRID_HOME>/report/restore and add them to DB.

2. StoreGrid 1.6 to 2.0 Server Side Migration

The operations performed in server side migration are as follows:

1. For each backup client backing up to the server, find the backup location from <SG_HOME>/conf/diskspaceconfiguration/and migrate the backed up files to a new 2.0 directory structure which is based on directory Ids. Note that StoreGrid 2.0 will move the backed up files from the original location to the new location.

2. By default all the client's backup will be done under a directory called "1" under the backup location.

3. Move Disk Space Configuration information of all clients to Server DB.

Migrating from version 1.2.1 to 2.0

If you are still using the 1.2.1 release and want to migrate from 1.2.1 to 2.0, then the migration is a two step process.

1. Firstly you need to migrate from 1.2.1 to 1.6 by installing StoreGrid 1.6. You can check whether the migration has completed by logging into the UI. The steps for migrating from 1.2.1 to 1.6 is given below.

2. After migrating to 1.6, then you can migrate StoreGrid to 2.0 by installing 2.0 on top of the 1.6 version. The steps for migrating from 1.6 to 2.0 is given above.

Migrating from version 1.2.1 to 1.6

NOTE: StoreGrid 1.6 is a minor bug fix release over 1.5.1. So there is no special migration procedure if you are updating from 1.5.1 to 1.6

Vembu StoreGrid 1.6 has some significant improvements in terms of how a StoreGrid client internally maintains metadata information.

In earlier versions , metadata information like the signature (used for incremental backups) and file statistics (modified time, created time etc.) were stored in flat files. This was relatively inefficient as the metadata occupied more space than necessary. StoreGrid 1.6 uses an embedded relational database (RDBMS) to store the metadata efficiently. Moving to an RDBMS also enhances StoreGrid's ability to provide more detailed reports.

The first time it runs, StoreGrid 1.6 automatically migrates the metadata maintained in flat files to the embedded RDBMS. Depending upon the number of files you had backed up earlier, the migration may take some time. The time taken for the migration depends upon the total number of files that were earlier backed up with StoreGrid 1.2.1. Migrating 10,000 files will take about 2 minutes and 100,000 files will take about 30 minutes.

StoreGrid will not be functional while the migration is in progress. While you update from Version 1.2.1 to 1.6 , please note that:

1. StoreGrid will not be able to schedule any backups while the migration is in progress.

2. The StoreGrid Web Console, when accessed, will come up with a message that "Migration is in progress". StoreGrid Web Console features cannot be used while the migration is in progress.

3. StoreGrid Migration process may use high CPU cycles and may slow down other processes on the machine/PC. Hence it is advisable to update to StoreGrid 1.6 when you are not using the machine/PC for CPU intensive tasks.

4. The last backup information in the backup reports will be reset after the migration, i.e. the last backup information like Total Files, Total Files Protected etc. will be set to zero. These fields will be updated once StoreGrid 1.6 runs and completes a backup.

For Advanced Users

The following points should help you understand the internal migration process when you run StoreGrid 1.6 for the first time after updating from 1.2.1

1. StoreGrid 1.6 creates a relational database file "storegrid.db" in <INSTALLATION_HOME>/Vembu/StoreGrid/data directory.

2. The 1.2.1 version metadata information available in the <INSTALLATION_HOME>/Vembu/StoreGrid/data/<backup-schedule> directory will be copied to the relational database. At the end of migration of every backup schedule, StoreGrid will rename the existing backup schedule metadata directories to <backup-schedule>_SG_1_2_1. StoreGrid 1.6 will not delete the 1.2.1 version's meta data information. All the directories renamed with _SG_1_2_1 can be deleted by the user manually after making sure StoreGrid 1.6 works correctly after the migration process.

3. StoreGrid 1.6 will also migrate the reports available under <INSTALLATION_HOME>/Vembu/StoreGrid/report/backup to the relational database.

4. In case StoreGrid is terminated during migration, StoreGrid will migrate the remaining metadata the next time StoreGrid is restarted.