Applies to: Nerdio for Azure (NFA) Professional, Enterprise and Core Accounts Only.
Refer this KB article to determine if you are a NFA user.
This article applies to anyone who would like to perform restores outside of the scope of what Nerdio is able to accomplish with its backup defaults. For more information on using the back up features in Nerdio, please review this article. NFA Backup Overview
- Making the Azure portal a little more manageable to work with backup
- Steps to perform a image restore of a VM as another separate instance
- Steps to perform a file level restore with mountable disk images
Image level restore as new virtual machine
The default retention in Nerdio is 30 days. This can be extended on a per VM basis if a longer retention time is needed.
This particular set of instructions is focused on creating a new instance of an image restore. The Create new should be highlighted and the fields should be filled out appropriately. The VM name should be something different than the already existing virtual machine. The storage account be an existing or a new storage account. All other fields should default to the settings that would be typical for a Nerdio created resource group.
There are two options in the Restore Type, Create Virtual Machine is the default and is what is needed for our current example.
Hit save and commit the restore. With a reasonable period of time the new running instance will be available for login and use. If you want to see or manage the progress, go to you vault again and choose Backup jobs in the monitoring section. Here you will see any active backup work occurring including start times.
Selecting the job will provide additional detail including a progress bar and percentage.
File level restore as mountable disk
A file level restore involves the use of an existing VM where you are able to mount the disk resources to an existing and running virtual machine. A great use case would be performing these steps on FS01 to mount the additional disk and copy deleted files back into the production server data disk.
Similar to a prior step in an image restore, the alternative selection would have been to choose File Recovery.
Once File Recovery is selected a new blade will appear with a three step process. The first two steps are to get the to the files, the remaining step is to unmount the image and put the virtual machine back into normal operating mode.
Step 1 would be to choose a date within the retention period. Step 2 is to download and secure the executable to be run as an administrator on a running virtual machine in the same resource group. This could also be the same server where the files originally existed and were being backed up. Finally, step 3 is to clean up the process by removing (unmounting) the recovery disk that was mounted to the server.