Critical and Non-Critical System State Components for Windows File System

Critical Components

Critical components are components that are essential and necessary for the operating system to come back alive after the restore of system state.

If a critical component fails during the backup of system state, the backup job fails with an error code as the backed up data is not sufficient for a restore of the operating system.

Note

You cannot add the following critical system state components to subclient filters. If you still add the following components to subclient filters, you will receive the following error message:

Critical system state components cannot be filtered from subclient configured to perform system state backup operation.

  • {active directory}

  • {asr}

  • {cluster database}

  • {registry}

  • {system info archive}

  • {system protected files}

  • {system volume}

  • {offline files}

  • {one touch files}

Non-Critical Components

Non-Critical components are components that are part of system state but are not essential for the operating system to come back alive after the restore of system state.

If a non-critical component fails during the backup of system state, the backup job completes with an error code as the backed up data is sufficient for a restore of the operating system. However, the non-critical components do not get restored.

  • {BITS service}

  • {Certificate services}

  • {COM+ database}

  • {Content indexing catalogs}

  • {DDR explicit content}

  • {DFS replication services}

  • {DHCP}

  • {Disk quotas}

  • {Event logs}

  • {File Server Resource Manager} (FSRM)

  • {IIS}

  • {Metadata}

  • {NPS database}

  • {Performance Counter}

  • {Remote storage database}

  • {RSM}

  • {Terminal Services Licensing}

  • {UDDI database}

  • {WMI database}

  • {WINS}

For more information on system state, see Microsoft Articles on Backing Up and Restoring System State, Microsoft Backing Up and Restoring System State in Windows Server 2003 R2 and Windows Server 2003 SP1, and Backing Up and Restoring the Failover Cluster Configuration Using VSS.

Loading...