Quantcast
Channel: Veeam Support Knowledge Base
Viewing all 4502 articles
Browse latest View live
↧

Granular sudo Permissions for Management of Veeam Agent for Oracle Solaris

October 10, 2024, 5:00 pm
$
0
0

Granular sudo Permissions for Management of Veeam Agent for Oracle Solaris

KB ID: 4674
Product: Veeam Agent for Oracle Solaris | 4.5
Published: 2024-10-11
Last Modified: 2024-10-15

Purpose

This article provides examples of granular ‘sudo’ configuration for the Linux account that will be used by Veeam Backup & Replication when managing Veeam Agent for Oracle Solaris deployments with a Protection Group.

Solution

The following granular sudo permissions were tested with Veeam Agent for Oracle Solaris 4.5 and Veeam Backup & Replication 12.2.
Veeam Agent for Oracle Solaris - Intel x86 
#MISC
veeamdep ALL=(root) /usr/bin/whoami

#MKDIR
veeamdep ALL=(root) /usr/bin/mkdir -p /opt/veeam

#RM
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/veeaminstaller_solaris_x64
veeamdep ALL=(root) /usr/bin/rm -f /tmp/VeeamAgentSolaris-*-i386.tar
veeamdep ALL=(root) /usr/bin/rm /tmp/VeeamAgentSolaris-*-i386.tar
veeamdep ALL=(root) /usr/bin/rm /tmp/VeeamAgent-*-i386.pkg
veeamdep ALL=(root) /usr/bin/rm /tmp/mlocate-*-i386.pkg
veeamdep ALL=(root) /usr/bin/rm /tmp/xorriso-*-i386.pkg
veeamdep ALL=(root) /usr/bin/rmdir /opt/veeam/Upload
veeamdep ALL=(root) /usr/bin/rmdir /opt/veeam

#DEPLOYMENT INSTALL RESCAN
veeamdep ALL=(root) /usr/bin/digest -a md5 /opt/veeam/veeaminstaller_solaris_x64
veeamdep ALL=(root) /usr/bin/touch /opt/veeam/veeaminstaller_solaris_x64
veeamdep ALL=(root) /usr/bin/chmod 0750 /opt/veeam/veeaminstaller_solaris_x64
veeamdep ALL=(root) /usr/bin/cp -f /export/home/veeamdep/* /opt/veeam/veeaminstaller_solaris_x64
veeamdep ALL=(root) /usr/bin/chown root* /opt/veeam/veeaminstaller_solaris_x64
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_x64 system-info --format VBR
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_x64 agent-version
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_x64 check-package-name --name VeeamAgent
veeamdep ALL=(root) /usr/bin/gunzip /tmp/VeeamAgentSolaris-*-i386.tar.gz
veeamdep ALL=(root) /usr/bin/tar -tf /tmp/VeeamAgentSolaris-*-i386.tar
veeamdep ALL=(root) /usr/bin/sh -c cd /tmp && tar -xf /tmp/VeeamAgentSolaris-*-i386.tar
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_x64 install-packages --packages /tmp/VeeamAgent-*-i386.pkg
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_x64 update-packages --packages /tmp/VeeamAgent-*-i386.pkg
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_x64 remove-packages --packages VeeamAgent

#VEEAMCONFIG
veeamdep ALL=(root) /usr/sbin/veeamconfig vbrcmd print --agentInfo
veeamdep ALL=(root) /usr/sbin/veeamconfig --stdin
Veeam Agent for Oracle Solaris - Oracle SPARC 
#MISC
veeamdep ALL=(root) /usr/bin/whoami

#MKDIR
veeamdep ALL=(root) /usr/bin/mkdir -p /opt/veeam

#RM
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/veeaminstaller_solaris_sparc64
veeamdep ALL=(root) /usr/bin/rm -f /tmp/VeeamAgentSolaris-*-sparc.tar
veeamdep ALL=(root) /usr/bin/rm /tmp/VeeamAgentSolaris-*-sparc.tar
veeamdep ALL=(root) /usr/bin/rm /tmp/VeeamAgent-*-sparc.pkg
veeamdep ALL=(root) /usr/bin/rm /tmp/mlocate-*-sparc.pkg
veeamdep ALL=(root) /usr/bin/rm /tmp/xorriso-*-sparc.pkg
veeamdep ALL=(root) /usr/bin/rmdir /opt/veeam/Upload
veeamdep ALL=(root) /usr/bin/rmdir /opt/veeam

#DEPLOYMENT INSTALL RESCAN
veeamdep ALL=(root) /usr/bin/digest -a md5 /opt/veeam/veeaminstaller_solaris_sparc64
veeamdep ALL=(root) /usr/bin/touch /opt/veeam/veeaminstaller_solaris_sparc64
veeamdep ALL=(root) /usr/bin/chmod 0750 /opt/veeam/veeaminstaller_solaris_sparc64
veeamdep ALL=(root) /usr/bin/cp -f /export/home/veeamdep/* /opt/veeam/veeaminstaller_solaris_sparc64
veeamdep ALL=(root) /usr/bin/chown root* /opt/veeam/veeaminstaller_solaris_sparc64
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_sparc64 system-info --format VBR
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_sparc64 agent-version
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_sparc64 check-package-name --name VeeamAgent
veeamdep ALL=(root) /usr/bin/gunzip /tmp/VeeamAgentSolaris-*-sparc.tar.gz
veeamdep ALL=(root) /usr/bin/tar -tf /tmp/VeeamAgentSolaris-*-sparc.tar
veeamdep ALL=(root) /usr/bin/sh -c cd /tmp && tar -xf /tmp/VeeamAgentSolaris-*-sparc.tar
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_sparc64 install-packages --packages /tmp/VeeamAgent-*-sparc.pkg
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_sparc64 update-packages --packages /tmp/VeeamAgent-*-sparc.pkg
veeamdep ALL=(root) /opt/veeam/veeaminstaller_solaris_sparc64 remove-packages --packages VeeamAgent

#VEEAMCONFIG
veeamdep ALL=(root) /usr/sbin/veeamconfig vbrcmd print --agentInfo
veeamdep ALL=(root) /usr/sbin/veeamconfig --stdin
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
Search

Best Practice Guide for SQL Server Hosting Veeam Service Provider Console Configuration Database

October 10, 2024, 5:00 pm
$
0
0

Optimizing and Maintaining SQL Server Instance Hosting Veeam Service Provider Console Configuration Database

KB ID: 4670
Product: Veeam Service Provider Console | 8.0 | 8.1
Published: 2024-10-11
Last Modified: 2024-10-17

Purpose

This article was produced in coordination with the Veeam R&D team to provide Service Providers with a comprehensive list of the most common performance improvements and maintenance actions relating to the underlying Microsoft SQL Server instance that hosts the Veeam Service Provider Console configuration database.

The information, advice, and scripts provided in this article are provided as a courtesy. Assistance with implementing the configuration advice provided in this document is outside the scope of Veeam Support.
If you have feedback regarding the content of this article, please use the Article Feedback form.

Solution

This guide has been broken down into expandable sections below.
System Requirements and Sizing Guidelines
Check if your MS SQL Server follows the VSPC Sizing Guidelines recommendations:
SQL Server Instance Memory Configuration Options

Memory utilization for the SQL Server Database Engine is bounded by a pair of configuration settings, min server memory (MB) and max server memory (MB). Over time and under normal circumstances, SQL Server will attempt to claim memory up to the limit set by max server memory (MB).

Use max server memory (MB) to guarantee the OS and other applications don't experience detrimental memory pressure from SQL Server. Before you set the max server memory (MB) configuration, monitor the overall memory consumption of the server hosting the SQL Server instance during regular operation to determine memory availability and requirements.

Use SQL Server Management Studio to set server memory options:

  1. In Object Explorer, right-click a server and select Properties.
Properties
  1. Select the Memory page of the Server Properties window. The current values of Minimum server memory and Maximum server memory are displayed.
Memory Settings
  1. In Server memory options, enter desired numbers for Minimum server memory and Maximum server memory. For recommendations, see min server memory (MB) and max server memory (MB).
Managing SQL Server Data and Log Files

To manage data and log files, ensure the following:

  • Data and log files are on separate drives from each other and from all other files. The drive containing the data should contain only data (no logs), and the drive containing the log files should contain only log files (no data).
  • Using SSD for better I/O performance.
  • Auto-growth is correctly configured (10% by default).
  • Instant file initialization is configured.
  • Auto-shrink is not enabled and shrink is not part of any maintenance plans.

    If auto-shrink is enabled, disable it by using the following command:
ALTER DATABASE VSPC SET AUTO_SHRINK OFF;
Monitoring Physical Disks Performance

Performance Monitor is a built-in Windows Tool for monitoring all aspects of Windows and hosted applications such as SQL Server. A Data Collector Set is used to organize and schedule performance counter data as a single collection to be analyzed later.

To create a Data Collector Set for your physical disks:

  1. Launch the Performance Monitor (perfmon).
Run
perfmon
  1. In the Performance Monitor navigation pane, expand Data Collector Sets.
  2. Right-click User Defined, point to New, and click Data Collector Set.
New Data Collector
  1. Enter a name for the Data Collector Set and select Create manually, then click Next.
Set name and select manually create
  1. Select Create data logs, check the Performance counter box, and click Next.
Create logs and performance counters.
  1.  Click Add to open the Add Counters dialog box.
Add Counters
  1. Find and click the category entry PhysicalDisk, the Instances of selected object section will update.
Select Physical disk
  1. Double click <All instance> to add the PhsysicalDisk counters to the Added counters list, then click OK.
Add counters to list
  1. Click Finish to exit and save the current configuration.
Finish and save
  1. Start the created data collector set by right-clicking on it and selecting Start.
Start data set
  1. After a while, stop the data collection by clicking the Stop the Data Collector Set button.
Stop data collection
Results will be shown in the Reports folder in the navigation pane. It is important for the Avg. Disk Queue Length counter to have a value less than 1. Otherwise, it could mean that the system has poor disk performance.
Review
Reviewing SQL Server Logs

There are several areas where SQL Server logs information about processes that are occurring as well as errors that occur.  The most used is probably the SQL Server Error Log.  This error log provides startup information, integrity check information, backup information, and other information, as well as any SQL Server errors that occur.

To get to the MS SQL Server Logs, follow these steps:

  1. In Object Explorer, expand the Management node and the SQL Server Logs node.
  2. Right-click on the Current log entry and select View SQL Server Log.
View Logs
  1. In the Log File Viewer, you can analyze and export logs.
Monitoring VSPC Database Staging Tables

Almost all of the data collected by VSPC goes through Staging tables. It is important that these tables maintain as near to zero records as possible. If the number of records continues to increase, it could indicate that there is a performance issue.

To check how many records Staging tables have:

  1. In Object Explorer, right-click the VSPC database and go to the Reports -> Standard Reports, select the Disk Usage by Top Tables report.
disk usage table
  1. Check how many records VeeamBP.Staging and VeeamOD.Staging tables have.
staging tables
If either table has more than 5 million records, it could indicate performance issues. In such a situation, wait a couple of hours a generate the Disk Usage by Top Tables report again, and if the number of records hasn’t gone down – contact Veeam Support.
Database Shrinking Considerations

To view the current amount of free (unallocated) space in the database, see Display Data and Log Space Information for a Database.

Shrink Considerations and Limitations

Consider the following information when you plan to shrink a database:

  • A shrink operation is most effective after an operation that creates a large amount of unused storage space, such as a large DELETE statement, truncate table, or a drop table operation.
  • Most databases require some free space to be available for regular day-to-day operations. If you shrink a database repeatedly and notice that the database size grows again, this indicates that the free space is required for regular operations. In these cases, repeatedly shrinking the database is a wasted operation. Repeatedly shrinking the database causes the SQL instance to trigger autogrow events to grow the database file(s), which hinders performance.
  • A shrink operation doesn't preserve the fragmentation state of indexes in the database and generally increases fragmentation to a degree. This is another reason not to shrink the database repeatedly.
  • Unless you have a specific requirement, do not set the AUTO_SHRINK database option to ON.

Shrink operations in progress can block other queries on the database and can be blocked by queries already in progress.

Database Shrinking Documentation
Fragmentation Impact of Shrinking Database

Data that is moved to shrink a file can be scattered to any available location in the file. This causes index fragmentation and can slow the performance of queries that search a range of the index. To eliminate the fragmentation, consider rebuilding the indexes on the file after shrinking.

Rebuilding Table Indexes

Index and data pages can experience internal fragmentation. Index and table structures can experience logical scan and extent scan fragmentation. Periodically check index fragmentation of the VSPC database. The most sensitive tables for index fragmentation are:

  • VeeamBP. ObjectEntityPropertyValue
  • VeeamOD. ObjectEntityPropertyValue
  • VeeamBP.ObjectEntity
  • VeeamOD.ObjectEntity

Check Index Fragmentation using SQL Server Management Studio:

  1. Right-click the VSPC database and choose Reports -> Standard Reports.
  2. Select the Index Physical Statistics report.

You’ll see table names, indexes, and operation recommendations in that report. Follow the recommendations and rebuild\reorganize indexes.

Rebuild vs Reorganize Indexes

Please note that rebuilding indexes is a heavy task that can take a lot of time. Additionally, online indexing can only be done with the Enterprise Edition of Microsoft SQL Server. In other editions of the SQL Server, only offline indexing is available, meaning tables having their indexes rebuilt will be locked during the rebuild operation. Reorganizing the index, on the other hand, is less heavy an operation and can be done online with all editions. Generally speaking, reorganizing indexes is preferable to rebuilding when possible.

How to Rebuild Indexes (Offline)
  1. In Object Explorer, select the plus sign next to the VSPC database.
  2.  Expand the Tables folder.
  3.  Select the plus sign to expand the table whose indexes you want to rebuild.
  4.  Expand the Indexes folder.
  5.  Right-click the index that you want to rebuild and select Rebuild.
  6. In the Rebuild Indexes dialog box, verify that the correct index is in the Indexes to be rebuilt list and click OK.
How to Rebuild Indexes (Online)

For information about rebuilding Indexes (Online) with SQL Server Enterprise Edition, please review Microsoft documentation:
SQL Server - Perform index operations online - Use SQL Server Management Studio

How to Reorganize Indexes
  1. In Object Explorer, select the plus sign next to the VSPC database.
  2.  Expand the Tables folder.
  3.  Select the plus sign to expand the table whose indexes you want to reorganize.
  4.  Expand the Indexes folder.
  5. Right-click the index that you want to reorganize and select Reorganize.
  6. In the Reorganize Indexes dialog box, verify that the correct index is in the Indexes to be reorganized list and click OK.
Updating Table and Index Statistics
Ensure that the statistics describing the distribution of data values in a table or index are accurate and up-to-date. Updated statistics provide the query optimizer with the best possible information for generating query plans. Statistics are updated when they are created or modified, and they are also periodically updated by SQL Server unless the administrator has disabled automatic statistics updates. Auto Update Statistics doesn’t work for filtered indexes; those indexes need to be updated manually.
Check if Auto Update Statistics is ON
  1. Right-click the VSPC database and choose Properties.
  2. In the navigation menu on the left, select Options.
  3. Check if Auto Update Statistics has the True value and set it to the True if it’s not.
  4. Click OK to close the Database Properties.
Auto Update Statistics
Check VSPC Database Statistics Relevancy

You can check how irrelative the statistics are in your VSPC DB using the following query:

set transaction isolation level read uncommitted;

select quotename( sh.[name] ) + N'.' + quotename( t.[name] ) as [object_name]
     , s.stats_id
     , quotename( s.[name] ) as stat_name
     , s.auto_created
     , s.user_created
     , s.no_recompute
     , replace( sc.stat_columns, N'] [', N'], [' ) as stat_columns
     , cast( sp.last_updated as datetime2( 3 ) ) as last_updated
     , sp.[rows]
     , sp.rows_sampled
     , sp.steps
     , sp.modification_counter
     , ltrim( format( cast( sp.modification_counter as decimal( 20, 2 ) ) / cast( sp.[rows] as decimal( 20, 2 ) ), N'# ##0.00 %' ) ) as irrelevance
     , s.filter_definition    
  from sys.schemas sh
    inner join
      sys.tables t on t.[schema_id] = sh.[schema_id]
    inner join
      sys.stats s on s.[object_id] = t.[object_id]
    outer apply
      ( select quotename( c.[name] ) as [data()]
          from sys.stats_columns sc 
            inner join
              sys.columns c on c.[object_id] = sc.[object_id] and c.column_id = sc.column_id
          where sc.[object_id] = s.[object_id] 
            and sc.stats_id = s.stats_id
          order by sc.stats_column_id
          for xml path( '' ) ) sc( stat_columns )
    outer apply
      sys.dm_db_stats_properties( s.[object_id], s.stats_id ) as sp
  order by [object_name], s.stats_id;
go
How to Update a Statistics Object (using SQL Server Management Studio)
  1. In Object Explorer, select the plus sign next to the VSPC database.
  2.  Expand the Tables folder.
  3.  Select the plus sign to expand the table whose statistic you want to update.
  4.  Expand the Statistics folder.
  5. Right-click the statistics object you wish to update and select Properties.
  6. In the Statistics Properties dialog box, select the check box labeled "Update statistics for these columns" and click OK.
Update Stats

How to Update a Single Statistics Object using Transact-SQL

  1. Connect to the SQL Server instance.
  2. Click New Query.
  3. Copy and paste the following example into the query window and click Execute.
    Note: The statistic in this example can be changed to any statistic you'd like to update.
-- Use the name of your VSPC database instead of the VSPC_DB_NAME
USE VSPC_DB_NAME;
GO
-- The following example updates the statistics for the INDX_ObjectEntityPropertyValue_IsDeleted_DateTime index of the VeeamBP.ObjectEntityPropertyValue table. 
UPDATE STATISTICS VeeamBP.ObjectEntityPropertyValue
INDX_ObjectEntityPropertyValue_IsDeleted_DateTime;
GO

How to Update all Statistics for a Specific Table using Transact-SQL

  1. Connect to the SQL Server instance.
  2. Click New Query.
  3. Copy and paste the following example into the query window and click Execute.
    Note: The table in this example can be changed to any table whose statistics you'd like to update.
-- Use the name of your VSPC database instead of the VSPC_DB_NAME
USE VSPC_DB_NAME;   
GO  
-- The following example updates the statistics for all indexes on the VeeamBP.ObjectEntityPropertyValue table.
UPDATE STATISTICS VeeamBP.ObjectEntityPropertyValue;   
GO

How to Update all Statistics in a Specific Database using Transact-SQL

  1. Connect to the SQL Server instance.
  2. Click New Query.
  3. Copy and paste the following example into the query window and click Execute.
    Note: The statistic in this example can be changed to any statistic you'd like to update.
-- Use the name of your VSPC database instead of the VSPC_DB_NAME
USE VSPC_DB_NAME;   
GO  
-- The following example updates the statistics for all tables in the database.  
EXEC sp_updatestats;
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
↧

How to add SMB repository to Veeam Backup for Microsoft 365

October 14, 2024, 5:00 pm
$
0
0

How to add SMB repository to Veeam Backup for Microsoft 365

KB ID: 2971
Product: Veeam Backup for Microsoft 365 | 7.0 | 7a | 8
Published: 2019-06-26
Last Modified: 2024-10-15
Planned Feature Deprecation
Veeam Backup for Microsoft 365 support for SMB-based repositories will be deprecated in a future version.
For more information, see KB4567: Planned Veeam Backup for Microsoft 365 Feature Deprecation.
Experimental Support

SMB repository is considered as experimental support in the current version. 

If a storage device supports both SMB 3.0 and iSCSI protocol, the best practice would be to use iSCSI due to its use of Disk Queue, which acts as a buffer space for data to land on before being sent off to disk.

Purpose

This article covers two most popular scenarios of adding an SMB 3.0 repository to Veeam Backup for Microsoft 365

Note: If the SMB 3.0 share is a Windows-based shared folder, then it is recommended to add the server it’s based on as a proxy and connect the same storage as a directly attached disk. 

Cause

Due to the fact that all Veeam Backup for Microsoft 365 services must be run as the SYSTEM account, access to the SMB 3.0 share must be granted to the server itself rather than to a particular user.  

Solution

Scenario 1: Microsoft Windows SMB share with authorization

Prerequisites:

  • To use the SMB 3.0 share as a storage system, make sure you are using Windows 8/Server 2012 or later; older OS versions do not support the SMB 3.0 share as a storage system.
  • The Veeam Servers and the SMB share location must be deployed within the same or a trusted domain.
     
Configuration
  1. Open folder sharing settings for planned repository location and add all Veeam servers using their computer names.

    For example, if your Veeam server is called WIN-F4N92CDLKET, the list would look like this:
SMB Permissions Example
  1. Add the SMB 3.0 repository to Veeam Backup for Microsoft 365.

Scenario 2: Standalone storage appliance

In this example, we will use a Synology appliance, but the same method should work for any standalone device that supports Microsoft Active Directory and its computer groups. 

  1. Add the Veeam server and all remote backup proxies (if any) to the Active Directory domain.
  2. Create an Active Directory group in this domain and add all Veeam servers to it as “computer” objects:User-added image
  3. Add the storage device to the same domain:
    User-added image
  4. Make sure that SMB 3.0 protocol is enabled, and previous versions are not allowed to use:
    User-added image
  5. Create SMB shared folder and grant read/write access to it for the domain group that was created earlier:
    User-added image
  6. Add the SMB 3.0 repository in Veeam Backup for Microsoft 365.

Scenario 2 Alternate: Add standalone storage appliance using iSCSI protocol (Best Practice)

In this scenario, we will use the Synology appliance as an example, but the same method would work for any storage appliance that supports the iSCSI protocol.

  1. Within the Storage Appliance, open the iSCSI manager and create a new LUN and Target:
    User-added image
  2. On the Veeam Backup for Microsoft 365 server:
    1. Open the iSCSI Initiator
    2. Enter your storage appliance IP address
    3. Click “Quick Connect…”
    4. Click “Done”
      User-added image
    5. Open Disk Management, bring the iSCSI disk online, and initialize it using default parameters:
      User-added image
      User-added image
    6. Create a new simple volume using default parameters:
      User-added image
    7. Create a new repository for the disk in Veeam Backup for Microsoft 365.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Granular sudo Permissions for Management of Veeam Agent for Linux Deployments

October 17, 2024, 5:00 pm
$
0
0

Granular sudo Permissions for Management of Veeam Agent for Linux Deployments

KB ID: 2676
Product: Veeam Backup & Replication | 12 | 12.1
Veeam Agent for Linux | 6.0 | 6.1
Published: 2018-07-02
Last Modified: 2024-10-18
Veeam Backup & Replication 12.1 New Feature

Starting in Veeam Backup & Replication v12.1, it is now possible to deploy Veeam Agent for Linux using pre-installed Veeam Deployer Service and add that machine to a Protection Group using certificate-based authentication instead of credentials.

Veeam now recommends this new highly secure method of managing Veeam Agent for Linux deployments as a more secure alternative to password-based authentication and granular sudo configuration.

Article Applicability

The granular sudo permissions example provided in this article is intended for use with Protection Groups managing Veeam Agent for Linux deployments.

These granular sudo permissions are NOT for use with any other Linux-related task that Veeam Backup & Replication performs (e.g., Linux Hardened Repository, Linux Proxy, etc).

Purpose

This article provides examples of granular ‘sudo’ configuration for the Linux account that will be used by Veeam Backup & Replication when managing Veeam Agent for Linux deployments with a Protection Group.

Cause

Per the Agent Management User Guide, a user account for Agent Management should have administrative permissions on the computer you want to add to a protection group or a job. If you would like to avoid using the ‘root’ account in favor of a sudoer account, you may also want to set permissions granularly for one. This document helps you to achieve this goal.

Solution

  • Linux user account used by Veeam Backup & Replication for any Veeam Agent for Linux deployment and management operations must have /bin/bash shell set by default.
  • The account must have either ‘root’ or permissions to execute a specific list of commands as a sudoer on the target Linux machine. (See examples below.)
Distro-specific sudoers Examples
The examples below were developped for specific Linux distros, which will be indicated before each example. Process locations may need to be adjusted if using a different distro.
Veeam Agent for Linux 6.1.x / Veeam Backup & Replication 12.1.x
The example /etc/sudoers below is valid for for RHEL, SLES, Debian, and Ubuntu.
Optional Additional Customization

In the sudoers example below, there are four lines under #DEPLOYMENT INSTALL (lines # 16, 18,20, and 22) that, by default, utilize a wildcard for the package version (e.g., /tmp/veeamdeployment-12.1.*-1.x86_64.rpm). You may optionally choose to update those lines with the precise package file names found on the Veeam Backup Server in:

C:\Program Files\Veeam\Backup and Replication\Backup\Packages

For example, Veeam Backup & Replication 12.1.0.2131 uses deployment packages named:

  • veeamdeployment_12.1.0.2131_amd64.deb
  • veeamdeployment-12.1.0.2131-1.x86_64.rpm
#MISC 
veeamdep ALL=(root) /usr/bin/id -au
veeamdep ALL=(root) /usr/bin/whoami

#MKDIR
veeamdep ALL=(root) /bin/mkdir -p /opt/veeam

#RM
veeamdep ALL=(root) /bin/rmdir /opt/veeam
veeamdep ALL=(root) /bin/rmdir /opt/veeam/Upload
veeamdep ALL=(root) /bin/rm -rf /opt/veeam/deployment/
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/ValPackageIndex.xml

#DEPLOYMENT INSTALL
veeamdep ALL=(root) /bin/yum --assumeyes --errorlevel=0 install /tmp/veeamdeployment-12.1.*-1.x86_64.rpm
veeamdep ALL=(root) /bin/yum --assumeyes --errorlevel=0 remove veeamdeployment
veeamdep ALL=(root) /bin/rpm --install /tmp/veeamdeployment-12.1.*-1.x86_64.rpm
veeamdep ALL=(root) /bin/rpm --erase veeamdeployment
veeamdep ALL=(root) /usr/bin/dpkg --force-confold --install /tmp/veeamdeployment_12.1.*_amd64.deb
veeamdep ALL=(root) /usr/bin/dpkg --purge veeamdeployment
veeamdep ALL=(root) /usr/bin/zypper --terse --non-interactive --no-gpg-checks install --auto-agree-with-licenses --force-resolution /tmp/veeamdeployment-12.1.*-1.x86_64.rpm
veeamdep ALL=(root) /usr/bin/zypper --terse --non-interactive --no-gpg-checks remove veeamdeployment

#DEPLOYMENT SERVICE
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --dll-version
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --get-port
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --uninstall
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --set-user veeamdep
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --disable-restricted-mode
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --set-base-log-path /var/log/VeeamBackup
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --restart
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --get-fingerprint
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --install 6160
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --install-server-certificate /tmp/VeeamUpload*/ServerCertificate
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --install-certificate /tmp/VeeamUpload*/ClientCertificate
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --set-max-log-size 10485760
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --set-max-log-count 10
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --get-bios-uuid

#TRANSPORT
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport --version
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport-link --get-user
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport --disable-restricted-mode
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport-link --set-user root

#VEEAMCONFIG
veeamdep ALL=(root) /usr/bin/veeamconfig vbrcmd print --agentInfo
veeamdep ALL=(root) /usr/bin/veeamconfig --stdin
Veeam Agent for Linux 6.0.x / Veeam Backup & Replication 12.0.x
Example /etc/sudoers entries for RHEL and SLES:
#MISC
veeamdep ALL=(root) /usr/bin/arch
veeamdep ALL=(root) /usr/bin/md5sum /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/echo $HOME
veeamdep ALL=(root) /usr/bin/ls /opt/veeam/transport/veeamtransport-link
veeamdep ALL=(root) /usr/bin/ls /opt/veeam/deployment/veeamdeploymentsvc
veeamdep ALL=(root) /usr/bin/ls /opt/veeam/transport/veeamtransport
veeamdep ALL=(root) /bin/tar xvzf /tmp/VeeamDeploymentSvc_12.* -C /opt/veeam/deployment --no-same-owner
veeamdep ALL=(root) /usr/bin/id -au
veeamdep ALL=(root) /usr/bin/whoami

#MKDIR
veeamdep ALL=(root) /bin/mkdir -p /opt/veeam
veeamdep ALL=(root) /bin/mkdir --parents /opt/veeam/Upload/*
veeamdep ALL=(root) /bin/mkdir --parents /opt/veeam/deployment

#CP
veeamdep ALL=(root) /usr/bin/cp -f /home/veeamdep/* /tmp/VeeamDeploymentSvc_12*
veeamdep ALL=(root) /usr/bin/cp -f /home/veeamdep/* /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /usr/bin/cp -f /home/veeamdep/* /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/cp -f /home/veeamdep/* /opt/veeam/Upload/*

#RM
veeamdep ALL=(root) /bin/rmdir /opt/veeam*
veeamdep ALL=(root) /usr/bin/rm -rf /opt/veeam/Upload/*
veeamdep ALL=(root) /bin/rm -rf /opt/veeam/deployment
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/Upload/*
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/*
veeamdep ALL=(root) /usr/bin/rm /opt/veeam/deployment/certs/*
veeamdep ALL=(root) /usr/bin/rm /opt/veeam
veeamdep ALL=(root) /usr/bin/rm -f /tmp/VeeamDeploymentSvc_12.*

#TOUCH
veeamdep ALL=(root) /usr/bin/touch /tmp/VeeamDeploymentSvc_12*
veeamdep ALL=(root) /usr/bin/touch /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /usr/bin/touch /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/touch /opt/veeam/Upload/*

#CHGRP
veeamdep ALL=(root) /usr/bin/chgrp root /opt/veeam/veeaminstaller

#CHOWN
veeamdep ALL=(root) /usr/bin/chown * /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/chown root /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/chown -hR root /opt/veeam/deployment
veeamdep ALL=(root) /usr/bin/chown * /opt/veeam/ValPackageIndex.xml

#CHMOD
veeamdep ALL=(root) /usr/bin/chmod 0766 /opt/veeam/Upload/*
veeamdep ALL=(root) /usr/bin/chmod 0750 /home/veeamdep/*
veeamdep ALL=(root) /usr/bin/chmod 0750 /opt/veeam/veeaminstaller
veeamdep ALL=(root) /usr/bin/chmod 0644 /tmp/VeeamDeploymentSvc_12*
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/Upload
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/PackagesRegistry/VeeamTransport/PackageInfo
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/PackagesRegistry/VeeamTransport
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/PackagesRegistry
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/ca-trusted
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/scripts
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/certs
veeamdep ALL=(root) /usr/bin/chmod 755 /opt/veeam/deployment/certs/client
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/ca-trusted/DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crt.pem
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/ca-trusted/DigiCertTrustedRootG4.crt.pem
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/libVeeamDeploymentDll.so
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/scripts/veeamdeployment
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/scripts/veeamdeployment.service
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/VeeamDeploymentConfig
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/certs/client/cert_*.pem
veeamdep ALL=(root) /usr/bin/chmod 644 /opt/veeam/deployment/certs/cert.p12
veeamdep ALL=(root) /usr/bin/chmod 744 /opt/veeam/deployment/veeamdeploymentsvc
veeamdep ALL=(root) /usr/bin/chmod 0750 /opt/veeam/ValPackageIndex.xml

#FIND
veeamdep ALL=(root) /usr/bin/find /opt/veeam/deployment -type f -not -path /opt/veeam/deployment/veeamdeploymentsvc
veeamdep ALL=(root) /usr/bin/find /opt/veeam/deployment -type d

#DEPLOYMENT SERVICE
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --dll-version
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --get-port
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --uninstall
#
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --set-user veeamdep
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --disable-restricted-mode
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --set-base-log-path /var/log/VeeamBackup
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --restart
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --install-server-certificate /opt/veeam/Upload/*
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --get-fingerprint
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --install-certificate /opt/veeam/Upload/*
veeamdep ALL=(root) /opt/veeam/deployment/veeamdeploymentsvc --install 6160

#INSTALLER
veeamdep ALL=(root) /opt/veeam/veeaminstaller --install-info VAL --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --package-name-pattern-for-file-name --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --check-package-name * --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --install-packages * --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --agent-version --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --driver-version --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --system-info VBR --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --agent-version --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --check-system-support --packages-index-xml /opt/veeam/ValPackageIndex.xml
veeamdep ALL=(root) /opt/veeam/veeaminstaller --check-package-name VeeamPluginforOracleRMAN --packages-index-xml /opt/veeam/ValPackageIndex.xml

#TRANSPORT
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport --version
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport --get-port
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport-link --version
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport-link --get-user
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport --disable-restricted-mode
veeamdep ALL=(root) /opt/veeam/transport/veeamtransport-link --set-user root

#VEEAMCONFIG
veeamdep ALL=(root) /bin/veeamconfig vbrcmd print --agentInfo
veeamdep ALL=(root) /bin/veeamconfig --stdin acquireAgent *
veeamdep ALL=(root) /bin/veeamconfig --stdin print *
veeamdep ALL=(root) /bin/veeamconfig --stdin setCertificate *
veeamdep ALL=(root) /bin/veeamconfig --stdin
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Error: Failed to verify [C:\windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature.

October 17, 2024, 5:00 pm
$
0
0

Error: Failed to verify [C:\windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature.

KB ID: 4677
Product: Veeam Backup & Replication | 12.2
Veeam Agent for Microsoft Windows | 6.2
Published: 2024-10-18
Last Modified: 2024-10-18

Challenge

  • When Veeam Backup & Replication is attempting to install Veeam Agent for Microsoft Windows backup agents on a machine the procedure fails with: 
    Unable to install backup agent: failed to connect to <hostname> Error: Failed to verify [C:\windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature.
failed to verify error
  • When attempting to add a Windows machine to the Managed Servers section of Veeam Backup & Replication, the New Windows Server wizard displays the error: 
    Failed to upgrade Installer's DLL.
failed to upgrade

Cause

These errors may occur for any of the following reasons:

  • The root CA certificates that are needed to verify the uploaded VeeamDeploymentDll.dll are not present on the remote Windows machine.
  • Access to the folderC:\Windows\Veeam\Backup\Upload\ where VeeamDeploymentDll.dll was uploaded is limited, or the file is locked by antivirus and cannot be accessed.

Solution

Review the following possible solutions that Veeam Support has identified based on support cases:

  • For Veeam Agent for Microsoft Windows deployments, review certificate troubleshooting information on KB2566.
  • Check if VeeamDeployment.dll is present in:
    C:\Windows\Veeam\Backup\Upload\
    If present, delete it and re-attempt the original task that failed.
  • If security software (e.g., antivirus or antimalware) is running on the destination machine, ensure that an exclusion has been created for the folder, and subfolders of: C:\Windows\Veeam\Backup\
    Veeam Backup & Replication Exclusions: KB2034
    Veeam Agent for Microsoft Windows Exclusions: KB2034

More Information

To more accurately identify the issue, investigate C:\ProgramData\Veeam\Backup\Svc.VeeamInstaller.log from the remote Windows machine where the deployment dll could not be verified: 

Log entry examples:

  • The following is an example from an environment where the necessary root CA certificates were not present and could not be automatically installed by the OS (e.g., network connection security or group policy security):
    Note the specific error text: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    Upgrading DeploymentDll. New library: [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll]
  Verifying [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature.
    Certificate chain
      Trust status error:     CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION CERT_TRUST_IS_PARTIAL_CHAIN (0x01010040)
      Trust status info:      (0x00000000)
      Simple chain #0
        Count of elements:    2
        Trust status info:    (0x00000000)
        Trust status error:   CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION CERT_TRUST_IS_PARTIAL_CHAIN (0x01010040)
        Element #0
          Trust status info:  CERT_TRUST_HAS_KEY_MATCH_ISSUER CERT_TRUST_HAS_PREFERRED_ISSUER (0x00000102)
          Trust status error: CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION (0x01000040)
          Extended error:     <null>
        Element #1
          Trust status info:  CERT_TRUST_HAS_KEY_MATCH_ISSUER (0x00000002)
          Trust status error: CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION (0x01000040)
          Extended error:     <null>
    Certificate chain
      Trust status error:     CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION CERT_TRUST_IS_PARTIAL_CHAIN (0x01010040)
      Trust status info:      (0x00000000)
      Simple chain #0
        Count of elements:    2
        Trust status info:    (0x00000000)
        Trust status error:   CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION CERT_TRUST_IS_PARTIAL_CHAIN (0x01010040)
        Element #0
          Trust status info:  CERT_TRUST_HAS_KEY_MATCH_ISSUER CERT_TRUST_HAS_PREFERRED_ISSUER (0x00000102)
          Trust status error: CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION (0x01000040)
          Extended error:     <null>
        Element #1
          Trust status info:  CERT_TRUST_HAS_KEY_MATCH_ISSUER (0x00000002)
          Trust status error: CERT_TRUST_REVOCATION_STATUS_UNKNOWN CERT_TRUST_IS_OFFLINE_REVOCATION (0x01000040)
          Extended error:     <null>
    CN: [Veeam Software Group GmbH], complete: [0], valid: [1], root CA: [n/a]
    CN: [Veeam Software Group GmbH], complete: [0], valid: [1], root CA: [n/a]
    Failed to verify file using the Authenticode provider. Verification status: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (-2146762487), last error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (2148204809)
  Verifying [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature. Failed.

  • The following is an example from an environment where Veeam Backup & Replication was able to successfully upload VeeamDeploymentDll.dll to the C:\Veeam\Backup\Upload\ folder, but before the dll could be verified and moved, it was locked by the antivirus causing the verification process to fail:
    Note the verification status message: An error occurred while reading or writing to a file. 
    Failed to verify file using the Authenticode provider. Verification status: An error occurred while reading or writing to a file. (-2146885629), last error: An error occurred while reading or writing to a file. (2148081667)
Verifying [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature. Failed.
Upgrading DeploymentDll. New library: [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] Failed.
RPC: Upgrading deployment service dll... Failed.
ERR |Failed to verify [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll] signature
>>  |--tr:Failed to upgrade VeeamDeploymentDll. Path [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll].
>>  |An exception was thrown from thread [####].

  • The following is an example from an environment where the VeeamDeploymentDll.dll within C:\Veeam\Backup\Upload\ was already present and locked by the antivirus before Veeam Backup & Replication attempted to upload it, and Veeam Backup & Replication cannot upload and overwrite the existing VeeamDeploymentDll.dll because one already exists and is locked: 
    RPC: Creating file C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll
  FC: Creating file. Path: [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll]. Desired access: [1073741824]. Creation mode: [0].
  FC: Creating file. Path: [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll]. Desired access: [1073741824]. Creation mode: [0]. Failed.
RPC: Creating file C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll Failed.
ERR |The process cannot access the file because it is being used by another process.
>>  |--tr:Error code: 0x00000020
>>  |--tr:FC: Failed to create file. File path: [C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll]. Desired access: [1073741824]. Creation disposition: [0].
>>  |An exception was thrown from thread [####].
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
↧

How to Reset Password for Veeam Backup for Salesforce

October 20, 2024, 5:00 pm
$
0
0

How to Reset Password for Veeam Backup for Salesforce

KB ID: 4253
Product: Veeam Backup for Salesforce | 1.0 | 2.0 | 2.1 | 3.0
Published: 2022-10-27
Last Modified: 2024-10-21

Purpose

This article documents how to reset the password used to access Veeam Backup for Salesforce. 

Solution

  1. Connect to the Veeam Backup for Salesforce machine via SSH
  2. Run the script for changing the password:
    • For Veeam Backup for Salesforce version 3: 
      sudo /opt/vbsf/reset_password.sh
    • For Veeam Backup for Salesforce version 1, 2, and 2.1: 
      sudo /opt/vbsf/vbsf-backend/reset_password.sh
  3. Provide the new password and confirm the password.

  4. Once completed, the password has been changed.
    Using the new password, you can now log in to the Veeam Backup for Salesforce UI.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

After Upgrade Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization Appliance Is Listed as Unavailable

October 22, 2024, 5:00 pm
$
0
0

After Upgrade Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization Appliance Is Listed as Unavailable

KB ID: 4681
Product: Veeam Backup & Replication | 12.2
Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization | 5
Published: 2024-10-23
Last Modified: 2024-10-23

Challenge

After the upgrade of Veeam Backup & Replication to version 12.2 and subsequent upgrade of Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization to version 5, the Appliance is listed as Unavailable in the Veeam Backup & Replication Console. When this occurs, related jobs fail to start, and attempts to update Proxy parameters fail with the following errors:

Failed to edit the backup appliance settings: The backup appliance did not start within the expected time period

Failed to synchronize jobs: Communication channel has been forcibly closed

Cause

When the Veeam Appliance attempts to connect to Veeam Backup & Replication, it attempts to connect to each of the addresses sequentially. If multiple addresses are present on the Veeam Backup Server and are unreachable, the cumulative time spent trying and failing to connect to each address may exceed the service startup timeout.

Solution

To resolve this issue:

  1. Download Fix_806875_6fa7aa9684.zip.
  2. Close all Veeam Backup & Replication Consoles.
  3. Uninstall oVirt KVM Plug-In for Veeam Backup & Replication.
  4. Install KVMPlugin_12.5.0.410.exe from the downloaded hotfix.
  5. Upgrade the Proxy Appliance(s).
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

How to Detect and Remove Separated Disks During Veeam Agent for Linux Restore

October 22, 2024, 5:00 pm
$
0
0

How to Detect and Remove Separated Disks During Veeam Agent for Linux Restore

KB ID: 4680
Product: Veeam Agent for Linux | 6.0 | 6.1 | 6.2
Published: 2024-10-23
Last Modified: 2024-10-30

Purpose

This article documents how to detect and clean up the restored disks of a Linux machine that used LVM, was backed up with Veeam Agent for Linux, and restored to a hypervisor VM or cloud computing platform.

This issue is documented in the following Veeam Agent for Linux user guide restore sections:

Issue Summary

The following text is from the aforementioned Veeam Agent for Linux User Guide restore sections.

If the disk you want to restore contains an LVM volume group, consider the following:

  • Since LVM volume group is a logical entity that spans across the physical disks, Veeam Agent treats the original disk and the LVM volume group as separate entities. Therefore, Veeam Backup & Replication will restore the original disk and the LVM volume group as 2 separate disks. This way, all data, including the data within the LVM volume group, is accurately restored.
  • Restoring the original disk and the LVM volume groups as 2 separate disks requires an increased amount of storage space. For example, you restore a machine with 2 disks, and a separate LVM volume group is configured on each of these disks. In this case, Veeam Backup & Replication will restore 4 disks. The restored disks will consume the storage space equal to the size of the 2 original disks and the 2 LVM volume groups from these disks.
Intended Final Outcome
This article will guide you in identifying which disks are no longer actively used by the Volume Group (VG) and how to remove them from the virtual machine (VM) and storage system. The end result will be a Volume Group (VG) utilizing only a single physical disk, even though the original Linux machine had multiple physical disks pooled into the VG.

Challenge

The current design results in the restored machine having more disks than the original machine had, leading to increased storage consumption and potentially extra cost.

Example Scenario

Initial Linux Machine Configuration Overview
  • Disk sda: uses default partitioning for OS filesystems.
  • Disks sdb and sdc: partitioned as sdb1 and sdc1 and used as Physical Volumes to create the pool for a Volume Group named vg00.
  • Volume Group vg00: contains 2 logical volumes:
    • lv_big: formatted as ext4
    • lv_small: formatted as xfs
Commands to Review Disk Configuration

The following commands can be used to review the machine's disk configuration:

lsblk -fs
blkid
vgs; lvs
df -hT
Command Output Examples From Scenario Machine
root@linux-agent-host:~# lsblk -fs
NAME          FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda1          ext4        1.0            06522eee-d6c7-48ec-bb21-bacd2aa2806b     10.9G    21% /
`-sda                                                                                          
sda2                                                                                           
`-sda                                                                                          
sda5          swap        1              415c86a1-4b25-4d64-8250-9d3084a95623                  [SWAP]
`-sda                                                                                          
sr0                                                                                            
vg00-lv_big   ext4        1.0            2a038489-a343-413c-88cd-7b458a9c43d7      9.2G     0% /big
|-sdb1        LVM2_member LVM2 001       82fr31-JedF-sQlA-ZIha-S27n-xXq6-EetU5C                
| `-sdb                                                                                        
`-sdc1        LVM2_member LVM2 001       xnQ2CB-vufG-21Sq-h6yZ-mURX-jnV9-zIB3ce                
  `-sdc                                                                                        
vg00-lv_small xfs                        1f7b4748-9380-4e09-8a0c-dc9dbf51b878      2.9G     2% /small
`-sdb1        LVM2_member LVM2 001       82fr31-JedF-sQlA-ZIha-S27n-xXq6-EetU5C                
  `-sdb                                                                                        
root@linux-agent-host:~# blkid 
/dev/mapper/vg00-lv_small: UUID="1f7b4748-9380-4e09-8a0c-dc9dbf51b878" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdb1: UUID="82fr31-JedF-sQlA-ZIha-S27n-xXq6-EetU5C" TYPE="LVM2_member" PARTUUID="9ca89108-01"
/dev/mapper/vg00-lv_big: UUID="2a038489-a343-413c-88cd-7b458a9c43d7" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc1: UUID="xnQ2CB-vufG-21Sq-h6yZ-mURX-jnV9-zIB3ce" TYPE="LVM2_member" PARTUUID="8e1b0552-01"
/dev/sda5: UUID="415c86a1-4b25-4d64-8250-9d3084a95623" TYPE="swap" PARTUUID="38687d75-05"
/dev/sda1: UUID="06522eee-d6c7-48ec-bb21-bacd2aa2806b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="38687d75-01"
root@linux-agent-host:~# vgs; lvs
  VG   #PV #LV #SN Attr   VSize  VFree   
  vg00   2   2   0 wz--n- 13.99g 1016.00m
  LV       VG   Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  lv_big   vg00 -wi-ao---- 10.00g                                                    
  lv_small vg00 -wi-ao----  3.00g                                                    
root@linux-agent-host:~# df -hT
Filesystem                Type      Size  Used Avail Use% Mounted on
udev                      devtmpfs  2.9G     0  2.9G   0% /dev
tmpfs                     tmpfs     593M  736K  592M   1% /run
/dev/sda1                 ext4       15G  3.1G   11G  22% /
tmpfs                     tmpfs     2.9G  4.0K  2.9G   1% /dev/shm
tmpfs                     tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                     tmpfs     593M     0  593M   0% /run/user/0
/dev/mapper/vg00-lv_big   ext4      9.8G  5.4G  3.9G  59% /big
/dev/mapper/vg00-lv_small xfs       3.0G  2.1G  955M  69% /small

Solution

Post-Restore Configuration Review

After performing the restore, review the restored VM's disk layout. You'll notice that in addition to the original disks, there will be new a disk for each of the VGs (Volume Groups) that is equal in size to the combination of all LVs (Logical Volumes) in each VG from the original Linux machine.
 

Example Restored VM Configuration
  • Disk sda is restored as is.
  • Disks sdb and sdc are restored, and their partitions (sdb1 and sdc1) are present.
  • Disk sdd is new, and is sized to match the combined size of all LVs within the VG.
    • The logical volumes lv_big and lv_small are mounted as expected.
restored VM disks example
Example VM's Restored Disk Configuration
For this example, the machine was restored to VMware vSphere, and see can see in the VM's settings the disks:
vSphere VM Disks

Note: If there are multiple disks with the same size, use the command lsscsi to identify the SCSI nodes assigned to each disk and then correlate those to the VM configuration.

Example:

# lsscsi 
[0:0:0:0]    disk    VMware   Virtual disk     2.0   /dev/sda 
[0:0:1:0]    disk    VMware   Virtual disk     2.0   /dev/sdb 
[0:0:2:0]    disk    VMware   Virtual disk     2.0   /dev/sdc
[0:0:3:0]    disk    VMware   Virtual disk     2.0   /dev/sdd

Based on this, we can see that /dev/sdd is SCSI node 0:3, which correlates to the following VM disk:

SCSI node collelation

Detaching Unused Disks and Repairing LVM VG

After powering on the restored VM, attempting to execute any LVM commands results in warnings like:

WARNING: PV /dev/sdd in VG vg00 is using an old PV header, modify the VG to update.
WARNING: Device /dev/sdd has size of 27265024 sectors which is smaller than corresponding PV size of 13959692288 sectors. Was device resized?
WARNING: One or more devices used as PVs in VG vg00 have changed sizes.

 

Part 1:  Detach the Unused Disks

These steps continue with the prior example of working with a Linux machine restored to a vSphere VM. You will need to adapt these steps when restoring to other hypervisors or cloud computing platforms.

After identifying which VM disks represent the unused disks, in the ongoing example, sbd and sdc, perform the following to detach them from the VM:

  1. Power of the restored VM.
  2. Edit the VM in a vSphere Client.
  3. Remove disks, but don't delete the disks.
detech disks
  1. Save the new settings of the VM and start it.
  2. Review the disk configuration and ensure that the filesystems are mounted properly using:
lsblk
df -hT
Example
Note that sdd is now listed as sdb.
post disk removal configuration exampe

Part 2: Clean Up LVM Errors

WARNING: PV /dev/sdb in VG vg00 is using an old PV header, modify the VG to update
  1. To resolve this first warning, excute the following command replacing the vg00 with the actual VG name.
vgck --updatemetadata vg00
WARNING: Device /dev/sdb has size of 27265024 sectors which is smaller than corresponding PV size of 13959692288 sectors. Was device resized?
WARNING: One or more devices used as PVs in VG vg00 have changed sizes.

These warnings occur because the VG (vg00) was initially made from multiple PVs, and now only a single PV is present.

  1. Fix this by running the following command, specifying the correct device and sector count from the warning:
pvresize /dev/sdb –setphysicalvolumesize 27265024s
  1. The system should be rebooted to ensure all changes are committed.
  2. After reboot, ensure all volumes are mounted as expected.
  3. If everything is now functioning correctly with no further LVM warnings, the spare disks that were disconnected can be removed from the storage.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
Search

Installing package Transport Error: Error 1935.An error occurred during the installation of assembly component

October 24, 2024, 5:00 pm
$
0
0

Installing package Transport Error: Error 1935.An error occurred during the installation of assembly component

KB ID: 1689
Product: Veeam Backup & Replication | 12 | 12.1 | 12.2
Published: 2012-11-12
Last Modified: 2024-10-25

Challenge

When Veeam Backup & Replication attempts to install the Veeam Transport package (VeeamTransport.msiC:\Program Files\Veeam\Backup and Replication\Backup\Packages\VeeamTransport.msi) the package fails to install, and the following errors may be displayed in the UI:

Installing package Transport Error: Error 1935.An error occurred during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}. HRESULT: 0x80070543. 

Failed to install or upgrade packages: Error 1935.An error occurred during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}. HRESULT: 0x80070543. 

Failed to save Microsoft Windows server: Error 1935.An error occurred during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}. HRESULT: 0x80070543. 

Infrastructure item save failed Error: Error 1935.An error occurred during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}. HRESULT: 0x80070543. 

These errors may occur when:

Add win error
system error
Manual install error
Protection Group deployment

Cause

The MsiInstaller fails to process the VeeamTransport installer.

At this time, there are two leading causes:

  • Distributed COM (DCOM) Configuration Issue
  • AntiVirus/Security Software Interference

Solution

  1. Ensure that no Antivirus or Security software is interfering with the installation.

    The VeeamTransport.msi file will be uploaded to the following folder in the remote Windows machine:
    C:\Windows\Veeam\Backup\Upload\
  2. Check that the account being used to communicate with the remote machine is a member of the Local Administrators group on the affected machine.
  3. Check the DCOM communication properties:
    1. Run: dcomcnfg.exe
    2. In the console tree, expand Component Services and then expand Computers.
    3. Right-click on My Computer and click Properties.
    4. Within the My Computer Properties window, switch to the Default Properties tab.
    5. Confirm settings are system default:
      • Default Authentication Level — Connect.
      • Default Impersonation Level — Identify
    6. Save settings and close DCOM Manager.
default dcom settings
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
↧

Veeam Agent for Linux - veeamsnap and blksnap Extended Linux Distribution Support

November 5, 2024, 4:00 pm
$
0
0

Veeam Agent for Linux - veeamsnap and blksnap Extended Linux Distribution Support

KB ID: 2804
Product: Veeam Agent for Linux | 6.0 | 6.1 | 6.2
Published: 2018-11-29
Last Modified: 2024-11-08

This article documents the compatibility of the veeamsnap and blksnap kernel modules with Linux distributions that are not listed within the System Requirements for Veeam Agent for Linux. Veeamsnap and blksnap kernel modules are used both for Volume-Level Backup (except for btrfs volumes) and File-level Backup (except for Snapshot-Less File-Level Backup).

For more information, review the following:
Veeam Agent for Linux - Considerations and Limitations

Veeam Agent for Linux 6.2

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 9.3 and higher are supported.
9.0-9.4 5.14.0-427.31.1.el9_4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.16.1.el8_10 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.119.1.el7 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.4
(RHCK)		 5.14.0-427.31.1.el9_4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.4
(UEK7)		 5.15.0-209.161.7.2 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.16.1.el8_10 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-209.161.7.2 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.334.6.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.334.6.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-1902.300.11 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-112.16.4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.73 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP4 5.14.21-150400.24.100 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP3 5.3.18-150300.59.106.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.225 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.6 6.4.0-150600.23.17 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.5 5.14.21-150500.55.73 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.4 5.14.21-150400.24.100 6.2.0.101

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Leap 15.3 5.3.18-150300.59.106 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.10.5-1 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Ubuntu
22.04 5.15.0-119 6.2.0.101

6.2.0.101 initially shipped with Backup & Replication 12.2.0.334

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.1.2

New Distribution Support

Veeam Agent for Linux 6.1.2 introduces support for the following Linux Distributions:

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported. / Rocky / AlmaOnly Rocky/Alma 9.3 and higher are supported.
9.0-9.4 5.14.0-427.42.1.el9_4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.22.1.el8_10 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.119.1.el7 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.4
(RHCK)		 5.14.0-427.31.1.el9_4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.4
(UEK7)		 5.15.0-209.161.7.2 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10
(RHCK)		 4.18.0-553.16.1.el8_10 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.10
(UEK7)		 5.15.0-209.161.7.2 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.10
(UEK6)		 5.4.17-2136.334.6.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.334.6.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-1902.300.11 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-112.16.4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.83 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP4 5.14.21-150400.24.100 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.225 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.5 5.14.21-150500.55.73 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.4 5.14.21-150400.24.100 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.8.9-1 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-119 6.1.2.1781

6.1.2.1781 initially shipped with Backup & Replication 12.1.2.172

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.1

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.3-9.4 5.14.0-427.20.1.el9_4 6.1.0.1498 This kernel is supported using a patch available from Veeam Support.
Please create a support case to request it.

Uses the blksnap kernel module.
9.0-9.3 5.14.0-362.13.1.el9_3 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.10 4.18.0-553.5.1.el8_10 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.118.1.el7 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.4-6.10 2.6.32-754.53.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for the dkms package (a VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.3
(RHCK)		 5.14.0-362.13.1.el9_3 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.3
(UEK7)		 5.15.0-205.149.5.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-513.9.1.el8_9 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.5-8.9
(UEK7)		 5.15.0-205.149.5.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.

Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
8.1-8.9
(UEK6)		 5.4.17-2136.330.7.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.7-7.9
(UEK6)		 5.4.17-2136.330.7.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.5-7.9
(UEK5)		 4.14.35-1902.300.11 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.1-7.9
(UEK4)		 4.1.12-112.16.4 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.8-6.10
(UEK4)		 4.1.12-124.16.4 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.52 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP4 5.14.21-150400.24.100 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.201 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.5 5.14.21-150500.55.52 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.4 5.14.21-150400.24.100 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.7.2-1 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-105 6.1.0.1498

6.1.0.1498 initially shipped with Backup & Replication 12.1.0.2131

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.0.3

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduced the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.3 5.14.0-362.13.1.el9_3 6.0.3.1228

To acquire Veeam Agent for Linux 6.0.3.1228 packages and instructions, please open a support ticket.

 

Uses the blksnap kernel module.
9.0-9.2 5.14.0-284.25.1.el9_2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.9 4.18.0-513.11.1.el8_9 6.0.3.1228

To acquire Veeam Agent for Linux 6.0.3.1228 packages and instructions, please open a support ticket.

 

Uses the blksnap kernel module.
8.0-8.8 4.18.0-477.21.1.el8_8 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.108.1.el7 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.0-6.10 2.6.32-754.50.1.el6 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for a dkms package (VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.2
(RHCK)		 5.14.0-284.25.1.el9_2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.2
(UEK7)		 5.15.0-202.135.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-477.21.1.el8_8 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.7
(UEK6)		 5.4.17-2136.327.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.8
(UEK7)		 5.15.0-202.135.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
7.0-7.9
(UEK6)		 5.4.17-2136.327.2 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.44 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

 

Also available at repository.veeam.com
Recovery media


Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP4 5.14.21-150400.24.100 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718


Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.189 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

 

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.5 5.14.21-150500.55.44 6.0.3.1221

Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

 

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.4 5.14.21-150400.24.100 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.2.10-1 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-92 6.0.3.1221 Veeam Agent for Linux 6.0.3.1221
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230718

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.0.2

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduces the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.0-9.2 5.14.0-284.25.1.el9_2 6.0.2.1173 To acquire Veeam Agent for Linux 6.0.2.1173 packages and instructions, please open a support ticket.

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8 4.18.0-477.21.1.el8_8 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.108.1.el7 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.0-6.10 2.6.32-754.50.1.el6 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Please note that RHEL6 reached "End of life," and therefore EPEL repository has archived version 6 packages. If you are looking for a dkms package (VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.2
(RHCK)		 5.14.0-284.25.1.el9_2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412 .

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.1
(UEK7)		 5.15.0-100.96.32.el9uek 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-477.21.1.el8_8 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.7
(UEK6)		 5.4.17-2136.327.2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.8
(UEK7)		 5.15.0-202.135.2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Note: Building the veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information, refer to KB4394
7.0-7.9
(UEK6)		 5.4.17-2136.327.2 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP4 5.14.21-150400.24.100 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.189 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.4 5.14.21-150400.24.100 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.2.10-1 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on an available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-92 6.0.2.1168 Veeam Agent for Linux 6.0.2.1168
Shipped with Veeam Backup & Replication 12.0.0.1420 P20230412

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

Veeam Agent for Linux 6.0

blksnap kernel module

In addition to the veeamsnap kernel module, Veeam Agent for Linux 6 introduces the blksnap kernel module for use on newer Linux kernels. Both modules are used for the same purpose (snapshot creation).

  • Veeamsnap module is supported up to Linux kernel 5.18
  • The Blksnap module is supported for Linux kernels starting from 5.10

The default installed module is listed in the Details column for each supported distribution and version.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.0-9.1 5.14.0-162.12.1.el9_1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
8.0-8.8 4.18.0-477.21.1.el8_8 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9 3.10.0-1160.108.1.el7 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
6.0-6.10 2.6.32-754.50.1.el6 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check: https://archives.fedoraproject.org/pub/archive/epel/6/

See also: https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.1
(RHCK)		 5.14.0-162.12.1.el9_1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420 .

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
9.0-9.1
(UEK7)		 5.15.0-7.86.6.1.el9uek 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses blksnap kernel module.
8.0-8.8
(RHCK)		 4.18.0-477.21.1.el8_8 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
8.0-8.8
(UEK7)		 5.15.0-202.135.2 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
Note: Building veeamsnap kernel module on Oracle Linux 8 with UEK R7 kernel requires additional steps. For more information refer to KB4394
8.0-8.7
(UEK6)		 5.4.17-2136.327.2 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
7.0-7.9
(UEK6)		 5.4.17-2136.327.2 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
SUSE Linux Enterprise (SLES)
15 SP4 5.14.21-150400.24.100 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on available workaround, refer to KB4183
15 SP3 5.3.18-150300.59.106.1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
15 SP2 5.3.18-24.96.1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP5 4.12.14-122.189 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
12 SP4 4.12.14-95.54.1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the veeamsnap kernel module.
openSUSE
Leap 15.4 5.14.21-150400.24.100 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on available workaround, refer to KB4183
Leap 15.3 5.3.18-150300.59.106 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com
Recovery media

Uses the blksnap kernel module.
Tumbleweed 6.1.12-1 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.

Note: Known issue prevents recovery media patching. For more information on available workaround, refer to KB4183
Ubuntu
22.04 5.15.0-92 6.0.0.1060 Veeam Agent for Linux 6.0.0.1060
Shipped with Veeam Backup & Replication 12.0.0.1420

Also available at repository.veeam.com (Agent, kernel module)
Recovery media

Uses the blksnap kernel module.
Swipe to show more of the table

End of Life Versions

All Veeam Agent for Linux builds listed below have reached End-of-Support.

The information below is retained for historical reference only.

Any customer operating a version listed below is strongly encouraged to upgrade to the latest version.

Veeam Agent for Linux 5.0.2

Intended Audience for this Update

As of March 1, 2024, Veeam Agent for Linux 5.x is no longer supported.

On March 14, 2024, a final update, Cumulative Patch P20240304, was released for Veeam Backup & Replication 11a. This update included a new build of Veeam Agent for Linux. Veeam Backup & Replication 11a, P20240304, is provided as a courtesy to customers who wish to continue using Veeam Backup & Replication 11a for an extended time.

Veeam Agent for Linux 5.0.2.4707 is only available with Veeam Backup & Replication 11a P20240304. The table below has been updated to reflect the compatibility introduced by this new version of Veeam Agent for Linux.

CRITICAL: If you choose to install 11a P20240304, you will not be able to upgrade to version 12.1 until the next minor update, 12.1.2, is available (scheduled to be released in Q2 2024).

We strongly recommend that all customers use actively supported versions of Veeam products.

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
9.0-9.3
 5.14.0-362.24.1.el9_3 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
8.6-8.9 4.18.0-513.18.1.el8_9 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
8.0-8.5 4.18.0-348.20.1.el8_5

5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 Shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.
7.0-7.9 3.10.0-1160.114.2.el7 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.
6.0-6.10 2.6.32-754.50.1.el6 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.


Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check 
https://archives.fedoraproject.org/pub/archive/epel/6/

See also
https://access.redhat.com/discussions/4768501.
Oracle Linux
9.0-9.3
 5.14.0-362.24.1.el9_3
(RHCK)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
5.15.0-204.147.6.2.el9uek
(UEK7)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
8.6-8.9
 4.18.0-513.18.1.el8_9
(RHCK)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
5.15.0-204.147.6.2.el8uek
(UEK7)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
5.4.17-2136.329.3.1.el8uek
(UEK6)		 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
7.0-7.9
 5.4.17-2136.329.3.1.el7uek
(UEK6)		 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

Also available at repository.veeam.com.
Recovery media.
SUSE Linux Enterprise (SLES)
15 SP5 5.14.21-150500.55.52 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15 SP4 5.14.21-150400.24.100 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15 SP3 5.3.18-150300.59.106.1 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
15 SP2 5.3.18-24.96.1 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
12 SP5 4.12.14-122.194 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
openSUSE Leap
15.5 5.14.21-150500.55.52 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15.4 5.14.21-150400.24.100 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
15.3 5.3.18-150300.59.106 5.0.2.4567

Veeam Agent for Linux 5.0.2.4567 shipped with Backup & Replication 11.0.1.1261 P20211211.

 

Also available at repository.veeam.com.
Recovery media.
Ubuntu
22.04 5.15.0-101 5.0.2.4707

Veeam Agent for Linux 5.0.2.4707 shipped with Backup & Replication 11.0.1.1261 P20240304.
Swipe to show more of the table

Veeam Agent for Linux 5.0.1

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
8.0-8.4 4.18.0-305.25.1.el8_4

5.0.1.4493

Veeam Agent for Linux version 5.0.1. Shipped with Backup & Replication 11a GA.
7.0-7.9 3.10.0-1160.76.1.el7 5.0.1.4493

Veeam Agent for Linux version 5.0.1. Shipped with Backup & Replication 11a GA.
6.0-6.10 2.6.32-754.35.1.el6 5.0.1.4493 Veeam Agent for Linux version 5.0.1. Shipped with Backup & Replication 11a GA.

Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check 
https://archives.fedoraproject.org/pub/archive/epel/6/

See also
https://access.redhat.com/discussions/4768501.
Swipe to show more of the table

Veeam Agent for Linux 5.0

Version Maximum Supported Kernel VAL Build Details
Red Hat Enterprise Linux (RHEL) / CentOS*Only CentOS 7.x is supported.
8.4 4.18.0-305.25.1.el8_4

5.0.0.4325

Known issue: deployment via Agent Management fails.

For packages and instructions please open a support ticket.
8.0-8.3 4.18.0-240.22.1.el8_3

5.0.0.4318

Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA.
7.0-7.9 3.10.0-1160.76.1.el7 5.0.0.4325

Known issue: deployment via Agent Management fails. 

For packages and instructions please open a support ticket.
6.0-6.10 2.6.32-754.35.1.el6 5.0.0.4318 Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA.

Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check 
https://archives.fedoraproject.org/pub/archive/epel/6/

See also
https://access.redhat.com/discussions/4768501.
Swipe to show more of the table
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Veeam Data Cloud Release Information and Build Numbers

November 5, 2024, 4:00 pm
$
0
0

Veeam Data Cloud for Microsoft 365 Release Information and Build Numbers

KB ID: 4555
Product: Veeam Data Cloud for Microsoft 365 | 1.0
Published: 2024-03-07
Last Modified: 2024-11-06

This KB article lists all versions of Veeam Data Cloud for Microsoft 365 and their respective release information and build numbers.

For more information Veeam Data Cloud, visit:

Version

Click a row to expand and view release notes.

 Build Number Release Date
Veeam Data Cloud for Microsoft 365 1.6 Releases
Veeam Data Cloud for Microsoft 365 1.6.5 1.6.5 2024-11-05

What's New

  • Express Backup Bulk Restore - Added bulk restore for Express backup policies.
  • Mobile Notifications - Notifications now display message bodies on mobile.
  • Certificate Management - Streamlined multi-tenant management, eliminating duplicate certificates per organisation.
  • IP Blocking Enhancements - Improved IP address blocking to allow tenant switching, direct login after whitelisting, and single IP additions.
  • Chart Update - Updates chart labels to ‘Date’ and ‘Licenses'.

Resolved Issues

  • Various performance and bug fixes.
Veeam Data Cloud for Microsoft 365 1.6.4 1.6.4 2024-10-15

What's New

  • Repository Naming - Users can name repositories for easier selection in backup policies.
  • Restore Multi-select - Multi-select for restore with command/control keys, checkboxes, and ‘select all’.
  • Custom Encryption - Option to add or generate an encryption passphrase.
  • Labelling Update - ‘Backups’ is now ‘Flex Backups’, and ‘Microsoft Backups’ is now ‘Express Backups’.

Resolved Issues

  • Teams Folder Structure - Corrected an issue where the Teams folder structure wasn’t restoring properly in certain cases. 
  • App Registration Authorisation - Fixed a bug causing authorization to fail when adding a second app registration. 
  • Network Restriction - Resolved an error that occurred when adding more than 10 IP ranges to network restrictions.
  • Other minor fixes.
Veeam Data Cloud for Microsoft 365 1.6.3 1.6.3 2024-10-01

What's New

  • Added Dashboard and Report buttons on the navigation panel.
  • Added the ability to schedule reports to be run and emailed on a scheduled basis.

Resolved Issues

  • Improved performance when listing SharePoint sites for backup policy creation.
  • Minor fixes.
Veeam Data Cloud for Microsoft 365 1.6.2 1.6.2 2024-09-13

What's New

  • Express plan type can now select multiple objects to restore at once.
  • Streamlined time selection for Express plan restore points.
  • Updated dashboard widgets to include statistics for all plan types.

Resolved Issues

  • Minor fixes.
Veeam Data Cloud for Microsoft 365 1.6.1 1.6.1 2024-08-28

What's New

  • Streamlined Microsoft Backup Storage integration.
  • UI improvement for Microsoft Backup Storage.
  • Changed user interface language from Backup Jobs to Backup Policies now that VDC includes two different policy types.
  • Improved search to search for part of a word.
  • Added a new report type - Backup Job Summary.

Resolved Issues

  • Minor fixes.
Veeam Data Cloud for Microsoft 365 1.6.0 1.6.0 2024-08-15

What's New

  • Microsoft Backup Storage — We have added integration with Microsoft's first-party backup for Microsoft 365 (Microsoft Backup Storage).
    See this blog post for more information: Microsoft 365 Backup Storage with Veeam Game-Changing Integration.
    Customers can request enablement of this through their usual sales channels.
  • Searching — Added the option to search at the top level for Outlook/Exchange. This includes for self-service users.

Resolved Issues

  • Restores — Fixed an issue where OneDrive is not displaying items on the top level.
  • Other minor fixes
Veeam Data Cloud for Microsoft 365 1.5 Releases
Veeam Data Cloud for Microsoft 365 1.5.9 1.5.9 2024-07-29

What's New

  • UI Performance — Multiple optimizations have been implemented to improve UI performance.
  • Onboarding — Added the option to add an additional app registration to accelerate initial SharePoint onboarding backups.
  • Regionalization — The language selector has been relocated to the "My Profile" settings.

Resolved Issues

  • Restores — Fixed an issue where attempting to browse through file history would only display the previous 100 versions.
  • Other minor fixes
Veeam Data Cloud for Microsoft 365 1.5.8 1.5.8 2024-07-10

What's New

  • Backup Jobs — For customers who have backup job management, when creating backup jobs and specifying which items to include, there is now the option to specifically exclude certain items.
  • Dashboard —  The Storage Use widget now excludes group owners to give a clearer view of storage usage by users.
  • Activity Log —  The activity log previously included restores but not downloads; it has been extended to include items that have been downloaded. Note this information also remains available in the detailed user activity log.
  • UI — Clicking on the version number in the UI will now open this changelog article.
  • UI — An info pop-up has been added when creating restore sessions to give users better feedback when the time-consuming operation of opening a session occurs.

Resolved Issues

  • Restores —  Fixed an issue where OneDrive would stall on the Loading spinner.
  • Activity Log — Fixed an issue where the status was not updated as Failed if Download to local fails for OneDrive.
  • Backup Jobs — Attempting to create or edit a backup job caused the error "Unexpected Error" when that job included an M365 User's Upload file.
  • Restores — Fixed an issue where the Email list in the right pane does not show when there is only mail in the folder.
  • Fixed Backups — Fixed an issue where user was not always being added into the backup job.
  • Restores - Performance improvements to email searching/filtering.
  • Other minor fixes
Veeam Data Cloud for Microsoft 365 1.5.7 1.5.7 2024-06-21

What's New

  • Backup Jobs — We have added an option to exclude all personal sites from SharePoint backups to make it easier to manage them. We have also made exclusion the default for new backups.
  • Large Restores — We have made significant improvements to our restore in background functionality to make it faster and more resilient.

Resolved Issues

  • Mailbox Search — Fixed issue where search occasionally timed out.
  • Teams — "Team with Guest" Channel folder got error 500.
  • Backup Jobs — Unable to add teams to excluded items.
  • Self Service — Fixed an issue where a user could only see their primary mailbox or their in-place archive mailbox but not both.
  • AD group — Members assigned via AD group are not added to the VDC users list.
  • Advanced Search — The highlighted row is displayed incorrectly when the user selects an item in the Search result popup
Veeam Data Cloud for Microsoft 365 1.5.6 1.5.6 2024-06-13

What's New

  • Public Folder Support — You can now back up public folders and easily restore them when needed.
    For existing customers, you will need to reauthorize VDC to add additional required permissions.
  • Improved Content Searching/Filtering — Customers can now search for and filter content using special characters in the VDC platform.
  • Restore Activity Notifications — Administrators now have the option to receive notifications via email when any restore or preview item activities occur.
  • Improved Outlook search speed — The search speed in Outlook has been improved to return results as they become available, reducing the waiting time for users.

Resolved Issues

    • Backup Jobs
    • Fixed issue where users were unable to edit data types in an existing Groups backup.
    • Fixed issue where select all was not working while adding a user for a backup job.
  • OneDive Restores
    • Resolved the error "Cannot read properties of null (reading 'id')" that occurred when a user clicked on the top item of the treeview.
Veeam Data Cloud for Microsoft 365 1.5.5 1.5.5 2024-05-23

What's New

  • OneDrive Restores — We have made the following improvements to OneDrive restores:
    • When restoring a document from OneDrive, provide the ability to restore to a different user's OneDrive account.
    • Added versioning selection when choosing a file to restore.
  • RBAC — We have separated Outlook and OneDrive into different managed RBAC roles.

Resolved Issues

  • Performance — General performance improvements.
  • Restores — Fixed the following issues:
    • Significantly improved speed of filtering/searching within a folder.
    • Restore to original location was hanging at status "Running."
    • Restore SharePoint of a selected previous version with "Local computer (download)" attached the latest version.
    • Compare with production button is showing "Network Error."
  • RBAC — Fixed issue where a privileged user cannot see user management.
  • Backups — Backup progress bar intermittently not updating for customers.
Veeam Data Cloud for Microsoft 365 1.5.4 1.5.4 2024-05-10

What's New

  • Reporting — We have added a "Monthly backup report" to our reporting options. This will generate a CSV report with a summary and line-by-line details of each backup run.
  • Backups — More information about the target repository when editing a backup job will be displayed for customers with multiple repositories.

Resolved Issues

  • Outlook — Compare with production button returns "Network Error."
  • Backups — M365 Groups [Add Group] page can get stuck in a loop.
  • Restore [All] — In some situations, users cannot select the option to "Include items deleted by user."
  • RBAC — SharePoint Sites not Synchronization issues in roles view.
Veeam Data Cloud for Microsoft 365 1.5.3 1.5.3 2024-04-22

What's New

  • Dashboard — The dashboard has been updated to improve user experience and clarity of information presentation.
  • Performance — General performance improvements.

Resolved Issues

  • Teams — Teams objects unable to be selected after manually configuring the Teams section.
  • Teams — Inabailbity to filter and retrieve results for large organizations.
Veeam Data Cloud for Microsoft 365 1.5.2 1.5.2 2024-03-28

What's New

  • Restores — When restoring a SharePoint site to a new alias, the destination field now accepts special characters like ":" and "/", allowing for more flexible restore locations.
  • Backups — The backup jobs progress bar has been optimized to load faster, improving the user experience.
  • Performance — Improved performance when browsing restores.

Resolved Issues

  • Outlook: Cannot filter on special characters.
Veeam Data Cloud for Microsoft 365 1.5.1 1.5.1 2024-03-14

What's New

  • Restores — Added Teams filtering options.
  • Backup logs — Add a "Running" option in the backup logs filter.

Resolved Issues

  • Backup Job is set to disabled after editing the backup job's name.
  • The status of backup jobs in a running state does not auto-refresh.
  • OneDrive doesn't allow customers to load more OneDrive items.
  • Issue with Download Options in SharePoint Folder.
  • An error occurs when selecting a Sharepoint site in Role Setting.
  • The pagination of backup users is not functioning for some fixed customers.
  • Performance-related improvements.
  • Other minor features and bug fixes.
Veeam Data Cloud for Microsoft 365 1.5.0 1.5.0 2024-02-28
What's New
  • UI — Change logo and branding
    • Updated the product name and logo to "Veeam Data Cloud for Microsoft 365".
    • Changed logos on sign-in screens, menu logos, and the favicon to reflect the new branding.
    • Updated the color scheme on the login page and dashboard graphs.
  • Role-Based Access Control (RBAC)  — Veeam Data Cloud for Microsoft 365 users can now assign admin user roles using groups in Active Directory. Two new tabs have been added to the Settings -> Users page to add and manage Veeam Data Cloud for Microsoft 365 users and assign roles by AD group.
  • Restore — Added the capability to compare Outlook data within a backup to production during the restore process.
  • Admin Portal — You can now disable email previews for your entire organization if you do not want to allow your users to access this feature. Contact your reseller or Veeam Data Cloud support to disable it.
  • SharePoint — Added the ability to view previous versions of documents when selecting a file or folder for restore in SharePoint.
  • Settings — Customer admins can now enable self-service for their organization, allowing all users from that company domain to restore their own OneDrive and Outlook content.

Resolved Issues

  • Fixed issues identified in penetration test results, including updating API endpoints and implementing more granular permissions.
  • Other minor features and bug fixes.
Swipe to show more of the table

Related Articles
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Release Information for Proxmox Virtual Environment Plug-In for Veeam Backup & Replication v12.1.1.1024

November 5, 2024, 4:00 pm
$
0
0

Release Information for Proxmox Virtual Environment Plug-In for Veeam Backup & Replication v12.1.1.1024

KB ID: 4686
Product: Veeam Backup & Replication | 12.2
Published: 2024-11-06
Last Modified: 2024-11-06

Requirements

This update to the Proxmox Virtual Environment Plug-In for Veeam Backup & Replication requires:

  • Veeam Backup & Replication build 12.2.0.334
    You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.
  • Proxmox Virtual Environment Plug-In for Veeam Backup & Replication build 12.1.0.313
    You can check the current build number within the installed applications list.

 

After the updated Proxmox Virtual Environment Plug-In is installed, the Plug-In build number will be 12.1.1.1024.

Resolved Issues

  • Backup jobs and other activities fail to establish a network connection to the Veeam Backup Server when the Veeam Backup Server has disconnected network interfaces.
  • In certain circumstances, when processing a virtual disk with an intense I/O load, the backup job may read and store a later state of some disk blocks instead of their state at the time of the snapshot. This issue applies only to jobs using the Hot Add backup mode.
  • The loss of the most recent incremental restore point may cause the next run of the backup job to generate an incomplete incremental restore point.

Known Issues

  • After a failed incremental backup run, the next run of that backup job will perform a full read of the entire protected disk to identify changed blocks reliably. This will not affect incremental backup size as only those identified changed blocks will be stored in the incremental restore point.
  • During the first run of each backup job after applying this update, each job will automatically perform a full disk read to identify the actual state of all disk blocks reliably. This will not affect incremental backup size; only differences will be stored in the incremental restore point.

Download Information

Download Updated Plug-In

Filename: PVEPlugin_12.1.1.1024.zip

MD5: 14F48FEE70B604F8A1C6E1DF9893E479
SHA1: 1061276E9C13F3C6550B71F19BB682E57F186D80

Deployment Information 

  1. Download the updated Proxmox Virtual Environment Plug-In package using the link in this article.
  2. Copy PVEPlugin_12.1.1.1024.zip to the Veeam Backup Server.
  3. Close any open Veeam Backup & Replication Consoles, and ensure no veeam.backup.shell.exe processes are running.
  4. Unzip PVEPlugin_12.1.1.1024.zip and run PVEPlugin_12.1.1.1024.exe.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

How to Use Existing Veeam Backup & Replication PostgreSQL instance for Veeam Backup for Microsoft 365 Deployment

November 6, 2024, 4:00 pm
$
0
0

How to Use Existing Veeam Backup & Replication PostgreSQL instance for Veeam Backup for Microsoft 365 Deployment

KB ID: 4638
Product: Veeam Backup for Microsoft 365 | 8
Published: 2024-09-03
Last Modified: 2024-11-07
Article Applicability

This article documents issues that occur when installing Veeam Backup for Microsoft 365 v8 or higher on the same server as an existing Veeam Backup & Replication v12 or higher deployment that is using the included local PostgreSQL instance.

The errors described may also occur in other scenarios, as they are generic connection errors. This article is strictly relevant to the scenario described.

Challenge

When attempting to install Veeam Backup for Microsoft 365 on a machine where Veeam Backup & Replication is already installed, and that deployment of Veeam Backup & Replication is using the included local PostgreSQL Instance, the Veeam Backup for Microsoft 365 installer fails with the error:

Unable to proceed due to the following error:
Unable to connect to the specified server. Error: Failed to connect to: <IP>:<port>.
When postgres.conf contains listen_addresses = 'localhost'

Other less common but possible errors are:

  • Unable to proceed due to the following error:
Unable to connect to the specified server. Error: 28000: no pg_hba.conf entry
for host "<IP>", user " postgres", database "postgres",
no encryption.

  • Unable to proceed due to the following error:
Unable to access PostgreSQL server using SQL authentication. SQL
authentication is required by backup proxies. Please enable it on the
PostgreSQL server.

Cause

This issue occurs because the Veeam Backup for Microsoft 365 installer has detected the existing local PostgreSQL instance. However, the configuration settings applied to PostgreSQL by Veeam Backup & Replication are incompatible with those required by Veeam Backup for Microsoft 365.

Configuration conflicts:

  • Veeam Backup & Replication configures PostgreSQL to listen only for local connections.
    Veeam Backup for Microsoft 365 requires that PostgreSQL listen for remote connections from its proxies.
  • Veeam Backup & Replication does not configure PostgreSQL to allow remote access.
    Veeam Backup for Microsoft 365 requires that PostgreSQL allow remote connections so that its Proxies can access the configuration database using a dedicated read-only account using password-based authentication.

Solution

Windows-based PostgreSQL Deployment

The instructions provided below are specifically for a Windows-based PostgreSQL deployment. This is because the article explains how to configure the PostgreSQL instance deployed by Veeam Backup & Replication (VBR), enabling Veeam Backup for Microsoft 365 to connect to it.

If you are planning to deploy Veeam Backup for Microsoft 365 using a remote dedicated PostgreSQL instance (which may or may not also be used by VBR), that configuration is beyond the scope of this article. For such a setup, you should create a dedicated superuser account and use it during the deployment of Veeam Backup for Microsoft 365. After deployment, consult the Veeam Backup for Microsoft 365 User Guide for details on Adjusting PostgreSQL Instance Configuration.

To enable Veeam Backup for Microsoft 365 and Veeam Backup & Replication to share an existing local PostgreSQL instance, you must modify several PostgreSQL configuration files as described below.

Part 1: Stop Veeam Backup & Replication Tasks and Services

  1. Ensure all tasks within Veeam Backup & Replication are stopped.
  2. Stop all Veeam services:
Get-Service Veeam* | Stop-Service -Force

Part 2: Modify PostgreSQL Configuration Files

The default location for all PostgreSQL Configuration Files is:
C:\Program Files\PostgreSQL\15\data\

  1. Edit postgresql.conf and find the setting 'listen_address' and update the line to be:
listen_addresses = '*'
  1. Edit pg_hba.conf and add the following to the bottom of the file:
# non-localhost host with user 'postgres' and SSPI
host    all             postgres        0.0.0.0/0               sspi map=veeam
host    all				postgres		::/0                    sspi map=veeam
# non-localhost host with user 'all' and password
host    all             all             0.0.0.0/0               scram-sha-256
host    all             all             ::/0                    scram-sha-256
  1. Edit pg_ident.conf and ensure that at the bottom of the file there are:
    Note: Usernames are entered into this conf file in UPN format.
    1. An entry for:
      veeam   "SYSTEM@NT AUTHORITY"   postgres
      Note: The SYSTEM@NT AUTHORITY account naming is OS-locale dependent. If using an OS with a language other than English, check and use the appropriate value. Mouseover here for PowerShell Script to check.(New-Object System.Security.Principal.SecurityIdentifier("S-1-5-18")).Translate([System.Security.Principal.NTAccount]).Value
    2. An entry for the user account you will use to install Veeam Backup for Microsoft 365.
      • Domain Account Example: 
        veeam   user@DOMAIN   postgres
      • Local Account Example: 
        veeam   user@HOSTNAME   postgres
  2. Restart the PostgreSQL Service to apply the changes.
Restart-Service -Name "postgresql*"

Part 3: Start Veeam Backup & Replication Service and Reattempt Veeam Backup for Microsoft 365 Install

  1. Start the Veeam services:
Get-Service Veeam* | Start-Service
  1. Reattempt the Veeam Backup for Microsoft 365 install.

More Information

Related articles:

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
↧

NATS Server Configuration Advice for Use With Veeam Backup for Microsoft 365

November 6, 2024, 4:00 pm
$
0
0

NATS Server Configuration Advice for Use With Veeam Backup for Microsoft 365

KB ID: 4675
Product: Veeam Backup for Microsoft 365 | 8
Published: 2024-11-07
Last Modified: 2024-11-08

Purpose

This article provides advice for optimizing NATS Server configuration when used in conjunction with Veeam Backup for Microsoft 365.

Solution

When Veeam Backup for Microsoft 365 is deployed using the included NATS Server, the system variable 'GOMEMLIMIT' is set to 30% of the total system memory available at the time of installation.

Customers who choose to use an existing NATS Server are advised to closely monitor memory usage and consider instituting a similar memory limit to prevent Veeam Backup for Microsoft 365 from causing NATS Server to consume excessive memory.

More Information

Additional NATS Server Configuration Considerations

  • Since the GOMEMLIMIT value is a fixed value, any changes to the amount of system memory should be followed by an adjustment to the GOMEMLIMIT value. For the NATS Server deployed by the Veeam Backup for Microsoft 365 installer, this value is stored as a environmental variable"C:\Windows\system32\rundll32.exe" sysdm.cpl,EditEnvironmentVariables and should consistently be set to 30% of the total system memory.

    Note: For deployments on virtual machines with dynamic memory allocation (e.g., Hyper-V), the GOMEMLIMIT value may be set considerably lower than expected if the allocated memory was small during the initial deployment of Veeam Backup for Microsoft 365.
gomemlimit
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Veeam Backup for Salesforce Built-In Updater Not Finding Updates

November 7, 2024, 4:00 pm
$
0
0

Veeam Backup for Salesforce Built-In Updater Not Finding Updates

KB ID: 4684
Product: Veeam Backup for Salesforce | 1.0
Published: 2024-11-08
Last Modified: 2024-11-08

Challenge

In Veeam Backup for Salesforce v1, the Updater displays no updates available despite the fact that newer versions are available.

Cause

The updater fails to identify new updates as being available because of an expired or incorrect GPG key used to verify package integrity. Without the proper GPG key, the package manager cannot authenticate or apply updates correctly, resulting in errors during update attempts.

When this occurs, the Veeam-updater.log will contain the following error:

Service.CheckUpdates: Cannot find any updates for VBSF repository (<guid>): packageManagerErrorFailedGetList veeam-repo exit code: 1, timeout exceeded: false, output: , errors: Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature

Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature

Solution

Use the following scripts to switch to the correct GPG key:

For RPM-Based Systems (ex:RHEL)

  1. Download the script:
curl -O https://repository.veeam.com/yum/el/8/x86_64/update-gpg-vbsf-v1.sh
  1. Run the script:
sudo bash update-gpg-vbsf-v1.sh
  1. Check for updates once again via Veeam Backup for Salesforce Updater.

For DEB-Based Systems (ex:Ubuntu)

  1. Download the script:
curl -O https://repository.veeam.com/apt/stable/amd64/update-gpg-vbsf-v1.sh
  1. Run the script:
sudo bash update-gpg-vbsf-v1.sh
  1. Check for updates once again via Veeam Backup for Salesforce Updater.

More Information

Newer versions of Veeam Backup for Salesforce handle updating the repo GPG keys more effectively, which is why this issue eclusively affects Veeam Backup for Salesforce version 1.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
Search

Release Information for Proxmox Virtual Environment Plug-In v12.1.1.1024

November 5, 2024, 4:00 pm
$
0
0

Release Information for Proxmox Virtual Environment Plug-In v12.1.1.1024

KB ID: 4686
Product: Veeam Backup & Replication | 12.2
Published: 2024-11-06
Last Modified: 2024-11-12

Requirements

This update to the Proxmox Virtual Environment Plug-In for Veeam Backup & Replication requires:

  • Veeam Backup & Replication build 12.2.0.334
    You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.
  • Proxmox Virtual Environment Plug-In for Veeam Backup & Replication build 12.1.0.313
    You can check the current build number within the installed applications list.

 

After the updated Proxmox Virtual Environment Plug-In is installed, the Plug-In build number will be 12.1.1.1024.

Resolved Issues

  • Backup jobs and other activities fail to establish a network connection to the Veeam Backup Server when the Veeam Backup Server has disconnected network interfaces.
  • In certain circumstances, when processing a virtual disk with an intense I/O load, the backup job may read and store a later state of some disk blocks instead of their state at the time of the snapshot. This issue applies only to jobs using the Hot Add backup mode.
  • The loss of the most recent incremental restore point may cause the next run of the backup job to generate an incomplete incremental restore point.

Known Issues

  • After a failed incremental backup run, the next run of that backup job will perform a full read of the entire protected disk to identify changed blocks reliably. This will not affect incremental backup size as only those identified changed blocks will be stored in the incremental restore point.
  • During the first run of each backup job after applying this update, each job will automatically perform a full disk read to identify the actual state of all disk blocks reliably. This will not affect incremental backup size; only differences will be stored in the incremental restore point.

Download Information

Download Updated Plug-In

Filename: PVEPlugin_12.1.1.1024.zip

MD5: 14F48FEE70B604F8A1C6E1DF9893E479
SHA1: 1061276E9C13F3C6550B71F19BB682E57F186D80

Deployment Information 

  1. Download the updated Proxmox Virtual Environment Plug-In package using the link in this article.
  2. Copy PVEPlugin_12.1.1.1024.zip to the Veeam Backup Server.
  3. Close any open Veeam Backup & Replication Consoles, and ensure no veeam.backup.shell.exe processes are running.
  4. Unzip PVEPlugin_12.1.1.1024.zip and run PVEPlugin_12.1.1.1024.exe.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Optimizing and Maintaining SQL Server Instance Hosting Veeam Service Provider Console Configuration Database

October 10, 2024, 5:00 pm
$
0
0

Optimizing and Maintaining SQL Server Instance Hosting Veeam Service Provider Console Configuration Database

KB ID: 4670
Product: Veeam Service Provider Console | 8.0 | 8.1
Published: 2024-10-11
Last Modified: 2024-11-14

Purpose

This article was produced in coordination with the Veeam R&D team to provide Service Providers with a comprehensive list of the most common performance improvements and maintenance actions relating to the underlying Microsoft SQL Server instance that hosts the Veeam Service Provider Console configuration database.

The information, advice, and scripts provided in this article are provided as a courtesy. Assistance with implementing the configuration advice provided in this document is outside the scope of Veeam Support.
If you have feedback regarding the content of this article, please use the Article Feedback form.

Solution

This guide has been broken down into expandable sections below.
System Requirements and Sizing Guidelines
Check if your MS SQL Server follows the VSPC Sizing Guidelines recommendations:
SQL Server Instance Memory Configuration Options

Memory utilization for the SQL Server Database Engine is bounded by a pair of configuration settings, min server memory (MB) and max server memory (MB). Over time and under normal circumstances, SQL Server will attempt to claim memory up to the limit set by max server memory (MB).

Use max server memory (MB) to guarantee the OS and other applications don't experience detrimental memory pressure from SQL Server. Before you set the max server memory (MB) configuration, monitor the overall memory consumption of the server hosting the SQL Server instance during regular operation to determine memory availability and requirements.

Use SQL Server Management Studio to set server memory options:

  1. In Object Explorer, right-click a server and select Properties.
Properties
  1. Select the Memory page of the Server Properties window. The current values of Minimum server memory and Maximum server memory are displayed.
Memory Settings
  1. In Server memory options, enter desired numbers for Minimum server memory and Maximum server memory. For recommendations, see min server memory (MB) and max server memory (MB).
SQL Server Standard and Express Edition CPU Limitations

When utilizing SQL Server Standard Edition or Express Edition, be mindful of the compute capacity limitations when configuring the CPU socket and core configuration of the Virtual Machine (VM) hosting Microsoft SQL Server.

Microsoft SQL Server - Compute capacity limits by edition

  • SQL Server Standard Edition is "Limited to lesser of 4 sockets or 24 cores"
  • SQL Server Express Edition is "Limited to lesser of 1 socket or 4 cores"

Example:

If you intend to assign a total of 24 vCPUs to a VM and configure it as 24 sockets with 1 core each, SQL Server Standard edition would be able to utilize at most 4 cores. If the configuration were 4 sockets with 6 cores each, then SQL Server Standard Edition would be able to access all 24 cores.

Managing SQL Server Data and Log Files

To manage data and log files, ensure the following:

  • Data and log files are on separate drives from each other and from all other files. The drive containing the data should contain only data (no logs), and the drive containing the log files should contain only log files (no data).
  • Using SSD for better I/O performance.
  • Auto-growth is correctly configured (10% by default).
  • Instant file initialization is configured.
  • Auto-shrink is not enabled and shrink is not part of any maintenance plans.

    If auto-shrink is enabled, disable it by using the following command:
ALTER DATABASE VSPC SET AUTO_SHRINK OFF;
Monitoring Physical Disks Performance

Performance Monitor is a built-in Windows Tool for monitoring all aspects of Windows and hosted applications such as SQL Server. A Data Collector Set is used to organize and schedule performance counter data as a single collection to be analyzed later.

To create a Data Collector Set for your physical disks:

  1. Launch the Performance Monitor (perfmon).
Run
perfmon
  1. In the Performance Monitor navigation pane, expand Data Collector Sets.
  2. Right-click User Defined, point to New, and click Data Collector Set.
New Data Collector
  1. Enter a name for the Data Collector Set and select Create manually, then click Next.
Set name and select manually create
  1. Select Create data logs, check the Performance counter box, and click Next.
Create logs and performance counters.
  1.  Click Add to open the Add Counters dialog box.
Add Counters
  1. Find and click the category entry PhysicalDisk, the Instances of selected object section will update.
Select Physical disk
  1. Double click <All instance> to add the PhsysicalDisk counters to the Added counters list, then click OK.
Add counters to list
  1. Click Finish to exit and save the current configuration.
Finish and save
  1. Start the created data collector set by right-clicking on it and selecting Start.
Start data set
  1. After a while, stop the data collection by clicking the Stop the Data Collector Set button.
Stop data collection
Results will be shown in the Reports folder in the navigation pane. It is important for the Avg. Disk Queue Length counter to have a value less than 1. Otherwise, it could mean that the system has poor disk performance.
Review
Reviewing SQL Server Logs

There are several areas where SQL Server logs information about processes that are occurring as well as errors that occur.  The most used is probably the SQL Server Error Log.  This error log provides startup information, integrity check information, backup information, and other information, as well as any SQL Server errors that occur.

To get to the MS SQL Server Logs, follow these steps:

  1. In Object Explorer, expand the Management node and the SQL Server Logs node.
  2. Right-click on the Current log entry and select View SQL Server Log.
View Logs
  1. In the Log File Viewer, you can analyze and export logs.
Monitoring VSPC Database Staging Tables

Almost all of the data collected by VSPC goes through Staging tables. It is important that these tables maintain as near to zero records as possible. If the number of records continues to increase, it could indicate that there is a performance issue.

To check how many records Staging tables have:

  1. In Object Explorer, right-click the VSPC database and go to the Reports -> Standard Reports, select the Disk Usage by Top Tables report.
disk usage table
  1. Check how many records VeeamBP.Staging and VeeamOD.Staging tables have.
staging tables
If either table has more than 5 million records, it could indicate performance issues. In such a situation, wait a couple of hours a generate the Disk Usage by Top Tables report again, and if the number of records hasn’t gone down – contact Veeam Support.
Database Shrinking Considerations

To view the current amount of free (unallocated) space in the database, see Display Data and Log Space Information for a Database.

Shrink Considerations and Limitations

Consider the following information when you plan to shrink a database:

  • A shrink operation is most effective after an operation that creates a large amount of unused storage space, such as a large DELETE statement, truncate table, or a drop table operation.
  • Most databases require some free space to be available for regular day-to-day operations. If you shrink a database repeatedly and notice that the database size grows again, this indicates that the free space is required for regular operations. In these cases, repeatedly shrinking the database is a wasted operation. Repeatedly shrinking the database causes the SQL instance to trigger autogrow events to grow the database file(s), which hinders performance.
  • A shrink operation doesn't preserve the fragmentation state of indexes in the database and generally increases fragmentation to a degree. This is another reason not to shrink the database repeatedly.
  • Unless you have a specific requirement, do not set the AUTO_SHRINK database option to ON.

Shrink operations in progress can block other queries on the database and can be blocked by queries already in progress.

Database Shrinking Documentation
Fragmentation Impact of Shrinking Database

Data that is moved to shrink a file can be scattered to any available location in the file. This causes index fragmentation and can slow the performance of queries that search a range of the index. To eliminate the fragmentation, consider rebuilding the indexes on the file after shrinking.

Rebuilding Table Indexes

Index and data pages can experience internal fragmentation. Index and table structures can experience logical scan and extent scan fragmentation. Periodically check index fragmentation of the VSPC database. The most sensitive tables for index fragmentation are:

  • VeeamBP. ObjectEntityPropertyValue
  • VeeamOD. ObjectEntityPropertyValue
  • VeeamBP.ObjectEntity
  • VeeamOD.ObjectEntity

Check Index Fragmentation using SQL Server Management Studio:

  1. Right-click the VSPC database and choose Reports -> Standard Reports.
  2. Select the Index Physical Statistics report.

You’ll see table names, indexes, and operation recommendations in that report. Follow the recommendations and rebuild\reorganize indexes.

Rebuild vs Reorganize Indexes

Please note that rebuilding indexes is a heavy task that can take a lot of time. Additionally, online indexing can only be done with the Enterprise Edition of Microsoft SQL Server. In other editions of the SQL Server, only offline indexing is available, meaning tables having their indexes rebuilt will be locked during the rebuild operation. Reorganizing the index, on the other hand, is less heavy an operation and can be done online with all editions. Generally speaking, reorganizing indexes is preferable to rebuilding when possible.

How to Rebuild Indexes (Offline)
  1. In Object Explorer, select the plus sign next to the VSPC database.
  2.  Expand the Tables folder.
  3.  Select the plus sign to expand the table whose indexes you want to rebuild.
  4.  Expand the Indexes folder.
  5.  Right-click the index that you want to rebuild and select Rebuild.
  6. In the Rebuild Indexes dialog box, verify that the correct index is in the Indexes to be rebuilt list and click OK.
How to Rebuild Indexes (Online)

For information about rebuilding Indexes (Online) with SQL Server Enterprise Edition, please review Microsoft documentation:
SQL Server - Perform index operations online - Use SQL Server Management Studio

How to Reorganize Indexes
  1. In Object Explorer, select the plus sign next to the VSPC database.
  2.  Expand the Tables folder.
  3.  Select the plus sign to expand the table whose indexes you want to reorganize.
  4.  Expand the Indexes folder.
  5. Right-click the index that you want to reorganize and select Reorganize.
  6. In the Reorganize Indexes dialog box, verify that the correct index is in the Indexes to be reorganized list and click OK.
Updating Table and Index Statistics
Ensure that the statistics describing the distribution of data values in a table or index are accurate and up-to-date. Updated statistics provide the query optimizer with the best possible information for generating query plans. Statistics are updated when they are created or modified, and they are also periodically updated by SQL Server unless the administrator has disabled automatic statistics updates. Auto Update Statistics doesn’t work for filtered indexes; those indexes need to be updated manually.
Check if Auto Update Statistics is ON
  1. Right-click the VSPC database and choose Properties.
  2. In the navigation menu on the left, select Options.
  3. Check if Auto Update Statistics has the True value and set it to the True if it’s not.
  4. Click OK to close the Database Properties.
Auto Update Statistics
Check VSPC Database Statistics Relevancy

You can check how irrelative the statistics are in your VSPC DB using the following query:

set transaction isolation level read uncommitted;

select quotename( sh.[name] ) + N'.' + quotename( t.[name] ) as [object_name]
     , s.stats_id
     , quotename( s.[name] ) as stat_name
     , s.auto_created
     , s.user_created
     , s.no_recompute
     , replace( sc.stat_columns, N'] [', N'], [' ) as stat_columns
     , cast( sp.last_updated as datetime2( 3 ) ) as last_updated
     , sp.[rows]
     , sp.rows_sampled
     , sp.steps
     , sp.modification_counter
     , ltrim( format( cast( sp.modification_counter as decimal( 20, 2 ) ) / cast( sp.[rows] as decimal( 20, 2 ) ), N'# ##0.00 %' ) ) as irrelevance
     , s.filter_definition    
  from sys.schemas sh
    inner join
      sys.tables t on t.[schema_id] = sh.[schema_id]
    inner join
      sys.stats s on s.[object_id] = t.[object_id]
    outer apply
      ( select quotename( c.[name] ) as [data()]
          from sys.stats_columns sc 
            inner join
              sys.columns c on c.[object_id] = sc.[object_id] and c.column_id = sc.column_id
          where sc.[object_id] = s.[object_id] 
            and sc.stats_id = s.stats_id
          order by sc.stats_column_id
          for xml path( '' ) ) sc( stat_columns )
    outer apply
      sys.dm_db_stats_properties( s.[object_id], s.stats_id ) as sp
  order by [object_name], s.stats_id;
go
How to Update a Statistics Object (using SQL Server Management Studio)
  1. In Object Explorer, select the plus sign next to the VSPC database.
  2.  Expand the Tables folder.
  3.  Select the plus sign to expand the table whose statistic you want to update.
  4.  Expand the Statistics folder.
  5. Right-click the statistics object you wish to update and select Properties.
  6. In the Statistics Properties dialog box, select the check box labeled "Update statistics for these columns" and click OK.
Update Stats

How to Update a Single Statistics Object using Transact-SQL

  1. Connect to the SQL Server instance.
  2. Click New Query.
  3. Copy and paste the following example into the query window and click Execute.
    Note: The statistic in this example can be changed to any statistic you'd like to update.
-- Use the name of your VSPC database instead of the VSPC_DB_NAME
USE VSPC_DB_NAME;
GO
-- The following example updates the statistics for the INDX_ObjectEntityPropertyValue_IsDeleted_DateTime index of the VeeamBP.ObjectEntityPropertyValue table. 
UPDATE STATISTICS VeeamBP.ObjectEntityPropertyValue
INDX_ObjectEntityPropertyValue_IsDeleted_DateTime;
GO

How to Update all Statistics for a Specific Table using Transact-SQL

  1. Connect to the SQL Server instance.
  2. Click New Query.
  3. Copy and paste the following example into the query window and click Execute.
    Note: The table in this example can be changed to any table whose statistics you'd like to update.
-- Use the name of your VSPC database instead of the VSPC_DB_NAME
USE VSPC_DB_NAME;   
GO  
-- The following example updates the statistics for all indexes on the VeeamBP.ObjectEntityPropertyValue table.
UPDATE STATISTICS VeeamBP.ObjectEntityPropertyValue;   
GO

How to Update all Statistics in a Specific Database using Transact-SQL

  1. Connect to the SQL Server instance.
  2. Click New Query.
  3. Copy and paste the following example into the query window and click Execute.
    Note: The statistic in this example can be changed to any statistic you'd like to update.
-- Use the name of your VSPC database instead of the VSPC_DB_NAME
USE VSPC_DB_NAME;   
GO  
-- The following example updates the statistics for all tables in the database.  
EXEC sp_updatestats;
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
↧

How to Migrate Veeam Backup for Microsoft 365 Configuration Database

November 13, 2024, 4:00 pm
$
0
0

How to Migrate Veeam Backup for Microsoft 365 Configuration Database

KB ID: 4676
Product: Veeam Backup for Microsoft 365 | 8
Published: 2024-11-14
Last Modified: 2024-11-14

Purpose

This article documents the procedure for migrating the Configuration Database of Veeam Backup for Microsoft 365 from one PostgreSQL instance to another.

Solution

Prepare for Migration

  1. Ensure all jobs and restore tasks are completed, stopped, and disabled.
  2. On the primary Veeam Backup for Microsoft 365 server (aka controller) and all associated Proxies, stop the Veeam Backup for Microsoft 365 services:
    • Veeam Backup for Microsoft 365 Server

      Veeam Backup for Microsoft 365 Service 
      Get-Service Veeam.Archiver.Proxy | Stop-Service
      Veeam Backup for Microsoft 365 Proxy Service 
      Get-Service Veeam.Archiver.Service | Stop-Service
    • Veeam Backup for Microsoft 365 Windows Proxy

      Veeam Backup for Microsoft 365 Proxy Service 
      Get-Service Veeam.Archiver.Proxy | Stop-Service
    • Veeam Backup for Microsoft 365 Linux Proxy

      Veeam.Archiver.Proxy 
      systemctl stop Veeam.Archiver.Proxy
  3. Review the Veeam Backup for Microsoft 365 configuration to identify the current database connection information.
    1. On the machine where Veeam Backup for Microsoft 365 is installed open the following file in a text editor:
      C:\ProgramData\Veeam\Backup365\Config.xml
    2. Look for the node named ControllerPostgres. On that line will be the current database connection information.
      • Example 1: Using VB365 Installer-deployed PostgreSQL Instance 
        <ControllerPostgres ControllerConnectionString="host=vb365srv;port=5432;database=VeeamBackup365;username=postgres;maxpoolsize=100;connectionidlelifetime=10" />
        In this example, we can see that the PostgreSQL server is named vb365srv, the configuration database is named VeeamBackup365, and we can tell that SSPI authentication is being used because there is no password= parameter.
      • Example 2: Using Remote Dedicated PostgreSQL Instance 
        <ControllerPostgres ControllerConnectionString="host=pgsqlsrv;port=5432;database=VeeamBackup365;username=veeam365svc;password=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAnyPJ1ttvw06By6Ldd2NKOkEHjdXl7buhzxlW4MjXMBBqLZQGWWjXHgyM%3D;maxpoolsize=100;connectionidlelifetime=10;PasswordEncrypted=True" />
        In this example, we can see that the PostgreSQL server is named pgsqlsrv, the configuration database is named VeeamBackup365, the user is named veeam365svc, and native password-based authentication is in use because there is a passsword= parameter configured.
pgAdmin Required

The migration procedure documented in this article requires pgAdmin.

To deploy pgAdmin, either download it from the pgAdmin website or run the postgresql installer, which includes pgAdmin, from the Redistr folder on the Veeam Backup for Microsoft 365 installer ISO.

Export from Source

Using pgAdmin, connect to the PostgreSQL server where the Veeam Backup for Microsoft 365 configuration database is located and export the following (the sections that follow explain in detail how to export these):

  • SQL Script files to recreate:
    • Group Role: proxy_role_<config_db_name>
      Example Export Filename: proxyrole.sql
    • User: proxy_dbuser_<config_db_name>
      Example Export Filename: proxyuser.sql
  • Database Backup Files
    • Configuration Database: VeeamBackup365
      Example Export Filename: VeeamBackup365.backup
    • Cache Database(s): cache_<guid>
      Example Export Filename: cache_<guid>.backup

Note: When connecting to the default included PostgreSQL instance, the default authentication method for the postgres user is SSPI, and you may see the error "SSPI authentication failed for user." If this occurs, review KB4542. If prompted to specify a password after connecting, click OK with the password field empty.

Export the Proxy Group Role

  1. Under Login/Group Roles, identify the Group Role named proxy_role_veeambackup365
  2. Right-click on that Group Role and select CREATE script.
Backup Role
  1. A query tool window will appear with an SQL query to recreate the Group Role.
  2. In the Query Tool Toolbar, click the Save icon and save the SQL script as proxyrole.sql for use later in the migration.
Save SQL Role

Export the Proxy User

  1. Under Login/Group Roles, identify the User named proxy_role_veeambackup365
  2. Right-click on that Group Role and select CREATE script.
Export Proxy User
  1. A query tool window will appear with an SQL query to recreate the Proxy user.
  2. In the Query Tool Toolbar, click the Save icon and save the SQL script as proxyuser.sql for use later in the migration.
Save SQL Role

Export Configuration Database

  1. Expand the Databases node.
  2. Right-click on the Veeam Backup for Microsoft 365 Configuration Database, by default, named VeeamBackup365.
  3. Select Backup...
Backup DB
  1. In the Backup dialog window that appears, provide a path where the database backup will be created, ensure that the format is set to Custom, and then click Backup.
Backup Database Form

Export Cache Databases

  1. If any database(s) are present named cache_<guid>, back them up.
    Tip: If you right-click on the cache database and select Properties, you can copy the database name to the clipboard so that you can save the .backup file with the database name to make it easier to recreate and restore the database with the correct name during the Import portion of the migration.
cache db backup
Tip
If Veeam Backup for Microsoft 365 was using the included local PostgreSQL deployment, and that PostgreSQL instance will not be used by any other software, stop and disable the postgresql-x64-15 service. This will prevent the software from mistakenly connecting to the old PostgreSQL instance if a configuration file is not correctly updated during the migration finalization stage.

Import to Destination

Notes:
  • The destination PostgreSQL instance can be hosted on either Windows or Linux.
  • When migrating the Configuration Database to a remote PostgreSQL instance, the authentication method Veeam Backup for Microsoft 365 uses to connect to the PostgreSQL instance must be switched to native password-based authentication.
  • Due to the variability of possible PostgreSQL configurations, this guide cannot account for all possible custom configurations that may occur when a PostgreSQL instance is already in use by other third-party software. This guide instead aims to document the configuration changes required to modify a default new deployment of PostgreSQL to allow it to host the Veeam Backup for Microsoft 365 Configuration and Cache databases.
  • Ensure that the destination PostgreSQL instance is running a version supported by Veeam Backup for Microsoft 365.

Copy Generated Files to Destination

  1. Copy the generated .sql and .backup files to the new PostgreSQL server.

Recreate the Proxy Group Role

  1. Using pgAdmin, connect to the destination PostgreSQL instance.
  2. Right-click on any database and select Query Tool.
Open Query Tool
  1. In the Query Tool Toolbar, click the Open button.
Open Query File
  1. Open the exported Proxy Group Role SQL script, proxyrole.sql.
  2. With the query now open in the Query Tool, click Execute script in the Query Tool Toolbar to recreate the Proxy Group Role.
recreate proxy group role

Recreate the Proxy User

  1. With the Query Tool still open from adding the Proxy Group Role, click the Open button again.
Open Query File
  1. Open the exported Proxy User SQL script,  proxyuser.sql.
  2. Click Execute to recreate the Proxy User.
recreate proxy user

Recreate and Restore the Configuration Database

  1. Right-click on the Databases node, and highlight Create>, then click Database...
create new database
  1. Name the database after the Configuration Database that was backed up.
create database name
  1. Right-click on the new database and select Restore...
Restore Database
  1. Select the .backup file created from the Configuration Database and click Restore.
start restore

Recreate and Restore Cache Databases

If any databases named cache_<guid> were backed up from the original PostgreSQL instance:

  1. Create new cache_<guid> database(s) with their original names.
  2. Use the .backup file from each cache_ database to restore the cache database(s).

Configure PostgreSQL Authentication

When the Veeam Backup for Microsoft 365 Configuration Database is hosted on a remote PostgreSQL Instance, you must configure authentication within the PostgreSQL configuration to allow Veeam Backup for Microsoft 365 to access the restored Configuration Database.

Create a PostgreSQL User for Veeam Backup for Microsoft 365
  1. Using pgAdmin, connect to the new PostgreSQL instance.
  2. Open the Query Tool.
    Right-click on a database and select Query Tool.
  3. Paste the following query (don't execute without updating it).
CREATE ROLE "vb365svc" WITH
	LOGIN
	SUPERUSER
	CREATEDB
	CREATEROLE
	INHERIT
	REPLICATION
	BYPASSRLS
	CONNECTION LIMIT -1
	PASSWORD 'pa55word';
  1. Update the role name (vb365svc) and password (pa55word) values in the query and Execute it.

    Tip: Remember which role name and password you specified, as you'll need that when reconfiguring Veeam Backup for Microsoft 365.

    Note: The password must not contain the following characters:
    • @
    • <
    • >
    • '
    • "

Update PostgreSQL Configuration Files to Allow Authentication

  1. Open pg_hba.conf in a text editor.
    • Windows default location: C:\Program Files\PostgreSQL\15\data\pg_hba.conf
    • Linux conf file location will depend on the distro and the method used to install PostgreSQL.
  2. Add the following lines to the bottom of the ph_hba.conf file:
# Allow remote access using Password-based authentication.
host    all    all         0.0.0.0/0   scram-sha-256
host    all    all         ::/0        scram-sha-256
  1. Save the pg_hba.conf file.
  2. Restart the PostgreSQL service.

Reconfigure Veeam Backup for Microsoft 365 and Proxies

In this section you'll update the PostgreSQL connection settings on the Veeam Backup for Microsoft 365 machine and any associated Proxies.

Configuration Formatting
All parameters within the discussed configuration files (Config.xml and Proxy.xml) are separated by a semicolon ( ; ) symbol. Ensure that the format of the xml file is preserved and that parameters are correctly separated using that semicolon. Any malformation in the configuration file may cause the service to fail to start or load the settings.

Update Connection Settings on Veeam Backup for Microsoft 365 Machine

  1. On the machine where Veeam Backup for Microsoft 365 is installed, navigate to:
    C:\ProgramData\Veeam\Backup365\
  2. Make a copy of Config.xml and Proxy.xml, just in case changes need to be reverted or a misconfiguration occurs.
Update Config.xml
  1. Open Config.xml in a text editor.
  2. On the line starting with <ControllerPostgres, review and update each parameter as needed:
    1. host=  —  Hostname of the new PostgreSQL machine.
    2. port=  —  Port to connect to the PostgreSQL instance.
    3. database=  —  Configuration Database name. (This should not have changed if you followed the steps in this guide.)
    4. username=  —  Set the username= parameter to use the new user role you created in the previous section.
    5. password= — This value should be configured as follows:
      For more information on updating the password used by Veeam Backup for Microsoft 365 to connect to PostgreSQL, review KB4669.
      • If the password= parameter is not present:
        1. Add ;password=<password> with the password in plaintext after the username parameter.
          Note: Once the service is started, the plaintext password in the file will be replaced with an encrypted value.
          Example: 
          <ControllerPostgres ControllerConnectionString="host=pgsql;port=5432;database=VeeamBackup365;username=veeam365svc;password=pa55word;maxpoolsize=100;connectionidlelifetime=10" />
      • If the ;password= parameter is present:
        1. Replace the encrypted password value with the new password in plaintext.
          Note: Once the service is started, the plaintext password in the file will be replaced with an encrypted value.
        2. Remove the ;PasswordEncrypted=True parameter from the end of the same line.
  3. On the line starting with <RemoteProxyDeploymentSettings, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
  4. Save the updated Config.xml
Update Proxy.xml
  1. Open Proxy.xml in a text editor.
  2. On the line starting with <ProxyPostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
  3. On any line(s) starting with <PersistentCachePostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct.
  4. Save the updated Proxy.xml

Update Connection Settings on the Proxies

  1. On each Veeam Backup for Microsoft 365 Proxy, navigate to:
    • Windows: C:\ProgramData\Veeam\Backup365\
    • Linux: /opt/veeamvboproxy/
  2. Make a copy of Proxy.xml, just in case changes need to be reverted or a misconfiguration occurs.
Update Proxy.xml
  1. Open Proxy.xml in a text editor.
  2. On the line starting with <ProxyPostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
  3. On any line(s) starting with <PersistentCachePostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct.
  4. Save the updated Proxy.xml

Finalize Migration

  1. On the primary Veeam Backup for Microsoft 365 server (aka controller) and all associated Proxies, start the Veeam Backup for Microsoft 365 services:
    • Veeam Backup for Microsoft 365 Server 
      Get-Service Veeam.Archiver.Proxy | Start-Service
Get-Service Veeam.Archiver.Service | Start-Service
    • Veeam Backup for Microsoft 365 Windows Proxy 
      Get-Service Veeam.Archiver.Proxy | Start-Service
    • Veeam Backup for Microsoft 365 Linux Proxy 
      systemctl start Veeam.Archiver.Proxy

More Information

Should any issues occur during the migration, please create a Veeam Support case. To help expedite the investigation, please include a zip of the contents of C:\ProgramData\Veeam\Backup365\Logs\.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

How to Migrate Veeam Backup for Microsoft 365 Configuration and Cache Databases

November 13, 2024, 4:00 pm
$
0
0

How to Migrate Veeam Backup for Microsoft 365 Configuration and Cache Databases

KB ID: 4676
Product: Veeam Backup for Microsoft 365 | 8
Published: 2024-11-14
Last Modified: 2024-11-18

Purpose

This article documents the procedure for migrating the Configuration and Cache Databases of Veeam Backup for Microsoft 365 from one PostgreSQL instance to another.

Solution

Prepare for Migration

  1. Ensure all jobs and restore tasks are completed, stopped, and disabled.
  2. On the primary Veeam Backup for Microsoft 365 server (aka controller) and all associated Proxies, stop the Veeam Backup for Microsoft 365 services:
    • Veeam Backup for Microsoft 365 Server

      Veeam Backup for Microsoft 365 Proxy Service 
      Get-Service Veeam.Archiver.Proxy | Stop-Service
      Veeam Backup for Microsoft 365 Service 
      Get-Service Veeam.Archiver.Service | Stop-Service
    • Veeam Backup for Microsoft 365 Windows Proxy

      Veeam Backup for Microsoft 365 Proxy Service 
      Get-Service Veeam.Archiver.Proxy | Stop-Service
    • Veeam Backup for Microsoft 365 Linux Proxy

      Veeam.Archiver.Proxy 
      systemctl stop Veeam.Archiver.Proxy
  3. Review the Veeam Backup for Microsoft 365 configuration to identify the current database connection information.
    1. On the machine where Veeam Backup for Microsoft 365 is installed open the following file in a text editor:
      C:\ProgramData\Veeam\Backup365\Config.xml
    2. Look for the node named ControllerPostgres. On that line will be the current database connection information.
      • Example 1: Using VB365 Installer-deployed PostgreSQL Instance 
        <ControllerPostgres ControllerConnectionString="host=vb365srv;port=5432;database=VeeamBackup365;username=postgres;maxpoolsize=100;connectionidlelifetime=10" />
        In this example, we can see that the PostgreSQL server is named vb365srv, the configuration database is named VeeamBackup365, and we can tell that SSPI authentication is being used because there is no password= parameter.
      • Example 2: Using Remote Dedicated PostgreSQL Instance 
        <ControllerPostgres ControllerConnectionString="host=pgsqlsrv;port=5432;database=VeeamBackup365;username=veeam365svc;password=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAnyPJ1ttvw06By6Ldd2NKOkEHjdXl7buhzxlW4MjXMBBqLZQGWWjXHgyM%3D;maxpoolsize=100;connectionidlelifetime=10;PasswordEncrypted=True" />
        In this example, we can see that the PostgreSQL server is named pgsqlsrv, the configuration database is named VeeamBackup365, the user is named veeam365svc, and native password-based authentication is in use because there is a passsword= parameter configured.
pgAdmin Required

The migration procedure documented in this article requires pgAdmin.

To deploy pgAdmin, either download it from the pgAdmin website or run the postgresql installer, which includes pgAdmin, from the Redistr folder on the Veeam Backup for Microsoft 365 installer ISO.

Export from Source

Using pgAdmin, connect to the PostgreSQL server where the Veeam Backup for Microsoft 365 configuration database is located and export the following (the sections that follow explain in detail how to export these):

  • SQL Script files to recreate:
    • Group Role: proxy_role_<config_db_name>
      Example Export Filename: proxyrole.sql
    • User: proxy_dbuser_<config_db_name>
      Example Export Filename: proxyuser.sql
  • Database Backup Files
    • Configuration Database: VeeamBackup365
      Example Export Filename: VeeamBackup365.backup
    • Cache Database(s): cache_<guid>
      Example Export Filename: cache_<guid>.backup

Note: When connecting to the default included PostgreSQL instance, the default authentication method for the postgres user is SSPI, and you may see the error "SSPI authentication failed for user." If this occurs, review KB4542. If prompted to specify a password after connecting, click OK with the password field empty.

Export the Proxy Group Role

  1. Under Login/Group Roles, identify the Group Role named proxy_role_veeambackup365
  2. Right-click on that Group Role and select CREATE script.
Backup Role
  1. A query tool window will appear with an SQL query to recreate the Group Role.
  2. In the Query Tool Toolbar, click the Save icon and save the SQL script as proxyrole.sql for use later in the migration.
Save SQL Role

Export the Proxy User

  1. Under Login/Group Roles, identify the User named proxy_role_veeambackup365
  2. Right-click on that Group Role and select CREATE script.
Export Proxy User
  1. A query tool window will appear with an SQL query to recreate the Proxy user.
  2. In the Query Tool Toolbar, click the Save icon and save the SQL script as proxyuser.sql for use later in the migration.
Save SQL Role

Export Configuration Database

  1. Expand the Databases node.
  2. Right-click on the Veeam Backup for Microsoft 365 Configuration Database, by default, named VeeamBackup365.
  3. Select Backup...
Backup DB
  1. In the Backup dialog window that appears, provide a path where the database backup will be created, ensure that the format is set to Custom, and then click Backup.
Backup Database Form

Export Cache Databases

  1. If any database(s) are present named cache_<guid>, back them up.
    Tip: If you right-click on the cache database and select Properties, you can copy the database name to the clipboard so that you can save the .backup file with the database name to make it easier to recreate and restore the database with the correct name during the Import portion of the migration.
cache db backup
Tip
If Veeam Backup for Microsoft 365 was using the included local PostgreSQL deployment, and that PostgreSQL instance will not be used by any other software, stop and disable the postgresql-x64-15 service. This will prevent the software from mistakenly connecting to the old PostgreSQL instance if a configuration file is not correctly updated during the migration finalization stage.

Import to Destination

Notes:
  • The destination PostgreSQL instance can be hosted on either Windows or Linux.
  • When migrating the Configuration Database to a remote PostgreSQL instance, the authentication method Veeam Backup for Microsoft 365 uses to connect to the PostgreSQL instance must be switched to native password-based authentication.
  • Due to the variability of possible PostgreSQL configurations, this guide cannot account for all possible custom configurations that may occur when a PostgreSQL instance is already in use by other third-party software. This guide instead aims to document the configuration changes required to modify a default new deployment of PostgreSQL to allow it to host the Veeam Backup for Microsoft 365 Configuration and Cache databases.
  • Ensure that the destination PostgreSQL instance is running a version supported by Veeam Backup for Microsoft 365.

Copy Generated Files to Destination

  1. Copy the generated .sql and .backup files to the new PostgreSQL server.

Recreate the Proxy Group Role

  1. Using pgAdmin, connect to the destination PostgreSQL instance.
  2. Right-click on any database and select Query Tool.
Open Query Tool
  1. In the Query Tool Toolbar, click the Open button.
Open Query File
  1. Open the exported Proxy Group Role SQL script, proxyrole.sql.
  2. With the query now open in the Query Tool, click Execute script in the Query Tool Toolbar to recreate the Proxy Group Role.
recreate proxy group role

Recreate the Proxy User

  1. With the Query Tool still open from adding the Proxy Group Role, click the Open button again.
Open Query File
  1. Open the exported Proxy User SQL script,  proxyuser.sql.
  2. Click Execute to recreate the Proxy User.
recreate proxy user

Recreate and Restore the Configuration Database

  1. Right-click on the Databases node, and highlight Create>, then click Database...
create new database
  1. Name the database after the Configuration Database that was backed up.
create database name
  1. Right-click on the new database and select Restore...
Restore Database
  1. Select the .backup file created from the Configuration Database and click Restore.
start restore

Recreate and Restore Cache Databases

If any databases named cache_<guid> were backed up from the original PostgreSQL instance:

  1. Create new cache_<guid> database(s) with their original names.
  2. Use the .backup file from each cache_ database to restore the cache database(s).

Configure PostgreSQL Authentication

When the Veeam Backup for Microsoft 365 Configuration Database is hosted on a remote PostgreSQL Instance, you must configure authentication within the PostgreSQL configuration to allow Veeam Backup for Microsoft 365 to access the restored Configuration Database.

Create a PostgreSQL User for Veeam Backup for Microsoft 365
  1. Using pgAdmin, connect to the new PostgreSQL instance.
  2. Open the Query Tool.
    Right-click on a database and select Query Tool.
  3. Paste the following query (don't execute without updating it).
CREATE ROLE "vb365svc" WITH
	LOGIN
	SUPERUSER
	CREATEDB
	CREATEROLE
	INHERIT
	REPLICATION
	BYPASSRLS
	CONNECTION LIMIT -1
	PASSWORD 'pa55word';
  1. Update the role name (vb365svc) and password (pa55word) values in the query and Execute it.

    Tip: Remember which role name and password you specified, as you'll need that when reconfiguring Veeam Backup for Microsoft 365.

    Note: The password must not contain the following characters:
    • @
    • <
    • >
    • '
    • "

Update PostgreSQL Configuration Files to Allow Authentication

  1. Open pg_hba.conf in a text editor.
    • Windows default location: C:\Program Files\PostgreSQL\15\data\pg_hba.conf
    • Linux conf file location will depend on the distro and the method used to install PostgreSQL.
  2. Add the following lines to the bottom of the ph_hba.conf file:
# Allow remote access using Password-based authentication.
host    all    all         0.0.0.0/0   scram-sha-256
host    all    all         ::/0        scram-sha-256
  1. Save the pg_hba.conf file.
  2. Restart the PostgreSQL service.

Reconfigure Veeam Backup for Microsoft 365 and Proxies

In this section you'll update the PostgreSQL connection settings on the Veeam Backup for Microsoft 365 machine and any associated Proxies.

Configuration Formatting
All parameters within the discussed configuration files (Config.xml and Proxy.xml) are separated by a semicolon ( ; ) symbol. Ensure that the format of the xml file is preserved and that parameters are correctly separated using that semicolon. Any malformation in the configuration file may cause the service to fail to start or load the settings.

Update Connection Settings on Veeam Backup for Microsoft 365 Machine

  1. On the machine where Veeam Backup for Microsoft 365 is installed, navigate to:
    C:\ProgramData\Veeam\Backup365\
  2. Make a copy of Config.xml and Proxy.xml, just in case changes need to be reverted or a misconfiguration occurs.
Update Config.xml
  1. Open Config.xml in a text editor.
  2. On the line starting with <ControllerPostgres, review and update each parameter as needed:
    1. host=  —  Hostname of the new PostgreSQL machine.
    2. port=  —  Port to connect to the PostgreSQL instance.
    3. database=  —  Configuration Database name. (This should not have changed if you followed the steps in this guide.)
    4. username=  —  Set the username= parameter to use the new user role you created in the previous section.
    5. password= — This value should be configured as follows:
      For more information on updating the password used by Veeam Backup for Microsoft 365 to connect to PostgreSQL, review KB4669.
      • If the password= parameter is not present:
        1. Add ;password=<password> with the password in plaintext after the username parameter.
          Note: Once the service is started, the plaintext password in the file will be replaced with an encrypted value.
          Example: 
          <ControllerPostgres ControllerConnectionString="host=pgsql;port=5432;database=VeeamBackup365;username=veeam365svc;password=pa55word;maxpoolsize=100;connectionidlelifetime=10" />
      • If the ;password= parameter is present:
        1. Replace the encrypted password value with the new password in plaintext.
          Note: Once the service is started, the plaintext password in the file will be replaced with an encrypted value.
        2. Remove the ;PasswordEncrypted=True parameter from the end of the same line.
  3. On the line starting with <RemoteProxyDeploymentSettings, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
  4. Save the updated Config.xml
Update Proxy.xml
  1. Open Proxy.xml in a text editor.
  2. On the line starting with <ProxyPostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
  3. On any line(s) starting with <PersistentCachePostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct.
  4. Save the updated Proxy.xml

Update Connection Settings on the Proxies

  1. On each Veeam Backup for Microsoft 365 Proxy, navigate to:
    • Windows: C:\ProgramData\Veeam\Backup365\
    • Linux: /opt/veeamvboproxy/
  2. Make a copy of Proxy.xml, just in case changes need to be reverted or a misconfiguration occurs.
Update Proxy.xml
  1. Open Proxy.xml in a text editor.
  2. On the line starting with <ProxyPostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
  3. On any line(s) starting with <PersistentCachePostgres, review and update each parameter as needed.

    Note: Only the host and port values should need to be checked to make sure they are correct.
  4. Save the updated Proxy.xml

Finalize Migration

  1. On the primary Veeam Backup for Microsoft 365 server (aka controller) and all associated Proxies, start the Veeam Backup for Microsoft 365 services:
    • Veeam Backup for Microsoft 365 Server 
      Get-Service Veeam.Archiver.Proxy | Start-Service
Get-Service Veeam.Archiver.Service | Start-Service
    • Veeam Backup for Microsoft 365 Windows Proxy 
      Get-Service Veeam.Archiver.Proxy | Start-Service
    • Veeam Backup for Microsoft 365 Linux Proxy 
      systemctl start Veeam.Archiver.Proxy

More Information

Should any issues occur during the migration, please create a Veeam Support case. To help expedite the investigation, please include a zip of the contents of C:\ProgramData\Veeam\Backup365\Logs\.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧

Options to Add Some Hypervisors Missing After Upgrading to Veeam Backup & Replication 12.2

November 18, 2024, 4:00 pm
$
0
0

Options to Add Some Hypervisors Missing After Upgrading to Veeam Backup & Replication 12.2

KB ID: 4687
Product: Veeam Backup & Replication | 12.2
Veeam Backup for Nutanix AHV
Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
Published: 2024-11-19
Last Modified: 2024-11-19

Challenge

After upgrading to Veeam Backup & Replication 12.2 or higher, the option to add Proxmox VE, Nutanix AHV, Red Hat Virtualization, and Oracle Linux Virtualization Manager is not listed when adding Virtualization Platforms.

Note: The root cause of this issue causes the options for all Virtualization Platforms that are added to Veeam Backup & Replication via a Plug-In module to become unavailable (i.e., Nutanix AHV, Red Hat Virtualization, and Oracle Linux Virtualization Manager).

missing

Cause

This issue occurs because the Platform Service (Veeam PVE Service/Veeam AHV Service/Veeam KVM Service) fails to establish a connection to Veeam Backup & Replication over the expected port (6172).

When this occurs, the log Platform Service logs will contain the following:

  • C:\ProgramData\Veeam\Backup\Plugins\PVE\Veeam.PVE.PlatformSvc.log 
    ERROR | [PlatformService]: Failed to start PlatformService: System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (localhost:6172)
ERROR | [PlatformService]:  ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.
  • C:\ProgramData\Veeam\Backup\Plugins\RHV\Veeam.RHV.PlatformSvc.log 
    ERROR | [StorageClient]:  ==> Response "Get" "https://localhost:6172/api", "status: Error", duration: "2 sec 32 msec", body: """" 
ERROR | [StorageClient]: Exception accrued during connection attempt: No connection could be made because the target machine actively refused it. (localhost:6172)
  • C:\ProgramData\Veeam\Backup\Plugins\AHV\Veeam.AHV.PlatformSvc.log 
    ERROR | [StorageClient]:  ==> Response "Get" "https://localhost:6172/api", "status: Error", duration: "2 sec 6 msec", body: """"
ERROR | [StorageClient]: Exception accrued during connection attempt: No connection could be made because the target machine actively refused it. (localhost:6172)

Solution

Reboot Required
This solution requires the Veeam Backup Server to be rebooted, please plan accordingly.

Ensure that the registry value controlling the dbProvider port has been set to the correct port.

  1. Set the following registry value to the correct value as shown:

    Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\API\DbProvider
    Value Name: Port
    Value Type: DWORD (32-Bit) Value
    Value Data(Decimal): 6172

    Set value using PowerShell:
New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\API\DbProvider' -Name 'Port' -Value "6172" -PropertyType DWORD -Force
  1. Reboot the Veeam Backup Server.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
↧
Viewing all 4502 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>