You can use the System Status feature in the Administration Console to help you resolve this issue.
If you see this error frequently, slightly increase the number of Restore processes or threads. The settings are on the Advanced tab of the Storage service's properties.
Target | Veritas.EnterpriseVault.12.AdminService |
Category | EventCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Veritas.EnterpriseVault.12.EventProvider.DataSourceModuleType | Veritas.EnterpriseVault.MonitoringProfile |
WriteToDB | WriteAction | Microsoft.SystemCenter.CollectEvent | Veritas.EnterpriseVault.MonitoringProfile |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Veritas.EnterpriseVault.MonitoringProfile |
<Rule ID="Veritas.EnterpriseVault.12.AdminService.Restoration_queue_length_warning.Rule" Target="Veritas.EnterpriseVault.12.AdminService" Enabled="true" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Veritas.EnterpriseVault.12.EventProvider.DataSourceModuleType" RunAs="EV!Veritas.EnterpriseVault.MonitoringProfile">
<ComputerName>$Target/Host/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<EventNumber>41023</EventNumber>
<LogName>Application</LogName>
<EventSourceName>Enterprise Vault</EventSourceName>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectEvent" RunAs="EV!Veritas.EnterpriseVault.MonitoringProfile"/>
<WriteAction ID="WriteToDW" TypeID="MSDL!Microsoft.SystemCenter.DataWarehouse.PublishEventData" RunAs="EV!Veritas.EnterpriseVault.MonitoringProfile"/>
</WriteActions>
</Rule>