HP StoreAll Storage - Manual (Page 242)

Description Parameter
A file’s state can be changed to WORM only once. A file in WORM or
retained state cannot be reverted to non-WORM, and cannot be un-retained
through the StoreAll REST API. See the ibrix_reten_adm command or
the equivalent Management Console actions for administrative override
methods to un-retain a file.
Example: Set a file to WORM without specifying retention expiration
curl -g -X PUT
"https://99.226.50.92/ibrix_share1/lab/images/xyz.jpg?assign=system::worm='true'"
In this example, no retention expiration date/time is provided, but the file state is changed to
WORM.
As part of processing this command, the file may also be set to the retained state. This will occur
if the atime has already been set into the future, or if the file system’s default retention period is
non-zero. The retention expiration time will be set to the atime (if in the future) or the default.
Example: Set a file to WORM and retained with a retention expiration date/time
curl -g -X PUT
"https://99.226.50.92/ibrix_share1/lab/images/xyz.jpg?assign=system::retentionExpirationTime=
1376356584,system::worm='true'"
In this example, the file state is changed to WORM and retained. The retention expiration date/time
is set to 13 Aug 2013 01:16:24. The file system default retention period is ignored.
Example: Set/change the retention expiration date/time without a WORM state transition
curl -g -X PUT
"https://99.226.50.92/ibrix_share1/lab/images/xyz.jpg?assign=system::retentionExpiration
Time=1376356584"
In this example, a file’s retention expiration date/time is assigned, but no state transition to WORM
is performed.
If the file is not already retained, the atime is assigned this value, and it remains un-retained. But
the value will take effect if the file is ever transitioned to WORM in the future, either manually or
by autocommit. If the file is already retained, the retention expiration date/time will be changed
to this new value. If retention settings prohibit this, an error is returned.
HTTP Status Codes
The following HTTP status codes can be returned by the StoreAll REST API. For error status codes,
check the following files for further information about the error:
•
access_log
•
error_log
The logs are in the following directory, on the Active FM server node of the cluster:
/usr/local/ibrix/httpd/debug/logs
By default, there is no activity written to the access_log file. To enable the HTTP Server to write
entries to the file for every HTTP access from a client, uncomment this line in the file /usr/local/
ibrix/httpd/conf/httpd.conf
:
# CustomLog "debug/logs/access_log" common
242 HTTP-REST API file-compatible mode shares