How to check allocation unit size

The best way, and the right tool for the job is fsutil. In command line just type;

fsutil fsinfo ntfsinfo <drive>:

Examplae: fsutil fsinfo ntfsinfo c:


C:\>fsutil fsinfo ntfsinfo e:
NTFS Volume Serial Number : 0x0e6640c86640b1ef
Version : 3.1
Number Sectors : 0x0000000018ffe2fb
Total Clusters : 0x000000000031ffc5
Free Clusters : 0x0000000000059043
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
Bytes Per Cluster : 65536
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000280000
Mft Start Lcn : 0x000000000000c000
Mft2 Start Lcn : 0x000000000018ffe2
Mft Zone Start : 0x00000000002e88c0
Mft Zone End : 0x0000000000307ea0



Change disks in SQL Cluster.

Here are the general steps recommended for the migration of SQL Storage volumes, for instance:Ensure that there are Full backups of all databases in the system, when just prior to migration.

Stop all SQL Server services (Cluster Manager – Take Offline Services SQL only).

Assigning the new storage volumes and Drive Letter’s temporary copies.

Full copy of all existing data, keeping the ACLs of existing volumes to new ones.

Removal of dependencies on the SQL Service of old records.

Removing the Drive Letter’s of old records and assignment of these new discs to Drive Letters (attention has to be guaranteed that all drive Letters are kept for each volume replaced)

We recommend that prevented access by the operating system on both nodes to the old disk (disable the making of the Path, or another method which ensures that the OS does not access the old disk), but keeping the data intact in case you need to RollBack.

Allocation of new volumes in the SQL Cluster Group.

Making even the services of SQL “Offline” Move SQL group for each of the physical nodes in the cluster, must raise all funds, with the exception of SQL Services. With this step we ensure that the new volumes are correctly recognized by the OS of each physical node.

Assign dependencies removed in section 5 to the SQL Service, should be exactly the same as previously existing.

Making again the SQL Failover Group, even with the SQL services “Offline”, among all physical nodes in the cluster.

Making the Bring Online Services and SQL Move Group from all physical nodes in the cluster to ensure that the SQL service is started successfully on all physical nodes in the cluster.

You can follow the following article concerning optimization of the discs to SQL Server 2008: