To keep a copy of the most up-to-date versions of FSSP files and registry data, create a batch file and then create a scheduled task to keep the version information up to date.

Note:

The steps for creating a scheduled task differ for Windows Server 2008 and Windows Server 2003; follow the appropriate procedure.

After completing these steps, the server will be configured to automatically export versions of FSSP files and registry data.

To create a batch file

In Windows Explorer, locate the following folder:

drive:\Program Files\Microsoft Forefront Security\SharePoint\Data

On the File menu, point to New, and then click Text Document.

Type ForefrontDiagnostics.bat for the file name, press ENTER, and then click Yes.

Right-click the ForefrontDiagnostics.bat file, and then click Edit.

In Notepad, edit the batch file to include a command to start the Forefront Security Diagnostic tool (FSCDiag.exe) in order to obtain registry and file information for FSSP. The contents of the ForefrontDiagnostics.bat file should resemble the following:

After you select the restoration strategy that is most applicable to your environment, you can perform the appropriate restoration tasks. The recovery procedures that you perform depend on the following factors:

The kind of disaster or failure that may occur

The kind of backups that are available

The time that you can spend to perform the recovery

After the whole system has been restored to an earlier state, you can recover the Incidents database and the Quarantine database along with your configuration settings. You can also create templates in order to deploy configuration settings to servers in your enterprise. (For more information about creating templates, see SharePoint Templates.) Then, you can use these templates and the Microsoft Forefront Server Security Management Console (FSSMC) in order to help you quickly recover from a failure.

When these Forefront services are offline, files that are uploaded or downloaded from the SharePoint site are not scanned. If you do not want uploads or downloads to occur, stop these services, and then bring the SharePoint site offline.

In Windows Explorer, locate and open the following folder:
drive:\Program Files\Microsoft Forefront Security\SharePoint\Data

Rename the Incidents.mdb file to Incidents.old.

Rename the Quarantine folder to QuarantineOld.

Move the Incidents.mdb file and the Quarantine directory from the temporary location to the following folder:
drive:\Program Files\Microsoft Forefront Security\SharePoint\Data

Start the Forefront services.

To restore data files in a standalone environment

Select the server that you want to use for configuring your Forefront Security for SharePoint templates.

Restore the failed SharePoint server.

On the SharePoint server that you restored, follow these steps:

Install FSSP and all related hotfixes or rollups that were installed at the time of the backup.

Note:

You can compare the file versions against the VerForefront.csv file that is located in the latest ForefrontDiag backup.

Restore the Template.fdb file, the Incidents.mdb file, and the Quarantine directory to a temporary location.

When these Forefront services are offline, files that are uploaded or downloaded from the SharePoint site are not scanned. If you do not want uploads or downloads to occur, stop these services, and then bring the SharePoint site offline.

In Windows Explorer, locate and open the following folder:
drive:\Program Files\Microsoft Forefront Security\SharePoint\Data

Rename the Incidents.mdb file to Incidents.old.

Rename the Quarantine folder to QuarantineOld.

Rename the Templates.fdb file to Templates.old.

Move Templates.fdb, Incidents.mdb, and the Quarantine folder from the temporary location to the following folder:
drive:\Program Files\Microsoft Forefront Security\SharePoint\Data

Start the Forefront services.

At a command prompt, type the following command, and then press ENTER:

The FSCStarter t command loads the templates from the Templates.fdb file.
Because the General Options settings have registry values that are associated with them, they cannot be recovered in a standalone environment. It is recommended that you compare your registry settings against another server in your organization or against the Reg_ForefrontSoftware.txt file that is located in the latest ForefrontDiag backup, and then manually configure the General Options settings by using the Forefront Server Security Administrator. (For more information about configuring General Options, see General Options in "SharePoint Forefront Server Security Administrator".)
It is recommended that you do not copy Forefront database (.fdb) files from another server. If you do this, the associated globally unique identifiers (GUIDs) of the databases will have conflicts.