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 the SORT website. 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 installer can 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 Where version is 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 the installer from the DVD provided by Symantec, regardless of the product version. For more information about installing VCS using installer, see Installing 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 the Data Collector tab, 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 the Upload Reports tab, 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, visit https://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, see Symantec™ 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, visit https://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 –precheck14KViews0likes1Commentvxdisk list showing errors on multiple disks, and I am unable to start cluster on slave node.
Hello, If anybody have same experience and can help me, I am gonna be very thankful I am using solars 10 (x86 141445-09) + EMC PowerPath (5.5.P01_b002) + vxvm (5.0,REV=04.15.2007.12.15) on two node cluster. This is fileserver cluster. I've added couple new LUNs and when I try to scan for new disk :"vxdisk scandisks" command hangs and after that time I was unable to do any vxvm job on that node, everytime command hangs. I've rebooted server in maintanance windows, (before reboot switched all SGs on 2nd node) After that reboot I am unable to join to cluster with reason 2014/04/13 01:04:48 VCS WARNING V-16-10001-1002 (filesvr1) CVMCluster:cvm_clus:online:CVMCluster start failed on this node. 2014/04/13 01:04:49 VCS INFO V-16-2-13001 (filesvr1) Resource(cvm_clus): Output of the completed operation (online) ERROR: 2014/04/13 01:04:49 VCS ERROR V-16-10001-1005 (filesvr1) CVMCluster:???:monitor:node - state: out of cluster reason: Cannot find disk on slave node: retry to add a node failed Apr 13 01:10:09 s_local@filesvr1 vxvm: vxconfigd: [ID 702911 daemon.warning] V-5-1-8222 slave: missing disk 1306358680.76.filesvr1 Apr 13 01:10:09 s_local@filesvr1 vxvm: vxconfigd: [ID 702911 daemon.warning] V-5-1-7830 cannot find disk 1306358680.76.filesvr1 Apr 13 01:10:09 s_local@filesvr1 vxvm: vxconfigd: [ID 702911 daemon.error] V-5-1-11092 cleanup_client: (Cannot find disk on slave node) 222 here is output from 2nd node (working fine) Disk: emcpower33s2 type: auto flags: online ready private autoconfig shared autoimport imported guid: {665c6838-1dd2-11b2-b1c1-00238b8a7c90} udid: DGC%5FVRAID%5FCKM00111001420%5F6006016066902C00915931414A86E011 site: - diskid: 1306358680.76.filesvr1 dgname: fileimgdg dgid: 1254302839.50.filesvr1 clusterid: filesvrvcs info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 and here is from node where i see this problems Device: emcpower33s2 devicetag: emcpower33 type: auto flags: error private autoconfig pubpaths: block=/dev/vx/dmp/emcpower33s2 char=/dev/vx/rdmp/emcpower33s2 guid: {665c6838-1dd2-11b2-b1c1-00238b8a7c90} udid: DGC%5FVRAID%5FCKM00111001420%5F6006016066902C00915931414A86E011 site: - errno: Configuration request too large Multipathing information: numpaths: 1 emcpower33c state=enabled Can anybody help me? I am not sure about Configuration request too largeSolved5.8KViews1like16Commentsadding new volumes to a DG that has a RVG under VCS cluster
hi, i am having a VCS cluster with GCO and VVR. on each node of the cluster i have a DG with an associated RVG, this RVG contains 11 data volume for Oracle database, these volumes are getting full so i am going to add new disks to the DG and create new volumes and mount points to be used by the Oracle Database. my question: can i add the disks to the DG and volumes to RVG while the database is UP and the replication is ON? if the answer is no, please let me know what should be performed on the RVG and rlink to add these volumes also what to perform on the database resource group to not failover. thanks in advance.Solved4.5KViews0likes14CommentsSFHA Solutions 6.0.1: Using Veritas Cluster Server Simulator
Veritas Cluster Server (VCS) Simulator enables you to simulate and test cluster configurations. You can use VCS Simulator to view and modify service group and resource configurations and test failover behavior. VCS Simulator can run on a stand-alone system and does not require any additional hardware. You can install VCS Simulator only on a Windows operating system. VCS Simulator runs an identical version of the VCS High Availability Daemon (HAD) as in a cluster, ensuring that failover decisions are identical to those in an actual cluster. Using VCS Simulator, you can test configurations from different operating systems. For example, you can run VCS Simulator to test configurations for VCS clusters on Windows, AIX, HP-UX, Linux, and Solaris operating systems. VCS Simulator also enables you to create and test global clusters. You can administer VCS Simulator from the Java Console or from the command line. To download VCS Simulator, see: http://go.symantec.com/vcsm_download For more information on installing and administering VCS Simulator, see: Installing VCS Simulator on a Windows System Upgrading VCS Simulator Administering VCS Simulator Predicting VCS behavior using VCS Simulator Administering VCS Simulator from the Java Console Administering VCS Simulator from the command line interface VCS documentation for other releases and platforms can be found on the SORT website.4.3KViews3likes7CommentsClusdb File on Windows 2008 Microsoft Cluster
Hello, This week we are doing some tests with microsoft regarding Backup & Restore of Microsoft Clustered environment. I installed netbackup 7.6.0.1 Client on the servers (with windows cluster 2008) And we see that during the backup the CLUSDB file is being skipped. HHere is output from Diskshadow Exclude list: technote : http://www.symantec.com/business/support/index?page=content&id=TECH76997 WRITER "Cluster Database" - Writer ID = {41e12264-35d8-479b-8e5c- 9b23d1dad37e} - Writer instance ID = {46a75fd5-5b3b-4e8c-a140- 189419c23b13} - Supports restore events = TRUE - Writer restore conditions = VSS_WRE_ALWAYS - Restore method = VSS_RME_RESTORE_STOP_START - Requires reboot after restore = FALSE - Excluded files: + Component "Cluster Database:\Cluster Database" - Name: Cluster Database - Logical path: - Full path: \Cluster Database - Caption: ClusterDatabase - Type: VSS_CT_FILEGROUP [2] - Is selectable: TRUE - Is top level: TRUE - Notify on backup complete: FALSE - Components: - File List: Path = C:\Windows\cluster\, Filespec = CLUSDB - Paths affected by this component: - C:\Windows\cluster\ - Volumes affected by this component: - \\?\Volume{9b236815-75eb-11e3- 8eed-806e6f6e6963}\ [C:\] - Component Dependencies: Info From bpbkar While doing a backup: 10:46:14 BKR - C:\Windows\Cluster\ 10:46:14 INF - Filtered 'BEDS Exclude' Object: C:\Windows\Cluster\CLUSDB <- you can see the file was excluded when excplictly telling netbackup do d C: \ SystemStaete' \ Shadowcopycomponent backup. Question is : Why its in the Exclude list of the cluster vss, How should I do a GOOD backup of microsoft cluster if netbackup dosent do a backup of this file. BTW: ntbackup of microsoft is able to backup clusdb file.Solved2.9KViews1like10CommentsMS Cluster Storage migration problem
Hi guys, Could you please help me with storages migration problem. We have some WinServ 2003 clusters in our company and now we have a task to migrate our old SANs to the new ones. The best way we imagined as solution is to create 2 dynamic DG in Veritas SF: one for old SAN disks and another for new SAN disks, then join these groups into one DG, then make a mirroring between old and new disks and in final do the split of this common DG to 2 independent DG (one with old and one with new disks). You know that MS cluster can use only basic disks as storage resources. Therefore we can't add these disks into the DG in storage foundation. So, is there any solution here or not?Solved2.9KViews0likes6Commentsvxio: Cluster software communication timeout. Reservation refresh has been suspended
Hi, We are experiencing this error on one of our clusters. It's a two-node campus cluster with the following specifications SiteA Node1 is a Windows Server 2008 R2 virtual machine residing on a ESXi 5.1 host in this site Disk1 and 3 are LUNs in an enclosure in this site SiteB Node2 is a Windows Server 2008 R2 virtual machine residing on a ESXi 5.1 host in this site Disk2 and 4 are LUNs in an enclosure in this site We have created two VMDGs, one contains Disk 1 and 2, while the other contains Disk 3 and 4. On these VMDGs, we have created mirrored dynamic volumes. The VMDGs are then presented to the failover cluster. The quorum type on the failover cluster is a file share witness, on another server. We are also running Microsoft System Center Configuration Manager to install updates and patches on Node 1 and 2. Whenever patches are installed on a node, it gets restarted. Whenever that occurs, failover from Node 1 to Node 2 occurs for the cluster resource group. Everything seems to failover just fine, and the VMDG is imported successfully (according to the log). But 10 minutes after the VMDG has been imported, the following error is logged on Node 2 http://s28.postimg.org/ubh8skfh9/vmdg2.png If I check the status of the VMDGs in VEA its Deported for both VMDGs. http://s3.postimg.org/72ort9683/vmdg3.png But even if the disks and VMDGs seem to be offline on the active node, failover does not occur, as in Failover Cluster Manager, the VMDG is online, but there are no volumes enumerated on it. http://s12.postimg.org/p31vncct9/vmdg1.png Has anyone else experienced the same, and knows why the status of the disks change to deported, without failover occuring?Solved2.6KViews2likes6CommentsDisk group not imported
SFHA 5.1 SP2 , Win2008 64-bit, with sql2008 and disaster recovery configuration with global cluster manager The point is that due to unknown disk error during evacuating a cluster disk, a cluster disk group in the recovery site cannot be imported because of missing volumes. Is there a way of solving this (eg. force import the disk group, and reconfigure vvr rvg group) , or do i have to reconfigure this cluster disk group (VVR and so on) from the beginning ? Thanks in advanced2.5KViews0likes6CommentsWindows 2012 R2 Failover cluster and SF Volume Manager Disk Group
Hi, I just found this article and its quite the problem I'm facing right now: https://www-secure.symantec.com/connect/forums/one-cooperation-issue-about-windows-2012-r2-failover-cluster-and-sf-cluster-shared-disk-group I created a new Windows Server 2012 R2 Failover Cluster with several mirrored Disks in DynamicDiskGroups in StorageFoundation. As a next step, I wanted to add the Diskgroups from SF as a Ressource to my Failover Roles. Actual scenario: Cluster Role Name: C0002Z DiskGroupName in SF: DG_C0002Z_1 Then I added a Ressource to the Cluster Role via Add Resource -> More Resources -> Volume Manager Disk Group I changed the Name of the VMDG in "General" to "DG_C0002Z_1", apply, ok. Then I wanted to add the Name of the DiskGroup in Properties -> Properties -> DiskGroupName of the VMDG to "DG_C0002Z_1". And thats where I dont get any further. It doesn't matter which Name I want to enter into DiskGroupName, theres always this Error: There was an error saving properties for 'DG_C0002Z_1'. Failed to execute control code '20971654'. Error Code: 0x800700a0 One or more arguments are not correct I also tried to enter Names without special characters but that doesnt help eather. Do you have any Idea how to fix or bypass this issue? Thanks2.5KViews0likes1CommentVeritas Storage Foundation for Windows 5.1 Volume Manager Disk Group fails to come online
We are trying to implement a 2 Node SQL server cluster on Windows 2008 R2 for last few days. We have so far successfully completed Windows cluster part and have tested quorum failover and single basic disk failover. Our challenge is that for shared storage between two nodes where we have got 30 LUNs from SAN but we need to have single drive. Since merging LUNs at SAN level is not an option for us and MSCS does not understand dynamic disk group created using winodws disk manager we have to use Veritas Storage Foundation for windows 5.1. We have successfully installed SFW 5.1 and created Cluster Dynamic Disk group and Volume on this disk group. This volume is visible in Windows Explorer without any issue. To add this disk group in cluster we followed below steps 1. In "Failover Cluster Manager" we created "Empty Service or Application" 2. Added "Volume Manager Disk Group" resource in the application. 3. After right clicking on the resource and selecting "Bring this resource online option" the disk group was brought online. To test the failover we rebooted the first node. The disk group failed over to the second node without any issue. To bring back disk group on node one again we restarted the second node, however this time on the first node the disk group could not come online with status was shown as "Failed". Since then we have tried rebooting both nodes alternatively, refreshed , rescaned disks but everything has failed to bring back the resource online. We have again followed all the steps from the start but same result. Can anybody suggest forward path?2.2KViews0likes4Comments