Once logged into your vCloud director tenant user interface, navigate to More -> Data Protection With Veeam, on the top menu bar.
From here, you can either restore an entire vAPP/VM, specific virtual hard disks, or even individual files. The below guide is broken up into three sections to show the method for each of these restore types.
Skip ahead to the section you need:
Restore entire VM/vAPP
Click on the VMs tab, and find the VM you’d like to restore in the list.
Click on the VM/vAPP, then click on the Restore vAPP or Restore VM button, then choose if you’d like to overwrite the existing VM/vAPP or keep it and create a new one from the backup. This can be achieved either by selecting the VM in question, and using the options at the top, or by right clicking the VM, and using the in-context menu there.
Entire VM Restore vs Restore vApp
Each of these has been broken into their own small section below, for Entire VM Restore, continue onwards. To navigate to Restore vApp, you can click here: Restore vApp
If you have multiple Virtual Data Centers under your account, and wish to restore a VM or vApp, you'll want to go with Restore vApp, as it allows to restore into another Virtual Data Center as long as it is nested under your Customer ID.
Entire VM restore:
Choose the backup date that you want to restore the VM from.
In the event that you want this to replace the original VM, choose Restore to the original location. If you want to keep the original VM, for instance to get data off of it, choose Restore to a new location, or with different settings.
If you have chosen to Restore to a new location, Destination and Network will now appear as options. Within Destination, choose the vApp that it'll be restored to, alongside the name of the restored VM:
Within Network, you can decide whether or not you want this to be connected when it boots, or if it should be disconnected at first. We recommend leaving it disconnected if the original VM will be remaining powered on, that way there's no issue with duplicate Mac Addresses in your VDC. Once it restores, you can disconnect it
From here, it will take you to the Datastore options, where you can configure it to use an alternative storage policy as desired.
From which, clicking Next will bring you to the Summary, where you can review your configuration, and choose whether the VM will power on automatically post restore:
Clicking Finish will start the restoration process.
Restore vApp:
Choose the date you wish to restore the vApp from:
If you are wanting to replace the original vApp, choose Restore to the original location, from where you will be taken to the Summary to confirm. If you instead want to change it to a new location or with different settings, choose Restore to a new location, or with different settings. Within
Within Destination, you can choose the Organisation alongside the name of the restored vApp.
What is the organisation?
The organisation refers to your VDC, which is nested under your Customer ID. If you have multiple VDC environments, you can use this functionality to directly restore vApps into your different environments. Your Virtual Data Centers are labelled with a -VD at the end of them, and will look similar to SAU-XXXXX-VD with the middle X's replaced by a unique alphanumeric string.
Within Network, you can decide whether or not you want this to be connected when it boots, or if it should be disconnected at first. We recommend leaving it disconnected if the original VM will be remaining powered on, that way there's no issue with duplicate Mac Addresses in your VDC. Once it restores, you can disconnect it
Within the Datastore menu, you can select the Storage Policy that will be used. With the Restore to Original Location, this will default to the same as the original VM.
From which, clicking Next will bring you to the Summary, where you can review your configuration, and choose whether the VM in question will power on automatically post restore:
When ready for it to restore, click Finish and the restoration process with begin.
Instant Recovery of a Virtual Machine
Click on the VMs tab, and find the VM you’d like to restore in the list. Click on the VM, then click on the Instant Recovery button, or you can right-click the VM and select it
Select the restore point that you wish to use and select 'next'.
In the event that you want this to replace the original VM, choose Restore to the original location. If you want to keep the original VM, for instance to get data off of it, choose Restore to a new location, or with different settings.
If you have chosen to restore to a new location, Destination and Network will now appear as options. Within Destination, choose the vApp that it'll be restored to, alongside the name of the restored VM:
Restore individual virtual disk
Click on the VMs tab, then choose the VM you’d like to restore the virtual disk for.
Click the Virtual Disks button.
Select the restore point you want and click Next.
Within Disk Mapping, select the Virtual Machine that this will be getting attached to. By Default, this will be the VM that the backups are of. If you need to attach it to another VM, this can done here.
Make sure that Restored Disk Type is set to Same as source. Do not click Next yet.
Virtual Device Node:
By Default, the disk mapping for the virtual disk will match the original VM. If this is not changed, it will replace the Existing Virtual Disk. If you wish to add it as an additional virtual disk, you will need to change the mapping.
To change the Disk Mapping, select the disk in question, and then Change disk mapping:
In this example, it is mapped to SCSI 0:0. To avoid it being replaced, we can change this to an unused Node, for instance SCSI 0:1 to add it as an additional disk instead.
We can see this is unused by the lack of device statistics, and the warning changing to inform us it will be added instead.
Whilst there, if you wish to restore it under a different storage policy, this can also be configured within Change Disk Mapping -> Choose... -> Storage Policies -> SAU-XXXXX-VD -> and then your storage policy of choice. 
From there, hit Next to continue onto the Summary to confirm your configuration and click Finish to begin the process.
Warnings:
If you haven't change the Disk Mapping and saved that change, you will receive a warning about the disk replacement. If this is intended, go ahead and continue.
Regardless of the disk mapping, the VM in question will be powered off for the duration of the restore, you will receive a warning stating as such that needs to be agreed to in order to continue.
Restore individual files or folders - Windows
Click Files -> Pick from list -> and select the VM.
To select a specific time click the calendar icon to select your desired restore point, and click Mount.
Navigate the folder structure on the left to find the file or folder you’d like to restore. Select it, then click Restore.
Provide the guest OS username and password, then click OK to start restoring.
User Permissions
The User provided will need full read/write permissions for your location you're restoring to.
Once Veeam verifies the credentials are correct, it will take you to a file restore history page where you can view the progress of the restore.
At any time, you can click the green arrow to go back and restore more files.
Restore individual files or folders - Linux
Prerequisites
* Ensure open-vm-tools package is installed
# On RHEL based systems:
yum install open-vm-tools -y
#On Ubuntu / Debian based systems:
apt install open-vm-tools -y* Ensure the vmware-tools service is enabled and running
[root@server~]# systemctl enable vmtoolsd
[root@server~]# systemctl restart vmtoolsd
[root@server~]# systemctl status vmtoolsd
● vmtoolsd.service - Service for virtual machines hosted on VMware
Loaded: loaded (/usr/lib/systemd/system/vmtoolsd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2025-04-09 16:05:06 AEST; 6s ago
Docs: https://github.com/vmware/open-vm-tools
Main PID: 3623355 (vmtoolsd)
Tasks: 3 (limit: 126250)
Memory: 1.7M
CGroup: /system.slice/vmtoolsd.service
└─3623355 /usr/bin/vmtoolsd* Ensure the /tmp/ directory inside your linux VM is executable.
sudo mount -o remount,exec /tmp* Ensure the hostname of the VM you're restoring to is set to a fully qualified domain name (FQDN) which resolves to the public address of the VM. This is especially important if the VM is on a private IP and behind NAT.
root@server:~# hostname
example.com
root@server:~# dig a +short example.com
104.21.21.68 #Make sure the IP that shows here is the public IP of your server.
#If your server hostname doesn't point to a valid domain name you can update it with the following command, replacing mydomain.com with your actual domain name:
root@server:~# hostnamectl set-hostname mydomain.com* Ensure that the Veeam FLR IP addresses are whitelisted in both the NSX firewall and also in the VM's local firewall. The FLR appliance must be able to SSH to the VM to send files to it via SCP.
The IP addresses you need to whitelist on your NSX and inside your VM are:
118.127.40.117 (Veeam FLR Public IP)* Ensure root logins are allowed in your SSHD config. E.g. edit the sshd config
nano /etc/ssh/sshd_configSet the PermitRootLogin value to 'yes'
PermitRootLogin yesRestart SSH
systemctl restart sshdAlternatively, ensure you add an SSH key during the restore wizard instead of using password authentication. For servers that are managed by SAU (MMA) you will need to either create a new 'veeam' user with sudo permission or use an SSH key for root, as the MMA system doesn't allow root logins via password.
Note:
Once your file restore has fully completed, and you no longer need to restore any files; you can re-enable the noexec option on your /tmp/ directory for optimal security.
sudo mount -o remount,noexec /tmpThe below guide shows how this can be done using IPTables, but it may differ depending on which firewall or distro you’re running.
https://help.serversaustralia.com.au/s/article/How-To-Whitelist-An-IP-Address-In-IPTables
Click Files then Pick from list.
Choose the VM you want to restore files to, then click Select.
On the left, choose the restore point you’d like to restore files from, then click Mount.
The backup file is now being mounted to the Linux file restore helper VM (FLR).
Once the backup file is mounted, you will see a directory listing.
Browse to the file or folder you’d like to restore. Select it, then you can either download or restore the file.
You can choose to overwrite or keep the existing file.
Now provide the root credentials to the VM and the SSH port details. If SSH fails, then the FLR will attempt to use VMware tools to communicate to the VM.
If you enter the wrong credentials you will see an error message, and you can try again.
Once you click OK the file restore process starts.
Once Veeam verifies the credentials are correct, it will take you to a file restore history page where you can view the progress of the restore.
You can click the green arrow to go back and restore more files.
If you chose to keep the existing file, the restored file will have RESTORED and a date string appended to the file name.
