Windows File System Backed Up Components
You can back up the data that resides on your client computer and restore it when required.
What Is Backed Up
File Allocation Table (FAT) file systems
New Technology File Systems (NTFS)
Transactional File Systems
Distributed File System (DFS) data
Oracle ASM Cluster File System (Oracle ACFS)
Resilient File System (ReFS) on Windows Server 2012
USB drives that are fixed disks
Cluster Shared Volume
Data Deduplication-Enabled Volumes
File System Elements
Universal Naming Convention (UNC) Paths
Share with Macintosh data
Single Instance Storage
Remote Storage Service
System File Protection catalog and files
Performance monitor configuration files
SYSVOL (if this is a domain controller)
Certificate Services database (if this is a certificate server)
Cluster database (if this server is part of a cluster)
Terminal Server Licensing database
UDDI (only with Windows Server 2003 using VSS)
Disk quota information
Content Indexing catalogs
Network Policy Server (NPS)
Quorum data on the physical node of the cluster
Third-Party Software encrypted data
Data encrypted using McAfee Endpoint Encryption.
- Data from the Web Server on Windows Server 2012 is not backed up.
- Response File Group Configuration is not backed up when you back up the Lync Server. For more information about backing up Response File Group Configuration, refer to http://technet.microsoft.com/en-us/library/hh202170.aspx.
- By default, the directory junction point is backed up but the source data (data linked to junction point) is not backed up. This prevents undesired backup and restore of system created directory junction points. To back up the source data of a junction point that is not part of a subclient contents, the source data must be explicitly added to a subclient's content.
Last modified: 2/3/2020 8:32:14 PM