It is possible to backup both metadata and EBS volumes attached to the instances. With an easy to use web interface you are able to quickly orchestrate data protection for AWS EC2 workloads. It also provides snapshot management for the EBS volumes.
- Backup of instance metadata and data in EBS volumes
- Option to exclude specific volumes
- Full backup and file-level restore – use mountable backups and browse them via the web interface or directly in the Storware node. The second option is to expose the drives via iSCSI.
There are several scenarios
for AWS which may suit your case
Backup EC2 to S3
In this case after dumping backup Storware can push them to the S3 bucket. You may consider using a VPC endpoint to boost your store operation performance.
Backup EC2 to your other cloud provider
If you’re using multiple clouds, you may also consider storing data in GCS or Azure backup providers.
Backup EC2 to EBS volume on the proxy
You can use PowerProtect DD to deduplicate data and optimize your storage consumption significantly. Keep in mind that you might want to protect your EBS volume using EBS snapshots as well.
Backup EC2 to your local backup provider
If you already have a central enterprise backup solution, you might want to use it as a backup provider for EC2 instances running in AWS. You should consider using Direct connect to have a higher bandwidth available.
Avoid being trapped in the AWS ecosystem
With Storware Backup and Recovery, your backups do not need to be stored in the AWS ecosystem. Store backups anywhere according to your needs.
Storware allows you to choose from multiple data backup destinations. From file systems, other cloud storage providers like Azure or Google Cloud Storage, to instances of an enterprise backup provider like IBM Spectrum Protect. This means you can successfully implement several other scenarios: data protected in a single Availability Zone, transferred to another AZ/region, cloud storage or maybe even to your local data center.
Backup destinations can be anywhere, as long as you have a network connection between the cloud and your on-premises backup provider. If anything goes wrong with AWS, you still have a local copy of your data.