Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Certain backup software may fail on Forefront Endpoint Protection database

Certain backup software may fail on Forefront Endpoint Protection database

View products that this article applies to.

Symptoms

Backup applications that rely on volume shadow copies, including EMC NetWorker, may fail to backup partitions containing the Forefront Endpoint Protection (FEP) database.

↑ Back to the top

Cause

The Forefront Endpoint Protection volume shadow copy service (VSS) writer does not fully populate metadata for the restoration of the database. The absence of this metadata may cause errors in backup or restore software that use this information.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Microsoft regularly releases software updates to address specific bugs. If Microsoft releases a software update to resolve this bug, this article will be updated with additional information.

↑ Back to the top

Workaround

To workaround this issue, disable the VSS writer. This does not present a loss of functionality as the database is backed up by the SQL VSS writer. You can disable the VSS writer by modifying the AgentComponents.xml located in the folder “%ProgramFiles%\Microsoft Forefront\Forefront Endpoint Protection” using the steps below. The new contents shown below use a XML comment to prevent the FepWriterManager component from being used.
  1. Open the Services in Administrative Tools.
  2. Stop the Forefront Endpoint Monitoring Service (FEPSrv).
  3. Open Windows Explorer and browse to “%ProgramFiles%\Microsoft Forefront\Forefront Endpoint Protection”.
  4. Make a copy of AgentComponents.xml, for example AgentComponents.xml.bak.
  5. Using Notepad or other text editor, replace the entire content of the AgentComponents.xml so that it is the exact XML below.
  6. Save AgentComponents.xml 
  7. In the services snap-in, start the Forefront Endpoint Monitoring Service (FEPSrv).
<?xml version='1.0' encoding='utf-8'?>
<Agent>
  <AgentComponentsData>
    <AgentComponents>
      <AgentComponentData>
        <ComponentId>DCE36B58-C9AF-4D02-ABCC-F8DD23F790DD</ComponentId>
        <Assembly>MetadataUpdater</Assembly>
        <ClassName>Microsoft.Forefront.EndpointProtection.MetadataManager</ClassName>
      </AgentComponentData>
      <AgentComponentData>
        <ComponentId>2887E727-D317-4f2b-B02A-EF8F955D4225</ComponentId>
        <Assembly>AlertsManager</Assembly>
        <ClassName>Microsoft.Forefront.EndpointProtection.AlertsManager.AlertsManager</ClassName>
      </AgentComponentData>
      <AgentComponentData>
        <ComponentId>58438CB1-012D-429f-BD74-E7C54DA8CE7A</ComponentId>
        <Assembly>SqmAgents</Assembly>
        <ClassName>Microsoft.Forefront.EndpointProtection.SqmAgents.SqmCollectorsManager</ClassName>
      </AgentComponentData>
      <!-- 
      <AgentComponentData>
        <ComponentId>DFB0D73F-1360-4C21-9825-F9C23CF9CBF5</ComponentId>
        <Assembly>FepWriterManager</Assembly>
        <ClassName>Microsoft.Forefront.EndpointProtection.FepWriterManager</ClassName>
      </AgentComponentData> 
      -->
    </AgentComponents>
  </AgentComponentsData>
</Agent>

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2570654
Revision : 1
Created on : 1/7/2017
Published on : 4/6/2012
Exists online : False
Views : 255