Navigate to NetApp Cloud Central and log in or sign up.

After you log in, you should be taken to the Canvas.

Click "Add Working Environment" and choose Cloud Volumes ONTAP in AWS. Here, you also choose whether you want to deploy a single node system or a high availability pair. I have chosen to deploy a high availability pair.

If no connector has been created, a pop-up appears asking you to create a connector.

Click Lets Start, and then choose AWS.

Enter your secret key and access key. Make sure that your user has the correct permissions outlined on the NetApp policies page.

Give the connector a name and either use a predefined role as described on the NetApp policies page or ask Cloud Manager to create the role for you.

Give the networking information needed to deploy the connector. Verify that outbound internet access is enabled by:

Provide communication with the connector via SSH, HTTP, and HTTPs by either providing a security group or creating a new security group. I have enabled access to the connector from my IP address only.

Review the information on the summary page and click Add to deploy the connector.

The connector now deploys using a cloud formation stack. You can monitor its progress from Cloud Manager or through AWS.

When the deployment is complete, a success page appears.

Select AWS and the type of deployment based on your requirements.

If no subscription has been assigned and you wish to purchase with PAYGO, choose Edit Credentials.

Choose Add Subscription.

Choose the type of contract that you wish to subscribe to. I chose Pay-as-you-go.

You are redirected to AWS; choose Continue to Subscribe.

Subscribe and you are redirected back to NetApp Cloud Central. If you have already subscribed and don't get redirected, choose the "Click here" link.

You are redirected to Cloud Central where you must name your subscription and assign it to your Cloud Central account.

When successful, a check mark page appears. Navigate back to your Cloud Manager tab.

The subscription now appears in Cloud Central. Click Apply to continue.

Enter the working environment details such as:

Choose which additional services you would like to deploy. To discover more about these services, visit the NetApp Cloud Homepage.

Choose whether to deploy in multiple availability zones (reguires three subnets, each in a different AZ), or a single availability zone. I chose multiple AZs.

Choose the region, VPC, and security group for the cluster to be deployed into. In this section, you also assign the availability zones per node (and mediator) as well as the subnets that they occupy.

Choose the connection methods for the nodes as well as the mediator.

Floating IP addresses are used to allow access to the various IP addresses that Cloud Volumes ONTAP uses, including cluster management and data serving IPs. These must be addresses that are not already routable within your network and are added to route tables in your AWS environment. These are required to enable consistent IP addresses for an HA pair during failover. More information about floating IP addresses can be found in the NetApp Cloud Documenation.

Select which route tables the floating IP addresses are added to. These route tables are used by clients to communicate with Cloud Volumes ONTAP.

Choose whether to enable AWS managed encryption or AWS KMS to encrypt the ONTAP root, boot, and data disks.

Choose your licensing model. If you don't know which to choose, contact your NetApp representative.

Select which configuration best suits your use case. This is related to the sizing considerations covered in the prerequisites page.

Optionally, create a volume. This is not required, because the next steps use SnapMirror, which creates the volumes for us.

Review the selections made and tick the boxes to verify that you understand that Cloud Manager deploys resources into your AWS environment. When ready, click Go.

Cloud Volumes ONTAP now starts its deployment process. Cloud Manager uses AWS APIs and cloud formation stacks to deploy Cloud Volumes ONTAP. It then configures the system to your specifications, giving you a ready-to-go system that can be instantly utilized. The timing for this process varies depending on the selections made.

You can monitor the progress by navigating to the Timeline.

The Timeline acts as an audit of all actions performed in Cloud Manager. You can view all of the API calls that are made by Cloud Manager during setup to both AWS as well as the ONTAP cluster. This can also be effectively used to troubleshoot any issues that you face.

After deployment is complete, the CVO cluster appears on the Canvas, which the current capacity. The ONTAP cluster in its current state is fully configured to allow a true, out-of-the-box experience.

Click the source ONTAP system (on-premises) and either drag and drop it to the destination, select Replication > Enable, or select Replication > Menu > Replicate.

If you did not drag and drop, choose the destination cluster to replicate to.

Choose the volume that you'd like to replicate. We replicated the data and all log volumes.

Choose the destination disk type and tiering policy. For disaster recovery, we recommend an SSD as the disk type and to maintain data tiering. Data tiering tiers the mirrored data into low-cost object storage and saves you money on local disks. When you break the relationship or clone the volume, the data uses the fast, local storage.

Select the destination volume name: we chose [source_volume_name]_dr.

Select the maximum transfer rate for the replication. This enables you to save bandwidth if you have a low bandwidth connection to the cloud such as a VPN.

Define the replication policy. We chose a Mirror, which takes the most recent dataset and replicates that into the destination volume. You could also choose a different policy based on your requirements.

Choose the schedule for triggering replication. NetApp recommends setting a "daily" schedule of for the data volume and an "hourly" schedule for the log volumes, although this can be changed based on requirements.

Review the information entered, click Go to trigger the cluster peer and SVM peer (if this is your first time replicating between the two clusters), and then implement and initialize the SnapMirror relationship.

Continue this process for data volumes and log volumes.

To check all of your relationships, navigate to the Replication tab inside Cloud Manager. Here you can manage your relationships and check on their status.

After all the volumes have been replicated, you are in a steady state and ready to move on to the disaster recovery and dev/test workflows.

Select the right instance type based on the required workload. Factors to consider include the number of business transactions to be supported, the number of concurrent users, data set sizing, and so on.

EC2 instance deployment can be launched through the EC2 Dashboard. The exact deployment procedures are beyond the scope of this solution. See Amazon EC2 for details.

Add an Oracle standby instance to the DNS server for name resolution within the SnapCenter management domain.

Add a Linux management user ID as the SnapCenter OS credentials with sudo permissions without a password. Enable the ID with SSH password authentication on the EC2 instance. (By default, SSH password authentication and passwordless sudo is turned off on EC2 instances.)

Configure Oracle installation to match with on-premises Oracle installation such as OS patches, Oracle versions and patches, and so on.

NetApp Ansible DB automation roles can be leveraged to configure EC2 instances for database dev/test and disaster recovery use cases. The automation code can be download from the NetApp public GitHub site: Oracle 19c Automated Deployment. The goal is to install and configure a database software stack on an EC2 instance to match on-premises OS and database configurations.

Retrieve the Windows administrator password to log in to an instance via RDP.

Disable the Windows firewall, join the host to Windows SnapCenter domain, and add the instance to the DNS server for name resolution.

Provision a SnapCenter log volume to store SQL Server log files.

Configure iSCSI on the Windows host to mount the volume and format the disk drive.

Again, many of the previous tasks can be automated with the NetApp automation solution for SQL Server. Check the NetApp automation public GitHub site for newly published roles and solutions: NetApp Automation.