Back up and restore Citrix ADC instances
You can back up the current state of a Citrix Application Delivery Controller (Citrix ADC) instance and later use the backed-up files to restore the Citrix ADC instance to the same state. You must always back up an instance before you upgrade it or for just precautionary reasons. A backup of a stable system enables you to restore it back to a stable point if it becomes unstable. There are multiple ways to perform backups and restores on a Citrix ADC instance. You can manually backup and restore Citrix ADC configurations using the GUI, CLI, or you can use Citrix Application Delivery Management (Citrix ADM) to perform automatic backups and manual restores. Citrix ADM backs up the current state of your managed Citrix ADC instances by using NITRO calls and the Secure Shell (SSH) and Secure Copy (SCP) protocols.
Citrix ADM backs up and restores the following types of Citrix ADC instances:
- Citrix ADC SDX
- Citrix ADC VPX
- Citrix ADC MPX
For a Citrix ADC VPX instance, Citrix ADM backs up the files depending on the type of data to be backed up. You can create either a basic backup or a full backup.
You cannot perform the backup and restore operation on a Citrix ADC cluster.
- Basic backup: In this type, only configuration files are backed up as these are the files that change regularly. The following table lists the files that are backed up in the respective folders. Note that if a folder name is followed by a “*,” all files in that folder are backed up.
- Full backup: In this type, in addition to the files that are backed up by a basic backup, some less frequently updated files are also backed up. The following table lists the files that are backed up when using the full backup option:
The backed up files are stored as a compressed TAR file in the /var/ns_sys_backup/ directory. To avoid issues due to non-availability of disk space, you can save a maximum of 50 backup files in this directory. You can use the “rm system backup” command to delete existing backup files so that you can create more backups.
- You cannot use the backup file taken from one instance to restore a different instance.
- You can back up and restore instances in an HA setup. But ensure to restore the same instance from which the backup file was created. For example, if the backup was taken from the primary instance of the HA pair when restoring ensure you are restoring the same instance, even if it is no longer the primary instance.
To back up and restore Citrix ADC instances, you must first configure the backup settings on Citrix ADM. After configuring the settings, you can select a single Citrix ADC instance or multiple instances and create back up of the configuration files in these instances. If required you can also restore the Citrix ADC instances by using these backed up files.
Configuring Instance Backup Settings
The Instance Backup Settings page allows you to configure settings on Citrix ADM to back up a selected Citrix ADC instance or multiple instances:
In Citrix ADM, navigate to System > System Administration. In the right-hand pane, under Instance Settings, select Instance Backup Settings, and specify the following:
Enable Instance Backups: By default, Citrix ADM is enabled for taking backups of Citrix ADC instances. Clear this option if you do not want to create backup files for the instances.
Password Protect File: (optional) Select password protect option to encrypt the backup file. Encrypting the backup file ensures that all the sensitive information inside the backup file is secure.
Note: You can download the encrypted backup file to your local machine, but you cannot open the file either with Citrix ADM GUI or with any text editor. The file can be retrieved and used by Citrix ADM alone. You are prompted to provide the password when restoring the encrypted backup file. You can, however, open an unencrypted backup file on your system.
Number of Backup Files to retain: Specify the number of backup files to retain in Citrix ADM. You can retain up to 50 backup files of the current state of a Citrix ADC instance. The default is three backup files.
Note: Each backup file accounts for some storage requirement. Citrix recommends that you store an optimal number of Citrix ADC backup files on Citrix ADM as per your requirement.
Backup Scheduling Settings: (optional) There are two options available for creating backup files, though you can use only one option at a time:
- The default backup scheduling option is “interval-based.” A backup file is created in Citrix ADM after the specified interval elapses. The default backup interval is 12 hours.
- You can also change the type of scheduled backups to “time-based.” In this option you specify the time in “hours:minutes” format at which the backup should happen. Citrix ADM allows a maximum of four daily backups to happen on the instances.
NetScaler Settings: (optional) By default, Citrix ADM does not create a backup file when it receives the “NetScalerConfigSave” trap. But, you can enable the option to create a new backup file whenever a Citrix ADC instance sends a “NetScalerConfigSave” trap to Citrix ADM. A Citrix ADC instance sends “NetScalerConfigSave” every time the configuration on the instance is saved.
Geodatabase files: (optional) By default, Citrix ADM does not back up the GeoDatabase files. You can enable the option to create a backup of these files also.
External Transfer: (optional) Citrix ADM allows you to transfer the Citrix ADC instance backup files to an external location:
- Specify the IP address of the location.
- Specify the username and the password of the external server to which you want to transfer the backup files.
- Specify the transfer protocol and the port number.
- You can specify the directory path where the file will be stored.
- You also have the option to delete the backup file from Citrix ADM after transferring it to the external server.
Citrix ADM sends an SNMP trap or a Syslog notification to itself when there is a backup failure for any of the selected Citrix ADC instances.
Creating a Back Up for a Selected Citrix ADC instance by Using Citrix ADM
Perform this task if you want to back up a selected Citrix ADC instance or multiple instances:
In Citrix ADM, navigate to Networks > Instances. Under Instances, select the type of instances (for example, VPX) to display on the screen.
Select the instance that you want to back up, and then click View Backup.
On the Backup Files page, click Back Up.
Specify whether to encrypt your backup file for additional security. You can either enter your password or use the global password that you previously specified on the Instance Backup Settings page.
Restoring a Citrix ADC instance by Using Citrix ADM
Perform this task to restore a Citrix ADC instance by using the backup file that you had created earlier:
Navigate to Networks > Instances, select the instance that you want to restore, and then click View Backup.
On the Backup Files page, select the backup file containing the settings that you want to restore, and then click Restore.
For a Citrix ADC SDX appliance, Citrix ADM backs up only the following:
- Citrix ADC instances hosted on the appliance
- SVM SSL certificates and keys
- Instance prune settings (in XML format)
- Instance backup settings (in XML format)
- SSL certificate poll settings (in XML format)
- SVM db file
- Citrix ADC config files of devices present on SDX
- Citrix ADC build images
- Citrix ADC XVA images
- SDX Single Bundle Image (SVM+XS)
- Third Party instance images (if provisioned)
You must restore your Citrix ADC SDX appliance to the configuration available in the backup file. During appliance restore, the entire current configuration is deleted.
If you are restoring the Citrix ADC SDX appliance by using a backup of a different Citrix ADC SDX appliance, make sure that you add the licenses and configure the appliance’s Management Service network settings to match those in the backup file before you start the restore process.
Make sure that the Citrix ADC SDX platform variant that was backed up was taken is same as the one on which you are trying to restore. You cannot restore from a different platform variant.