12-06-2010 11:27 AM
What is the maximum number of disks in a disk group for SFW 5.1 in a Windows 2008 Cluster? We ran into a situation where a high number of luns >100 will have slow failover times. The same number of luns in 2003 cluster does not have that same problem for us. Total storage is around 6 TB.
Solved! Go to Solution.
12-06-2010 01:04 PM
The maximum number of disk in a SFW dynamic disk group is not limited however, we do not recommend using a large number of disks to make up the volumes. What we do recommend is to carve out larger LUNS on the backend storage array eliminating the need for a large number of disks to make up a volume. This will cut back on the overhead SFW has to make when scanning the LUNS presented to a system on import.
Volume manager can take anywhere from 0 to 120 seconds to scan volume on import (with 120 seconds being the timeout) before the import will then fail.
What recommend to run VxScrub -p on the nodes. This will purge the old stale volume mount entries from the registry and allow the disk to import faster. (http://www.symantec.com/business/support/index?page=content&id=TECH39194)
Note this does require a reboot of the system.
Running the VxScrub utility as a part of regular system maintenance will shrink the registry size and avoid this problem. Rebooting the system after running vxscrub is mandatory. With the -p option, the utility can uninstall and clean up unused volume, disk, and Mount Manager registry entries. It also purges the registry to physically shrink the size of the registry. Run vxscrub -pfrom the command line and then immediately reboot the system to perform this operation.
12-06-2010 01:04 PM
The maximum number of disk in a SFW dynamic disk group is not limited however, we do not recommend using a large number of disks to make up the volumes. What we do recommend is to carve out larger LUNS on the backend storage array eliminating the need for a large number of disks to make up a volume. This will cut back on the overhead SFW has to make when scanning the LUNS presented to a system on import.
Volume manager can take anywhere from 0 to 120 seconds to scan volume on import (with 120 seconds being the timeout) before the import will then fail.
What recommend to run VxScrub -p on the nodes. This will purge the old stale volume mount entries from the registry and allow the disk to import faster. (http://www.symantec.com/business/support/index?page=content&id=TECH39194)
Note this does require a reboot of the system.
Running the VxScrub utility as a part of regular system maintenance will shrink the registry size and avoid this problem. Rebooting the system after running vxscrub is mandatory. With the -p option, the utility can uninstall and clean up unused volume, disk, and Mount Manager registry entries. It also purges the registry to physically shrink the size of the registry. Run vxscrub -pfrom the command line and then immediately reboot the system to perform this operation.
12-09-2010 11:37 AM
Is there a documented maximum number of disk groups and disks SFW supports?