Skip to main content
Version: 3.8.x.x LTS

Cloning a server

It can be helpful to clone a server when setting up a failover configuration. To do so, obtain the configuration of the server that needs to be cloned, modify the data structure to your needs and create a new server resource (refer to the chapter: Creating a new resource, for details).

Then, repeat these steps on the instance and service levels.

Prerequisites and known limitations​

  • The order of how objects are cloned is important (see next bullet).

  • A resource needs to exist before it can be assigned to any other resource.

    For example, the remote cache databases need to exist on the target server prior to assigning them to a nevisProxy instance. This means that you have to create/clone them first.

  • Certain resources cannot be cloned.

    This includes nevisKeybox, nevisAgent, and some of the less frequently used types such as nevisSign or nevisGate. You have to create them manually via the nevisAdmin GUI.

  • Key material cannot be cloned.

    Once you have created the clone server, we recommend that you take care of the necessary key material prior to adding any further resource. Either add (discover) key material to the keybox of the cloned server or use the nevisAdmin GUI to generate it. The keys for nevisAgent need to be generated in the GUI, too. If the key material is not present on the target server, it cannot be assigned using the REST API.