Migration From Breeze Agent 1.x to 3.x

Breeze Agent 3.x is designed to be a drop‑in successor to 1.x. This guide outlines how to migrate from Breeze Agent 1.x to 3.x, including planning, rollout options, upgrade steps, and post-migration validation.

Prerequisites

Before you begin:

• Confirm that target hosts meet the Breeze Agent Requirements and any internal policies (change management, backups, approvals).
• Ensure outbound HTTPS over TCP 443 from each host to Cloudaware and access to cloud instance metadata (for example, 169.254.169.254 in public clouds).
• Decide whether you will upgrade in place or run 3.x side‑by‑side with 1.x during a transition period.

Migration Patterns

• In‑place upgrade – install the 3.x agent on hosts currently running 1.x; the installer replaces the existing agent and 3.x then self‑updates going forward.
• Side‑by‑side rollout – deploy 3.x to a pilot set of hosts or environments first (for example, non‑production), then expand to the rest of the fleet in waves.
• Platform‑specific automation – use your existing tooling (for example, configuration management, software distribution, or Mobile Device Management (MDM) software such as Jamf for macOS) to push the 3.x installer.

Example High‑Level Steps

• Linux/macOS

  • Download the latest 3.x installer from Cloudaware Admin → DevOps → Breeze.
  • Deploy and run the installer script under root/sudo on target hosts.
  • Verify breeze status and breeze version on a sample of machines.

• Windows

  • Download the signed 3.x installer executable from the Breeze integration.
  • Roll out via your software distribution tool or group policy.
  • Verify that the Breeze scheduled task is present and reporting.

• Kubernetes

  • Update the Breeze DaemonSet manifests or Helm release to use the 3.x image or package.
  • Roll out gradually across clusters and nodes, monitoring CMDB data and agent health.

Post‑Migration Validation

• Confirm that hosts still appear in Cloudaware CMDB and that OS-level facts are updating as expected.
• Spot‑check key modules (for example, vulnerability scanning, patch management, IDS) on upgraded hosts.
• Review the 3.x Changelog and the core Breeze Agent 1.x Changelog for any behavior changes that may affect your environment.

If you encounter issues, refer to the Troubleshooting guide or contact Cloudaware Support.