Backing Up Antlets
Last updated
Last updated
Check your settings tab in antMan, your version of antMan should should be 2.2.1 (or higher). Why is this important? Any antlet backups taken before this version can not be restored on edgeLinux 2.0 and may have issues when restoring to another server. If your antMan is not up to date then run upgrade-antman in your console before taking backups.
Log in antHill.antsle.com and make sure that your server is activated and visible there. antHill is the central hub and will allow you to restore backups across multiple Antsle servers.
Healing only works between similar platforms. Nano to Nano or antsle One/Two to antsle One/Two.
Your backups can be started and managed from the Backups tab under your antlet settings.
Your backups can be taken to the Antsle Cloud or self-managed storage. To back up your server just select Back Up Now and then choose your storage backend. Do the same to schedule daily backups (scheduled daily backups run every day at midnight).
Every subscription with Antsle comes with a certain amount of free storage space for backups to the Antsle Cloud. It ranges from 10 GB to 5 TB. Additional storage is available for as low as $6.90/100GB/mo. You can see the details on our pricing page.
All data in the Antsle Cloud is encrypted via SSL when in flight and on the server side. Antsle handles key management and key protection for you with 256-bit Advanced Encryption Standard (AES-256).
If backing up via SSH, be sure the antsle's public SSH key is in the the remote host 'authorized_keys' file so that the SSH session will be automatically authenticated.
You can back up your antlet to a mounted storage volume or to another device in your local network. To learn how to mount external storage, view our docs articles on setting up a shared storage volume. You then need to either refer to your storage volume's file path or the ip address when taking a backup.
IMPORTANT: At this time, only drives within the same zpool as your antlet are backed up. That means if you have your antlet and virtual drives in different zpools you will need to move your virtual drive to the same zpool or use a different method to keep it backed up.
In the example below, both virtual drives will be included in the backup since they are in the same zpool. If you want to move the drive to the same zpool , download your drive as a .qcow2 file, choose the "import disk" button, then when you add it, choose the same zpool as your antlet.
If your Antsle server goes down you will probably want to get your antlets back up and running on another server. You can have a second server on standby and all users with a Scale Plan can get free access to a dedicated server in the cloud up to 4 Cores, 8 GB of RAM, and 80 GB SSD for up to 2 weeks. Once you are in your new server:
Click on the Heal antlets tab on the left
Retrieve your antlet. That will copy it over to your server.
Restore your antlet. That makes the antlet available to start and manage in your antlets window.
For peace of mind you can restore a backup as a clone by clicking the '...' options dropdown and select 'Restore as Clone'. Rather than restoring over the existing antlet, this will create a new antlet with a new name which you can test to verify a good backup.
All data is encrypted at rest with AES-256 bit encryption and we use HTTPS standards to protect data during transfers. We use top tier storage providers to hold the data - such as AWS or Wasabi.
We have multiple redundant and secure 10 Gbps Internet connections. This means blazing fast upload and download times (as long as your connection can keep up).
Your data is stored in one location, it is not replicated across multiple data centers.
