9.3 Backing Up the Filr MySQL Database to Prepare for the Upgrade

When upgrading your Filr deployment, you need to also upgrade the Filr database in the following scenarios:

  • You are upgrading a small deployment.

  • You are upgrading a large deployment and you are using the MySQL database appliance that ships with Filr.

    In a large deployment, the MySQL database backup and upgrade are independent of the Filr and search index upgrades. For example, you can upgrade the Filr and search index appliances in your Filr system first (as described in Section 9.4, Upgrading the Filr, Search, or Database Appliances), then back up and upgrade the MySQL appliance at a later time. However, if you upgrade the MySQL database appliance at a later time, the Filr service needs to be stopped until the database upgrade is complete.

If you are leveraging your own MySQL database or MSSQL database, you do not need to upgrade the Filr database as described in the following sections.

To back up the Filr MySQL database to prepare it to be upgraded:

  1. Determine the size of your current Filr database. You will need this information when copying the database to the new hard disk.

    At the appliance console where the database is running, run the following command to view the database size:

    du -h /vastorage/mysql

  2. (Conditional) If you are upgrading a small deployment, shut down the Filr appliance.

    For information about how to shut down the Filr system, see Shutting Down and Restarting the Novell Appliance in the Novell Filr 1.1 Administration Guide.

  3. (Conditional) If you are upgrading a large deployment, shut down the Filr, search index, and MySQL database appliances that you plan to upgrade from.

    For information about how to shut down the Filr system, see Shutting Down and Restarting the Novell Appliance in the Novell Filr 1.1 Administration Guide.

  4. In a small deployment, attach a new hard disk to the Filr appliance that you are upgrading from.

    In a large deployment, attach a new hard disk on the MySQL database appliance that you are upgrading from.

    IMPORTANT:When creating the hard disk, consider the following:

    • The hard disk must be large enough to store the existing Filr database.

    • Select SCSI (2:0) as the device controller.

  5. Power on the appliance that you are upgrading from where you attached the disk.

    The disk is not recognized until the appliance is powered on.

    IMPORTANT:Before powering on the appliance, ensure that the existing appliance’s /vastorage does not point to an NFS mount point. If it does, you must migrate it to an appliance-based hard disk (as described in Section B.0, Migrating /vastorage from NFS to a Hard Disk).

  6. (Conditional) If you are upgrading a small deployment, stop the Filr and FAMT services:

    1. Log in to the Filr appliance configuration at the following URL:

      https://server_url:9443

    2. Click the Appliance Configuration icon.

    3. Click System Services.

    4. Select Novell Filr, then click Action > Stop > Yes.

    5. Select Novell FAMT, then click Action > Stop > Yes.

  7. Start the SSH service:

    1. Log in to the appliance configuration at the following URL:

      https://server_url:9443

    2. Click the Appliance Configuration icon.

    3. Click System Services.

    4. Select SSH, then click Action > Start.

  8. Download the mysqlbackup.zip file from the Novell Customer Center (NCC).

  9. Copy the mysqlbackup.zip file to the Filr appliance in a small deployment, or copy it to the MySQL appliance in a large deployment.

    You can copy the mysqlbackup.zip file by using WinSCP or a similar program.

  10. Unzip the mysqlbackup.zip file.

  11. Change to the directory where you unzipped the mysqlbackup.zip file.

    cd mysqlbackup

  12. Run the run-mysqlbackup.sh file.

    sh run-mysqlbackup.sh

    If the name of the database is anything other than filr, add the name of the database as a parameter when you run the file.

    sh run-mysqlbackup.sh DatabaseName

    For example, if the name of the database is acme, use acme as the parameter:

    sh run-mysqlbackup.sh acme

    This formats the disk that you attached in Step 4 to be used as the Filr database backup. This script utilizes mysqldump to provide an export of the database.

  13. Specify the user name and password of the MySQL database.

    In a small deployment, the user name is filr and the password is the password that you specified during installation. In a large deployment, this is the user name and password that you specified during installation.

    HINT:If you are unable to connect to the database by using the filr user, you can use the root user as a secondary option.

    The backup is created.

  14. (Optional) To verify that the backup was created:

    In a small deployment, change to the /filr-appliance directory.

    cd /filr-appliance

    In a large deployment, change to the /mysql-appliance directory.

    cd /mysql-appliance

    The Filr database is backed up at this location:

    Small deployment: /filr-appliance/mysqlbackup/filr.sql

    Large deployment: /mysql-appliance/mysqlbackup/filr.sql

  15. In a small deployment, install the new Filr all-in-one appliance, as described in Section 9.4, Upgrading the Filr, Search, or Database Appliances.

    In a large deployment, install the new MySQL database appliance, as described in Section 9.4, Upgrading the Filr, Search, or Database Appliances.