Check one or more file systems for files with given file status CheckFileStatus and query file stati via configured HSM Module for update.
By configuring HSMModulServicename to Mapped HSMModule (service=FileCopyHSMModule,type=Mapped) the monitored file systems can be of different types (FileBased, Command,..) ]]> org.dcm4chex.archive.hsm.SyncFileStatusService The default constructor SyncFileStatusService NONE = disabled this service.]]> MonitoredFileSystem java.lang.String Module 'dcm4chee.archive:service=FileCopyHSMModule,type=Mapped' can be used if more than one HSM modules are active. ]]> HSMModulServicename java.lang.String MinimumFileAge java.lang.String Checks files with the specified status for status change. Enumerated values: DEFAULT, TO_ARCHIVE, ARCHIVED, QUERY_HSM_FAILED CheckFileStatus java.lang.String If enabled the tar file is verified by
1) checking MD5 sums of the tar content.
2) check if tar file contains the file.
Only applicable if filesystem is a tar filesystem! ]]> VerifyTar boolean Enumerated values: DEFAULT, TO_ARCHIVE, ARCHIVED, QUERY_HSM_FAILED or NONE.
Optionally HSM status can be overwritten by <hsmStatus>=<newStatus>
newStatus can be DEFAULT, TO_ARCHIVE, ARCHIVED, QUERY_HSM_FAILED or DELETE.
Only applicable if VeryfyTar is enabled! ]]> SkipVerifyTarHSMStati java.lang.String Enumerated values: DELETE or DEFAULT, TO_ARCHIVE, ARCHIVED, QUERY_HSM_FAILED, MD5_CHECK_FAILED
DELETE..Delete all file entities related to this invalid tar file.
Only applicable if VerifyTar is enabled. ]]> InvalidTarStatus java.lang.String Enumerated values: DELETE or DEFAULT, TO_ARCHIVE, ARCHIVED, QUERY_HSM_FAILED
DELETE..Delete such invalid file entities. Only applicable if VerifyTar is enabled. ]]> NotInTarStatus java.lang.String Format:
interval!from-to or NEVER
interval = ##m (in minutes), ##h (in hours).
from = start hour (0-23) when no file status check should be performed
to = end hour (0-23) when no file status check should be performed
NEVER = disable file status checking
Example:
1h!9-17 means every hour, synchronize file status, except between the hours of 9:00am and 5:00pm. By setting this type of TaskInterval, you can perform file status synchronisation outside of peak hours. ]]> TaskInterval java.lang.String Creation Date of oldest file on configured filesystem with file status of configured CheckFileStatus. OldestCreatedTimeOfCheckFileStatus java.lang.String Maximum number of files which are checked for status change in one task. NumberOfFilesPerTask int Current state if syncFileStatus task is running. Used to avoid concurrency! isRunning boolean Used internally. Do NOT modify. TimerIDCheckSyncFileStatus java.lang.String Used internally. Do NOT modify. TarRetrieverName javax.management.ObjectName Used internally. Do NOT modify. SchedulerServiceName javax.management.ObjectName &defaultAttributes; &defaultOperations; Return number of updated files or -1 if check is already running (Timer). ]]> check int updateOldestCreatedTimeOfCheckFileStatus void This can be used to update instances that are already copied with a version prior to 2.16.0. ]]> syncArchivedStatusOfInstances File System ID where files must have file status ARCHIVED. fsID java.lang.String limit java.lang.String int