Retention properties assignment – HP StoreAll Storage User Manual
Page 240
Get all files that match a name pattern
The following is one command line:
curl -g "http://99.226.50.92/ibrix_share1/lab/images?query=
nl
system::path~'.*\.(gif|jpg)$'"
This example returns a JSON document that contains all files in the lab/images directory that
end in .gif or .jpg.
Get all activity-related times for files with recent activity
The following is one command line:
curl -i "http://99.226.50.92/ibrix_share1/?attributes=system::createTime,
system::lastChangedTime,system::lastModifiedTime,system::lastPathChangedTime,
system::deleteTime&query=system::lastActivityTime>1334642962&freshness&bypoid"
This example returns a JSON document keyed by poid field that contains all files in the lab/images
directory that have experienced activity since April 17, 2012, 06:09:22 UTC/GMT. For live files,
the following attributes are returned: system::createTime, system::lastChangedTime,
system::lastModifiedTime
and system::lastPathChangedTime. For deleted files,
system::deleteTime
is returned.
The attribute freshness returns the last date which Express Query has been ingested into the
database. The attribute bypoid has to be used always system::deleteTime is referred in the
request. See
.
Retention properties assignment
Retention and WORM support was initially implemented in StoreAll v6.0 following an atime-based
retention date interface, to be compatible with existing products that implement retention this way.
This feature is independent of the StoreAll REST API.
Briefly, without the API, the sequence of events is:
1.
A user creates or uploads a file to a StoreAll file system.
2.
If the autocommit feature is enabled, the file becomes WORM after a certain period of inactivity.
If a non-zero default retention period is defined for the file system, then the file is also set to
the retained state for that period of time, at the same time it becomes WORM.
3.
If no autocommit, the user sets the last access time (atime) to the desired retention expiration
date/time (or skips this step if a non-zero default retention period is defined for the file system
and the user does not want to override that period).
4.
If no autocommit, after setting the atime, the user turns off all write permission bits on the file.
This triggers the file’s state transition to WORM, and also to retained if the atime is in the
future or if there is a non-zero default retention period.
5.
Later, the user can change the atime to change the expiration time, subject to the file system’s
retention policy settings.
The StoreAll REST API commands provide the same ability to perform these actions, but in fewer
steps.
240 HTTP-REST API file-compatible mode shares