Today, the Failover Clustering services are essential for every organization that deploys line-of-business and business-critical e-commerce applications. The Failover cluster is the group of individual computers, which work together for increasing availability of services and applications. In some circumstances, where you use Failover Clustering with Windows 2003, your data and applications may become inaccessible. This behavior leads to serious data loss situations and you need windows data recovery to fix the issue.

You may face any of the below symptoms with Microsoft Windows 2003 Failover Clustering:

• The File Share resources become inaccessible even if the resources are displayed online by Cluster Administrator.

• Either of the below error message is logged into Cluster.log file:

  • 00000930.00000af8::{2003/01/01 23:00:00.001} File Share ShareName: Share has gone offline, Error=64!
    00000930.00000934::{2003/01/01 23:00:00.001} File Share ShareName: Share has gone offline, error=64!
    
    Click on Start, Run, cmd.exe
    Type "Net HelpMsg 64"
    "The specified network name is no longer available."

  • Description: Cluster File Share resource 'ShareName' has failed a status check. The error code is 32.
    
    Click on Start, Run, cmd.exe
    Type "Net HelpMsg 32"
    "The process cannot access the file because it is being used by another process."

• Local shares can not be accessed.

After this behavior of Windows operating system, the data become inaccessible. In order to access data in such cases, you need to perform