Versioning and Logging

Updated on 06 Sep 2023

Article Summary

Share feedback

Thanks for sharing your feedback!

Versioning

The Wasabi versioning feature allows you to preserve, retrieve, and restore every version of every object stored in a Wasabi bucket. Versioning offers an additional level of protection by providing a means of recovery if you accidentally overwrite or delete objects. This allows you to easily recover from unintended user actions and application failures. You can also use versioning for data retention and archiving.

Once you enable versioning for a bucket, Wasabi preserves existing objects any time you perform a PUT, POST, COPY, or DELETE operation on them. By default, GET requests will retrieve the most recently written version. Older versions of an overwritten or deleted object can be retrieved by specifying a version in the request.

Creating a Bucket with Versioning

An option is provided to set the bucket versioning feature. By default, this feature is suspended (not enabled).

When Bucket Versioning is enabled, every version of every object in the bucket will be stored. You can then retrieve and restore any version of an object in the bucket. This provides protection against inadvertent removal of an object (such as by overwriting or expiration).

Use versioning cautiously because when versioning is enabled different versions of all the objects in the bucket are saved. This means the costs could be very high, eventually, as versions are stored.

Refer also to Bucket Versioning for more information about bucket settings and versioning.

Creating a Bucket with Logging

An option is provided to set the bucket logging feature. By default, this feature is suspended (not enabled).

When Bucket logging is enabled, a text log will be maintained of all access to the bucket. This provides details about the types of access requests made, request resources, and the date/time of processed requests.

Use logging cautiously because when logging is enabled, all log files are saved. This means the costs could be high, eventually, as log files are stored

If you enable logging, you must:

Enter a logging prefix to include in the log file name. Each log file will start with the characters you enter.
Enter the name of a bucket in which to store log files. Click the down arrow to select from a list of target buckets.
In the following example, log file names will begin with “wdgt99” and the files will be stored in the “user.docs” bucket.
Click NEXT.
The bucket properties are displayed for your review. You can click BACK if you need to change any information. But, for this exercise, click CREATE BUCKET to accept the information and create the bucket.
A message displayed at the top of your screen indicates that the bucket was created successfully.

Refer also to Bucket Logging for more information about bucket settings and logging.

What's Next

Objects, Folders, and Files

Table of contents

Versioning
Creating a Bucket with Logging

WASABI and the WASABI logo are trademarks of Wasabi Technologies LLC and may not be used without permission of Wasabi Technologies. All other names are used for identification purposes only and are trademarks or registered trademarks of their respective companies.

Information presented herein is subject to change without notice. Companies, names, and data used in examples are fictitious unless otherwise noted. No part of this information may be reproduced or transmitted in any form by means electronic or mechanical, for any purpose, without express written permission of Wasabi Technologies.