Manage Snap-To-Object using the CLI
This page describes the Snap-To-Object feature, which enables the committing of all the data of a specific snapshot to an object store.
Using the CLI, you can:
weka fs snapshot upload
Use the following command line to upload an existing snapshot:
weka fs snapshot upload <file-system> <snapshot> [--site site]
weka fs download
Use the following command line to create a filesystem from an existing snapshot:
weka fs download <name> <group-name> <total-capacity> <ssd-capacity> <obs-bucket> <locator> [--additional-obs additional-obs] [--snapshot-name snapshot-name] [--access-point access-point]
locatorcan be a locator saved previously for disaster scenarios, or you can obtain the
weka fs snapshotcommand on a system with a live filesystem with snapshots.
The workflow to manage the incremental snapshots includes:
- 2.Download the incremental snapshot (described below).
weka fs snapshot download
Use the following command line to download an incremental snapshot. This command is only relevant for snapshots uploaded from a system of version 4.0 and higher:
weka fs snapshot download <file-system> <locator>
When recovering a snapshot residing on a remote object store, it is required to define the object store bucket containing the snapshot as a local bucket.
To recover a snapshot residing on a remote object store, create a new filesystem from this snapshot as follows:
- 1.Add a new local object-store, using
weka fs tier obs addCLI command.
- 2.Add a local object-store bucket, referring to the bucket containing the snapshot to recover, using
weka fs tier s3 add.
- 3.Download the filesystem, using
weka fs download.
- 4.If the recovered filesystem should also be tiered, add a local object store bucket for tiering using
weka fs tier s3 add.
- 5.Detach the initial object store bucket from the filesystem.
- 6.Assuming you want a remote backup to this filesystem, attach a remote bucket to the filesystem.
- 7.Remove the local object store bucket and local object store created for this procedure.