Performing backups of your servers including system, log, and exported Forefront UAG configuration files, is your first line of defense in planning for a disaster. Your organization probably has a well-planned disaster recovery plan that includes the backup of your Forefront UAG servers. Forefront UAG log files provide critical information about your Forefront UAG operations. Depending on the frequency of your server backups, you should consider backing up your Forefront UAG log and export files independently.
The following sections describe some of the backups you may need to do:
- Forefront UAG server backup
- Built-in log
- Forefront UAG export
- Other vendor log
- Backing up the Forefront
UAG DirectAccess configuration
Forefront UAG server backup and restore
You should back up your Forefront UAG servers regularly, and in line with your organization’s disaster recovery plan. Depending on the frequency of these backups, other logs and files, for example built-in logs and export files, may require backing up independently.
|For example, if the built-in log files have been deleted and they were not backed up, Web Monitor will be unable to provide information for the missing periods contained in the log files.|
Periodically, you should perform a test restore from a backup on a test Forefront UAG server, to confirm that the backed up information will be usable in the event of a disaster recovery scenario. This restore could be of a full system backup, independent log files, or imported and exported configuration files.
Built-in log files
When using built-in log files, events are logged to the native Forefront UAG format, and are used by the Web Monitor that queries this event log, and lets you filter events according to type, time, and other parameters. When setting up built-in logging, you can specify the location to where log files that are generated by the built-in reporter should be stored. Web Monitor creates a new event log file every day, saving the previous log to the default folder \Program files\Microsoft Forefront Unified Access Gateway\Logs\Events, or to a location you specify when configuring logging.
|You can use the Web Monitor only if the built-in reporter is enabled.|
For instructions on how to query events that are recorded by the built-in Forefront UAG logging mechanism, see Querying events.
Forefront UAG export configuration files
Exported configuration files contain a record of the latest configuration settings, and can be used, during maintenance or disaster recovery, to restore configuration settings to the same Forefront UAG server from which the settings were exported, or to a different Forefront UAG server.
For instructions on how to backup and restore your Forefront UAG configuration, see Backing up and restoring with export and import.
Note the following:
- By default, the export file is automatically
exported to the \Program files\Microsoft Forefront Unified
Access Gateway\Backup folder, whenever the Forefront UAG
configuration is Activated.
- You can also export the Forefront UAG
configuration file in xml format, from the Forefront UAG Management
Console. For more information, see Exporting the
Forefront UAG configuration settings.
Other vendor log files
Follow the vendor instructions for how and when to backup vendor log files.
Backing up the Forefront UAG DirectAccess configuration
The Forefront UAG DirectAccess configuration generated at the end of the Forefront UAG DirectAccess Configuration Wizard is automatically backed up, when you activate Forefront UAG or export the Forefront UAG configuration. If you export and change your Forefront UAG DirectAccess configuration script, it is recommended that you back up the edited configuration file.