If selected, the Quick Format option will cause the format to be performed without any error checking. The Enable file and folder compression option dictates whether the data stored in the volume is to be compressed to maximize use of space. This option is only available for NTFS volumes and has some inherent disk performance issues associated with the compressed and subsequent decompression of data. Click on the Next button to proceed to the summary screen. Assuming the settings are satisfactory, click on Finish to begin the formatting process.
The wizard will close and the disk in the graphical display will show the new volume as a primary volume and show the progress of the formatting process. Once the process is completed the disk will be ready for use. To create additional volumes, repeat the above steps. When the fourth volume is created the wizard will create it as an extended volume and all subsequent volumes will be created as logical drives within the extended partition.
For example, the following figure shows Disk 1 with three primary partitions E, F and G and one extended partition containing two logical drives H and I :. During the volume creation process outlined in the preceding sections of this chapter it was mentioned that a new partition on a disk drive may be created without formatting it for a particular file system. This is known as a raw partition and will be listed in the disk manager as having a RAW file system type.
Before the volume can be used it must be formatted. This can be achieved using either the Disk Management interface or from the command line using the diskpart tool. To perform the format from Disk Management simply select the desired volume from the graphical display, right click and select Format The format dialog will appear requesting the file system type, volume name, allocation unit size and volume label.
Options to perform a quick format which does not perform an error check and enable disk compression for NTFS file systems only are also provided. Once the desired settings are selected, initiate the format simply by clicking on OK and then respond affirmatively to the warning dialog.
Windows Server R2 provides the ability to format volumes from the command line using the diskpart tool. This can be invoked by entering diskpart either at the command prompt or in a Run dialog. The first step is to identify the disks on the system. This information is obtained using the list disk command:. For the purposes of this tutorial we will be working on a partition on disk 1. To select the required disk use the select disk command:. Having selected the disk, the next step is to select the partition which is to be formatted.
Right-click the newly added disk resources, and then click More actions. Click Move this resource to Another Service or application to move the resource to the appropriate application or service group. In these steps, volume N and volume Y already exist in the same "Cluster Service and Application" group. Volume N represents the volume that will host the mount point folder. Volume Y represents the volume that is being mounted by the mount point.
Volume Y does not require an assigned drive letter before you follow these steps. In the middle pane of the Disk Management console of the cluster node that owns both volumes N and Y, right-click volume Y, and then click Change Drive Letter and Paths.
Click volume N, click New Folder , type a name for the new folder, and then click OK two times to return to the Server Manager console. Test the mount point on each node by moving the "Service and Application" group that holds both of the disk resources to each node.
Create a dependency in the mounted volume disk resource that specifies the disk that is hosting the mount point folder. This makes the mounted volume dependent on the host volume, and it makes sure that the host volume comes online first. Note This practice is no longer necessary in Windows Server and later versions of Windows. If you move a mount point from one shared disk to another shared disk, make sure that the shared disks are located in the same group.
Try to use the root host volume exclusively for mount points. The root volume is the volume that hosts the mount points. This practice greatly reduces the time that is required to restore access to the mounted volumes if you have to run the Chkdsk.
This also reduces the time that is required to restore from backup on the host volume. If you use the root host volume exclusively for mount points, the size of the host volume must be at least 5 megabytes MB. This reduces the probability that the volume will be used for anything other than the mount points. In a cluster where high availability is important, you can make redundant mount points on separate host volumes.
This helps guarantee that if one root host volume is inaccessible, you can still access the data that is located on the mounted volume through the other mount point. Note Because the user data that is located on LUN3 depends on both the D and E volumes, you must temporarily remove the dependency of any failed host volume until the volume is back in service. Otherwise, the user data that is located on LUN3 remains in a failed state. Need more help? Expand your skills. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.
Privacy policy. This article describes how to create volume mount points on a server cluster by using the NTFS volume mount points functionality. By using volume mount points, you can graft or mount a target partition onto a folder on another physical disk.
You can also exceed the letter limitation for drive letter references. When you create a volume mount point on a Windows Server failover cluster, you must consider the following key items:.
Log on to the local computer by using administrative rights to the cluster node that hosts both the mount point and the volume for the mount point. On each node of the cluster, use the Disk Management console to make sure that only one node has each disk in the "online" state.
The disks should be online on the same node and on only that node. Open the Failover Cluster Management snap-in. If the User Account Control dialog box appears, confirm that the action that it displays is what you want, and then click Continue. Select the disk that hosts both the mount point and the volume for the mount point, and then click OK. Both disks now appear in the Available Storage area of the storage pane. Right-click the disk resource that hosts the mount point, and then click Properties.
Click the root disk, click Apply , and then click OK. This dependency will cause the resource to come online after the disk resource that hosts the mount point is successfully brought online.
0コメント