• From 3.2.2 to 3.4
• From 2.x to 3.2.x
• From 2.0 to 2.1
• From 1.x to 2.x

Upgrade from Virtual Bugzilla Server version 3.2.2 or earlier to version 3.4

Upgrade from VBS 3.2.2 to VBS 3.4 is not much different from other VBS upgrades. It boils down to:

• Installing a blank new VBS server;
• Extracting data and configuration from the old VBS server;
• Putting the data and configuration into the new VBS;
• Upgrading the data and checking the configuration.

1. Install VBS 3.4 into a separate folder

   Do not overwrite old VBS!

2. Start old and new Bugzilla servers

   Use VMWare Player or Workstation to open and start both old VBS and new VBS. When new VBS starts, write down its IP address, which is shown in Bugzilla URL. If needed, configure network on the new server.

3. Login to the VBS 3.2.2 using 'bugzilla' account

   Use console, shown in the VMWare window, or a SSH client. The password is 'bugzilla', unless it has been changed.

4. Make sure old VBS is not accessible

   If the old VBS is accessible while you are migrating data from it, someone may make changes which will be lost or will get in the way.

   The easiest way is to stop Apache web server:

   su - root -c "apache2 -k stop"
   when asked for a password, type 'root'

5. Back up MySQL database

   Database dump contains all user data from Bugzilla. To create it, use mysqldump utility:
   

   mysqldump -uroot --add-drop-table --disable-keys bugs >/tmp/bugs.sql

6. Create backup of local Bugzilla configuration

   Use the following commands:

   cd /home/bugzilla
   tar cf /tmp/bugzilla-data.tar --exclude=data/template localconfig data
   

7. Create backup of your custom config files

   If you have customized Virtual Bugzilla Server somehow, create a tar archive with your custom configuration files. You will then unpack and apply them on the new server.

8. Transfer backup files to the new VBS

   Use command:

   cd /tmp
   scp *.sql *.tar bugzilla@ IP_address_of_the_new_VBS:/tmp

   When asked about authenticity, enter yes.
   When asked for password, enter bugzilla — the default password for bugzilla account on the new VBS.

9. Login to the new VBS

   Use root account with default password being root as well. You can login on console or use SSH client.

10. Verify that backup files have been transferred

    cd /tmp
    ls -l *.sql *.tar

11. Drop and create mysql database

    mysql -e 'drop database bugs'
    mysql -e 'create database bugs character set utf8'

12. Import data into mysql database

    Command: mysql bugs <bugs.sql

13. Unpack bugzilla configuration files

    su - bugzilla
    tar xf /tmp/bugzilla-data.tar

    It's probable that you will see warnings about time stamps — ignore them.

14. (Optionally) Edit localconfig

    You probably need to change database access parameters in localconfig file: db_name, db_user and db_pass.

    Use joe localconfig to launch file editor and make arbitrary changes.

15. Run checksetup.pl

    Run checksetup.pl, the Bugzilla's installation and upgrade uberscript.

    ./checksetup.pl

16. Change urlbase parameter

    At last, you need to change the urlbase parameter in data/params file.

    If your old VBS is still using numerical URL (with IP address), you can try this:
    logout     (going back from "bugzilla" to "root" account)
    /vbs/update-bugzilla-urlbase.sh

    Otherwise, edit data/params manually.

17. Move other configuration files that you have changed on the old VBS

    Other configuration files, like Apache and MySQL setup may be moved in the same way.

18. Done!

    This is it. If there were no errors during the upgrade, you should now be able to access new Bugzilla with your old data and settings.

A few things to do after the upgrade

• Check that e-mail sending works. If necessary, tweak Bugzilla configuration;
• Back up your new VBS;
• Do not delete your old VBS! That's your latest backup at this moment.

If something went wrong

• Try once more from scratch;
• Ask for help at our community forums;
• Consider commercial support options (by Everything Solved, Inc).

Upgrade Virtual Bugzilla Server from version 2.1 or earlier to version 3.2.2

Upgrade from VBS 2.x to VBS 3.2.x is not much different from other VBS upgrades. It boils down to:

• Installing a blank new VBS server;
• Extracting data and configuration from the old VBS server;
• Putting the data and configuration into the new VBS;
• Upgrading the data and checking the configuration.

NB: Virtual Bugzilla 3.2 doesn't come with Testopia. If you use Testopia on VBS 2.x, look out for Virtual Testopia Server.

1. Install VBS 3.2.x into a separate folder

   Do not overwrite old VBS!

2. Start old and new Bugzilla servers

   Use VMWare Player or Workstation to open and start both old VBS and new VBS. When new VBS starts, write down its IP address, which is shown in Bugzilla URL. If needed, configure network on the new server.

3. Login to the VBS 2.x using 'bugzilla' account

   Use console, shown in the VMWare window, or a SSH client. The password is 'bugzilla', unless it has been changed.

4. Make sure old VBS is not accessible

   If the old VBS is accessible while you are migrating data from it, someone may make changes which will be lost or will get in the way.

   The easiest way is to stop Apache web server:

   su - root -c "apache2 -k stop"
   when asked for a password, type 'root'

5. Back up MySQL database

   Database dump contains all user data from Bugzilla. To create it, use mysqldump utility:
   

   mysqldump -uroot -proot --add-drop-table --disable-keys bugs >/tmp/bugs.sql

6. Create backup of local Bugzilla configuration

   Use the following commands:

   cd /home/bugzilla
   tar cf /tmp/bugzilla-data.tar --exclude=data/template localconfig data
   

7. Create backup of your custom config files

   If you have customized Virtual Bugzilla Server somehow, create a tar archive with your custom configuration files. You will then unpack and apply them on the new server.

8. Transfer backup files to the new VBS

   Use command:

   cd /tmp
   scp *.sql *.tar bugzilla@ IP_address_of_the_new_VBS:/tmp

   When asked about authenticity, enter yes.
   When asked for password, enter bugzilla — the default password for bugzilla account on the new VBS.

9. Login to the new VBS

   Use root account with default password being root as well. You can login on console or use SSH client.

10. Verify that backup files have been transferred

    cd /tmp
    ls -l *.sql *.tar

11. Drop and create mysql database

    mysql -e 'drop database bugs'
    mysql -e 'create database bugs character set utf8'

12. Import data into mysql database

    Command: mysql bugs <bugs.sql

13. Unpack bugzilla configuration files

    su - bugzilla
    tar xf /tmp/bugzilla-data.tar

    It's probable that you will see warnings about time stamps — ignore them.

14. (Optionally) Edit localconfig

    You probably need to change database access parameters in localconfig file: db_name, db_user and db_pass.

    Use joe localconfig to launch file editor and make arbitrary changes.

15. Run checksetup.pl

    Run checksetup.pl, the Bugzilla's installation and upgrade uberscript.

    ./checksetup.pl

16. Change urlbase parameter

    At last, you need to change the urlbase parameter in data/params file.

    If your old VBS is still using numerical URL (with IP address), you can try this:
    logout     (going back from "bugzilla" to "root" account)
    /vbs/update-bugzilla-urlbase.sh

    Otherwise, edit data/params manually.

17. Move other configuration files that you have changed on the old VBS

    Other configuration files, like Apache and MySQL setup may be moved in the same way.

18. Done!

    This is it. If there were no errors during the upgrade, you should now be able to access new Bugzilla with your old data and settings.

A few things to do after the upgrade

• Check that e-mail sending works. If necessary, tweak Bugzilla configuration;
• Back up your new VBS;
• Do not delete your old VBS! That's your latest backup at this moment.

If something went wrong

• Try once more from scratch;
• Ask for help at our community forums;
• Consider commercial support options (by Everything Solved, Inc).

Upgrade Virtual Bugzilla Server from version 2.0 to version 2.1

Upgrade from VBS 2.0 to VBS 2.1 is not much different from other VBS upgrades. It boils down to:

• Installing a blank new VBS server;
• Extracting data and configuration from the old VBS server;
• Putting the data and configuration into the new VBS;
• Upgrading the data and checking the configuration.

This upgrade guide is not as thorough as instructions for upgrading VBS 1.x to 2.x, to which you can refer if you get lost in the process.

1. Install VBS 2.1 into a separate folder

   Do not overwrite old VBS! If you are upgrading VBS with Testopia, don't forget to install Testopia add-on on VBS 2.1.

2. Start old and new Bugzilla servers

   Use VMWare Player or Workstation to open and start both old VBS and new VBS. When new VBS starts, write down its IP address, which is shown in Bugzilla URL.

3. Login to the old VBS using 'bugzilla' account

   Use console, shown in the VMWare window, or a SSH client. The password is 'bugzilla', unless it has been changed.

4. Make sure old VBS is not accessible

   If the old VBS is accessible while you are migrating data from it, someone may make changes which will be lost or will get in the way.

   The easiest way is to stop Apache web server:

   su - root -c "apache2 -k stop"
   when asked for a password, type 'root'

5. Back up MySQL database

   Database dump contains all user data from Bugzilla. To create it, use mysqldump utility:
   

   mysqldump -uroot -proot --add-drop-table --disable-keys bugs >/tmp/bugs.sql

   If using Testopia:

   mysqldump -uroot -proot --add-drop-table --disable-keys testopia >/tmp/testopia.sql

6. Create backup of local Bugzilla configuration

   Use the following commands:

   cd /home/bugzilla
   tar cf /tmp/bugzilla-data.tar --exclude=data/template localconfig data
   

   If using Testopia:

   cd /testopia
   tar cf /tmp/testopia-data.tar --exclude=data/template localconfig data
   

7. Create backup of your custom config files

   If you have customized Virtual Bugzilla Server somehow, create a tar archive with your custom configuration files. You will then unpack and apply them on the new server.

8. Transfer backup files to the new VBS

   Use command:

   cd /tmp
   scp *.sql *.tar bugzilla@ new.VBS.IP.address:/tmp

   When asked about authenticity, enter yes.
   When asked for password, enter bugzilla — the default password for bugzilla account on the new VBS.

9. Login to the new VBS

   Use account bugzilla/bugzilla. You can login on console or use SSH client.

10. Verify that backup files have been transferred

    cd /tmp
    ls -l *.sql *.tar

11. Drop and create mysql database

    mysql -uroot -proot -e 'drop database bugs'
    mysql -uroot -proot -e 'create database bugs character set utf8'

    If importing Testopia, use the same commands to recreate database testopia.

12. Import data into mysql database

    Command: mysql -uroot -proot bugs <bugs.sql

    For testopia: mysql -uroot -proot testopia <testopia.sql

13. Unpack bugzilla configuration files

    cd /bugzilla
    tar xf /tmp/bugzilla-data.tar

    For Testopia:

    cd /testopia
    tar xf /tmp/testopia-data.tar

    It's probable that you will see warnings about time stamps — ignore them.

14. (Optionally) Edit localconfig

    You probably need to change database access parameters in localconfig file: db_name, db_user and db_pass.

    Use joe localconfig to launch file editor and make arbitrary changes.

15. Run checksetup.pl

    Run checksetup.pl, the Bugzilla's installation and upgrade uberscript.

    cd /bugzilla
    ./checksetup.pl

    For Testopia:

    cd /testopia
    ./checksetup.pl

16. Change urlbase parameter

    At last, you need to change the urlbase parameter in data/params file.

    If your old VBS is still using numerical URL (with IP address), you can try to run this command: /vbs/update-bugzilla-urlbase.sh:

    Otherwise, edit data/params manually.

17. Move other configuration files that you have changed on the old VBS

    Other configuration files, like Apache and MySQL setup may be moved in the same way.

18. Done!

    This is it. If there were no errors during the upgrade, you should now be able to access new Bugzilla (Testopia) with your old data and settings.

A few things to do after the upgrade

• Check that e-mail sending works. If necessary, tweak Bugzilla configuration;
• Back up your new VBS;
• Do not delete your old VBS! That's your latest backup at this moment.

If something went wrong

• Try once more;
• Ask for help at our community forums.

How to upgrade Virtual Bugzilla Server from version 1.x to version 2.x

Virtual Bugzilla Server 2.0 is a completely rebuilt product. Briefly, upgrading from previous versions boils down to:

• Install VBS 2.0 in a new directory and start it;
• Back up files on the old version of VBS;
• Transfer files to the new VBS;
• Use backup files to restore database and configuration on the new VBS.

This how-to explains the upgrade process in detail. By default, we assume that you are upgrading from version 1.2. When actions are different for VBS 1.0 and 1.1, there are special notes.

1. Install VBS 2.0 into a separate folder

   Do not overwrite old VBS!

2. Start old and new Bugzilla servers

   Use VMWare Player or Workstation to open and start both old VBS and new VBS. When new VBS starts, write down its IP address, which is shown in Bugzilla URL.

3. Login to the old VBS using 'bugzilla' account

   Use console, shown in the VMWare window, or a SSH client. The password is 'bugzilla', unless it has been changed.

4. Make sure old VBS is not accessible

   If the old VBS is accessible while you are migrating data from it, someone may make changes which will be lost or will get in the way.

   The easiest way is to stop Apache web server.
   

5. Verify that your current directory is /home/bugzilla

   Use pwd command.
   

6. Create database dump

   Database dump contains all user data from Bugzilla. To create it, use mysqldump utility:
   

   VBS 1.2:	mysqldump -uroot -pmysql --add-drop-table --disable-keys bugs >bugs.sql
   VBS 1.0, 1.1:	mysqldump -uroot -pmysql --add-drop-table --disable-keys bugz220 >bugs.sql

   

   "mysql" is the default mysql root password and may have changed.

7. Create backup of local Bugzilla configuration

   Use the following commands:

   cd bugzilla (on VBS 1.0 and 1.1: cd bugz220)
   tar cf ../bugzilla-data.tar --exclude=data/template localconfig data
   cd ..
   

8. Create backup of your custom config files

   If you have customized Virtual Bugzilla Server somehow, create a tar archive with your custom configuration files. You will then unpack and apply them on the new server.

9. Transfer backup files to the new VBS

   Use command: scp bugs.sql bugzilla-data.tar bugzilla@ new.VBS.IP.address:
   

   

   When asked about authenticity, enter yes.
   When asked for password, enter bugzilla — the default password for bugzilla account on the new VBS.

10. Login to the new VBS

    Use account bugzilla/bugzilla. You can login on console or use SSH client.

11. Verify that backup files have been transferred

    ls -l bugs.sql bugzilla-data.tar

    

12. Drop and create mysql database

    You need to drop and create again mysql database bugs:

    mysql Цuroot Цproot Цe 'drop database bugs'
    mysql Цuroot Цproot Цe 'create database bugs character set utf8'

    VBS 1.0 and 1.1: Use character set that has been used on your old mysql database. This is important if you have non-Latin characters in bugs.

    

13. Import data into mysql database

    Command: mysql -uroot -proot bugs <bugs.sql

    

14. Unpack bugzilla configuration files

    Command: tar xf bugzilla-data.tar

    It's probable that you will see warnings about time stamps — ignore them.

    

15. (Optionally) Edit localconfig

    You probably need to change database access parameters in localconfig file: db_name, db_user and db_pass. You definitely need to change them if you are upgrading from VBS 1.0 or 1.1.

    To quickly change database access parameters from bugz220 to bugs, you can use command sed -i 's/bugz220/bugs/' localconfig. Use joe localconfig to launch file editor and make arbitrary changes.

16. (Optionally) Recode database

    If you are migrating from database not in UTF-8 charset, you need to re-code the database. Use this command:
    contrib/recode.pl --charset= original_database_charset

17. Run checksetup.pl

    Run checksetup.pl, the Bugzilla's installation and upgrade uberscript.

    

    At some point, the script will ask you to confirm database conversion. Press ENTER to continue. Don't worry about the warning, you still have your old VBS as a backup.

    

    When checksetup.pl finishes, the screen should look like this:

    

18. Change urlbase parameter

    At last, you need to change the urlbase parameter in data/params file.

    If your old VBS is still using numerical URL (with IP address), you can try to run this command: /vbs/update-bugzilla-urlbase.sh:

    

    Otherwise, edit data/params manually.

19. Congratulations!

    This is it. If there were no errors during the upgrade, you should now be able to access new Bugzilla with your data.

A few things to do after the upgrade

• Check that e-mail sending works. If necessary, tweak Bugzilla configuration;
• If you were using national characters, make sure they are displayed correctly in the new VBS. If needed, turn on "utf8" option in "Parameters" section of Bugzilla configuration;
• Back up your new VBS.