Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos Space] How to migrate Junos Space Virtual Appliance from one VM to another VM



Article ID: KB36198 KB Last Updated: 08 Sep 2020Version: 2.0

This article explains the recommended method for migrating/relocating Junos Space Virtual Appliance. It discusses backing up Junos Space VM and relocating it by configuring network address as needed.


This article helps in backing up Junos Space DB, install a new VM and restore it with precautionary considerations.


There are many ways to migrate a VM from one host to another. It is not recommended to follow VMWare method eg: vMotion/cloning, as there are risks involved. For the issues that are faced during this process, it is out of scope as VMWare Application is not managed by JTAC. To understand the best practices for Junos Space VMWare, refer to KB35153 - Junos Space VMWare Best Practices.

The JTAC recommended method for Migrating Junos Space Application hosted on VM is to take a complete backup of your Junos Space environment including (Mysql + Pgsql) data from VM A and restore it on another VM B by creating a new VM instance with the same Platform and Application version.

Steps for migrating Junos Space hosted on a Virtual Appliance:

  1. Take a complete backup from the existing Junos Space Setup in VM A (Backing Up the Junos Space Network Management Platform Database).

  2. Deploy a new VM instance as VM B with the same version and make sure that resources allocated to it like RAM, CPU and Storage are similar or more when with the existing setup (Deploying a Junos Space Virtual Appliance on a VMware ESXi Server).

  3. Proceed with installation of Junos Space while installing the node. Be sure to choose "n" when the system asks the question below to build a Standalone node (Configuring a Junos Space Virtual Appliance as a Junos Space Node).

    • Eg: Will this Junos Space system be added to an existing cluster? [y/n]

  4. Once the installation completes, allow 10-15 mins for the packages to be deployed. Then you will see the login prompt (Web UI) while accessing the VIP.

  5. Log in using default credentials (username: super | password: juniper123). Install the application to match the existing Junos Space VM (Adding a Junos Space Application).

  6. After verifying the working of the node, restore the backed-up data on to this new setup (Restoring the Junos Space Network Management Platform Database) (Contact JTAC if restore postgres has any issues).

  7. Carry out further testing to ensure the system is working normal in the new environment.

  8. Power down the VM A and start using the VM B setup for further activities. 


    Whenever there is a change in Junos Space server management IP:

    • The connectivity between the Junos Space server IP and devices will be re-initiated again as long as “Junos Space initiates connection to device” is enabled in settings. The only pre-requisite is the Device IP should have SSH connectivity from Junos Space Management IP.

      Administration > Applications > Network Management Platform > Modify Application Settings

      Junos Space initiates connection to device  -This check box is selected by default, so Junos Space Platform initiates a connection with managed devices. To have managed devices initiate a connection with Junos Space Platform, clear this check box.

    • For collecting SNMP traps in the new VM instance, the SNMP trap target configuration on end device should be modified with new server details accordingly. Use Resync Nodes option under Network Monitoring to set the trap target configuration to your end device.This enables the devices to send their SNMP traps to the Junos Space VIP node.

    Steps 9 and 10 are specific to building a Junos Space cluster (Optional):

  9. To build a Junos Space Fabric cluster, deploy the second VM and add it to the existing setup. While installing the second node, follow the same procedure as installing the first node, but choose "y" when the system asks the question below (Deploying a Junos Space Virtual Appliance on a VMware ESXi Server).

    • Eg: Will this Junos Space system be added to an existing cluster? [y/n]

  10. Adding a node to an existing Junos Space Fabric (Adding a Node to an Existing Junos Space Fabric):

    Before you begin, the following prerequisites must be in place:

    • Multicast enabled on the switches to which Junos Space nodes are connected.
    • IGMP-snooping is disabled on the switches to which Junos Space nodes are connected. By default, IGMP-snooping is enabled on most switches.
    • All Junos Space nodes are interconnected using a high-speed (1-Gbps or 100-Mbps) network with a maximum latency not exceeding 300 milliseconds.

    If Multicast traffic is blocked in the VM environment, then unicast communication should be configured on the Junos Space node (Creating a Unicast Junos Space Cluster)

Note: Ensure no changes are done to devices from the Junos Space Network Management Platform or its application during the migration activity because the data that has been modified would be lost.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search