The Storage Team Blog about file services and storage features in Windows and Windows Server.
Consistently identify, classify, and protect data across all file servers in your organization
The Solution Accelerators team is pleased to announce the Data Classification Toolkit for Windows Server 2008 R2 Beta.
Join the Beta Program (Windows Live ID required)
Designed to help reduce the cost and complexity of data compliance, the Data Classification Toolkit for Windows Server 2008 R2 helps organizations consistently identify, classify, and protect data across multiple file servers. Using out-of-the-box classification knowledge, this tool gives organizations visibility into how data is distributed across their file servers to help them apply the right policies, protect critical data, and identify potential data storage efficiencies
Want to learn more about IT Governance and Compliance? Visit the IT GRC home page, and check out all the free content the IT GRC team has to offer!
Could you guys do a posting to answer some VSS questions ?
I understand how a VSS backup works. All writes to the file system are stopped while the VSS service inserts itself into the file stack, then the writes resume while VSS copys any blocks to the "shadow copy" before they get overwritten. Once the backup is complete VSS removes itself from the file stack. What I don't understand is how this process works with the Previous Versions feature and the System Restore feature. If you want to make a backup of the way the disk looks at a point in time X then you would have to have the VSS service insert itself in the file stack at time X, copy any blocks before they get overwritten, and continue to do this indefinately because if you stop then blocks will be overwritten. But I don't think the VSS service is in place in the file stack all the time so what is really happening ? If it is in place all the time then how do different points in time get created ?