Additional configuration options of HSM in Configuration tool described in this chapter are optional. However, they provide administrator with diagnostic, encryption, pack and async task possibilities on the following tabs:
This tab is used to configure the more advanced settings of HSM as single instancing, cache settings and temporary folder. After configuring all options press the Apply button.
Duplicate files detection
Since the HSM system includes the Duplicate Files Detection service, it means that identical files are stored only once. In the Duplicate files detection section you may specify the detection method:
a)Select the Detect by content option, should you wish to use the size, checksum and content for detection.
b)Select the Detect by checksum option, should you wish to use the size and checksum for detection;
c)Select Do not detect duplicate files option, should you wish to disable this detection
WARNING: In case the Force in store is enabled, the file is stored in both stores.
Use caching in case of slow storages (tape etc.). HSM will cache the recently used files to speed up the retrieving process.
If Enable caching is checked, HSM will copy all retrieved files to an HSM internal cache. To set the Cache directory (which should be a local hard disk), use the Browse button next to the respective text box. If you have a cluster, the HSM will know that each installation has its own path.
Set the Minimum cache size and Maximum cache size as well. The Minimum size should be about 80% of the cache size. If the cache is full, HSM will delete files (the oldest first) until the cache reaches the minimum size.
NOTE: To choose which Media Store should be cached, use the MediaStoreAdministrator tool. It is started when you click Launch on the Stores & Schemas tab.
The HSM stores temporary files created during duplication detection, compression etc. in temporary directory. Its location can be set in Temp directory text box. Usage of environment variables is allowed in this box (e.g. %TEMP% denotes the temp folder of the currently logged on user).
From time to time administrators need to check systems they manage, examine and analyze their behavior. This tab provides access to features that facilitate this task. Logs and tracing record HSM actions specified by the administrator at the defined extent.
Manage trace settings
In the HSM Trace Settings configuration you can enable various kinds of loggings for the specific HSM components. Select the component in the list and then configure it by checking/unchecking the desired check boxes. Multi-select is possible.
You can enable verbose logging (Debug Output), two kinds of performance loggings (logging information after a specific operation is completed or before a specific operation begins Performance logging and Performance logging (with entry) and choose whether you want to re-direct outputs either to debug output (Force output to debug output) or to the given trace file (Force output to trace file). In the case of Force output to trace file the path has to be specified in the Trace File box. The trace information will be logged there. You can also Open the trace file with the Open file button or delete its contents with the Clear File button. If you clear the file then the file itself wont be deleted. Use Add comment in case you wish to add some text to the file.
After changing the settings you want click the OK button. If you want to discard them click the Cancel button.
Manage log settings
In the Log settings dialog configure the overall HSM logs to your needs:
Include message levels define which information should be logged
oErrors and warnings
oErrors, warnings and Information
NOTE: Error and Warning is internal classification of log entries.
Debug output check to enable verbose logging
Log file check to save the messages in log files
Path set logs location
Name prefix define naming convention; log file name will include this prefix and a number
Number of files if a new log file should be created when the limit is reached, the oldest log file will be deleted
Size of each file when the defined size is reached, new log file will be started
Click Open the current log file to open it.
Clicking the Clear all files will delete all logs.
On this tab you can define and apply encryption keys for archived items stored in HSM. Using encryption keys you make the access to archived files safer.
WARNING: Always export and store encryption keys at safe location. If key get lost, it will not be possible to read the files encrypted with it.
If you want to create a new encryption key press the Create... button. A dialog will appear where you can specify the name of the key.
Press the OK button to create the key. The dialog will ask if you want to export the new key. It is highly recommended to export the encryption key because if you loose your encryption key then the files archived with this key are lost too.
If you confirm the export key dialog appears and you can insert the path where the key should be exported. Also you need to enter and then confirm the password for this file. Press the Export button to export the encryption key.
On the encryption tab you can also Modify the settings of the selected encryption key and also delete it. If you want to delete the key press the Delete button. The application will ask for confirmation and then deletes the key.
If you havent exported the encryption key while creating it, then you can additionally accomplish this with the Export button. If you want to import an exported key back to HSM then click the Import button.
In the encryption dialog specify the path of the key and then enter the password for the key. Key name is filled in automatically. Click Import and the key will be imported to HSM.