The "Devices Space Cleanup" is a very handy feature for monitoring the storage usage of a device and automatically free it up according to custom cleanup policies and workflows. The devices for which this feature is supported are listed below:
Archives - (e.g. Generic Storage Servers, P2 Servers, HSM Libraries, etc.)
Video Servers - (e.g. ETX, etc.)
Etere PC's - (i.e. Workstations where Etere modules is installed)
The cleanup procedure mainly consist of automatically deleting files from a certain metadevice whenever its storage is detected as "full":
The clean-up procedure takes in consideration:
1. the full disk capacity if the value is not set in Etere Configuration > Resource Editor > Properties > Volume > Size;
2. or the volume size which is set in Etere Configuration > Resource Editor > Properties > Volume > Size;
The system takes as total volume space the logical space of the volume, and shows the used space as the sum of the media stored in the given metadevice.
In order to start using this feature for a device follow the instructions provided below:
Configuration
1. Design a cleanup T-workflow to delete files on a metadevice based on custom policies (i.e. delete files if not scheduled for the next 3 days).
2. Design a cleanup query to retrieve the assets which linked files can be deleted from the device and save it in the db. It can be created from Media Library, performing a search with the relevant filters enabled and saving the search in Query Manager. The query can be then manually edited according to specific requirements.
3. Specify the information required for the storage calculation of the resource.
4. Configure the cleanup parameters of the resource (polling frequency, space threshold, saved query, etc.).
5. Open a Monitoring Console and enable the cleanup feature.
6. Monitoring Console automatically tracks (based on the configured frequency) the storage usage of all configured devices. When it detects that the storage threshold of a device has been reached, the following cleanup process is automatically performed:
a. The query set in the resource is launched.
b. Monitoring console determines if a new instance of the cleanup workflow can be triggered on the assets retrieved. This depends on whether the number of currently active workflows exceeds or not the max. workflows limit (e.g. 20). If it's exceeded, it waits for some workflows to finish to respect the maximum limit.
c. Determine if there is an asset which the "deletion workflow" is not yet attached to. If the workflow is not attached yet, it will be attached and launched it, otherwise it will be restarted.
d. The system performs the actions in the cleanup workflow and deletes the files, lowering the used space on the device below the threshold.
Notice that all performed cleanup operations can be consulted as explained in chapter "View the Cleanup Logs".