Archive and Restore for the End-Users

Zoom users can invoke archive or restore operations from various client interfaces like the command line, or from the Asset Browser.

Check here for details about the configuration and management related to the archive module: Archive Management and Configuring Archive Module

Archive From Asset Browser

A user who is in a role with permission levels of EDIT_ALL will be allowed to invoke archive of assets in the corresponding project. The option is available both in the right-click context menu and from the cart menu, within the Asset Browser.

On clicking Archive depending upon the Archive Module installed the following sequence of steps will occur:

  1. The asset is marked for archiving and is added to an archive queue
  2. Once the asset is completed check-pointed (all pending change transactions have been applied), usually after a Zoom server periodic re-start, the archive queue is flushed out
  3. If Basic Archive Module is configured by the administrator, upon restart the asset will be copied to a designated folder path and removed from the Zoom database. In the Zoom Asset Browser an orange circle will show up to indicate the asset is archived
  4. If there is an external archive module installed instead of a Basic Module, Zoom will delegate to the module to mark the asset as ‘Pending Archive’. A scheduled task will scan and copy all the assets pending archive to the external archive store such as AwsS3 and mark the metadata status for the asset as ‘Archived’. For exact flow please see the documentation for each external archive module handler. 

Restore / Petition From Asset Browser

For users who have permission higher than EDIT_ALL, any restore request will go through directly.

For users who have permission less than EDIT_ALL but equal to or above CONTRIBUTE, the request may be completed or be converted into a petition depending on the following.

If the restore-threshold in the archive configuration is set to a value other than -1, then for file sizes less than that threshold, the end user’s restore request is automatically escalated to an actual restore operation. Such assets will be restored immediately and do not need any administrator intervention. For assets of larger sizes, the request is converted into a petition. The administrators will then have to parse the request from the Web Management Console and decide whether or not to allow restore of the relevant assets.

On clicking Restore depending upon the Archive Module installed the following sequence of steps will occur:

  1. If Basic Archive Module is configured by the administrator, upon restore (or approval of a restore petition) the asset will be copied from the designated folder path and added  to the Zoom database. In the Zoom Asset Browser an orange circle will disappear to indicate the asset is restored
  2. If there is an external archive module installed instead of a Basic Module, Zoom will delegate to the module to mark the asset as ‘Pending restore’. A scheduled task will scan and copy all the assets pending restore from the external archive store such as AwsS3 and mark the metadata status for the asset as ‘Online’. For exact flow please see the documentation for each external archive module handler. 

Notifications

All archive / restore operations are accompanied by email notifications to the super-admins and project-admins. Apart from that, for restore petitions, the petitioner is also notified through email whether a request was approved or rejected.

Leave a Comment