A backup is a copy of data that is used to restore lost data after a system failure. By using suitable backups, you can recover from many failures that include the following conditions:

• Media failure
  
  
• User errors, such as when a file is deleted by mistake
  
  
• Hardware failures, such as a damaged disk drive or the permanent loss of a server
  
  
• Natural disasters
  
  

For more detailed information about creating backups and recovering data for Microsoft SharePoint Server 2007, see Backup, Recovery, and Availability Resource Center for SharePoint Server 2007.

In order to keep a copy of the most up-to-date versions of FPSP files, you should 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 you complete these steps, the server is configured to automatically export versions of FPSP files.

1. In Windows Explorer, locate the FPSP data folder. For the location of the default FPSP data folder on your operating system, see Default folders.

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

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

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

5. In Notepad or a similar text editor, edit the batch file to include a command to start the Forefront diagnostic tool (FSCDiag.exe) in order to obtain file information for FPSP. For more information about the Forefront diagnostic tool, see Using the diagnostic tool to gather information about the product. The contents of the ForefrontDiagnostics.bat file should resemble the following two lines (provided that you are using the default FPSP program folder):

   	Copy Code
   cd drive:\Program Files (x86)\Microsoft Forefront Protection for SharePoint FSCDiag.exe /c /ver Forefront

   Note:
   If you are not sure about the location of the FSCdiag.exe file, perform a search operation to find the location, and then use it to replace the path in the sample .bat file.

6. On the File menu, click Save, and then close the text editor.

7. Double-click the ForefrontDiagnostics.bat file.

8. In Windows Explorer, open the Diagnostics folder under the log folder you just created by running the batch file. The log folder is located under the FPSP data folder. For example:

   c:\Program Files (x86)\Microsoft Forefront Protection for SharePoint\Data\log\Diagnostics

9. Make sure that a file that is named ForefrontDiag-ServerName-Date-Time.zip was created as a result of running the batch file.

   Note:
   The placeholders ServerName, Date, and Time represent the actual server name and the date and time when the log file was created.

1. Click Start, point to Administrative Tools, and then click Task Scheduler.

   If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.

2. On the Actions menu, click Create Basic Task.

3. In the Create Basic Task Wizard, type the schedule name in the Name box, type the schedule description in the Description box, and then click Next. For example, type the following information:

   Name: Forefront Diagnostics

   Description: Runs ForefrontDiagnostics.bat in order to update and store updated file version information for FPSP.

4. On the Task Trigger page, select an acceptable interval (for example Weekly), and then click Next.

5. Depending on the selected interval, set the start date, the start time, and the recurrence details, and then click Next. For example, configure the following settings:

   Weekly

   Start MM/DD/YYYY - HH:MM:SS AM/PM

   Recur Every: X weeks on: Saturday

   Where MM/DD/YYYY is the month, day and year; HH:MM:SS is the hour, minutes, and seconds; and X is the number of weeks.

6. On the Action page, select the Start a program button, and then click Next.

7. On the Start a Program page, click Browse, locate the ForefrontDiagnostics.bat file that you previously created, click Open, and then click Next.

   Note:
   Leave the Add Arguments (optional) and the Start in (optional) text boxes blank.

8. On the Summary page, verify the settings, and then click Finish.

1. Click Start, click Control Panel, and then double-click Scheduled Tasks.

2. In Scheduled Tasks, double-click Add Scheduled Task.

3. In the Scheduled Task Wizard, click Next.

4. On the Click the program you want Windows to run page, click Browse.

5. In the Select Program to Schedule window, locate and then double-click the ForefrontDiagnostics.bat file that you previously created.

6. In the Type a name for this task box, type a schedule name, select an acceptable interval, and then click Next. For example, use the following name and interval for the task:

   Forefront Diagnostics

   Weekly

7. On the Select the time and date you want this task to start page, set an appropriate start date and time, and then click Next. For example, configure the following settings:

   Start HH:MM:SS AM/PM

   Every: X weeks on: Saturday

   Where HH:MM:SS is the hour, minutes, and seconds; and X is the number of weeks.

8. On the Enter the name and password of a user page, provide the user credentials for an administrator who has permissions to the server, and then click Next.

9. On the You have successfully scheduled the following task: schedule name page, click Finish.

In order to make sure that you can recover configuration settings, all quarantined items, and malware and filtering incidents, copy all FPSP data files to another location. In order for this to work, the version of the product that you are copying must be the same version of the product that you will later try to restore.

1. Create a new folder in a new location (for example: C:\BackupDatabase).

2. Access the Services Control Manager and then stop all relevant Microsoft SharePoint and Microsoft Forefront Protection Suite services. Typically, this includes Windows SharePoint Services Timer, World Wide Web Publishing Service, and all the applications using Microsoft SharePoint Object Model.

3. Make sure the incidents database is in a “Clean Shutdown” state by running the following from a command prompt at the Incidents directory, which is located in the data folder (for the location of the default FPSP data folder, see Default folders):

   esentutl -mh incident.fssdb

   Look for the State item in the output. If it says "Clean Shutdown", you can proceed. If it says "Dirty Shutdown", the backup failed. In that case, start and stop the Microsoft Forefront Protection Eventing Service service. Then run the following again:

   esentutl -mh incident.fssdb

4. Copy the contents of the data folder, excluding the ProgramLog.etl file and the Engines and EngineUpdateLocks folders, to the folder you created in step 1 (for example, C:\BackupDatabase).

   Note:
   You may want to back up the ProgramLog.etl file in order to review previous FPSP diagnostic information, but you will not be able to restore this file with the rest of the FPSP data folder.

After you have successfully backed up your FPSP data files and restored your entire system to an earlier state (including the failed SharePoint server), use the following procedures to restore your FPSP data files.

Note:
You cannot restore data files to a server with a different operating system from the server on which you created the backup files.

1. Install FPSP 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.

2. On the SharePoint server that you restored, stop all relevant Microsoft SharePoint and Microsoft Forefront Protection Suite services. Typically, this includes Windows SharePoint Services Timer, World Wide Web Publishing Service, and all the applications using Microsoft SharePoint Object Model.

3. Follow these steps in order to restore your configuration files, quarantine data files, the incidents database, and all related files:

   1. In Windows Explorer, locate and open the FPSP data folder. For the location of the default FPSP data folder on your operating system, see Default folders.
      
      
   2. Rename the Quarantine folder to QuarantineOld.
      
      
   3. Rename the Incidents folder to IncidentsOld.
      
      
   4. Copy the contents of the FPSP data folder you backed up to the temporary location (for example: C:\BackupDatabase), including the subfolders, to the FPSP data folder. If prompted, overwrite all existing files.
      
      
   5. Delete everything from the Incidents folder (located under the FPSP data folder) except Incident.fssdb.
      
      
   6. In Task Manager, click the Processes tab, and then select Show processes from all users. If the FSCConfigurationServer.exe process is running, end this process.
      
      
   7. Start all relevant Microsoft SharePoint services.
      
      

4. If you are using Forefront Protection Manager to manage FPSP, perform the following additional steps:

   1. On each SharePoint server running FPSP, re-install the Forefront Protection Manager monitoring components (Forefront Protection Manager agent and Operations Manager agent) so that Forefront Protection Manager can successfully communicate with FPSP. For more information, see "Deploying Forefront Protection Manager monitoring components to FPSP" in Integrating Forefront Protection 2010 for SharePoint with Protection Manager.
      
      
   2. Using Forefront Protection Manager, redeploy your FPSP policies. For more information, see Working with groups and policies in the Forefront Protection Manager Operations Guide.