EV Admin Service does not start after failing over on a Microsoft Cluster
Article ID: 100014066
Updated On:
Description
Error Message
Event ID: 4143 Insufficient Diskspace is available on drives [All Mapped Drives] for the Enterprise Vault to run.
Enterprise Vault will now be shut down; to correct this problem, delete any unwanted files and restart Enterprise Vault
V-437-4143
The following is shown in a Dtrace of the AdminService process:
CPerfMonitor::Is Valid: [YES]|
CWMIPerfQuery::GetCounter(B) (Entry)|
CWMIPerfQuery::GetFormattedValue - (Entry)|
CWMIPerfQuery::GetFormattedValue - [Win32_PerfFormattedData_PerfDisk_LogicalDisk] Value [0.000000]|
CPerfMonitor::CheckCounters I: value[5] 0|
CPerfMonitor::CheckCounters critical level (99) breached|
Cause
This can occur when the EV Admin Service resource starts up before the storage resource(s) have initialized.
Resolution
The EV Admin Service resource should be configured to list all storage resources as dependencies. This will ensure that the storage resources are initialized prior to the Admin Service's checking them for free disk space.
The Enterprise Vault Configuration wizard sets up the proper dependencies for the Enterprise Vault components. However, any storage resources subsequently added must be configured with the proper dependencies. It is these subsequently added storage resources that are most likely to cause the issue described above if they are not configured properly.
Issue/Introduction
During a failover of an active passive Microsoft Cluster, the Enterprise Vault (EV) Admin Service will not start, citing insufficient disk space. The disks are the same as on the Active node and have plenty of space. The drive letters that are cited as lacking sufficient space are not consistent across multiple failovers.
Additional Information
Adding shared storage to an existing Windows Server failover cluster for an Enterprise Vault cluster server
You may want to add shared storage to an existing Enterprise Vault cluster to provide more storage for an Enterprise Vault cluster server.
To add shared storage to an existing Windows Server failover cluster for an Enterprise Vault cluster server
- Set up the additional shared disks and volumes, sharing the volumes on the nodes that require access to them.
-
For the cluster server that is to use the new storage:
-
Add a Storage Device resource to the cluster service for each new volume.
Note:
It is important to make the Storage Device resource dependent on the Enterprise Vault Server Instance resource. This prevents two Enterprise Vault cluster servers from running on the same clustered node in an unsupported "active/active" configuration.
The Enterprise Vault Server Instance resource is not reliant on any disk storage; it does not store data on any disk that is configured within the cluster group.
-
Change the Properties of the Admin Service resource to add a dependency on each new Storage Device resource.
-
- Specify the required nodes as possible owners for the new Storage Device resources, according to your cluster operation mode.
- Test the modified cluster to confirm that the Enterprise Vault cluster server can access the new shared storage successfully before and after failover.
