Table of contents
- 2. You can run the installer to upgrade from earlier versions of Amanda Enterprise 3.3.x. Please make sure you preserve configuration and data if you decide to uninstall earlier version of Amanda Enteprise 3.3.x and install Amanda Enterprise 3.3.8 If you are backing up VMware using Amanda Enterprise VMware agent, you should upgrade VDDK libraries to 5.1.1 version (if you have not already done so). VDDK 5.1.1 can be obtained from Zmanda Network.
- 3. It is not possible to automatically upgrade configurations from Amanda Enterprise 3.1.5 to Amanda Enterprise 3.3.8. You will have to create backup sets in 3.3.8 similar to 3.1.5. Since there are significant changes in device configurations, backup set and device configuration has to be manually. Zmanda support can provide a migration tool to migrate all client configurations (ZMC Backup What) from 3.1.5 backup set to 3.3.8 backup set. The backup images will be created using Amanda Enterprise 3.1.5 will be recoverable using Amanda commands.
- 4.
Do NOT use package upgrade option to upgrade to 3.3.8 Uninstall the old package and install 3.3.8 client packages. For rpm based installations, use the following commands: rpm -e <amanda enterprise client extension package> rpm -e <amanda enterprise client package> rpm -i amanda_enterprise-backup_client-3.3.8-1.* rpm -i amanda_enterprise-extensions-client-3.3.8-1* For debian/ubuntu installations, use the following commands: dpkg --remove <amanda enterprise client extension package> dpkg --remove <amanda enterprise client package> dpkg --install amanda-enterprise-backup-client_3.3.8* dpkg --install amanda-enterprise-extensions-client_3.3.8* On MacOS X, Install the package by double clicking on the disk image (.dmg) for the client and extensions packages.
- 4.1.1. New Features in 3.3
- 4.1.2. Documentation
- 5.
For a full list of supported platforms please review the compatibility guide here.
Amanda Enterprise 3.3 documentation provides detailed information on how to install and configure Amanda server and client on these platforms.
- 5.1.1. Known Issues in 3.3.8
Amanda Enterprise 3.3.8 provides new functionality and fixes issues reported by Amanda Enterprise customers.
Upgrading from Amanda Enterprise 3.3.x
You can run the installer to upgrade from earlier versions of Amanda Enterprise 3.3.x. Please make sure you preserve configuration and data if you decide to uninstall earlier version of Amanda Enteprise 3.3.x and install Amanda Enterprise 3.3.8
If you are backing up VMware using Amanda Enterprise VMware agent, you should upgrade VDDK libraries to 5.1.1 version (if you have not already done so). VDDK 5.1.1 can be obtained from Zmanda Network.
Upgrading Amanda Enterprise 3.1.5 server to 3.3.8
- It is not possible to automatically upgrade configurations from Amanda Enterprise 3.1.5 to Amanda Enterprise 3.3.8. You will have to create backup sets in 3.3.8 similar to 3.1.5. Since there are significant changes in device configurations, backup set and device configuration has to be manually. Zmanda support can provide a migration tool to migrate all client configurations (ZMC Backup What) from 3.1.5 backup set to 3.3.8 backup set.
- The backup images will be created using Amanda Enterprise 3.1.5 will be recoverable using Amanda commands.
Upgrading Amanda Enterprise Linux/Mac OS X/Solaris Clients to 3.3.8
- Do NOT use package upgrade option to upgrade to 3.3.8 Uninstall the old package and install 3.3.8 client packages.
- For rpm based installations, use the following commands:
- rpm -e <amanda enterprise client extension package>
- rpm -e <amanda enterprise client package>
- rpm -i amanda_enterprise-backup_client-3.3.8-1.*
- rpm -i amanda_enterprise-extensions-client-3.3.8-1*
- For debian/ubuntu installations, use the following commands:
- dpkg --remove <amanda enterprise client extension package>
- dpkg --remove <amanda enterprise client package>
- dpkg --install amanda-enterprise-backup-client_3.3.8*
- dpkg --install amanda-enterprise-extensions-client_3.3.8*
- On MacOS X,
- Install the package by double clicking on the disk image (.dmg) for the client and extensions packages.
- rpm -e <amanda enterprise client extension package>
- rpm -e <amanda enterprise client package>
- rpm -i amanda_enterprise-backup_client-3.3.8-1.*
- rpm -i amanda_enterprise-extensions-client-3.3.8-1*
- dpkg --remove <amanda enterprise client extension package>
- dpkg --remove <amanda enterprise client package>
- dpkg --install amanda-enterprise-backup-client_3.3.8*
- dpkg --install amanda-enterprise-extensions-client_3.3.8*
- Install the package by double clicking on the disk image (.dmg) for the client and extensions packages.
New Features in 3.3
- Amanda Enterprise server and client support for newer versions of Ubuntu, Debian, RHEL and Fedora distributions. See Supported Platform matrix for list of distributions supported.
- Support for Ubuntu 9.04, Fedora 8 and 9 have been dropped.
- Support for new Amazon S3 cloud features and new locations (such as Oregon, Sao Paulo/Brazil).
- Support for Google Enterprise Cloud.
- Significant enhancements to ZMC and ZMC processes.
- Significant changes in the configuration of disk and cloud devices. ZMC automatically determines the slot information. This change simplifies the device configuration.
- Support for Multiple drives in a tape library in the same backup set.
- Parallel backups and recovery in a backup set.
- Support for Linux databases - Oracle and Postgres.
- Support for Windows and Windows applications.
- Support for Solaris clients.
- Selective backup and recovery of MS SQL servers and MS Exchange.
- Significant improvements to vaulting - more vaulting options, better monitoring
- Ability to backup all Windows local drives using one backup object.
- Support AES 256 bit encryption on Windows client.
- SQL server backups and recovery are done using SQL VDI not VSS interface.
- Zmanda Windows Client uses MariaDB InnoDB storage engine for catalog. Windows client catalog can be recovered faster with this change. The database will use more disk space (20% more in general) compared to earlier release.
- Zmanda Windows Client can be also installed on Hyper-V Core Server installation to perform backups of Hyper-V VMs.
- Support for starting backup of specific backup object (DLE) in a backup set
- Support for Solaris/x86 server and Solaris/Sparc client. All Amanda binaries and files are stored on the Solaris server under /opt/zmanda/amanda directory.
- ZMC provides restore reports and also allow users to search the catalog using wild card characters and restore files/folders.
- The VMware backups are significantly faster. They do not use additional disk space.
- The Amanda catalog is stored in MariaDB database.
- The PostgreSQL server backups do not require additional disk space to store backups in the client. The backups are directly streamed to the Amanda server. To support this feature, GNU tar 1.20 or later should be installed on PostgreSQL server. Please continue using Amanda 3.3.5 client to backup PostgreSQL server if GNU tar 1.20 or later is not available for the client OS/distribution.
- Additional information about SQL server recovery model is shown in the ZMC Backup What page.
Documentation
For a full list of supported platforms please review the compatibility guide here.
Amanda Enterprise 3.3 documentation provides detailed information on how to install and configure Amanda server and client on these platforms.
Known Issues in 3.3.8
-
Amanda Enterprise backup server 3.3.8 is not available on Solaris/Sparc platform and does not support single tape drive without a changer. Please use Amanda Enterprise 3.1.5 for these configurations.
-
NDMP restores of EMC appliances will not work if DAR is enabled. Please remove DIRECT=Y from /etc/amanda/<backup set name>/index/127.0.0.1/*/<datestamp>_<level>.state before running restore job from ZMC.
-
Hyper-V discovery in ZMC Backup What page displays virtual disks. But, virtual disks cannot be backed up individually as an backup object. Complete virtual machine has to be backed up.