HP File System Extender (FSE) manual Release, Trigger-deletion

2.6 NAME 45

–file is present on the HSM file system but had not been recognized by the FSE implementation for some reason. Adding it to the migration candidate list with this command preserves its attributes;

–the file is already migrated to an FSE medium that has its current status set to UNRELIABLE or it is obviously worn out. In these cases the file can be re–migrated to another FSE medium.

Note:

If specified file is already migrating or present on the release candidate list it cannot be added to the migration candidate list.

•–S ,– –release

Unconditionally release files, specified by the FileName... argument. All files must be located on the same HSM file system. The purpose of this operation is to gain free space on an HSM file system by releasing (large) files from it. The files released this way must be on the release candidate list. For details on the unconditional release process, see the FSE user guide.

•–T ,– –trigger–migration

Trigger migration job for files that are currently present on the migration candidate list on FSE partition PartitionName.

Trigger migration job for files that were not migrated because migration of those files failed.

•–D ,– –trigger–deletion

Trigger deletion of files on an HSM file system, which correspond to the deletion policy defined for the belonging FSE partition. The deletion pol- icy consists of a sequence of FileExpiration – Path parameter pairs that are specified in the FSE partition configuration file. Although the deletion re- moves the corresponding files from the HSM file system, their migrated generations still exist on FSE media, unless the media reorganization with appropriate parameters has been run on the media that hold the migrated copies. If this is not the case, these migrated generations can still be re- called. For more information on configuring the deletion policy, see the FSE user guide.

•–F ,– –force

HP StorageWorks File System Extender Software CLI reference