There are three different levels of backup managed by Noovolari Smart backup.
A snapshot is a physical backup of a volume, managed by AWS.
A volume is a physical block level storage which contains data in a resource (e.g. Amazon Elastic Block Store (Amazon EBS) provides block level storage volumes for use with EC2 instances).
One or more volumes can be associated with a single resource.
“Snapshots are incremental backups, which means that only the blocks on the device that have changed after your most recent snapshot are saved.
This minimizes the time required to create the snapshot and saves on storage costs by not duplicating data.
When you delete a snapshot, only the data unique to that snapshot is removed. Each snapshot contains all of the information needed to restore your data (from the moment when the snapshot was taken) to a new volume.” (See Aws documentation).
A volume can be encrypted; Snapshots of encrypted volumes are consequently encrypted, too.
While AWS takes care of data, Noovolari masters how snapshots are taken and managed, for example, it manages the time in which snapshots should be created and/or deleted.
Snapshots, when created, are associated with a specific region by AWS default. Noovolari allows you to replicate a snapshot across different regions or even across different AWS accounts, even if the snapshot is encrypted.
As already described, as part of Cloud resources, volumes (one or more) can be associated with resources. Each resource is correlated to backups.
A Backup in Noovolari Smart Backup is the minimal recoverable entity of our service. When a Backup is done, not only the data are saved but the whole configuration of the Resource is taken alongside. We do this because our focus is to make Backups recoverable with predictable and known result, thus treating resources as a whole. So, inside a backup of an EC2 instance is common to find more than one snapshot, because a snapshot is taken for each volume, and when a Recovery is done all volumes are restored to the condition as they were before.
A backup is a set of snapshots. While AWS only allows you to manage single snapshots (therefore single volumes, when an instance can be made up of multiple volumes), with Noovolari you are able to manage snapshots as a block. Blocks are called backups.
Actions you can do on backups with Noovolari are “clone” and “Recovery”(destructive and Non-destructive)
When you clone a resource, a copy of a selected backup is created in the same region of the resource cloned, in a single click.
There are two different kinds of recovery: destructive and non-destructive recovery.
By recovering a resource in a destructive way, the recovered resource will be terminated after the recovery process is finished. The new resource, created from a Noovolari backup, also inherits the same configuration, network and device mapping from the recovered one.
Non-destructive recovery, instead, saves a copy of the recovered resource after the recovery process is completed.
One or more Cloud resources are managed by Backup Jobs.
Backup jobs are a set of configurations such as how many backups in a given period of time and how many of them need to be retained. To do this, a backup job must be composed by a set of retention rules (the maximum number of retention rules you can define is 5 for each backup job).
Backup jobs create a set of backups.
The set of backups just mentioned above is called Recovery Point.
A recovery point is a collection of Backups taken at the same time. This ensures application level consistency not only for a single Backup but, if correctly configured, for the whole application stack.
Backup jobs manage replicas of regions or accounts; that is to say, each recovery point is duplicated in a different region or account.
By duplicating a recovery point, Noovolari Smart backup creates a copy of each backup and, consequently, of each snapshot in it.
When you register a new Backup Job you can specify Retention Rules that are applied to all Recovery Points related to it.
Each Retention Rule takes into account two different concepts: schedule an retention.