Veritas InfoScale 7.3.1 Release Notes - Windows
- Release notes for Veritas InfoScale
- Limitations
- Deployment limitations
- Cluster management limitations
- Storage management limitations
- Multi-pathing limitations
- Replication limitations
- Solution configuration limitations
- Internationalization and localization limitations
- Interoperability limitations
- Known issues
- Deployment issues
- Cluster management issues
- Cluster Server (VCS) issues
- Cluster Manager (Java Console) issues
- Global service group issues
- VMware virtual environment-related issues
- Cluster Server (VCS) issues
- Storage management issues
- Storage Foundation
- VEA console issues
- Snapshot and restore issues
- Snapshot scheduling issues
- Storage Foundation
- Multi-pathing issues
- Replication issues
- Solution configuration issues
- Disaster recovery (DR) configuration issues
- Fire drill (FD) configuration issues
- Quick recovery (QR) configuration issues
- Internationalization and localization issues
- Interoperability issues
- Miscellaneous issues
- Fibre Channel adapter issues
- Deployment issues
Resource for Exchange Information Store may take time to online
If the Microsoft Exchange database is in an inconsistent state and the enterprise agent for Exchange attempts to bring the resource for Microsoft Exchange Information Store (IS) service online, the IS service runs a recovery on the Exchange database. This recovery may take considerable time, depending on the number of transaction logs to be replayed.
As a default behavior, the enterprise agent for Exchange waits in the Online entry point and returns only when the IS resource starts or when the start operation fails. When IS service is delayed, the enterprise agent for Exchange logs the following message:
The Information Store service is not yet started. It might be running recovery on the database.
In some cases, however, the IS service may not be running a recovery.
Workaround: If the IS service is stuck in the STARTING state, you can force the Online entry point to exit without waiting for IS service to start.
To work around this issue
- Open the Registry Editor.
- From the navigation pane, go to
\\hkey_local_machine\software\veritas\vcs\ exchconfig\parameters\msexchangeis
- On the Edit menu, select New, and then click DWORD Value.
- Name the value ForceExit.
- Right-click the value and select Modify.
- In the Edit DWORD Value dialog box, specify the value data as '1'.
Click OK
When the Online routine detects this value in the registry, it exits without waiting for the IS resource to start.
Note:
To restore the default behavior of the agent, set the ForceExit value to zero.