6.5 HP StoreAll OS CLI Reference Guide
Table Of Contents
- HP StoreAll OS CLI Reference Guide
- Contents
- 1 General CLI information
- 2 StoreAll commands
- ibrix_activedirectory
- ibrix_archiving
- ibrix_audit_reports
- ibrix_auth
- ibrix_av
- ibrix_avconfig
- ibrix_avquarantine
- ibrix_avscan
- ibrix_caseinsensitive
- ibrix_certificate
- ibrix_chassis
- ibrix_cifs
- ibrix_cifsconfig
- ibrix_cifsmonitor
- ibrix_cifsperms
- ibrix_client
- ibrix_cluster
- ibrix_clusterconfig
- ibrix_collect
- ibrix_crr
- ibrix_crreq
- ibrix_crr_export
- ibrix_crrhealth
- ibrix_crr_nic
- ibrix_datavalidation
- ibrix_dbck
- ibrix_df
- ibrix_edquota
- ibrix_evacuate
- ibrix_event
- ibrix_exportfs
- ibrix_fm
- ibrix_fm_tune
- ibrix_fs
- Description
- Synopsis
- Create a file system
- View information about file systems
- Extend a file system
- Audit log expiration policy
- Archiving/auditing synchronizer (Retention Expiration and Autocommit)
- Delete a file system
- Migrate segment ownership
- Enable or disable quotas
- Enable, disable, or display Express Query and auditing settings
- Mark a bad segment
- Enable or disable Export Control
- Assign or delete a standby server for the specified segments
- Options
- See also
- ibrix_fs_ops
- ibrix_fs_tune
- ibrix_fsck
- ibrix_ftpconfig
- ibrix_ftpshare
- ibrix_haconfig
- ibrix_hba
- ibrix_health
- ibrix_healthconfig
- ibrix_host_tune
- ibrix_hostgroup
- ibrix_hostpower
- ibrix_httpconfig
- ibrix_httpshare
- ibrix_httpvhost
- ibrix_idmapping
- ibrix_ldapconfig
- ibrix_ldapidmapping
- ibrix_license
- ibrix_localgroups
- ibrix_localusers
- ibrix_lookup
- ibrix_lv
- ibrix_lwhost
- ibrix_lwmount
- ibrix_lwumount
- ibrix_migrator
- ibrix_mount
- ibrix_mountpoint
- ibrix_ndmpconfig
- ibrix_ndmpsession
- ibrix_nic
- ibrix_objectstore
- ibrix_objectstoreadmin
- ibrix_objectstoremonitor
- ibrix_onlinequotacheck
- ibrix_phonehome
- ibrix_powersrc
- ibrix_profile
- ibrix_pv
- ibrix_rebalance
- ibrix_reports
- ibrix_reten_adm
- ibrix_server
- ibrix_snap
- ibrix_snapreclamation
- ibrix_snmpagent
- ibrix_snmpgroup
- ibrix_snmptrap
- ibrix_snmpuser
- ibrix_snmpview
- ibrix_stats
- ibrix_tape
- ibrix_task
- ibrix_tier
- ibrix_top
- ibrix_umount
- ibrix_usernamemapping
- ibrix_version
- ibrix_vg
- ibrix_vs
- ibrix_vs_snap
- ibrix_vs_snap_strategy
- MDexport
- MDimport
- upgrade60.sh
- verify_client_update
- 3 Support and other resources
- 4 Documentation feedback
- Glossary
- Index
ibrix_reten_adm
The ibrix_reten_adm command does the following:
• Manages retained and WORM files in a file system or directory enabled for data retention.
• Enables data retention features for file systems created with StoreAll version 6.0 or earlier.
IMPORTANT: Do not use the ibrix_reten_adm command on a post-6.1.1 file system that is
not enabled for data retention, except in the case of upgrading a pre-6.1.1 file system as described
in Upgrade a pre–6.1.1 file system for data retention features: (page 177).
Description
Use the ibrix_reten_adm command to manipulate WORM and retained files. You can perform
the following tasks:
• Add or remove a legal hold on a WORM or retained file. While the hold is in effect, the file
cannot be deleted, even if the expiration period has expired.
• Reset the expiration time for a file, in effect increasing or decreasing the expiration period.
• Remove the retention period for retained files.
• Delete retained files administratively, regardless of whether the retention period has expired.
• List the retention attributes for files in the file system.
• Upgrade a file system created with StoreAll version 6.0 or earlier to enable data retention
features.
NOTE: A file system or directory enabled for data retention can contain normal files. These files
are created read-only or read-write, and can be modified or deleted at any time. A checksum is
not calculated for normal files and they are not managed by data retention.
Specifying path lists
In the commands, the -P PATHLIST option specifies the files that are to be affected by the
command. The following rules apply when specifying path lists:
• A path list can contain one or more entries, separated by commas.
• Each entry can be a fully-qualified path, such as /myfs1/here/a.txt. An entry can also
be relative to the file system mount point. For example, if myfs1 is mounted at /myfs1, the
path here/a.txt is a valid entry.
• A relative path cannot begin with a slash (/). Relative paths are always relative to the mount
point; they cannot be relative to the user’s current directory, unlike other UNIX commands.
• A directory cannot be specified in a path list. Directories themselves have no retention settings,
and the command returns an error message if a directory is entered.
To apply an action to all files in a directory, you need to specify the paths to the files. You can use
wildcards in the pathnames, such as /my/path/*,/my/path/.??*. The command does not
apply the action recursively; you need to enter subdirectories.
To apply a command to all files in all subdirectories of the tree, you can wrap the
ibrix_reten_adm command in a find script (or other similar script) that calls the command
for every directory in the tree. For example, the following command sets a legal hold on all files
in the specified directory:
find /ibrixFS/mydir -type d -exec ibrix_reten_adm -h -f ibrixFS -P {}/*
\;
176 StoreAll commands