Table of Contents:
I.  Details
II.  Who Is Affected
III.  Identification of the Issue
IV. Solution
V.  Email Notification Service

Details
Data corruption may occur in a file managed by Storage Migrator for Windows 2000/Exchange, versions 3.0, 3.0 SR1 and 3.0 SR2.  If this issue is experienced in your environment, 2 to 19 bytes of a file may be missing on the data store media.  This will not affect all files managed, but may affect a select few, which you can identify using the SQL query in the "Identification" section below.

If this issue occurs in your environment, you may see one of the following three errors:

1.  During the background space management job, the following error will appear:

2.  During a file retrieval job:

3. During a file retrieval job:  

Who Is Affected
This issue affects Storage Migrator for Windows 2000/Exchange, versions 3.0, 3.0 SR1 and 3.0 SR2.   All Media Managers (NetBackup, BackupExec, RSM and all media types including Hard Disk Data Store media) could be affected by this issue.  Media written by releases prior to Storage Migrator for Windows 2000/Exchange version 3.0 are not affected unless the system has been upgraded to version 3.0 and files/attachments have been managed with the version 3.0 software.  Only the files that have been managed/relocated will be affected.


Identification of the Issue
To identify this issue, run the SQL query below.  Another option is to upgrade to Storage Migrator for Windows 2000 4.1 (when available) and run a Verify Data job against the suspected version 3.0 media.

This SQL script can be run through query analyzer, or by using osql.exe from the command prompt on the SQL Server.

PRINT 'Inconsistent Objects'

SELECT RsCartridge.DisplayName [Media Master Name], RsDataSetLocation.ObjectID, RsDataSetSegment.DataSetID, ( RsVolumeInfo.DeviceName + RsVolumeInfo.Name + RsPathInfo.ShortPath + RsDataObject.Name) [Full Path]
FROM  dbo.RsDataSetSegment, RsPathVolume, RsPathInfo,RsDataObject, RsDataSetLocation, RsStream, RsVolumeInfo, RsCartridge
WHERE RsPathVolume.PathSignature = RsPathInfo.PathSignature
   AND RsPathVolume.VolumeID = RsVolumeInfo.VolumeID
   AND RsDataObject.ObjectID = RsDataSetLocation.ObjectID
   AND RsDataObject.ObjectID = RsStream.ObjectID
   AND RsPathVolume.PathVolumeID = RsDataObject.PathVolumeID
   AND RsDataSetLocation.DataSetID = RsDataSetSegment.DataSetID
   AND RsDataSetSegment.CopySetID = RsCartridge.CopySetID
   AND RsStream.Signature = 0
   AND RsStream.StreamSize <> 0
   AND RsCartridge.CopyNumber = 0

select count(*) As [Total Number of Inconsistent Objects]
from RsDataObject, Rsdatasetlocation, rsstream
where rsdatasetlocation.objectid = rsdataobject.objectid
and rsdatasetlocation.objectid = rsstream.objectid
and rsstream.signature = 0
and rsstream.streamsize <> 0

select count(*) AS [Total Number of Objects Checked] from rsstream
---
Note:  To run this using osql.exe, save the query to a file named:  CheckDB.sql
Then use the following syntax to execute the query:

Output from the SQL script should appear as follows:

Inconsistent Objects
Media Master Name  ObjectID      DataSetID       Full Path                  

RS-Hard Drive-1-0     E69BE910-7CD0-4724-B284-EE0C7305A204  80A6581E-D09E-43A9-B3D7-0E2B596825D9                                  \\BDODEV-TST-1\RsFsa\Volume{9454f007-016e-11d7-a9af-00065b871b0d}_G_Data 2\dir2\test881.tst

(1 row affected)
Total Number of Inconsistent Objects  
------------------------------------  
                                   1
(1 row affected)
Total Number of Objects Checked
-------------------------------
                         196779
(1 row affected)

Note:  The Total Number Of Inconsistent Objects would indicate the number of potentially corrupt files.

If files are corrupt and you have either File System Agent (FSA) or Remote Storage for Exchange (RSE) in your environment, see the notes pertaining to each in the "Solution" section below.


Solution
A hot-fix for this issue is available below in the Related Document section (a requirement to apply this hot-fix is to be at 3.0 SR2).

Another solution is to upgrade to Storage Migrator for Windows 2000/Exchange, version 4.0 or 4.0 SR1 to minimize this issue.  Version 4.0 has incorporated code changes to prevent further corruption.

Note:  Upgrading, as suggested above, will prevent any additional data corruption from occurring, but will not correct any corruption that has already been written to the media.


File System Agent (FSA) customers:
If file corruption is identified and the file has been truncated/purged it will be necessary to use the primary backup to restore the original file. If the managed file has been relocated, but not truncated/purged, Storage Migrator 4.0 or 4.0 SR-1 will prevent this file from being truncated/purged, and return the file to an "un-managed" state during the execution of a Background Space Management job.

Remote Storage for Exchange (RSE) customers:
If attachment corruption is identified, it will be necessary to run a mailbox restore from primary backup to recover corrupt attachment. By design, RSE truncates/purges attachments as soon as they are managed/relocated.

If you have not automatically received the TechAlert in regards to this issue via the VERITAS Email Notification Service for Storage Migrator, please navigate to the following URL and sign up:

 http://maillist.support.veritas.com