Backing up data

R-Cloud enables you to back up your Amazon Route 53 data securely and efficiently.

Configuring the SaaS application for backup operations

R-Cloud starts protecting the Amazon Route 53 service resources after you complete the following steps:

Add the module as a source to R-Cloud. For instructions, see Adding the module to R-Cloud.
Add your AWS account as a source to R-Cloud. For instructions, see Managing AWS accounts.

 Note When adding the AWS account as a source, make sure you sign into your AWS account by using the account root user or an IAM user with administrative permissions.
Edit the AWS JSON policy document. For instructions, see Editing the HycuPolicy JSON policy file.
Assign a policy to the related SaaS application. For instructions, see Defining your backup strategy.

Editing the HycuPolicy JSON policy file

In the IAM Management Console, click Roles, and then HycuRole. Click HycuPolicy to edit the policy. Append the following statements to the existing HycuPolicy JSON policy file:

{
  "Effect":"Allow",
  "Action": [
    "iam:ListAttachedRolePolicies",
    "iam:ListRolePolicies",
    "iam:GetRolePolicy",
    "iam:GetPolicy",
    "iam:GetPolicyVersion",
    "ec2:DescribeRegions",
    "ec2:DescribeVpcs"
    "route53:ListHostedZones",
    "route53:ListResourceRecordSets",
    "route53:ListHealthChecks",
    "route53:ListCidrCollections",
    "route53:ListCidrLocations",
    "route53:ListCidrBlocks",
    "route53:ListTrafficPolicies",
    "route53:ListTrafficPolicyVersions",
    "route53:ListTrafficPolicyInstances",
    "route53:ListQueryLoggingConfigs",
    "route53:GetHostedZone",
    "route53:GetDNSSEC",
    "route53:GetQueryLoggingConfig",
    "route53:GetHealthCheck",
    "route53:GetTrafficPolicy"
    "route53:GetTrafficPolicyInstance",
    "route53:CreateHostedZone",
    "route53:AssociateVPCWithHostedZone",
    "route53:ChangeResourceRecordSets",
    "route53:CreateKeySigningKey",
    "route53:EnableHostedZoneDNSSEC",
    "route53:CreateQueryLoggingConfig",
    "route53:CreateHealthCheck",
    "route53:UpdateHealthCheck",
    "route53:CreateTrafficPolicy",
    "route53:CreateTrafficPolicyVersion",
    "route53:CreateTrafficPolicyInstance",
    "route53:CreateCidrCollection",
    "route53:ChangeCidrCollection",
    "route53resolver:ListResolverEndpoints",
    "route53resolver:ListResolverRules",
    "route53resolver:ListResolverRuleAssociations",
    "route53resolver:ListResolverQueryLogConfigs",
    "route53resolver:ListResolverQueryLogConfigAssociations",
    "route53resolver:ListFirewallRules",
    "route53resolver:ListFirewallDomainLists",
    "route53resolver:ListFirewallRuleGroups",
    "route53resolver:ListFirewallRuleGroupAssociations",
    "route53resolver:GetResolverEndpoint",
    "route53resolver:GetResolverRule",
    "route53resolver:GetResolverRulePolicy",
    "route53resolver:GetResolverRuleAssociation",
    "route53resolver:GetFirewallRuleGroup",
    "route53resolver:GetFirewallDomainList",
    "route53resolver:GetFirewallRuleGroupAssociation",
    "route53resolver:GetResolverQueryLogConfig",
    "route53resolver:GetResolverQueryLogConfigPolicy",
    "route53resolver:GetResolverQueryLogConfigAssociation",
    "route53resolver:CreateResolverEndpoint",
    "route53resolver:CreateResolverRule",
    "route53resolver:AssociateResolverRule",
    "route53resolver:PutResolverRulePolicy",
    "route53resolver:CreateFirewallRuleGroup",
    "route53resolver:AssociateFirewallRuleGroup",
    "route53resolver:CreateFirewallRule",
    "route53resolver:CreateFirewallDomainList",
    "route53resolver:UpdateFirewallDomains",
    "route53resolver:CreateResolverQueryLogConfig",
    "route53resolver:AssociateResolverQueryLogConfig",
    "route53resolver:PutResolverQueryLogConfigPolicy",
    "arc-zonal-shift:ListManagedResources",
    "arc-zonal-shift:GetManagedResource",
    "arc-zonal-shift:CreatePracticeRunConfiguration",
    "arc-zonal-shift:UpdateZonalAutoshiftConfiguration",
    "route53-recovery-control-config:ListClusters",
    "route53-recovery-control-config:ListControlPanels",
    "route53-recovery-control-config:ListRoutingControls",
    "route53-recovery-control-config:ListSafetyRules",
    "route53-recovery-control-config:ListAssociatedRoute53HealthChecks",
    "route53-recovery-control-config:ListTagsForResource"
    "route53-recovery-control-config:DescribeCluster",
    "route53-recovery-control-config:DescribeControlPanel",
    "route53-recovery-control-config:DescribeRoutingControl",
    "route53-recovery-control-config:DescribeSafetyRule",
    "route53-recovery-control-config:CreateCluster",
    "route53-recovery-control-config:CreateControlPanel",
    "route53-recovery-control-config:CreateRoutingControl",
    "route53-recovery-control-config:CreateSafetyRule",
    "route53-recovery-readiness:ListCells",
    "route53-recovery-readiness:ListRecoveryGroups",
    "route53-recovery-readiness:ListReadinessChecks",
    "route53-recovery-readiness:ListResourceSets",
    "route53-recovery-readiness:ListTagsForResources",
    "route53-recovery-readiness:GetCell",
    "route53-recovery-readiness:GetRecoveryGroup",
    "route53-recovery-readiness:GetReadinessCheck",
    "route53-recovery-readiness:GetResourceSet",
    "route53-recovery-readiness:CreateCell",
    "route53-recovery-readiness:CreateRecoveryGroup",
    "route53-recovery-readiness:CreateReadinessCheck",
    "route53-recovery-readiness:CreateResourceSet",
    "route53-recovery-readiness:UpdateCell",
    "route53-recovery-readiness:UpdateRecoveryGroup",
    "route53-recovery-readiness:UpdateReadinessCheck"
    "route53profiles:ListProfiles",
    "route53profiles:ListProfileAssociations",
    "route53profiles:ListProfileResourceAssociations"
    "route53profiles:ListTagsForResource",
    "route53profiles:GetProfile",
    "route53profiles:GetProfileAssociation",
    "route53profiles:GetProfileResourceAssociation",
    "route53profiles:CreateProfile",
    "route53profiles:AssociateProfile",
    "route53profiles:AssociateResourceToProfile"
    ],
    "Resource":"*"
}

After completing the steps in topic Backing up data, the following main groups of resources can be backed up:

Route 53 resources:
- Hosted zones with their records
- CIDR locations
- Health checks
- Traffic policies with their records
- Profile resources with their associations
Route 53 Resolver resources:
- Outbound and inbound endpoints with their rules
- VPC associations
- Logging configurations with their VPC associations
- DNS firewall resources with their domain lists, rules, and VPC associations
Route 53 Application Recovery resources:
- Routing controls resources
- Readiness checks resources
- Zonal autoshift resources

Backing up SaaS application data

Limitation

Only backup data can be stored to the automatically created targets (and not copies of backup data or archive data).

Procedure

Select the SaaS applications and/or resources that you want to back up.

 Note If you want to narrow down the list of displayed SaaS applications, use the filtering options as described in Filtering and sorting data.
Click Set Policy. The Set Policy dialog box opens.
From the list of available policies, select the preferred policy.
Click Assign to assign the policy to the selected SaaS applications and/or resources.

After you assign a policy to a SaaS application, a backup task starts immediately. Subsequent backups are scheduled according to the values defined in the policy.

If required, you can also perform a manual backup of individual SaaS applications and/or resources at any time. For details, see Performing manual backups.