• Linux

• Windows

Via portal:

• Linux

• Windows

Active alarm for a backup job

Please refer to the HI GIO BaaS guide in the list below.

• BaaS Support Matrix

• Install Veeam Agent for Linux

• Install Veeam Agent for Windows

• Update Veeam Service Provider Console Management Agent v.7 & Backup Agent v.6

• Cloud Gateway:

HCM site: backup-hcmc.higio.net (IP address 118.68.171.248 and 118.68.171.233)

HN site: backup-hni.higio.net (IP address 1.55.215.248 and 1.55.215.250)

sudo chmod +x LinuxAgentPackages...

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:

Veeam Backup & Replication 12.3.2 (starting from 12.3.2.3617) and 13.0.1 or later

• Management Agent (Management Agent line): System Requirements - Veeam Service Provider Console Deployment Guide

• Backup Agent Windows: KB2683: Build Numbers and Versions of Veeam Agent for Microsoft Windows

• Backup Agent Linux: KB2681: Build Numbers and Versions of Veeam Agent for Linux

• Linux Backup Agent module: KB2804: Veeam Agent for Linux - veeamsnap and blksnap Extended Linux Distribution Support

Overview

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)

Documentation References

Overview

Procedure - Install Veeam Agent for Windows

Consider the following limitations:

• Linux kernel version 2.6.32 or later is supported as long as you use kernels supplied by your distribution.

• Fedora and openSUSE Tumbleweed are supported up to kernel 6.14.

• Linux kernel 2.6.32 - 754.6.3 in CentOS / RHEL and Oracle Linux (RHCK) is not supported.

• Automatic deployment from the Veeam Service Provider Console is not supported for the following distributions:

  • Fedora 36, 37, 38, 39

  • openSUSE Tumbleweed.

Consider the following limitations:

• Linux kernel version 2.6.32 or later is supported as long as you use kernels supplied by your distribution.

• Linux kernel 2.6.32 - 754.6.3 in RHEL and Oracle Linux (RHCK) is not supported.

• For the full list of limitations, see Veeam Agent for Linux documentation: Veeam Agent for Linux 13 User Guide.

Veeam Agent for Linux supports 32-bit versions of:

• RHEL 6.

• Oracle Linux 6 distributions only.

Limitation: https://helpcenter.veeam.com/rn/veeam_agent_linux_6_3_2_release_notes.html#considerations-and-limitations

Limitation: https://helpcenter.veeam.com/docs/agentforlinux/userguide/system_requirements.html?ver=13#hardware_lim

Input the IP address then choose OK

Choose Restore volumes

Choose Add Cloud 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.

Backup Agent updated successfully:

Choose Server Windows > Management Agent > Upgrade

Wait for Deployment Progress

Overview

Procedure

Overview

Procedure

Overview

Procedure

The Veeam Recovery Media for Linux preparation is completed.

Overview

Procedure - Prepare & setup Veeam Recovery Media for Linux

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.

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

Overview

Procedure

Veeam blksnap module: blksnap-6.0.3.1221-1

Overview

Procedure

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-aware processing 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.

The backup job has been created and completed.

Overview

Procedure

• 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.

The Veeam repository for Linux can be found at Index of /backup/linux/agent/rpm/el/9/x86_64/ . 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.

• 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.

Grand permission for 3 scripts:

# chmod u+x one-time-setup sign-modules dkms-sign-module

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.

Overview

Procedure