Instance settings

Last published : Sep 25, 2026
You can manage the discovered instances in {{page.adm-product-name-short}} and configure the instance backup settings.

Manage the instance configuration

In Settings > Global Settings > Instance Settings > Instance Management, you can modify the following instance configurations:
  • Communication with instance(s) - You can choose an HTTP or HTTPS communication channel between {{page.adm-product-name-short}} and the discovered instances.
  • Enable Certificate Download - Allows you to download the SSL certificates from a discovered instance.
  • Prompt Credentials for Instance Login - When you access the instance through the {{page.adm-product-name-short}} GUI, the instance login page appears. Specify your login credentials to access an instance.

Configure instance backup settings

In Settings > Global Settings > Instance Settings > Instance Backup, you can configure the backup settings for the discovered {{page.citrix-adc-generic}} instances in {{page.adm-product-name-short}}.
In Configure Instance Backup Settings, select Enable Instance Backups.
  • Number of Backup Files to retain: Specify the number of backup files to retain in the {{page.adm-product-name-short}}. You can retain up to 3 backup files per {{page.citrix-adc-generic}} instance. The default is 1 backup file.
  • Backup Scheduling Settings- You can schedule an instance backup in two ways:
    • Interval Based - A backup file is created in {{page.adm-product-name-short}} after the specified interval elapses. The default backup interval is 12 hours.
    • Time Based - Specify the time in hours:minutes format at which you want {{page.adm-product-name-short}} to take the instance backup.
  • {{page.citrix-adc-generic}} settings - With this option, you can initiate a backup based on the trap and to include GeoDB files with the backup. This setting applies to MPX,VPX,CPX, and BLX instances.
    • Do instance backup when NetScalerConfigSave trap is received - By default, {{page.adm-product-name-short}} does not create a backup file when it receives the “NetScalerConfigSave” trap. But, you can enable the option to create a backup file whenever a {{page.citrix-adc-generic}} instance sends a NetScalerConfigSave trap to {{page.adm-product-name-short}}.
      A {{page.citrix-adc-generic}} instance sends NetScalerConfigSave every time the configuration on the instance is saved.
      Specify Backup on trap delay in minutes. If the received NetScalerConfigSave trap persists for the specified minutes on {{page.adm-product-name-short}}, {{page.adm-product-name-short}} backs up the instance.
    • Include GeoDB files - By default, {{page.adm-product-name-short}} does not back up the GeoDatabase files. You can enable the option to create a backup of these files also.
  • {{page.netscaler-sdx-short}} Settings - To back up SDX instances, specify Backup Timeout in minutes. During an SDX instance backup, the connection between {{page.adm-product-name-short}} and SDX is maintained for the specified period.
    For large SDX backup files, maintain the connection between {{page.adm-product-name-short}} and SDX instance for a longer period to ensure backup completion.
    Important:
    The backup fails if the connection times out.
  • External Transfer - {{page.adm-product-name-short}} allows you to transfer the {{page.citrix-adc-generic}} instance backup files to an external location:
    1. Specify the IP address of the location.
    2. Specify the user name and the password of the external server to which you want to transfer the backup files.
    3. Specify the transfer protocol and the port number.
    4. Specify the directory path where the file must be stored.
    5. If you want to delete the backup file after you transfer the file to an external server, select Delete file from Application Delivery Management after transfer.

Disable notifications for managed devices

Administrators can temporarily disable notifications for specific managed devices during maintenance and troubleshooting windows. By disabling notifications, you can avoid receiving unnecessary alerts and notifications concerning device-specific issues and status updates during these intervals.
Administrators can select individual devices, including primary, secondary, or specific cluster nodes. If a VPX instance is on SDX, then VPX and SDX are treated as separate entities for notification configuration. If the disable notifications window is configured for a device, then the configuration is applicable to device partitions as well.
During these intervals, events do get processed, but no notifications (email, Slack, PagerDuty) are sent to administrators for the selected devices. This behavior is applicable to both device-specific events (such as configuration changes, entity down alerts) and console-generated events (such as status polls, threshold breaches).
To disable notifications for specific managed devices, perform the following steps:
  1. Navigate to Settings > Administration > Instance Settings and click Notification Disable Windows.
  2. In Notification Disable Windows, click Add.
  3. In Add Notification Disable Windows, click Add Instances and select the required instances. Click Ok.
  4. Select the date and time for Start Date, Start Time, End Date, and End Time.
  5. Add a comment (optional) and click Create. The disable notification window appears on the Notification Disable Windows page.
You can also edit or delete these disable notification windows. You can also click History to view the historical details of the disable notification windows.