This short manual guide is designed to help HI GIO users understand the features and benefits of our Backup as a Service and provide step-by-step instructions for setting up and managing your backups. Whether a small business or a large enterprise, our BaaS solution is tailored to meet your unique needs, ensuring your data is protected against loss, corruption, or unforeseen disasters.
Overview
We provide BaaS for all enterprises who need to protect their data in cloud environments, on-premises virtualization environments, and physical servers with a comprehensive backup solution. This solution can back up multiple platforms such as Centos, RedHat, Ubuntu, Windows, etc.
Guidelines
We offer a user-friendly & cost-effective online Data Backup & Recovery solution ensuring safeguarding files, folders, etc.
Utilizing Veeam Portal
Applying on Gen.1, Gen.2 and on-premises environment
Tailoring a secure & efficient storage, disaster recovery, and backup service to business need
We offer a high-speed Backup & Recovery solution with VM servers in a single portal, exclusively available for HI GIO Gen.2.
Allowing tenants to backup & restore single VMs and vApps.
Facilitating handy self-service restoration within a single portal using vCloud Director (vCD).
Swiftly restore diverse workloads as VMs by instant recovery; aid in migration or quickly recovering with minimal impact; improve RTO and minimize disruption to mere minutes.
Our current Backup as a Service (BaaS) for Microsoft 365 solution harnesses Veeam’s proficiency and capabilities in backup, recovery, and data management to deliver a simple and complete way to eliminate the risk of losing access and control over your Office 365 data.
Microsoft 365 (formerly Office 365) provides robust services, but a comprehensive backup of your data is not included in a standard Microsoft 365 license.
Create backup job on Linux OS via Veeam agent console
Overview
This is a document on how to Create a backup job on Linux.
Procedure
1
Step 1: Start Veeam Backup Agent
Using this command “veeam” to start service Veeam
2
Step 2: Create a Back Job
Press “c” and input Job name
Choose Veeam Cloud Connect Repository
Enter the address of BaaS Cloud Gateway Address:
HCM: backup-hcmc.higio.net
HN: backup-hni.higio.net
Accept the certificate details.
Enter Username and Password
Check the capacity of BaaS Storage.
Advanced configuration.
Schedule Backup.
Check the settings.
Run the Backup Job.
How to prepare and setup Veeam Recovery Media for Windows
This is a document on how to prepare and setup Veeam Recovery Media for Windows.
We will need Windows machine or VM to setup.
1
Step 1: Install Veeam Backup Agent for Windows (v13 and above).
Deploying by BaaS portal following this guide
1. HI GIO BaaS
1
Step 1: Check and prepare your machine to match the requirements from :
2
Step 2: Open firewall outbound to Cloud Gateway IP with ports 6180 and 53:
3
How to prepare and setup Veeam Recovery Media for Linux
This is a document on how to prepare and setup Veeam Recovery Media for Linux
For this Veeam Recovery Media we don’t need to make the ISO by ourselves because Veeam already public this ISO from theirs’s repository. Just download and use it.
1
Step 1: Access to this link:
Choose the correct architectures
How to configure receive Alarm from BaaS
This is a document for how to configure receive Alarm from BaaS
1
Step 1: Access by URL:
HN site:
2
Step 2: After completed installed the Backup Agent go to Start > Veeam folder > Choose Create Recovery Media.
3
Step 3: From Create Recovery Media windows you can choose what you want to include to media from current OS, after done click Next.
NOTE: In VMware environments or on physical servers, if Windows uses VMXNET3 NIC drivers or other specific storage/network drivers that are not detected when booting Veeam Recovery Media, follow article to add the required drivers to the recovery media.
NOTE: To make sure Veeam Recovery Media can manually install VMXNET3/PVSCSI drivers during recovery, if the VM is deployed using the HI GIO template, you must follow article to add the required drivers into the recovery media.
4
Step 4: Specify Path to for the ISO file choose Browse to choose the correct path you want, you also can set credential for ISO too by enabling This share requires access credentials. After done click Next.
5
Step 5: Review again the config of Recovery Media you have configured. If all correct click Create.
6
Step 6: Wait for the creation completed, after that click Finish.
7
Step 7: Validate the ISO file that already choose the path from Step 4.
The Veeam Recovery Media for Windows preparation is completed.
Overview
Procedure - Prepare & setup Veeam Recovery Media for Windows
Manage backup (After installation is completed, you can manage the backup job and machine via the BaaS portal or via the Veeam agent console).
Create a backup job:
Via agent console:
Via portal:
Restore process: Restore the machine after disaster, system error, or with Veeam media:
Please refer to the HI GIO BaaS guide in the list below.
Overview
Online backup service, also known as cloud backup or backup as a service (BaaS), is a method of offsite data storage in which a service vendor regularly backs up files, folders, or the entire contents of a hard drive to a remote secure cloud-based data repository over a network connection.
Portal:
HCM site:
HN site:
Cloud Gateway:
HCM site: (IP address 118.68.171.248 and 118.68.171.233)
HN site: (IP address 1.55.215.248 and 1.55.215.250)
Choose the Veeam Cloud Connect repository, then Next
Set the Restore points you want to keep and choose Advanced Settings… for more options.
Advanced Option:
After finishing Apply then, choose Next to continue.
Choose Use sub-tenant accounts for each managed backup agent with the following quota and set the quota for this backup job, or you can set it Unlimited.
Enable application-awareprocessing or script execution or file system indexing if you want to back up. Next.
Schedule the backup job, then Next.
Review the backup job configuration and then choose Finish.
Tick the job that wants to run, then choose Assign.
Choose the policy from the Backup Policy column to check the create backup job process.
Copy the agent installation file to the machine where you want to install the agent.
Make sure that you have permission to execute the installation file.
Install the Management Agent:
Wait for the connection to be connected:
3
Step 3: Install Veeam Backup Agent Windows
Login to the Web UI > Managed Computers > Discovered Computers
Choose the Windows Server > Install Backup Agent
In the Use guest OS credentials form section, select an account that will be used to upload setup files to client computers and start installation.
The account must have local privilege permissions on computers where you want to install Veeam backup agents.
Select the Account specified in the discovery rule or the management agent settings if you want to install the same account that you specified for the discovery of client computers, either in the master agent configuration or in the discovery rule settings.
Select The following user account if you want to specify an account different from the one you used for discovery. You can select an account from the list or click Create New to specify credentials for a new account.
4
Step 4: Check the result via portal and OS:
Overview
Procedure - Install Veeam Agent for Windows
Restore Linux on Physical Server by Veeam Recovery Media
Overview
This is a document on how to Restore Linux on Physical Server by Veeam Recovery Media.
Procedure
We will need a USB to make a booting device for Veeam Recovery Media.
1
Step 1: Access to Microsoft Store or go to this link to download Rufus.
2
Step 2: Open Rufus, from the Device option, verify and choose the correct USB drive.
3
Step 3: From Boot selection option click SELECT to choose the Veeam Recovery Media ISO file that already prepared on .
4
Step 4: After seeing the Status option showing READY choose START to begin creating the USB bootable device (Please note that this action will erase all data exist on the USB).
5
Step 5: After completed creating the USB bootable device insert to the machine need to restore. Then power on the machine and choose boot from USB drive.
6
Step 6: Restore from a restore point
When boot is completed, choose Proceed without SSH
Accept license agreement
Remember to configure IP for the connection to Cloud Gateway via Configure network
Choose Edit a connection
Restore Linux VM on HIGIO Cloud via Media file (ISO file)
Overview
This is a document on how to Restore a Linux VM.
Procedure
1
Step 1: Insert Veeam Recovery Media for Windows to VM
From VM choose ALL ACTION > Media > Insert Media
Choose Veeam Recovery Media(According to your OS) > Insert
Then POWER ON VM and wait for Veeam Recovery Media to boot
2
Step 2: Restore from a restore point
When boot is completed, choose Proceed without SSH
Accept license agreement
Remember to configure IP for the connection to Cloud Gateway via Configure network
Check that the mapping is correct, and then press ”s” to continue
Review the Summary of the restore job, then press Enter to begin
Begin the process and complete the restore
Shutdown the VM and then Eject Media
POWER ON the VM
>
Management Agent
>
Upgrade
Wait for Deployment Progress
Backup Agent updated successfully:
Choose Server Windows > Management Agent > Upgrade
Wait for Deployment Progress
2
Step 2: Update Backup Agent for Linux
Select Managed Computers > Backup Agents
Choose Server Linux > Backup Agent > Upgrade.
Wait for Deployment Progress
Backup Agent updated successfully:
Update Veeam Service Provider Console Management Agent for Linux from v.8.1 to v.9 and Veeam Backup Agent for Linux from v.6 to v.6.3
Device
option, verify and choose the correct USB drive.
3
Step 3: From Boot selection option click SELECT to choose the Veeam Recovery Media ISO file that already prepared on this guide.
4
Step 4: After seeing the Status option showing READY choose START to begin creating the USB bootable device (Please note that this action will erase all data exist on the USB).
5
Step 5: After completed creating the USB bootable device insert to the machine need to restore. Then power on the machine and choose boot from USB drive.
6
Step 6: Restore from a restore point
When the boot is completed, choose Bare Metal Recovery
Choose Network storage
Remember to configure IP for the connection to Cloud Gateway via Configure network settings
Choose available Ethernet > Properties.
Input the IP address, then choose OK
Choose the Veeam Cloud Connect repository
Enter the address of BaaS Cloud Gateway Address:
HCM: backup-hcmc.higio.net
HN: backup-hni.higio.net
Continue on the certificate details.
Enter Username and Password
Select Job that want to restore
Select restore point that want to restore
Choose Restore Mode
Review Summary of restore job
Begin the process and complete the restore
Shutdown the VM and then Eject the USB drive
Power on the machine again to boot to the Windows OS that already restored.
Log on to the machine where you want to install the master agent.
Copy the agent installation package (the .sh file) to the machine where you want to install the agent.
Make sure that you have permission to execute the installation package file.
sudo chmod +x LinuxAgentPackages...
3
Step 3: Install the package with the following command:
sudo ./LinuxAgentPackages....
Check connection by command:
veeamconsoleconfig -s
Note: if you cannot connect to Cloud Gateway, please check:
Cloud Gateway address:
HCM: backup-hcmc.higio.net
HN: backup-hni.higio.net
Check connections to the internet.
Check connections to Cloud Gateway port 6180. #telnet {Cloud Gateway address} 6180
If the connection to Cloud Gateway port 6180 cannot be opened, do the following command:
Delete iptables rule:
4
Step 4: Return to the Veeam Server Provider Console that the Linux Machine will be displayed in “Discovery Computer” with the status “active.”
5
Step 5: Install Veeam Backup Agent Linux
Login to the Web UI > Managed Computers > Discovered Computers
Choose the Linux Server > Install Backup Agent
In the Use guest OS credentials form section, select an account that will be used to upload setup files to client computers and start installation.
The Account must have local root permissions on computers where you want to install Veeam backup agents.
Select the Account specified in the discovery rule or the management agent settings if you want to install the same Account that you specified for the discovery of client computers, either in the master agent configuration or in the discovery rule settings.
6
Step 6: Check the result via portal and VM:
Overview
Procedure - Install Veeam Agent for Linux
Restore Entire VM via vCD's portal
Overview
With the option of Entire recovery, you can restore an entire VM from a backup file to the latest state or to a previous point in time if the original VM fails. Entire VM restore enables full disk I/O performance.
Requirement
Check your available resources.
Create a new vApp to restore the VM if you want to restore it to a new location.
Add the original VM network to the new vApp.
Choose the VM and point that needs to be restored with Entire Recovery.
Select Restore mode.
Verify status restore.
1
2
Step 2. Select tab VMs
3
Restore Windows VM on HIGIO Cloud via Media file (ISO file)
Overview
This is a document on how to Restore a Windows VM.
Procedure
1
Step 1: Insert Veeam Recovery Media for Windows to VM
From VM choose ALL ACTION > Media > Insert Media
Choose Veeam Recovery Media(According to your OS) > Insert
Then POWER ON VM and wait for Veeam Recovery Media to boot
2
Step 2: Restore from restore point
When the boot is completed, choose Bare Metal Recovery
Choose Network storage
Remember to configure IP for the connection to Cloud Gateway via Configure network settings
Choose available Ethernet > Properties.
Create backup job for Windows via Portal
Overview
This is a document on creating a backup job for Windows on Portal.
You can choose the job already created from the Service Prover template, or you can create a new one by choosing Create New.
Input the Name, Description (Optional) then click Next.
Select The following user account if you want to specify an account different from the one you used for discovery. You can select an account from the list or click Create New to specify credentials for a new account.
In the Backup policy to apply list, choose a backup policy that must be used as part of the installation process.
If you allocate all cloud resources specified in the policy to the company, the chosen backup policy will configure backup job settings after installing Veeam backup agents. You can select No policy if you do not want to configure backup job settings as part of installation.
By default, read-only access is enabled for all Veeam backup agents. To disable the read-only access mode for Veeam backup agents, set the Enable read-only UI access for the backup agent toggle to Off.
Mode 01- Restore to the original location: Quickly restore the selected VM to its original location with the original name and settings. This option minimizes the chance of user input error.
The restore VM will override the original VM.
The original VM will be shut down and deleted when the storage is successful.
>> Please follow step 5.1
Mode 02 - Restore to a new location or with different settings: Customize the restored VM location and change its settings. The wizard will automatically populate all controls with the original VM settings as the defaults.
This mode will increase your resources, so please check your available resource and contact HI GIO-Sales if you want to add more resources to restore the VM.
You need to create a new vApp to restore the VM.
>> Please follow step 5.2
5.1.1 Select Next
5.1.2 On Summary
Verify VM restore information → select Power on VM automatically → Finish
5.2.1 Select Next
5.2.2 On Destination
*** Specify vApp to restore the virtual machine to, and type in the restored VM's name.
Click Choose
Select vApp has been created before
Change VM name → Next
5.2.3 On Network
Keep default or choose network already added on vApp → Select Next
5.2.4 On Datastore
Keep default or choose Policy already on your resource → Select Next
5.2.5 On Summary
Verify VM restore information → select Power on VM automatically → Finish
6
Step 6. Verify Status VM restore
Select tab VMs → History to check the status of VM restore
Restore VM successfully
You'll get the message like this:"Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring."
The reason for this is VM has been assigned an ethernet adapter with a different MAC address than what the source VM was using.
Resolve: Get MAC address that VM has assigned and update it to interface
Get MAC address from portal
Follow on your distribute to update MAC address
Procedure
Step 1. From the main menu vCD Portal, select More -> Data Protection with Veeam
Step 3. Select VM need to restore --> Entire Recovery
Set the Restore points you want to keep and choose Advanced Settings… for more options.
Advanced Option:
After finishing Apply then, choose Next to continue.
Choose Use sub-tenant accounts for each managed backup agent with the following quota and set the quota for this backup job, or you can set it Unlimited.
Enable the backup cache feature if needed, then go next.
Enable application-awareprocessing or file system indexing you want to backup, then Next.
Schedule the backup job, then Next.
Review the backup job configuration and then choose Finish.
Tick the job that wants to run, then choose Assign.
Choose the policy from the Backup Policy column to check the create backup job process.
We offer a high-speed Backup & Recovery solution with VM servers in a single portal, exclusively available for HI GIO Gen.2. This is a document for how to:
How to access to Veeam Backup
Procedure
Step 1: From the main menu vCD Portal, select More Data Protection with Veeam
Step 2: The Dashboard will display statistics:
Number of VMs backed up
Number of backup jobs configured
Total storage quota
Used storage size
Status of backup jobs
Average data transfer speed
Step 1: Select the tab Jobs
Step 2: Select Create
Step 3: Open the Backup Job window
Step 4: Input the backup job name in the box Job name
Step 5: Input a description of the backup job in the box Description (or keep default)
Step 1: After creating the Backup Jobs, the created backup jobs will display in the tab Jobs.
Step 2: To execute the backup job, select the backup job and select Start
Here, the customer can also select Stop to stop the backup job
Step 1: Select tab VMs
The list of VMs that have been successfully backed up and the number of restore points corresponding to each VM will be displayed here.
Step 2: Select VM needs to be restored, select Restore VM Overwrite
Overwrite: Backup data will be restored overwriting the current VM
Veeam Agent Installation for RHEL 9.2
Overview
This document is for installing the Veeam Backup Agent Linux on RHEL 9.2
The Veeam repository for Linux can be found at . On this page select "veeam-release-el9-1.0.8-1.x86_64.rpm", “blksnap-6.0.3.1221-1.noarch.rpm”, “veeam-6.0.3.1221-1.el9.x86_64.rpm“.
Step 2: Install Veeam and dependencies:
This will download an RPM file. You will likely be unable to download this directly from this page to your Linux machine, as your server will likely not have a GUI or web browser. To get around this, it is best to download the RPM to your workstation and then use WinSCP or MobaXterm to copy the RPM file to your server via SSH.
Create backup job on Windows OS via Veeam agent console
This is a document on how to create a backup job on Windows.
1
Step 1: Configure job on Veeam Backup Agent
StartVeeam Backup Agent Application
2
Workaround
Please refer to the other guides in the list below.
Step 5.2 Restore to a new location, or with different settings
In a some case after restore the linux VM (RHEL, CentOS, Ubuntu..) the machine will boot up without the local network interface.
Step 6:
Select the number of
Restore points
to keep
After each successful backup, the system creates a version of the data during that backup, called a restore point.
If a customer needs to backup 1 VM daily, once a day, and store all those backups in the last 15 days, the number of restore points customers need to set is 15.
Select Next to continue.
Step 7: At the tab Virtual Machines, select Add
Step 8: Select VM need backup, select OK
Select symbol + to open the components until the list of VMs appears (VM will be at the last symbol +)
Select Next to continue.
Step 9: (Optional) Set some advanced features (can keep default)
Select Next to continue.
Step 10: Schedule a backup job
Check the box Run the job automatically, andlet the system automatically backup according to the set schedule.
Specify the time to backup (every day, every month, specific days of the week, …)
Automatic retry: Option to run the backup job again if the job fails for some reason.
Wait before each attempt for: interval between retry.
Step 11: (Optional) Setting Email Notifications
Check the box Enable e-mail notifications to turn on notifications
Input e-mail address in the box Recipients
Select cases to receive notifications:
Notify on success: Receive email notification if the job is completed successfully
Notify on warning: Receive an email notification if the job is completed with a warning
Notify on error: Receive email notification if the job fails
Suppress notifications until the last retry: Receive email notification about the final job status
Keep:
Backup data will be restored as a new VM
Step 3: Select the restore point needed to restore
Check the box Power on a machine after restoring to power on the VM after the restore is complete.
Step 4: Select History to view restore history and restore process
How to create Backup Jobs
How to perform Backup
How to perform Restore
(Note: The more restore points, the storage usage of customers increase)
Once the RPM is on your server, install it and its dependencies:
The modules bdevfilter and blksnap will be created in /lib/modules/$(uname -r)/extra
We can confirm that this module has not loaded by running lsmod, and grepping for blksnap. We will see that grep returns no output.
Step 3: Insert modules bdevfilter and blksnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent-based backups will run fine; however, the loaded module will not persist if we reboot. We must create a file called /etc/modules-load.d/bdevfilter.conf and/etc/modules-load.d/blksnap.conf , and make sure that it has the name of the kernel module. We will also need to run depmod to add the loaded kernel module to the kernel module dependencies list.
Once we reboot the RHEL server, the bdevfilter and blksnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
The Veeam repository for Linux can be found at . On this page, select "veeam-release-el9-1.0.8-1.x86_64.rpm".
Step 2: Install Veeam and dependencies:
This will download an RPM file. You will likely be unable to download this directly from this page to your Linux machine, as your server will likely not have a GUI or web browser. To get around this, it is best to download the RPM to your workstation and then use WinSCP or MobaXterm to copy the RPM file to your server via SSH.
Step 1: Download Veeam repository:
The Veeam repository for Linux can be found at . On this page, select "veeam-release-el9-1.0.8-1.x86_64.rpm".
Step 2: Install Veeam and dependencies:
This will download an RPM file. You will likely be unable to download this directly from this page to your Linux machine, as your server will likely not have a GUI or web browser. To get around this, it is best to download the RPM to your workstation and then use WinSCP or MobaXterm to copy the RPM file to your server via SSH.
Instant Recovery
Overview
With the option of Instant recovery, you can recover VM quickly. VM will mount workload images to a host directly from the backup stored on backup repositories. However, it will be limited I/O performance; you must migrate the VM to production when successfully restored.
Requirement
Check your available resources.
Create a new vApp to restore the VM
*** During recovery
You can only restore and migrate each VM in turn.
*** If you want to restore and migrate many VMs at the same time
Please contact HI GIO support.
Choose the VM and point that needs to be restored with Instant Recovery.
Select Restore mode.
Verify status restore.
Migrate and Verify VM.
1
Step 1: From the main menu vCD Portal, select More -> Data Protection with Veeam
2
Step 2: Select tab VMs
BaaS Support Matrix
Overview
This is a document for which the agent supported:
Management (MGMT) Agent Compatibility
Management Agent OS and Infrastructure support
Backup Agent Compatibility
Backup Agent OS and Infrastructure support
Documentation References
Version
Supported
Windows
Linux
Windows
Linux
Version
Windows OS
Version
Linux OS
Veeam Backup & Replication 12.3.2 (starting from 12.3.2.3617) and 13.0.1 or later
Management Agent (Management Agent line):
Backup Agent Windows:
Backup Agent Linux:
Linux Backup Agent module:
Veeam Agent Installation for CentOS 8 Stream
This document is for installing the Veeam Backup Agent Linux on CentOS 8 Stream
OS: CentOS is 8 Stream, running kernel 4.18.0-500.el8.x86_64
Once the RPM is on your server, install it and its dependencies:
The modules bdevfilter and blksnap will be created in /lib/modules/$(uname -r)/extra
We can confirm that this module has not loaded by running lsmod, and grepping for blksnap. We will see that grep returns 0 lines of output.
Step 3: Insert modules bdevfilter and blksnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent-based backups will run fine; however, the loaded module will not persist if we reboot. We must create a file called /etc/modules-load.d/bdevfilter.conf and/etc/modules-load.d/blksnap.conf , and make sure that it has the name of the kernel module. We must also run depmod to add the loaded kernel module to the kernel module dependencies list.
Once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
Create 2 files for signing modules to the UEFI database.
Run the file one-time-setup first and then reboot:
During the reboot, when prompted, press any key to perform MOK management.
At the wizard's first step, select Enroll MOK and press [Enter].
At the Enroll the key(s) step, select Yes and press [Enter].
Provide the password for the root account and press [Enter].
At the final step, select Reboot and press [Enter].
After that, sign 2 modules by running file sign-modules:
Step 4: Insert modules bdevfilter and blksnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent-based backups will run fine; however, the loaded module will not persist if we reboot. We must create a file called /etc/modules-load.d/bdevfilter.conf and/etc/modules-load.d/blksnap.conf , and make sure that it has the name of the kernel module. We must also run depmod to add the loaded kernel module to the kernel module dependencies list.
Once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
Once the RPM is on your server, install it and its dependencies:
The modules bdevfilter and blksnap will be created in /lib/modules/$(uname -r)/extra
We can confirm that this module has not loaded by running lsmod, and grepping for blksnap. We will see that grep returns 0 lines of output.
Create 2 files for signing modules to the UEFI database.
Run the file one-time-setup first and then reboot:
During the reboot, when prompted, press any key to perform MOK management.
At the wizard's first step, select Enroll MOK and press [Enter].
At the Enroll the key(s) step, select Yes and press [Enter].
Provide the password for the root account and press [Enter].
At the final step, select Reboot and press [Enter].
After that, sign 2 modules by running file sign-modules:
Step 4: Insert modules bdevfilter and blksnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent-based backups will run fine; however, the loaded module will not persist if we reboot. We must create a file called /etc/modules-load.d/bdevfilter.conf and/etc/modules-load.d/blksnap.conf , and make sure that it has the name of the kernel module. We must also run depmod to add the loaded kernel module to the kernel module dependencies list.
Once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
Important: If the server boots with Secure Boot, we can’t insert the module → Must run step 3 on Secure Boot below first.
3
Step 3: Select VM need to restore --> Instant Recovery
4
Step 4: On Restore Point
Select backup date want to restore --> Next
5
Step 5. On Restore mode
There are 2 modes:
*** Restore to the original location: Quickly restore the selected VM to its original location with the original name and settings. This option minimizes the chance of user input error.
VM restore will override the original VM.
VM original will be shut down and deleted when you successfully restore.
>> Please follow step 5.1
*** Restore to a new location or with different settings: Customize the restored VM location and change its settings. The wizard will automatically populate all controls with the original VM settings as the defaults.
This mode will increase your resources, so please check your available resources and contact HI GIO-Sales if you want to add more resources to restore the VM.
You need to create a new vApp to restore the VM.
>> Please follow step 5.2
5.1.1 Select Next
5.1.2 On Summary
Verify VM restore information → select Power on VM automatically → Finish
5.2.1 Select Next
5.2.2 On Destination
Specify vApp to restore the virtual machine to, and type in the restored VM's name.
Click Choose
Select vApp has been created before
Change VM name → Next
5.2.3 On Network
Keep default → Select Next
5.2.4 On Summary
Verify VM restore information → select Power on VM automatically → Finish
6
Step 6: Verify Status VM restore
Select tab VMs → History to check the status of VM restore
VM restore has been recovered successfully, we can back to vCD portal to check the data
Back to vCD portal, VM restore had power-on
7
Step 7: Migrate to Production
*** After checking the data on VM restore, if it contains the data you want, you need to migrate to production to ensure I/O performance for the VM.
Back to Data Protection with Veeam → Instant Recovery
Select VM restore → Migrate to Production
On Destination → Select Choose...
Select Storage Policy → OK
Select Next
On Ready → Finish
To check the status of the migrated VM restore, select VMs → History
Select VM restore
VM restore has migrated to production
8
Step 8: Verify VM restore information
*** To make sure VM restore has run with the correct configuration, go back to vCD portal and check:
Hard disk (Size, IOPS, Storage Policy)
Compute (CPU, Memory)
Procedure
Veeam Agent Linux v6.3.2
x
Veeam Agent Windows v13
x
Veeam Agent Linux v13
x
MGMT Agent v8.1 and below
MGMT Agent v9
x(will auto-update)
MGMT Agent v9.1
x
64-bit versions of the following operating systems are supported except Server Core installations for server OS:
Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11
Microsoft Windows 10 (starting from version 1909)
Microsoft Windows 10 LTSC versions (1607, 1809)
Linux kernel versions 2.6.32 – 6.10 are supported if you use kernels supplied by your distribution.
Only 64-bit versions of the following operating systems are supported:
Oracle Linux 6 (starting from UEK R2) – Oracle Linux 8 (up to UEK R6)
Oracle Linux 8 (UEK R7) — for information on installation, see .
Oracle Linux 9 (UEK R7 up to 5.15.0-308.179.6.3.el9uek)
Oracle Linux 9 (UEK R8) – for information on installing Veeam Agent on Oracle Linux 9 with UEK R8, see .
SLES 12 SP4, 12 SP5, 15 SP1 – 15 SP6
SLES for SAP 12 SP4, 12 SP5, 15 SP1 – 15 SP6
Fedora 36, 37, 38 and 39
openSUSE Leap 15.3 – 15.6
openSUSE Tumbleweed has an experimental support status. For details about experimental support, see .
Veeam Agent for Linux supports 32-bit versions of:
RHEL 6.
Oracle Linux 6 distributions only.
Limitation:
13.0.1.94
Linux kernel version 3.10 to version 6.17 is supported. For the most up-to-date information on the Veeam Agent compatibility with Linux kernel versions of the supported distributions, see this Veeam KB article.
Veeam Agent supports the 64-bit versions of the following Linux distributions:
Debian 11.0 – 13.21
Ubuntu 16.04, 18.04, 20.04, 22.04 and 24.04
RHEL 8.4 – 9.6 and 10.0
Oracle Linux 7 – 10.0 (RHCK)
Oracle Linux 7 (starting from UEK R4) – Oracle Linux 8 (up to UEK R6)
Oracle Linux 8 (UEK R7) — for information on installation, see .
Oracle Linux 9 (UEK R7 up to 5.15.0-313.189.5.2.el9uek.x86_64)
Oracle Linux 9 (UEK R8) – for information on installing Veeam Agent on Oracle Linux 9 with UEK R8, see .
Oracle Linux 10 (UEK R8)
SLES 12 SP5, 15 SP3 – 15 SP7
SLES for SAP 12 SP5, 15 SP3 – 15 SP7
Rocky Linux 8.10, 9.4 – 9.6 and 10.0
AlmaLinux 8.10, 9.4 – 9.6 and 10.0
Limitation:
Management (MGMT) Agent Compatibility
Management Agent OS and Infrastructure support
1.Management Agent v9
2.Management Agent v9.1
Backup Agent Compatibility
Backup Agent OS and Infrastructure support
1. Veeam Agent for Microsoft Windows
2. Veeam Agent for Linux
3. Veeam Backup & Replication (VBR)
NOTE:
Veeam Backup & Replication 13.0.0 is not supported.
This will download an RPM file. It is likely that you will be unable to download this directly from this page to your Linux machine, as your server will most likely not have a GUI and a web browser. To get around this it is best to download the RPM to your workstation, then use WinSCP or MobaXterm to copy the RPM file to your server via SSH.
Once the RPM is on your server, install it.
This will install the required packages for the Veeam agent, including a kmod-veeamsnap package; however, you will notice that there are still issues with the Linux kernel module for veeamsnap. If we inspect the files installed with kmod-veeamsnap, and compare it with our current kernel version, we can see that the kernel module is not installed for our version. The difference is very minute.
From this, we can see that the kernel module was installed for 4.18.0-477.10.1.el8_7.x86_64, but our current kernel is 4.18.0-500.el8.x86_64.
Without this kernel module, our agent based Veeam backups will fail.
We can confirm that this module has not loaded by running lsmod, and grepping for Veeam. We will see that grep returns 0 lines of output.
Fortunately, the difference in these kernel versions is small enough that the veeamsnap.ko file will still work for us.
First, we must create the /extra/ directory for our kernel version, then copy the kernel module to this directory.
Step 3: Insert module veeamsnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent based backups will run fine; however, the loaded module will not persist if we reboot. We will need to create a file called /etc/modules-load.d/veeam.conf, and make sure that it has the name of the kernel module in it. We will also need to run depmod to add the loaded kernel module into the kernel module dependencies list.
Now, once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
This will download an RPM file. It is likely that you will be unable to download this directly from this page to your Linux machine, as your server will most likely not have a GUI and a web browser. To get around this it is best to download the RPM to your workstation, then use WinSCP or MobaXterm to copy the RPM file to your server via SSH.
Once the RPM is on your server, install it.
This will install the required packages for the Veeam agent, including a kmod-veeamsnap package; however, you will notice that there are still issues with the Linux kernel module for veeamsnap. If we inspect the files installed with kmod-veeamsnap, and compare it with our current kernel version, we can see that the kernel module is not installed for our version. The difference is very minute.
From this we can see that the kernel module was installed for 4.18.0-477.10.1.el8_7.x86_64, but our current kernel is 4.18.0-500.el8.x86_64.
Without this kernel module, our agent based Veeam backups will fail.
We can confirm that this module has not loaded by running lsmod, and grepping for Veeam. We will see that grep returns 0 lines of output.
Fortunately, the difference in these kernel versions is small enough that the veeamsnap.ko file will still work for us.
First, we need to create the /extra/ directory for our kernel version, then copy the kernel module over to this directory.
Step 3: Enrolling Veeam Kernel Module Key:
Install the package that contains the public key for pre-built Veeam kernel module by using the following command:
We will have the notification like this:
Reboot the computer to enroll the Veeam public key into the UEFI database.
During reboot, when prompted, press any key to perform MOK management.
At the first step of the wizard, select Enroll MOK and press [Enter].
At the Enroll the key(s) step, select Yes and press [Enter].
Provide the password for the root account and press [Enter].
At the final step, select Reboot and press [Enter].
Step 4: Insert module veeamsnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent based backups will run fine; however, the loaded module will not persist if we reboot. We will need to create a file called /etc/modules-load.d/veeam.conf, and make sure that it has the name of the kernel module in it. We will also need to run depmod to add the loaded kernel module into the kernel module dependencies list.
Now, once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
Overview
Procedure
Automatic deployment from the Veeam Service Provider Console is not supported for the following distributions:
Step 5.2 Restore to a new location, or with different settings
When Instant Recovery is performed:
Veeam Backup & Replication uses the Veeam vPower technology to mount a workload image to an ESXi host directly from a compressed and deduplicated backup file.
DO NOT shutdown\Power Of VM to avoid data loss.
Please process step 7 & 8 to complete the recovery.
Important: If the server boots with Secure Boot, we can’t insert the module → Must run step 3 on Secure Boot below first.
Important: The prompt will time out in 10 seconds. If you don't press any key, the system will continue booting without enrolling the key. If you don't enroll the key at reboot, you will have to reconfigure the key by reinstalling the ueficert package and reboot again
3. HI GIO M365 BaaS
Overview
This is a document on how to:
Add New Organizations
Create a Backup Job
Restore on Self-service Restore Portal
Procedure
Step 1: Log in to HI GIO Portal with your company account.
In the Enter Company\User and Enter password fields, specify the credentials of an authorized user.
The user name must be provided in the Company Name\User format.
Click Log in.
Step 1: To launch the New Backup Job wizard:
In the menu on the left, click Backup Jobs.
Open the Microsoft 365 Objects tab.
At the top of the jobs list, click Create Job
Step 1: Open a web browser on any computer and navigate to the Restore Portal web address
Internet Explorer is not supported. To access Restore Portal, use Microsoft Edge (version 79 or later), Mozilla Firefox (version 21 or later), or Google Chrome (version 24 or later).
Log in with the Microsoft Office account that you need to restore items. You must provide a user account in one of the following formats: user@domain.com or .
Step 2: At the top right corner of the HIGIO Portal., click Configuration
Step 3: In the configuration menu on the left, click Plugin Library, then Click the Veeam Backup for Microsoft 365 plugin tile.
Step 4: In the menu on the left, click Organizations, then at the top of the list, click New.
Step 5: At the Protected Services step of the wizard, select Microsoft services that you want to protect (Exchange Online, SharePoint Online and OneDrive for Business, Microsoft Teams, Teams chats).
You can select Microsoft Teams and Teams chats check boxes only if both Exchange Online, SharePoint Online, and OneDrive for Business check boxes are selected.
Step 6: At the Connections Settings step of the wizard, select Microsoft Azure region is Default
Step 7: At the Application Settings step of the wizard, select the Register a new Azure AD application automatically option and specify the name of the new Azure AD application.
[If you have selected to protect SharePoint Online and OneDrive for Business] Select allow this application to enable export mode for SharePoint Web Parts check box to allow Veeam Backup for Microsoft 365 to back up web parts of your Microsoft SharePoint sites. For details on web parts, see Microsoft Docs.
Step 8: At the Microsoft 365 Logon step of the wizard, log in to your Microsoft 365 organization:
Click Copy code to copy an authentication code.
Consider that the code is valid for 15 minutes. You can click Refresh code to request a new code from Microsoft.
Click the Microsoft verification portal link.
A web browser window will open.
On the Sign in to your account webpage, paste the code you have copied and sign in to Microsoft Azure.
Make sure to sign in with the user account that has the Global Administrator role. For details on this role, see Microsoft Docs.
Return to the wizard and click Next when the Verification status: Verified
Step 9: Review organization settings and click Finish at the Summary step of the wizard.
From now on, these steps below just need to be done one time
Step 10: Register AzureADServicePrincipal for Tenant
Azure AD application that end users and restore operators from tenant organizations will use to access Restore Portal must be created for a Microsoft 365 organization on a service provider side.
Open the Powershell
Update PowerShell with Winget by below command
Run the Install-Module cmdlet to install the Azure Active Directory PowerShell for Graph module. For more information, see this Microsoft article.
Open a Windows PowerShell Command Prompt window. Depending on the permissions of your logged-in account, you may need to open the PowerShell window in Administrator mode.
To install the v1 module of the SDK in PowerShell Core or Windows PowerShell, run the following command:
This process may take some time to complete.
Run this command to install the beta module:
Run this command to install AzureAD module:
Register AzureADServicePrincipal with Power Shell
Connect to Organization and register AzureADServicePrincipal using the command below.
Connect-AzureAD
This command to log in to Azure Organization, the please user account that has Global Administrator permission
Step 11: Grant admin consent to this application on behalf of all users in the tenant organization
Access Azure Portal https://portal.azure.com/ with a user account that has Global Administrator permission
Find AzureADServicePrincipal by application ID.
Choose tab permission to Grant admin consent.
and select Backup Job.
Veeam Service Provider Console will open the New Backup Job wizard.
Step 2: At the Job Name step of the wizard, specify the job name and description.
Step 3: At the Organization step of the wizard, choose an organization to back up:
Click Select.
In the Available Organizations window, select an organization to back up.
Click Apply.
Step 4: At the Backup Mode step of the wizard, select the mode in which you want to create a backup:
In the Backup scope section, specify objects to back up:
Select the Entire organization option to back up the whole organization.
Select the Back up the specified objects option to back up individual objects:
Click Configure.
In the Objects to Back up window, select the type of object to back up: User, Group, Site, Teams, Personal Sites, or Current organization.
The list of available objects depends on which Microsoft Online services are selected in the organization settings.
Click Add. In this guide, I choose User for Objects to back up
Select an object in the list to customize processing options, click Edit Processing Options, or click a link in the Processing Options column.
[For User, Teams, Group, and Current organization object types] In the Edit processing options window, select the necessary processing options and click Save.
Note that processing options for Current organization objects will be applied to all users, groups, sites, and teams in the organization.
[For Teams and Current organization object types] You can modify the Chats and Teams chats check boxes only if the Teamschats protected service is selected in the organization settings.
For details about available object types and their processing options, see the section Organization Object Types of the Veeam Backup for Microsoft 365 User Guide.
#Optional: To exclude specific objects, in the Exclusions section, set the toggle to On and specify objects to exclude:
Step 5: Review backup job settings at the wizard's Summary step.
After creating a Backup Job, please contact the support team to apply the daily schedule.
Click Log In.
Restore Portal will redirect you to the Microsoft authentication portal where you will be prompted to enter your Microsoft 365 user account password.
Step 2: Select a restore point from which you want to explore and restore data from backups created by Veeam Backup for Microsoft 365. For more information on how to view and select available restore points in Restore Portal, see Selecting Restore Point.
To view available restore points and select a restore point that you want to use, do the following:
In the upper-left corner of the Restore Portal window, click Select Restore Point or the restore point timestamp.
In the displayed dialog box, do one of the following:
In the calendar, click the date for which Veeam Backup for Microsoft 365 has available restore points. Such dates are marked in bold. The available restore points for the selected date will be displayed on the right.
Click Select Latest Point to select the latest restore point available in a backup repository.
Click Apply.
Step 3: Example with Exchange Restore
To restore Exchange items, do the following:
Open the Explore tab.
Select a restore point from which you want to explore and restore data. For more information, see Selecting Restore Point.
In the navigation pane, browse through the hierarchy of folders with backed-up data.
Select a folder that contains the data you want to restore.
Select check boxes next to the necessary Exchange items in the preview pane.
Click Restore.
The Exchange Restore wizard runs to configure the restore operation options.
Step 4: At the Items step, specify the items you want to restore. If you no longer wish to restore an item, select it and click Remove.
Step 5: At the Restore mode step, select where you want to restore the selected items:
Restore to the original location. Select this option if you want to restore the selected items to their original location.
Restore to a new location. Select this option if you want to restore the selected items to another location and specify the folder name in the Restore to the following folder field. If the specified folder does not exist, it will be created automatically.
Step 6: Click Advanced options to open the Restore options dialog.
In the Restore Options dialog, select check boxes next to the additional options that you want to apply during the restore operation and then click Apply:
Restore changed items. Select this check box if you want to restore items that have been changed.
Restore missing items. Select this check box if you want to restore missing items in the target folder.
Mark restored items as unread. Select this check box if you want to mark each restored item as unread.
Default is all options are selected.
#Optional: At the Reason step, specify a restore reason. This information will be available in the Reason column on the Restore Sessions tab, which you can reference later.
Step 7: At the Summary step, review the details of the restore operation and click Finish.
The Restore Portal runs the restore operation immediately and opens the Restore Sessions tab, where you can view details about the restore session's progress and results.
As we can see, restore items were restored to the Restore folder that we chose and marked as unread.
Restore other items. We can do the same step with Restore Exchange items.
Attention: Backing up Teams chats requires using protected APIs and additional billing charges from Microsoft. For details, see Microsoft Docs. For details on configuring your backup infrastructure to back up Teams chats, see this
This option is not recommended due to the time it takes to back up the whole organization. We should choose what to back up.
