Overview

Egnyte's archive domains are intended to be an affordable cold storage option for clients who have purchased our Retention, Archive, and Deletion (RAD) product.  An archive domain has certain specified restrictions and these restrictions pertain to the type of storage, number of users, and the collaboration capabilities available on the domain.  Such restrictions help bring down the infrastructure and compute costs for the domain and thereby makes it viable and cost-effective for customers to utilize more storage on this domain.

An archive domain can be purchased along with RAD and as such with the new Business, Enterprise-Lite, and Enterprise Platform plans.

Technical Specifications

Category

Description

Supported User Types

Admin Users

Number of Users

5

Archival Storage Type

Egnyte-allocated storage only

No customer-allocated external storage buckets

Data residency requirements cannot be met outside our current regions. Please contact the PM if there are such requirements

Authentication

Egnyte Authentication, Single Sign-On (SSO)

Multi-Entity Management (MEM) enabled

Permissions

We do not support permissions in archive domains

Allowed End-points

Web UI, Public API, Migration

Apps & Integrations

We do not support any integrations on the Archive domain

Version Limit

Unlimited

File Size Limits

Unlimited

Data Minimization

Enterprise, Enterprise-Lite & RAD Customers

RAD can be configured on the active domain to purge data on the archive domain

Classification

Not supported on archival. Customers can use pre-archived classified information on active domain

% Active

Limited to 5%

Search

Metadata searches are allowed

Content search is not allowed (e.g. search for a string within a file)

Protect Classification

Cannot be turned on for Archive domain

Classification can be run on the source (active domain, on-prem server, or other cloud sources) before archiving the data

RAD policy on Trash contents

Allowed

Archival policies apply to files that are accidentally deleted from the folder that has the policy configured. For e.g. if a file is deleted and moved to Trash before its archival policy, say 2 years, the file will be archived to the destination folder that was configured in the archival policy

Subject Access Request (SAR) on Archive

Not Possible