Restoring a whole application
With R‑Cloud, you can restore a whole application to its original or a new location by restoring the instance on which the SQL Server application is running.
Important Before you start restoring your SQL Server applications, make sure that you are familiar with all the prerequisites, limitations, considerations, and/or recommendations related to the instances on which these applications are running. For details, see Restoring instances.
Restore options
Option | Description | Instructions |
---|---|---|
Restore Instance | Enables you to restore an application by restoring the instance on which the application is running to its original location. | |
Clone Instance | Enables you to restore an application by creating a clone of the instance on which the application is running to the same or a different location on the same cloud platform. | Cloning an instance |

To access the Applications panel, in the navigation pane, click Applications.
Restoring an instance
You can restore an SQL Server application by restoring the instance on which the application is running to its original location. In this case, the original instance will be overwritten.
Consideration
Any data changes after the last successful backup are not protected and therefore cannot be restored.
Procedure
-
In the Applications panel, click the SQL Server application that you want to restore to open the Detail view.
Note The Detail view appears only if you click an application. Selecting the check box before the name of the application does not open the Detail view.
-
In the Detail view that appears at the bottom of the screen, select the preferred restore point.
-
Click
Restore.
-
Select Restore Whole Server, and then click Next.
-
Select Restore Instance, and then click Next.
-
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)
-
-
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.
-
Optional and available only if you specified the Pre/post Scripts option for the instance on which the application is running. 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.
- Click Restore.
Cloning an instance
You can restore an SQL Server application by creating a clone of the instance on which the application is running to its original or a different location on the same cloud platform. In this case, the original instance will not be overwritten.
Depending on whether you want to restore an SQL Server application running on an AWS, Azure, or a Google Cloud instance, see one of the following
Cloning an AWS instance
Limitations
-
You cannot restore instances that belong to a deleted AWS account.
-
You cannot restore an instance to a different AWS region from a snapshot.
Procedure
-
In the Applications panel, click the application that you want to restore to open the Detail view.
Note The Detail view appears only if you click an application. Selecting the check box before the name of the application will not open the Detail view.
-
In the Detail view that appears at the bottom of the screen, select the preferred restore point.
-
Click
Restore.
-
Select Restore Whole Server, and then click Next.
-
Select Clone Instance, and then click Next.
-
In the New Instance Name field, specify a new name for the instance.
-
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)
-
- 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.
-
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.
-
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 the Use custom image check box, and then enter the image AMI ID.
-
Under Disk Name, do the following:
-
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.
-
Edit the disks as required. For each selected disk, do the following:
-
Click
Edit Disk.
-
Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:
-
In the New Device Name field, enter a name for the restored disk device.
-
In the New Disk Name field, enter a name for the restored disk.
-
-
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.
-
Only if you want to add labels to the restored disk.
-
Click Advanced.
-
Click
Manage.
-
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 next to it.
-
- Click Save.
-
-
-
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.
Modifying network settings
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 next to the network interface that you want to edit, and then follow these steps:
- From the Subnet drop-down menu, select the subnet.
- From the Security Groups drop-down menu, select the security group.
-
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.
-
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.
-
Click Add or Save.
-
Click
Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.
-
-
Only if you want to add tags to the restored instance.
-
Click Advanced.
- For each custom metadata tag that you want to add, click
Manage.
-
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 next to it.
-
Click Save.
-
-
Click Restore.
Cloning an Azure instance
Procedure
-
In the Applications panel, click the application that you want to restore to open the Detail view.
Note The Detail view appears only if you click an application. Selecting the check box before the name of the application will not open the Detail view.
-
In the Detail view that appears at the bottom of the screen, select the preferred restore point.
-
Click
Restore.
-
Select Restore Whole Server, and then click Next.
-
Select Clone Instance, and then click Next.
-
In the New Instance Name field, specify a new name for the instance.
-
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)
-
-
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.
- 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.
-
From the Destination Region and Destination Zone drop-down menus, select the Azure region and zone to which you want to restore the instance. The original region and zone of the instance are preselected.
-
Under Disk Name, do the following:
-
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.
-
Edit the disks as required. For each selected disk, do the following:
-
Click
Edit Disk.
-
Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. In the New Disk Name field, enter a name for the restored disk.
-
Only if you want to add labels to the restored disk.
-
Click Advanced.
-
Click
Manage. The Custom Metadata dialog box opens.
-
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 next to it.
-
- Click Save.
-
-
-
Under Network Interfaces, review the list of networks that the original instance was configured in at the time of backup. 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.
Modifying network settings
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 next to the network interface that you want to edit, and then follow these steps:
-
From the Destination Source drop-down menu, select the source on which the destination network is configured.
- From the Destination Networks drop-down menu, select the destination network.
- From the Subnet drop-down menu, select the subnet.
- From the Security Groups drop-down menu, select the security group.
-
Under Public Address Type, select the public IP address for the network interface. You can select among the following options:
Option Description None No public IP address will be assigned to the network interface on the restored instance.
Static A static public IP address will be assigned to the network interface on the restored instance. Existing A preferred public IP address that you have created in Azure will be assigned to the network interface on the restored instance. -
Under Private Address Type, select the private IP address for the network interface. You can select between the following options:
Option Description Dynamic A dynamic private IP address will be assigned to the network interface on the restored instance.
Static A static private IP address will be assigned to the network interface on the restored instance.
-
Click Add or Save.
-
-
Click
Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.
-
-
Only if you want to add tags and/or labels to the restored instance.
-
Click Advanced.
- For each custom metadata tag that you want to add, click
Manage.
-
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 next to it.
-
-
Click Restore.
Cloning a Google Cloud instance
Limitation
You cannot restore instances that belong to a deleted Google Cloud project.
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
-
In the Applications panel, click the application that you want to restore to open the Detail view.
Note The Detail view appears only if you click an application. Selecting the check box before the name of the application will not open the Detail view.
-
In the Detail view that appears at the bottom of the screen, select the preferred restore point.
-
Click
Restore.
-
Select Restore Whole Server, and then click Next.
-
Select Clone Instance, and then click Next.
-
In the New Instance Name field, specify a new name for the instance.
-
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)
-
-
Optional and available only if you specified the Pre/post scripts option for the instance on which the application is running. 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.
- 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.
-
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.
-
Under Disk Name, do the following:
-
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.
-
Edit the disks as required. For each selected disk, do the following:
-
Click
Edit Disk.
-
Only if you do not want R‑Cloud to automatically generate a name for the restored disk device or disk. Do the following:
-
In the New Device Name field, enter a name for the restored disk device.
-
In the New Disk Name field, enter a name for the restored disk.
-
-
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.
-
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.
-
Only if you want to add labels to the restored disk.
-
Click Advanced.
-
Click
Manage.
-
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 next to it.
-
- Click Save.
-
-
-
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.
Modifying network settings
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 next to the network interface that you want to edit, and then follow these steps:
- From the Destination Networks drop-down menu, select the destination network.
-
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. -
In the Private Address Type field, select the private IP address for the network interface. You can select among 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.
-
Click Add or Save.
-
Click
Delete next to the network interface that you want to delete. Keep in mind that you cannot restore the instance without a network interface.
-
-
Only if you want to add tags and/or labels to the restored instance.
-
Click Advanced.
- For each label, network tag, or custom metadata tag that you want to add, click
Manage.
-
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 next to it.
-
Click Save.
-
-
Click Restore.