You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Overview
- Images are sent to dcm4chee
- images are stored in /archive (status is DEFAULT - 0)
- FileCopyService creates a tar archive and copies it into
/hsm folder (it creates new file entries in DB with status TO_ARCHIVE - 1). The status to be used is set in FileStatus config parameter. At this stage for each file you will see two entries in DB: one will have it's file_path something like 2007/3/6/18/F14966A3/92C7AD0D/92C7AFB7 and another - <SOME_PATH>.tar!<PATH_TO_FILE_IN_TAR>. Don't forget to add "tar:" prefix to your destination file system (tar:/hsm) in FileCopyService, otherwise files won't be packed into a tar file.
- HSM software migrates it to tape (or whatever you have it set up to do).
- At this stage SyncFileStatus comes into play. It checks files in your original filesystem (
/archive) querying HSM and marks them as ARCHIVED - 2, if it was successful. Query is done using "Command" parameter in the SyncFileStatus configuration and checking the result against the regular expression given in "Pattern" field of the SyncFileStatus configuration. It is environment specific and you'll have to change them according the tools you use for HSM.
- FileSytemMgt service checks file system using intervals from it's configuration and deletes files depending on rules you showed in the configuration. In your case you'll need to change DeleteLocalStudiesCopyAvailable to "true", ValidFileStatus to "ARCHIVED" and study age for deletion in StudyAgeForDeletion to something like "52w" (means 52 weeks, you can use h - hours, d - days as well). It checks all files older than the given age and if it can find a copy entry in DB with the status ARCHIVED then it deletes the original file and deletes the DB entry for the original file. At this stage in DB you'll have only one entry for the file with file_path something like
<SOME_PATH>.tar!<PATH_TO_FILE_IN_TAR>
- Then QueryRetrieveScpService will use TarRetriever to retrieve files on demand. TarRetriever uses TarFetchCommand config parameter to retrieve files from an external system (tapes), but, I guess, in your case your HSM agent will retrieve tar-files when TarRetriever tries to access them. If so, then leave TarFetchCommand as NONE.
- FileCopyService reschedules copy orders if they fail, you can change the rescheduling rule in RetryIntervals config parameter.
Configuration
HSM Service Configuration