User's Manual

124 Migration, release, recall, and deletion
Windows specific
This deletion policy will have the following effect:
• All files in the directories \Months\Current and "\Arch\June 2005" on the owning HSM file
system are to be considered for deletion as soon as one month has passed since they were last
changed.
• All files in the directories \Weeks\Current and "\Arch\Week 24" are to be considered for
deletion as soon as seven days have passed since they were last changed.
Default deletion policy
By default, deletion policy is not configured.
Part of the FSE partition configuration template that includes the disabled deletion policy parameters is
depicted in ”Template for FSE partitions - Deletion part” on page 252.
Starting the deletion job
You start a deletion job by running the following command on the FSE client:
Before running the command, ensure that the HSM file system of the selected FSE partition is mounted.
By default, fsefile requires confirmation before starting the deletion process. You can suppress the
confirmation request by specifying the --force option. This is particularly useful when using the
command within scripts.
During execution of the deletion job, fsefile reports the job execution progress to the standard output,
allowing you to monitor the deletion process in the command shell. You can disable monitoring (force
fsefile to return to the command prompt immediately) by specifying the --no-monitor option.
NOTE: If two consecutive deletion jobs using the same deletion policy are started on the same HSM file
system in a short period of time, the files that were deleted by the first job may show up as still present on
the HSM file system during the execution of the second job. This happens if the deletions had not yet been
“migrated” to FSE media by the time the second job was started. In this case, the second deletion job does
not perform any operation on these files, but returns an error for the files that have already been deleted.
If the HSM file system on which the deletion job is running is unmounted during the job, the job is aborted.
To complete the deletion process, you need to restart it from the beginning.
For more information on fsefile, see the FSE Command-Line Reference.
Recalling deleted files
Files deleted from an HSM file system can still be recreated using FSE’s “recall by file ID” functionality. File
IDs are stored in the File System Catalog (FSC) and can be retrieved with the fsefile --history
command. To recall deleted files using their file IDs, run fsefile --recall on the FSE client. You must
run the command separately for each deleted file.
[Delete]
FileExpiration "1M"
{
Path = (\Months\Current, "\Arch\June 2005")
}
FileExpiration "7D"
{
Path = (\Weeks\Current, "\Arch\Week 24")
}
fsefile --trigger-deletion PartitionName [--force] [--no-monitor]