 | ||
| Features introduced in VCS 5.0 | ||
|---|---|---|
| Prev | Veritas Cluster Server Release Notes | Next |
See the Veritas Cluster Server User's Guide for details.
The new Cluster Management Console replaces Cluster Manager (Web Console) and CommandCentral Availability.
Cluster Management Console enables administration and analysis for VCS clusters in your enterprise from a single console. You can install Cluster Management Console on a stand-alone system to manage multiple clusters or you can install the console on cluster nodes to manage a local cluster. When installed to manage a local cluster, the console is configured as part of the ClusterService group and the AppName attribute is set to cmc.
Cluster Monitor is now called Cluster Connector
CommandCentral Availability installed a component called Cluster Monitor on cluster nodes. The updated component is called Cluster Connector.
VCS 5.0 lets you assign VCS privileges to native users at an operating system (OS) user group level in secure clusters.
Assigning a VCS role to a user group assigns the same VCS privileges to all members of the user group, unless you specifically exclude individual users from those privileges.
See the Veritas Cluster Server User's Guide for more information.
VCS now supports configuring up to five levels of service group dependencies. The exception is the online local hard dependency, for which only two levels are supported.
The new RemoteGroup agent monitors and manages service groups in a remote cluster. See the Veritas Cluster Server Bundled Agents Reference Guide for more information about the agent.
You can customize the behavior of the hastop command by configuring the new EngineShutdown attribute for the cluster.
VCS Simulator now supports deleting simulated clusters.
Symantec recommends using the same tool (command line or Java Console) to create and delete a cluster. For example, if you created the cluster from the Java Console, delete the cluster from the Java Console.
Dynamic multi-pathing (DMP) allows coordinator disks to take advantage of the path failover and the dynamic adding and removal capabilities of DMP. You can configure coordinator disks to use Veritas Volume Manager DMP feature.
You can set the coordinator disks to use either raw or DMP as the hardware path to a drive. See the Veritas Cluster Server Installation Guide for more information.
See the Veritas Cluster Server Installation Guide for a strategy on upgrading to VCS 5.0 while ensuring a minimal downtime for your applications.
VCS backs up all configuration files (<config>.cf) including main.cf and types.cf to <config>.cf.autobackup. The configuration is backed up only if the BackupInterval is set and the configuration is writable.
When you save a configuration, VCS saves the running configuration to the actual configuration file (i.e. <config>.cf) and removes all autobackup files. This does away with the VCS behavior of creating stale files
If you do not configure the BackupInterval attribute, VCS does not save the running configuration automatically.
See the Veritas Cluster Server User's Guide for more information.
In certain situations, the HP-UX operating system may assign the CPU to high priority interrupts or processes like HAD. To overcome this issue, VCS provide the option of running HAD on a specific processor. This way you can shield HAD from other high priority processes. See the Veritas Cluster Server User's Guide for more information.
When the VCS engine HAD dumps core, the core is written to the directory /var/VRTSvcs/diag/had, where the diagnostic information is stored. When HAD and GAB encounter heartbeat problems, VCS runs the script /opt/VRTSvcs/bin/vcs_diag to collect the diagnostic information.
The current working directory of VCS engine is VCS_DIAG whose default value is $VCS_HOME/diag. In earlier versions of VCS, the default directory of HAD was VCS_HOME whose default value was /opt/VRTSvcs.
The VCS engine, HAD, runs as a high-priority process to send heartbeats to kernel components and to respond quickly to failures. In VCS 5.0, HAD runs logging activities in a separate thread to reduce the performance impact on the engine due to logging.
The new NFSRestart agent provides high availability to NFS locks. Use the agent in conjunction with the NFS agent. See the Veritas Cluster Server Bundled Agents Reference Guide for more information.
The NIC and MultiNICA agents now support VLAN interfaces. The agents do not configure the NICs, but can monitor them.
See the OS vendor's documentation on how to configure VLAN on your host, and ensure that the switch or router connected to such an interface is compatible with your configuration. Both server-side and switch-side VLAN configurations are supported.
VCS supports a virtual fire drill capability that lets you test whether a resource can fail over to another node in the cluster. Virtual fire drills detect discrepancies between the VCS configuration and the underlying infrastructure on a node; discrepancies that might prevent a service group from going online on a specific node. See the Veritas Cluster Server User's Guide for more information on running virtual fire drills.
Daemon Down Node Alive (DDNA) is a condition in which the VCS high availability daemon (HAD) on a node fails, but the node is running. When HAD fails, the hashadow process tries to bring HAD up again. If the hashadow process succeeds in bringing HAD up, the system leaves the DDNA membership and joins the regular membership. See the Veritas Cluster Server User's Guide for more information.
VCS 5.0 does not support using spaces as delimiters to separate vector, association, or keylist values. You must use a comma or a semicolon as a delimiter.
The new EngineVersion attribute replaces the MajorVersion and MinorVersion attributes. VCS stores version information in the following format:
major.minor.maintenance_patch_num.point_patch_num
VCS now provides finer control over the resfault trigger. The resfault trigger is now invoked if the TriggerResFault attribute is set to 1.
VCS enterprise agents are now installed in the /opt/VRTSagents/ha/bin directory.
The <agent>Types.cf files are now located at /etc/VRTSagents/ha/conf/<agent>.
VCS stores binary message catalogs (BMCs) at the following location:
/opt/VRTS/messages/language/module_name
The variable language represents a two-letter abbreviation.
The attribute pools also move from /var to /opt.
Use the -v option to retrieve concise information about the VCS version. Use the -version option to get verbose information.
VCS introduces the following new agents:
See No longer supported.
VCS now follows the licensing scheme that is described below:
| License | What's included |
|---|---|
| VCS | |
| VCS HA/DR |
Note Database agents are included on the VCS 5.0 disc. The replication and application agents are available via the Veritas High Availability Agent Pack.
VCS 5.0 introduces the following new attributes. See the Veritas Cluster Server User's Guide for more information.
The Veritas High Availability Agent for Sybase agent supports Sybase ASE 12.5.x and 15 on AIX, HP-UX, Linux, and Solaris.
The agent uses the Action entry point to support the virtual fire drill functionality.