Restores
Last updated
Last updated
It should first be determined
WHAT: Which target and which backup job
WHEN: What status of backups
HOW: With what options
is to be restored.
The "Restore" dialog in the NovaBACKUP 21.1 backup client is where you will perform the restores for all backup types (other than image backups):
To start a restore in the NovaBACKUP backup client, first click the "Restore" tab.
Here you decide what backups and the selection from that backup you want to restore.
The "Backup Type" column refers to the backup type that was used to back up the data, in this case if "FPI" is seen as the value in the "Backup Type" column in the "Restore" dialog, that just means the newer backup engine in 21.1 was utilized to store that backup to. And additionally in that case, if the "Hybrid Backup" option is enabled in a 'Local Backup' device assigned backup job, and there is at least one completed "Hybrid Backup" enabled backup job in the Restore UI, then in the "Location (Device)" column in the Restore UI the "Hybrid AR" enabled restore index record will always contain an "AR" value in that "Location (Device)" column, which will state "AR" in the value of that column, as well as it will also state the complete "S3devicename" that will equate to the complete 'Cloud S3' device name (for whatever you named it as at the device level) in plaintext + the additional word "_hybridbackup" right after that, near the end of the "Location (Device)" column value + a .dct file extension at the very end of the restore index record value, in that column.
The "Restore Settings" (labeled as "Properties for Restore Jobs") dialog allows you to define how the backup will be restored, and to what destination target location, either to the original location or to an alternate location (just know that two plugin backup types, which are MS SQL and Hyper-V, cannot restore to the original location, only to an alternate location, and then you can utilize native restore ability in SQL Server Management Studio (SSMS) and Hyper-V Manager apps to restore the already restored to an alternate folder SQL database or Hyper-V VM, directly to the current SQL Server or Hyper-V Server):
And for a Hybrid enabled backup job, a special "AR" restore index entry will be created in the 'Local Backup' device, which will be above the normal restore index entry, where both restore index entries in that case will match the same "Created on" column date and time value, and take note that for the Hybrid portion of the backup entry to restore, that it will mention "AR" and the "S3 device name" in this restore index entry, in the "Location (Device)" column value for that non Hybrid enabled backup (note you will have to expand that column size to see the complete value in most cases), which will look like this:
The above content covers the restore of normal non Hybrid enabled backups. However, the restore of Hybrid enabled backups has some special consideration in the documentation needed to point out, which is covered in the next "" topic. Or you can keep reading about that here if you want to know what the difference would be and would look like, when talking about the Restore tab in the client UI:
Note: For Hybrid enabled backup jobs, the backup is stored to a 'Local Backup' device type first, and then after that portion of the backup job is done the at rest completed backup is then uploaded to the 'Cloud Backup' (Cloud S3 based) device, as a copy of that at rest 'Local Backup' device backup, that was defined in the Hybrid backup job settings (as covered in the related "Hybrid Backup" topic ). In that case both the normal 'Local Backup' device restore index entry, and the 'Cloud S3 based' device restore index entry are stored next to each other on the same 'Local Backup' device type, to make them easier to see and identify, and in the Restore UI dialog in the "Location (Device)" column, for the "Hybrid AR" backup entry, for the restore index record value for that Hybrid enabled backup that had complete, it will state "AR" in the value of that column, as well as it will also append the complete "S3devicename", that will equate to the complete 'Cloud S3' device name (for whatever you named it as at the device level) in plaintext + the additional word "_hybridbackup" right after that, near the end of the "Location (Device)" column value + a .dct file extension at the very end of the restore index record value, in that column. Some for examples are below for what we mean here: For a normal non Hybrid enabled backup job, a backup restore index entry will look like this, and take note that there is no mention of "AR" or the "S3 device name" in this restore index entry, in the "Location (Device)" column value for that non Hybrid enabled backup in that case (note you will have to expand that column size to see the complete value in most cases):
Note: If the backup to restore does not exist in the "Restore" dialog, you may need to think about Importing the backup records (restore index records) for that particular device, as for instance if you install NovaBACKUP clean on a replacement machine then it will not have any backup records (restore index records) in that case visible in this dialog. If you want to learn about Importing backup records, please visit those additional topics under the "Restores" category. And keep in mind that Imports of backup records for an entire either 'Local Backup' or 'Cloud Backup' (S3) device type (the modern device types added in NovaBACKUP 21.0) can only be done with non-Legacy backup devices. If you do ever need to restore individual existing at rest backups, to get the restore index records back for those individual legacy device backups, then you can still do that, but you'd need to follow the additional "" topic.
