17.08.2015 Views

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec

Veritas Storage Foundation™ and High ... - SORT - Symantec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

74About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues5 Relayout the volumes to striped-mirror. Enter the following:# vxassist -g diskgroup relayout vol layout=stripe-mirror6 Associate the data volumes to the RVG. Enter the following:# vxvol -g diskgroup assoc rvg vol7 Start the RVG. Enter the following:# vxrvg -g diskgroup start rvg8 Resume or start the applications.Creating a primary diskgroup fails if there is no extra LUN to mirror thedata change map (2478684)Creating a primary diskgroup fails if there is no extra LUN to mirror the datachange map (DCM), even if you have enough disk space.Workaround:Add a LUN to the diskgroup before creating the primary diskgroup.vradmin verifydata operation fails when replicating between versions 5.1<strong>and</strong> 6.0 (2360713)When replicating in a cross-version VVR environment consisting of hosts running<strong>Storage</strong> <strong>Foundation</strong> 5.1 <strong>and</strong> hosts running <strong>Storage</strong> <strong>Foundation</strong> 6.0, the vradminverifydata comm<strong>and</strong> fails with the following error:VxVM VVR vxrsync ERROR V-5-52-2222 [from host]: VxVM in.vxrsyncdERROR V-5-36-2125 Server volume access error during [assign volids]volume path: [/dev/vx/dsk/dg/snapshot_volume] reason: [this could bebecause a target volume is disabled or an rlink associated with atarget volume is not detached during sync operation].Workaround:There are two workarounds for this issue.■■Upgrade the hosts running <strong>Storage</strong> <strong>Foundation</strong> 5.1 to <strong>Storage</strong> <strong>Foundation</strong>5.1SP1 or later <strong>and</strong> re-run the vradmin verifydata comm<strong>and</strong>.Follow the offline verification procedure in the "Verifying the data on theSecondary" section of the <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong><strong>Solutions</strong> Replication Administrator's Guide. This process requires ensuringthat the secondary is up-to-date, pausing replication, <strong>and</strong> running the vradminsyncrvg comm<strong>and</strong> with the -verify option.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!