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
Advanced data lifecycle management
Mount filesystems
Snapshots
Manage snapshots using the GUI
Manage snapshots using the CLI
Snap-To-Object
Quota management
Additional Protocols
NFS
SMB
S3
Operation Guide
Alerts
Events
Statistics
System congestion
Security management
User management
Organizations management
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 management
Appendix
Weka CSI Plugin
Monitor using external tools
Snapshot management
REST API Reference Guide
Powered By GitBook
Snapshots
Snapshots enable the saving of a filesystem state to a directory and can be used for backup, archiving and testing purposes.
Snapshots allow the saving of a filesystem state to a .snapshotsdirectory located under the root filesystem. They can be used for:
  • Physical backup: The snapshot directory can be copied into a different storage system, possibly on another site, using either the Weka system Snap-To-Object feature or a third-party software.
  • Logical backup: Periodic snapshots enable filesystem restoration to a previous state if logical data corruption occurs.
  • Archive: Periodic snapshots enable the accessing of a previous filesystem state for compliance or other needs.
  • DevOps environments: Writable snapshots enable the execution of software tests on copies of the data.
Snapshots have no impact on system performance and can be taken for each filesystem while applications are running. They consume minimal space, according to the actual differences between the filesystem and the snapshots, or between the snapshots, in 4K granularity.
By default, snapshots are read-only, and any attempt to change the content of a read-only snapshot returns an error message.
It is possible to create a writable snapshot or update an existing snapshot to be writable. However, a writable snapshot cannot be changed to a read-only snapshot.
The Weka system supports the following snapshot operations:
  • View snapshots.
  • Create a snapshot of an existing filesystem.
  • Delete a snapshot.
  • Access a snapshot under a dedicated directory name.
  • Restore a filesystem from a snapshot.
  • Make snapshots writable.
  • Create a snapshot of a snapshot (relevant for writable snapshots, or for read-only snapshots before being made writable).
  • List of snapshots and obtaining their metadata.
  • Schedule automatic snapshots (see Snapshot management in the Appendix).
Note: The number of snapshots per system is limited to 4,096. Each live filesystem consumes one of the total snapshots count.
​
Related topics
WekaFS Filesystems & Object Stores - Previous
Mount filesystems
Next
Manage snapshots using the GUI
Last modified 1mo ago
Copy link