Restoring instances

R‑Cloud enables you to restore an entire instance or its individual disks to a specific point in time, or multiple instances or disks belonging to multiple instances in a single session. In the event of a disaster in your environment, you can also restore instance data to a different cloud platform by using the Move Instance restore option.

Prerequisites

  • Only if you plan to specify post-restore scripts.

    • Access to the instance file system must be enabled. For instructions, see Enabling access to data.

    • A script must be available in an accessible folder.

    • The user account must have permissions to run a script on the instance.

  • For AWS: Before restoring an instance to the same or a different VPC, subnet, or region, make sure the following prerequisites are met in the location of the instance:

    • In a VPC without public IPs or in subnets without public IPs, you must create the following VPC endpoints:

      • Interface endpoints: Amazon EC2 (ec2), AWS Security Token Service (sts), Amazon SQS (sqs), and Amazon SNS (sns)

      • Gateway endpoint for Amazon S3

      For details on how to enable Amazon VPC endpoints, see AWS documentation.

    • The security group that the instance belongs to must have an inbound firewall rule for port 443 (HTTPS), source IP 0.0.0.0/0 and an outbound firewall rule for port 443 (HTTPS), destination IP 0.0.0.0/0.

      For instructions on how to configure and apply the network firewall rule, see AWS documentation.

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 the instance.
  • Only if you plan to specify post-restore scripts. The scripts are run from the home directory of the user account that R‑Cloud uses for running the scripts.

  • Depending on the operating system on the instance, the following user accounts are used:

    • For AWS instances: The user account that is assigned to the instance in R‑Cloud through a credential group.

    • For Google Cloud instances running Linux:

      • The instance has no credential group assigned in R‑Cloud: The HYCU Managed Service Account (HMSA).

      • The instance has a credential group assigned: The user account specified in the credential group.

    • For Google Cloud instances running Windows: The user account that is assigned to the instance in R‑Cloud by means of a credential group.

Depending on what you plan to restore, see one of the following topics:

I plan to restore... Instructions
A single instance or its disks. Restoring a single instance or its disks
Multiple instances or disks belonging to multiple instances in a single session. Restoring multiple instances or disks belonging to multiple instances in a single session

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

Restoring a single instance or its disks

When you restore a single instance or its disks, you can select among the following options:

Option Description Instructions
Restore Instance Enables you to restore an instance and its disks to the original location with the same settings.

Restoring an instance

Restore Disks Enables you to restore disks and attach them to the same instance. Restoring disks
Clone Instance Enables you to restore an instance and its disks by creating a clone of the instance. Cloning an instance
Clone Disks Enables you to restore disks by creating their clones and attaching them to the same or a different instance, or by creating their clones in the same or a different source and zone and leaving them unattached. Cloning disks
Move Instance Enables you to move an instance by restoring it to a different cloud platform. Moving an instance
Move Disks Enables you to move disks by restoring them and attaching them to an instance on a different cloud platform, or by restoring them to a different cloud platform and leaving them unattached. Moving disks

Restoring an instance

You can restore an instance and its disks to the original location with the same settings. In this case, you replace the original instance with the restored one.

Consideration

Any data changes after the last successful backup are not protected and therefore cannot be restored.

Procedure

  1. In the Instances panel, click the instance that you want to restore to open the Detail view.

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

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.

  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.

  4. Select Restore Options, and then click Next.

  5. Select Restore Instance, and then click Next.

  6. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  7. From the Disks drop-down menu, select the instance disks that you want to restore.

    Note  All disks of the instance are preselected for the restore. With such selection, the entire instance is restored. The boot disk is restored even if you do not select it.

  8. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run on the instance after the restore.

    Note  You can enter any command that the command-line interface of your instance supports.

  9. Click Restore.

Restoring disks

You can restore disks and attach them to the same instance. In this case, you replace the original disks with the restored ones.

Procedure

  1. In the Instances panel, click the instance whose disks you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.
  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.
  4. Select Restore Options, and then click Next.
  5. Select Restore Disks, and then click Next.

  6. From the list of disks that are available for the restore, select the ones that you want to restore, and then click Next.

    Note  If you select the boot disk, the instance will be shut down and restarted when the disks are restored.

  7. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  8. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run after the restore on the instance to which the restored disks are attached.

    Note  You can enter any command that the command-line interface of your instance supports.

  9. Click Restore.

Cloning an instance

You can clone an instance by restoring it to its original or a new location with custom settings. In this case, you create a new instance containing the restored data alongside the original instance. When cloning an instance, you can change the following properties: the selection of the backed-up disks, the destination source, region, and zone, and the instance network configuration.

For details on how to clone AWS and Google Cloud instances, see the following topics:

Cloning an AWS instance

Limitations

  • You cannot restore instances that belong to a deleted AWS account. Such instances are not listed in the Instances panel of the R‑Cloud web user interface.

  • You cannot restore an instance to a different source or AWS region from a snapshot.

  • For instances running Windows: Using post-restore scripts is not supported.

Procedure

  1. In the Instances panel, click the instance that you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.

  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.

  4. Select Clone Options, and then click Next.

  5. Select Clone Instance, and then click Next.

  6. In the New instance name field, specify a new name for the instance.

  7. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  8. Only if the original operating system image was not found. From the Image drop-down menu, select the operating system image you want to use.

    To use a custom image, select Use custom image and enter the image AMI ID.

  9. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run on the restored instance after the restore.

    Note  You can enter any command that the command-line interface of your instance supports.

  10. From the Destination source drop-down menu, select the source to which you want to restore the instance. The original source of the instance is preselected. You can choose from sources that belong to the currently selected protection set and that your user account can access.

  11. From the Destination region and Destination zone drop-down menus, select the AWS region and zone to which you want to restore the instance. The original region and zone of the instance are preselected.

  12. Under Disk name, do the following:

    1. Select the instance disks that you want to restore.

      Note  All disks of the instance are preselected for the restore. With such selection, the entire instance is restored. The boot disk is restored even if you do not select it.

    2. Edit the disks as required. For each selected disk, do the following:

      1. Click Edit Edit Disk.

      2. Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:

        1. In the New device name field, enter a name for the restored disk device.

        2. In the New disk name field, enter a name for the restored disk.

      3. If you want to change the disk type, from the Disk type drop-down menu, select one of the available disk types for the restored disk. By default, the original disk type is selected.

        The list shows only the disk types that match the required disk size and can include the following disk types: General Purpose SSD, Previous Generation Volume, and Provisioned IOPS SSD.

        If you selected Provisioned IOPS SSD or General Purpose SSD, enter the IOPS number.

      4. Only if you want to add labels to the restored disk.

        1. Click Advanced.

        2. Click Manage Manage. The Custom Metadata dialog box opens.

        3. Enter a key and a value, and then click Add for each label that you want to add.

          Note  If the selected disk already has one or more labels added, they are listed under Labels. If you want to delete any of the added labels, click Delete Delete next to it.

      5. Click Save.

  13. Under Network interfaces, review the list of networks that the original instance was configured in at the time of backup. The list shows the following for each such network:

    • VPC ID

    • Subnet ID

    For each configured network interface, you can separately adjust its public and private IP address types. By default, the public IP address configuration of the original instance is kept.

    If you want to modify network settings, you can add an additional network interface, edit an existing network interface, or delete a network interface:

    • Click Add network interface to add a network interface or click Edit Edit next to the network interface that you want to edit, and then follow these steps:

      1. From the Subnet drop-down menu, select the subnet.
      2. From the Security group drop-down menu, select the security group.

      3. In the Public address type field, select the public IP address for the network interface. You can select among the following options:

        Option Description
        None

        The network interface does not use a public IP address.

        This option is preselected if the network interface of the original instance did not use a public IP address.
        Auto-assign

        The network interface uses an automatically allocated public IP address.

        This option is preselected if the network interface of the original instance used a public IP address.

        Note  Auto-assign will not work if the Auto-assign public IPv4 address on a subnet option is set to No or if more than one network interface is specified.
        Elastic IP (Reserved) The network interface uses an elastic public IP address that was reserved in Amazon EC2 in advance.
        Elastic IP (New)

        The network interface uses a new elastic public IP address.

        Note  Allocation of the IP address in Amazon EC2 is performed at the very beginning of the restore. If the allocation fails, the restore task is terminated without being logged.

      4. In the Private address type field, select the private IP address for the network interface. You can select between the following options:

        Option Description
        Auto-assign

        The network interface uses an automatically allocated private IP address.

        This option is selected by default.
        Custom

        The network interface uses a private IP address that is defined by you.

        Important  Use of this option might result in IP address conflicts.

      5. Click Add or Save.

    • Click Delete Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.

  14. Only if you want to add tags to the restored instance.

    1. Click Advanced.

    2. For each custom metadata tag that you want to add, click Manage Manage.

    3. Enter a key and a value, and then click Add.

      Note  If the selected instance already has one or more custom metadata tags added, they are listed under Custom metadata. If you want to delete any of the added custom metadata tags, click Delete Delete next to it.

  15. Click Restore.

Cloning a Google Cloud instance

Limitation

You cannot restore instances that belong to a deleted Google Cloud project. Such instances are not listed in the Instances panel of the R‑Cloud web user interface.

Considerations

Only if you plan to replicate disks.

  • The boot disk cannot be replicated.

  • Standard persistent disks smaller than 200 GiB cannot be replicated.

  • Regional disks can be replicated only across two zones in the same region. One of these zones must be the same as the zone of the target instance.

  • If the region or zone of the target instance changes, all regional disks are automatically converted to zonal disks. In this case, the procedure of replicating the disks must be performed again.

Procedure

  1. In the Instances panel, click the instance that you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.

  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.

  4. Select Clone Options, and then click Next.

  5. Select Clone Instance, and then click Next.

  6. In the New instance name field, specify a new name for the instance.

  7. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  8. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run on the restored instance after the restore.

    Note  You can enter any command that the command-line interface of your instance supports.

  9. From the Destination source drop-down menu, select the source to which you want to restore the instance. The original source of the instance is preselected. You can choose from sources that belong to the currently selected protection set and that your user account can access.

  10. From the Destination region and Destination zone drop-down menus, select the Google Cloud region and zone to which you want to restore the instance. The original region and zone of the instance are preselected.

  11. Under Disk name, do the following:

    1. Select the instance disks that you want to restore.

      Note  All disks of the instance are preselected for the restore. With such selection, the entire instance is restored. The boot disk is restored even if you do not select it.

    2. Edit the disks as required. For each selected disk, do the following:

      1. Click Edit Edit Disk.

      2. Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:

        1. In the New device name field, enter a name for the restored disk device.

        2. In the New disk name field, enter a name for the restored disk.

      3. If you want to change the disk type, from the Disk type drop-down menu, select one of the available disk types for the restored disk Standard persistent disk, Balanced persistent disks, or SSD persistent disk). By default, the original disk type is selected.

      4. If you want to replicate data between two zones in the region of the instance, make sure the Replicate this disk within region check box is selected, and then, from the Target zone drop-down menu, select to which zone you want to replicate data. If the selected disk was regional at backup time, the two zones across which the disk is replicated are shown, otherwise, a list of all zones in the region of the instance is shown.

      5. Only if you want to add labels to the restored disk.

        1. Click Advanced.

        2. Click Manage Manage. The Custom Metadata dialog box opens.

        3. Enter a key and a value, and then click Add for each label that you want to add.

          Note  If the selected disk already has one or more labels added, they are listed under Labels. If you want to delete any of the added labels, click Delete Delete next to it.

      6. Click Save.

  12. Under Network Interfaces, review the list of networks that the original instance was configured in at the time of backup. The list shows the following for each such network:

    • Network type: Subnetwork for VPC networks and shared VPC networks, Legacy for legacy networks

    • Subnetwork name (for VPC networks and shared VPC networks) or network name (for legacy networks)

    • Only in case of a shared VPC network. Name of the host project of the network

    For each configured network interface, you can separately adjust its public and private IP address types. By default, the public IP address configuration of the original instance is kept.

    If you want to modify network settings, you can add an additional network interface, edit an existing network interface, or delete a network interface:

    • Click Add network interface to add a network interface or click Edit Edit next to the network interface that you want to edit, and then follow these steps:

      1. From the Destination network drop-down menu, select the destination network.

      2. In the Public address type field, select the public IP address for the network interface. You can select among the following options:

        Option Description
        None

        The network interface does not use a public IP address.

        This option is preselected if the network interface of the original instance did not use a public IP address.
        Ephemeral

        The network interface uses an automatically allocated public IP address.

        This option is preselected if the network interface of the original instance used a public IP address.
        Static (Reserved) The network interface uses a static public IP address that was reserved in Google Compute Engine in advance.
        Static (New) The network interface uses a static public IP address that is allocated at the time of the restore. If the allocation fails, the instance is assigned a temporary public IP address. Such fallback also sets the restore task status to Done with errors.

      3. In the Private address type field, select the private IP address for the network interface. You can select between the following options:

        Option Description
        Ephemeral (Automatic)

        The network interface uses an automatically allocated private IP address.

        This option is selected by default for the preselected network interfaces.
        Ephemeral (Custom)

        The network interface uses a private IP address that is defined by you.

        Important  Use of this option might result in IP address conflicts.
        Static (Reserved) Not available for legacy networks. The network interface uses a static private IP address that was reserved in Google Compute Engine or in advance.
        Static (New)

        Not available for legacy networks. The network interface uses a new static private IP address that is defined by you.

        Note  Allocation of the IP address in Google Compute Engine is performed at the very beginning of the restore. If the allocation fails, the restore task is terminated without being logged.

      4. Click Add or Save.

    • Click Delete Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.

  13. Only if you want to add tags and/or labels to the restored instance.

    1. Click Advanced.

    2. For each label, network tag, or custom metadata tag that you want to add, click Manage Manage.

    3. Enter a key and a value, and then click Add.

      Note  If the selected instance already has one or more labels, network tags, and/or custom metadata tags added, they are listed under Labels, Network tags, or Custom metadata. If you want to delete any of the added labels, network tags, and/or custom metadata tags, click Delete Delete next to it.

  14. Click Restore.

Cloning disks

You can create clones of disks by restoring them and attaching them to the same or a different instance, or by restoring them to the same or a different source, region, or zone and leaving them unattached. In this case, the original disks will not be overwritten.

Limitations

  • You can attach the restored disks only to an instance that is running the same operating system as the original instance and that belongs to the same protection set as the original instance.

  • You cannot restore disks to a different source or region from a snapshot.

  • Only if you plan to restore disks to a different source and leave them unattached. The default network must be set for the source to which you plan to restore the disks, or the source to which you plan to restore the disks must have the same network as the instance whose disks you plan to restore.

Considerations

  • Only if you are restoring Google Cloud instance disks and you plan to replicate disks.

    • The boot disk cannot be replicated.

    • Standard persistent disks smaller than 200 GiB cannot be replicated.

    • Regional disks can be replicated only across two zones in the same region. One of these zones must be the same as the zone of the destination instance.

    • If the region or zone of the destination instance changes, all regional disks are automatically converted to zonal disks. In this case, the procedure of replicating the disks must be performed again.

Procedure

  1. In the Instances panel, click the instance whose disks you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.
  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.
  4. Select Clone Options, and then click Next.
  5. Select Clone Disks, and then click Next.
  6. From the list of disks that are available for the restore, select the ones that you want to restore, and then click Next.

  7. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  8. Select the source, the region, and the zone that contain the instance to which you want to attach the restored disks.

  9. From the Destination instance drop-down menu, select the instance to which you want to attach the restored disks. If you do not want to attach the disks to an instance, select None (Leave unattached).

  10. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run after the restore on the instance to which the restored disks are attached.

    Note  You can enter any command that the command-line interface of your instance supports.

  11. Edit the disks as required. For each selected disk, do the following:

    1. Click Edit Edit Disk.

    2. Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:

      1. In the New device name field, enter a name for the restored disk device.

      2. In the New disk name field, enter a name for the restored disk.

    3. If you want to change the disk type, from the Disk type drop-down menu, select one of the available disk types for the restored disk. By default, the original disk type is selected. The following disk types are available:

      • For Google Cloud: Standard persistent disk, Balanced persistent disks, and SSD persistent disk.

      • For AWS: General Purpose SSD, Previous Generation Volume, and Provisioned IOPS SSD.

      If you selected Provisioned IOPS SSD or General Purpose SSD, enter the IOPS number.

    4. Only if you are restoring Google Cloud instance disks. If you want to replicate data between two zones in the region of the instance, make sure the Replicate this disk within region check box is selected, and then, from the Target Zone drop-down menu, select to which zone you want to replicate data. If the selected disk was regional at backup time, the two zones across which the disk is replicated are shown, otherwise, a list of all zones in the region of the instance is shown.

    5. Only if you want to add labels to the restored disk.

      1. Click Advanced.

      2. Click Manage Manage. The Custom Metadata dialog box opens.

      3. Enter a key and a value, and then click Add for each label that you want to add.

        Note  If the selected disk already has one or more labels added, they are listed under Advanced. If you want to delete any of the added labels, click Delete Delete next to it.

    6. Click Save.
  12. Click Restore.

Moving an instance

You can move instances across different cloud platforms (AWS and Google Cloud) by restoring them to the preferred platform. In this case, the original instance will be kept.

For details on how to move instances to AWS and Google Cloud, see the following topics:

Moving an instance to AWS

Limitation

You cannot restore an instance to a different cloud platform from a snapshot.

Procedure

  1. In the Instances panel, click the instance that you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.

  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.

  4. Select Move Options, and then click Next.

  5. Select Move Instance, and then click Next.

  6. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  7. From the Destination source drop-down menu, select the source to which you want to restore the instance. You can choose from sources that belong to the currently selected protection set and that your user account can access.

  8. Click Next.

  9. In the New instance name field, enter the name for the instance.

  10. Only if the original operating system image was not found. From the Image drop-down menu, select the operating system image you want to use.

    To use a custom image, select Use custom image and enter the image AMI ID.

  11. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run on the restored instance after the restore.

    Note  You can enter any command that the command-line interface of your instance supports.

  12. From the Destination region and Destination zone drop-down menus, select the AWS region and zone to which you want to restore the instance.

  13. In the vCPU cores field, enter the number of virtual CPUs for the restored instance multiplied by the number of cores per virtual CPU.

  14. In the Memory field, set the amount of memory (in GiB) for the restored instance. The default value is the amount of memory in GiB of the original instance.

  15. From the Instance type drop-down menu, select the instance type for the restored instance.

    Note  The list shows instance types that match the specified number of virtual CPUs and amount of memory, and the boot type of the instance you are moving to cloud (BIOS or UEFI). If no instance type exactly corresponds to the specified values, the closest matches are shown.

  16. Under Disk name, do the following:

    1. Select the disks that you want to restore.

      Note  All disks of the instance are preselected for the restore. With such selection, the entire instance is restored. The boot disk is restored even if you do not select it.

    2. Edit the disks as required. For each selected disk, do the following:

      1. Click Edit Edit Disk.

      2. Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:

        1. In the New device name field, enter a name for the restored disk device.

        2. In the New disk name field, enter a name for the restored disk.

      3. If you want to change the disk type, from the Disk type drop-down menu, select one of the available disk types for the restored disk. By default, the original disk type is selected.

        The list shows only the disk types that match the required disk size and can include the following disk types: General Purpose SSD, Previous Generation Volume, and Provisioned IOPS SSD.

        If you selected Provisioned IOPS SSD or General Purpose SSD, enter the IOPS number.

      4. Only if you want to add labels to the restored disk.

        1. Click Advanced.

        2. Click Manage Manage. The Custom Metadata dialog box opens.

        3. Enter a key and a value, and then click Add for each label that you want to add.

          Note  If the selected disk already has one or more labels added, they are listed under Labels. If you want to delete any of the added labels, click Delete Delete next to it.

      5. Click Save.

  17. Under Network interfaces, review the list of networks that are available in the selected AWS zone.

    For each configured network interface, you can separately adjust its public and private IP address types. By default, the public IP address configuration of the original instance is kept.

    If you want to modify network settings, you can add an additional network interface, edit an existing network interface, or delete a network interface:

    • Click Add network interface to add a network interface or click Edit Edit next to the network interface that you want to edit, and then follow these steps:

      1. From the Subnet drop-down menu, select the subnet.
      2. From the Security group drop-down menu, select the security group.

      3. In the Public address type field, select the public IP address for the network interface. You can select among the following options:

        Option Description
        None

        The network interface does not use a public IP address.

        This option is preselected if the network interface of the original instance did not use a public IP address.
        Auto-assign

        The network interface uses an automatically allocated public IP address.

        This option is preselected if the network interface of the original instance used a public IP address.

        Note  Auto-assign will not work if the Auto-assign public IPv4 address on a subnet option is set to No or if more than one network interface is specified.
        Elastic IP (Reserved) The network interface uses an elastic public IP address that was reserved in Amazon EC2 in advance.
        Elastic IP (New)

        The network interface uses a new elastic public IP address.

        Note  Allocation of the IP address in Amazon EC2 is performed at the very beginning of the restore. If the allocation fails, the restore task is terminated without being logged.

      4. In the Private address type field, select the private IP address for the network interface. You can select between the following options:

        Option Description
        Auto-assign

        The network interface uses an automatically allocated private IP address.

        This option is selected by default.
        Custom

        The network interface uses a private IP address that is defined by you.

        Important  Use of this option might result in IP address conflicts.

      5. Click Add or Save.

    • Click Delete Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.

  18. Only if you want to add tags to the restored instance.

    1. Click Advanced.

    2. For each custom metadata tag that you want to add, click Manage Manage.

    3. Enter a key and a value, and then click Add.

      Note  If the selected instance already has one or more custom metadata tags added, they are listed under Custom metadata. If you want to delete any of the added custom metadata tags, click Delete Delete next to it.

  19. Click Restore.

Moving an instance to Google Cloud

Limitation

You cannot restore an instance to a different cloud platform from a snapshot.

Procedure

  1. In the Instances panel, click the instance that you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.

  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.

  4. Select Move Options, and then click Next.

  5. Select Move Instance, and then click Next.

  6. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  7. From the Destination source drop-down menu, select the source to which you want to restore the instance. You can choose from sources that belong to the currently selected protection set and that your user account can access.
  8. Click Next.
  9. In the New instance name field, specify a new name for the instance.
  10. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run on the restored instance after the restore.

    11. Note  You can enter any command that the command-line interface of your instance supports.

  11. From the Destination region and Destination zone drop-down menus, select the Google Cloud region and zone to which you want to restore the instance.

  12. In the vCPU cores field, enter the number of virtual CPUs for the restored instance multiplied by the number of cores per virtual CPU.

  13. In the Memory field, set the amount of memory (in GiB) for the restored instance.

  14. From the Instance type drop-down menu, select the instance type for the restored instance.

    Note  The list shows instance types that match the specified number of virtual CPUs and amount of memory, and the boot type of the instance you are moving to cloud (BIOS or UEFI). If no such match exists, you can select the custom machine type. For more information about machine types, see Google Cloud documentation.

  15. Under Disk name, do the following:

    1. Select the instance disks that you want to restore.

      Note  All disks of the instance are preselected for the restore. With such selection, the entire instance is restored. The boot disk is restored even if you do not select it.

    2. Edit the disks as required. For each selected disk, do the following:

      1. Click Edit Edit Disk.

      2. Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:

        1. In the New device name field, enter a name for the restored disk device.

        2. In the New disk name field, enter a name for the restored disk.

      3. If you want to change the disk type, from the Disk type drop-down menu, select one of the available disk types for the restored disk Standard persistent disk, Balanced persistent disks, or SSD persistent disk). By default, the original disk type is selected.

      4. Only if you want to add labels to the restored disk.

        1. Click Advanced.

        2. Click Manage Manage. The Custom Metadata dialog box opens.

        3. Enter a key and a value, and then click Add for each label that you want to add.

          Note  If the selected disk already has one or more labels added, they are listed under Labels. If you want to delete any of the added labels, click Delete Delete next to it.

      5. Click Save.

  16. Under Network interfaces, review the list of networks that are available in the selected Google Cloud zone.

    For each configured network interface, you can separately adjust its public and private IP address types. By default, the public IP address configuration of the original instance is kept.

    If you want to modify network settings, you can add an additional network interface, edit an existing network interface, or delete a network interface:

    • Click Add network interface to add a network interface or click Edit Edit next to the network interface that you want to edit, and then follow these steps:

      1. From the Destination network drop-down menu, select the destination network.

      2. In the Public address type field, select the public IP address for the network interface. You can select among the following options:

        Option Description
        None

        The network interface does not use a public IP address.

        This option is preselected if the network interface of the original instance did not use a public IP address.
        Ephemeral

        The network interface uses an automatically allocated public IP address.

        This option is preselected if the network interface of the original instance used a public IP address.
        Static (Reserved) The network interface uses a static public IP address that was reserved in Google Compute Engine in advance.
        Static (New) The network interface uses a static public IP address that is allocated at the time of the restore. If the allocation fails, the instance is assigned a temporary public IP address. Such fallback also sets the restore task status to Done with errors.

      3. In the Private address type field, select the private IP address for the network interface. You can select between the following options:

        Option Description
        Ephemeral (Automatic)

        The network interface uses an automatically allocated private IP address.

        This option is selected by default for the preselected network interfaces.
        Ephemeral (Custom)

        The network interface uses a private IP address that is defined by you.

        Important  Use of this option might result in IP address conflicts.
        Static (Reserved) Not available for legacy networks. The network interface uses a static private IP address that was reserved in Google Compute Engine or in advance.
        Static (New)

        Not available for legacy networks. The network interface uses a new static private IP address that is defined by you.

        Note  Allocation of the IP address in Google Compute Engine is performed at the very beginning of the restore. If the allocation fails, the restore task is terminated without being logged.

      4. Click Add or Save.

    • Click Delete Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.

  17. Only if you want to add tags and/or labels to the restored instance.

    1. Click Advanced.

    2. For each label, network tag, or custom metadata tag that you want to add, click Manage Manage.

    3. Enter a key and a value, and then click Add.

      Note  If the selected instance already has one or more labels, network tags, and/or custom metadata tags added, they are listed under Labels, Network tags, or Custom metadata. If you want to delete any of the added labels, network tags, and/or custom metadata tags, click Delete Delete next to it.

  18. Click Restore.

Moving disks

You can move disks by restoring them and attaching them to an instance on a different cloud platform, or by restoring them to a different cloud platform and leaving them unattached. In this case, the original disks will be kept.

Limitation

You cannot restore disks to a different cloud platform from a snapshot.

Procedure

  1. In the Instances panel, click the instance whose disks you want to restore to open the Detail view.

    Note  The Detail view appears only if you click an instance. Selecting the check box before the name of the instance will not open the Detail view.

  2. In the Detail view that appears at the bottom of the screen, select the preferred restore point.
  3. Click Restore Instance Restore Instance. The Restore Options dialog box opens.
  4. Select Move Options, and then click Next.
  5. Select Move Disks, and then click Next.

  6. From the Restore from drop-down menu, select which tier you want to use for the restore. 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)

  7. From the Destination source drop-down menu, select the source to which you want to restore the instance. You can choose from the sources that belong to the currently selected protection set and that your user account can access.
  8. Click Next.
  9. From the list of disks that are available for the restore, select the ones that you want to restore, and then click Next.

  10. Select the region and the zone that contain the instance to which you want to attach the restored disks.

  11. From the Destination instance drop-down menu, select the instance to which you want to attach the restored disks. If you do not want to attach the disks to an instance, select None (Leave unattached).

  12. Optional. In the Post-restore script field, enter the path to the script or a command that R‑Cloud should run after the restore on the instance to which the restored disks are attached.

    Note  You can enter any command that the command-line interface of your instance supports.

  13. Edit the disks as required. For each selected disk, do the following:

    1. Click Edit Edit Disk.

    2. Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:

      1. In the New device name field, enter a name for the restored disk device.

      2. In the New disk name field, enter a name for the restored disk.

    3. If you want to change the disk type, from the Disk type drop-down menu, select one of the available disk types for the restored disk. By default, the original disk type is selected. The following disk types are available:

      • For Google Cloud: Standard persistent disk, Balanced persistent disks, and SSD persistent disk.

      • For AWS: General Purpose SSD, Previous Generation Volume, and Provisioned IOPS SSD.

      If you selected Provisioned IOPS SSD or General Purpose SSD, enter the IOPS number.

    4. Only if you want to add labels to the restored disk.

      1. Click Advanced.

      2. Click Manage Manage. The Custom Metadata dialog box opens.

      3. Enter a key and a value, and then click Add for each label that you want to add.

        Note  If the selected disk already has one or more labels added, they are listed under Advanced. If you want to delete any of the added labels, click Delete Delete next to it.

    5. Click Save.
  14. Click Restore.

Restoring multiple instances or disks belonging to multiple instances in a single session

When you restore multiple instances or disks belonging to multiple instances in a single session, you can select among the following options:

Option Description Instructions
Restore Instances Enables you to restore multiple instances by creating clones of the instances.

Restoring multiple instances in a single session

Restore Disks Enables you to restore multiple disks on multiple instances at once.

Restoring multiple disks in a single session
Restore from JSON

Enables you to upload an existing restore specification to R‑Cloud and use it to restore multiple instances or disks.

 Restoring multiple instances or disks from a JSON file

Restoring multiple instances in a single session

You can restore multiple instances by using a restore specification that you create in the R‑Cloud web user interface. After the restore specification is created, you can use it immediately or further modify it according to your needs. You can also download the restore specification and use it the next time you want to restore the instances to speed up the restore process.

For details on how to restore AWS and Google Cloud instances in a single session, see the following topics:

Restoring multiple AWS instances

Limitation

You can use only the latest restore point to restore multiple instances.

Procedure

  1. In the Instances panel, select the instances that you want to restore.

  2. Click  Bulk Restore. The Bulk Restore Options dialog box opens.

  3. Select Restore Instances, and then click Next.

  4. From the Destination Source drop-down menu, select the source to which you want to restore the instances. You can choose from sources that belong to the currently selected protection set and that your user account can access.

  5. From the Destination Region and Destination Zone drop-down menus, select the region and the zone to which you want to restore the instances.

  6. Optional. Enter the destination instance postfix and the target disk postfix to add a postfix to the names of the destination instances and target disks.

  7. Optional. In the Post-restore Script field, enter the path to the script or a command that R‑Cloud should run on the restored instances after the restore.

    Note  You can enter any command that the command-line interface of your instance supports.

  8. Enable the Overwrite Existing switch to overwrite the existing instances. By default, this option is disabled and the restore of the instance fails if an instance with the same name exists in the destination zone.

  9. Only if you want to apply custom settings to an instance, or edit or download the restore specification.

    1. Click Advanced Settings.

    2. Only if you want to apply custom settings to an instance. Do the following:

      1. Under Instance Options, from the Instance drop-down menu, select the instance to which you want to apply the custom settings.

      2. Only if you want to rename the instance. Select Rename Instance, and then enter the new name for the instance.

      3. From the Destination Source drop-down menu, select the source to which you want to restore the instance.

      4. From the Destination Region drop-down menu, select the region to which you want to restore the instance.

      5. From the Destination Zone drop-down menu, select the zone to which you want to restore the instance.

      6. From the Image drop-down menu, select the operating system image you want to use.

        To use a custom image, select Use custom image and enter the image AMI ID.

      7. Only if you want to rename a restored disk. Under Disk Options, do the following:

        1. From the Disk drop-down menu, select the disk that you want to rename.

        2. Select Rename Disk, and then enter a new name for the disk and click Confirm.

      8. Under Network Interfaces, review the list of networks that the original instance was configured in at the time of backup. The list shows the following for each such network:

        • VPC ID

        • Subnet ID

        For each configured network interface, you can separately adjust its public and private IP address types. By default, the public IP address configuration of the original instance is kept.

        If you want to modify network settings, you can add an additional network interface, edit an existing network interface, or delete a network interface:

        • Click Add Network Interface to add a network interface or click Edit Edit next to the network interface that you want to edit, and then follow these steps:

          1. From the Subnet drop-down menu, select the subnet.
          2. From the Security Groups drop-down menu, select the security groups.

          3. In the Public Address Type field, select the public IP address for the network interface. You can select among the following options:

            Option Description
            None

            The network interface does not use a public IP address.

            This option is preselected if the network interface of the original instance did not use a public IP address.
            Auto-assign

            The network interface uses an automatically allocated public IP address.

            This option is preselected if the network interface of the original instance used a public IP address.

            Note  Auto-assign will not work if the Auto-assign public IPv4 address on a subnet option is set to No or if more than one network interface is specified.
            Elastic IP (Reserved) The network interface uses an elastic public IP address that was reserved in Amazon EC2 in advance.
            Elastic IP (New)

            The network interface uses a new elastic public IP address.

            Note  Allocation of the IP address in Amazon EC2 is performed at the very beginning of the restore. If the allocation fails, the restore task is terminated without being logged.

          4. In the Private Address Type field, select the private IP address for the network interface. You can select between the following options:

            Option Description
            Auto-assign

            The network interface uses an automatically allocated private IP address.

            This option is selected by default.
            Custom

            The network interface uses a private IP address that is defined by you.

            Important  Use of this option might result in IP address conflicts.

          5. Click Add or Save.

        • Click Delete Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.

      9. Only if you want to edit or download the restore specification. Do the following:

        1. Click Edit or download restore JSON. The restore specification generated by R‑Cloud for all selected instances is displayed, and you can edit it as required.

        2. Only if you want to download the restore specification. Click Download JSON.

        3. Only if you want to start the restore. Click Restore from .json.

          Note  If you want to edit the restore specification by using the REST API Explorer, you can use the URL that is displayed under Request URL.

      10. Click Save Restore Settings to apply the custom settings to the instance.

    3. Click Continue to Summary.

    4. Only if you want to download the restore summary. Click Download Restore Summary as JSON.

    5. Review the restore summary, and then click Start Restore.

Restoring multiple Google Cloud instances

Limitation

You can use only the latest restore point to restore multiple instances.

Procedure

  1. In the Instances panel, select the instances that you want to restore.

  2. Click  Bulk Restore. The Bulk Restore Options dialog box opens.

  3. Select Restore Instances, and then click Next.

  4. From the Destination Source drop-down menu, select the source to which you want to restore the instances. You can choose from sources that belong to the currently selected protection set and that your user account can access.

  5. From the Destination Region and Destination Zone drop-down menus, select the region and the zone to which you want to restore the instances.

  6. Optional. Enter the destination instance postfix and the target disk postfix to add a postfix to the names of the destination instances and target disks.

  7. Optional. In the Post-restore Script field, enter the path to the script or a command that R‑Cloud should run on the restored instances after the restore.

    Note  You can enter any command that the command-line interface of your instance supports.

  8. Enable the Overwrite Existing switch to overwrite the existing instances. By default, this option is disabled and the restore of the instance fails if an instance with the same name exists in the destination zone.

  9. Only if you want to apply custom settings to an instance, or edit or download the restore specification.

    1. Click Advanced Settings.

    2. Only if you want to apply custom settings to an instance. Do the following:

      1. Under Instance Options, from the Instance drop-down menu, select the instance to which you want to apply the custom settings.

      2. Only if you want to rename the instance. Select Rename Instance, and then enter the new name for the instance.

      3. From the Destination Source drop-down menu, select the source to which you want to restore the instance.

      4. From the Destination Region drop-down menu, select the region to which you want to restore the instance.

      5. From the Destination Zone drop-down menu, select the zone to which you want to restore the instance.

      6. Only if you want to rename a restored disk. Under Disk Options, do the following:

        1. From the Disk drop-down menu, select the disk that you want to rename.

        2. Select Rename Disk, and then enter a new name for the disk and click Confirm.

      7. Under Network Interfaces, review the list of networks that the original instance was configured in at the time of backup. The list shows the following for each such network:

        • Network type: Subnetwork for VPC networks and shared VPC networks, Legacy for legacy networks

        • Subnetwork name (for VPC networks and shared VPC networks) or network name (for legacy networks)

        • Only in case of a shared VPC network. Name of the host project of the network

        For each configured network interface, you can separately adjust its public and private IP address types. By default, the public IP address configuration of the original instance is kept.

        If you want to modify network settings, you can add an additional network interface, edit an existing network interface, or delete a network interface:

        • Click Add Network Interface to add a network interface or click Edit Edit next to the network interface that you want to edit, and then follow these steps:

          1. From the Destination Network drop-down menu, select the destination network.

          2. In the Public Address Type field, select the public IP address for the network interface. You can select among the following options:

            Option Description
            None

            The network interface does not use a public IP address.

            This option is preselected if the network interface of the original instance did not use a public IP address.
            Ephemeral

            The network interface uses an automatically allocated public IP address.

            This option is preselected if the network interface of the original instance used a public IP address.
            Static (Reserved) The network interface uses a static public IP address that was reserved in Google Compute Engine in advance.
            Static (New) The network interface uses a static public IP address that is allocated at the time of the restore. If the allocation fails, the instance is assigned a temporary public IP address. Such fallback also sets the restore task status to Done with errors.

          3. In the Private address type field, select the private IP address for the network interface. You can select between the following options:

            Option Description
            Ephemeral (Automatic)

            The network interface uses an automatically allocated private IP address.

            This option is selected by default for the preselected network interfaces.
            Ephemeral (Custom)

            The network interface uses a private IP address that is defined by you.

            Important  Use of this option might result in IP address conflicts.
            Static (Reserved) Not available for legacy networks. The network interface uses a static private IP address that was reserved in Google Compute Engine or in advance.
            Static (New)

            Not available for legacy networks. The network interface uses a new static private IP address that is defined by you.

            Note  Allocation of the IP address in Google Compute Engine is performed at the very beginning of the restore. If the allocation fails, the restore task is terminated without being logged.

          4. Click Add or Save.

        • Click Delete Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.

      8. Only if you want to edit or download the restore specification. Do the following:

        1. Click Edit or download restore JSON. The restore specification generated by R‑Cloud for all selected instances is displayed, and you can edit it as required.

        2. Only if you want to download the restore specification. Click Download JSON.

        3. Only if you want to start the restore. Click Restore from .json.

          Note  If you want to edit the restore specification by using the REST API Explorer, you can use the URL that is displayed under Request URL.

      9. Click Save Restore Settings to apply the custom settings to the instance.

    3. Click Continue to Summary.

    4. Only if you want to download the restore summary. Click Download Restore Summary as JSON.

    5. Review the restore summary, and then click Start Restore.

Restoring multiple disks in a single session

You can restore disks belonging to multiple instances by using a single restore specification. After the restore specification is generated, you can use it immediately or further modify it according to your needs. You can also download the restore specification and use it the next time you want to restore multiple disks to speed up the restore process.

Limitation

You can use only the latest restore point to restore disks belonging to multiple instances. Other restore points are not available.

Procedure

  1. In the Instances panel, select the instances whose disks you want to restore.

  2. Click  Bulk Restore. The Bulk Restore Options dialog box opens.

  3. Select Restore disks, and then click Next. The Restore Disks dialog box opens.

  4. From the Destination source drop-down menu, select the source to which you want to restore the disks. You can choose from sources that belong to the currently selected protection set and that your user account can access.

  5. From the Destination region and Destination zone drop-down menus, select the region and the zone to which you want to restore the disks.

  6. Optional. Enter the target disk postfix to add a postfix to the names of the target disks.

  7. Enable the Overwrite existing switch if you want to overwrite existing disks. By default, this option is disabled and the restore fails if a disk with the same name exists at the instance to which the disks are attached.

  8. Only if you want to rename a disk, or edit or download the restore specification.

    1. Click Advanced Settings.

    2. Only if you want to rename a restored disk. Do the following:

      1. From the Instance drop-down menu, select the instance to which the disk you want to rename is attached.

      2. Under Disk options, from the Disk drop-down menu, select the disk that you want to rename.

      3. Select Rename Disk, and then enter the new name for the disk and click Confirm.

      4. Click Save Restore Settings to rename the disk.

    3. Only if you want to edit the restore specification. Do the following:

      1. Click Advanced.

      2. Click Edit or download restore JSON. The restore specification generated by R‑Cloud for all selected instances is displayed, and you can edit it as required.

      3. Only if you want to download the restore specification. Click Download JSON.

      4. Only if you want to start the restore. Click Restore from .json.

      Note  If you want to edit the restore specification by using the REST API Explorer, you can use the URL that is displayed under Request URL.

    4. Click Continue to Summary.

    5. Only if you want to download the restore summary. Click Download Restore Summary as JSON.

    6. Review the restore summary, and then click Start Restore.

Restoring multiple instances or disks from a JSON file

If you previously downloaded a restore specification, you can use it to restore multiple instances or disks by uploading the JSON file to R‑Cloud and restoring directly from it.

Procedure

  1. In the Instances panel, select the instances that you want to restore or the instances whose disks you want to restore.

  2. Click  Bulk Restore. The Bulk Restore Options dialog box opens.

  3. Select Restore from JSON, and then click Next.

  4. Under Restore JSON, click Browse. Browse for and then select the JSON file that you want to use for the restore.

  5. Click Start restore.