InfoScale™ 9.0 Disaster Recovery Implementation Guide - Linux
- Section I. Introducing Storage Foundation and High Availability Solutions for disaster recovery
- About supported disaster recovery scenarios
- About campus cluster configuration
- About replicated data clusters
- About global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- 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
- About running a fire drill in a campus cluster
- About setting up a campus cluster configuration
- Setting up campus clusters for SFCFSHA, SFRAC
- 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
- Section IV. Implementing global clusters
- Configuring global clusters for VCS and SFHA
- Setting up VVR 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
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- Configuring a global cluster with Storage Foundation Cluster File System High Availability, Storage Foundation for Oracle RAC, or Storage Foundation for Sybase CE
- Configuring the secondary site
- Configuring global clusters with VVR and Storage Foundation Cluster File System High Availability, Storage Foundation for Oracle RAC, or Storage Foundation for Sybase CE
- Setting up replication on the primary site using VVR
- Setting up replication on the secondary site using VVR
- Configuring Cluster Server to replicate the database volume using VVR
- Configuring global clusters for VCS and SFHA
- Section V. 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
- Appendix A. Sample configuration files
Setting the latency protection for a Secondary
The vradmin set command enables you to set the latencyprot attribute to override, fail, or off; it also enables you to specify a latency_high_mark and a latency_low_mark, which indicate when the protection becomes active or inactive.
Set the latencyprot attribute to enable latency protection between a Primary and a Secondary.
Note:
Before enabling latency protection, be sure you understand how latency protection works when the Primary and Secondary are connected or disconnected.
- Set the latencyprot attribute of the corresponding RLINKs on the Primary and Secondary.
To set the latencyprot attribute to override:
# vradmin -g diskgroup set local_rvgname sec_hostname \ latencyprot=override
To set the latencyprot attribute to fail:
# vradmin -g diskgroup set local_rvgname sec_hostname \ latencyprot=fail
- Set the latency_high_mark and the latency_low_mark attributes:
# vradmin -g diskgroup set local_rvgname sec_hostname \ latency_high_mark=high_mark
# vradmin -g diskgroup set local_rvgname sec_hostname \ latency_low_mark=low_mark
The argument local_rvgname is the name of the RVG on the local host and represents the RDS.
The argument sec_hostname is the name of the Secondary host as displayed in the output of the vradmin printrvg command.
Note that the value of latency_high_mark must be greater than the value of latency_low_mark. We recommend that the difference between the value of latency_high_mark and the value of latency_low_mark be a small number, for example, 50.
- Setting the latencyprot attribute to off disables latency protection. This does not limit the number of waiting updates in the SRL.
To set the latencyprot attribute to off:
# vradmin -g diskgroup set local_rvgname sec_hostname latencyprot=off
The argument local_rvgname is the name of the RVG on the local host and represents the RDS.
The argument sec_hostname is the name of the Secondary host as displayed in the output of the vradmin printrvg command.