Skip to main content

Migration From Breeze Agent 1.x to 3.x

Breeze Agent 3.x is a separate agent that is installed next to Breeze Agent 1.x, not an in-place upgrade of it. A host migrates in two steps: Breeze Agent 3.x is installed and starts reporting, and then Breeze Agent 1.x is removed.

There are two ways to migrate:

You choose the path and when to migrate. You can migrate some hosts and keep others on Breeze Agent 1.x.

Step 1: Check Feature Availability​

Do this first, whichever path you choose. Not every Breeze Agent 1.x capability is available on 3.x yet. In particular, patch management is not available on Breeze Agent 3.x yet.

  1. Review Feature Availability.
  2. List the capabilities the hosts you plan to migrate use.
  3. Keep on Breeze Agent 1.x every host that uses a capability marked Planned or Not available.

If you are not sure which capabilities your hosts use, contact Cloudaware Support before you migrate.

How Migration Works​

  • Side-by-side installation. Breeze Agent 3.x installs into its own directory, and both agents run on the host until 1.x is removed.

    Breeze Agent 1.xBreeze Agent 3.x
    Linux/opt/breeze-agent/opt/cloudaware/breeze
    WindowsC:\Program Files\BreezeC:\Program Files\Cloudaware\Breeze

  • The host keeps its identity. Breeze Agent 3.x registers the host under the same identity as Breeze Agent 1.x, so the host stays the same object in Cloudaware CMDB.

  • No configuration is carried over. The 3.x installer contains its own certificate. If Breeze Agent 1.x uses a proxy, a custom CA bundle, or other settings, configure them for 3.x. See Configuration.

  • Linux and Windows only. macOS hosts are not supported for migration to Breeze Agent 3.x.

Get the Installer​

A Breeze Agent 3.x installer is built for each Cloudaware account. Both paths start with one.

  • Install it yourself: ask Cloudaware Support to build an installer for your account. When it is ready, it appears in Cloudaware Admin → DevOps → Breeze.
  • Cloudaware-run migration: Cloudaware builds the installer and stages it for your hosts. You do not need to download it.

If your hosts reach the internet through a proxy, tell Cloudaware Support, so the installer can be built with your proxy. See Install Behind a Proxy.

Install Breeze Agent 3.x Yourself​

Before you start, complete Step 1: Check Feature Availability.

  1. Download the installer from Cloudaware Admin → DevOps → Breeze. See Download the Installer.
  2. Install on a few pilot hosts by following Installation. Breeze Agent 1.x keeps running while you do.
  3. Verify the pilot hosts. See Verify the Migration.
  4. Roll out to the remaining hosts in waves, with your usual tools: for example, AWS Systems Manager, SCCM, Intune, or Ansible. On Windows, use the -gm2 option for a silent installation.
  5. Remove Breeze Agent 1.x from each host once Breeze Agent 3.x is reporting. Either:

Until Breeze Agent 1.x is removed, both agents run on the host.

Cloudaware-Run Migration​

Before you start, complete Step 1: Check Feature Availability, and agree with Cloudaware Support which hosts to migrate.

  1. Cloudaware installs Breeze Agent 3.x on a pilot set of hosts. Breeze Agent 1.x downloads the installer and installs Breeze Agent 3.x next to itself on its next scheduled run, within about 15 minutes. A host that already has Breeze Agent 3.x installed is left as it is.
  2. You and Cloudaware verify the pilot hosts, then Cloudaware extends the installation to the remaining hosts. See Verify the Migration.
  3. Cloudaware removes Breeze Agent 1.x. The removal runs from Breeze Agent 3.x, so it only happens on hosts where 3.x is installed and reporting. It takes two runs of Breeze Agent 3.x, normally about 15 minutes apart:
    1. The first run removes the Breeze Agent 1.x scheduled task. Breeze Agent 1.x stays on the disk but no longer runs.
    2. The next run deletes the Breeze Agent 1.x directory.

Between the two runs, a host with Breeze Agent 1.x present but not scheduled is expected.

Verify the Migration​

On each pilot host, and on a sample of hosts in each wave:

  1. Check that Breeze Agent 3.x is scheduled and has run. Load the agent environment and run breeze version and breeze scheduler status, then check var/log/breeze.log for the latest run. See Verify the Installation.
  2. Check Cloudaware CMDB. Confirm that the host is still present and that its OS-level facts are updating.
  3. Check the modules you use on the host, for example Vulnerability Management or Intrusion Detection.
  4. After Breeze Agent 1.x is removed, confirm that its directory is gone:
    • Linux: /opt/breeze-agent
    • Windows: C:\Program Files\Breeze

If a check fails, run breeze troubleshoot and contact Cloudaware Support with its output.

On this page