Cryptzone Support

If you wish to submit a support ticket please sign in to your customer portal or use the “submit a ticket” button at the top menu.
If you need to find documentation about our Sheriff Suite please login to the Hive- Click Here




« Go Back


individual backups from nodes in a cluster contain the local files, local to the node, as listed in the backup list. Local files with same path and name can differ from node to node. Thus backing up individual nodes creates a backup from the cluster configuration with the files from that node.

Restoring a backup will spread the files from the backup-list over all nodes in the cluster. This means the files which were individual to a certain node will be spread over all other nodes. Thus, if the file & path are the same but content different, you can not restore only one particular node (applied to all).

Restoring into a cluster will spread all the files on all cluster members. Which means for all files listed in backup-list. If the files on many nodes use same filename but it's  content differ, you will need to do one of the following:
- Change the name of the file so that cluster members do not share file&path name
- Change your configuration to use the new file name (for the ones changed)
- Add the files (or directory) to distd.

If there is no possibility of changing file name:
Create a directory in /var/opt/appgate/local/backup/nodeX/ and copy the files per node into the node specific directory. Add /var/opt/appgate/local/backup/ to distd and backup list. Copy the files into the directory after they have been modified. Create a text file, or script, which tells you, or can be run, where to put the files on the node. A restore will require to manually copy the files on every node into it's place, or run the script doing it.

Restoring from a cluster-member into a single appliance works as expected.

Clone a Cluster from backups

If you want to create a new cluster from existing backups, you would need do it in the following order:

1. restore node 1 on new unclustered appliance A
2. restore node 2 on new unclustered appliance B
3. Establish the cluster communication through cable connect

Now you can connect to the cluster and change the configuration for your target installation. Note that licenses are copied along and no not allow you to be used on cloned instances. For questions please contact

Further reading: Migrating to new HW


Article Info
3/13/2015 8:43 AM
3/13/2015 8:43 AM



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255