Please follow the steps below to migrate Amanda Enterprise 3.6 to 4.1.
Value for the field “Tape Drive Device” in “backup where” page of backup set linked to tape device, will not be migrated. Please remember to update it manually post migration.
If any configuration files within /etc/zmanda/zmc/zmc_ags/device_profiles/ or /etc/amanda have been manually modified or the extensions of any file within these directories have been modified, then their migration may not be successful. Please verify after migration.
# apt remove amanda-enterprise-backup-server
Please perform the following steps before performing migration. These steps will help with reattempting the migration, if there are any migration failures during the process.
1. Copy the backup set directories from /etc/amanda and device yaml files from /etc/zmanda/zmc/zmc_ags/device_profiles to any directory of your choice.
2. Copy the .am_passphrase file from /var/lob/amanda to preserve server encryption key.
o From within /etc/amanda:
o From within /etc/zmanda/zmc/zmc_ags/device_profiles:
[config backup dir] – path of the directory where the backup set directories and device yaml files have been backed up to.
5. Move all backup directories related to disk, vtape storage devices from /var/lib/amanda-1 to /var/lib/amanda.
Run the following command for each of the copied directories:
o chown -R amandabackup:amandabackup [copied directories]
6. Run the following cmd:
o cat /var/lib/amanda-1/.am_passphrase>/var/lib/amanda/.am_passphrase
7. Run the following cmd[optional step]:
o cat zmc_migrate_fix>/usr/sbin/zmc_migrate
8. To migrate AWS devices which have storage class set as ONEZONE_IA or STANDARD_IA, perform the following changes in order to migrate such devices and the linked backup sets:
o Go to - /etc/zmanda/zmc/zmc_ags/device_profiles
o Open the yml file corresponding to the concerned AWS device
o Update the value of the field S3_STORAGE_CLASS to STANDARD or REDUCED_REDUNDANCY.
All the operations stated below are to be run as root user.
1. Install 4.1 binaries both AE server and ZMC UI binaries by following Installation Guide to update the link
[Note: Mt-st is required to be installed before installing the Server binaries, in order to use Tapes storage. In case if mt-st is installed later, then make sure to run "setup-aee" utility as root user]
2. Login to the Zmanda console, upload the license and add to the cluster, IP of the machine on which the server binaries have been installed.
[Please note that the migration script will not work unless license file is uploaded]
[Caution: the license must be as per the features supported by that of 3.6 license]
3. Apply 4.1.0.106 patch by installing ZMC and Backup Server binaries
i. For RPM Based Systems(CentOS/RHEL/Fedora/SUSE)
a. Install the latest 4.1.0.106 patch binaries by using,
i. # ./patch-backup-server-4.1.0.106x64.run
ii. # ./patch-zmc-4.1.0.106-x64.run
ii. For Debian Based Systems (Ubuntu/Debian)
a. Uninstall the 4.1.0.18 Backup Server and ZMC binaries by using,
i. /opt/zmanda/amanda/zmanda-zmc-pkg/uninstall
ii. / opt/zmanda/amanda/zmanda-backup-pkg/uninstall
b. Install the 4.1.0.106 patch binaries by using,
i. # ./
ii. # ./patch-zmc-4.1.0.106-x64.run
4. Run the command –
o zmc_migrate
o Inputs[to be entered in this order]:
§ Admin level username
§ Password for the user
§ IP of the machine on which the Zmanda console is present
§ Port of that machine
§ Cluster Id corresponding to the server on which the migration script is being run
Following operations/edits are necessary to successfully complete the migration:
In case the migration run fails please include the timestamp which is printed right above the part where you are prompted to enter the “username”, or the one which is printed at end of the migration run.
When triggering restore of a backup which had client side encryption enabled, make sure that the contents of the “.am_passphrase” file from the client side is temporarily copied into the “.am_passphrase” file on the server. This change needs to be reverted once the restore is completed.