Upgrade strategies from ZMC 5.0 to 5.1 to ensure safe migrations

Problem

During the upgrade of Zmanda EBR from version 5.0 to 5.1, some configuration folders are retained, leading to migration issues. These directories may affect future upgrades as well.

Cause

The existing aee4 and zmc4 configurations can lead to symbolic link issues, subsequently corrupting the symbolic links within the actual config folders zmc5 and aee5.

Solution

To ensure a smooth upgrade and avoid future issues, follow these steps:

  1. Before upgrading:

    • Identify configuration folders: Locate the configuration folders aee4, installed alongside the backup server and zmc4 installed alongside Zmanda Management Console (ZMC), typically situated in the directory /etc/zmanda.

    • Back up existing configuration: If necessary, create a backup of the aee4 and zmc4 folders for reference.

    • Remove old configurations: Safely remove the aee4 and zmc4 folders using the rm -rf command with caution.

  2. Upgrade Zmanda EBR: Proceed with the upgrade to version 5.1 following the official Zmanda documentation.

Note: The rm -rf command permanently deletes all files and folders within the specified directory. Use it only after verifying the correct folder paths and backing up essential data.

Additional Information

  • Who is affected? This issue applies to users upgrading from Zmanda EBR 5.0 to 5.1.

  • Impact of not removing folders: Failure to remove these folders might lead to service failures preventing Zmanda services from starting.

  • Data safety: Removing aee4 and zmc4 folders does not affect your actual configuration files. The relevant configurations are in aee5 and zmc5 folders.

By following these steps, you can ensure a smooth upgrade experience and avoid potential migration issues and service failures.

More Resources