Storage Settings
Storage settings define how documents will be migrated from the Therefore™ Buffer cache to a separate and permanent storage device, as well as a backup device. These can be accessed by right-clicking the Storage node. Below is a reference for each of the tabs in the settings dialog.
Migrate
Idle time
Time that the service will wait before checking again to see if any documents need to be migrated (minutes).
Block size
Defines the maximum number of documents that are written in each migration.
Keep free
The minimum amount (kilobytes) that should remain free on each Medium.
Faulty limit
The migration of documents will be aborted if the specified number of attempts to transfer a document fails.
Copy block size
Number of documents processed in one copy operation (database transaction).
Migrate Logging
This tab is used to control the detailed logging of migrate events. Completed log files are saved to the Therefore™ system. They can be retrieved by searching the Log Files category. Note that Therefore™ events will be written to the Windows Event log regardless of these settings.
Migrate Events
Four settings are possible for each event.
-
Do note log: no log data is recorded.
-
Log success: log data is only recorded when the event is successful.
-
Log failure: log data is only recorded when the event fails.
-
Log always: log data is always recorded.
| Event | Description |
|---|---|
| Startup / Shutdown | Log when the migrate process starts or stops. |
| Build Result set | Log when a list of pending documents is created. |
| Worker completed | Log when the documents in a storage policy have been migrated. |
| Start Worker | Log when migration begins for the documents in a storage policy. |
| Disk Full | Log when the disk is full. |
Archive
Frequency of log file creation can be defined based on time or size.
-
Every Day: the log file is archived everyday at the Time specified.
-
Every Week: the log file is archived once a week on the Weekday and at the Time specified.
-
Every Month: the log file is archived on the first day of each month.
-
On Size: the log file is archived as soon as the Size specified is exceeded.
Migrate Schedule
Migration schedules move documents from the Buffer directory to a Therefore™ device based on storage policies and device definitions. They include a weekly schedule of default (active) and inactive periods. Default periods are when the migration will occur. During inactive periods, no migration of documents occur.
Double-clicking on a default (active) or inactive time zone opens the Schedule Entries dialog for that particular day. The duration of the default (active) and inactive zones can then be edited.
Double-clicking on a profile opens a dialog where attached devices can be switched on by selecting them.
Advanced
| Setting | Description |
|---|---|
| Migrate-Log Break Day | The day of week when a new log file will be started. Ignored if the log file break mode is not set to 'Weekly' (2). |
| Migrate-Log Break Mode | The break mode for the log file. 1 = Daily, 2 = Weekly, 3 = Monthly, 4 - By file size. |
| Migrate-Log Break Size | The size when a new log file will be created (in MB). Ignored if the log file break mode is not set to 'By file size' (4). |
| Migrate-Log Break Time | The time of the day when the new log file will be started (in minutes from midnight) |