Cluster Server Agents for Veritas™ Volume Replicator Configuration
Contents
1. The info entry point displays information about the replication status of an RDS By default the info interval is set to zero To change the default info interval use the following command hatype modify resourcetype name InfoInterval interval For example to set the info interval to 60 seconds for the RVG resource type enter hatype modify RVG InfoInterval 60 The info interval indicates how frequently VCS executes the info entry point to update the replication status In the above example the info interval is set to 60 so VCS updates the replication status every 60 seconds To display the output of the info entry point use the following command hares value resource name ResourcelInfo The output of the info entry point is also logged in the file var VRTSvcs log engine_A log State definitions The RVG agent has the following state definitions ONLINE Indicates that the RVG is in ENABLED ACTIVE state OFFLINE Indicates that the RVG is in DISABLED CLEAN state FAULTED The RVG resource fails if the RVG is not in the ENABLED ACTIVE state 14 Overview of the VCS agents for VVR How the agents for failover applications work Agent attributes Table 1 1 The required attributes for the RVG agent RVG The name of the RVG being monitored Type and dimension string scalar DiskGroup The disk group that this RVG is associated with Type and dimension string scalar StorageDG The name of the bunker disk2. Licensing and registration If your Symantec product requires registration or a license key access our non technical support Web page at the following URL customercare symantec com Customer service Customer Care information is available at the following URL www symantec com customercare Customer Service is available to assist with the following types of issues Questions regarding product licensing or serialization Product registration updates such as address or name changes General product information features language availability local dealers Latest information about product updates and upgrades Information about upgrade assurance and maintenance contracts Information about the Symantec Buying Programs Advice about Symantec s technical support options Nontechnical presales questions Issues that are related to CD ROMs or manuals Documentation feedback Your feedback on product documentation is important to us Send suggestions for improvements and reports on errors or omissions Include the title and document version located on the second page and chapter and section titles of the text on which you are reporting Send feedback to sfha_docs symantec com Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement please contact the maintenance agreement administration team for your region as follows Asia Pacific and Japan customercare_apac symantec com
3. fbsync resync static int static int static str NumThreads 1 OnlineRetryLimit 1 ArgList RvgResourceName RvgResourceName RVG RvgResourceName DiskGroup AutoTakeover AutoResync str RvgResourceName int AutoTakeover 1 int AutoResync 0 temp str VCSResLock 32 Overview of the VCS agents for VVR How the agents for hybrid applications work How the agents for hybrid applications work The agents for hybrid applications include the following m RVG agent m RVGPrimary agent A hybrid configuration is for Replicated Data Clusters RDCs and is a combination of the failover and parallel service groups A hybrid service group behaves like a failover group within a system zone and like a parallel group across system zones It cannot fail over across system zones A switch operation on a hybrid service group is allowed only between systems within the same system zone For more information about the RVG agent and RVGPrimary agent see RVG agent and RVGPrimary agent These sections give information about the entry points state definitions and attributes for the RVG agent and the RVGPrimary agent In addition the following attribute must be set for the RVG agent and the RVGPrimary agent while configuring RDCs Table 1 9 Attribute for RDCs SystemZones integer association Indicates failover zone An RDC uses VVR as opposed to shared storage to provide access to data at the Secondary An RDC exists wi
4. CVM groups are configured as parallel groups 38 Configuring the agents for high availability Example configuration for a parallel application The service groups Logowner and Oracle are dependent on the service group RVGShared The RVGShared manages the RVG in a shared environment therefore it is dependent on the cvm service group Figure 2 2 RVGShared RVGLogowner and RVGSharedPri agents Service Groups and Resource Dependencies Oracle service parallel Logowner service failover rvg_logowner RVGLogowner logowner_ip ora_vwvr_shpri RVGSharedPri online local firm dependencies racdata_rvg RVGShared group parallel cvm_vxconfigd CMVconfigd Configuring the agents for high availability 39 Example Setting up VVR in a VCS environment Example Setting up VVR in a VCS environment Configuring VVR with VCS requires the completion of several tasks each of which must be performed in the following order m Setting up the VVR configuration m Verifying the VVR replication state m Configuring the agents for failover applications m Configuring the agents for parallel applications Before setting up the VVR configuration verify whether all the nodes in the cluster that have VVR installed use the same port number for replication To verify and change the port numbers use the vrport command If the port number is the same on all nodes add the VVR agents to the VCS configuration For instruct
5. Hr_Mount01 MountPoint hr mount01 BlockDevice dev vx dsk Hr_Dg hr_dv01 FSType vxfs FsckOpt n MountOpt rw 7 Add the Mount resource Hr_Mount02 to mount the volume hr_dv02 in the RVG resource Hr_Rvg hares hares hares hares hares SS SF HE hares add Hr Mount02 Mount ORAGrp modify modify modify modify modify Hr Mount02 Hr Mount02 Hr Mount02 Hr Mount02 Hr Mount02 MountPoint hr_mount02 BlockDevice dev vx dsk Hr_ Dg hr_dv02 FSType vxfs FsckOpt n MountOpt rw 8 Add the Mount resource Hr Mount03 to mount the volume set hr_vset01 in the RVG resource Hr_Rvg hares hares hares hares hares Sb Sb SFOS HE hares add Hr Mount03 Mount ORAGrp modify modify modify modify modify Hr Mount03 Hr Mount03 Hr Mount03 Hr Mount03 Hr Mount03 MountPoint hr_mount03 BlockDevice dev vx dsk Hr Dg hr_vset0l FSType vxfs FsckOpt n MountOpt rw Configuring the agents for high availability 47 Example Setting up VVR in a VCS environment 9 Add the Oracle resource Hr Oracle hares add Hr Oracle Oracle ORAGrp hares modify Hr Oracle Sid hrl hares modify Hr Oracle Owner oracle hares modify Hr Oracle Home hr mount01 OraHomel hares modify Hr Oracle Pfile inithrl ora hares modify Hr Oracle User dbtest hares modify Hr Oracle Pword dbtest hares modify Hr Oracle Table oratest hares modify Hr Oracle MonScript bin Oracle SqlTest pl hares modify Hr Oracl
6. definitions The RVGLogowner resource type definition follows type RVGLogowner static int NumThreads 1 RVG static int OnlineRetryLimit RVG DiskGroup StorageRVG static str ArgList DiskGroup 5 str str str str StorageDG str StorageHostIds Overview of the VCS agents for VVR 29 How the agents for parallel applications work RVGSharedPri agent Attempts to migrate or takeover a Secondary to a Primary when a parallel service group fails over The RVGSharedPri agent enables migration and takeover of a VVR replicated data set in parallel groups in a VCS environment Bringing a resource of type RVGSharedPri online causes the RVG on the local host to become a primary if it is not already The agent is useful when hosts in both the primary and secondary side are clustered using a VCS global cluster to completely automate the availability of writable replicated disks to an application managed by VCS The RVGSharedPri agent includes the following key features m Removes manual steps of migrating a VVR primary and secondary roles when failing over applications across a wide area m Minimizes the need for resynchronizing replicated volumes by attempting a migration before attempting a hard takeover m Waits for the two sides of a replicated data set to become completely synchronized before migrating roles m Supports an automatic fast failback resynchronization of a downed primary if it later returns after a
7. Europe Middle East and Africa semea symantec com North America and Latin America supportsolutions symantec com Additional enterprise services Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge expertise and global insight which enable you to manage your business risks proactively Enterprise services that are available include the following Symantec Early Warning Solutions These solutions provide early warning of cyber attacks comprehensive threat analysis and countermeasures to prevent attacks before they occur Managed Security Services These services remove the burden of managing and monitoring security devices Consulting Services Educational Services and events ensuring rapid response to real threats Symantec Consulting Services provide on site technical expertise from Symantec and its trusted partners Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment design implementation monitoring and management capabilities Each is focused on establishing and maintaining the integrity and availability of your IT resources Educational Services provide a full array of technical training security education security certification and awareness communication programs To access more information about Enterprise services please visit our Web site at the following URL www s
8. If the original Primary is down it attempts a takeover If the RVG is a Primary it performs no actions and goes online Offline Performs no actions Monitor Performs no actions The RVG agents monitors the actual RVG Clean Performs no actions State definitions The RVGPrimary agent has the following state definitions ONLLINE Indicates that the role of the RVG is Primary Overview of the VCS agents for VVR 17 How the agents for failover applications work FAULTED The RVG agents monitors the actual RVG Accidental migration of a VVR Primary outside of VCS causes other resources to fault immediately such as Mount No special monitoring by this agent is necessary Agent attributes Table 1 2 The required attributes for the RVGPrimary agent RvgResourceName The name of the RVG resource type that this agent promotes The name RVG resource type which has been configured using the RVG agent Type and dimension string scalar AutoTakeover A flag to indicate whether the agent should perform a takeover on online if the original Primary is down Type and dimension integer scalar AutoResync A flag to indicate whether the agent should attempt to automatically perform a fast failback resynchronization of the original Primary after a takeover and after the original Primary returns Type and dimension integer scalar Resource type definition The RVGPrimary resource type definition follows type RVGPrimary static ke
9. Network used for replication Shared disks VCS private network 34 Overview of the VCS agents for VVR Example VVR configuration in a VCS environment Example VVR configuration in a VCS environment In the following example two clusters are located at separate sites VVR replicates data between the sites using a WAN The first cluster is located in Seattle and is named Seattle The cluster Seattle consists of two nodes seattle1 and seattle2 The second cluster is located in London and is named London The cluster London also consists of two nodes london and london2 The nodes located in the cluster Seattle contain the Primary RVG The nodes located in the cluster London contain the Secondary RVG Note that the following illustration shows the names of the VVR components used by the RVG agent Figure 1 9 Example VVR configuration in a VCS environment Seattle London Primary RVG hr_rvg Secondary RVG hr_rvg hr_dv01 a hr_dvO1 hr_dv02 hr_dv02 D hr_srl hr_srl 5 gt E rlk_london_hr_rvg p rlk_seattle_hrrvg q Chapter Configuring the agents for high availability This chapter includes the following topics m Requirements for configuring VVR in a VCS environment m Example configuration for a failover application m Example configuration for a parallel application m Example Setting up VVR in a
10. S DOCUMENTATION THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12 212 and subject to restricted rights as defined in FAR Section 52 227 19 Commercial Computer Software Restricted Rights and DFARS 227 7202 Rights in Commercial Computer Software or Commercial Computer Software Documentation as applicable and any successor regulations Any use modification reproduction release performance display or disclosure of the Licensed Software and Documentation by the U S Government shall be solely in accordance with the terms of this Agreement Symantec Corporation 350 Ellis Street Mountain View CA 94043 http www symantec com Technical Support Symantec Technical Support maintains support centers globally Technical Support s primary role is to respond to specific queries about product features and functionality The Technical Support group also creates content for our online Knowledge Base The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion For example the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates Symantec s maintenance offerings include the following m Arange of support options that give you th
11. S agents for a bunker over IP is the same as for any other Secondary To set up a bunker configuration 1 The Primary and Secondary configurations are the same as for any other RDS using VCS agents See Example Setting up VVR in a VCS environment on page 39 2 Add the bunker to the RDS with the vradmin addbunker command For a detailed procedure see the Veritas Volume Replicator Administrator s Guide 3 Configure the VCS agent on the bunker in the same way as the configuration for any other Secondary There is no special configuration that needs to be done for a bunker over IP Administering the service groups This section explains how to administer a VCS service group for cluster Seattle from the command line Note that you can also use the VCS Java and Web consoles to administer service groups To administer a VCS service group 1 Start the VCS engine on seattle1 hastart 2 Verify that all the service groups that contain RVG resource type are brought online hagrp display 56 Configuring the agents for high availability Administering the service groups 3 Take the service group offline and verify that all resources are stopped hagrp offline hr_grp sys seattlel hagrp display 4 Bring the service group online again and verify that all resources are available hagrp online hr _ grp sys seattlel hagrp display 5 Start the VCS engine on seattle2 hastart 6 Switch the VVR service group to s
12. VCS environment m Configuring the agents for a bunker replication configuration m Administering the service groups Requirements for configuring VVR in a VCS environment The requirements for configuring VVR in a VCS environment are as follows m Follow the best practices for setting up replication with VVR For information about setting up replication refer to the Veritas Volume Replicator Administrator s Guide m Fach node that is part of a particular VCS service group involved in replication must use the same port number for replication You may need to change this number on some nodes before configuring VVR m Ifanode has more than one network interface card on the same physical network being used for replication each network interface card must have a different MAC address This is true for all the nodes at the Primary and Secondary sites 36 Configuring the agents for high availability Requirements for configuring VVR in a VCS environment This requirement is specific to the RVG Agent VCS requires the noautoimport attribute of the disk group to be set Refer to the Veritas Cluster Server Bundled Agents Reference Guide for more information about setting the noautoimport attribute Best practices for setting up the agents The following list gives the best practices for setting up the agents Only one DiskGroup and one RVG resource must be present in a service group If a disk group is configured as a DiskGroup resource t
13. Veritas Cluster Server Agents for Veritas Volume Replicator Configuration Guide Solaris 5 1 5 symantec Veritas Cluster Server Agents for Veritas Volume Replicator Configuration Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement Product version 5 1 Document version 5 1 0 Legal Notice Copyright 2009 Symantec Corporation All rights reserved Symantec the Symantec Logo Veritas Veritas Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U S and other countries Other names may be trademarks of their respective owners The product described in this document is distributed under licenses restricting its use copying distribution and decompilation reverse engineering No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors if any THE DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE OR USE OF THI
14. a parallel group Refer to the Veritas Cluster Server Administrator s Guide for more information on dependencies Figure 1 6 Sample service group for an RVGShared resource racdata_rvg RVGShared racdata_voldg CVMVolIDg RVGShared parallel service group Note Do not add any volumes that are part of the RVG in the CVMVolume attribute of the CVMVolDg resource The volumes in the RVG are managed by the RVGShared resource Agent functions The RVGShared agent has the following agent functions Online Verifies whether the RVG is started If the RVG is not started recovers and starts the RVG Offline No action Monitor Displays the state as ONLINE if the RVG is started Displays the state as OFFLINE if the RVG is not started Clean No action Overview of the VCS agents for VVR 25 How the agents for parallel applications work Info Gives the information about the replication status for the Replicated Data Set RDS The info entry point displays information about the replication status of an RDS By default the info interval is set to zero To change the default info interval use the following command hatype modify resourcetype name InfoInterval interval For example to set the info interval to 60 seconds for the RVG resource type enter hatype modify RVG InfolInterval 60 The info interval indicates how frequently VCS executes the info entry point to update the replication status In the above
15. agents ccceeceeceeeeeeeeenes 36 Example configuration for a failover application cccceeeeeeee ee 37 Example configuration for a parallel application cccceeeeeeees 37 Example Setting up VVR in a VCS environment c2ceeeeee ees 39 Setting up the VVR configuration cccccceecseeeeeneeeeeneeeeenes 39 Verifying the VVR replication state cccceccecceeeeeeeeeeeeeeeees 42 Configuring the agents for failover applications 0 006 42 Configuring the agents for parallel applications 00c00s 49 Configuring the agents for a bunker replication configuration 52 VCS configuration for a bunker using the STORAGE PrOtOCON oneei rr Oe nT a 52 VCS configuration for a bunker using IP cccceeceeeeeeeeee ees 55 Administering the service groups cceceececeeceeeeceeeeeeeeeeeeeeeeeeens 55 8 Contents Chapter Overview of the VCS agents for VVR This chapter includes the following topics Introducing the VCS agents for VVR How the agents for failover applications work How the agents for parallel applications work How the agents for hybrid applications work Overview of how to configure VVR in a VCS environment Generic VVR setup in a VCS environment Example VVR configuration in a VCS environment Introducing the VCS agents for VVR VCS provides agents that manage applications an
16. aining an RVGSnapshot resource Type and dimension string scalar Resource type definitions The resource type definition for the RVGSnapshot agent follows type RVGSnapshot static keylist RegList Prefix static int NumThreads 1 static str ArgList RvgResourceName CacheObj Prefix DestroyOnOffline str RvgResourceName str CacheObj str Prefix boolean DestroyOnOffline 1 temp str FDFile How the agents for parallel applications work The agents for parallel applications include the following m RVGShared agent m RVGLogowner agent m RVGSharedPri agent RVGShared agent Monitors the RVG in a shared environment This is a parallel resource The RVGShared agent enables you to configure parallel applications to use an RVG in acluster The RVGShared agent monitors the RVG in a shared disk group environment The RVGShared agent must be configured as a parallel group in VCS Typically the RVGShared resource is online or offline at the same time on all the nodes in the VCS cluster An example configuration file for this agent that can be used as a guide when creating your configuration is located at etc VRTSvcs conf sample_vvr RVGLogowner 24 Overview of the VCS agents for VVR How the agents for parallel applications work Resource dependencies The RVGShared resource represents the RVG of the RDS The RVGShared resource is dependent on the CVMVolDg resource The RVGShared resource must be configured in
17. attle site mkdir hr_mount01 mkdir hr_mount02 mkdir hr_mount03 4 On seattle1 create file systems on the volumes hr_dv01 and hr_dv02 and on the volume set hr _vset01 Verifying the VVR replication state Test the replication state between seattlel and london to verify that VVR is configured correctly To verify the replication state 1 Type the following command on each node vxprint g hrdg hr_rvg 2 Inthe output verify the following m State of the RVG is ENABLED ACTIVE m State of the RLINK is connEctT ACTIVE Configuring the agents for failover applications This section explains how to configure the VVR agents for failover applications See Configuring the agents for parallel applications on page 49 You can configure the RVG agent and RVGPrimary agent when VCS is stopped or when VCS is running Sample configuration files main cf seattle and main cf london are located in the etc VRTSvcs conf sample_vvr RVG and Configuring the agents for high availability 43 Example Setting up VVR in a VCS environment etc VRTSvcs conf sample_vvr RVGPrimary directories respectively and can be used for reference You can add the RVG resource to your existing VCS configuration using any one of the following procedures m Configuring the agents when VCS is running m Configuring the agents when VCS is stopped Configuring the agents when VCS is running The example in this section explains how to configure
18. ccess to the RVG and takes the RVG offline This is a failover resource The RVG agent enables replication between clusters It manages the Primary VVR node in one cluster and the Secondary VVR node in another cluster Each node can be failed over in its respective cluster In this way replication is made highly available The RVG works with the RVGPrimary agent to provide failover of the Primary VVR node to the Secondary VVR node If a disaster occurs on the Primary VVR node and all the nodes in the Primary cluster are unavailable the RVG agent does not fail over the Primary role from the Primary VVR node to the Secondary VVR node Using a VCS global cluster enables you to fail over the Primary role from a Primary VVR node to a Secondary VVR node The RVG agent includes the following key features m Removes potential single points of failure by enabling Primary and Secondary VVR nodes to be clustered m Enables you to bring a service group online to start VCS managed applications that use VVR m Continues replication after a node in a cluster fails without losing updates m Ensures that VVR can be added to any VCS cluster by including the RVG resource type definitions An example configuration file for this agent that can be used as a guide when creating your configuration is located at 12 Overview of the VCS agents for VVR How the agents for failover applications work etc VRTSvcs conf sample_vvr RVG Note This release do
19. condary similarly would include the StorageRVG StorageDG and StorageHostIds attributes group AppsG ClusterList cluster_london 0 SystemList seattle 0 london 1 Authority 1 AutoStartList seattle ClusterFailOverPolicy Manual RVG RVG 1 RVG vcesrvg DiskGroup pdg Primary true StorageRVG brvg StorageDG bdg StorageHostIds portland Sample configuration file parallel application The following sample file shows the configuration for the VCS agent on the Primary The RVGLogowner agent includes attributes for a STORAGE bunker to enable the bunker diskgroup to failover together with the logowner In this example the disk group on the Primary is a shared disk group If the Secondary for the RDS has a bunker associated to it the RVGLogowner resource on the Secondary similarly would include the StorageRVG StorageDG and StorageHostIds attributes group RVGLogownerGrp SystemList seattle 0 london 1 AutoStartList seattle london IP vvr_ip Device bge0 Address 192 168 3 13 NIC vvr_nic Device bge0 RVGLogowner vvr_rvglogowner Configuring the agents for high availability 55 Administering the service groups RVG rvg DiskGroup vvrdg StorageRVG brvg StorageDG bdg StorageHostIds portland requires group RVGSharedGrp online local firm vvr_ip requires vvr_nic VCS configuration for a bunker using IP The configuration for the VC
20. d resources in a cluster The different types of agents follow VCS comes packaged bundled with a set of agents that enable VCS to provide high availability These include agents for mount points IP addresses file systems VVR and virtual environments These agents are immediately available to you after install VCS For more information about VCS bundled agents refer to the following guides m Veritas Cluster Server Bundled Agents Reference Guide m Veritas Cluster Server Agents for Veritas Volume Replicator Configuration Guide 10 Overview of the VCS agents for VVR Introducing the VCS agents for VVR m VCS also provides a set of agents that enable high availability for key enterprise applications and third party products which includes the following m Databases m Replication solutions m Middleware solutions m Enterprise applications These agents are available in the Agent Pack which is updated quarterly For more information about VCS agents for enterprise applications refer to the individual agent s guide the Agent Pack or contact Symantec consulting services m Symantec consulting services can create custom agents for applications that the current set of VCS agents do not support You can also develop custom agents for your environment Creating custom agents requires knowledge of VCS scripting skills and basic programming logic For more information about creating VCS agents refer to the Veritas Cluster Server Ag
21. e StartUpOpt STARTUP hares modify Hr Oracle ShutDownOpt IMMEDIATE hares modify Hr Oracle AutoEndBkup 1 10 Add the Oracle listener resource LISTENER hares add LISTENER Netlsnr ORAGrp hares modify LISTENER Owner oracle hares modify LISTENER Home hr_mount01 OraHomel hares modify LISTENER Listener LISTENER hares modify LISTENER EnvFile oracle profile hares modify LISTENER MonScript bin Netlsnr LsnrTest pl Se Sb SF OSE HE 11 Add the RVGPrimary resource Hr RvgPri hares add Hr RvgPri RVGPrimary ORAGrp hares modify Hr RvgPri RvgResourceName Hr Rvg 12 Specify resource dependencies for the resources you added in the previous steps hares link LISTENER Hr_ Oracle hares link LISTENER oraip hares link Hr Oracle Hr_Mount01 hares link Hr Oracle Hr Mount02 hares link Hr Mount01 rvg pri hares link Hr Mount02 rvg pri hares link Hr Mount03 rvg pri hares link oraip oranic 48 Configuring the agents for high availability Example Setting up VVR in a VCS environment 13 14 15 16 17 The application service group and the replication service group must both exist before doing this step If you have not yet created the replication service group do so now See Configuring the agents when VCS is running on page 43 After you have created the application service group and the replication service group specify an online local hard group dep
22. e flexibility to select the right amount of service for any size organization m Telephone and Web based support that provides rapid response and up to the minute information m Upgrade assurance that delivers automatic software upgrade protection m Global support that is available 24 hours a day 7 days a week m Advanced features including Account Management Services For information about Symantec s Maintenance Programs you can visit our Web site at the following URL www symantec com business support index jsp Contacting Technical Support Customers with a current maintenance agreement may access Technical Support information at the following URL www symantec com business support contact_techsupp_static jsp Before contacting Technical Support make sure you have satisfied the system requirements that are listed in your product documentation Also you should be at the computer on which the problem occurred in case it is necessary to replicate the problem When you contact Technical Support please have the following information available m Product release level m Hardware information m Available memory disk space and NIC information m Operating system Version and patch level Network topology Router gateway and IP address information Problem description m Error messages and log files m Troubleshooting that was performed before contacting Symantec m Recent software configuration changes and network changes
23. eattle2 hagrp switch hr _grp to seattle2 7 Verify that all the service groups that contain RVG resource type are brought online on seattle2 hagrp display Repeat step 1 through step 7 for the cluster London If required check the following log files on any system for the status or any errors var VRTSvcs log engine_A log var VRTSvcs log RVG_A log A agents See individual agents See RVG agent best practices for setting up 36 configuring 42 configuring when VCS is stopped 48 list of VVR 9 RVGLogowner See RVGLogowner agent RVGPrimary See RVGPrimary agent RVGShared See RVGShared agent RVGSharedPri See RVGSharedPri agent RVGSnapshot See RVGSnapshot agent setting up best practices 36 AutoResync attribute RVGPrimary agent 31 best practices setting up VVR agents 36 c configuration setting up the VVR 39 configuration files sample RVG agent 43 configuring RVG agent when VCS is started 43 when VCS is stopped 48 configuring VVR in VCS environment overview 32 requirements 35 D dependency graphs RVGLogowner agent 26 RVGPrimary agent 15 RVGShared agent 24 RVGSharedPri agent 29 E examples setting up VVR in a VCS environment 39 F failover group RVGLogowner agent 26 fast failback AutoResync attribute of RVGPrimary 31 fast failback resynchronization RVGPrimary 15 RVGSharedPri 29 files sample configuration RVG agent 43 fire drill RVGSnaphot agent 21 G generic VVR setup in a VCS
24. ed as a global service group For more information about configuring global clusters see the Veritas Cluster Server Administrator s Guide Sample configuration files are located in the etc VRTSvcs conf sample_rac directory and include CVR in the filename These sample files are installed as part of the VRTSdbac package and can be used as a guide when creating your configuration You can configure agents from the command line or from the VCS Java and Web consoles See the Veritas Cluster Server Administrator s Guide for more information To modify the VCS configuration on the Primary cluster 1 Define two new service groups A logowner group that includes the RVGLogowner resource and an RVG group that includes the RVGShared resource replication objects 2 Inthe logowner group define IP and NIC resources used by the RLINKs for the RVG and the RVGLogowner resource for which the RVG and its associated disk group are defined as attributes 3 Inthe RVG service group set up the RVGShared agent to monitor the RVG resource Because it is shared the RVG must be configured to depend on the CVMVolDg resource which defines the shared disk group and its activation mode Define the RVGShared and CVMVolDg resources within a parallel service group so that the service group may be online at the same time on all cluster nodes 4 Addthe RVGSharedPri resource to the existing application service group and define the service group to be a global grou
25. endency between oraGrp and vvRGrp hagrp link ORAGrp VVRGrp online local hard Enable all resources in oRAGrp hagrp enableresources ORAGrp Save and close the VCS configuration haconf dump makero Bring the service groups online if not already online hagrp online VVRGrp sys seattlel hagrp online ORAGrp sys seattlel Verify that the service group ORAGrp is ONLINE on the system seattle1 by issuing the following command hagrp state ORAGrp Configuring the agents when VCS is stopped Perform the following steps to configure the RVG agent using the sample configuration file on the first node in the Primary cluster and Secondary cluster In the example in this guide seattle1 is the first Primary node and london is the first Secondary node Configuring the agents for high availability 49 Example Setting up VVR in a VCS environment To configure the agents when VCS is stopped 1 Loginas root 2 Ensure that all changes to the existing configuration have been saved and that further changes are prevented while you modify main cf If the VCS cluster is currently writeable run the following command haconf dump makero If the VCS cluster is already read only run the following command haconf dump 3 Do not edit the configuration files while VCS is started The following command will stop the had daemon on all systems and leave resources available hastop all force 4 Make a backup copy of
26. ent Developers Guide or contact Symantec consulting services Agents are processes that manage predefined resource types When an agent is started it obtains configuration information from the Veritas Cluster Server VCS It then periodically monitors the resources and updates VCS with the resource status Typically agents do the following m Bring resources online m Take resources offline m Monitor resources and report any state changes to VCS The VCS Agents for VVR monitor and manage Replicated Volume Groups RVGs Each agent includes VCS type declarations and agent executables which represent a resource type The VCS Agents for VVR include Agents for failover applications Review the following m See How the agents for failover applications work on page 11 m See RVG agent on page 11 m See RVGPrimary agent on page 14 m See RVGSnapshot on page 20 Overview of the VCS agents for VVR 11 How the agents for failover applications work Agents for parallel applications Review the following m See How the agents for parallel applications work on page 23 m See RVGShared agent on page 23 m See RVGLogowner agent on page 26 m See RVGSharedPri agent on page 29 How the agents for failover applications work The agents for failover applications include the following m RVG agent m RVGPrimary agent m RVGSnapshot RVG agent Brings the RVG online monitors read and write a
27. environment 33 H hybrid group about 32 L list of VCS agents for VVR 9 logowner virtual IP requirement 26 M migrating RVGPrimary 15 RVGSharedPri 29 Mount resource volume sets 36 58 Index N noautoimport attribute RVG agent requirement 36 0 overview configuring VVR in a VCS environment 32 P parallel group RVGShared agent 23 R RDC about 32 SystemZones attribute of RVG and RVG Primary agents 32 Replicated Data Cluster See RDC replication setting up 35 replication state verifying 42 requirements configuring VVR in VCS environment 35 RVG agent configuring 43 configuring when VCS is started 43 configuring when VCS is stopped 48 described 11 requirement noautoimport 36 sample configuration file 43 SystemZones attribute 32 virtual IP requirement 41 RVGLogowner agent configuring 49 dependency graph 26 described 26 failover group 26 RVGPrimary agent dependency graph 15 described 14 migrating 15 SystemZones attribute 32 takeover 15 RVGShared agent configuring 49 dependency graph 24 RVGShared agent continued described 23 parallel group 23 RVGSharedPri agent configuring 49 dependency graph 29 described 29 migrating 29 takeover 29 RVGSnapshot agent described 20 fire drill 21 S sample configuration files RVG agent 43 to configure agent location 39 setting noautoimport attribute 36 setting up replication 35 setting up the VVR configuration 39 setting up VVR agents be
28. es for configuring bunker failover StorageDG The name of the bunker disk group StorageRVG The name of the bunker RVG StorageHostIds Hostid of the bunker node or if the bunker is clustered a space separated list of the hostids of each node in the bunker cluster The bunker failover attributes described in this section are the only specific attributes that differ for an RDS containing a bunker The rest of the configuration for the VCSAgent is the same as for any other RDS See Example Setting up VVR in a VCS environment on page 39 Sample configuration files for VCS agents in a bunker replication environment The following examples show sample configuration files when the bunker Secondary is connected to the Primary using the STORAGE protocol This example uses the following names m seattle primary cluster node m london bunker node m bdg bunker disk group name m brvg bunker RVG name Sample configuration file failover application The following sample file shows the configuration for the VCS agent on the Primary The RVG agent includes attributes for a STORAGE bunker to enable the bunker diskgroup to failover together with the parent RVG 54 Configuring the agents for high availability Configuring the agents for a bunker replication configuration In this example the disk group on the Primary is not a shared disk group If the Secondary for the RDS has a bunker associated to it the RVG agent on the Se
29. es not support the attributes Primary SRL and RLinks of the RVG agent If you have a configuration from a previous release you must remove these attributes during the upgrade or the configuration will fail Resource dependencies The RVG resource represents the RVG Replicated Volume Group in the RDS Replicated Data Set The RVG resource is dependent on the DiskGroup resource The RVG resource is also dependent on the IP resources that it uses for replication In a VVR environment higher level application resources such as Mount that would typically depend on a Volume resource must depend on the associated RVG resource Refer to the Veritas Cluster Server Administrator s Guide for more information on dependencies Figure 1 1 Sample service group for an RVG resource Agent functions The RVG agent has the following agent functions Online Verifies whether the DiskGroup agent has recovered the RVG If not recovers and starts the data volumes and the Storage Replicator Log SRL recovers the RVG recovers all RLINKs in the RVG and then starts the RVG Offline Stops the RVG Overview of the VCS agents for VVR 13 How the agents for failover applications work Monitor Monitors the state of the RVG using the vxprint command The RVG resource monitors an RVG for local access only It does not monitor replication Clean Stops the RVG Info Gives the information about the replication status for the Replicated Data Set RDS
30. example the info interval is set to 60 so VCS updates the replication status every 60 seconds To display the output of the info entry point use the following command hares value resource name ResourcelInfo The output of the info entry point is also logged in the file var VRTSves log engine_A log State definitions The RVGShared agent has the following state definitions ONLINE Indicates that the RVG is in the ENABLED ACTIVE state OFFLINE Indicates that the RVG is not in the ENABLED ACTIVE state or that the administrator has invoked the offline entry point Agent attributes Table 1 5 The required attributes for the RVGShared agent RVG The name of the RVG being monitored Type and dimension string scalar DiskGroup The shared disk group with which this RVG is associated Type and dimension string scalar 26 Overview of the VCS agents for VVR How the agents for parallel applications work Resource type definitions The RVGShared resource type definition follows type RVGShared static int NumThreads 1 static str ArgList RVG DiskGroup str RVG str DiskGroup RVGLogowner agent Assigns and unassigns a node as the logowner in the CVM cluster this is a failover resource The RVGLogowner agent assigns or unassigns a node as a logowner in the cluster To replicate data VVR requires network connectivity between the Primary and the Secondary In a shared disk group environment only one node that i
31. gents do not support mounting a volume set that is partially associated to an RVG that is if one or more of its component volumes are not associated to the RVG For more information about using volume sets in an RVG refer to the Veritas Volume Replicator Administrator s Guide Configuring the agents for high availability 37 Example configuration for a failover application Example configuration for a failover application In the following example a failover application that uses an RVG is made highly available across two clusters The application service group contains the following resources application Mount NIC IP and RVGPrimary The replication group contains the RVG IP NIC and DiskGroup resources The application group has an online local hard dependency on the replication group Figure 2 1 RVG and RVGPrimary Agents Service Groups and Resource Dependencies Application service group that is online on the Primary online local hard dependency Replication service group that is online at both Primary and Secondary Example configuration for a parallel application In the following example a parallel application that uses an RVG is made highly available across two clusters The Oracle service group is the application group and contains the CFSMount resource The Logowner service group is a failover group which manages the logowner The service group RVGShared manages the RVG used by the application The Oracle and
32. group Type and dimension string scalar StorageRVG The name of the bunker RVG Type and dimension string scalar StorageHostIds A space separated list of the hostids of each node in the bunker cluster Type and dimension string keylist Resource type definitions The RVG agent resource type definition follows type RVG static int NumThreads 1 static str ArgList RVG DiskGroup str RVG str DiskGroup str StorageRVG str StorageDG str StorageHostIds RVGPrimary agent Attempts to migrate or takeover a Secondary to a Primary upon an application failover The RVGPrimary agent enables migration and takeover of a VVR replicated data set in a VCS environment Bringing a resource of type RVGPrimary online causes the RVG on the local host to become a primary The agent is useful when hosts in both the primary and secondary side are clustered in particular a Overview of the VCS agents for VVR 15 How the agents for failover applications work VCS replicated data cluster or a VCS global cluster to completely automate the availability of writable replicated disks to a VCS managed application The RVGPrimary agent includes the following key features m Removes the manual steps of migrating a VVR primary and secondary roles when failing over applications across a wide area m Minimizes the need for resynchronizing replicated volumes by attempting a migration before attempting a hard takeover m Waits for t
33. he two sides of a replicated data set to become completely synchronized before migrating roles m Supports an automatic fast failback resynchronization of a downed primary if it later returns after a takeover Asample configuration file for this agent that can be used as a guide when creating your configuration is located at etc VRTSvcs conf sample_vvr RVGPrimary Resource dependencies You usually use the RVGPrimary agent in conjunction with the RVG agent in two groups with an online local hard group dependency The parent group contains the resources that manage the actual application and file systems and as the RVGPrimary resource The child group contains the resources managing the storage infrastructure which include the RVG and DiskGroup type resources Refer to the Veritas Cluster Server Administrator s Guide for more information on detailed setup of a VVR environment using the RVGPrimary agent 16 Overview of the VCS agents for VVR How the agents for failover applications work Figure 1 2 Sample service group for an RVGPrimary resource Application service group that is online on the Primary online local hard dependency Replication service group that is online at both Primary and Secondary Agent functions The RVGPrimary agent has the following agent functions Online Determines the current role of the RVG If the role is Secondary it attempts a migrate It waits for any outstanding writes from the original Primary
34. hen all the RVGs in this disk group must be configured as RVG resources If a disk group is configured as a CVMVoIDG resource then all the RVGs must be configured as RVGShared resources When configuring failover applications use the RVG RVGPrimary and RVGSnapshot agents When configuring parallel applications use the RVGShared RVGSharedPri and RVGLogowner agents If the configuration has multiple RVGLogowner resources we recommend that you alternate the order of hosts in the AutoStartList attributes for the service groups containing the RVGLogowner resources VCS then brings online the RVGLogowner resources on different nodes in the cluster which facilitates load balancing For example the first service group containing an RVGLogowner resource would appear as AutoStartList seattlel seattle2 whereas the next service group would have AutoStartList seattle2 seattlel and so on Do not configure the RVGShared resource in the cvm group Configure the RVGShared resource in a separate group which contains the RVGShared resource and the CVMVolDg resource If a volume set is fully associated to an RVG that is if all its component volumes are associated to the RVG you can add the volume set to the agent configuration in the same way that a volume is added Specify the volume set in the Mount resource instead of the component volume names See Example Setting up VVR in a VCS environment on page 39 Note The a
35. iguration for a bunker using IP VCS configuration for a bunker using the STORAGE protocol When a bunker is set up using the STORAGE protocol the disk group containing the bunker RVG is imported on the Primary node If the Primary RVG is in a VCS cluster the bunker RVG must remain online on the same node on which the Primary RVG is online In a shared disk group environment the bunker RVG must be online on the logowner node This section describes how to configure the agents to automate the failover of the bunker RVG In a private disk group environment the RVG resource handles the failover process If the node on which the RVG resource is online fails the RVG resource fails over to another node within the cluster The RVG resource ensures that the Configuring the agents for high availability 53 Configuring the agents for a bunker replication configuration bunker RVG also fails over so that the bunker RVG continues to be on the same node with the Primary RVG Inashared disk group environment the RVGLogowner agent handles the failover of the bunker RVG If the logowner fails over the bunker RVG must be deported from the original logowner node and imported on the new logowner node To set up automated failover of the bunker RVG specify the bunker RVG the bunker disk group and the bunker node using the following attributes of the RVG resource in the application service group or the RVGLogowner agent Table 2 1 Attribut
36. initions FAULTED Monitoring of the actual RVG is done by the RVGShared agent accidental migration of a VVR Primary outside of VCS would cause other resources to fault immediately such as Mount so no special monitoring by this agent is necessary Overview of the VCS agents for VVR 31 How the agents for parallel applications work Agent attributes Table 1 8 The required attributes for the RVGSharedPri agent RvgResourceName The name of the RVGShared resource type that this agent will promote that is the name RVG resource type which has been configured using the RVGShared agent The required VVR object names such as the name of the RVG Disk Group RLINKs SRL are discovered by this agent by querying VCS directly Type and dimension string scalar AutoTakeover A flag to indicate whether the agent should perform a takeover on online if the original Primary is down Type and dimension integer scalar Default 1 AutoResync A flag to indicate whether the agent should attempt to automatically perform a fast failback resynchronization of the original Primary after a takeover and after the original Primary returns Type and dimension integer scalar Default 0 VCSResLock This attribute is reserved for internal use by VCS Type and dimension string scalar Resource type definitions The RVGSharedPri resource type definition follows type RVGSharedPri static keylist SupportedActions
37. ions on using the vrport command see the Veritas Volume Replicator Administrator s Guide Setting up the VVR configuration This section provides the steps to set up a sample VVRconfiguration The VVR configuration that is being set up in this example applies to the RVG Agent that is it uses the names that are used in the sample configuration file of the RVG agent The procedure to configure VVR is the same for all the VVR agents Use the sample configuration files located in etc VRTSvcs conf sample_vvr directory to configure the other agents For more information on configuring VVR refer to the Veritas Volume Replicator Administrator s Guide The example uses the names listed in the following table Name of Cluster Seattle Disk group hrdg Primary RVG hr_rvg Primary RLINK to london1 rlk_london_hr_rvg Primary data volume 1 hr_dv01 Primary data volume 2 hr_dv02 Primary volume set hr_vset01 with data volumes hr_dv03 hr_dv04 40 Configuring the agents for high availability Example Setting up VVR in a VCS environment Primary SRL for hr_rvg Cluster IP Name of Cluster London Disk group Secondary RVG Secondary RLINK to seattle Secondary data volume 1 Secondary data volume 2 Secondary volume set with data volumes hr_dv03 hr_dv04 Secondary SRL for hr_rvg Cluster IP hr_srl 10 216 144 160 hrdg hr_rvg rlk_seattle_hr_rvg hr_dv01 hr_dv02 hr_vset01 hr_srl 10 216 144 162 This exam
38. o the agent itself a text based wizard opt VRTSvcs bin fdsetup that prepares the VVR and VCS infrastructure for a fire drill and a script opt VRTSvcs bin fdsched that runs the fire drill and consolidates the results are included with this package Complete details are in the Veritas Cluster Server Administrator s Guide The RVGSnapshot agent includes the following key features m Automates the process of creating a space optimized snapshot on a VVR secondary that can be mounted to simulate a wide area failover without affecting the production application m Includes a wizard to effectively set up and schedule fire drills that are completely managed by VCS Resource dependencies The RVGSnapshot agent depends on these resources Figure 1 5 Sample service group for an RVGSnapshot resource RVGSnapshot Agent functions The RVGSnapshot agent has the following agent functions Online Creates a transactionally consistent snapshot of all volumes in the RDS Offline Destroys the snapshot Monitor No operation failure of the snapshot will be indicated by the failure of the Mount resource of any file systems mounted on it 22 Overview of the VCS agents for VVR How the agents for failover applications work Clean Cleans up any failed snapshot creation or deletion State definitions The RVGSnapshot agent has the following state definitions ONLINE Indicates that a snapshot was created OFFLINE Indicates that a snapshot was dest
39. ogowner agent has the following agent functions Online Assigns the logowner on the node Offline Unassigns the logowner on the node Monitor Returns ONLINE if the node is the logowner and the RVG is in ENABLED ACTIVE State Returns OFFLINE if the node is the logowner and the state is not ENABLED ACTIVE or if the node is not the logowner regardless of the state The RVG for which the logowner is monitored must be configured as the RVGShared resource type Clean Unassigns the logowner on the node State definitions The RVGLogowner agent has the following state definitions ONLINE Indicates that the node is the logowner for the RVG in the cluster OFFLINE Indicates that the node is not the logowner for the RVG in the cluster 28 Overview of the VCS agents for VVR How the agents for parallel applications work Age Table 1 6 nt attributes The required attributes for the RVGLogowner agent RVG The name of the RVG being monitored Type and dimension string scalar DiskGroup The disk group with which this RVG is associated Type and dimension string scalar Table 1 7 The bunker attributes for the RVGLogowner agent StorageDG The name of the bunker disk group Type and dimension string scalar StorageRVG The name of the bunker RVG Type and dimension string scalar StorageHostIds A space separated list of the hostids of each node in the bunker cluster Type and dimension string keylist Resource type
40. or failover applications work Figure 1 3 RVGPrimary three way global clustering support Primary Secondary 1 The three sites are en clustered Secondary 2 Application service group Replication service group The application s service group depends on the replication s service group 20 Overview of the VCS agents for VVR How the agents for failover applications work Figure 1 4 RVGPrimary three way global clustering migration and takeover Primary Secondary 1 previously Primary Primary previously Secondary 1 Secondary 2 now an orphan RVGSnapshot Creates and destroys a transactionally consistent space optimized snapshot of all volumes in a VVR secondary replicated data set The RVGSnapshot agent automates the taking of space optimized snapshots on a secondary RVG since these snapshots can be mounted and written to without affecting the actual replicated data a space optimized snapshot can be an effective tool for scheduling a fire drill to confirm that a wide area failover is possible By combining this agent with VCS Mount agents and VCS agents that manage the application being Overview of the VCS agents for VVR 21 How the agents for failover applications work replicated a special fire drill service group can be created that can be brought online and taken offline at regularly scheduled intervals to confirm the robustness of a disaster recovery environment In addition t
41. oup VVRGrp hares modify Hr Dg DiskGroup hrdg 5 Adda NIC resource vvrnic to the service group vvRGrp and modify the attributes of the resource hares add vvrnic NIC VVRGrp hares modify vvrnic Device qfe3 6 Add the IP resource vvrip to the service group vvRGrp and modify the attributes of the resource hares add vvrip IP VVRGrp hares modify vvrip Device qfe3 hares modify vvrip Address 192 168 40 20 hares modify vvrip NetMask 255 255 248 0 On the Secondary cluster use the appropriate IP for the Address For example hares modify vvrip Address 192 168 40 21 7 Specify resource dependencies for the resources you added in the previous steps hares link Hr Rvg vvrip hares link Hr Rvg Hr Dg hares link vvrip vvrnic Configuring the agents for high availability 45 Example Setting up VVR in a VCS environment 8 Enable all resources in vvRGrp hagrp enableresources VVRGrp 9 Save and close the VCS configuration haconf dump makero Perform the following steps on the system seattle1 in the Primary cluster Seattle and then repeat the steps with minor changes as noted on the system london1 in Secondary cluster London To create the application service group 1 Loginas root 2 Set the VCS configuration mode to read write by issuing the following command haconf makerw 3 Add a service group ORAGrp to the cluster seattle This group will contain all the application specific re
42. owing changes m Edit the CVM group on the secondary cluster Use the CVM group on the primary as your guide m Add the logowner group and the RVG service groups m Add an application service group Use the application service group on the primary cluster as a pattern for the service group on the secondary cluster 52 Configuring the agents for high availability Configuring the agents for a bunker replication configuration m Since the service group is a global group assign it the same name as the group on the primary cluster m Define the ClusterList and ClusterFailOverPolicy cluster attributes m Include the RVGSharedPri resource 6 Save and close the main cf file Verify the syntax of the file etc VRTSvcs conf config main cf hacf verify etc VRTSvcs conf config 8 Start VCS on all systems in both clusters The application group should be online on both systems of the primary cluster The application service group should not be online on the secondary cluster but the CVM RVG logowner and RVG groups should be online Configuring the agents for a bunker replication configuration This section describes how to set up the VCS agents for a bunker replication configuration that is an RDS that includes a bunker site A bunker can be set up using the STORAGE protocol or using IP Refer to one of the following sections to configure the VCS agents m VCS configuration for a bunker using the STORAGE protocol m VCS conf
43. p See the Veritas Cluster Server Administrator s Guide for instructions on how to create global groups Configuring the agents for high availability 51 Example Setting up VVR in a VCS environment 5 Move the CVMVolDg resource from the existing application service group to the newly created RVGShared service group 6 Set the following service group dependencies m The RVG logowner service group has an online local firm dependency on the service group containing the RVG m The RVG service group has an online local firm dependency on the CVM service group m The application service group has an online local firm dependency on the RVG service group To modify the VCS configuration on the Secondary cluster 1 Logon toa node in the secondary cluster as root 2 Ensure that all changes to the existing configuration have been saved and that further changes are prevented while you modify main cf If the VCS cluster is currently writeable run the following command haconf dump makero If the VCS cluster is already read only run the following command haconf dump 3 Ensure VCS is not running while you edit main cf by using the hastop command to stop the VCS engine on all systems and leave the resources available hastop all force 4 Make a backup copy of the main cf file cd etc VRTSvcs conf config cp main cf main orig 5 Use vior another text editor to edit the main cf file making the foll
44. ple assumes that each of the hosts seattle1 and london has a disk group named hrdg with enough free space to create the VVR objects mentioned in the example Set up the VVR configuration on seattle1 and london to include the objects used in the sample configuration files main cf seattle and main cf london located in the etc VRTSvcs conf sample_vvr RVG directory See Example VVR configuration in a VCS environment on page 34 To set up the VVR configuration 1 Onlondon1 m Create the Secondary data volumes vxassist g hrdg make hr dv01 100M layout mirror logtype dcm mirror 2 vxassist g hrdg make hr dv02 100M layout mirror logtype dcm mirror 2 m Create the data volumes for the volume set on the Secondary and create the volume set vxassist g hrdg make hr _dv03 100M layout mirror logtype dcm mirror 2 vxassist g hrdg make hr dv04 100M layout mirror logtype dcm mirror 2 Configuring the agents for high availability 41 Example Setting up VVR in a VCS environment vxmake g hrdg vset hr vset01 appvols hr_ dv03 hr_dv04 m Create the Secondary SRL vxassist g hrdg make hr _ srl 200M mirror 2 On seattle1 m Create the Primary data volumes vxassist g hrdg make hr dv01 100M layout mirror logtype dcm mirror 2 vxassist g hrdg make hr _dv02 100M layout mirror logtype dcm mirror 2 m Create the data volumes for the volume set on the Primary and create the volume set vxas
45. royed FAULTED The RVGSnapshot resource faults on timeout if a snapshot creation did not succeed during an online Agent attributes Table 1 3 The required attributes for the RVGSnapshot agent RvgResourceName The name of the VCS RVG type resource that manages the RVG that will be snapshot by this agent Type and dimension string scalar CacheObj Name of the cache object that is required for a space optimized snapshot the fdsetup wizard will create one if it does not exist Type and dimension string scalar Prefix Token put before the name of the actual volume when creating the snapshotted volumes Type and dimension string scalar Table 1 4 The optional attributes for the RVGSnapshot agent DestroyOnOffline A flag to indicate whether to destroy the snapshot upon taking the resources offline For a fire drill the snapshot should be deleted to reduce any performance impact of leaving the snapshot for a long period of time however if there is interest in keeping the data then this value should be set to 0 The default is 1 true Type and dimension integer scalar Default 1 Overview of the VCS agents for VVR 23 How the agents for parallel applications work Table 1 4 The optional attributes for the RVGSnapshot agent continued FDFile The fire drill schedule updates this attribute with the system name and the path to a file containing the output of the last complete fire drill for the group cont
46. s the logowner can replicate data to the Secondary For replication to be highly available the logowner must be highly available To make the logowner highly available the RVGLogowner resource must be configured as aresource in a failover group Also a virtual IP must be set up on the logowner to enable replication and failover of the logowner from one node to another in a cluster The virtual IP must be configured as an IP resource For more information about the logowner see the Veritas Volume Replicator Administrator s Guide An example configuration file for this agent that can be used as a guide when creating your configuration is located at etc VRTSvcs conf sample_vvr RVGLogowner Resource dependencies The RVGLogowner resource represents the logowner for RVG in the cluster The RVGLogowner resource is dependent on the IP resource that it uses for replication The RVGLogowner resource must be configured in a failover group The RVGLogowner group is used in conjunction with the RVGSharedPri and RVGShared agents in separate groups with the appropriate service group dependencies For more information on dependencies refer to the Veritas Cluster Server Administrator s Guide Overview of the VCS agents for VVR 27 How the agents for parallel applications work Figure 1 7 Sample service group for an RVGLogowner resource rvg_logowner RVGLogowner logowner_ip Logowner failover service group Agent functions The RVGL
47. sist g hrdg make hr _dv03 100M layout mirror logtype dcm mirror 2 vxassist g hrdg make hr _dv04 100M layout mirror logtype dcm mirror 2 vxmake g hrdg vset hr vset01 appvols hr_dv03 hr_dv04 m Create the Primary SRL vxassist g hrdg make hr srl 200M mirror 2 m Create the Primary RVG vradmin g hrdg createpri hr rvg hr_dv01 hr_dv02 hr vset0l1 hr srl m Determine the virtual IP address to be used for replication and then verify that the device interface for this IP is plumbed If the device interface for this IP is not plumbed then plumb the device Get the IP up using the OS specific command This IP address that is to be used for replication must be configured as the IP resource for this RVG service group m Create the Secondary RVG vradmin g hrdg addsec hr _rvg 100 216 144 160 10 216 144 162 prlink rlk_london_hr rvg srlink rlk_seattle_hr_rvg 42 Configuring the agents for high availability Example Setting up VVR in a VCS environment Note The RLINKs must point to the virtual IP address for failovers to succeed The virtual IP address 10 216 144 160 must be able to ping virtual IP address 10 216 144 162 and vice versa IPv6 addresses are supported m Start replication vradmin g hrdg f startrep hr_rvg 3 Create the following directories on seattle1 and seattle2 These directories will be used as mount points for volumes hr _dv01 and hr_dv02 and the volume set hr_vset0O1 on the se
48. sources Populate the attributes SystemList AutoStartList and ClusterList of the service group hagrp add ORAGrp hagrp modify ORAGrp SystemList seattlel 0 seattle2 1 hagrp modify ORAGrp AutoStartList seattlel seattle2 hagrp modify ORAGrp ClusterList Seattle 0 London 1 Se SE SESE On the Secondary replace seattle1 and seattle2 with london1 and london2 as follows hagrp add ORAGrp hagrp modify ORAGrp SystemList londonl 0 london2 1 hagrp modify ORAGrp AutoStartList londonl london2 hagrp modify ORAGrp ClusterList Seattle 0 London 1 4 Adda NIC resource oranic to the service group oRAGrp and modify the attributes of the resource hares add oranic NIC ORAGrp hares modify oranic Device hme0 46 Configuring the agents for high availability Example Setting up VVR in a VCS environment 5 Add an IP resource oraip to the service group oRAGrp and modify the attributes of the resource hares hares modify hares modify hares modify On the Secondary appropriately add oraip IP ORAGrp oraip Device hme0 oraip Address 192 168 40 1 oraip NetMask 255 255 248 0 modify the Address attribute for the IP resource 6 Add the Mount resource Hr Mount01 to mount the volume hr _dv01 in the RVG resource Hr_Rvg hares hares hares hares hares Sb SF H E HE hares add Hr_Mount01 Mount ORAGrp modify modify modify modify modify Hr_Mount01 Hr_Mount01 Hr_Mount01 Hr_Mount01
49. st practices 36 snapshots using RVGSnapshot agent for 20 state of replication 42 SystemZones attribute of RVG and RVG Primary agents 32 T takeover RVGPrimary 15 RVGSharedPri 29 Vv VCS configuring RVG agent with 43 48 VCS agents for VVR list 9 VCS environment configuring VVR in 32 example setting up VVR 39 generic VVR setup 33 requirements for configuring VVR 35 setting up VVR virtual IP requirement 41 verifying VVR replication state 42 virtual IP requirement 41 RVGLogowner agent requirement 26 volume sets using agents with 36 VVR agents configuring 42 list of 9 VVR configuration setting up 39 VVR in a VCS environment configuring 32 requirements 35 set up example 39 virtual IP requirement for setting up 41 VVR setup in a VCS environment 33 Index 59
50. takeover Sample configuration files are located in the etc VRTSvcs conf sample_rac directory and include CVR in the filename These sample files are installed as part of the VRTSdbac package and can be used as a guide when creating your configuration Resource dependencies The RVGSharedPri agent is used in conjunction with the RVGShared and RVGLogowner agents in separate groups with the appropriate service group dependencies The RVGSharedPri agent must be configured in a parallel service group The application service group contains the resources managing the actual application and file systems as well as the RVGSharedPri agent 30 Overview of the VCS agents for VVR How the agents for parallel applications work Figure 1 8 Sample service group for an RVGSharedPri resource ora_db1 ora_mnt ora_vvr_shpri RVGSharedPri Application parallel service group Agent functions The RVGSharedPri agent has the following agent functions Online Offline Monitor Clean Determines the current role of the RVG if Secondary attempt a migrate waiting for any outstanding writes from the original Primary if the original Primary is down attempt a takeover if the RVG is a Primary perform no actions and go online Performs no actions Performs no actions monitoring of the actual RVG is done by the RVGShared agent Performs no actions State definitions The RVGSharedPri agent has the following state def
51. the RVG and RVGPrimary agents when VCS is running See Example configuration for a failover application on page 37 Note Use this example as a reference when creating or changing your resources and attributes To add the agent resources to your existing VCS configuration when VCS is running perform the following procedures m Create the replication service group m Create the application service group Perform the following steps on the system seattle1 in the Primary cluster Seattle and then repeat the steps with minor changes as noted on the system london1 in Secondary cluster London To create the replication service group 1 Loginas root 2 Set the VCS configuration mode to read write by issuing the following command haconf makerw 44 Configuring the agents for high availability Example Setting up VVR in a VCS environment 3 Add the replication service group vvRGrp to the cluster This group will contain all the storage and replication resources Modify the attributes SystemList andAutoStartList of the service group to populate systemList and AutoStartList hagrp add VVRGrp hagrp modify VVRGrp SystemList seattlel 0 seattle2 1 hagrp modify VVRGrp AutoStartList seattlel seattle2 On the Secondary cluster replace seattle1 and seattle2 with london1 and london2 4 Add the DiskGroup resource Hr_Dg to the service group vvRGrp and modify the attributes of the resource hares add Hr Dg DiskGr
52. the main cf file cd etc VRTSvcs conf config cp main cf main cf orig 5 Edit the main cf files for the Primary and Secondary clusters The files main cf seattle and main cf london located in the etc VRTSvcs conf sample_vvr RVGPrimary directory can be used for reference for the primary cluster and the secondary cluster respectively Save and close the file Verify the syntax of the file etc VRTSvcs conf config main cf hacf verify etc VRTSvcs conf config 8 Start VCS on all systems in both clusters 9 Administer the service groups See Administering the service groups on page 55 Configuring the agents for parallel applications Use the RVGShared RVGSharedPri and the RVGLogowner agents to manage and monitor RVGs used by parallel applications in a shared environment 50 Configuring the agents for high availability Example Setting up VVR in a VCS environment Note Determine the node that is performing the most writes by running the vxstat command on each node for a suitable period of time after you set up replication specify this node as the logowner The prerequisites for configuring the agents are as follows m You must have replication set up between the Primary and Secondary sites For more information about replicating in a shared environment see the Veritas Volume Replicator Administrator s Guide m The sites must be configured in a global cluster and the application service must be configur
53. thin a single VCS cluster The application group which is configured as a failover group can be online only on the Primary host In the case of the failure of the Primary site the Secondary is promoted to a Primary and the application is brought online on the new Primary host An RDC configuration is appropriate in configurations lacking shared storage or SAN interconnection between the Primary site and Secondary site but where dual dedicated LLT links are available between the Primary site and the Secondary site For more information about RDCs refer to the Veritas Cluster Server Administrator s Guide Overview of how to configure VVR in a VCS environment This section gives an overview of how to configure VVR in a VCS environment for high availability of the application that is involved in replication Overview of the VCS agents for VVR 33 Generic VVR setup in a VCS environment To configure VVR in a VCS environment you must perform the following tasks in the order in which they are listed m Setting up a VVR configuration which involves creating a Replicated Data Set RDS m Creating service groups for the VVR agents and adding the resource and group dependencies appropriately Generic VVR setup in a VCS environment The following illustration shows how VVR replicates in a VCS environment given a two cluster environment Cluster A VCS private network Shared disks Network used for replication Cluster B
54. ylist SupportedActions fbsync static int NumThreads 1 static int OnlineRetryLimit 1 static str ArgList RvgResourceName AutoTakeover AutoResync str RvgResourceName int AutoTakeover 1 int AutoResync 0 Using the RVGPrimary agent for migration and takeover The RVGPrimary agent can now handle the migration and takeover when you have multiple secondary sites that you have configured for VCS disaster recovery and global failover n way GCO 18 Overview of the VCS agents for VVR How the agents for failover applications work After the first failover succeeds the rlinks from remaining secondaries to the new primary need to be attached Attach these rlinks before trying subsequent failovers and to be ready for the next failovers to succeed Consider an example of a disaster recovery DR setup where two DR sites are configured as follows m Primary RVG PRI_RVG PRI_RVG has the following rlinks m rik SEC RVG1 m rlik_SEC RVG2 m Secondary RVG SEC_RVG1 SEC_RVG1 has the following rlinks m rik PRI RVG m rik SEC_RVG2 m Secondary RVG SEC_RVG2 SEC_RVG2 has the following rlinks m rik PRI RVG m rik SEC RVG1 When the Primary site is failed over to secondary site SEC_RVG1 becomes new primary Use the vradmin or vxrlink commands to attach the following rlinks m rlk SEC RVG2 that is associated with SEC_RVGI1 m rlk PRI RVG that is associated with SEC_RVG2 Overview of the VCS agents for VVR 19 How the agents f
55. ymantec com Select your country or language from the site index Contents Technical Support sree dick ganas anne dopa viedeaeadcdecs famedbsenanervas v Soares aun db nieead nanan lvebacdous 4 Chapter 1 Overview of the VCS agents for VVR ou cece 9 Introducing the VCS agents for VVR ccccscceceeeceeceeceeeeceeeeeseenenes 9 How the agents for failover applications Work cccseceeeeeeeeenes 11 RVG ag ent oaoa SERN E EE E NER 11 RVGPrimary aget sscscieecedissasieowaesavicasdaasesnsneavnomenesseteedseteainays 14 RVGSnapshot cc cece ec ec ec ee eee e ec ee ec ececececeseeeeeeneneneenenenenenens 20 How the agents for parallel applications work cccseceeeeeeeenes 23 RVGShared agent cccccececeececeeceeeeceeeeeeeeeeeeeeeeeeeeeeeneaeees 23 RV GLOgOWner agent oikeeseen oman en ina E OnE a sai 26 RVGSharedPri agent cccececcec eee ec eee eeeen sense sense eceeeeeeeneaeees 29 How the agents for hybrid applications Work ccecceeeeeeeeeeeeeee 32 Overview of how to configure VVR in a VCS environment 4 32 Generic VVR setup in a VCS environment ccccececeeeeeeeeeeeeenees 33 Example VVR configuration in a VCS environment c0eceeeeeee 34 Chapter 2 Configuring the agents for high availability 35 Requirements for configuring VVR in a VCS environment 35 Best practices for setting up the
Download Pdf Manuals
Related Search