Challenge

Cause

• Backup of failover clusters is supported in Veeam Agent for Microsoft Windows managed by Veeam Backup & Replication only. You cannot process a failover cluster by Veeam Agent for Microsoft Windows operating in the standalone mode.
• Agent license with a server counter must be installed in Veeam Backup & Replication to enable Agent Management features including failover cluster support.
• Veeam Agent for Microsoft Windows supports Windows Server Failover Clusters running Microsoft Windows Server 2008 R2 and later.
• Workgroup clusters, multi-domain clusters, and mixed OS version clusters are not supported.
• Cluster Shared Volumes (CSV) are skipped automatically during the backup.
• The following Microsoft Failover Cluster applications are supported: Microsoft SQL Server Failover Cluster Instances (Microsoft SQL Server 2008 SP4 or newer), Microsoft SQL AlwaysOn Availability Groups, Microsoft Exchange Database Availability Groups (Microsoft Exchange Server 2010 or newer).
• AlwaysOn Clusterless Availability Groups are not supported.
• Managed by backup server job with failover cluster type does not support the file-level backup mode.
• Recovery must be performed via Veeam Backup & Replication console.

Solution

Microsoft Windows Server Failover Clusters, Microsoft SQL Server Failover Cluster Instances, SQL Always On Availability Groups

Microsoft Exchange Database Availability Group

Starting with Veeam Backup & Replication 9.5 Update 4, Microsoft Exchange database availability group (DAG) nodes are now automatically processed in a sequential manner, so it is possible to use Veeam Agent for Microsoft Windows to process Microsoft Exchange Database Availability Groups (DAGs).

The procedure of adding a DAG to a Veeam Agent backup job differs depending on the type of the DAG that you want to process:

• For a regular DAG, the backup job configuration procedure is the same as for any failover cluster mentioned above, so all the steps above are relevant
• For an IP Less DAG (a DAG without an Administrative Access Point), the backup job configuration procedure is similar to the same procedure for standalone servers. To process an IP Less DAG, you must create a Veeam Agent backup job for servers in the Veeam backup console and add  all nodes of the IP Less DAG (the steps below show it in detail) to this job.

Then add servers that act as DAG nodes to a Veeam Agent backup job for servers configured in Veeam Backup & Replication.

During the backup process, Veeam Backup & Replication detects that servers in the backup job are part of a DAG, and creates a transactionally consistent backup of Microsoft Exchange databases running on these servers (only passive database copies are processed, active ones are excluded from VSS freeze operations; however, the job still copies all the correspondent EDB-files of all databases from all the nodes).

Application-aware processing should be enabled for a consistent backup, log truncation and application-item restore possibility.

Challenge

Product Information:

Company name: ExaGrid
Product Family: ExaGrid with Veeam Accelerated Data Mover
Status: Veeam Ready - Repository
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup or restore functionalities.

Solution

Product Details:

ExaGrid understands that deduplication is required, but how you implement it changes everything in backup. ExaGrid has a unique landing zone where backups can land straight to disk without any inline processing. Backups are fast and the backup window is short. Deduplication and offsite replication occur in parallel with the backups. Deduplication and replication never impede the backup process as they always are second order priority. ExaGrid calls this “adaptive deduplication.”

Veeam testing configuration:

Veeam Build Number: 9.0.0.902

Job Settings:

Repository Settings:

Special Considerations:

• Scale-out Backup Repositories supported on ExaGrid EX series appliances starting from Exagrid Software version 5.0

Challenge

Product Information:

Company name: Hewlett Packard Enterprise
Product Family: StoreOnce w/Catalyst
Status: Veeam Ready - Repository
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup or restore functionalities.

Solution

Product Details:

Veeam testing configuration:

Veeam Build Number: 9.0.0.902

Job Settings:

Repository Settings:

Challenge

Solution

VSSADMIN LIST PROVIDERS

If more than the default software provider is installed, another third party software suite may have enabled its provider on the guest.  When this provider remains on the system when backup has ceased, it may cause problems for native backup and other tasks that attempt to initiate a VSS backup. This component of the third party software will need to be removed if Veeam Backup & Replication is to process this source guest consistently.

For more information on removing specific providers, please refer to vendor documentation regarding VSS Provider and Agent installation. In some instances, the VSS Provider component can be removed while keeping the rest of the software functionally intact.

More Information

Challenge

Cause

Solution

More Information

Veeam Backup & Replication support for VMware vSphere: https://www.veeam.com/kb2443

Challenge

Product Information:

Company name: ExaGrid
Product Family: ExaGrid with Veeam Accelerated Data Mover
Status: Veeam Ready - Repository
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup or restore functionalities.

Solution

Product Details:

ExaGrid understands that deduplication is required, but how you implement it changes everything in backup. ExaGrid has a unique landing zone where backups can land straight to disk without any inline processing. Backups are fast and the backup window is short. Deduplication and offsite replication occur in parallel with the backups. Deduplication and replication never impede the backup process as they always are second order priority. ExaGrid calls this “adaptive deduplication.”

Veeam testing configuration:

Veeam Build Number: 9.0.0.902

Job Settings:

Repository Settings:

Special Considerations:

• Scale-out Backup Repositories supported on ExaGrid EX series appliances starting from Exagrid Software version 5.0

Challenge

Product Information:

Company name: Hewlett Packard Enterprise
Product Family: StoreOnce w/Catalyst
Status: Veeam Ready - Repository
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup or restore functionalities.

Solution

Product Details:

Veeam testing configuration:

Veeam Build Number: 9.0.0.902

Job Settings:

Repository Settings:

Challenge

Cause

Please confirm that you are running version 9.5.4.2615 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console.

To upgrade from 9.0 or earlier version, download 9.5 Update 4a ISO image, and consult the upgrade section of the Release Notes document.

After upgrade, your build number will be 9.5.4.2753. You will also see the vendor name changed from Veeam Software AG to Veeam Software Group GmbH, reflecting the legal company name change. Please note that the name change has also resulted in a change of the code signing certificate.

Solution

• VMware vSphere 6.7 U2 readiness, including support for virtual hardware version 15. Please note that the testing has been performed on pre-release 6.7 U2 builds, while official support will still require a comprehensive testing of the generally available build.
• Microsoft System Center Virtual Machine Manager 2019 is now supported as a source for Microsoft Hyper-V VMs backup jobs.
• Dell EMC Data Domain DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols.
• New Japanese Era compatibility. 天皇陛下万歳

• Upgrade to Update 4 fails with the "Database version downgrade detected ... Reboot and restart the setup" error on machines where system time regional format uses a.m. and p.m. (lowercase with dots)
• On Hyper-V versions prior to 2016, backup and replication jobs without application-aware processing enabled failing with "The system cannot find the file specified" error.
• Backup console failing to open after upgrade with "Object reference not set to an instance to an object" from backup console or "Could not load file or assembly" error in the log.
• Backup of Windows XP SP1 VMs fails with the "Failed to call RPC function Vss.GetFileFromGADir" error.
• After upgrading to Update 4, SureBackup jobs may start failing due to lack of disk space in the vPower NFS cache folder due to virtual lab settings incorrectly updated during configuration upgrade.
• VeeamZIP™ operations should no longer consume a license for virtual machine that were previously licensed due to being a part of regular backup jobs.
• Primary storage integration issues around HPE Nimble, NetApp, IBM and Dell EMC VNX storage.
• HPE StoreOnce Catalyst library was updated to version 24.90.0.8 fixing the memory leak issue.
• Tape support reliability improvements, including a number of UI performance issues around tape management functionality.

More Information

Challenge

Task fails with the error "root element is missing."
You can find such entries in the log file:

[timestamp] <01> Error Read summary xml error at Veeam.Backup.Core.CRawSummary.CreateOibSummary()
[timestamp] <01> Error at Veeam.Backup.Core.CSynOibAlg.CreateOib(CPoint fullPoint, CPoint rollPoint, CStorage fullStorage, CStorage rollStorage, COib rollOib)
[timestamp] <01> Error at Veeam.Backup.Core.CBackupJobPerformer.ExecuteTask(IBackupTask task, ITarget target)
[timestamp] <01> Error  Root element is missing. at System.Xml.XmlTextReaderImpl.Throw(Exception e)

Cause

This usually occurs when part of Veeam data could not be written to the summary.xml file (due to space, connectivity issue or some other specific issue). After that failure, cleaning up space on a target or fixing other problems that caused this behavior initially will not let you proceed with the incremental because the summary.xml is missing critical information on the previous backup.

Solution

There are two methods to potentially resolve this:

• The first option is to run a full backup on the corresponding job by right-clicking on a job and selecting "perform full backup". This is the method that leaves the least possibility of later issues.
   
• The second option is more involved, has some caveats, and is not guaranteed to work but may save some time.
  1. Verify the job itself is not currently running.
  2. Once verified go into the backup repository and locate the backup files for the job having the issue.
  3. Move the VBM file to another location without deleting it.
  4. After the VBM file has been moved, return to Veeam B&R and run a normal backup operation.
      

     Note: This also works for PerVM and SOBR based backups.
     
     Note 2: When moving the VBM, do so to a path outside the backup repository path. For instance, if the repository path is C:\Backups, move the VBM to either the root of the drive or another path from the drive. If it is placed in another subfolder of C:\Backups, and the repository is re-scanned, Veeam will attempt to import the VBM as a backup.
     
     This will attempt to create a new VBM file for the chain itself using metadata mirrored in the full backup storages, without the need to create another active full backup, avoiding larger amounts of data being sent to the repository. If this fails, the first option will likely be necessary.
     
     If the chain contains multiple full backups, only the latest full and increments following it will be used to recreate the VBM file. Retention may need to be performed manually by deleting older backup files when they are no longer needed.

      

Challenge

Cause

Please confirm that you are running version 9.5.4.2615 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console.

To upgrade from 9.0 or earlier version, download 9.5 Update 4a ISO image, and consult the upgrade section of the Release Notes document.

After upgrade, your build number will be 9.5.4.2753. You will also see the vendor name changed from Veeam Software AG to Veeam Software Group GmbH, reflecting the legal company name change. Please note that the name change has also resulted in a change of the code signing certificate.

Solution

• VMware vSphere 6.7 U2 readiness, including support for virtual hardware version 15. Please note that the testing has been performed on pre-release 6.7 U2 builds, while official support will still require a comprehensive testing of the generally available build.
• Microsoft System Center Virtual Machine Manager 2019 is now supported as a source for Microsoft Hyper-V VMs backup jobs.
• Dell EMC Data Domain DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols.
• New Japanese Era compatibility. 天皇陛下万歳

• Upgrade to Update 4 fails with the "Database version downgrade detected ... Reboot and restart the setup" error on machines where system time regional format uses a.m. and p.m. (lowercase with dots)
• On Hyper-V versions prior to 2016, backup and replication jobs without application-aware processing enabled failing with "The system cannot find the file specified" error.
• Backup console failing to open after upgrade with "Object reference not set to an instance to an object" from backup console or "Could not load file or assembly" error in the log.
• Backup of Windows XP SP1 VMs fails with the "Failed to call RPC function Vss.GetFileFromGADir" error.
• After upgrading to Update 4, SureBackup jobs may start failing due to lack of disk space in the vPower NFS cache folder due to virtual lab settings incorrectly updated during configuration upgrade.
• VeeamZIP™ operations should no longer consume a license for virtual machine that were previously licensed due to being a part of regular backup jobs.
• Primary storage integration issues around HPE Nimble, NetApp, IBM and Dell EMC VNX storage.
• HPE StoreOnce Catalyst library was updated to version 24.90.0.8 fixing the memory leak issue.
• Tape support reliability improvements, including a number of UI performance issues around tape management functionality.

More Information

Challenge

Cause

• In VMware environments, VSS ensures transaction consistency when backing up Windows VMs.
• In Hyper-V on Windows Server 2008R2, 2012, and 2012R2, VSS is the primary component of the backup API.
• Veeam Agent for Windows (formerly Veeam Endpoint Backup) uses VSS to help make sure data is consistent.
• VSS is used to trigger transaction log truncation for Microsoft Exchange.

Solution

Test shadow copy creation, then review Interpreting the Results (below).  

VMware Environments or Agent Backups

Copy-Only Mode

Use this method when transaction log truncation is not relevant. For best comparison, specify copy-only in the Veeam job settings.

​diskshadow /l c:\windows\temp\output.txt (the /l parameter is optional, it enables logging to a file; the path to the file is an example)
set verbose on
set context volatile

add volume \\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}\
add volume X:
add volume C:\ClusterStorage\Volume1

create

Full Mode

Full mode is the default setting for Veeam jobs. This method will notify VSS writers that a backup has occurred. Some applications, including Microsoft Exchange, will truncate transaction logs automatically in response to this notification. Other applications, such as Microsoft SQL Server, record that a backup has been taken but do not truncate transaction logs.

To test log truncation along with the creation of the shadow, run the following commands.
 

​diskshadow /l c:\windows\temp\output.txt (the /l parameter is optional, it enables logging to a file; the path to the file is an example)
set verbose on
set context volatile

add volume \\?\Volume{3c8d1bcb-9d95-11e5-80b0-806e6f6e6963}\
add volume X:
add volume C:\ClusterStorage\Volume1

begin backup
create

end backup

Hyper-V Environments

Note: The following information is applicable to Server 2008R2, 2012, and 2012R2.

Veeam Backup & Replication creates shadow copies of volumes containing virtual machines. For transactionally-consistent backups (Application-Aware Image Processing or Hyper-V Quiescence), the Hyper-V VSS Writer triggers the Hyper-V Volume Shadow Copy Requestor service in each VM to create shadow copies of volumes within the VM. Error messages generated by shadow copy creation failure generally do not indicate whether the problem is isolated to a hypervisor volume or an in-guest volume.

Start by isolating whether the failure occurs only when using Application-Aware Image Processing or Hyper-V Quiescence. If the problem does not occur when both options are disabled, test shadow copy creation from within the virtual machine as described in the VMware Environments or Agent Backups section, above.

If snapshot creation is failing for crash-consistent backups, or if in-guest shadow copy creation does not result in any errors, it may be necessary to test shadow copy creation on the Hyper-V host. Because Hyper-V backup can be complex, a scripted approach is recommended. Veeam Support can run a scripted test that also collects a significant amount of useful logging. Contact support to schedule a remote session, and ask about hv_mkshadow.

Warning: Attempting to perform a shadow copy of a volume containing virtual machines will trigger in-guest shadow copy creation on all VMs on that volume unless specifically excluded. This may have negative effects on performance or responsiveness of these VMs and the Hyper-V host. Veeam Backup and the hv_mkshadow script exclude unnecessary VSS writer components from the shadow copy.

Finding Volume GUIDs

To add volumes that lack a mount point (such as the System Reserved Partition), use the volume GUID obtained through either the mountvol command-line tool, or the Shadow Copies utility.

To access the Shadow Copies utility, right click any volume and choose Configure Shadow Copies. On older operating systems, this may instead be a tab in Properties. In the Shadow Copies utility:

1. Select the volume displayed as a GUID;
2. Click Settings…
3. Copy the volume GUID from the settings window and paste it into DiskShadow.

Alternatively, run “mountvol” from a command prompt; below the usage information will be a list of GUIDs and their associated mount points, if any.

More Information

Interpreting the Results

Typically, if shadow copy creation fails via both Diskshadow and Veeam products, that indicates that the problem is isolated to shadow copy creation. Troubleshoot the errors reported by Diskshadow and any events appearing in Event Viewer.

Troubleshooting shadow copy creation or transaction log truncation may require the assistance of Microsoft technical support.

Two examples of failures reported directly by Diskshadow are as below. The first is an instance where the Volume Shadow Copy service fails, hangs, or is shut down midway through the creation process. The “RPC server” error can be a bit misleading; in this case a call was sent to the Volume Shadow Copy service and it was not there to receive it.

COM call "m_pVssBackup->StartSnapshotSet" failed.

The last operation failed.
- Returned HRESULT: 800706ba
- Error text: The RPC server is unavailable.

Another example shows a more common issue, that of the volume having insufficient free storage for the shadow copy creation.

The last operation failed.
- Returned HRESULT: 8004231f
- Error text: VSS_E_INSUFFICIENT_STORAGE

These messages will usually immediately follow the list of included writers, and should be the last output returned in the Diskshadow process.

In some cases, shadow copy creation will succeed via Diskshadow, but error or warning events will be generated in the event log. If similar errors are generated when Veeam backup or replication jobs fail to create a shadow copy, that usually indicates that the Veeam application is aborting the shadow copy in response to the errors. In this situation, the Veeam application can usually be assumed to be functioning correctly, so it is best to focus troubleshooting on any events appearing in Event Viewer.

Troubleshooting shadow copy creation or transaction log truncation may require the assistance of Microsoft technical support.
The error “COM call "lvssObject4->GetRootAndLogicalPrefixPaths" failed” may be ignored. For more information, see Microsoft KB3025158.

Challenge

Cause

Solution

•          Eject manually;
•          Eject media once job finished;
•          Unload media in the slot during the job;

Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TDS-16489U-R2
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TDS-16489U-SFx-R2
Storage Category: RAID Storage Array
Drive quantity, size, type: 16 - 2TB HDD
Storage configuration: RAID6, no SSD caching
Firmware version: QES 2.1.0.0790 and QTS 4.3.6.0805
Connection protocol and speed: SMB | 10 GbE
Additional support: All models and configurations of TDS-16489U-R2 with specifications equivalent or greater than the above

Dual CPU and dual OS system: A perfect NAS solution for high-performance computing and storage by using the QES or QTS operating system. Integrating an application server and storage server into one system, the next-generation TDS-16489U R2 also provides you with the option of using either QES (an enterprise-grade OS that provides efficient and reliable storage for mission-critical tasks) or QTS (a feature-rich OS for storage and diverse application servers).

Veeam testing configuration:

Veeam Build Number: 9.5.4.2615

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• No array deduplication used in testing
• No array compression used in testing
• Jumbo frames used in testing (MTU=9000)

Challenge

Cause

Solution

1. Ensure that all jobs are in a stopped state.
2. Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
3. Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)
4. Rename the Veeam.Backup.Model.dll file to Veeam.Backup.Model.dll_backup
5. Replace the files listed in the previous step with those found in the hotfix package
6. Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )

More Information

Challenge

Cause

• /Jobs: LastRun or EndTime now returns 00:00:00.0000000 UTC, January 1, 0001 if the value is not populated in UI
• /HardwarePlans: memoryQuota now correctly returns '0' with memoryQuotaUnits set to "Unlimited" if the quota is unlimited
• /BackupResources: backupRepositories now returns a proper link to a tenant's cloud repository
• /BackupResources: usedStorageQuota now always returns correct values
• /Computers: destinationFreeSpace now returns '0' when subtenant quota or policy is defined
• Deserialization failure now returns a proper response in the following format: List<ResponseResult>
• Some resources' IDs may change after the upgrade. It is recommended to request all data anew
• The following resources are now considered legacy and may retrieve incorrect data: /BackupLicenses: licensedVMs, usedVMs , newVMs; /CloudLicenses: licensedVMs, usedVMs, newVMs

Solution

Challenge

Cause

Solution

Challenge

Product Information:

Company name: FAST LTA, AG
Product Family: Silent Brick System
Status: Veeam Ready – Archive
Classification Description: Verified disk archive storage that can be used as a Backup Copy target. Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.

Solution

Product Details:

Model number: Silent Brick
Storage Category: Hybrid Storage
Drive quantity, size, type: 12 - SATA HDDs via SAS Bus
Storage configuration: SecureNAS - Triple Parity
Firmware version: 2.11
Connection protocol and speed: 10GbE
Additional support: All models and configurations of Silent Brick System with specifications equivalent or greater than the above.

General product family overview: Simplify your backup with Silent Bricks. On-premise storage appliances with integrated data protection for all NAS and VTL requirements. Media replication and rotation. Online, offline and off-site, with support for air gap environments. All in one system. The Silent Brick System is based on modular and transportable storage units called 'Silent Bricks' where each Silent Brick consists of 12 Disks. Depending on the Silent Brick Type these disks may be HDD (Silent Brick ) or SSD ( Silent Brick FLASH ).
The assignment is done on a per Brick Basis where each Brick can act as a Backup to Disk Storage, a virtual Tape Library or an Archival Storage. The redundancy when set up as Backup to Disk Storage is configurable with 2 or 3 Parities per Silent Brick. A SecureNAS Volume can then be spanned over 1 to many Silent Bricks. Extending a SecureNAS Volume is possible on the fly by assigning additional Bricks. The parities will still be on a per Silent Brick Basis. For optimal performance the Silent Brick System offers dual 10GB Ethernet connection.

Veeam testing configuration:

Note: The following settings were used by the vendor to meet Veeam Ready testing requirements and should not be considered best practices. Additional changes or settings may be needed to meet the storage efficiency or performance needs for each environment. For each setting, reference links are provided for further clarification.

Veeam Build Number: 9.5.0.1922

Job Settings:

• Deduplication: Enabled (Default)
• Compression: Optimal (Default)
• Storage Optimization: Local Target (Default)

Repository Settings:

• Repository Type: Shared Folder
• Align backup file blocks: Disabled (Default)
• Decompress before storing: Disabled (Default)
• This repository is backed by rotated hard drives: Enabled
• Per-VM Backup Files: Disabled (Default)

Vendor recommended configuration:

Hardware Settings:

• Jumbo frames used in testing environment
• SMB storage protocol used during testing. Vendor also supports NFS, and ISCSI or Fibre Channel for virtual tape library support.
• Dedicated SMB user for storage share, used default settings for share configuration
• 3 parities used in SNAS configuration

Challenge

Cause

Solution

1. Ensure that all jobs are in a stopped state.
2. Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
3. Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)
4. Rename the Veeam.Backup.Model.dll file to Veeam.Backup.Model.dll_backup
5. Replace the files listed in the previous step with those found in the hotfix package
6. Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )

More Information

Challenge

Cause

• /Jobs: LastRun or EndTime now returns 00:00:00.0000000 UTC, January 1, 0001 if the value is not populated in UI
• /HardwarePlans: memoryQuota now correctly returns '0' with memoryQuotaUnits set to "Unlimited" if the quota is unlimited
• /BackupResources: backupRepositories now returns a proper link to a tenant's cloud repository
• /BackupResources: usedStorageQuota now always returns correct values
• /Computers: destinationFreeSpace now returns '0' when subtenant quota or policy is defined
• Deserialization failure now returns a proper response in the following format: List<ResponseResult>
• Some resources' IDs may change after the upgrade. It is recommended to request all data anew
• The following resources are now considered legacy and may retrieve incorrect data: /BackupLicenses: licensedVMs, usedVMs , newVMs; /CloudLicenses: licensedVMs, usedVMs, newVMs

Solution

Challenge

Cause

Solution

1. Verify that the account used to connect to Veeam Backup and Replication OR Hyper-V server in Veeam ONE has correct permissions. To check the account name, go to Veeam ONE Monitor > Data Protection View > right-click on the Veeam Backup and Replication object. Note the specified account. You can check the same for the Hyper-V server: Veeam ONE Monitor > Infrastructure tree > right-click on the Hyper-V object.
2. On the Veeam Backup and Replication OR Hyper-V server, confirm that this account as well as the Veeam ONE service account are added to the Event Log Readers Group and Administrators group in Local Systems and Groups
3. Even if the Firewall is off, activate the following firewall rules on the Veeam Backup and Replication OR Hyper-V server side:

• Remote Event Log Management (NP-In)
• Remote Event Log Management (RPC)
• Remote Event Log Management (RPC-EPMAP)
• COM+ Network Access (DCOM-In)

4. Check UAC settings.

1. Change the type of the all Public network connections to Private using the following Powershell cmdlet: 

Set-NetConnectionProfile -NetworkCategory Private

Or using the registry editor (machine restart will be required):

More Information