Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
How do I move Bot/DDoS protection settings to another vService or device (Export / Import)?
Short answer
The Export and Import buttons are located at the bottom right of the Bot/DDoS Protection Mode strip on the Bot/DDoS Management screen. Export downloads the whole Bot/DDoS configuration of the vService (the three protections, limit blocks, country and network type rules, whitelists, Captcha, Quarantine, Waiting Room, Notifications and Learning settings) as a single JSON file. Import loads this file to the target vService and completely replaces the Bot/DDoS configuration there; no merging is done, the operation takes effect right after confirmation and cannot be undone. Bot/DDoS protection must have been enabled beforehand on the target vService. Keys that the target device does not recognize are dropped silently; both buttons are displayed only for users who have edit permission in the Load Balancer area.
Problem: Settings Are Kept Per vService
The Bot/DDoS configuration is a separate record for each vService: the limits, country and network type rules, exemption lists, Captcha and Quarantine cards and learning settings belong to that vService. Entering these settings again screen by screen, in order to use the same protection on a new vService, when moving from a test device to a production device or as a backup before a big change, both takes time and carries a risk of error.
Solution
Export and Import
- How it works Export downloads the Bot/DDoS record of the source vService as a JSON file; Import writes the settings in the file in place of the record of the target vService.
- Where it is opened Left Monitor Panel → Bot/DDoS Protected vServices → vService → Bot/DDoS Management → bottom right of the Bot/DDoS Protection Mode strip
- Requirement Bot/DDoS protection having been enabled on the target vService; edit permission in the Load Balancer area
- vService type HTTP and L7 TCP
- Out of scope The record identity; the file does not carry which vService it was taken from, and on import it is bound to the target vService
Step-by-Step Configuration
1
Adım 1 Open the Bot/DDoS Management tab of the source vService
The Left Monitor Panel is opened, Bot/DDoS Protected vServices is selected from the category tabs at the top left, the source vService is clicked, and the Bot/DDoS Management tab is opened (accessing the screen).
2
Adım 2 Click the Export button
The Export button at the bottom right of the strip is clicked.
3
Adım 3 Confirm the export
The confirmation window asks the question The entire Bot/DDoS protection configuration of vService "<vService-name>" — protections, whitelists, notification and learning settings — will be downloaded as a single file. Continue?; the Yes button is clicked. The file is downloaded directly; its name consists of the vService name, the _threat suffix and the date-time stamp (e.g. Web_Servisi_threat_20260828_1745.json, export steps).
4
Adım 4 Enable the protection on the target vService (if needed)
If Bot/DDoS protection is off on the target vService, it is enabled first (How to Enable Bot/DDoS Protection?). Since a vService whose protection has never been enabled has no Bot/DDoS record, the file cannot be loaded. If the target is on another device, the file is loaded from the interface of that device.
5
Adım 5 Back up the current settings of the target vService
On the Bot/DDoS Management tab of the target vService, an Export is also taken first. Since the import cannot be undone, this file is the only point of return.
6
Adım 6 Select the file with the Import button
The Import button on the strip of the target vService is clicked, and the file downloaded in step 3 is selected. The picker shows .json files by default.
7
Adım 7 Confirm the import
The confirmation window asks the question The ENTIRE Bot/DDoS protection configuration of vService "<vService-name>" will be REPLACED with the selected file — protections, whitelists, notification and learning settings included. The operation is written to the user logs with a change summary. Continue?. The correctness of the target is confirmed by reading the vService name in the window, and the Yes button is clicked. There is no separate deployment step; the configuration is regenerated and applied, and in a cluster setup it is also sent to the peer device.
Verification
1Cards of the target vServiceTR7 side
On the Bot/DDoS Management tab of the target vService, the mode of the three protections, the limit blocks and the cards on the strip are compared with the source.
Expected
The modes, limits and rules are the same as on the source vServiceIn a file taken from a device of a different version, the keys that the target does not recognize drop silently; the comparison is made especially in this case.
2User Logs recordTR7 side
The import record is searched for on the Settings → System Logs → User Logs screen; the Changes column lists the changed fields (User Logs).
Expected
Threat protection configuration of "<vService-name>" is replaced from an imported fileThe client-side timeout of the import request is 10 seconds; if the time is exceeded, the result may not appear on the screen, and the result is verified from this record.
Common Mistakes
Import does not merge, it replaces completely
Settings that are not in the file are not kept on the target; the whole Bot/DDoS configuration of the target is replaced with the one in the file. Import is not used to move only a single limit or a single rule list; that setting is entered manually on the target.
- Running Import without backing up the target. The operation has no undo step; the previous settings can be returned to only with an Export file taken from the target beforehand.
- Trying to load to a vService whose protection has not been enabled. If the target has no Bot/DDoS record, the import is stopped; the protection is enabled first.
- Forgetting the objects independent of the file itself. The Condition and Content Page objects selected in the Whitelist Condition fields and in Show Content actions do not enter the file; the file carries only their selection. When moving to another device, these fields are checked from the cards after the transfer.
- Not verifying the result between different versions. Of the keys in the file, only the ones the target device recognizes are taken, and the dropped ones are not reported; even a valid JSON file (
{}) that carries no recognized key returns the configuration to the default behavior (unrecognized keys). - Leaving the file in a shared location. The file contains the thresholds, the exemption lists and the notification recipients (e-mail addresses, SMS numbers); it is kept in a location with restricted access.
- Looking for the buttons on a view-only account. Export and Import are displayed only for users who have edit permission in the Load Balancer area; exporting is also counted as a write operation on the server.
How it is done in the documentation
