Restoring data

R-Cloud enables you to restore an entire SaaS application or its resources to a specific point in time.

R-Cloud allows you to restore your protected Google Cloud SQL data at the following levels:

  • Instance

  • Database

Considerations

  • The R-Cloud module for Google Cloud SQL restores data using a temporary Google Cloud bucket.

    • Temporary buckets are created in the destination project and the region of the selected resource.

    • Temporary buckets are not deleted automatically. In case of a failed restore, data will be deleted after seven days.

    • Temporary buckets follow this naming convention: hycu-cloudsql-{project_name}-{region}.

Instance restore

The following options are available when performing an instance restore:

  • Restore the original instance and the included resources. This overwrites the original instance (in-place restore).

  • Restore the instance and the included resources to a new instance with a different name.

Important  The module generates a root password when creating a new instance. Change the password after the restore is complete.

In-place restore for the primary instance and its replicas

To successfully complete the in-place restore for the Google Cloud SQL primary instance and its replicas, perform the following steps:

  1. In Google Cloud, manually delete all the Google Cloud SQL replicas of the primary instance.

  2. In R-Cloud, restore the Google Cloud SQL primary instance.

  3. In Google Cloud, manually re-create the replicas of the restored primary instance.

Database restore

R-Cloud allows you to restore one or more databases to a selected Google SQL instance.

When selecting an instance to restore the databases, define the suffix to be appended to the original database name in R-Cloud.

Example  <original_database_name>_<databaseNameSuffix>

If you select the override option, both the instance selector and the suffix field are hidden. The databases will be restored using the original name and override the existing database.

Important  To prevent an unwanted deletion, adding the suffix to the PostgreSQL system database name is mandatory.

The PostgreSQL system database is restored under a different name as a standard database. As a result, the restored PostgreSQL system database cannot be used for restoring the users and the roles on a Google Cloud SQL instance.

The users and the roles must be created manually by completing the following steps:

  1. Create new PostgreSQL instance.

  2. In Google Cloud console, create the users and the roles on the restored instance.

  3. Restore the databases into the restored instance.

Restoring a SaaS application or its resources

Prerequisites

  • Only if you plan to restore the SaaS application or its resource to a different source. Your SaaS application must support restoring data to a different source and more than one source (that is, more than one R-Cloud module of the same type) must be added to R‑Cloud.

  • Only if the R-Cloud module does not support using a staging target. If you want to restore SaaS application data that is stored in the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage class, or in the Azure Archive tier, contact HYCU Support.

Limitation

If your data is stored as a snapshot, you cannot restore it to a different source.

Considerations

  • Only one restore task can run at the same time for a SaaS application or its resource.
  • Only if a SaaS application resource is deleted from cloud. If the deleted resource has at least one valid restore point available in R‑Cloud, it is considered protected and its status is Protected deleted.

To access the SaaS panel, in the navigation pane, click SaaS SaaS.

Procedure

  1. In the SaaS panel, click the SaaS application or the resource that you want to restore. The Detail view appears at the bottom of the screen.

    Note  The Detail view appears only if you click a SaaS application. Selecting the check box before the name of the SaaS application does not open the Detail view.

  2. If you know which restore point you want to use for the restore, in the Detail view, select the preferred restore point, and then click Restore Restore. Otherwise, click Search Search to search the multiple versions for the data that you want to restore.

  3. Only if you clicked the Restore option in the previous step and the selected restore point has more than one selectable tier. From the Restore From drop-down menu, select which tier you want to use for the restore, and then click Next.

    Your restore point can contain one or more tiers among which you can select:

    • Automatic: This option ensures the fastest and most cost-effective restore.

    • Backup (Snapshot)

    • Backup (Target)

    • Copy

    • Archive—(daily, weekly, monthly, yearly)

  4. Select the resource that you want to restore. You can filter the resources in the following ways:

    • By using the Search field on the left side of the table. Typing text in this field automatically filters and displays only the matching items. You can limit the scope of your search in the following ways:

      • From the Object Type drop-down menu, select the object type of the resource that you want to restore.

      • From the Version drop-down menu, select All Versions to display and search all available versions of the SaaS application data, or select a specific version. If you selected a restore point at the start of the restore procedure, that version is preselected.

      • From the Paths drop-down menu, select Current Path to limit your search to the currently selected path, or All Paths to search all paths.

    • By using the filtering option:

      1. On the right side of the table, click Filters Filters.

      2. In the side panel that opens, select your filter criteria.

      3. Click Apply Filters.

    If needed, click or to move between the pages, or enter a page number to go directly to that page. You can also adjust the number of items shown on a page.

  5. Depending on whether you started the restore procedure by clicking the Restore option or the Search option, click Next or Restore to continue to the next step.

  6. Only if restore options specific to your SaaS application are available. Specify which of the available restore options you want to use and provide the required information.

  7. Click Restore.

Exporting SaaS application data

R‑Cloud enables you to export specific objects within the SaaS application resources to a target. This is useful, for example, if the related SaaS service is not available and the entire SaaS application cannot be restored, or if you need to retrieve your SaaS application data for legal compliance reasons.

Prerequisites

  • The target to which you plan to export SaaS application data must be added to R‑Cloud. For instructions, see Setting up targets.

  • Only if the R-Cloud module does not support using a staging target. If you want to export SaaS application data that is stored in the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage class, or in the Azure Archive tier, contact HYCU Support.

Limitation

You cannot export SaaS application data from a snapshot.

Procedure

  1. In the SaaS panel, click the SaaS application or resource whose data you want to export. The Detail view appears at the bottom of the screen.

    Note  The Detail view appears only if you click a SaaS application. Selecting the check box before the name of the SaaS application does not open the Detail view.

  2. If you know which restore point you want to use for the export, in the Detail view, select the preferred restore point, and then click Export Export. Otherwise, click Search Search to search the multiple versions for the data that you want to export.

  3. Only if you clicked the Export option in the previous step and the selected restore point has more than one selectable tier. From the Restore From drop-down menu, select which tier you want to use for the export, and then click Next.

    Your restore point can contain one or more tiers among which you can select:

    • Automatic: This option ensures the fastest and most cost-effective export.

    • Backup (Snapshot)

    • Backup (Target)

    • Copy

    • Archive—(daily, weekly, monthly, yearly)

  4. Select the resources that you want to export. You can filter the resources in the following ways:

    • By using the Search field on the left side of the table. Typing text in this field automatically filters and displays only the matching items. You can limit the scope of your search in the following ways:

      • From the Object Type drop-down menu, select the object type of the resource that you want to export.

      • From the Version drop-down menu, select All Versions to display and search all available versions of the SaaS application data, or select a specific version. If you selected a restore point at the start of the export procedure, that version is preselected.

      • From the Paths drop-down menu, select Current Path to limit your search to the currently selected path, or All Paths to search all paths.

    • By using the filtering option:

      1. On the right side of the table, click Filters Filters.

      2. In the side panel that opens, select your filter criteria.

      3. Click Apply Filters.

    If needed, click or to move between the pages, or enter a page number to go directly to that page. You can also adjust the number of items shown on a page.

  5. Depending on whether you started the export procedure by clicking the Export option or the Search option, click Next or Export to continue to the next step.

  6. From the Target drop-down menu, select the target to which you want to export the data.

  7. In the Destination Path on the Target field, enter the path that will be used in the name of the exported file. The default value is the time when the export procedure was started, represented as the Unix epoch.

  8. Click Export.