This section describes key content stored in each of the platform data stores.

MPF Configuration Database (MPFConfig)

Backup Frequency: every 24 hours

Contents:

  • Provisioning Engine server names and states (active/inactive)
  • Provisioning Engine client list and latest transaction (last time at which client connected to server)
  • Transaction log server names and last time transaction data was flushed to log
  • Audit log server names
  • Named procedures, their calling relationship tree and associated ACLs
  • Site information for the provisioning system
  • Queue manager server names
  • 'Execute As' credentials

Transaction Log Database (MPFTranLogData)

Backup Frequency: every 24 hours (depends on provisioning activity)

Contents:

  • Logged requests to the MPF service. For each request:
    • Credentials, if provided
    • Steps:
      • Rollback data
      • Status
      • Timestamp

Audit Log Database (MPFAudit)

Backup Frequency: every 24 hours

Contents:

  • Logged requests to the MPF service. For each request:
    • Credentials, if provided
    • Steps:
      • Status
      • Last running time

Resource Manager Database (ResourceManager)

Backup Frequency: every hour (schedule at same time as Plans Database)

Note:
Backups of the Resource Manager database must be synchronized with backups of the Plans database. These two databases together act as a single data storage component and must therefore be backed up and restored as a pair.

Contents:

  • Available resource types in the environment
    • Disk space
    • Mailbox size
    • IIS site data
  • Available resources (instantiations of the above types) for example:
    • Disk space available to server GUID
    • Resource consumer instance (GUID for resource, GUID for consumer)

Plans Database (PlanManager)

Backup Frequency: every hour (schedule at same time as Resource Manager Database)

Note:
Backups of the Plans database must be synchronized with backups of the Resource Manager database. These two databases together act as a single data storage component and must therefore be backed up and restored as a pair.

Contents:

  • Feature types:
    • Web site
    • Mailbox
    • Disk Space
    • Mailbox Size
  • Plans (Instantiations of feature types)
    • Web sites
    • Mailboxes
    • Disk space
  • Subscriptions
    • Organization Plan
      • User Plan (sub-features from among those offered by Organizational level plan)
      • Demographic/Geographic organization data
      • Organization configuration data (SMTP domain, mailbox server)

NT Data Store (NTDS)

Backup Frequency: every 24 hours (synchronize with

Contents:

  • Organizations (cross-linked to GUIDs in Resource Manager and Plans databases)
    • Users (cross-linked to GUIDs in Resource Manager and Plans databases)
    • Service Pointers
      • IIS server path
      • Mailbox server
      • Customer Directory Integration (CDI) data
      • SharePoint sites
      • DNS zones
    • Mailbox stores (GUID and name cross-linked to resource Manager and Plans databases)
    • Public Folders (GUID and name cross-linked to resource Manager and Plans databases)
    • Offline Address Books (GUID of organization cross-linked to Resource Manager database)
    • Address lists (DN is stored against the owner organization)
    • Customized Exchange permissions

Microsoft Operations Manager (MOM) Database

Backup Frequency: every 24 hours

Contents: Performance Monitor counters (events for all computers in the environment)

Performance Warehouse Database (PWDB40)

Backup Frequency: every 24 hours

Contents:

  • A warehouse of all the information in the Plans database
  • Statistical information (used for Microsoft SQL Server 2005 with SP1 reporting services reporting)
    • Current mailbox sizes
    • Mailbox count
    • Current SharePoint space consumption