Home Print  

Migrating from version 4.2/4.2.1/4.2.5/4.3 to 4.4

You can install v4.4 on top of the existing v4.2/4.2.1/4.2.5/4.3 and will automatically migrate to v4.4. Before migrating to v4.4, please make a note of the following instructions:

  • ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST.

  • To upgrade to v4.4, you should be currently running the v4.2/4.2.1/4.2.5/4.3

  • To upgrade to v4.4, just install v4.4 on top of the v4.2/4.2.1/4.2.5/4.3 installation. DO NOT UNINSTALL v4.2/4.2.1/4.2.5/4.3.

  • If you are currently running a version older than v4.2, ensure you first upgrade to v4.2. After upgrading to v4.2, start , log into the webconsole to make sure that the upgrade to v4.2 is successful before installing v4.4 on top of it.

  • Ensure that your Backup & Replication Servers are first upgraded from v4.2/4.2.1/4.2.5/4.3 to v4.4 before upgrading the v4.2/4.2.1/4.2.5/4.3 clients.

  • Only v4.2, v4.2.1, v4.2.5, v4.3 and v4.4 clients can backup to v4.4 Backup Server.

We have ensured backward compatibility for v4.2, v4.2.1, v4.2.5 and v4.3 clients; so they can continue backing up to a v4.4 backup server (this way, you can upgrade your clients in a phased manner).

Migrating from version 4.0/4.1 to 4.2

You can install v4.2 on top of the existing v4.0/v4.1 and will automatically migrate to v4.2. Before migrating to v4.2, please make a note of the following instructions:

  • To upgrade to v4.2, you should be currently running the v4.0/v4.1

  • To upgrade to v4.2, just install v4.2 on top of the v4.0/v4.1 installation. DO NOT UNINSTALL v4.0 / v4.1.

  • If you are currently running a version older than v4.0, make sure you first upgrade to v4.0. After upgrading to v4.0, make sure you start , log into the webconsole, make sure the upgrade to v4.0 is successful before installing v4.2 on top of it.

Also ensure that your Backup & Replication Servers are first upgraded from v4.0/v4.1 to v4.2 before upgrading the v4.0/v4.1 clients. Only v4.0, v4.1 and v4.2 clients can backup to v4.2 Backup Server. Therefore, before upgrading clients to v4.2, you must ensure that your Backup Server has been upgraded to v4.2. We have ensured backward compatibility for v4.0 and v4.1 clients; so they can continue backing up to a v4.2 backup server (this way, you can upgrade your clients in a phased manner). ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST.

Migrating from version 3.5 to 4.0

You can install v4.0 on top of the existing v3.5 and will automatically migrate to v4.0. Before migrating to v4.0, please make a note of the following instructions:

  • To upgrade to v4.0, you should be currently running the v3.5.

  • To upgrade to v4.0, just install v4.0 on top of the v3.5 installation. DO NOT UNINSTALL v3.5.

  • If you are currently running a version older than v3.5, make sure you first upgrade to v3.5. After upgrading to v3.5, make sure you start , log into the webconsole, make sure the upgrade to v3.5 is successful before installing v4.0 on top of it.

Also ensure that your Backup & Replication Servers are first upgraded from v3.5 to v4.0 before upgrading the v3.5 clients. Only v3.5 and v4.0 clients can backup to v4.0 Backup Server. Therefore, before upgrading clients to v4.0, you must ensure that your Backup Server has been upgraded to v4.0. We have ensured backward compatibility for v3.5 clients; so they can continue backing up to a v4.0 backup server (this way, you can upgrade your clients in a phased manner). ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST.

Migrating from version 3.1/3.2 to 3.5

You can install v3.5 on top of the existing version 3.1/3.2 and will automatically migrate to v3.5. Before migrating to v3.5, please make a note of the following instructions:

  • To upgrade to v3.5, you should be currently running the v3.1/v3.2.

  • To upgrade to v3.5, just install v3.5 on top of the v3.1/v3.2 installation. DO NOT UNINSTALL v3.1/v3.2.

  • If you are currently running version 3.0, make sure you first upgrade to v3.1. After upgrading to v3.1, make sure you start , log into the webconsole, make sure the upgrade to v3.1 is successful before installing v3.5 on top of it.

  • If you are currently running a version older than v3.0, make sure you first upgrade to v3.2. After upgrading to v3.2, make sure you start , log into the webconsole, make sure the upgrade to v3.2 is successful before installing v3.5 on top of it.

Also ensure that your Backup Server is first upgraded from v3.1/v3.2 to v3.5 before upgrading the v3.5 clients. Only v3.1 and v3.2 clients can backup to v3.5 Backup Server, Therefore, before upgrading clients to v3.5, you must ensure that your Backup Server has been upgraded to v3.5. We have ensured backward compatibility for v3.1/v3.2 clients so that they can continue backing up to a v3.5 server (this way, you can upgrade your clients in a phased manner). ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST.

Migrating from version 2.5.x to 3.2

Migrating Backup Server and Replication Server from version 2.5.5 to 3.2

You can install v3.2 Server Build on top of v2.5.5 installations in Backup and Replication Servers. will automatically migrate to v3.2. Before migrating to v3.2, please make a note of the following instructions:

  • To upgrade Backup Server to v3.2, you should be currently running v2.5.5 in the Backup Server.

  • To upgrade Replication Server to v3.2, you should be currently running v2.5.5 in the Replication Server.

  • To upgrade Backup/Replication Server to v3.2, just install v3.2 server build on top of the v2.5.5 installation. DO NOT UNINSTALL v2.5.5..

  • If you are currently running a version older than v2.5.5 in the Backup/Replication Server, make sure, you first upgrade to them v2.5.5. After upgrading to v2.5.5, make sure you start to complete the migration process. Also, make sure you log into the web console and make sure the upgrade to v2.5.5 has completed successfully before installing v3.2 on top of v2.5.5.

If you are running v2.5.1 in the Backup/Replication Servers, then please follow the migration steps given in "Migrating from version 2.5.1 to 2.5.5" section below.

NOTE: After migrating the Backup Server to v3.2 version, the existing v2.5.1 clients can continue the incremental backup to v3.2 Backup Server.

Migrating Client from version 2.5.1 to 3.2

You can install v3.2 Client Build on top of the existing Client v2.5.1 installation and will automatically migrate it to v3.2. Before migrating to v3.2, please make a note of the following instructions:

  • To upgrade a Client to v3.2, you should be currently running v2.5.1.

  • To upgrade a Client to v3.2, just install v3.2 on top of the v2.5.1 installation. DO NOT UNINSTALL v2.5.1.

  • If you are currently running a Client version older than v2.5.1, make sure you first upgrade the Client to v2.5.1 and then start to complete the migration process before installing v3.2.

Before upgrading Clients to v3.2, you must ensure that your Backup Server has been upgraded to v3.2. The existing v2.5.1 client can continue backing up to a v3.2 Backup Server.

Client machines running version older than v2.5.1 cannot be migrated directly to v3.2. If you are running v2.4 in the client machines, then follow the migration steps given in "Migrating from version 2.4 to 2.5.1" section below.

Migrating from version 2.5.1 Client-Server to 3.2

From v2.5.5, Client-Server mode of deployment is not supported. Hence to migrate v2.5.1 Client-Server installations to v3.2, mode should be first changed to either Client Only or Server Only before migration.

Steps to migrate v2.5.1 Client-Server to v3.2 Client-Only:

  • Stop .

  • Set the StartModule attribute to 602(Client-Only) in the <InstallationLocation>/conf/SGConfiguration.conf file.

  • Start .

  • Now, install SG v3.2 Client Build on top of the existing v2.5.1 Client-Only installation.

Steps to migrate v2.5.1 Client-Server to v3.2 Server-Only:

  • Stop .

  • Set the StartModule attribute to 601(Server-only) in the <InstallationLocation>/conf/SGConfiguration.conf file.

  • Start .

  • Now, install SG v2.5.5 Server Build on top of the existing 2.5.1 Server-Only installation.

    Please note that migration to v2.5.5 takes some time. Once v2.5.5 migration is complete, you can login to web console and make sure the data is successfully migrated to v2.5.5.

  • Now, install SG v3.2 Server Build on top of the existing v2.5.5 Server installation.

NOTE: Migrating from versions 3.0 or 3.1 to 3.2 is not supported.

Migrating from older version to v3.1

Migration from older version to v3.1 is not supported. v3.1 has to be installed as a fresh installation. Migration from v2.5.1 to v3.x will be supported in future.

  • To upgrade your backup/Replication Server to v2.5.5, just install v2.5.5 on top of v2.5/v2.5.1 installation. DO NOT UNINSTALL v2.5/v2.5.1.

  • If you are upgrading from v2.5.1 to v2.5.5, please note that v2.5.5 Backup/Replication Server uses ODBC Datasources of Client-Server (MySQL) database as the backend database to store the clients' metadata. Make sure you have installed and configured MySQL before installing v2.5.5. Please follow the following URLs to know more about installing and configuring MySQL and other related packages required for v2.5.5

    MySQL installation and configuration guide for Windows
    MySQL installation and configuration guide for Linux

  • If you are currently running v2.5, then you already have MySQL installed as v2.5 uses MySQL as the backend database. But you need to update the MySQL configuration file my.cnf (for Linux) or my.ini (for Windows) and the MySQL Connector file odbcinst.ini file (for Linux alone) before migrating to v2.5.5. To do this, please follow the below steps :

    1. Stop in your backup/Replication Server.
    2. Open the MySQL configuration file /etc/my.cnf (for Linux) or <MySQL Installation Dir>/my.ini (for Windows)
    3. Add the following attributes under [mysqld] section
    4. [mysqld]
      slow_query_log = 1
      innodb_flush_method=O_DIRECT (only for MySQL server running in Linux)

    5. Save the file.
    6. If it is a Windows machine, you can now restart MySQL Server by going to 'Start -> Run -> services.msc' and right click on 'MySQL51' service and select 'Restart'. If it is a Linux machine, follow the steps 6-10 listed below.
    7. Execute the command 'odbcinst -j'. (Only for Linux)
    8. Note the path of the 'odbcinst.ini' file for DRIVERS. By default, it is '/usr/local/etc/odbcinst.ini'
    9. Open the odbcinst.ini
    10. Append the attribute 'Threading' under [MySQL] section as follows :
    11. [ODBC]
      Trace = No
      Trace File = /tmp/sql.log
      Pooling = Yes

      [MySQL]
      Description =
      Driver = /usr/local/lib/libmyodbc3-3.51.27.so
      Driver64 =
      Setup = /usr/local/lib/libmyodbc3S-3.51.27.so
      Setup64 =
      UsageCount =1
      CPTimeout =300
      CPReuse =1
      Threading =0

    12. Restart MySQL Server. To restart MySQL in Linux, execute the command '/etc/init.d/mysql restart' as root.

  • After completing installation and configuration of MySQL, start MySQL Server and then upgrade to v2.5.5

  • Upgrading from v2.5.1 to v2.5.5 will migrate all the backups' metadata from the embedded SQLite database to Client-Server MySQL database. v2.5.5 migration will take time based on the number of clients, backups and number of rows/entries available in the SQLite databases.

    As an estimate might take 30 to 40 minutes for migrating 1 million records from SQLite to MySQL database based on the system hardware configuration. Hence, if you have 25 million files backed up with around 50 million records in the database, then it might take around 25 hours to migrate the metadata from SQLite databases to MySQL. This time duration could be lesser based on the hardware configuration of your Server.

    Please note that, as the database entries are populated in MySQL Server, the MySQL's innodb file size will increase based on the number of records migrated from the SQLite database. Hence, it is wise to plan the MySQL database storage as well as to optimize InnoDB storage engine for the migration. Please refer the above MySQL installation guide for more details on this.

  • From v2.5.5, uses separate MySQL database for each backups in the Backup Server/Replication Server for better scalability and performance. v2.5 uses a single global database to store the metadata of the all the clients. While upgrading from v2.5 to v2.5.5, you can migrate the metadata of the backups from the single global database to separate databases for each backups. Or you can opt to not migrate the existing backups' metadata to separate databases and to use separate databases only for the future new backups. If you choose the former option, then migration will take time based on the number of clients, backups and number of rows/entries available in the global databases.

  • When migration is in progress, if you login to the web console, you will see the number of total backups to be migrated, number of backup databases already migrated, number of backup databases which have failed migration, number of replication databases already migrated and number of replication databases which have failed migration.

    Please do not stop/restart while migration is in progress.

  • If you see any failed backups during migration, please check <_HOME>/sgmysqlmigration/failedBackups.xml file for more details. Contact support, to import the backups which have failed during migration.

  • Migrating from version 2.4 to 2.5.1

    You can install v2.5.1 on top of the existing version 2.4 and will automatically migrate to v2.5.1. Before migrating to v2.5.1, please make a note of the following instructions:

    • To upgrade to v2.5.1, you should be currently running the v2.4.

    • To upgrade to v2.5.1, just install v2.5.1 on top of the v2.4 installation. DO NOT UNINSTALL v2.4.

    • If you are currently running a previous version, make sure you first upgrade to v2.4 and start to complete the migration process before installing v2.5.1.

    Also ensure that your Backup Server is running the same (or higher) version than the clients backing up to it. For example: before upgrading clients to v2.5.1, you must ensure that your Backup Server has been upgraded to v2.5.1; we typically ensure backward compatibility for clients, for example, a v2.4 client can still backup to a v2.5.1 server (this way, you can upgrade your clients in a phased manner). In short, ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST.

    Versions previous to v2.4 cannot be migrated directly to v2.5.1. If you are running version older than v2.4, follow the migration steps given in "Migrating from version 2.3.5 to 2.4" section below. " OnClick ="http://storegrid.vembu.com/online-backup/storegrid-24-downloads.php?edt=pro.

    Migrating from version 2.3.5 to 2.4

    You can install v2.4 on top of the existing version 2.3.5 and will automatically migrate to v2.4 release. Before migrating to v2.4, please make a note of the following instructions:

    • To upgrade to v2.4 SP edition, you should be currently running the v2.3.5 SP edition.

    • To upgrade to v2.4, just install v2.4 on top of the v2.3.5 installation. DO NOT UNINSTALL v2.3.5.

    • If you are currently running a previous version, make sure you first upgrade to v2.3.5 and start to complete the migration process before installing v2.4.

    Also ensure that your Backup Server is running the same (or higher) version than the clients backing up to it. For example: before upgrading clients to v2.4, you must ensure that your Backup Server has been upgraded to v2.4; we typically ensure backward compatibility for clients, for example, a v2.3.5 client can still backup to a v2.4 server (this way, you can upgrade your clients in a phased manner). In short, ALWAYS UPGRADE THE BACKUP (& REPLICATION) SERVERS FIRST.

    Versions previous to v2.3.5 cannot be migrated directly to v2.4. You will have to first migrate them to v2.3.5 and install v2.4 on top of it. For versions previous to v2.2.1, first migrate them to v2.2.1 and to v2.3 and then to v2.3.5. http://storegrid.vembu.com/online-backup/storegrid-pro-221-downloads.phphttp://storegrid.vembu.com/online-backup/storegrid-23-downloads.php?edt=pro http://storegrid.vembu.com/online-backup/storegrid-235-downloads.php?edt=pro

    Migrating from version lower than 2.3.5

    If you are currently running a version previous to 2.3.5, then you need to first upgrade to v2.3.5 before installing v2.4.

    It is very important that after every version upgrade, you need to start the application and login into the web console and confirm the upgrade has happened successfully before upgrading it to the next version. !!!!

    As an example, if you are currently running v2.2, then you need to follow the steps given below to upgrade to v2.4

    1. Install v2.2.1 build on top of the existing v2.2 installation.

    2. Choose 'Start ' option after completing the installation and wait for some time to let the application to complete the migration. If you log into the web console while the migration is in progress, you will be redirected to page that indicates the migration is in progress.

    3. Once the migration process is completed, login to the web console and verify all the configurations and backups are intact - VERY IMPORTANT

    4. Install v2.3 build on top of the existing v2.2.1 installation.

    5. Choose 'Start ' option after completing the installation and wait for some time to let the application to complete the migration.

    6. Once the migration process completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT

    7. Install v2.3.5 build on top of the existing v2.3 installation.

    8. Choose start option after completing the installation and wait for some time to let the application to complete the migration.

    9. Once the migration process is completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT

    10. Install v2.4 build on top of the existing v2.3.5 installation.

    11. Choose start option after completing the installation and wait for some time to let the application to complete the migration.

    12. Once the migration process is completed, login to the web console and verify whether all the configurations are intact - VERY IMPORTANT

    Migrating from version 2.3 to 2.3.5

    You can install v2.3.5 on top of the existing version 2.3 and 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. http://storegrid.vembu.com/online-backup/storegrid-pro-221-downloads.php and version v2.3 from http://storegrid.vembu.com/online-backup/storegrid-23-downloads.php?edt=pro

    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 as this will only further delay the migration.

    Migrating from version 2.2.1 to 2.3

    You can upgrade v2.2.1 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. http://storegrid.vembu.com/online-backup/storegrid-pro-221-downloads.php

    Migration might take some time depending upon the amount of data to be migrated. Please don't restart as this will only further delay the migration. If you log into the 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.0/2.0.1/2.1/2.1.1 to 2.2.1

    Migrating to 2.2.1 is completely automatic.

    All you have to do is to install 2.2.1 on top of your existing (2.0/2.0.1/2.1/2.1.1) 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. Server-side Migration

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

    While updating a server installation to version 2.2.1, most of the migration procedures are internal and automatic. But the following changes to 2.2.1 needs to be understood by the service provider before deploying and using 2.2.1.

    1.1. 2.2.1 Groups

    From 2.2.1, all clients are organized under Groups. In 2.1.1 Professional Edition, the clients were listed directly in the 'Server Admin -> Client Management'. Now in 2.2.1, the clients will be by default organized under the 'Default Group'. Users can create multiple Groups (up to one level) and organize their clients based on their Groups, such as Departments, Office Branches, etc.,

    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 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 2.1.1 on top of the existing 2.0/2.0.1/2.1 version and will automatically migrate to the 2.1.1 release. 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. will not be able to schedule any backups while the migration is in progress.

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


    Migrating from version 1.6 to 2.0

    2.0 is a major upgrade release over the 1.6 release. '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 . Towards that end, 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 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 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 with the 2.0 version, we expect to deliver customer focused features at a more rapid pace than before.

    Whether installation is a Client, Server, Or Client-Server Installation, the first time it runs, 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 Client side migration is quite fast. Even for 1000s of files, the client side migration will take only a few minutes. On the 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 1.6. Migrating 10,000 files will take about 4 minutes and 100,000 files will take about 40 minutes.

    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. 2.0 will automatically migrate your 1.6 data to 2.0 formats when it runs first time after the upgrade.

    2. 2.0 is not interoperable with 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 servers first. 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. will not be able to schedule any backups while the migration is in progress.

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

    5. Migration process may use high CPU cycles and may slow down other processes on the machine/PC. Hence it is advisable to upgrade to 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 2.0 for the first time after upgrading from 1.6.

    1. 1.6 to 2.0 Client Side Migration

    2. 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 <_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 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 <_HOME> and add them to Discovery DB.

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

      5. Delete Configuration & Reports Migration: List the *.sdf files from <_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 <_HOME>/report/restore and add them to DB.

    3. 1.6 to 2.0 Server Side Migration

    4. 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 <INSTALLATION_HOME>/conf/diskspaceconfiguration/and migrate the backed up files to a new 2.0 directory structure which is based on directory Ids. Note that 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 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 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: 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

    1.6 has some significant improvements in terms of how a 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. 1.6 uses an embedded relational database (RDBMS) to store the metadata efficiently. Moving to an RDBMS also enhances 's ability to provide more detailed reports.

    The first time it runs, 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 1.2.1. Migrating 10,000 files will take about 2 minutes and 100,000 files will take about 30 minutes.

    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. will not be able to schedule any backups while the migration is in progress.

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

    3. Migration process may use high CPU cycles and may slow down other processes on the machine/PC. Hence it is advisable to update to 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 1.6 runs and completes a backup.

    For Advanced Users

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

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

    2. The 1.2.1 version metadata information available in the <INSTALLATION_HOME>//data/<backup-schedule> directory will be copied to the relational database. At the end of migration of every backup schedule, will rename the existing backup schedule metadata directories to <backup-schedule>_SG_1_2_1. 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 1.6 works correctly after the migration process.

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

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


    Print  
    Technical support-