Frequently Asked Questions

Chances are, others have the same questions that you do. Therefore, we have taken the common questions for Diskeeper, Sitekeeper and Undelete and provided the answers (and the questions) below in our Frequently Asked Questions section. Simply select the product below that you have questions about. If you can’t find the answer you’re looking for, you can submit a tech support question here.

Diskeeper | Sitekeeper | Undelete

Question
Does Diskeeper support windows clustering?
Answer
Diskeeper is certified for Windows Clustering. To run Diskeeper in a Clustered environment, perform the following steps: 1. On the system that has control of the clustered disks, install Diskeeper and schedule it. 2. Fail the clustered disks over to the other system, install Diskeeper and schedule it. After performing the above steps, Diskeeper will run on the clustered system that remains in operation after the other clustered system has experienced a system failure. Diskeeper will also run on the clustered disk/partition in an active-active cluster, defragmenting the clustered disk/partition on the system that currently has control of the disk/partition. Note: Diskeeper's Boot Time Defragmentation will not function on clustered partitions as clustered volumes fail over during system reboots. Note: It is not recommended to schedule defragmentation on Quorum drives. Defragment these drives as needed during maintenance windows. TIP: Assuming that ALL nodes in a cluster share identical drive lettering (e.g. C:\, D:\, Q:\, U:\, etc…) step 2 can be eliminated, by simply copying the schedule file from the first node to any subsequent nodes’ Diskeeper program folder.

Question

Does Diskeeper support windows clustering?

Answer

Diskeeper is certified for Windows Clustering. To run Diskeeper in a Clustered environment, perform the following steps:

1. On the system that has control of the clustered disks, install Diskeeper and schedule it.

2. Fail the clustered disks over to the other system, install Diskeeper and schedule it.

After performing the above steps, Diskeeper will run on the clustered system that remains in operation after the other clustered system has experienced a system failure. Diskeeper will also run on the clustered disk/partition in an active-active cluster, defragmenting the clustered disk/partition on the system that currently has control of the disk/partition.

Note: Diskeeper's Boot Time Defragmentation will not function on clustered partitions as clustered volumes fail over during system reboots.

Note: It is not recommended to schedule defragmentation on Quorum drives. Defragment these drives as needed during maintenance windows.

TIP: Assuming that ALL nodes in a cluster share identical drive lettering (e.g. C:\, D:\, Q:\, U:\, etc…) step 2 can be eliminated, by simply copying the schedule file from the first node to any subsequent nodes’ Diskeeper program folder.

<<Back