Self-healing NTFS in Windows Server 2008 and Windows Vista

apawar — Thu, 14 Feb 2008 01:24:23 GMT

I ask this question to a customer who ask me about how Windows Server 2008 can help them achieve higher availability for their data.

Have you ever had some weird disk or system behavior on your system volume, discovered or believed it was disk corruption, and then ran “chkdsk c: /f” on it only to get that lovely message:
“Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts (Y/N)”?

So then I ask them how would you like to reduce the likely hood of ever having to do a chkdsk. An the IT Pros in the room want to know more about a feature in Windows Server 2008 and Windows Vista called Self-healing NTFS. This is not one of the features that filters up into the marketing material for either Windows Vista or Windows Server 2008. However when I am talking to customers who want high availability for their data this feature is very important to talk about.

So what is is Self-healing NTFS and how can it help :

By default in Server 2008, self-healing NTFS is turned on and automatically detects and recovers/repairs/removes corruptions on the NTFS volume, boot sector, or files. It does this on the When any of these repairs are done, it will log a NTFS source event in the system event log (# 130 and 55 event IDs).

It’s going to possibly remove/delete a corrupted file someone is using on the disk? What if I lose data?

So lets look at this way – if the file is corrupted, it’s gone anyway and you can look at what was removed in the logs. Furthermore, there is a good possibility self-healing NTFS can fix the issue without the user ever even knowing there is a problem and you get all of the overall benefits listed below.

However, just for those who don’t want the automatic repair/deletions, there is a way to turn it on/off. It’s a pretty simple command: “fsutil repair set c: 0” where c: represents the volume you’d like to turn in off. Replace the 0 with a 1 and it will turn it back on the drive. When you turn it off, it will notify you a file is corrupt but do nothing to fix it.

Overall benefits (rephrased from the Changes in functionality from WS2003 SP1 guide below):
· Runs without requiring reboots on all volumes, except in extreme corruption conditions
· Preserves as much data as possible - based on the type of corruption
· Reduces failed file system mounting requests
· Provides better reporting for file system changes
· Recovers volumes when boot sector is readable, but no NTFS volume identified
· Validates and preserves data with critical system files

Technorati Tags: NTFS,Windows Server 2008,Fix,Chkdsk

High availability features of Windows Server 2008

apawar — Thu, 14 Feb 2008 01:09:34 GMT

Technorati Tags: High Availability,Winodws Server 2008,Clustering

Customer that I talk to want to know how they can providing high availability to mission-critical applications, services, and data. When services are down or fail, business continuity is interrupted, which can result in significant losses.

Windows Server 2008 supports two key high-availability features to help organizations meet their uptime requirements for their critical systems: Failover Clustering and Network Load Balancing (NLB). Failover Clustering and NLB in Windows Server 2008 have been improved to offer simplified management and more robust functionality. In addition, Windows Server Backup provides a basic backup and recovery solution in case of hardware failures.

Failover Clustering

Failover clustering can help you build redundancy into your network and eliminate single points of failure. The improvements to failover clusters (formerly known as server clusters) in Windows Server 2008 are aimed at simplifying clusters, making them more secure, and enhancing cluster stability.

Cluster Validation Tool

By using the new Cluster Validation Tool, you can perform tests to determine whether your system, storage, and network configuration is suitable for a cluster. The Cluster Validation Tool verifies that the nodes meet all of the operating system requirements, that the networks are configured correctly, that there are at least two separate networks on each node for redundancy, and that the storage subsystem supports the necessary Small Computer System Interface (SCSI) commands to handle cluster actions.
Setup Improvements

Once validated by the Cluster Validation Tool, the installation has been streamlined so that administrators can set up a cluster in one step. The cluster installation is completely scriptable, enabling administrators to automate cluster deployments.
Migration Improvements

When migrating a clustered service from one cluster to another, cluster settings can be captured and copied to another cluster. This reduces the time it takes to build the new cluster and configure the services.
Cluster Management and Operations Improvements

The cluster management interface has been optimized to make managing the cluster easier and more intuitive. Cluster management can be performed from the command line as well as the Windows Management Instrumentation (WMI) management console. Managing clustered shared folders is now easier to do because it can create customized views to quickly see which shared folders are clustered and which cluster a shared folder is available on.
Backup and Restore Improvements

Full integration with the Volume Shadow Copy Service makes it easier to back up and restore cluster configurations.
Cluster Infrastructure Improvements

The cluster quorum contains the configuration settings for the entire cluster. With Windows Server 2008, you can configure a cluster so that the quorum resource is not a single point of failure by using the majority node set or a hybrid of the majority node set and the quorum resource model. The cluster service can also isolate DLLs that perform actions incorrectly to minimize impact to the cluster, as well as verify consistency among copies of the quorum resource.
Storage Improvements

Administrators have better control and can achieve better performance with storage than was possible in previous releases. Failover clusters now support GUID partition table (GPT) disks that can have capacities of larger than 2 terabytes, for increased disk size and robustness. Administrators can now modify resource dependencies while resources are online, which means they can make an additional disk available without interrupting access to the application that will use it. And administrators can run tools in Maintenance Mode to check, fix, back up, or restore disks more easily and with less disruption to the cluster.
Network Improvements

Networking has been enhanced to support Internet Protocol version 6 (IPv6) as well as Domain Name System (DNS) for name resolution, removing the requirement to have WINS and NetBIOS name broadcasts. Other network improvements include managing dependencies between network names and IP addresses: If either of the IP addresses associated with a network name is available, the network name will remain available.
Security Improvements

Internet Protocol security (IPsec) can be used between clients and the cluster nodes, as well as between nodes so that you can authenticate and encrypt the data. Access to the cluster can also be audited to determine who connected to the cluster and when.

Network Load Balancing

Network Load Balancing (NLB) allows you to distribute TCP/IP requests to multiple systems in order to optimize resource utilization, decrease computing time, and ensure system availability. NLB has been improved in Windows Server 2008, including:

Next Generation TCP/IP

The TCP/IP protocol suite has been completely redesigned for Windows Server 2008. Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) are both supported natively by Windows Server 2008. NLB extends full support to IPv6 for all communication while maintaining IPv4 support.
Multiple IP Address Support

Each node in your NLB cluster can now have multiple dedicated IP addresses.
Microsoft ISA Server Integration

Microsoft ISA Server can support your mixed IPv4 and IPv6 infrastructure by allowing multiple IP addresses for each NLB node where IPv4 and IPv6 clients are used. ISA Server can also provide intrusion detection services to protect your NLB cluster.

Amit Pawar - Infrastructure blog : High Availability

Self-healing NTFS in Windows Server 2008 and Windows Vista

High availability features of Windows Server 2008

Failover Clustering

Network Load Balancing