This article applies to:
Question:
What files or directories should be backed up in the installation directory for Firewall Suite?
Information:
The most complete method of backing up a Firewall Suite installation would be to back up the entire directory. This assumes that all profiles, reports, and databases are stored as subdirectories of the installation directory. Not all users, however, keep all of the Firewall Suite files in the default location, and some users do not use all cartridges (General Activity, Incoming Activity and Outgoing Activity); therefore, more specific guidelines may be needed to ensure a full back up.
| Firewall Suite |
| Installation Directory: |
| \wt_urlcat\ |
URL Categorization |
| \wtm_alrt\ |
Alerting and Monitoring cartridge |
| \wtm_FirewallOther\ |
General Firewall Activity cartridge |
| \wtm_FirewallWebIn\ |
Incoming Firewall Activity cartridge |
| \wtm_FirewallWebOut\ |
Outgoing Firewall Activity cartridge |
| departments.txt |
Department Management |
| WTProtocols.txt |
Protocol Information |
| \wtm_alrt\datfiles |
| *.amp |
Alerting and Monitoring Profile |
| *.amr |
Alerting and Monitoring Memorized Report Template |
| *.ams |
Alerting and Monitoring Scheduled Event |
| *.rap |
Alerting and Monitoring Response Action |
| *.rpc |
Alerting and Monitoring Response Alert Profile |
| \wtm_FirewallOther\datfiles\ |
| *.fir |
General Firewall Activity Profile |
| *.mss |
Memorized Report Template |
| *.dat directories |
FastTrends Database Directory |
| \wtm_FirewallWebIn\datfiles |
| *.fwi |
Incoming Firewall Activity Profile |
| *.mss |
Memorized Reporting Template |
| *.dat folders |
FastTrends Database Directory |
| \wtm_FirewallWebOut\ |
| urlcatmap.ini |
URL Category Work Mappings |
| \wtm_FirewallWebOut\datfiles |
| *.fwo |
Outgoing Firewall Activity Profile |
| *.mss |
Memorized Reporting Template |
| *.dat folders |
FastTrends Database Directory |
Notes:
These instructions are for backup purposes, only to be used with the same version of the product. Files should only be moved from one build to another installation of the same build. Moving these files to a different version can cause issues.
- This article was previously published as:
- NETIQKB1966
