April 13, 2008
11:29 pm

  • You can surpass the 26-drive-letter limitation, by using volume mount points feature.  If you use the root (host) volume exclusively for mount points, the size of the host volume only has to be several MB.  This reduces the probability that the volume is used for anything other than the mount points.  This feature can also decrease the amount of time it can take to defragment a drive, backup/restore and run CHKDSK against a volume as oppose executing these tasks on a terabyte volume. (ref: KB280297)
  • The dependency hierarchy in cluster is important.  Most resources should depend on Physical Disk and Network Name resource within its own group,  especially Server Message Block (SMB) File Share resource which requires both a Physical Disk and Network Name dependencies.  The only resource types that do not usually depend on another resource are the Physical Disk and IP Address resources. (ref: KB171791) The only exception of a Physical Disk having any kind of dependency, is when it’s a Mount Point that is dependent of the root Physical Disk coming Online first before the actual Mount Point. (ref: KB280297)
  • When configuring Microsoft Distributed Transaction Coordinator (MS DTC) on a cluster, make sure to create a separate MS DTC Group with its unique Physical Disk, Network Name and IP Address resources. (ref: KB301600). 

    NOTE:  Before brining MS DTC resource online, you should confirm Enable Network DTC Access is enabled. (ref: KB817064

    Under some situations, applications that can heavily us MS DTC may require Enable Network COM+ Access to be enabled. (ref: KB817065)

    Pages: 1 2 3

    Loading

    Contextual Related Posts:

  • No followup yet

    Leave a Response

    Comment Preview
    « Live Maps returns to UK usersIdentity Lifecycle Manager (ILM) “2″: Coming soon and it’s all about TCO! »
    Feed Icon

    Subscribe via RSS or email: