Veritas InfoScale™ 7.3.1 Release Notes - Linux
- Introduction
- Changes introduced in 7.3.1
- Changes related to installation and upgrades
- Changes related to the Cluster Server engine
- Changes related to Cluster Server agents
- Changes related to InfoScale in cloud environments
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to replication
- Changes related to Dynamic Multipathing
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Virtualization known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Cluster Server agents for Volume Replicator known issues
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Storage Foundation for Sybase ASE CE known issues
- Application isolation feature known Issues
- Cloud deployment known issues
- Issues related to installation and upgrade
- Software Limitations
- Virtualization software limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation for Sybase ASE CE software limitations
VVR configuration may go in a primary-primary configuration when the primary node crashes and restarts [3314749]
The AutoResync attribute of the RVGPrimary and RVGSharedPri agent control whether the agent must attempt to automatically perform a fast-failback resynchronization of the original primary after a takeover and after the original primary returns. The default value of this attribute is 0, which instructs the agent not to perform a fast-failback resynchronization of the original primary after a takeover and after the original primary returns. The takeover is performed automatically since the default value of the AutoTakeover attribute of the RVGPrimary and RVGShared agents is 1. Thus, the default settings of AutoTakeover and AutoResync set to 1 and 0 respectively cause the first failover to succeed when the original primary goes down, and on return of the original primary, the Replicated Data Set (RDS) ends up with a primary-primary configuration error.
Workaround: Set the default value of the AutoResync attribute of the RVGPrimary agent to 1 (one) when you want the agent to attempt to automatically perform a fast-failback resynchronization of the original primary after a takeover and after the original primary returns. This prevents the primary-primary configuration error. Do not set AutoResync to 1 (one) if you intend to use the Primary-Elect feature.
Moreover, if you want to prevent VCS from performing an automatic takeover and fast-failback resynchronization, set AutoTakeover and AutoResync attributes to 0 for all the RVGPrimary and RVGSharedPri resources in your VCS configuration. For more information, refer to the RVGPrimary and RVGSharedPri agent sections of the Replication Agents chapterin the Cluster Server Bundled Agents Reference Guide.