When creating a mirrored volume or when performing a 'Snap Back' operation, the process fails with Event ID 10251or Event ID 799 in Storage Foundation for Windows (SFW) 5.1. SFW specific logs also report error e51500d3.
When creating a mirrored volume or when performing a 'Snap Back' operation using FlashSnap, the process fails during the resynchronization of the volumes with Event ID 10251. This issue can also be seen during a mirror reattach operation in cases where a mirrored plex has to be reactivated/resynchronized due to a degraded disk. This specific attach/reattach issue is only seen in the SFW 5.1 version of the product.
When this issue occurs, the following errors are recorded:
Application Event Log:
ERROR 10251(0xe515280b) VxSvc_vxvm <Server_Name> Resynchronization for \Device\HarddiskDmVolumes\<DG_Name>\<Volume_Name> failed to complete.
vxvm - OnTaskFinish - task finished with error : e51500d3
In addition to the errors above, the following errors may be seen depending on the specific 'mirror attach' operation being performed on the server (i.e. 'Mirror Create' or 'Snap Back').
Mirror Attach / Snap Prepare:
This operation is performed when creating a new mirrored volume or when adding a mirror to an existing volume. This is also seen when creating an initial Snap Shot set using the FlashSnap option. In addition to the errors provided above, the following event will also be logged to the Application Event log:
ERROR 799 (0xe515031f) VxSvc_vxvm <Server_Name> Failed to attach a mirror to volume \Device\HarddiskDmVolumes\<DG_Name>\<Volume_Name>
Snap Back Operation:
This is used with the FlashSnap option in SFW. This operation is performed when a snap volume that is in a snapped state is reattached to the original volume and a resynchronization process is performed. Note: This is also called a 'reattach' operation when using the vxsnap command line utility for VSS supported volumes (i.e. Microsoft Exchange and Microsoft SQL).
In addition to the errors shown at the beginning of this document, the following errors will also be recorded in the %VMPATH%\logs\vxsnap.log file when the Snap Back operation is being performed:
VxSnap ResynchComponentVolumes() Failed with error (e51500d3)
VxSnap ResynchComponentVolumes() returning code (e51500d3)
This issue is caused by a problem that has been found in the SmartMove feature of SFW. SmartMove helps reduce the resynchronization time for mirror operations and subdisk moves. It accomplishes this by using NTFS file system metadata to determine all populated regions of a disk, and only synchronizing these regions. This avoids SFW having to replicate empty (blank) space on a volume that is not being used.
The SmartMove operation is enabled by default. To determine if this is enabled on a server, open the Veritas Enterprise Administrator (VEA) and navigate to the following location:
'Control Panel' > StorageAgent > System Settings > Smart Move (See Figure 1 below):
A workaround for this issue is to disable the SmartMove option. This will increase the resynch operation time (especially on volumes with a lot of empty space), but will allow the attach operation to complete successfully.
The source of this issue has been identified and a private fix is available and can be downloaded below. Instructions for the installation can be found in the README file included in the download and these installation instructions have also been provided below:
Files included in this Private Fix:
|File||Windows 2003 32bit||Windows 2003 64bit||Windows 2008 32bit||Windows 2008 64bit|
|832,512 bytes||832,512 bytes||846,848 bytes||846,848 bytes|
This Fix has been updated and the newer version of vxconfig.dll is available with the following download :