Event-Driven Cleanup

Cleanup is performed between scheduled cleanups in the following two cases:

  1. Free Space size falls below the Generate alerts when free space falls below value (default = 50GB).

    In this case, the cleanup process performs the following operations:

    1. An event message is created in the Event Viewer, which indicates a low disk space condition.

    2. Indexes older than the Retain index for n days setting (default: 15 days) are deleted until Clean up until free space is at least n percent is reached (default = 15 percent).

    3. In the event that, after removing the old indexes, the used disk space still exceeds Clean up until free space is at least n percent, the process continues by removing the least-recently-used indexes in the directory, until the Free Space percent becomes equal to or greater than the Clean up until free space is at least n percent setting.

  2. Free Space size falls below the value in Take the Index offline when free space falls below n GB (default = 10GB).

    In this case, the cleanup process performs the following operations:

    1. The MediaAgent is brought offline.

    2. Indexes older than the Retain index for n days setting (default = 15 days) are deleted.

    3. If the used disk space still exceeds the percentage specified by Clean up until free space is at least n percent (default: 15 percent), the process removes the least-recently-used index files in the directory, until the Free Space becomes equal to or greater than the Clean up until free spaceis at least n percent setting.

    4. Within 20 minutes of the MediaAgent being taken offline, if cleanup activities have brought the disk utilization to or above the free space percent setting, the MediaAgent is brought back online. If after 20 minutes the disk utilization percent setting still has not been met, the MediaAgent is left offline, and administrative staff must manually delete data from the Index Directory (see Correcting Cleanup Issues), and then bring the MediaAgent back online manually (see Enable or Disable a MediaAgent) or wait for the next run of the scheduled job to bring it back online.

Examples

  • Preconditions

    • Total Size is 300 GB

    • Retain index for n days = 15 days

    • Generate alerts when free space falls below is set to 50.0 GB

    • Take the Index offline when free space falls below n GB is set to 10.0 GB

    • Clean up until free space is at least n percent is set to 15 percent

  • Cases

    • Indexes are found to be old

      While an event-driven cleanup is running, some index files are found to be 16 or more days old, and are deleted.

    • Free Space indicates 18 GB (6.00%)

      Because the amount of free space is less than 50 gigabytes, but more than 10 gigabytes, the MediaAgent places an event message into the Event Viewer and, if alerts are configured, sends an alert to the administrator. An event-driven cleanup begins. It ends when Free Space is 15 percent or more.

    • Free Space indicates 8 GB (2.67%)

      Because the amount of free space is less than 10 gigabytes, the MediaAgent goes offline and places an event message into the Event Viewer. If alerts are configured, the MediaAgent sends an alert to the administrator. An event-driven cleanup begins. Within 20 minutes, if the Free Space percent is 15 percent or more, the MediaAgent comes back online. If Free Space is still less than 15 percent, the MediaAgent stays offline, and administrative staff should perform a manual cleanup, then bring the MediaAgent back online when ready.

    • Free Space percent shows 9.00 percent (273 gigabytes used)

      The percentage of available disk space has fallen below Clean up until free space is at least n percent, so the MediaAgent begins deleting index files that are older than the Retain index for n days setting, until the percentage of available disk space is equal to or more than the Clean up until setting. If this is not sufficient, it continues by deleting least-recently-used indexes until enough space is recovered to meet the free space percentage requirement.

      In this example, at least 18 GB worth of indexes are aged out in order to cross below the 255 GB threshold dictated by the Clean up until free space is at least n percent setting.

Loading...