Hotfix 36: NTFS sparse use in Server Space Management Job reworked

Article:TECH39604  |  Created: 2008-03-11  |  Updated: 2008-06-10  |  Article URL http://www.symantec.com/docs/TECH39604
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Issue



Space Usage Calculation on the Storage Management and on the operating system do not match in spite of successful Server Space Management (SSM) Job.


Environment



Recovery Solution 6.2.2332 (SP1)

Cause



Currently, our design assumes that sparsing works perfectly and when the Recovery Solution Server communicates to the file system that some of the blocks are no longer required, and the UsedSpace is updated immediately. In fact, some of the setups have different cluster block size (like 64 KB) that affects the ability of sparsing to process small data chunks. As a result:

  • Recovery Server did not respect storage limits that are set in the Console.
  • Recovery Server tried to write to a storage when the storage is already full.

Solution



Note: This hotfix is a cumulative hotfix which includes Hotfix 30 and Hotfix 28 for Recovery Solution 6.2.2332.

NTFS sparsing use in Server Space Management (SSM) has been completely reworked and this HotFix is in the form of the following SQL Stored Procedures:

  • DeleteRawVolumeGroup.sql
  • FinishBlobSync.sql
  • GetAllBlobFileNames.sql
  • GetUnsyncFileBlocks.sql
  • MarkBlobFileFull.sql
  • RemoveUnsyncFileBlocks.sql
  • SetBlobFileState.sql

And the following binaries:

  • DSFile.dll
  • DSRawData.dll
  • ServerJobs.dll

The HotFix can be applied in the following way:

  1. Stop the Recovery Solution Server Service.
  2. Browse to the %Program Files%\Altiris\Recovery Solution\Server folder.
  3. Replace the DSFile.dll, DSRawData.dll and ServerJobs.dll with the new ones from attachments.
  4. Load each SQL Stored Procedure to SQL Query Analyzer (SQL 2000 Server) or SQL Server Management Studio (SQL 2005 Server) and execute them against the AeXRSDatabase (default name of Recovery Solution Database).
  5. Start the Recovery Solution Server service.
  6. To force Server Space Management job for setting sparse blocks correctly for the old BLOBs, use the following script which will do a bitwise 'or' on the current value and 32 (note: this often does not make the state value 32):
    update DiskFileVolume set State = State | 32
  7. Start Server Space Management Job.

Attachments

Binaries.zip (1.1 MBytes)
StoredProcedures.zip (7 kBytes)


Supplemental Materials

SourceDEFECT
ValueTLN 24934
DescriptionLogged in tlndev (Altiris - Talinn) database

Legacy ID



40850


Article URL http://www.symantec.com/docs/TECH39604


Terms of use for this information are found in Legal Notices