Screen Capture Data Lifecycle Management

Screen capture data takes up more storage space than metadata and is configured separately so you need to understand how to manage the recorded screen data.

Version 7.15.2 was the last version allowing screenshot storage on SQL Server database. From version 7.15.3, screenshot storage will be allowed on file-systems only. Previously stored screenshots will remain in their current location.

To manage the screen capture data, a Hot/Warm storage combination is available. The Hot storage acts as a small, fast, short-term cache, while the Warm storage acts as large, cheap, long-term screen capture data storage.

Hot storage is backed by fast, mixed read/write SSD disks. This is where the screen capture data arrives immediately after being captured by the ITM On-Prem (ObserveIT) Agents.

Hot storage is backed by the NTFS file system, formatted with 8 KB blocks.

From version 7.11.0, for large deployments, the use of multiple HOT storage volumes that can be attached to each Application Server is supported and recommended. In addition, multiple Screenshot Storage Optimizer components on each Application Server are supported. This infrastructure, provides better IOPS to share the load across multiple OS's and disk resources. To set up this infrastructure for large deployments, contact Proofpoint Support or Professional Services.

Warm storage is backed by slower NL-SAS or SATA drives. This is where the data is stored for the entire term of retention period.

You can configure up to 4 multiple Hot storage locations and 1 Warm storage location.

The data spends up to 3 days on the Hot storage after which the ITM On-Prem (ObserveIT) Screenshot Storage Optimizer component moves the data to the Warm storage.

The diagram below shows the data flow between components from when the data arrives, is placed in storage, and is removed within the ITM On-Prem (ObserveIT) product.

For details on how to configure, see Configuring Screenshot Storage .