JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Storage Archive Manager 5.3 Configuration and Administration Guide     Sun QFS and Sun Storage Archive Manager 5.3 Information Library
search filter icon
search icon

Document Information

Preface

1.  About SAM-QFS

2.  Configuring Storage Devices for Archiving

3.  Performing Additional SAM-QFS Configuration

4.  Creating Parameters Files for Network-Attached Automated Libraries

5.  Checking the Drive Order in Libraries

6.  Populating the Catalog

7.  Managing Automated Libraries and Manually Loaded Drives

8.  Managing Vendor-Specific Libraries

9.  About Archiving

Planning Archiving Operations

Preview Queue

Archiver Daemons

Archiving Operations

Step 1: Identifying Files to Archive

Continuous Archiving

Scanned Archiving

Step 2: Composing Archive Requests

Step 3: Scheduling Archive Requests

Drive Usage

Volume Usage

Step 4: Archiving the Files in an Archive Request

Sample Default Output From the archiver -l Command

Log Files and Event Logging for Archive Operations

Data Verification

10.  Configuring the Archiver

11.  Archive Directives (archiver.cmd)

12.  Archive Set Directives (archiver.cmd)

13.  Data Integrity Validation in SAM-QFS

14.  About Releasing

15.  Configuring the Stager

16.  Configuring the Recycler

17.  Advanced SAM-QFS Topics

18.  Using the Sun SAM-Remote Software

Data Verification

You can enable data verification for archive copies. This feature checks for data corruption on any data that is copied to secondary and/or tertiary media.

The data verification process performs a read-after-write verification test and records a confirmation of data validity in the metadata properties for that file. The process uses the ssum option to mark files and directories to be verified. The normal checksum method is employed to verify copies written to tape or disk archive.

Use the ssum -e command to set data verification for a file or directory. A child directory inherits the data verification properties of its parent. This command forces the generation and use of checksums for archiving and staging. It also prevents the release of the file until all archive copies have been created and their checksums verified. Only superuser can set this attribute on a file or directory.


Note - Data verification places an additional burden on stager resources because data verification requests are placed on the stager queue in addition to normal stage requests. Data verification also leads to additional tape mounts and therefore affects archiver and stager performance. Because a file cannot be released until all archive copies are made, using data verification might also require additional disk cache.