How many copies of Diskeeper are needed for an OpenVMS Cluster?
One. If all the disks on an OpenVMS Cluster are accessible from a single node, then one copy of Diskeeper can keep all the disks defragmented. This is true for a CI cluster, an NI cluster, a mixed interconnect cluster, a Local Area VAXcluster - any type of cluster supported by Digital.
For the best performance under most conditions, Executive Software recommends licensing and running Diskeeper on all the nodes of a cluster, then using Diskeeper to defragment the disks that are local to each node. By distributing the Diskeeper workload across the cluster, defragmentation can be completed in less time, since CPU and I/O resources are being shared by the various nodes in the cluster. Diskeeper must be licensed for each node on which it is installed.
If licensing Diskeeper on all of the cluster nodes is not feasible, the second alternative is to license Diskeeper for one or more of the fastest CPUs in the cluster. The faster the CPU, the faster Diskeeper completes its work, assuming the CPU is not already running at maximum potential (90% to 100% utilized).
If the high-powered CPUs in an OpenVMS Cluster are running at maximum potential, Diskeeper may offer the most improvement when licensed and running on one or more of the intermediate or smaller CPUs in the cluster. In cases such as these, licensing Diskeeper for the smaller VAXes may well be the optimum solution.
Regardless of which CPU(s) you choose to run Diskeeper on, licensing considerations require that you purchase a license for the largest CPU in an OpenVMS Cluster. To run Diskeeper on a smaller CPU in the same cluster, you need to purchase an additional license whether Diskeeper is actually used on the largest CPU or not.
Disks that are available to both platforms on a mixed VAX and Alpha cluster (known as a VMScluster) can be defragmented from either the VAX or the Alpha platform.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
