Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerScale OneFS 9.8.0.0 CloudPools Administration Guide

CloudPools and SmartLock

The OneFS SmartLock feature is a software implementation of write once read many (WORM) files. CloudPools and SmartLock are compatible where feasible for WORM file support.

WORM files in a Compliance domain

SmartLock supports two types of directories: a Compliance domain and an Enterprise domain.

There is nothing to gain by configuring a CloudPool policy to archive files in a SmartLock Compliance domain.
  • When you create a Compliance domain, the target directories must be empty. This requirement prevents CloudPools SmartLink files from being present in the domain.
  • You cannot move existing CloudPools SmartLink files into a Compliance domain. The request is denied.
  • You cannot archive existing files in a Compliance domain to the cloud. The CloudPools SmartLink file creation attempt generates an error.

In an Enterprise domain, a file is a normal file until it is committed. To become a WORM file, a file must have retention configured and be committed. For CloudPools support, this means the following:

  • You can archive a committed file. The CloudPools SmartLink file is successfully created in the Enterprise domain.
  • You can read the committed, archived file via the SmartLink file. You cannot edit, rename, move, or delete the file.
  • You can recall the committed, archived file, and you can archive it again. However, you cannot edit, rename, delete, or move the recalled file out of the Enterprise domain.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\