Table of ContentsView in Frames

Determining the WORM status of a file

You can check whether the files placed in a SnapLock volume are committed to the WORM state by using the file fingerprint command. If a file is transitioned from a writable state to a read-only state in a SnapLock volume, the file is in the WORM state.

Step

  1. You can check the WORM state by using the fingerprint of the file:file fingerprint -x pathname
    A file has WORM protection if the file-type is worm and the volume is a SnapLock volume. The file's expiry date is present in the retention-time and formatted-retention-time fields. You should check this date against the volume ComplianceClock time (specified in the snaplock-volume-compliance-clock and formatted-snaplock-volume-compliance-clock fields) to determine whether the file has expired.

Examples of file committed to WORM state by using the file fingerprint command

The following example shows a file with read-only permission with the file-type changed to worm:
file fingerprint -x /vol/test_slc_vol/sample_file.0

<fingerprint><fingerprint-info><fingerprint-algorithm>sha-256</fingerprint-algorithm><fingerprint-start-time>1306404712</fingerprint-start-time><formatted-fingerprint-start-time>Thu May 26 10:11:52 GMT 2011</formatted-fingerprint-start-time><fingerprint-scope>data_and_metadata</fingerprint-scope><fingerprint-version>2</fingerprint-version><fingerprint-input-path>/vol/test_slc_vol/sample_file.0</fingerprint-input-path><filer-id>118069060</filer-id><filer-name>f3070-230-70</filer-name><snaplock-license>compliance and enterprise</snaplock-license><snaplock-system-compliance-clock>1306404710</snaplock-system-compliance-clock><formatted-snaplock-system-compliance-clock>Thu May 26 10:11:50 GMT 2011</formatted-snaplock-system-compliance-clock><volume-name>test_slc_vol</volume-name><volume-uuid>43cf0d50-8780-11e0-a7ee-123478563412</volume-uuid><volume-type>flexible</volume-type><volume-containing-aggregate>slc</volume-containing-aggregate><aggregate-uuid>a235e9e7-8531-11e0-a7ee-123478563412</aggregate-uuid><volume-snaplock-type>compliance</volume-snaplock-type><snaplock-volume-compliance-clock>1306404710</snaplock-volume-compliance-clock><formatted-snaplock-volume-compliance-clock>Thu May 26 10:11:50 GMT 2011</formatted-snaplock-volume-compliance-clock><volume-expiry-date>1306491101</volume-expiry-date><is-volume-expiry-date-wraparound>false</is-volume-expiry-date-wraparound><formatted-volume-expiry-date>Fri May 27 10:11:41 GMT 2011</formatted-volume-expiry-date><metadata-files><file-fingerprint-info><path>/vol/test_slc_vol/sample_file.0</path><fsid>773461395</fsid><fileid>96</fileid><file-type>worm</file-type><file-size>2048</file-size><creation-time>1306404660</creation-time><formatted-creation-time>Thu May 26 10:11:00 GMT 2011</formatted-creation-time><modified-time>1306404660</modified-time><formatted-modified-time>Thu May 26 10:11:00 GMT 2011</formatted-modified-time><changed-time>1306404701</changed-time><is-changed-time-wraparound>false</is-changed-time-wraparound><formatted-changed-time>Thu May 26 10:11:41 GMT 2011</formatted-changed-time><retention-time>1306491101</retention-time><is-wraparound>false</is-wraparound><formatted-retention-time>Fri May 27 10:11:41 GMT 2011</formatted-retention-time><owner-id>0</owner-id><group-id>0</group-id><data-fingerprint>5aAKqZkayKXuMQmETYSlVYO9IFcq0//NQnkvPDaxg60=</data-fingerprint><metadata-fingerprint>aUe0DQjT73ncAwp9tWP+XdvgaU6mMJcnzsSlF5zb9CA=</metadata-fingerprint></file-fingerprint-info></metadata-files><fingerprint-end-time>1306404712</fingerprint-end-time><formatted-fingerprint-end-time>Thu May 26 10:11:52 GMT 2011</formatted-fingerprint-end-time></fingerprint-info></fingerprint>