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
VCS locks shared volumes during Exchange recovery
VCS monitors the shared volume used for storing Exchange databases. During online, offline, or clean operations, VCS MountV resources exclusively lock the shared volume. This exclusive lock may conflict with recovery of an Exchange volume.
Workaround: Veritas recommends freezing the service group containing the MountV resources before recovering Exchange volumes.
To recover an Exchange volume that is monitored by VCS
- Freeze the service group that contains the MountV resources corresponding to the volume to be recovered..
Type the following on the command prompt:
hagrp -freeze service_group [-persistent]
Here, service_group is the name of the service group.
- Recover the Exchange volume.
- Unfreeze the service group.
Type the following on the command prompt:
hagrp -unfreeze service_group [-persistent]
If custom resources are configured in VCS to monitor a snapshotted volume, follow the procedure before snapping back to the original or the replica.
Note:
If you cannot lock a volume for snapback, you can either force the operation or fail the operation and await administrator intervention.