Setting up targets

Targets are locations where protected data is stored. In addition to using targets to store protected data, R‑Cloud also allows you to define a snapshot as a location for storing your data.

Setting up targets includes the following tasks:

Task Instructions

  1. Get familiar with backup target types in R‑Cloud.

 Backup target types in R‑Cloud

  1. Set up the preferred targets.

Depending on which target type you want to set up, see one of the following topics:

Backup target types in R‑Cloud

You can define a target or a snapshot as a location where protected data is stored by selecting the preferred backup target type in the R‑Cloud policy. For details on backup target types, see the following topics:

Target

Protected data can be stored on targets that you create yourself or R‑Cloud creates for you automatically.

Caution  Never delete any targets used by R‑Cloud because this may result in data loss. Additionally, within targets, ensure that the hycu/backups/ folders are always kept intact.

You can create Amazon S3 buckets, Azure storage accounts, Google Cloud buckets, or S3 compatible buckets and set them up as targets in R‑Cloud.

R‑Cloud can automatically create Amazon S3 or Google Cloud targets while backing up data. These targets are always created in the same region as the entities that you are protecting, unless you are protecting SaaS applications that do not run in AWS or Google Cloud. In this case, the targets are created in the default region of any or Google Cloud project that was added to R‑Cloud as a source, or in the default region of any AWS account or Google Cloud project in which a manually created target resides.

Important  Automatically created targets are not available if you are protecting the following entities:

  • SAP HANA applications

  • SaaS applications that are related to R-Cloud modules that support storing data on a staging target

For R-Cloud modules that do not support storing data on a staging target, automatically created targets are available only for storing backup data of the related SaaS applications (and not copies of backup data or archive data).

The same target is used for storing the protected data of multiple entities where possible. You can use these targets also for storing your data.

For the target naming conventions, see Resources created by R‑Cloud.

Note  Only if you plan to protect SaaS applications. If the R-Cloud module supports storing data on a staging target, R‑Cloud uses a staging target either to temporarily store SaaS application data before it is moved to the target that you define in the R‑Cloud policy, or to store SaaS application data as a snapshot. For details on staging targets and how to add them to R‑Cloud, see Adding R-Cloud modules.

Snapshot

If you are protecting SaaS applications, GKE applications using persistent volumes, or instances, you can define a snapshot as a location for storing backup data. Snapshots that are created by R‑Cloud are stored at the following locations:

  • For SaaS applications: On staging targets or remote storage.

  • For GKE applications using persistent volumes: On clusters on which the GKE applications are deployed.

  • For AWS instances: In the AWS account that contains the instances.

  • For Google Cloud instances: In the Google Cloud project that contains the instances.

If snapshots created by R‑Cloud are deleted from any of these locations, you will not be able to restore backup data from this location. However, you can still restore your data from targets if copies of backup data or data archives exist.

For the snapshot naming conventions, see Resources created by R‑Cloud.