Veritas InfoScale™ 7.4.2 Release Notes - Solaris
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Fixed issues
- 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 software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager 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
- 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
- GAB 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
- Issues related to installation and upgrade
DCM logging in DCO
In InfoScale 7.4.1 and prior releases, when replication is configured, a DCM log is associated as separate log plex to each data volume in the RVG. Starting with version 7.4.2, InfoScale allows you to maintain DCM logs as per-volume FMR maps inside the DCO that is associated with the corresponding data volumes.
Data Change Map can be associated to a data volume in one of the following ways:
DCM logging in DCO
DCM logging using DCM log plexes
Starting with InfoScale version 7.4.2, for new replication setups, DCM logs are by default allocated as per-volume FMR maps in DCO.
The setups, where older version of InfoScale is upgraded and replication is already configured, continue to use the pre-configured DCM log plexes. In such a case, you can choose to either use the DCM logging using DCM log plexes or configure DCM logging in DCO.
You can use the vxprint -Vl command to verify what type of DCM logging is enabled in your setup. The presence of the dcm_in_dco
flag in the output of the vxprint command indicates that DCM logging is configured in DCO. If the flag is not set and DCM log plexes are associated with data volumes under the RVG, DCM logging is set to use DCM log plexes.
You can use the pre-existing vradmin createpri, vradmin addsec, and vradmin addvol commands to configure DCM logging in DCO. You can also use the -dcmplex option with these commands to change the configuration to use DCM log plexes even for new replication configurations.
Starting with InfoScale 7.4.2, for a new replication setup, DCM logging is configured in DCO by default. However, you can choose to configure DCM log plexes.
To use DCM log plexes, perform the following steps:
- Setup the primary RVG.
# vradmin -g <dg_name> -dcmplex createpri <rvg_name> <data_volume> <srl_name>
- Setup and associate secondary RVG.
# vradmin -g <dg_name> -dcmplex addsec <rvg_name> <primary_host> <sec_host>
- Add data volumes to RVG
# vradmin -g <dg_name> -dcmplex addvol <rvg_name> <data_volumes>
When you upgrade InfoScale from an older version and replication is already configured, the setup continues to use the preconfigured DCM log plexes.
Perform the following steps to enable DCM logging in DCO in such upgraded setups.
- Stop replication
# vradmin - g <dg_name> stoprep <rvg_name> <sec_host>
- Un-configure replication by removing the secondary and the primary RVG.
# vradmin - g <dg_name> delsec <rvg_name> <sec_host>
# vradmin - g <dg_name> delpri <rvg_name>
- Remove DCM log plexes
# vxassist - g <dg_name> remove log <data_volume> logtype=dcm nlog=<#_dcm_plexes>
- Re-configure replication
# vradmin -g <dg_name> createpri <rvg_name> <data_volume> <srl_name>
# vradmin -g <dg_name> addsec <rvg_name> <primary_host> <sec_host>
# vradmin - g <dg_name> -a startrep <rvg_name> <sec_host>
For details, refer to Veritas InfoScale Replication Administrator's Guide.