VERITAS Volume Replicator 3.

Release Notes
Solaris

July 2002 32-000105-011

Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and tness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. Copyright Copyright 1998-2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, VERITAS Volume Replicator, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies. July 2002. VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 6505278000 Fax 6505272908 www.veritas.com

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 VERITAS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Displaying Documentation Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Printing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 For the Latest Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 New Features in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Changes in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Recommended Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Compatibility Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Upgrading and Installing Volume Replicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Software Fixes and Enhancements in VVR 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Software Limitations and Problems in VVR 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

iii

iv

VERITAS Volume Replicator Release Notes

VERITAS Volume Replicator Release Notes

Introduction
VERITAS Volume Replicator (VVR) is a licensed product and an add-on feature to the VERITAS Volume Manager (VxVM). This document provides release information for VERITAS Volume Replicator 3.5 on Solaris and contains additional information to the Release Notes for VxVM. Note that Volume Replicator Administrative Services (VR-AS) has been integrated with VVR, that is, VR-AS is no longer a separate package. Review this entire document before installing VVR. For additional information about this release, see section For the Latest Product Information on page 5. VERITAS Volume Replicator has been tested on Solaris 2.6, Solaris 7 (32-bit and 64-bit), Solaris 8 (32-bit and 64-bit), and Solaris 9 (32-bit and 64-bit) operating systems. This release of VVR is not supported on Solaris 2.5.1 and Solaris x86.

Getting Help

Getting Help
For assistance with any of the VERITAS products, contact VERITAS Technical Support: U.S. and Canadian Customers: 1-800-342-0652 International: +1-650-527-8555 Email: support@veritas.com For license information: Phone: 1-925-931-2464 Email: license@veritas.com Fax: 1-925-931-2487 For software updates: Email: swupdate@veritas.com For information on purchasing VERITAS products: Phone: 1-800-258-UNIX (1-800-258-8649) or 1-650-527-8000 Email: vx-sales@veritas.com For additional information about VERITAS and VERITAS products, visit the Web site at: www.veritas.com. For late-breaking news about this release, see section For the Latest Product Information on page 5. For additional technical support information, such as technical notes, alerts, and hardware compatibility lists, visit the Knowledge Base on the Technical Support Web site at: www.support.veritas.com

VERITAS Volume Replicator Release Notes

VERITAS Packages

VERITAS Packages
The VERITAS CD labeled VERITAS Storage Solutions for SolarisDisc 2 contains the following packages: VRTSvlicVERITAS Licensing Utilities. VRTSvxvmVERITAS Volume Manager and Volume Replicator software. VRTSwebVERITAS Web GUI Common Web Server package. VRTSvrwVERITAS Volume Replicator Web Console package. VRTSvrdocOnline copies of VERITAS Volume Replicator guides. VRTSvmdocOnline copies of VERITAS Volume Manager guides. VRTSvmmanVolume Replicator and Volume Manager manual pages. VRTSobVERITAS Enterprise Administrator Service (required) VRTSobguiVERITAS Enterprise Administrator (required) VRTSvmproVERITAS Virtual Disk Management Services Provider (required) VRTSfsproVERITAS File System Provider (required, even if you are not installing the VERITAS File System software)

Displaying Documentation Online

You can nd the VERITAS Volume Replicator documentation set under the foundation_suite/docs directory on the VERITAS CD labeled VERITAS Storage Solutions for SolarisDisc 2. You can also install the VVR documentation set by installing the VRTSvrdoc package located on Disc 2 under the foundation_suite/pkgs directory. The VERITAS Volume Replicator Release Notes (this document) is available online in the foundation_suite/release_notes directory. Because product release notes are not installed by any packages, VERITAS recommends that you copy them to the /opt/VRTS/doc directory so that they are available for future reference. For a list of the VERITAS Volume Manager documents provided with this release, see the VERITAS Volume Manager Release Notes. This product includes online documentation in Adobe Portable Document Format (PDF).

VERITAS Volume Replicator Release Notes

Printing Documentation

VERITAS Volume Replicator Documentation Set VERITAS Volume Replicator Release Notes 3.5 (this document) VERITAS Volume Replicator Administrators Guide 3.5 VERITAS Volume Replicator Conguration Notes 3.5 VERITAS Volume Replicator Web Console Administrators Guide VERITAS Volume Manager Documentation Set Refer to the Volume Manager Release Notes for a list of the Volume Manager documents that accompany this release of Volume Manager. To view PDF documents, use the Adobe Acrobat Reader. You can use Acrobat Reader as a stand-alone application, or as a plug-in to your web browser. However, VERITAS Software assumes no responsibility for the correct installation or use of Acrobat Reader. For more information on the latest versions of Acrobat Reader, or for help with installation problems, visit the Adobe Web site at: www.adobe.com Unformatted manual pages related to the VERITAS Volume Manager and Volume Replicator are provided in the VRTSvmman package on the CD-ROM. If you have installed the VRTSvmman package, the manual pages can be found in the /opt/VRTS/man directory. If you add that directory to your MANPATH environment variable, you can view these manual pages with the man(1) command.

Printing Documentation
Use the print options in your Acrobat Reader viewer to print one or more pages.

VERITAS Volume Replicator Release Notes

For the Latest Product Information

For the Latest Product Information

There may be important information about this release that is available from VERITAS technical support. To view this information: 1. Go to www.support.veritas.com. 2. Click Knowledge Base Search. 3. Select Volume Replicator in the Search Product eld, and then enter late breaking information in the Search Phrase eld. 4. Click Search Now. This will provide the latest VVR 3.5 product information.

VERITAS Volume Replicator Release Notes

New Features in This Release

New Features in This Release

This release of VERITAS Volume Replicator includes the following features:
x

Firewall Support Now you can congure VVR to replicate in a rewall environment. For more information, see the VERITAS Volume Replicator Conguration Notes.

Support for Layered SRL In the earlier releases of VVR, the SRL could not be congured as a stripe-mirror volume. In this release of VVR, the SRL can be a striped-mirror volume. If you want to convert an existing mirror-stripe SRL, use the following command: # vxassist -g diskgroup convert srl layout=stripe-mirror

Integration of VERITAS Volume Replicator Administrative Services With VxVM and VVR The Volume Replicator Administrative Services (VR-AS) package has been merged with the VERITAS Volume Manager package. This provides simplied installation of VVR and avoids compatibility issues between VVR and VR-AS.

Simplied Upgrade Procedure This release of VVR includes scripts to simplify the upgrade procedure. For instructions, see the VERITAS Volume Replicator Administrators Guide.

Volume Replicator Web Console (VRW) VRW is the Web-based GUI for VVR. For details, see the Volume Replicator Web Console Administrators Guide and Volume Replicator Web Console Release Notes.

New Tunables Two new tunables have been included in this release: vol_dcm_replay_size, and vol_nm_hb_timeout. Refer to the VERITAS Volume Replicator Conguration Notes for information about these tunables.

Simplied Framework for Using IBC messaging With Off-host Processing Earlier, using IBC messaging for off-host processing required execution of multiple commands on multiple hosts. Now, VVR provides the vradmin ibc command, which simplies this task and enables you to dene and execute scripts to automate the procedure.

Ofine Data Verication The vradmin syncrvg command and the vradmin syncvol commands have been enhanced to verify whether the Primary and Secondary data is identical. This data verication can only be done while application is inactive.

VERITAS Volume Replicator Release Notes

New Features in This Release x

New Mode of SRL Protectionautodcm By default, SRL protection is set to autodcm; if the SRL is about to overow, VVR switches automatically to dcm logging mode and writes continue. Previously, writes were throttled until either the RLINK disconnected or until 20MB or 5% of the SRL, whichever is lower, was free.

Consolidated View of Replication Status In the earlier releases of VVR, you were required to run multiple commands on multiple hosts to determine replication status. Now, the new vradmin repstatus command provides a consolidated view of the replication status.

New VVR Commands In addition to the above enhancements, VVR provides new commands to perform the following tasks:

To change the replication network setting To remove a Primary from its RDS

vradmin changeip vradmin delpri

To replay a DCM that is active because of an SRL overow or vradmin resync failback logging, that is, to incrementally synchronize the Secondary To change replication settings including mode of replication, SRL protection, and latency protection. To display the VVR and VxVM memory pool statistics. To prematurely terminate the receive and regrecv operations before the IBC message arrives on the Secondary. To display the names of the RLINKs that are associated with the specied RVG. To display the names of the data volumes that are associated with the specied RVG. To display application statistics for the specied RVG vradmin set

vxmemstat vxibc stoprecv

vxrvg getrlinks

vxrvg getdatavols

vxrvg stats

VERITAS Volume Replicator Release Notes

Changes in This Release

Changes in This Release

x

The tunable parameters for VVR have been relocated from the /etc/system le to the les /kernel/drv/vxio.conf for the vxio driver, and /kernel/drv/vxdmp.conf for the vxdmp driver. The default value of the tunable voliomem_maxpool_sz has been changed from 4MB to either 128MB or 5% of the main memory, whichever is lower. The value of this tunable has been adjusted to suit large systems. For more information, see the VERITAS Volume Replicator Conguration Notes.

Recommended Patches
The following section contains patch information required for proper use of VVR. Patch information is determined at the time of product release. For the latest information, contact Sun Microsystems. Refer to VERITAS Volume Manager Release Notes 3.5 for the Solaris patch requirements. VVR requires the following Solaris patches in addition to the ones listed in the VERITAS Volume Manager Release Notes. The following list gives the minimum revision levels for the required patches: Solaris 2.6: 105541-05, 106532-03 Solaris 7: 108263-06 Solaris 8: 108981-03, 108806-02 Solaris 9: None

VERITAS Volume Replicator Release Notes

Compatibility Considerations

Compatibility Considerations
This release of VVR is available for the Solaris 2.6, Solaris 7, Solaris 8, and Solaris 9 operating systems. Solaris 8 and Solaris 9 includes a new version of Internet Protocol (IP), IPv6. VVR is not supported with IPv6. All nodes in a VVR environment must use IPv4. You can replicate between nodes running the 32-bit versions and the 64-bit versions of these operating systems, that is, you can mix 32-bit and 64-bit versions. VVR has been tested to work with the host operating interchangeably between 32-bit and 64-bit environments. VVR 3.5 is not interoperable with prior releases of VVR. All systems in a VVR environment must have VVR 3.5 installed. Note that this release of VVR does not include VERITAS Volume Manager Storage Administrator for VVR (VMSA-VVR). Prior versions of VMSA will not work with VVR 3.5. VERITAS Enterprise Administrator (VEA) does not include functionality to administer VVR. To administer VVR using a GUI, use VERITAS Volume Replicator Web Console (VRW). VVR 3.5 has been tested with VERITAS Cluster Server 2.0 and VERITAS Cluster Server 3.5. Use VERITAS Cluster Server Enterprise Agent for VVR version 3.5 with VVR 3.5.

Obtaining a License Key

Before installing VVR, obtain a license key for VERITAS Volume Replicator. Note that even if you have already obtained a VERITAS Volume Manager license key, you must obtain a separate license key for VVR. For details, see the section about license information in the VERITAS Volume Manager Installation Guide.

Upgrading and Installing Volume Replicator

Refer to Chapter 3, Installing VERITAS Volume Replicator in the VERITAS Volume Replicator Administrators Guide.

VERITAS Volume Replicator Release Notes

Software Fixes and Enhancements in VVR 3.5

Software Fixes and Enhancements in VVR 3.5

Note that Volume Replicator Administrative Services (VR-AS) has been integrated with VVR, that is, it is no longer a separate package. The following table includes the software xes and enhancements in VVR 3.5, which includes VR-AS.
Incident Number Description

47554

RLINK detach was allowed even if data volumes were open, the SRL had pending updates, or the DCM was not empty. Now, the operation fails with an error message. If you still must detach the RLINK, use the force option (-f) with the vxrlink detach command. A warning will be printed indicating that the Secondary needs to be completely synchronized. In the earlier releases of VVR, the SRL could not be congured as a stripe-mirror volume. Now, the SRL can be a striped-mirror volume. If you want to convert an existing mirror-stripe SRL, use the following command: # vxassist -g dg_name convert srl layout=stripe-mirror When the vradmin syncvol command was terminated, the synchronization process continued through completion. This problem has been xed. The default value for the tunable voliomem_maxpool_sz has been increased to accommodate larger systems with more real memory. For more information, see the VERITAS Volume Replicator Conguration Notes. The vradmin resumerep command would not resume the paused Secondary RLINK. This problem has been xed. If a Secondary RVG has multiple RLINKs and all the RLINKs are detached, the vradmin -N takeover command will fail. If the RVG was disabled, the vxrlink updates command printed the following message, which is not self-explanatory:
vxvm:vxrlink: ERROR Rvg upid ioctl failed 6

56015

58918

60840

68786 71386 72696

This has been xed. Now, the vxrlink updates command prints the following message:
The updates command cannot be run when the RVG rvg is in a disabled state.

72972

On a disk group version that is lower than 90, vxprint -l on an associated RLINK would always prints the protocol as TCP/IP. This occurred even if the UDP/IP was congured. This problem has been xed.

10

VERITAS Volume Replicator Release Notes

Software Fixes and Enhancements in VVR 3.5

74723

When running a vradmin command that requires a user response, such as vradmin stoprep, if the user did not respond within a few minutes after the command was issued, the command would terminate with error messages similar to the following:
TAG_C 2001/08/08 16:28:20 IpmHandle:recv peer exited errno=131 vradmind stopped running - Exiting

The command failed because the connection to vradmind had timed out. However, the second error message was incorrect because vradmind was still running even after the command terminated. Now the command does not terminate and the error messages do not appear. 76477 The vxrvg stop rvg_name command would work even when the data volumes were open. Because the command caused all subsequent I/Os to the data volume to fail, the application with the data volume open would see the I/O failures. This problem has been xed. Killing the vrnotify command while it is running resulted in vradmind dumping core. This problem has been xed. Some conguration error messages would not get cleared in the output of the vradmin -l printrvg command after the errors were corrected. This problem has been xed. The vradmin takeover command would take a long time to complete. This problem has been xed. While an automatic synchronization to a Secondary was in progress, running the vradmin migrate command to migrate the Primary role to that Secondary would cause the vradmind daemon to core dump. The output of the vradmin -l printrvg command would not show network-disconnected error in the Cong Errors block in some cases. This problem has been xed. VVR now provides additional notications for various events. Events such as a change in replication mode from synchronous-> asynchronous and asynchronous->synchronous, RVG state transitions, notication for node connect or disconnect are logged in syslog and available as trace events. Now VVR fails the resyncfromreplica option of the vxassist snapback command for the data volumes if the RLINKs are attached. On the Secondary, VVR fails the resyncfromreplica option unless the RLINKs are in the FAIL state, that is, VVR allows you to recover the Secondary data volumes. For details, see "Using Snapback With resyncfromreplica Option" in the VERITAS Volume Replicator Adminstrators Guide.

81134 81535

81737 82941

84166

84729

85995

VERITAS Volume Replicator Release Notes

11

Software Fixes and Enhancements in VVR 3.5

87221

In the earlier release, a waiting IBC receive operation could not be terminated. Now, VVR provides the vxibc stoprecv command to terminate a waiting IBC receive operation. After a failed vradmin addsec command, the displayed RDS information could be incorrect. This problem has been xed. On recovery, VVR warns if a condition will disallow replication to continue. If for any reason the RLINK cannot replicate after a recovery, a message stating so is displayed on the console. The vradmin addsec command did not perform a security check similar to the one performed in the vradmin syncvol command before adding a new Secondary to an RDS. VVR now performs the security check in the vradmin addsec command. The vradmin resizevol command did not require the -f option to shrink volumes. Now VVR requires the -f option to the vradmin resizevol command to shrink volumes in an RDS. The vradmin makesec command should not be allowed on a failed Primary which was taken over by its Secondary with failback logging enabled. VVR now contains this check. At a customer site, the SRL had become corrupted but the RLINK would not detach. The following message was displayed on the console:
WARNING: vxvm:vxio: rvg rvg_name, SRL srl_name: Inconsistent log - detaching all RLINKs

87917 88037

88855

88983

89363

89428

Now, VVR detaches the RLINKs. However, sufcient information was not available to determine why the SRL became inconsistent. 89625 If an IBC message was pending for an RLINK, you could not pause that RLINK. This has been xed. Also, if you received an IBC message on the Secondary and the corresponding application name was not registered, the message was discarded. VVR now waits for 10 minutes for the application to be registered. 91044 90154 The vradmin syncrvg command had performance issues over a high latency WAN. This problem has been xed. The vradmin createpri command would fail if the data volumes and SRL were not in the disk group rootdg and the -g diskgroup option was not specied in the createpri command. This problem has been xed. The vradmin addsec command would not start the new Secondary RVG. VVR now contains this change.

91302

12

VERITAS Volume Replicator Release Notes

Software Fixes and Enhancements in VVR 3.5

91786 92414

The vradmin migrate command would not stop the old Primary RVG. This has been xed. The vrnotify command would not handle arguments properly. The command would core dumps if no arguments were specied after the -g option. This problem has been xed. While a vradmin command was running, pressing CTRL+C twice would result in vradmind dumping core. This problem has been xed. VVR now supports up to 46 checkpoints. Fixed the problem that caused panic during readback processing and resulted in corrupting the SRL. This could have caused loss of data on the Secondary requiring a full resynchronization. The vxrlink stats command shows negative stream errors. A failed vradmin takeover command could put the Secondary in a wrong state that caused all vradmin commands that were subsequently run on this RDS to fail. This problem has been xed. The vradmin createpri, vradmin addsec, and vradmin addvol commands now remove the DRLs from data volumes and add DCMs to the data volumes by default. The vradmin delsec command would fail if the name of the SRL on the Secondary RVG was different from the name of the SRL on the Primary. This problem has been xed. If the RLINK disconnects or the original Primary reboots while the original Primary recovers after a takeover of the Primary role and the original Primary is being resynchronized using the new Primary, data loss may occur thus requiring a complete resynchronization of the original Primary. This problem has been xed.

93597 94032 95246

97270 95306

98019

98704

100375

VERITAS Volume Replicator Release Notes

13

Software Limitations and Problems in VVR 3.5

Software Limitations and Problems in VVR 3.5

Incident Number Description

34581

A disk group cannot be imported as shared if it contains VVR objects. Attempting to do so will leave the disks marked as shared and therefore subsequent non-shared imports will also fail. You can enable subsequent imports by doing a vxdisk clearimport on all the disks in the disk group. If a number of vradmin commands are started in background at the same time, some of them might fail. The vradmin printrvg command does not display an error message to indicate an incorrect conguration when the local_host and remote_host attributes contain the names of hosts that are not in the RDS. Solaris 8 and Solaris 9 include a new version of Internet Protocol (IP), IPv6. VVR does not support IPv6. VxFS commands may execute very slowly and appear to be hung when the following conditions exist: The RLINK is in synchronous mode The network has a low bandwidth VxFS has a very large cache

46153 50275

52850 55586

If you encounter this problem, contact Customer Support for help. 55695 If the total size of the RVG name and the remote host names exceed 26 characters, the default RLINK names created by the vradmin addsec command are truncated. This may result in a conict with other RLINK names and cause an error. To avoid this error, use the prlink and srlink attributes with the addsec command. 62037 If you create a volume with a DCM and want to convert it to be part of a layered volume by issuing the vxedit set layered=on volume command, the following error message displays:
Unexpected kernel error in configuration update

Do not use this command for volumes to be associated with an RVG. 94274 The vxrlink updates command may display that the Secondary is a few updates behind than it is in reality. The number of updates is less than the number of concurrent application writes.
VERITAS Volume Replicator Release Notes

14

Software Limitations and Problems in VVR 3.5

94339

Running the vradmin addsec command from a system running VVR 3.5 to add a Secondary that is running an earlier version than VVR 3.5 results in incorrect conguration information on the Secondary host. To x the problem, restart vradmind on the Secondary host. If a volume is associated with an RDS for which automatic synchronization is in progress to one of its Secondary hosts, VVR does not warn the user that the new volume will not be synchronized. Synchronize the volume before associating it with the RDS. The vxrlink stats command may display an incorrect number of stream errors after an RLINK disconnects. The vxrlink command usage message has a typographical mistake. The presented option [-timestamp_freq] should be [-t timestamp_freq]. If you change the IP address of a host but do not change the host name, vradmind may not work correctly because it still uses the previous IP address to communicate to other hosts in the RDS. To x the problem, restart vradmind. In an environment that contains shared disk groups and a VVR license, vradmind core dumps if it is started before the slave completes joining the cluster. Restart vradmind for the vradmin commands to work. To restart vradmind, run /etc/init.d/vras-vradmind.sh start. If there is a pending IBC operation when the SRL overows, make sure that the Secondary is unfrozen before initiating replay of the DCM. Failure to do so could result in loss of data on the Secondary. Synchronizing two or more Secondary hosts simultaneously using the automatic synchronization feature can result in incomplete synchronization of the data on the Secondary making it unusable. If it is necessary to synchronize two or more Secondary hosts using the automatic synchronization feature, synchronize each Secondary separately. The vxprint -e pattern command: Selecting RVG and RLINK records using search expressions is not currently supported. VVR does not support Volume Manager RAID5 volumes as part of RVGs. Hardware RAID5 is supported. If a disk group containing VVR objects is imported on two nodes, as well as the problems documented for VxVM objects, the SRL is corrupted and a full resynchronization of the Secondary is required. It is not recommended to have replicated volumes in the root disk group (rootdg).

97821

99025 100962

102187

102598

103326

103127

None None None

None

VERITAS Volume Replicator Release Notes

15

Configuration Worksheet

None

VVR does not support Disk Group Split and Join. This means that you cannot use Disk Group Split and Join on data volumes in an RVG. However, you can take snapshots of data volumes and use DGSJ on the snapshots. Do not use the layered ag attribute for a replicated volume. A failure will occur if you try to set the layered ag on when the volume is in an RVG. For a Replicated Data Set (RDS) with multiple Secondaries, the vradmin migrate command does not automatically recongure any additional Secondaries as Secondaries of the new Primary. If required, recongure the additional Secondaries as Secondaries of the new Primary using the VVR command-line interface. When adding a Secondary to the RDS, the vradmin addsec command cannot be entered from the host being added. If the RDS contains the Primary only, the command must be entered on the Primary.

None None

None

Conguration Worksheet
The conguration worksheet helps you plan the layout of a Replicated Data Set and prepares you to set up a VVR conguration. This worksheet appears in the VERITAS Volume Replicator Administrators Guide also. The worksheet has been provided here to enable you to easily make copies. Use one worksheet for each RVG on each host of the RDS, that is, one Primary and as many Secondaries as required.

16

VERITAS Volume Replicator Release Notes

Configuration Worksheet

Conguration Worksheet

Primary/Secondary (choose one): Hostname: IP Addresses: Disk Group: RVG: (If this is the Primary node, repeat the RLINK information for each Secondary node in the conguration.) RLINK: Remote Host: Remote RLINK: Synchronous (off/override/fail): Latencyprot (off/override/fail): Srlprot (autodcm/override/fail/dcm/off): SRlog: Volume: Data Volumes: Volume: Volume: Volume: Volume: Plex: Plex: Plex: Plex: Disk: Disk: Disk: Disk: Size: Size: Size: Size: DCM (Y/N): DCM (Y/N): DCM (Y/N): DCM (Y/N): Plex: Disk: Size: Remote DG: Disk Group Version: Aliases: License Key:

(Repeat the Data Volumes: information for each Data Volume in the conguration.)

Note Specifying the disks for a volume is optional.

VERITAS Volume Replicator Release Notes

17

Configuration Worksheet

18

VERITAS Volume Replicator Release Notes