Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
Also, in case your network is not allowing multicast communication, try this:
We use Junos Space disaster recovery with our ESX setup
One site is primary one is secondary files are copied down to the secondary site every day and the seconday junos space server only takes over if their is a total failure at the primary location
You have to match memeory cpu's and hard drive space on the ESX host in both the primary and secondary sites
There is an official disaster recovery solution for Junos Space with a standby enviroment with database syncronization. The description can be found here:
In general you would only need licenses for Junos Space and Security Director on the primary/active installation. Doing the manual disaster recovery will import the licenses from the backup.
Right now I cannot find information on the full disaster recovery solution will require licenses on both sites. I will try to find out an update this thread if other people have not been able to answer before me.
Just got information back from internal ressources:
If you deploy a set of DR Space instances, these will need to be licensed as well as your primary site.
So a fabric of two space nodes on each site will require 4 x JS-PLATFORM licenses as well as application licenses on top (eg. JS-SECDIR-X).
Ideally, you would need JS-Platform license for each node in a Space Cluster or Fabric deployment.