W E K A
WebsiteSupportDownloads/LicensingAWS Self-Service Portal
Search…
4.0
Weka documentation
Weka System Overview
About the Weka system
SSD capacity management
Filesystems, object stores, and filesystem groups
Weka networking
Data lifecycle management
Weka client and mount modes
Glossary
Getting Started with Weka
Quick installation guide
Manage the system using the Weka CLI
Manage the system using the Weka GUI
Run first IOs with WekaFS
Getting started with Weka REST API
Planning & Installation
Prerequisites for installation
Weka installation on bare metal
Weka installation on AWS
Performance
Weka performance tests
WekaFS Filesystems & Object Stores
Manage object stores
Manage filesystem groups
Manage filesystems
Attach or detach object store buckets
KMS management
Advanced data lifecycle management
Advanced time-based policies for data storage location
Data management in tiered filesystems
Transition between tiered and SSD-only filesystems
Manual fetch and release of data
Mount filesystems
Snapshots
Snap-To-Object
Quota management
Additional Protocols
NFS
SMB
S3
Operation Guide
Alerts
Events
Statistics
System congestion
Manage security
Expand and shrink cluster resources
Background tasks
Upgrade Weka versions
Billing & Licensing
License overview
Classic license
Pay-As-You-Go license
Support
Prerequisites and compatibility
Get support for your Weka system
The Weka support cloud
Diagnostics CLI command
Appendix
Weka CSI plugin
Monitor using external tools
Snapshot management
REST API Reference Guide
Powered By GitBook
Transition between tiered and SSD-only filesystems
This page describes how to transition from an SSD-only to a tiered filesystem, and vice versa.

The transition from SSD-only filesystem to tiered filesystem

An SSD-only filesystem can be reconfigured as a tiered filesystem by attaching an object store. In such a situation, the default is to maintain the filesystem size. In order to increase the filesystem size, the total capacity field can be modified, while the existing SSD capacity remains the same.
Note: Once an SSD-only filesystem has been reconfigured as a tiered filesystem, all existing data will be considered to belong to interval 0 and will be managed according to the 7-interval process. This means that the release process of the data created before the reconfiguration of the filesystem is performed in an arbitrary order and does not depend on the timestamps.

The transition from tiered filesystem to SSD-only filesystem

A tiered filesystem can be un-tiered (and only use SSDs) by detaching its object stores. This will copy the data back to the SSD.
Note: The SSD must have sufficient capacity, i.e., the allocated SSD capacity should be at least the total capacity used by the filesystem.
For more information, refer to Attaching/Detaching Object Stores Overview.
Previous
Data management in tiered filesystems
Next
Manual fetch and release of data
Last modified 1mo ago
Copy link
Contents
The transition from SSD-only filesystem to tiered filesystem
The transition from tiered filesystem to SSD-only filesystem