Configuring Bucket Settings in Wasabi Cloud NAS

You can configure the following Wasabi bucket settings directly through the Wasabi Cloud NAS Configuration interface:

  • Enable/disable versioning in the bucket.
  • Turn on/off compliance mode for the bucket and configure the retention time of objects in it.
Note: If both the versioning and compliance settings are enabled from the Wasabi Cloud, click on the refresh all button in the client so the changes made to the Wasabi Cloud for these settings are reflected on the client. 

Enabling/Disabling Versioning in the Bucket

When versioning in the bucket is disabled, if a replicated file is modified on the source and is queued for replication again, the new copy on the bucket overwrites the previous one. When you enable versioning in the bucket, WCN  does not overwrite the replica on the bucket and each copy of the file is kept as a separate version.

As long as versioning is enabled, using WCN  you can retrieve from the bucket a specific version of a replicated file or restore the contents of a whole folder to the latest submitted version of all files in it by a specific time. For more information, refer to Managing File and Folder Versions.

If you disable versioning after it has been enabled, all versions of a specific replicated file will be kept on the bucket, but you will be able to retrieve them only directly from the bucket. Additionally, any modifications of a file on the source will overwrite only the latest version of the file on the bucket and you will be able to retrieve only this version using WCN.

To enable/disable versioning in the bucket:

  1. In the left pane, click Bucket Settings under a selected source.

  2. In the right pane, do one of the following:
    • Enable versioning in the bucket by switching the Versioning setting to the active position:
    • Suspend versioning in the bucket by switching the Versioning setting to the inactive position:
  3. Click Apply.
  4. Once you complete adding a new source-target pair and configuring Bucket Settings, click Resume (navigate to the left pane, click Wasabi Cloud NAS) to allow WCN to resume operations. See Pausing/Resuming Automatic Wasabi Cloud NAS Operations, for instructions on how to resume.

Turning On/Off Compliance Mode

When compliance mode is turned on through WCN, the local source corresponding to it is set to WORM mode. (This does not apply to the NAS source.) The files in the local folder cannot be edited or deleted anymore. If a local file has been modified, the system will force the user to save it as a new file.

To turn on/off compliance mode:

  1. In the left pane, click Bucket Settings under a selected source.
  2. In the right pane, do one of the following:
    • Turn on compliance mode by switching the Compliance Settings to the active position:
    • Turn off compliance mode by switching the Compliance Settings to the inactive position:
  3. In Retention Time, enter the time after which objects in the bucket can be modified and/or deleted.
  4. Click Apply.
  5. Once you complete adding a new source-target pair and configuring Bucket Settings, click Resume (navigate to the left pane, click Wasabi Cloud NAS) to allow WCN  to resume operations. See Pausing/Resuming Automatic Wasabi Cloud NAS Operations for instructions on how to resume.

What to expect when the versioning, compliance, and or both settings are enabled?

OperationWhen only Versioning is enabledWhen only Compliance is enabledWhen both Versioning and Compliance are enabled
ModifyUsers are allowed to update the file at the source
Users cannot update the file at the source until after the retention period
Users are allowed to update the file at the source
VersionEach time the file at the source is updated, a new version is created in the Wasabi Cloud, and the source folderNo new versions will be created either at the source or on the Wasabi CloudEach time the file at the source is updated, a new version is created in the Wasabi Cloud, and the source folder
DeleteUsers can delete the original object, any version, and/or all the versions at the source or in the CloudUsers cannot delete the object until after the retention periodUsers cannot delete the original object, any version, and/or all the versions at the source or in the Cloud