Veritas InfoScale™ 8.0.2 Replication Administrator's Guide - Linux
- Section I. Getting started with Volume Replicator
- Introducing Volume Replicator
- Understanding how Volume Replicator works
- How VVR uses kernel buffers for replication
- Replication in a shared disk group environment
- Using SmartTier with VVR
- Understanding the VVR snapshot feature
- About VVR compression
- Planning and configuring replication
- Before you begin configuring
- Choosing the mode of volume replication
- Planning the network
- Sizing the SRL
- Understanding replication settings for a Secondary
- Configuring VVR in a VCS environment
- Using the primary-elect feature to choose the primary site after a site disaster or network disruption
- Requirements for configuring VVR in a VCS environment
- Example setting up VVR in a VCS environment
- Configuring the agents for a bunker replication configuration
- Section II. Setting up and administering VVR
- 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
- Displaying configuration information
- Displaying RVG and RDS information
- Displaying information about data volumes and volume sets
- Displaying information about Secondaries
- Displaying statistics with the vrstat display commands
- Collecting consolidated statistics of the VVR components
- Displaying network performance data
- VVR event notification
- Administering Volume Replicator
- Administering data volumes
- Associating a volume to a Replicated Data Set
- Associating a volume set to an RDS
- Associating a Data Change Map to a data volume as a log plex
- Resizing a data volume in a Replicated Data Set
- Administering the SRL
- Incrementally synchronizing the Secondary after SRL overflow
- Administering replication
- Administering the Replicated Data Set
- Administering Storage Checkpoints
- Creating RVG snapshots
- Using the instant snapshot feature
- About instant full snapshots
- Preparing the volumes prior to using the instant snapshot feature
- Creating instant full snapshots
- About instant space-optimized snapshots
- Creating instant space-optimized snapshots
- About instant plex-breakoff snapshots
- Administering snapshots
- Using the traditional snapshot feature
- Using Veritas Volume Manager FastResync
- Verifying the DR readiness of a VVR setup
- Backing up the Secondary
- Administering data volumes
- Using VVR for off-host processing
- Transferring the Primary role
- Migrating the Primary
- About taking over from an original Primary
- Failing back to the original Primary
- Choosing the Primary site after a site disaster or network disruption
- Troubleshooting the primary-elect feature
- Replication using a bunker site
- Introduction to replication using a bunker site
- Setting up replication using a bunker site
- Using a bunker for disaster recovery
- Replication using a bunker site in a VCS environment
- Troubleshooting VVR
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Tuning replication performance
- SRL layout
- Tuning Volume Replicator
- VVR buffer space
- Tuning VVR compression
- VVR buffer space
- Setting up replication
- Section III. Getting started with File Replicator
- Introducing File Replicator
- Administering File Replicator
- Displaying file replication job information
- Section IV. Analyzing your environment with Volume Replicator Advisor
- Introducing Volume Replicator Advisor (VRAdvisor)
- Collecting the sample of data
- About collecting the sample of data
- Collecting the sample of data on UNIX
- Collecting the sample of data on Windows
- Analyzing the sample of data
- About analyzing the sample of data
- Analyzing the collected data
- Understanding the results of the analysis
- Viewing the analysis results
- Recalculating the analysis results
- Installing Volume Replicator Advisor (VRAdvisor)
- Section V. VVR reference
- Appendix A. VVR command reference
- Appendix B. Using the In-band Control Messaging utility vxibc and the IBC programming API
- Using the IBC messaging command-line utility
- Examples - Off-host processing
- In-band Control Messaging API
- Appendix C. Volume Replicator object states
- Appendix D. Alternate methods for synchronizing the Secondary
- Using the full synchronization feature
- Using block-level backup and Storage Checkpoint
- Using difference-based synchronization
- Examples for setting up a simple Volume Replicator configuration
- Appendix E. Migrating VVR from IPv4 to IPv6
- Migrating VVR to support IPv6 or dual stack
- About migrating to IPv6 when VCS global clustering and VVR agents are not configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Appendix F. Sample main.cf files
Understanding the current IPv4 configuration when VCS global clustering and VVR agents are not configured
Before you migrate VVR from IPv4 to IPv6, review your current configuration. The sample configuration is as follows:
There are two nodes each on the Primary and the Secondary site of replication.
RVG objects are created on both the sites. Replication between the sites uses the IPv4 address.
A failover service of the Virtual IPv4 address is created for high availability.
The failover service group consists of one IP resource and one NIC resource for the virtual IPv4 address.
On every system, the state of the resources in the failover service group is similar to the following:
# hares -state | grep -i res #Resource Attribute System Value ipres State swlx25 ONLINE ipres State swlx27 OFFLINE nicres State swlx25 ONLINE nicres State swlx27 ONLINE
On both the systems, the state of the failover service group is similar to the following:
# hastatus -summ | grep -i VVRGRP B VVRGRP swlx25 Y N ONLINE B VVRGRP swlx27 Y N OFFLINE
The contents of the
main.cf
file in the failover service group are displayed as follows:group VVRGRP ( SystemList = { swlx25 = 0, swlx27 = 1 } AutoStartList = { swlx25 } ) IP ipres ( Device = eth0 Address = "10.209.87.186" NetMask = "255.255.252.0" ) NIC nicres ( Enabled = 1 Device = eth0 ) ipres requires nicres // resource dependency tree // // group VVRGRP // { // IP ipres // { // NIC nicres // } // }
After you create the service group VVRGRP, the output of the ifconfig command is as follows:
# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:30:6E:2B:4F:B6 inet addr:10.209.85.35 Bcast:10.209.87.255 Mask:255.255.252.0 inet6 addr: fe80::230:6eff:fe2b:4fb6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:172660 errors:0 dropped:0 overruns:0 frame:0 TX packets:17172 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16012095 (15.2 Mb) TX bytes:3357637 (3.2 Mb) Interrupt:96 eth0:0 Link encap:Ethernet HWaddr 00:30:6E:2B:4F:B6 inet addr:10.209.87.186 Bcast:0.0.0.0 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:96 eth1 Link encap:Ethernet HWaddr 00:11:43:37:DA:68 inet6 addr: fe80::211:43ff:fe37:da68/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:33161 errors:0 dropped:0 overruns:0 frame:0 TX packets:18635 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:3315207 (3.1 Mb) TX bytes:3288512 (3.1 Mb) eth2 Link encap:Ethernet HWaddr 00:11:43:37:DA:69 inet6 addr: fd4b:454e:205a:111:211:43ff:fe37:da69/64 Scope:Global inet6 addr: fe80::211:43ff:fe37:da69/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:71504 errors:0 dropped:0 overruns:0 frame:0 TX packets:856 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:7700084 (7.3 Mb) TX bytes:285676 (278.9 Kb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:38 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4876 (4.7 Kb) TX bytes:4876 (4.7 Kb)