Managing Service Tasks
Service tasks are background tasks performed by the RamSoft Tasks Service. Although the user has the option to disable these tasks, allowing them to run during off hours is strongly recommended. These task organize the image data and provide optimal performance of the database.
There are several service tasks which are performed by RamSoft software. While these task can be turned off/ on through the main software itself (Settings > Server Settings > Service Task), some of their options are controlled by the Maintenance module.
These tasks are :
| Task | Description |
|---|---|
| DB Sweep | The DB Sweep task optimizes database indexes and removes references to deleted entries. Running it periodically keeps the database performance optimized and also helps keep the DB error free. Once the system reaches the pre-defined pending transaction counts, i.e, if the "Transaction Differences to Run DB Sweep" registry value count in PACS Server is greater than 250000 (the default allowed value), system will force a DB Sweep task followed with an email alerting the users of the transaction ID usage. This email is triggered by the registry value "Transaction Differences to Send Alerts" in the PACS> Server. The "Force Run DB Sweep Time Interval (mins)" value in registry is used to specify the time interval used to check the current transaction count difference. Sometimes a DB Sweep operation is forced to run when lot of changes have been detected and in this case the user is not alerted. |
| DB Backup | The DB Backup task creates a set of database backup files (.GBK files). These files are used to restore the database in case of a crash or corruption. This task should be configured to run daily to maintain the best possible disaster recovery resources. The DB Backup task creates one backup file on each day of the week that it is executed, for a total of eight backup files named pacs0.gbk - pacs7.gbk. The DB Backup Setup and other Database functions are explained in detail in the How Do I Setup The Database? section. |
| Auto Delete | This task has been eliminated by Auto Purging. For further information, please refer to the How Do I Configure Rule based Purging? section of the manual. |
| Backup Log | The Backup Log task extracts any entries in the System, Communication, HL7, Transmit and Request logs and exports them to CSV (comma separated values) files. Once exported, the entries are then deleted from the database. The backup log task uses a path and time set by the administrator, through the Maintenance module, to specify the location of stored CSV files and the time when the task will be run. The CSV files can be viewed and searched by opening them in a program which recognizes the CSV format, such as Microsoft Excel. |
| Auto Compression | The Auto Compression task compresses image data at a specific lossy ratio in JPEG2000 based on user-defined rules. After establishing the rules in the Maintenance module, the user can expect object files of matching studies to be reduced in sizes. The process of establishing these compression rules is explained in detail in the How Do I Configure Rule Based Compression? section. |
| Auto Purge | The Auto Purge task deletes study objects based on user-defined rules. After establishing the rules in the Maintenance module, the system will purge the studies matching the criteria. If the task has not been defined, then Auto Delete task will purge DICOM objects when the server's storage is full. The process of creating rules for this purge is explained in the How Do I Configure Rule Based Purging? section in detail. |