Volume Replicator 5.0 Release Notes - Storage Foundation ...
Volume Replicator 5.0 Release Notes - Storage Foundation ... Volume Replicator 5.0 Release Notes - Storage Foundation ...
16 Veritas Volume Replicator Release NotesKnown issues2 Kill the vxcached, vxrelocd and vxnotify processes by using the kill -9command with their process IDs as reported by the ps command.3 Eject the software disc.4 Restart the VxVM daemon processes:[622442]# /usr/sbin/vxddladm start eventsource# /etc/vx/bin/vxcached# /etc/vx/bin/vxrelocdSupport and compatibility issuesRunning VxFS commands (135938)VxFS commands may execute very slowly and appear to be hung when thefollowing conditions exist:■■The RLINK is in synchronous modeThe network has a low bandwidth■VxFS has a very large cacheIf you encounter this problem, contact Customer Support.VxVM ISP Stripe-mirror Volumes Cannot be Associated to an RVGYou cannot associate VxVM ISP volumes of the type stripe-mirror to an RVG.[497136]The vradmin issuesMultiple vradmin commands (304827)If a number of vradmin commands are started at the same time in the background, some of the commands might fail.Incorrect configuration (304859)The vradmin printrvg command does not display an error message to indicate an incorrect configuration when the local_host and remote_hostattributes contain the names of the hosts that are not in the RDS. Invalid license (139302)The vradmin commands that change the configuration may fail before completing if the VVR license has expired. Although an attempt is made to undo the changes, it may not be possible to undo the changes because the license has expired.
Veritas Volume Replicator Release Notes 17Known issuesSynchronizing volumes and RVG—user cannot specify an offset (306135)The vradmin syncrvg and the vradmin syncvol commands do not allow the user to specify an offset for the synchronization operation. They perform the operations on the entire data volume. If the operation is terminated, it must be restarted.Verifying data (306479)The vradmin verifydata command may hang if certain events occur, for example, if the network disconnects, or a large number of writes on the Primarycause the RLINK to go in to DCM mode after the command is issued and before it completes. Workaround: Kill the vradmin verifydata command using the SIGTERM signal. Press ^C on the command line, and then perform the following steps on Secondary host:1 Issue the command:# vxibc -g dg_name status rvg_nameThe output displays one or more application IDs.2 Choose the application ID that begins with VD and use this app-id in thefollowing steps.3 Issue the command:# vxibc -g dg_name stoprecv app-id rvg_name4 Issue the command:# vxibc -g dg_name unregister app-id rvg_nameThe output of the command vxibc -g dg_name status rvg_name shouldno longer display the app-id.Resizing the SRLThe vradmin resizesrl command enables you to increase the size of the SRL while the application is active and replication is in progress. The vradminresizesrl command does not allow you to decrease the size of the SRL. For instructions on resizing the SRL, see the Veritas Volume ReplicatorAdministrator's Guide.Separator display in the vradmin output (306642)The separator in the output of vradmin -l printrvg is not localized; it always displays as a comma (,). Adding a 5.0 Secondary to an RDS with a 4.1 Primary (423878)If the RDS has a 4.1 Primary and a 5.0 Secondary, you cannot use the vradmin addsec command to add an additional 5.0 Secondary to the RDS. First, upgrade the Primary to 5.0, and then add the Secondary.
- Page 1 and 2: Veritas Volume ReplicatorRelease N
- Page 3: Third-party legal noticesThird-part
- Page 6 and 7: 6 ContentsSelecting records using s
- Page 8 and 9: 8 Veritas Volume Replicator Release
- Page 10 and 11: 10 Veritas Volume Replicator Releas
- Page 12 and 13: 12 Veritas Volume Replicator Releas
- Page 14 and 15: 14 Veritas Volume Replicator Releas
- Page 18 and 19: 18 Veritas Volume Replicator Releas
- Page 20 and 21: 20 Veritas Volume Replicator Releas
- Page 22 and 23: 22 Veritas Volume Replicator Releas
- Page 24 and 25: 24 Veritas Volume Replicator Releas
- Page 26 and 27: 26 Veritas Volume Replicator Releas
- Page 28 and 29: 28 Third-party Legal NoticesApache
- Page 30 and 31: 30 Third-party Legal NoticesPARTICU
- Page 32 and 33: 32 Third-party Legal Notices3. YOU
- Page 34 and 35: 34 Third-party Legal NoticesTo prot
- Page 36 and 37: 36 Third-party Legal Noticescode fo
- Page 38 and 39: 38 Third-party Legal NoticesWILLING
- Page 40 and 41: 40 Third-party Legal NoticesThe lic
- Page 42 and 43: 42 Third-party Legal NoticesHowever
- Page 44 and 45: 44 Third-party Legal NoticesTo appl
- Page 46 and 47: 46 Third-party Legal NoticesCopyrig
- Page 48 and 49: 48 Third-party Legal Notices8. If t
- Page 50 and 51: 50 Third-party Legal NoticesTHIS SO
- Page 52 and 53: 52 Third-party Legal NoticesFile-Sp
- Page 54: 54 Third-party Legal NoticesSysdep.
16 Veritas <strong>Volume</strong> <strong>Replicator</strong> <strong>Release</strong> <strong>Notes</strong>Known issues2 Kill the vxcached, vxrelocd and vxnotify processes by using the kill -9command with their process IDs as reported by the ps command.3 Eject the software disc.4 Restart the VxVM daemon processes:[622442]# /usr/sbin/vxddladm start eventsource# /etc/vx/bin/vxcached# /etc/vx/bin/vxrelocdSupport and compatibility issuesRunning VxFS commands (135938)VxFS commands may execute very slowly and appear to be hung when thefollowing conditions exist:■■The RLINK is in synchronous modeThe network has a low bandwidth■VxFS has a very large cacheIf you encounter this problem, contact Customer Support.VxVM ISP Stripe-mirror <strong>Volume</strong>s Cannot be Associated to an RVGYou cannot associate VxVM ISP volumes of the type stripe-mirror to an RVG.[497136]The vradmin issuesMultiple vradmin commands (304827)If a number of vradmin commands are started at the same time in the background, some of the commands might fail.Incorrect configuration (304859)The vradmin printrvg command does not display an error message to indicate an incorrect configuration when the local_host and remote_hostattributes contain the names of the hosts that are not in the RDS. Invalid license (139302)The vradmin commands that change the configuration may fail before completing if the VVR license has expired. Although an attempt is made to undo the changes, it may not be possible to undo the changes because the license has expired.
Change language