Veritas InfoScale™ 8.0.2 Release Notes - Linux
- Introduction and product requirements
- Changes introduced in InfoScale 8.0.2
- Changes related to VxFS
- 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
- Known issues
- Issues related to installation, licensing, upgrade, and uninstallation
- REST API known issues
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Veritas File System known issues
- Virtualization 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
- Application isolation feature known Issues
- Cloud deployment known issues
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Issues related to installation, licensing, upgrade, and uninstallation
Upgrades to 8.0.2 may cause configuration errors in VVR replication (4115707)
This issue is observed when you upgrade to InfoScale 8.0.2 release. After the upgrade on the secondary site is complete, the RVG replication status shows that the RLINK is disassociated and the secondary SRL volume is missing.
This issue typically happens in cases where the SRL volume size is large (30 GB or more) and if the auto_recover
tunable is enabled. The SRL resync (recovery) process may take some time depending on the size of the SRL volume. The SRL volume remains unavailable during this time and any attempts to associate the SRL volume with the RVG fail.
The following errors are displayed in the replication status:
VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configuration error. Displayed status information is from Secondary and can be out-of-date. VxVM vxvol ERROR V-5-1-3681 Volume <volumename> state is not ACTIVE
Workaround:
Wait for the SRL volume resync (recovery) process to complete.
Check the progress using the following command:
# vxtask list
Once the recovery process is complete, the SRL volume status appears as enabled.
Compete the post-upgrade VVR replication configuration
- Identify the logowner node using the following command:
# vxprint -VI
- Configure the replication IP on the logowner node, if it is not already configured, and then verify using the following command:
# vxprint -PI
- Associate the SRL volume with the RVG:
# vxvol -g diskgroupname aslog rvgname srlname
- Recover the RLINK:
# vxrlink -g diskgroupname recover rlinkname
- Attach the RLINK on the secondary for the respective RVG:
# vxrlink -g diskgroupname -f att rlinkname
- Start the RVG:
# vxrvg -g diskgroupname start rvgname
- Restart the Veritas Volume Replicator Daemon (
vradmind
) on all nodes on both the primary and the secondary site:# /sbin/vxstart_vvr stop
# /sbin/vxstart_vvr start
- Check the replication status on the primary:
# vradmin -g diskgroupname -repstatus rvgname
- If the replication status shows as paused, then resume the replication:
# vradmin -g diskgroupname resumerep rvgname
- If the replication status shows as "logging to DCM " OR "DCM requires recovery", then resync the RVG:
# vradmin -g diskgroupname resync rvgname