Enhancements, Fixes, and Known Issues 12/12/2022
The following enhancements, fixes, and known issues are found in this release, dated 12/12/2022:
New features & enhancements
- Elastio now support integration with AWS Backup for cyber recovery protection. The seamless integration enables AWS Backup customers to leverage Elastio’s cyber recovery capabilities without changing their data protection process. Elastio imports AWS Backup recovery points into an Elastio vault and scans then for ransomware and malware and validates the health of its files systems. The import can be controlled from the CLI or from an EventBridge interface.
- Using a CLI command
elastio aws-backup
you can now import any AWS backup available in the AWS account connected to Elastio using the AWS recovery point ARN and AWS vault ARN. This would allow you to scan the AWS backups for all kinds of threats, such as ransomware and malware and file system integrity. - The EventBridge integration allows the user to control which AWS Backup recovery points are imported into Elastio based on rules. The result of the import and the integrity scans ( Ransomware, Malware, File system scans ) are returned to another EventBridge. In this way, indicators of compromise that Elastio detected can we integrated into your existing SOC framework.
- Using a CLI command
- PostgreSQL backup and restore were implemented as native PostgreSQL support in the CLI. The Elastio CLI provides backup and restore capabilities for PostgreSQL databases for both AWS RDS and host-based implementations.
- This feature is a precursor to the automated recovery testing capability coming soon.
- The CLI command can be incorporated into a CI/CD pipeline, a container or a Lambda.
- The backup and recovery supports databases and global objects.
- By default the backup and restore operation is run in the foreground. Foreground restore is currently available on Linux environments only.
- EC2 and EBS restore commands in the Elastio CLI were extended to support option to include or exclude a particular volume. This way a single EBS can be restored from the EC2 recovery point that has multiple EBS volumes. Alternatively, the EC2 can be restored with selected EBS volume(s) attached, i.e. not all of them. When restoring an EC2 recovery point with 1 root volume and 1 data volume and the requirement is to restore EC2 with the data volume(s) only, Elastio will default the root volume to the original AMI and attach the restored data volume(s) to the new restored instance.
- The following notifications were added:
- Asset backup policy coverage evaluated successfully.
- Asset is no longer protected by any policy.
- Backup policy coverage evaluation failed.
- Backup policy coverage evaluation succeeded.
- Asset met backup window SLA.
- Asset missed backup window SLA.
- A search by the recovery point ID was added to the Reports page in Elastio Tenant for a quick option to locate the ransomware or malware report of a certain asset. Note, that when the search is used the time frame filter is disabled - this is due to the fact that the search is performed across all reports without time restrictions.
Bug Fixes
- Block backup of read-only block device would fail to start with “os error 30” in some cases when
elastio-snap
driver was installed. This was fixed. - Backups would occasionally fail with “Essential container in task exited” if the Asset tag wasn’t set to any value. This was fixed.
- Iscan would in some cases get stuck in running state when the vault was misconfigured. This was fixed.
- In Elastio CLI the progress bar for the Total value would not get updated with the child operation processes bars. This was fixed.
Known Issues:
- Postgres restore is not available on Windows due to limitations of the platform. It will be added in the upcoming release.