Select Managed Computers > Discovered Computers

Overview

Procedure - Install Veeam Agent for Windows

Overview

Procedure

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

Overview

Procedure

Overview

Procedure

• Wait for Deployment Progress

• Backup Agent updated successfully:

sudo chmod +x LinuxAgentPackages...

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

Log in, then click Configuration:

Overview

Procedure

The Veeam Recovery Media for Linux preparation is completed.

Overview

Procedure - Prepare & setup Veeam Recovery Media for Linux

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 Recovery Media for Windows preparation is completed.

Overview

Procedure - Prepare & setup Veeam Recovery Media for Windows

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:

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

• POWER ON the VM

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.

Choose available Ethernet > Edit

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 Media

POWER ON the VM

Choose available Ethernet > Edit

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.

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

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

• Fedora 36, 37, 38, 39

• openSUSE Tumbleweed.

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

• 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: Make DKMS sign kernel modules on installation, with full script support and somewhat distro independent and put it in the directory just created:

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.