Cloud Rewind enables discovery, protection and recovery of entire or partial cloud application environments.
With a provided connection to your cloud account, Cloud Rewind discovers and records cloud configuration items and organizational data from all or specified cloud resources and intelligently calculates resource dependencies. Backup schedule and retention are configurable according to organizational policy, and all backup data is stored in Cloud Rewind’s cloud servers. When needed, recovery to point-in-time is available for all or specified parts of the protected environment, to original or new contexts as specified.
Cloud Rewind is a cloud service, requiring no on-premise infrastructure or installations. Cloud Rewind is agentless, instead connecting directly to organizational cloud accounts and leveraging cloud-native services. Amazon AWS, MS Azure, and Google GCP cloud vendors are supported. Depending on cloud vendor, supported resource types include cloud virtual machines, containers, block storage volumes, database services, security groups, load balancers, VPCs, routes, internet gateways, customer gateways, DHCP options, and more.
Cloud Connection
After subscribing to Cloud Rewind, log into Cloud Rewind and configure a Cloud Connection to your cloud account.
The Cloud Connection is Cloud Rewind’s communication channel with your cloud account for all operations, from discovery to recovery. Upon establishing the Connection, Cloud Rewind discovers and lists cloud resources available for protection. Optionally, you can limit the Connection to specified cloud regions or cloud services.
To enable cross-account recovery (currently: AWS only), or to discover and protect resources in multiple cloud accounts, configure additional Cloud Connections.
Cloud Assembly
To protect discovered resources, configure a Cloud Assembly.
Cloud Assemblies define protection (backup) jobs:
-
What to protect: Specify storage regions and resources.
-
Backup scheduling and retention policies.
Even when all resources need to be protected, large or complex infrastructures may be split into multiple Assemblies, by applications or by resource tags, to enhance application-level recovery options and to reduce recovery time.
Recovery
When you need it, recovery to any retained protection job is available.
Recovery can be performed for all or specified Assembly resources, to the original or a different context – VPC, region, zone, or even account (depending on cloud vendor), with various configurable options such as IP allocation method.
Assembly resources to be recovered can be selected specifically, or by tags. Context options and additional configuration can be predefined in one or more Recovery Profiles, so that at recovery time you need to select only Assembly resources (all or specified) and the Recovery Profile.