Options for backing-up data prior to in-place migration

The migration process for Blueworx Voice Response Version 7 will not affect your existing system or application data. However, you should always make a backup of your data prior to starting the migration process, so that you can recover if any problems are encountered. This is particularly important if you are migrating from a previous release in-place.

Making a backup using mksysb

The safest option is to backup a complete image of your system by using the mksysb command. Although this can take a long time, it ensures that, if you do encounter problems during installation, you can easily get back to the point from which you started. Details of how to use the mksysb command can be found in the https://www.ibm.com/support/knowledgecenter/.

Note: You can use the savevg command to back up other volume groups.

Making a backup using saveDT

An alternative method of backing-up data is to use the Blueworx Voice Response saveDT utility. However, unlike mksysb, this backs up only the application data, so if you encounter any problems during installation, you would need to separately reinstall the level of Blueworx Voice Response that you had been previously using, and then use the restoreDT utility to recover the data. In addition, the following types of data are not backed-up by the saveDT utility:

Java and VoiceXML applications.
Backing up $DTJ_DIR/default.cff is critical
AIX_file objects.
The supplied help text files, which are replaced with a new set during migration.
Any changes you may have made to the Blueworx Voice Response resource files. If, for example, you made color or font changes, you have to make the same changes again.
Your values for any system configuration parameters. These may have a new default value in Blueworx Voice Response Version 7, and the new default value would overwrite the value you have been using.
Information about Single System Image clusters. If you have a Single System Image configuration you will need to recreate your cluster after the save-and-restore process.
Custom server data that is not in the custom server directory (ca/custom_server_name) or in ca/bin.
Current reports and log files. If you want to save your current statistics data you must archive it first, as described in Archiving your reports and log files.

For detailed information about backing up data using saveDT, see Backing-up your data using saveDT.