InfoScale™ 9.0 Disaster Recovery Implementation Guide - Solaris
- Section I. Introducing Storage Foundation and High Availability Solutions for disaster recovery
- About supported disaster recovery scenarios
- About disaster recovery scenarios
- About campus cluster configuration
- About replicated data clusters
- About global clusters
- How VCS global clusters work
- User privileges for cross-cluster operations
- VCS global clusters: The building blocks
- Visualization of remote cluster objects
- About global service groups
- About global cluster management
- About serialization - The Authority attribute
- About resiliency and "Right of way"
- VCS agents to manage wide-area failover
- About the Steward process: Split-brain in two-cluster global clusters
- Secure communication in global clusters
- Disaster recovery feature support for components in the Veritas InfoScale product suite
- Virtualization support for InfoScale 9.0 products in replicated environments
- Planning for disaster recovery
- About supported disaster recovery scenarios
- Section II. Implementing campus clusters
- Setting up campus clusters for VCS and SFHA
- About setting up a campus cluster configuration
- Preparing to set up a campus cluster configuration
- Configuring I/O fencing to prevent data corruption
- Configuring VxVM disk groups for campus cluster configuration
- Configuring VCS service group for campus clusters
- Setting up campus clusters for VxVM and VCS using Veritas InfoScale Operations Manager
- Fire drill in campus clusters
- About the DiskGroupSnap agent
- About running a fire drill in a campus cluster
- About setting up a campus cluster configuration
- Setting up campus clusters for SFCFSHA, SFRAC
- About setting up a campus cluster for disaster recovery for SFCFSHA or SF Oracle RAC
- Preparing to set up a campus cluster in a parallel cluster database environment
- Configuring I/O fencing to prevent data corruption
- Configuring VxVM disk groups for a campus cluster in a parallel cluster database environment
- Configuring VCS service groups for a campus cluster for SFCFSHA and SF Oracle RAC
- Tuning guidelines for parallel campus clusters
- Best practices for a parallel campus cluster
- Setting up campus clusters for VCS and SFHA
- Section III. Implementing replicated data clusters
- Configuring a replicated data cluster using VVR
- Configuring a replicated data cluster using third-party replication
- About setting up a replicated data cluster configuration using third-party replication
- About typical replicated data cluster configuration using third-party replication
- About setting up third-party replication
- Configuring the service groups for third-party replication
- Fire drill in replicated data clusters using third-party replication
- Section IV. Implementing global clusters
- Configuring global clusters for VCS and SFHA
- Installing and Configuring Cluster Server
- Setting up VVR replication
- About configuring VVR replication
- Best practices for setting up replication
- Creating a Replicated Data Set
- Creating a Primary RVG of an RDS
- Adding a Secondary to an RDS
- Changing the replication settings for a Secondary
- Synchronizing the Secondary and starting replication
- Starting replication when the data volumes are zero initialized
- Setting up third-party replication
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- Fire drill in global clusters
- Configuring a global cluster with Storage Foundation Cluster File System High Availability, Storage Foundation for Oracle RAC, or Storage Foundation for Sybase CE
- About global clusters
- About replication for parallel global clusters using Storage Foundation and High Availability (SFHA) Solutions
- About setting up a global cluster environment for parallel clusters
- Configuring the primary site
- Configuring the secondary site
- Setting up replication between parallel global cluster sites
- Testing a parallel global cluster configuration
- Configuring global clusters with VVR and Storage Foundation Cluster File System High Availability, Storage Foundation for Oracle RAC, or Storage Foundation for Sybase CE
- About configuring a parallel global cluster using Volume Replicator (VVR) for replication
- Setting up replication on the primary site using VVR
- Setting up replication on the secondary site using VVR
- Starting replication of the primary site database volume to the secondary site using VVR
- Configuring Cluster Server to replicate the database volume using VVR
- Replication use cases for global parallel clusters
- Configuring global clusters for VCS and SFHA
- Section V. Implementing disaster recovery configurations in virtualized environments
- Section VI. Reference
- Appendix A. Sample configuration files
- Sample Storage Foundation for Oracle RAC configuration files
- About sample main.cf files for Storage Foundation (SF) for Oracle RAC
- About sample main.cf files for Storage Foundation (SF) for Sybase ASE CE
- Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
- Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
- Sample main.cf for a primary CVM VVR site
- Sample main.cf for a secondary CVM VVR site
- Appendix A. Sample configuration files
Prerequisites for creating a Primary RVG of an RDS
Before creating a Primary RVG of an RDS, the following prerequisites must be met:
Ensure that the SRL volume and the data volumes are created on the primary.
Note:
All the volumes must either be encrypted or non-encrypted. A mixed set of volumes is not supported. The createpri command that is used to create a primary RVG fails, if the volume type is not same.
The SRL cannot be a volume set or a component volume of a volume set.
The data volumes and SRL are started, and its state is active.
The data volumes used by the application exist in the same RVG and the data volumes used by the application are in the same RVG.
In a SAN disk group environment, if the application resides on the volume client, all the Primary data volumes must be attached to the volume client or unattached from the volume client.
Make sure you include the appropriate loopback address(es) in the
/etc/hosts file.If your environment only uses IPv4, you must include an IPv4 loopback address in the
/etc/hostsfile. The following is a sample entry:127.0.0.1 localhost loopback
If your environment only uses IPv6, you must include an IPv6 loopback address in the
/etc/hostsfile.::1 localhost loopback
If your environment uses both IPv4 and IPv6, the
/etc/hostsfile must include both loopback addresses.127.0.0.1 localhost loopback ::1 localhost loopback
On Solaris 11, you must manually edit the
/etc/hostsfile to remove the hostname from the lines for loopback addresses.For example:
::1 seattle localhost
127.0.0.1 seattle loghost localhost
needs to be changed to:
::1 localhost
127.0.0.1 loghost localhost
129.148.174.232 seattle
To create a Primary RVG of an RDS
Run the following command on the host on which you want to create the Primary RVG:
# vradmin -g diskgroup createpri rvgname \
dv01_name,dv02_name... srl_nameThe argument rvgname is the name of the RVG to be created.
The argument dv01_name,dv02_name,... is a comma-separated list of the names of the data volumes to be associated to the RVG. Each item can be an independent data volume name, or the name of a volume set. To associate a volume set to the RVG, specify the name of the volume set, not the names of the individual component volumes.
Note:
In previous releases, component volumes could be associated directly to an RVG. Beginning in release 5.0, the volume set itself is associated to the RVG, enabling VVR to verify consistency between the volume sets on the Primary and the Secondary RVGs. The vradmin createpri command fails if a component volume of the volume set and the volume set itself are each specified for an RVG.
The argument srl_name is the name of the SRL to be associated to the RVG.
Use -nodcm option if you do not want DCMs to be added to the data volumes. By default, DCMs are added automatically.