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
Starting the vxfstaskd and vxfsrepld file replication daemons
The vxfstaskd daemon is a scheduler daemon that takes scheduled Storage Checkpoints, starts the replication process against newly created Storage Checkpoints, and cleans up unused Storage Checkpoints. The daemon periodically scans Veritas File System (VxFS) mount points for replication job configuration and automatically schedules any enabled jobs. The vxfstaskd daemon must be started on the source system before a replication job can be scheduled.
The replication scheduler and target daemon can be started and stopped by either using the init script vxfs_replication
or by running the vfradmin command directly. To start both the daemons using the init script, run following command on both the source and the target system:
For systemd environments with supported Linux distributions:
# systemctl start vxfs_replication
For other supported Linux distributions:
# /etc/init.d/vxfs_replication start
By default, the init script will not start the daemons at system bootup or when run manually. If you want to start the replication daemons, edit the replication configuration file at /etc/vx/vxfs_repltab
and set VXFS_REPLICATION_START=1 . The replication daemon, by default uses TCP port 56987. If this port is not free in the environment, specify a desired port in VXFS_REPLICATION_TGT_PORT=port number.
To stop the replication scheduler and the target daemon, run the following command:
For systemd environments with supported Linux distributions:
# systemctl stop vxfs_replication
For other supported Linux distributions:
# /etc/init.d/vxfs_replication stop
To start the vxfstaskd scheduler daemon manually, type the following command on the source system:
# vfradmin sched start
To stop the vxfstaskd daemon, type the following command on the source system:
# vfradmin sched stop [-f]
The vfradmin sched stop command stops the scheduler process after all the in progress replication jobs are complete. If the -f option is specified, all currently scheduled replication jobs are aborted. Specifying the -f option may leave the file system Storage Checkpoints mounted and may leave the target file system in an intermediate state.
The vxfsrepld daemon must be running on the systems that function as replication targets. This daemon listens on the replication port and applies the delta changes sent by the source system. The vxfsrepld daemon must be started on the target system before a replication job can be started.
To start the vxfsrepld replication target daemon manually, type the following command on the target system:
# vfradmin vxfsrepld start [-p port]
where port specifies the port on which the vxfsrepld daemon will listen for the incoming connection.
Note:
By default, the replication daemon uses port 56987. If this port is not free in the environment, you must specify a different port number, using the -p option.
To stop the vxfsrepld daemon, type the following command on the target system:
# vfradmin vxfsrepld stop [-f]
The vfradmin vxfsrepld stop command stops the vxfsrepld daemon after all the in-progress replication jobs are complete. If the -f option is specified, all in progress replication jobs are aborted. This may result in a file system in an intermediate state.
Note:
If either daemon processes are killed and they are not being managed by VCS, they must be manually re-started using the init script or the vfradmin command.