Challenge

During the snapshot removal step of a Veeam job, the source VM loses connectivity temporarily.

Cause

Veeam does not remove the snapshot itself, Veeam sends an API call to VMware to have the action performed.

The snapshot removal process significantly lowers the total IOPS that can be delivered by the VM because of additional locks on the VMFS storage due to the increase in metadata updates, as well as the added IOP load of the snapshot removal process itself. In most environments, if you are already over 30-40% IOP load for your target storage, which is not uncommon with a busy SQL/Exchange server, then the snapshot removal process will easily push that into the 80%+ mark and likely much higher. Most storage arrays will see a significant latency penalty once IOP's get into the 80%+ mark which will of course be detrimental to application performance.

Solution

Isolation Test

The following test should be performed during a time when connectivity to the VM is not sensitive, for instance during off peak hours.

To isolate this issue to the specific VMware snapshot removal event, Veeam suggests the following isolation test:

1. Create a snapshot on the VM in question.
2. Leave the snapshot on the VM for duration of time that a Veeam job runs against that VM.
3. Remove the snapshot.
4. Observe the VM during the snapshot removal.

If while performing the test above you observe the same connectivity issues as during the Veeam job run, the issue very likely exists within the VMware environment itself. Please review the following list of troubleshooting steps and known issues. If none of the following work to resolve the issue, we advise that you contact VMware support directly regarding the snapshot removal issue.

Common Troubleshooting Tasks

• Check the VM for snapshots while no job is running and remove any that are found.
• Check for orphaned snapshots on the VM. (See: http://kb.vmware.com/kb/1005049)
• Reduce the number of concurrent tasks that are occurring within Veeam, this will in turn reduce the number of active snapshot tasks on the datastores.
• Move VM to a datastore with more available IOPS, or split the disks of the VM up into multiple datastores to more evenly spread the load.
• If the VMs CPU resources spike heavily during Snapshot consolidation, consider increasing the CPU reservation for that VM.
• Ensure you are on the latest build of your current version of vSphere, hypervisors, VMware Tools and SAN firmware when applicable.
• Move VM to a host with more available resources.
• If possible, change the time of day that the VM gets backed up or replicated to a time when the least storage activity occurs.
• Use a workingDir to redirect Snapshots to a different datastore than the one the VM resides on. http://kb.vmware.com/kb/1002929
• Disable VMware Tools Sync driver on the VM: http://kb.vmware.com/kb/1009886

Known Issue with NFS 3.0 Datastores

Note: This issue will present as multiple minutes worth of stun. Normal snapshot stun is only mere seconds.

At the time of the writing of this KB there is a known issue with NFS Datastores and Virtual Appliance (HOTADD) transport mode. The issue is documented in this VMware KB article: http://kb.vmware.com/kb/2010953

Veeam advises that if this issue occurs one of three things can be done to work around this:

1. Use Direct NFS Mode

More details available here:
https://helpcenter.veeam.com/docs/backup/vsphere/direct_nfs_access.html

2. Configure Veeam Backup & Replication to use a Proxy on the same host as the VM

Note: This option is only available in versions newwer than 7.0.0.839

1. Create a VM proxy on every host in your VMware cluster where backups occur
2. On the server where the Veeam Backup & Replication console is installed open ‘Registry Editor’
3. Create the following registry value in the key below:
   HKLM\Software\Veeam\Veeam Backup and Replication\
   Type: DWORD
   Name: EnableSameHostHotaddMode
   value: 
   For the value there are two options, "1" or "2" these options are explained below:
   • 1- if proxy on same host as VM is unavailable, Veeam Backup & Replication will fail over to a proxy on a different host and use available transport mode, which may cause stun
   • 2 - If proxy on same host as VM is unavailable, Veeam Backup & Replication will use an available proxy on a different host, but force it to use network transport mode, so that no stun occurs; this may be preferable when stun is not tolerable.

Note: Both values 1 or 2 will enable the SameHostHotaddMode, which forces Veeam B&R to first attempt to use the Proxy that is on the same host as the VM to be backed up.

3. Reconfigure proxies to use Network Transport mode.

1. Edit the proxies listed under [Backup Infrastructure]>[Backups Proxies]
2. Click the [Choose] button next to “Transport mode”
3. Select the radio option for “Network” mode
4. Click [OK] to close the prompt and then [Finish] to commit the change.

More Information

The following links are provided to help understand more about the Snapshot Removal process within VMware:

http://up2v.nl/2011/05/09/know-the-performance-impact-of-snapshots-used-for-backup/

http://kb.vmware.com/kb/1002836
 

Challenge

Solution

• Microsoft System Center Virtual Machine Manager 2019 is now supported.
• VMware vCloud Director 9.7 compatibility at the existing Update 4 feature level.
• VMware vSphere 6.7 U2 readiness including support for VMs with virtual hardware version 15. 
• Dell EMC Data Domain using DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols. 
• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support as guest VMs, and for the installation of Veeam ONE. 
• VMware vSphere 6.5 U3 and VMware vSphere 6.7 U3 are officially supported with Update 4a. 

• High CPU usage is observed on the Veeam Backup & Replication 9.5 Update 3/3a/4 server after upgrading Veeam ONE to v9.5 Update 4
• Business View grouping expression raises an error “invalid expression” if the length is longer than 25 rows
• Exporting Business View objects in the Veeam ONE Monitor client does not include category names
• Object Properties collection task returns error or warning with “Failed to retrieve empty storage controller list for Hyper-V host” message in the session details
• High load on Veeam ONE SQL Server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances Veeam ONE cannot connect to the database after upgrading Veeam ONE to v9.5 Update 4
• Failed to download clients.xml from the vCenter server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances performance data cannot be collected from SCVMM server and its objects
• Veeam ONE cannot collect data from Veeam Backup Enterprise Manager and its objects
• Veeam ONE tries to connect to already deleted hosts from the monitoring

More Information

Challenge

Product Information:

Company name: Fujitsu
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000
Drive quantity, size, type: 10 - SAS HDD
Firmware version: V6.1A7120-SP03
General product family overview:

ETERNUS CS8000 is a datacenter solution for backup storage for mainframe and open systems. Its intelligent process automation and pooling of storage capacity reduces the TCO for complex backup environments by 40%. Unique scalability in capacity and performance makes ETERNUS CS8000 a viable solution, delivering ongoing cost savings.

Veeam testing configuration:

Veeam Build Number: 9.5.x

Job Settings:

Repository Settings:

More Information

Challenge

Product Information:

Company name: Fujitsu (Fujitsu Technology Solutions)
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000 V7.1
Storage Category: RAID Storage Array
Drive quantity, size, type: 24 – 960GB SSD 2.5” drives
Storage configuration: RAID5
Firmware version: V7.1A2140-SP00
Connection protocol and speed: CIFS 10GbE
Additional support: All models and configurations of ETERNUS CS8000 with specifications equivalent or greater than the above

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)

More Information

Challenge

Product Information:

Company name: Adistec
Product Family: Data Protection Appliance Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DPA M (M24)
Storage Category: Integrated Data Protection Appliance
Drive quantity, size, type: 4, 8TB, SAS HDD | (32TB total)
Storage configuration: RAID5 configured HDDs (12Gbps SAS) with read/write cache
Firmware version: V2
Connection protocol and speed: 10GbE ISCSI
Additional support: All models and configurations of DPA M with specifications equivalent or greater than the above: M, L & XL

Adistec Data Protection Appliances for VEEAM combine: customized Intel hardware platform, Veeam Availability Suite software, and Adistec Enterprise Cloud services resulting in a robust solution to protect your customer’s data supported by Adistec Total Support and Veeam. Simplify the Backup Storage’s infrastructure, eliminate complexity and maximize data availability and protection with this turnkey solution at an affordable price. Three models available in one and two RUs, with single Quad-Core or dual Octa-Core processors configuration. Starting with four 3.5” disks up to twelve, getting 16TB to 120TB of usable capacity.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• HDD – 1GB read cache on RAID controller, write back policy using backup battery
• Jumbo Frames used during testing (9000 MTU)
• Multipathing using Windows Server NIC teaming

More Information

Challenge

Product Information:

Company name: Hedvig Inc.
Product Family: Hedvig Distributed Storage Platform
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: Hedvig Distributed Storage Platform
Drive quantity, size, type: 1x 300GB SSD | 15x 1TB HDD (x3 Nodes)
Firmware version: 3.7.2
Connection protocol and speed: iSCSI, 10GbE
Additional support: All configurations of Hedvig Distributed Storage Platform with specifications equivalent or greater than the above

Hedvig provides multi-site software-defined storage for primary and secondary applications for private-, multi-, and hybrid-cloud deployments. Unique capabilities like replication policy, deduplication, compression, and encryption can be enabled per application. This programmable platform can scale from 10’s of TB to multi-PB with no practical limit.

Veeam testing configuration:

Veeam Build Number: 9.5.0.711

Job Settings:

Repository Settings:

More Information

Challenge

Product Information:

Company name: Panzura, Inc.
Product Family: Freedom NAS
Status: Veeam Ready - Repository*
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: 5500
Storage Category: Cloud-out NAS Storage
Drive quantity, size, type: 12 - 800GB, SAS SSD
Storage configuration: RAID50 via automatic software configuration
Firmware version: 7.0.2.5
Connection protocol and speed: SMB, 2 x 10GbE
Additional support: All models and configurations of Freedom NAS with specifications equivalent or greater than the above

Panzura FreedomTM is an intelligent hybrid cloud storage solution underpinned by Panzura CloudFS. Panzura CloudFS is a scale-out, distributed file system purpose-built for the cloud. Programmatically accessible through REST APIs, it utilizes high performance flash in the data center, and integrates the cloud for economics, scalability, and durability. Unlike NAS, it scales globally across multiple sites and multiple clouds.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings: The default configuration enables auto-tuning for all Panzura settings, which work well with the Veeam application. The caching policy should be set to pinned (as opposed to autotune) to ensure the administrator controls which backup sets are available locally. All Veeam backup data must be pinned locally to ensure fast restores and effective data operations within Veeam, without cloud reads.

More Information

Challenge

Cause

Solution

More Information

Challenge

This article documents how change the temporary staging location where SQL transaction log backups are stored during a Veeam Agent for Windows backup operation when Transaction Log Backup is enabled.

For more information on the Transaction Log Backup process for Veeam Agent for Windows please click here.

Cause

When SQL Transaction Log Backup is enabled, Veeam Agent for Windows copies transaction log files from the log archive destination (set by the Microsoft SQL Server administrator) to a temporary folder on the server. By default the path is: C:\ProgramData\Veeam\Endpoint\SqlLogBackup.

Solution

To change the location where the SQL Transaction Logs are temporarily stored, create the following registry entry on the server.

Note: This registry change is to be made on the machine where Veeam Agent for Windows is installed, and is running the backup with SQL Transaction Log backup enabled.

Key: HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup
Type: REG_SZ (String Value)
Name: SqlTempLogPath
Value: Path to desired location (without trailing backslash)

Note: if the backup job is managed by Veeam Backup & Replication, then the path for the registry should be:

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication

The key should be created manually in the Agent machine registry if it does not exist.

Example

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

• Constant
• Carp
• Cwd
• Data::Dumper
• Encode
• Encode::Alias
• Encode::Config
• Encode::Encoding
• Encode::MIME::Name
• Exporter
• Exporter::Heavy
• File::Path
• File::Spec
• File::Spec::Unix
• File::Temp
• List::Util
• Scalar::Util
• SOAP::Lite
• Socket
• Storable
• Threads

Subsystem sftp internal-sftp

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

• Constant
• Carp
• Cwd
• Data::Dumper
• Encode
• Encode::Alias
• Encode::Config
• Encode::Encoding
• Encode::MIME::Name
• Exporter
• Exporter::Heavy
• File::Path
• File::Spec
• File::Spec::Unix
• File::Temp
• List::Util
• Scalar::Util
• SOAP::Lite
• Socket
• Storable
• Threads

Subsystem sftp internal-sftp

More Information

Challenge

Solution

• Microsoft System Center Virtual Machine Manager 2019 is now supported.
• VMware vCloud Director 9.7 compatibility at the existing Update 4 feature level.
• VMware vSphere 6.7 U2 readiness including support for VMs with virtual hardware version 15. 
• Dell EMC Data Domain using DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols. 
• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support as guest VMs, and for the installation of Veeam ONE. 
• VMware vSphere 6.5 U3 and VMware vSphere 6.7 U3 are officially supported with Update 4a. 

• High CPU usage is observed on the Veeam Backup & Replication 9.5 Update 3/3a/4 server after upgrading Veeam ONE to v9.5 Update 4
• Business View grouping expression raises an error “invalid expression” if the length is longer than 25 rows
• Exporting Business View objects in the Veeam ONE Monitor client does not include category names
• Object Properties collection task returns error or warning with “Failed to retrieve empty storage controller list for Hyper-V host” message in the session details
• High load on Veeam ONE SQL Server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances Veeam ONE cannot connect to the database after upgrading Veeam ONE to v9.5 Update 4
• Failed to download clients.xml from the vCenter server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances performance data cannot be collected from SCVMM server and its objects
• Veeam ONE cannot collect data from Veeam Backup Enterprise Manager and its objects
• Veeam ONE tries to connect to already deleted hosts from the monitoring

More Information

Challenge

Cause

New fixes:

• “/v2/tenants” get request does not display the “deleted” status for removed companies. 
• Querying “v2/tenants/{id}” and “/v2/tenants/{id}/backupResources” information may take considerable amount of time. 
• A backup policy cannot be created if there are “space” symbols in the encryption hint. 
• A backup policy cannot be created when “processingEnabled” parameter is set to True, and “Credentials” parameter is used.

• After applying a backup policy to a managed Agent, job scheduling settings are displayed incorrectly in the VAC UI, but the settings pushed to the Agent are correct. 
• Site administrators can select Public IP Addresses belonging to a different site when creating a company. 
• Under certain conditions, “Used Storage” counter may display incorrect data on the “Overview” tab. 

• Management agent installed on a Cloud Connect server is incorrectly displayed on the Backup Agents tab. 
• Under certain conditions management agent restarts every hour. 

• Network Extension IP addresses are not filtered by a reseller. Reseller can select IP addresses belonging to unmanaged companies. 
• Reseller can change his or her backup quota to “unlimited” when creating a managed company with “unlimited” quota.

• Only the first 10 000 products are displayed in the mapping area of the plugin. 
• Plugin services may consume excessive memory when there are a lot of tickets created in the ConnectWise Manage application.

• Platform type cannot be detected for old computers and is reported as “Oher.”

• Under certain conditions after installing a private hotfix Veeam.MBP.Service fails to connect to the existing database with the following error message ”Cannot change configuration database: Database version is invalid.” 
• Veeam.MBP.Service fails to start when managed backup agents have duplicate IDs (due to cloning operation) in the configuration database.

• “VM without backup” alarm is triggered for VMs that are migrated between vCenter Servers or are re-registered in the virtual infrastructure.

• Under certain conditions, the management agent may connect to VAC server without authentication.

• Computer renaming leads to duplicated values in the Protected Computers report.

• Under certain conditions, usage report for managed Veeam Backup & Replication servers may not be created within first ten days of a month.

Fixes included from previous patches:

• Cloud Copies counter on the Overview dashboard does not return any data.
• Backup agents managed by Veeam Backup & Replication report 0 restore points available in the backup policy drill down view. 

• Portal administrators can log in only when using a full domain name of the Veeam Availability Console server. 
• Users belonging to a domain user group which is added to a Veeam Availability Console security group cannot log in to the portal.
• Users belonging to a nested domain group cannot log in to the portal.

• Under certain conditions, Veeam.MBP.Service might be consuming excessive memory.
• Under certain conditions, data collection job fails to retrieve information from a Cloud Connect server that has lots of task sessions on cloud gateway servers. This results in displaying these tenants’ companies as deleted in the Veeam Availability Console UI.
• Tenant password changed in Veeam Cloud Connect is not synchronized with Veeam Availability Console.

• Office 365 and Gmail SMTP servers are not supported for notifications.  

• Inaccessible computers cannot be located when using CSV and IP discovery rule options.

• Full Access UI mode cannot be applied to a backup agent.  
• When using Select All checkbox on the Managed Backup Agents tab agent settings are applied to all computers of all managed companies regardless of the selected scope in the Company\Reseller filter.  
• Licensing attribute is not updated for managed backup agents which leads to license expiration on the backup agent.    
• Backup agent files are not validated when the installation is performed from a local folder without using a master management agent. This may result in a corrupted installation/upgrade of the backup agent. 

• Under certain conditions, management agents fail to upgrade with the following error message “The system cannot find the file specified.”

• Workstation and server backup counters in the Veeam Cloud Connect usage report are mixed up.
• Under certain conditions License usage report for Veeam Backup & Replication servers is not generated. 

• Under certain conditions, all VMs with a cloud copy which belong to different locations are reported as VMs from the default location in the invoice. 

• Querying tenant information with SetLinks parameter may take considerable time.
• The vMsBackudUpToCloud counter does not display data about VM and Agent backup copy jobs targeted to a cloud repository.  

• Cloud repository usage is not updated in ConnectWise Manage agreements when there are unknown files (not related to Veeam backups) in the repository. 
• Tickets state synchronization may stop working when triggering a mass-resolve operation in the ConnectWise Manage application. 

Solution

msiexec /update c:\VAC.ApplicationServer.x64_3.0.0.2762.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt

msiexec /update c:\VAC.WebUI.x64_3.0.0.2762.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACWebUI.txt

msiexec /update c:\VAC.ConnectorService.x64_1.0.1.610.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorService.txt

msiexec /update c:\VAC.ConnectorWebUI.x64_1.0.1.610.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorWebUI.txt

More Information

Challenge

Cause

Solution

• Additional Hypervisor support vSphere 6.7. VMware vSphere 4.0 and later (including vSphere 6, vSphere 6.5, vSphere 6.7, vSphere 6.7 U1, vSphere 6.7 U2 and vSphere 6.7 U3) 
• Monitoring SQL Transaction Log Backup Job. Veeam MP separately monitors SQL Transaction Log Backup jobs running inside backup jobs with the enabled application-aware processing option. For this purpose, Veeam MP includes a new Veeam SQL Transaction Log Backup Jobs view and Veeam Backup: SQL Transaction Log Job Status monitor.
• Improved performance of Morning Coffee Dashboards. In previous versions, Morning Coffee Dashboards tended to load slowly for large-scale environments. In Veeam MP 8.0 Update 6, the performance of Morning Coffee Dashboards has been significantly improved.
• A new metric for Veeam VMware Collector. Due to the Ops Mgr Health Service (Monitoring Agent Service) limitations that appear when a Veeam VMware Collector processes a large amount of data, it is required to distribute monitoring load among multiple Veeam VMware Collectors in large environments. To assess the monitoring load on Veeam VMware Collectors more precisely, Veeam MP provides a new % Object Monitoring Load metric.

• No monitoring for Hyper-V hosts that exceeded the license limit. Veeam MP license limits the number of Hyper-V hosts enabled for monitoring in Ops Mgr. Earlier, if the number of licensed Hyper-V hosts was exceeded and new hosts were added to the Ops Mgr infrastructure, Ops Mgr automatically stopped monitoring the old infrastructure and started monitoring the newly added hosts. In Veeam MP 8.0 Update 6, the issue was resolved, and Ops Mgr continues monitoring the old infrastructure.
• Ops Mgr event log shows excessive BackupCopyJobSessionFinished events. In previous versions, the Ops Mgr event log contained a large number of 3101 events caused by errors in the backup copy job status collection process. In Veeam MP 8.0 Update 6, the issue was resolved.

• Collector Autodeploy limitations. If you use the Collector Auto-Deployment feature to automatically deploy Veeam VMware Collectors on Management Servers, keep in mind that it will install clear 8.0 version without patches. When the installation completes, run the ISO\Update\VeeamMP80_Update6.exe installation file on each Veeam Collector to install patches.  
• Veeam MP for Hyper-V stops collecting storage metrics. If storage migrates to another volume, the storage performance collection will halt and Veeam MP will stop collecting the following metrics: Storage IOPS, Storage KB Total/sec, Storage Flush Count and Storage Error Count. Note that this issue does not affect migration between hosts. To work around the issue, restart the Ops Mgr agent after storage migration.

More Information

Challenge

Cause

New fixes:

• “/v2/tenants” get request does not display the “deleted” status for removed companies. 
• Querying “v2/tenants/{id}” and “/v2/tenants/{id}/backupResources” information may take considerable amount of time. 
• A backup policy cannot be created if there are “space” symbols in the encryption hint. 
• A backup policy cannot be created when “processingEnabled” parameter is set to True, and “Credentials” parameter is used.

• After applying a backup policy to a managed Agent, job scheduling settings are displayed incorrectly in the VAC UI, but the settings pushed to the Agent are correct. 
• Site administrators can select Public IP Addresses belonging to a different site when creating a company. 
• Under certain conditions, “Used Storage” counter may display incorrect data on the “Overview” tab. 

• Management agent installed on a Cloud Connect server is incorrectly displayed on the Backup Agents tab. 
• Under certain conditions management agent restarts every hour. 

• Network Extension IP addresses are not filtered by a reseller. Reseller can select IP addresses belonging to unmanaged companies. 
• Reseller can change his or her backup quota to “unlimited” when creating a managed company with “unlimited” quota.

• Only the first 10 000 products are displayed in the mapping area of the plugin. 
• Plugin services may consume excessive memory when there are a lot of tickets created in the ConnectWise Manage application.

• Platform type cannot be detected for old computers and is reported as “Oher.”

• Under certain conditions after installing a private hotfix Veeam.MBP.Service fails to connect to the existing database with the following error message ”Cannot change configuration database: Database version is invalid.” 
• Veeam.MBP.Service fails to start when managed backup agents have duplicate IDs (due to cloning operation) in the configuration database.

• “VM without backup” alarm is triggered for VMs that are migrated between vCenter Servers or are re-registered in the virtual infrastructure.

• Under certain conditions, the management agent may connect to VAC server without authentication.

• Computer renaming leads to duplicated values in the Protected Computers report.

• Under certain conditions, usage report for managed Veeam Backup & Replication servers may not be created within first ten days of a month.

Fixes included from previous patches:

• Cloud Copies counter on the Overview dashboard does not return any data.
• Backup agents managed by Veeam Backup & Replication report 0 restore points available in the backup policy drill down view. 

• Portal administrators can log in only when using a full domain name of the Veeam Availability Console server. 
• Users belonging to a domain user group which is added to a Veeam Availability Console security group cannot log in to the portal.
• Users belonging to a nested domain group cannot log in to the portal.

• Under certain conditions, Veeam.MBP.Service might be consuming excessive memory.
• Under certain conditions, data collection job fails to retrieve information from a Cloud Connect server that has lots of task sessions on cloud gateway servers. This results in displaying these tenants’ companies as deleted in the Veeam Availability Console UI.
• Tenant password changed in Veeam Cloud Connect is not synchronized with Veeam Availability Console.

• Office 365 and Gmail SMTP servers are not supported for notifications.  

• Inaccessible computers cannot be located when using CSV and IP discovery rule options.

• Full Access UI mode cannot be applied to a backup agent.  
• When using Select All checkbox on the Managed Backup Agents tab agent settings are applied to all computers of all managed companies regardless of the selected scope in the Company\Reseller filter.  
• Licensing attribute is not updated for managed backup agents which leads to license expiration on the backup agent.    
• Backup agent files are not validated when the installation is performed from a local folder without using a master management agent. This may result in a corrupted installation/upgrade of the backup agent. 

• Under certain conditions, management agents fail to upgrade with the following error message “The system cannot find the file specified.”

• Workstation and server backup counters in the Veeam Cloud Connect usage report are mixed up.
• Under certain conditions License usage report for Veeam Backup & Replication servers is not generated. 

• Under certain conditions, all VMs with a cloud copy which belong to different locations are reported as VMs from the default location in the invoice. 

• Querying tenant information with SetLinks parameter may take considerable time.
• The vMsBackudUpToCloud counter does not display data about VM and Agent backup copy jobs targeted to a cloud repository.  

• Cloud repository usage is not updated in ConnectWise Manage agreements when there are unknown files (not related to Veeam backups) in the repository. 
• Tickets state synchronization may stop working when triggering a mass-resolve operation in the ConnectWise Manage application. 

Solution

msiexec /update c:\VAC.ApplicationServer.x64_3.0.0.2762.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt

msiexec /update c:\VAC.WebUI.x64_3.0.0.2762.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACWebUI.txt

msiexec /update c:\VAC.ConnectorService.x64_1.0.1.610.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorService.txt

msiexec /update c:\VAC.ConnectorWebUI.x64_1.0.1.610.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorWebUI.txt

More Information

Challenge

Cause

Solution

1. Download archive with u4b_FIX_Licensing.Reporting.CC.GetInstancesInfo.sql file, extract and copy it to the SQL server, which hosts the Veeam Cloud Connect database or any other machine that can connect to the SQL instance in question.
2. Connect to the SQL instance by using Microsoft SQL Studio. When connecting, please provide valid credentials with full permissions.
3. Find your Veeam Cloud Connect database (its default name is VeeamBackup). Right-click it and select New Query.
4. Open file u4b_FIX_Licensing.Reporting.CC.GetInstancesInfo.sql by using the text editor, copy all its content and paste it to the query window from step 3.
5. Run the query by clicking Execute or pressing F5. Make sure that the query is executed successfully.

More Information

Challenge

Cause

Solution

• Additional Hypervisor support vSphere 6.7. VMware vSphere 4.0 and later (including vSphere 6, vSphere 6.5, vSphere 6.7, vSphere 6.7 U1, vSphere 6.7 U2 and vSphere 6.7 U3) 
• Monitoring SQL Transaction Log Backup Job. Veeam MP separately monitors SQL Transaction Log Backup jobs running inside backup jobs with the enabled application-aware processing option. For this purpose, Veeam MP includes a new Veeam SQL Transaction Log Backup Jobs view and Veeam Backup: SQL Transaction Log Job Status monitor.
• Improved performance of Morning Coffee Dashboards. In previous versions, Morning Coffee Dashboards tended to load slowly for large-scale environments. In Veeam MP 8.0 Update 6, the performance of Morning Coffee Dashboards has been significantly improved.
• A new metric for Veeam VMware Collector. Due to the Ops Mgr Health Service (Monitoring Agent Service) limitations that appear when a Veeam VMware Collector processes a large amount of data, it is required to distribute monitoring load among multiple Veeam VMware Collectors in large environments. To assess the monitoring load on Veeam VMware Collectors more precisely, Veeam MP provides a new % Object Monitoring Load metric.

• No monitoring for Hyper-V hosts that exceeded the license limit. Veeam MP license limits the number of Hyper-V hosts enabled for monitoring in Ops Mgr. Earlier, if the number of licensed Hyper-V hosts was exceeded and new hosts were added to the Ops Mgr infrastructure, Ops Mgr automatically stopped monitoring the old infrastructure and started monitoring the newly added hosts. In Veeam MP 8.0 Update 6, the issue was resolved, and Ops Mgr continues monitoring the old infrastructure.
• Ops Mgr event log shows excessive BackupCopyJobSessionFinished events. In previous versions, the Ops Mgr event log contained a large number of 3101 events caused by errors in the backup copy job status collection process. In Veeam MP 8.0 Update 6, the issue was resolved.

• Collector Autodeploy limitations. If you use the Collector Auto-Deployment feature to automatically deploy Veeam VMware Collectors on Management Servers, keep in mind that it will install clear 8.0 version without patches. When the installation completes, run the ISO\Update\VeeamMP80_Update6.exe installation file on each Veeam Collector to install patches.  
• Veeam MP for Hyper-V stops collecting storage metrics. If storage migrates to another volume, the storage performance collection will halt and Veeam MP will stop collecting the following metrics: Storage IOPS, Storage KB Total/sec, Storage Flush Count and Storage Error Count. Note that this issue does not affect migration between hosts. To work around the issue, restart the Ops Mgr agent after storage migration.

More Information

Challenge

Product Information:

Company name: Fujitsu
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000
Drive quantity, size, type: 10 - SAS HDD
Firmware version: V6.1A7120-SP03
General product family overview:

ETERNUS CS8000 is a datacenter solution for backup storage for mainframe and open systems. Its intelligent process automation and pooling of storage capacity reduces the TCO for complex backup environments by 40%. Unique scalability in capacity and performance makes ETERNUS CS8000 a viable solution, delivering ongoing cost savings.

Veeam testing configuration:

Veeam Build Number: 9.5.x

Job Settings:

Repository Settings:

More Information