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:
Procedure
1
Step 1: Check and prepare your machine to match the requirements from BaaS Support Matrix:
2
Step 2: Open firewall outbound to Cloud Gateway IP with ports 6180 and 53:
3
Step 3: Access the BaaS portal, download and install the Agent following OS types:
For Server.
For Server.
Manage backup (After installation is completed, you can manage the backup job and machine via the BaaS portal or via the Veeam agent console).
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.
Make sure that you have permission to execute the installation package file.
sudo chmod +x LinuxAgentPackages...
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:
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.
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.
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
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 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 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
Choose available Ethernet > Edit
Input the IP address then choose OK
Choose Restore volumes
Choose AddCloud Connect provider
Enter address of BaaS Cloud Gateway Address:
HCM: backup-hcmc.higio.net
HN: backup-hni.higio.net
Accept the certificate details.
Enter Username and Password
Select Job and restore point that want to restore
Choose Hard disk that want to restore
Enter and select Restore from…
Choose the exact disk want to restore
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 the USB drive
Power on the machine again to boot to the Linux OS that already restored.
Restore Windows on Physical Server by Veeam Recovery Media
Overview
This is a document for how to restore Windows on Physical Server by Veeam Recovery Media.
Procedure
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 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 on Windows OS via Veeam agent console
Overview
This is a document on how to create a backup job on Windows.
Procedure
1
Step 1: Configure job on Veeam Backup Agent
StartVeeam Backup Agent Application
2
Step 2: Create a Back Job
Choose Add New Job…
Input Name and Description for the job
Choose Backup Mode
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
Advantage configuration
Enable or Disable Backup Cache
Enable or Disable Guest Processing (Backup SQL, File index)
Schedule Backup
Check the settings
Run the Backup Job
Create backup job for Linux via Portal
Overview
This is a document on creating a backup job for Linux on Portal.
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.
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.
How to prepare and setup Veeam Recovery Media for Linux
Overview
This is a document on how to prepare and setup Veeam Recovery Media for Linux
Procedure - Prepare & 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.
Choose the correct architectures you want (Example: x64).
2
Step 2: Choose the version you want download, the requirement of our portal will be v13.x and above.
3
Step 3: Validate the ISO file after completed the download progress.
The Veeam Recovery Media for Linux preparation is completed.
Create backup job for Windows via Portal
This is a document on creating a backup job for Windows on Portal.
1
Step 1: Access and login to BaaS portal:
HCM:
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
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.
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.
Choose Server, then Next.
Choose the Backup Mode that you want, then Next.
Choose 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 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.
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
The Veeam repository for Linux can be found at . On this page select "veeam-release-el8-1.0.8-1.x86_64.rpm".
Step 2: Install Veeam:
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.
Step 1: Download Veeam repository:
The Veeam repository for Linux can be found at . On this page select "veeam-release-el8-1.0.8-1.x86_64.rpm".
Step 2: Install Veeam:
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.
Install Veeam Agent for Windows
This is a document on how to install Veeam Agent for Windows.
1
Step 1: Download Veeam Service Provider Console Management Agent
Login to the Web UI with the customer user
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.
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.
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
Select Managed Computers > Discovered Computers
Choose Download Agent > Windows
2
Step 2: Install Windows Management Agent
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
Veeam Agent Installation for CentOS 9 Stream
This document is for installing the Veeam Backup Agent Linux on CentOS 9 Stream.
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.
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.
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.
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: Enrolling Veeam Kernel Module Key:
Create a directory /root/module-signing:
Download 3 scripts from the link: and put it in the directory just created:
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.
