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 Undelete support Windows clustering?
Answer
Undelete is fully compatible with Microsoft Clustering, but is not, by Microsoft's definition, "cluster aware," nor does it need to be. It is not necessary to create any type of resource group for Undelete to operate, but there are a few manual steps that need to be followed, so the local boot partition and the shared clustered partitions are known by Undelete on each node in the cluster. Also, make sure you are using Undelete version 2.1.064, or higher. Here are the steps to install Undelete correctly in a clustered environment. 1. Install Undelete on the primary node in the cluster. 2. When the system reboots, move the disk resources group back to the primary node. 3. Launch Undelete and go to the Recovery Bin Properties. The local disk volume as well as the shared disks should be seen. 4. Click OK. This creates the Recovery Bins on the shared clustered disks that weren't there during the reboot of the node. 5. Install Undelete on the other node and reboot. 6. Move the disk resources back to the node where you just installed Undelete (non-primary node). 7. Again launch Undelete and go to the Recovery Bin Properties. The local disk volume as well as the shared disks should be visible to Undelete. 8. Click OK and close Undelete. 9. Move the disk resources back to the primary node in the cluster and you are done. By doing this, both nodes now have the device intercept driver and file filter loaded. The Undelete service is running on both systems (as a Service), but since the shared clustered disks are known ONLY to one system at a time, only files deleted by that controlling system are captured or moved into the Recovery Bins. There is no need to set up or change this service.

Question

Does Undelete support Windows clustering?

Answer

Undelete is fully compatible with Microsoft Clustering, but is not, by Microsoft's definition, "cluster aware," nor does it need to be. It is not necessary to create any type of resource group for Undelete to operate, but there are a few manual steps that need to be followed, so the local boot partition and the shared clustered partitions are known by Undelete on each node in the cluster. Also, make sure you are using Undelete version 2.1.064, or higher.

Here are the steps to install Undelete correctly in a clustered environment. 1. Install Undelete on the primary node in the cluster.

2. When the system reboots, move the disk resources group back to the primary node.

3. Launch Undelete and go to the Recovery Bin Properties. The local disk volume as well as the shared disks should be seen.

4. Click OK. This creates the Recovery Bins on the shared clustered disks that weren't there during the reboot of the node.

5. Install Undelete on the other node and reboot.

6. Move the disk resources back to the node where you just installed Undelete (non-primary node).

7. Again launch Undelete and go to the Recovery Bin Properties. The local disk volume as well as the shared disks should be visible to Undelete.

8. Click OK and close Undelete.

9. Move the disk resources back to the primary node in the cluster and you are done.

By doing this, both nodes now have the device intercept driver and file filter loaded. The Undelete service is running on both systems (as a Service), but since the shared clustered disks are known ONLY to one system at a time, only files deleted by that controlling system are captured or moved into the Recovery Bins. There is no need to set up or change this service.

<<Back