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.
68<br />
<strong>Storage</strong> <strong>Foundation</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
Workaround<br />
Provide the name of a host that has the repository database, with the -r option<br />
of vxsfadm.<br />
FlashSnap validate reports snapshot unsplittable (2534422)<br />
The FlashSnap validation operation fails with the following error if the mirrors<br />
for data volumes and archive log volumes share the same set of disks:<br />
SFAE Error:0642: <strong>Storage</strong> for diskgroup oradatadg is not splittable.<br />
Workaround<br />
Ensure that snapshot plexes for data volumes and snapshot plexes for archive<br />
log volumes reside on separate set of disks.<br />
Attempt to use SmartTier commands fails (2332973)<br />
The attempts to run SmartTier commands such as dbdst_preset_policy<br />
ordbdst_file_move fail with the following error:<br />
fsppadm: ERROR: V-3-26551: VxFS failure on low level mechanism<br />
with message - Device or resource busy<br />
This error occurs if a sub-file SmartTier command such as dbdst_obj_move has<br />
been previously run on the file system.<br />
There is no workaround for this issue. You cannot use file-based SmartTier and<br />
sub-file SmartTier simultaneously.<br />
dbed_vmclonedb ignores new clone SID value after cloning<br />
once (2580318)<br />
After you have done FlashSnap cloning using a snapplan, any further attempts<br />
to create a clone from the same snapplan using the dbed_vmclonedb continue to<br />
use the original clone SID, rather than the new SID specified using the new_sid<br />
parameter.<br />
This issue is also observed when you resynchronize the snapplan, take a snapshot<br />
again without specifying the new clone SID, and then try to clone with the new<br />
SID.<br />
Workaround<br />
You can use one of the following workarounds:
Change language