How to verify VCS installation on a system
Symantec recommends that you verify your installation of Symantec Cluster Server (VCS) on a system before you install or upgrade VCS. This allows you to know about the product prerequisites, installed product version, and configuration. You can verify installation of VCS on a system using the following techniques: Operating System (OS) commands Script-based Installer Symantec Operations Readiness Tools (SORT) checks VCS command validation OS commands You can run native OS commands on the system to verify whether VCS is installed. The following table lists the commands to verify the VCS installation and the VCS version and patches installed on the system. Use cases AIX HP-UX Linux Solaris Verifying VCS installation lslpp -l VRTSvcs swlist VRTSvcs rpm –qi VRTSvcs For Solaris 10: pkginfo –l VRTSvcs For Solaris 11: pkg info VRTSvcs Verifying VCS version and patches lslpp -l VRTSvcs swlist VRTSvcs rpm –qi VRTSvcs showrev –p | grep VRTSvcs You can use these commands to verify which product packages are installed on the system.To get a complete list of required and optional packages for VCS, see the product release notes on theSORTwebsite. Note:On Linux, there is no sparse patch or patch ID. Therefore, the package version itself indicates the patch version of the installed VCS. Advantage of using the OS command technique By default, native commands are available on a system and can be used with ease. Limitations of using the OS command technique You must run OS commands as root on the cluster nodes. OS commands are useful for package and patch validation. However, these commands do not provide complete information about the VCS product installation. You need to run multiple commands to validate whether the required packages are installed on the system Script-based Installer Symantec recommends that you use the script-based installer to install Symantec products. The script-based installercan be used to identify which products from the Storage Foundation and High Availability (SFHA) family are installed on the system. The installer script can be executed to get a list of VCS packages and their versions installed on the system. These commands can be executed on AIX, HP-UX, Linux, and Solaris. The installer also allows you to configure the product, verify the pre-installation requisites, and view the description of the product. The following command provides the major version of the product and packages installed on the system. However, it does not provide details such as join version, build date, and patches installed on the other nodes in the cluster. To use this command, VCS must be already installed on the system. To use the script-based installer to verify the version of VCS installed on the system Run the following command: #/opt/VRTS/install/installvcs<version> –version Whereversionis the specific release version. For example, to validate the VCS 6.1 installation on the system, run the following command: #/opt/VRTS/install/installvcs61 –version To initiate the VCS installation validation using the product DVD media provided by Symantec, run the following installer script: #<dvd-media-path>/installer -version The installer script lists the Symantec products installed on the system along with the version details of the products. You can also use this script to perform a pre-check of the required package dependencies to install the product. If the product is already installed on the system and you want to validate the list of packages and patches along with their version, run the following command: #/opt/VRTS/install/showversion This command provides details of the product installed on all the nodes in a cluster. This information includes the product name, required and optional packages installed on the system, installed and available product updates, version, and product license key. Advantage of using script-based installer A single script validates all nodes in the cluster. Therefore, it does not need any platform-specific commands for performing validation. Limitation of using script-based installer The VRTSsfcpi package must be installed on the systems. Note: The VRTSsfcpi package was first released in VCS 6.0 and is available in the later versions. For earlier versions, use the installer from the DVD media. As an alternative, you can launch theinstaller from the DVD provided by Symantec, regardless of the product version. For more information about installing VCS using installer, seeInstalling VCS using the installer. SORT checks SORT provides a set of web-based tools to automate and simplify time-consuming administrator tasks. For example, the data collector tool gathers system-related information and generates web-based and text-based custom reports. These reports capture the system and platform-related configuration details and list the Symantec products installed on the system. SORT generates the following custom reports: Installation and Upgrade Risk Assessment License/Deployment You can generate and view custom reports to check which Symantec products are installed on a system. These reports list the passed and failed checks and other significant details you can use to assess the system. The checks and recommendations depend on the installed product. For SORT checks, see System Assessments. To generate a SORT custom report, On theData Collectortab, download the appropriate data collector for your environment. Follow the instructions in the README file to install the data collector. Run the data collector. It analyzes the nodes in the cluster and stores results in an XML file. On theUpload Reportstab, upload the XML file to the SORT website. SORT generates a custom report with recommendations and links to the related information. For more information about custom reports, visithttps://sort.symantec.com. Advantage of using the SORT checks SORT checks provide comprehensive information about the installed product. Limitation of using the SORT checks SORT data collector is not a part of product media and must be downloaded and installed on the system to generate reports. VCS command validation VCS provides a set of commands to validate and provide additional details of the components installed as a part of VCS product installation. For more information about verifying the VCS installation using VCS commands, seeSymantec™ Cluster Server 6.1 Administrator's Guide. The VCS command validation method allows you to check if VCS is correctly configured on the nodes in a cluster. To verify the status of the VCS components such as Low-Latency Transport (LLT), Group Membership Services/Atomic Broadcast (GAB), and the VCS engine, you can inspect the content of the key VCS configuration files or run the following VCS commands. Component Command Provides GAB #gabconfig -W GAB protocol version LLT #lltconfig -W LLT protocol version VCS engine #had -version HAD engine version and join version Cluster #hasys -state Cluster state Advantages of using VCS commands VCS commands provide comprehensive information about the cluster. VCS commands can be used for configuring the cluster. Limitation of using VCS commands VCS commands can be used only after the VCS product is completely installed and configured on the system. Frequently asked questions The following is a list of VCS installation-related frequently asked questions: Where do I check the availability of the CPI installer on a system? The installer script is located at /opt/VRTS/install. Where are the CPI installation logs located? The installation logs are located at /opt/VRTS/install. Where do I find information about SORT checks and reports? For information about SORT checks and reports, visithttps://sort.symantec.com. How do I validate a system before installing VCS? Before you install VCS, you must make sure the system is ready. To validate the system, use the installer script on the Symantec DVD. To start the pre-installation validation on the system and verify whether the system meets the product installation requirements, run the following command: #installer –precheck
Veritas InfoScale 7.0: Licensing Veritas InfoScale 7.0
You require a license to install and use Veritas InfoScale products. There are two ways you can register the Veritas InfoScale product license keys: Use key-based licensing When you purchase a Veritas InfoScale product, you receive a License Key certificate. The certificate specifies the product keys and the number of product licenses purchased. Use keyless licensing The license is registered based on the product you install. Within 60 days of choosing this option, you must install a valid license key corresponding to the license level, or continue with keyless licensing by managing the systems with Veritas InfoScale Operations Manager. You can register the product license keys either manually or by using the installer. You can use the vxlicinstupgrade utility, if you want to: Upgrade to another Veritas InfoScale product Upgrade a temporary license to a permanent license Manage co-existence of multiple licenses For more information on licensing Veritas InfoScale products, see: About Veritas InfoScale product licensing Registering Veritas InfoScale using product license keys Registering Veritas InfoScale product using keyless licensing Updating your product licenses Using the vxlicinstupgrade utility Veritas InfoScale documentation can be found on the SORT website.
NFS agent for CFS share
Dear All, I have setup CFSshare. I can see under cfsshare display, but if I run "cfsshare share /emm2 rw" is NOT sharing but from the Java Console of the cluster. The NFS resource has got a question MARK. So I am really not too what to do now., root@node_1# cfsmount /emm5 rw Mounting... [/dev/vx/dsk/mobile_dg/mobile_vol_4] already mounted at /emm5 onnode_0 [/dev/vx/dsk/mobile_dg/mobile_vol_4] already mounted at /emm5 on node_1 root@node_1# cfsshare share /emm5 Warning: V-35-465: Resource [share3] is not online on system [node_0]. Warning: V-35-465: Resource [share3] is not online on system [node_1]. root@node_1# cfsshare display CNFS metadata filesystem : /locks Protocols Configured : NFS #RESOURCE MOUNTPOINT PROTOCOL OPTIONS share1 /emm2 NFS rw share2 /emm3 NFS rw share3 /emm5 NFS rw root@node_1# Regards, Thokozani
Oracle Data Base Replication with VVR under SFCFSHA/DR
Hi All; we are looking for whether VVR can use for the oracle database replication instead of oracle data guard solution. If it is used, do you know veritas gives support for any problem faced. even VVR keeps the write order fidelity, it is not certain the database integrity will ve preserved at the disaster site. do you have any best practices and white papers, experience, anything you suggest for this deploymeny?
How To Manage Multiple VCS Clusters from a Central Location
What is the preferred tool/process used to manage multiple VCS clusters? We have several clusters in our environment and to date, the administrators RDP to one of the nodes in the cluster, open the Veritas Cluster Manager - Java Console. What is the solution to see all clusters in a single window or dashboard and also get notification of cluster events? Where is the documentation of how to setup the solution? Are there any videos that demonstrate how to setup or how the solution works?
Symantec ApplicationHA 6.0: Configuring single sign-on (SSO)
Symantec ApplicationHA monitors applications running inside virtual machines managed by a VMware vCenter Server. Symantec ApplicationHA adds a layer of application awareness to the core HA functionality offered by VMware virtualization technology. SSO is an authentication process where you can enter one user name and password and have access to multiple machines or multiple applications. In Symantec ApplicationHA, after you configure SSO, an authenticated vCenter user does not have to provide the virtual machine user credentials each time that user logs on to configure and monitor applications. You must configure SSO between: The virtual machine and ApplicationHA Console host. The virtual machines at the protected site and ApplicationHA Console host at the recovery site. The ApplicationHA Console host uses the Symantec ApplicationHA Authentication service to provide secure communications between the virtual machine and the Console host. It uses digital certificates for authentication and uses Secure Sockets Layer (SSL) to encrypt communications. SSO authentication is used for all operations on the virtual machine. Configuring SSO manually between the virtual machine and the ApplicationHA Console host You must specify the virtual machine administrator account to set up permanent authentication for the virtual machine. Use the ApplicationHA tab to manually configure SSO between the virtual machine and the Console host. Manually configure SSO if: SSO is not configured while installing or upgrading the guest. SSO configuration failed while installing or upgrading the guest. You have installed or upgraded the guest components using the command line interface. For more information, see the "Configuring single sign-on between the virtual machine and the ApplicationHA Console" section in the Symantec ApplicationHA User's Guide. Configuring SSO between the virtual machines at the protected site and the ApplicationHA Console host at the recovery site After you install Symantec ApplicationHA components for VMware Site Recovery Manager (SRM), you must configure SSO between the virtual machines at the protected site and the ApplicationHA Console host at the recovery site. You can use the Symantec ApplicationHA SRM Components Configuration Wizard to configure SSO for virtual machines. You can launch the configuration wizard from the ApplicationHA Console host at the recovery site. For more information, see the “Configuring single sign-on between the recovery and protected site” section in the Symantec ApplicationHA User's Guide. Symantec ApplicationHA documentation for other releases and platforms can be found on the SORT website.
SFHA Solutions 6.0: How to Install Veritas SFHA Solutions 6.0 Products
Veritas Storage Foundation and High Availability (SFHA) Solutions 6.0 includes products such as DMP, SF, SFHA, SFCFSHA, SF Oracle RAC, SF Sybase CE, VCS, and VirtualStore. Got questions about downloading, licensing, or installing the SFHA Solutions 6.0 products? The following HOWTO articles provide an overview and guide you through the procedures: SFHA Solutions products 6.0 licensing About Veritas SFHA Solutions product licensing Setting or changing the Veritas SFHA Solutions product level for keyless licensing Installing Veritas SFHA Solutions product license keys How to install Veritas SFHA Solutions 6.0 products SFHA Solutions installation and configuration methods SFHA Solutions installation scripts SFHA Solutions product installer Downloading the SFHA Solutions software Mounting the SFHA Solutions product disc Setting the PATH and MANPATH environment variables Installing the SFHA Solutions products using the installer Installing language packages on Solaris systemsSFHA Solutions 6.0.1: Adding a node to SFHA clusters
After you install Storage Foundation and High Availability (SFHA) and create a cluster, you can add and remove nodes from the cluster. You can create clusters of up to 64 nodes. To add a node to an existing SFHA cluster: Complete the prerequisites and preparatory tasks before adding a node to the cluster. Before adding a node to an existing SFHA cluster, verify that you have met the hardware and software requirements. You also need to prepare the new node. For information on preparing to add a node to an existing cluster, see: Before adding a node to a cluster Add a new node to the cluster. There are three ways to add a new node to the cluster: Adding a node to a cluster using the SFHA installer Adding a node using the Web-based installer Adding the node to a cluster manually Update the repository database (only if you are using the Storage Foundation for Databases (SFDB) tools). If you are using Database Storage Checkpoints, Database FlashSnap, or SmartTier for Oracle in your configuration, you have to update the SFDB repository to enable access for the new node after it is added to the cluster. For more information on updating the SFDB repository, see: Updating the Storage Foundation for Databases (SFDB) repository after adding a node. Veritas Storage Foundation and High Availability documentation for other platforms and releases can be found on the SORT website.