☁️
Zus Docs
  • About Züs
  • System
    • Providers and Services
      • Miner
      • Sharder
      • Blobber
      • Validator
      • Authorizer
      • Node Locator (0DNS)
    • Storage
      • Architecture and Data Management
      • Protocol
        • Allocations
        • Reference Objects
        • Challenges
        • Write Markers
          • Chain Hashing
          • Two Commit
        • Blobber Repair Protocol
      • ZS3 Server
        • Backup, Recovery and Replication
        • Encryption and Compression
        • S3FS Setup and Usage
        • Backup & Recovery with Restic on Blimp + ZS3 Server
        • Backup & Recovery with Veeam on Blimp + ZS3 Server
      • File Operations
        • Upload
        • Download
        • File Sharing
        • Partial Error Recovery
        • Streaming
        • Rent a Blobber
    • Smart Contracts
      • Storage S.C.
      • Miner S.C.
      • ZCN S.C.
      • ERC-20 S.C.s
      • Bridge Protocol
    • Blockchain & Consensus
      • Entities
    • User Authentication and Wallet Management System
      • OKTA Integration
      • Key Management System (KMS)
  • APIs
    • 0DNS API
    • JS API
    • Mobile API
  • CLIs
    • Storage CLI
      • Quickstart
      • Configuring the tool
    • Wallet CLI
      • Wallet Configuration
      • Quickstart
      • Configuring the tool
  • SDKs
    • Go SDK
      • GO SDK Microservices
    • JS SDK
  • Tokenomics
    • Staking
    • Reward & Penalty
  • ✨Züs Apps
    • 🗝️Vult
      • Getting Started
        • Web
        • Mobile
      • Vult AI
        • Batch Processing
        • Memory Retention
        • Technical Implementation
        • Architecture Overview
      • Login / Register
      • File Management Pages
      • File Sharing
      • Storage Management Dashboard
      • Storage Maintenance and Troubleshooting
      • Züs Subscription
      • Wallet Management
      • Refer a friend
      • Settings
    • 🏗️Blimp
      • Getting Started
      • Login / Register
      • Configure Storage
        • Create Standard Storage Allocation
        • Create Enterprise Allocation
        • Create S3 Server Allocation
        • Create Cloud Migration Allocation
        • Allocation Maintenance and Troubleshooting
      • File Management Pages
      • File Sharing
      • Manage Allocations
      • Upgrade Storage
      • Blimp Vault
      • Refer a friend
      • Settings
      • Launching ZS3 Server
      • Using CLI to backup files into Blimp + ZS3 Server
    • 🏠Chimney
      • Getting Started
      • Login / Register
      • Create New Deployment
      • Manage Your Deployments
      • Homepage
      • Staking Dashboard
      • Rank Dashboard
      • Monitor Dashboard
      • Stats Dashboard
      • Logs Dashboard
      • Wallet Dashboard
      • Operations on your Deployments
      • Restricted Blobbers
      • Settings
        • Manage Profile
        • Wallet Settings
        • Update Blobber Settings
        • Update Blobber Version
        • Refer a friend
        • Help
    • 🌐Atlus
      • Getting Started
      • Home page
      • Service Providers Page
      • Charts Page
        • Market Charts
        • Network Charts
        • Storage Charts
      • Blockchain Page
      • Server Map Page
      • Storage Explainer Page
      • Details Pages
        • Block Details Page
        • Transaction Details Page
        • Wallet Details Page
        • Miner Details Page
        • Sharder Details Page
        • Blobber Details Page
        • Validator Details Page
        • Authorizer Details Page
        • Allocation Details Page
      • Appendix: Common Components
    • ⚡Bolt
      • Getting Started
        • Web
        • Mobile
      • Login / Register
      • Sign In with external wallet
      • Staking Dashboard
      • Staking/Unstaking a provider
      • Claiming Rewards
      • Send/Receive ZCN tokens
      • Buy ZCN
      • Deposit/Withdraw ZCN tokens
      • Activity Dashboard
      • Refer a friend
      • Settings
  • Releases
    • Hardfork
Powered by GitBook
On this page
  1. System
  2. Storage
  3. ZS3 Server

Use Case - Backup and Restore

Use your ZS3 buckets as backup storage space for your data

Last updated 10 months ago

After deploying your S3 server, you can use to be able to use your bucket as backup storage space for your data, with better carbon footprint, security and performance.

Setup restic to use your bucket for backup

Here are the steps to use your ZS3 buckets for backup using Restic:

  1. Register to

  2. Deploy zs3server as mentioned in . Once deployed, you can find your URL, access key and secret key in the "Use CLI" section in Blimp's S3 operations page, as shown in the image below.

Example of this command (with the credentials part in double square parts)

curl -X GET [[https://blimpsogec.zus.network]]/minioclient/?action=createBucket&[[accessKey=devyetii&secretAccessKey=Admin@123]]

In this example:

  • The URL: https://blimpsogec.zus.network

  • The Access Key: devyetii

  • The secret key: Admin@123

  1. Connect to the machine you'll be using for backup/restore. This can be your local machine, or any other remote machine that you have. If it's a remote machine, then you can use SSH to connect to it as follows:

ssh <user>@<ip>
sudo apt update -y
sudo apt install restic -y
sudo restic self-update
  1. Prepare you environment variables as follows:

export AWS_ACCESS_KEY_ID=<your-access-key-from-step2>
export AWS_SECRET_ACCESS_KEY=<your-secret-key-from-step2>
export RESTIC_REPOSITORY="s3:<your-zs3server-url-from-step2>"

You should replace the placeholders in the command (<your-access-key-from-step2>, <your-secret-key-from-step2> and <your-url-from-step2>) with the corresponding values from Step 2.

  1. Initialize your Restic repository as follows:

restic init
  1. After the repository is initialized, we're ready to make a backup. Find a local directory with data files to backup. Use below command to start back up.

restic -r s3:<your-zs3server-url-from-step2> --verbose backup <path-to-directory-to-backup>
    

You should replace the command placeholders (<your-zs3server-url-from-step2>, <path-to-directory-to-backup> ) with corresponding values.

Now, a new backup snapshot of this directory is created and saved to the Restic repository. You can add this command to your crontab file to run the backup periodically.

  1. You can also list all of your snapshots with the following command:

restic snapshots
  1. To restore the latest snapshot to a specific target you can use the following command:

restic restore latest --target ~/ --verbose

Install Restic on your machine. Provided below are steps to install Restic on Ubuntu machine. For other Linux distros or other OSs, check .

For more sets of restic commands, you can refer to the .

Restic Installation Guide
official Restic Backup docs
Restic
https://blimp.software
this page
Fig1: URL, secret and access keys in Using CLI section