Veritas Storage Foundation Release Notes
Veritas Storage Foundation⢠Release Notes: HP-UX - Symantec
Veritas Storage Foundation⢠Release Notes: HP-UX - Symantec
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Storage</strong> <strong>Foundation</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
65<br />
3 Stop the affected RVG. Enter the following:<br />
# vxrvg -g diskgroup stop rvg<br />
4 Disassociate the volumes from the RVG. Enter the following:<br />
# vxvol -g diskgroup dis vol<br />
5 Resize the volumes. In this example, the volume is increased to 10 GB. Enter<br />
the following:<br />
# vxassist -g diskgroup growto vol 10G<br />
6 Associate the data volumes to the RVG. Enter the following:<br />
# vxvol -g diskgroup assoc rvg vol<br />
7 Start the RVG. Enter the following:<br />
# vxrvg -g diskgroup start rvg<br />
8 Resume or start the applications.<br />
Creating a primary diskgroup fails if there is no extra LUN to<br />
mirror the data change map (2478684)<br />
Creating a primary diskgroup fails if there is no extra LUN to mirror the data<br />
change map (DCM), even if you have enough disk space.<br />
Workaround: Add a LUN to the diskgroup before creating the primary diskgroup.<br />
verifydata operation fails when replicating between versions<br />
5.1 and 6.0 (2360713)<br />
When replicating in a cross-version VVR environment consisting of hosts running<br />
<strong>Storage</strong> <strong>Foundation</strong> 5.1 and hosts running <strong>Storage</strong> <strong>Foundation</strong> 6.0, the vradmin<br />
verifydata command fails with the following error:<br />
VxVM VVR vxrsync ERROR V-5-52-2222 [from host]: VxVM in.vxrsyncd<br />
ERROR V-5-36-2125 Server volume access error during [assign volids]<br />
volume path: [/dev/vx/dsk/dg/snapshot_volume] reason: [this could be<br />
because a target volume is disabled or an rlink associated with a<br />
target volume is not detached during sync operation].<br />
Workaround: There are two workarounds for this issue.