When upgrading an EX switch from older Junos releases that use the legacy MXOC Mist agent (for example, 21.4R3-S7) to a release that uses the Junos Mist Agent (JMA) (for example, 23.4R2-S7), the "Create a recovery snapshot post upgrade" option may fail to create the recovery snapshot. The issue occurs during the MXOC-to-JMA migration process and has been observed when the automatic post-upgrade recovery snapshot option is enabled in Mist.

• Upgrade completes successfully.
• The failure only occurs when the Create a recovery snapshot post upgrade option is selected during the upgrade workflow.
• 
• Recovery snapshot creation fails with errors similar to:

tar: var/db/scripts/jet/mxoc_*.py: Cannot stat: No such file or directory

ERROR: Failed to create Snapshot

• The switch remains online and connected to Mist.
• Some VC members may retain an older recovery snapshot version while others successfully create a new snapshot.

Old releases uses the legacy MXOC agent. During the upgrade, the switch automatically migrates from MXOC to JMA. If the automatic post-upgrade recovery snapshot process starts before the migration is fully completed, it may attempt to include MXOC files that have already been removed, causing the snapshot creation to fail.

{master:0}

mist@EX2300VC > show system commit | no-more 

0  2026-10-14 20:20:13 CET by mist via netconf commit confirmed, rollback in 10mins synchronize

  version=1792005359

1  2026-10-14 20:12:42 CET by mist via netconf commit confirmed, rollback in 10mins synchronize

  version=1792004414

2  2026-10-14 20:07:17 CET by mist via netconf commit synchronize

  annotate reg info

3  2026-10-14 20:05:11 CET by mist via netconf commit synchronize

  jma-init

4  2026-10-14 19:59:24 CET by mist via netconf commit confirmed, rollback in 10mins synchronize

  mist-pkg: configure jma pkg

5  2026-10-14 19:58:15 CET by mist via netconf commit synchronize

  mist-pkg: annotate reg info for jma pkg

6  2026-10-14 19:46:59 CET by root via other

Workaround:

1. Complete the upgrade normally.

2. Verify the JMA agent is installed:

{master:0}

mist@EX2300VC > show version | match mist | no-more 

JUNOS Mist Agent [v1.0.3059-8]

JUNOS Mist Agent [v1.0.3059-8]

JUNOS Mist Agent [v1.0.3059-8]

3. After the upgrade and migration have finished, manually create a new recovery snapshot.

4. Verify the snapshot was updated on all VC members: show system snapshot

Connect a Switch to Mist Cloud Through a Proxy Server Using CloudX | Mist | Juniper Networks

Junos OS Dates & Milestones - Juniper Networks