{"id":12364,"date":"2019-09-23T12:44:49","date_gmt":"2019-09-23T12:44:49","guid":{"rendered":"https:\/\/evolphin.com\/help\/?p=12364"},"modified":"2020-05-15T04:05:10","modified_gmt":"2020-05-15T08:05:10","slug":"auto-retirement-service","status":"publish","type":"post","link":"https:\/\/evolphin.com\/help\/administration-server\/auto-retirement\/auto-retirement-service\/","title":{"rendered":"Setting up Auto-Retirement Policy"},"content":{"rendered":"\n

A new feature for Auto-Retirement<\/span> has been introduced from Zoom 7.3 onwards, which allows Zoom admins to set up rules to determine which assets are automatically retired. This post outlines how the feature works and then shows how to configure it on your Zoom setup.<\/p>\n\n\n\n

Auto-retirement offers a mechanism by which assets can be identified periodically based on certain policies or rules and then these assets are automatically removed from the active Zoom repository by retiring them.<\/p>\n\n\n\n

Right now, archive is the only retirement action supported (either to tier-1 in the case of direct assets, or to tier-2 in the case of direct and external assets). Later on, more actions may be supported, like a purge.<\/div>\n\n\n\n

Auto-retirement works based on one or more rules configured in its settings. Each rule provides a set of criteria and a corresponding action that is to be executed on assets matching those criteria. All assets meeting the criteria will be automatically retired when the Auto-retirement rule runs and matches assets.<\/p>\n\n\n\n

For a Zoom NonStop  (HADR) setup, Auto-retirement should be configured on the highest weightage Zoom Server for it to work properly. This is needed as the other Zoom Servers are synched later and may not be up to date with the highest weightage Zoom Server. Auto-retirement’s search and execute should run on that asset storage which is the most current.<\/div>\n\n\n\n

Assets eligible for retirement<\/h2>\n\n\n\n

The rules for identifying assets that should be retired are set at the Zoom Server along with the frequency at which the rules should run.<\/p>\n\n\n\n

A typical rule picks assets that have not been modified (or had a revision change) for “n” number of days, where “n” is the inactive interval (duration) specified in the rule. The assets meeting the criteria become eligible to be retired.<\/p>\n\n\n\n

The easiest way to check asset modification is to see the “Revisions” panel in the Asset Browser. If the most recent revision has a date that is older than the interval defined in the rule, then the asset is considered inactive. However, there can be more conditions associated with the rule that should also be met, like checking linked assets for this asset.<\/p>\n\n\n\n

Updating metadata on an asset is not considered a modification of the asset.<\/div>\n\n\n\n

In addition to defining rules based on how long an asset must have remained inactive etc, it may also be required to check dependent or associated assets. For example, a video may be linked inside a Premiere Pro file. The video itself may have not been modified recently, but the Premiere Pro file may still be in use, and may still need this video file to be available. In this case, the video must not be archived based on its own inactivity, but rather be kept alive because an associated active asset is linked with it, and therefore it is still in use. <\/p>\n\n\n\n

The Auto-retirement module can be configured to look at the following specific associations to judge if an asset is still in use:<\/p>\n\n\n\n