Cyber Recovery On AWS FAQ
Cyber Recovery On AWS FAQ
Cyber Recovery On AWS FAQ
SOLUTION BRIEF 1
What do we need to configure manually in AWS after a
Questions successful stack deployment?
Is the Cyber Recovery solution
supported on Azure? After the stack deployment installs the Cyber Recovery software, reset the Cyber
Recovery security account (crso) user, MongoDB, and lockbox passwords:
Are Avamar, Networker, or
PowerProtect Data Manager crsetup.sh --reset
integrated into the architecture?
Which accounts can modify the Configure DDVE manually to enable the object store profile, add a disk to the active
configuration? tier, and create the file system. See the PowerProtect DD Virtual Edition on Amazon
Web Services Installation and Administration Guide.
Can the crso modify the
configuration?
Is Cyber Recovery on AWS Why do we use S3 instead of sending the yaml file to
supported in AWS GovCloud? PS/Consulting?
Why does the Cyber Recovery
software run on SUSE Linux? We want to keep the distribution consistent to AMI sharing and to track the accounts
enrolling for the Cyber Recovery on AWS solution.
Do we provide recommendations
for bandwidth between the on-
premises and AWS Where do I run sudo crsetup.sh?
environments?
Must we have the same DDVE
The Cyber Recovery software is installed silently when the stack is deployed. Run the
code for the on-premises and the
crsetup.sh --reset command from the Cyber Recovery instance in AWS using
AWS environments? the command prompt on the jump host. The stack deployment installs the jump host.
Do we recommend using Cyber
Recovery on AWS over Cyber What happens when I click Secure Vault?
Recovery deployed on-premises?
The Cyber Recovery vault is isolated because the replication context and replication
What regions are supported for
Cyber Recovery on AWS? interface on the VPC Data Domain system is disabled. Also, the security groups and
network ACLs isolate the vault by not accepting traffic from the production Data
Do we support using existing
Domain system running on-premises or on AWS.
AWS VPCs?
Do we have separate data and
management IP addresses for
Has the CyberSense feature been tested with Cyber
the DDVE instance in the Cyber Recovery on AWS?
Recovery vault?
For this release, the CyberSense feature is not supported. Support is planned for the
Does the stack deployment
next release in FY-22Q1.
provide Data Domain hardening?
Does the stack deployment
provide connectivity between the Has there been third-party penetration testing for Cyber
DDVE instance and the S3 Recovery on AWS?
bucket?
Can we have more than two No.
subnets in the Cyber Recovery
vault?
Do we support Data Domain HA
with the Cyber Recovery vault?
2
Will Sheltered Harbor certify Cyber Recovery on AWS?
Questions
No. The Sheltered Harbor specification requires the equivalent of Retention Lock
Do we support Data Domain HA
Compliance mode. Because DDVE on AWS does not support Retention Lock
with Cloud Vault?
Compliance mode, Sheltered Harbor is not supported with Cyber Recovery on AWS.
Must customers use a new AWS
account or an existing account to
deploy the CloudFormation Are we waiting for finalization of Sheltered Harbor testing and
stack? certification before version 19.7 is released?
Do we support AWS Simple
Yes. We have confirmation for Sheltered Harbor support with Cyber Recovery on AWS
Email Service (SES)?
before 19.7 RTS (2/2).
Does the replication traffic go
over the AWS VPN to the private
subnet that contains DDVE? Which accounts/hosts have access to the Cyber Recovery
Can we use CloudFormation to vault after deployment?
create CloudWatch policies to
monitor the Cyber Recovery Hosts—During stack deployment, production clients are specified using a single IP
environment? address or a range of IP addresses.
How does recovery work in Cyber Users—After the jump host is deployed, create other user accounts that can log in to
Recovery on AWS?
the jump host from one of the hosts.
Can the crso dynamically add accounts and hosts that have
access to the Cyber Recovery vault?
The Cyber Recovery security account (crso) is created automatically after the Cyber
Recovery software installation. The crso can create multiple admin accounts to access
the Cyber Recovery UI and CLI. Those accounts can only access the Cyber Recovery
software.
For hosts to access the Cyber Recovery vault through the jump host, provide
information under the Production Client option during stack deployment. For users,
other than default administrator, to access the Cyber Recovery vault through the jump
host, create the user locally on the jump host.
3
Are Avamar, Networker, or PowerProtect Data Manager
integrated into the architecture?
Yes. The customer can deploy and use the Avamar, Networker, and PowerProtect
Data Manager applications.
The reverse Sync feature allows customers to transfer a copy to the on-premises
environment and restore it.
Must we have the same DDVE code for the on-premises and
the AWS environments?
Ensure that you check the MTree replication compatibility between the on-premises
Data Domain system and the DDVE running in the Cyber Recovery vault.
4
What regions are supported for Cyber Recovery on AWS?
Currently, the CloudFormation template and AMI can only be deployed in northern
Virginia and Ohio. In the future, we will be limited to the regions to which DDVE is
limited.
The stack deployment creates a new VPC and subnets that are dedicated to the Cyber
Recovery vault.
• ethV0—Management traffic
• ethV1—Replication traffic
• One subnet for DDVE and the Cyber Recovery management host
5
Must customers use a new AWS account or an existing
account to deploy the CloudFormation stack?
You can use existing accounts; however, we recommend that you use new accounts
so that root accounts are not used in the Cyber Recovery vault.
6
You can find a comprehensive list of documentation for this solution at the Dell EMC
PowerProtect Cyber Recovery Info Hub.
Dell Technologies welcomes your feedback on the solution and the solution documentation.
Contact the Dell Technologies Solutions team by email or provide your comments by completing
our documentation survey.
Contact us
To learn more, contact your local
representative or authorized reseller.
The information in this publication is provided as is. Dell Inc. makes no representations or warranties of any kind with respect to the information in this
publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any
software described in this publication requires an applicable software license.
Copyright © 2021 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell
Inc. or its subsidiaries. Intel, the Intel logo, the Intel Inside logo and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Other
trademarks may be trademarks of their respective owners. Published in the USA February 2020 FAQ H18638.
Dell Inc. believes the information in this document is accurate as of its publication date. The information is subject to change without notice.
Author: Raghav Sachdeva
Contributor: Penelope Howe-Mailly
7