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, Windows Server 1709 core edition 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).
• Microsoft Exchange Database Availability Groups should be protected by independent managed by backup server jobs with server type.
• When using Basic Availability Groups on Microsoft SQL Server 2016 Standard Edition, consider that secondary replica node cannot be backed up because the secondary node is not readable. See the following article for more information.
•  AlwaysOn Availability Groups based on multiple Failover Cluster Instances are not supported.
• 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

Challenge

Cause

Solution

New in This Release

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.

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 monitoring load on Veeam VMware Collectors more precisely, Veeam MP provides a new % Object Monitoring Load metric.

Resolved Issues

No monitoring for Hyper-V hosts that exceeded 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 backup copy job status collection process. In Veeam MP 8.0 Update 6, the issue was resolved.
 

Known Issues and Limitations

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.

Veeam MP stops collecting storage metrics
If a 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.

Challenge

Cause

Solution

For Veeam Management Pack 8.0 Update 5:

For Veeam Management Pack 8.0 Update 6:

More Information

Challenge

Cause

• Under certain conditions password in the SMTP server settings is reset.
• Veeam Management Portal Service cannot be started after installing Update 1.

• Management agent RAM consumption might significantly increase when running computer discovery process.

• After upgrading to Update 1, backup resources of the managed company cannot be adjusted when backup portal is running under heavy load. 

• Job name filtering is ignored in the job session state alarm.
• Storage snapshots are treated as a backup repository resulting in triggered alarms for the repository free space. 

• Cloud repository quota usage may report incorrect values when Veeam Agent backups are sent to the cloud repository via backup copy jobs. 
• Under certain conditions Cloud replication quota usage is not displayed on the dashboard when logged in using managed company user account
• Management agent re-installation results in losing collected data about protected VMs from the managed backup server. This affects Overview dashboard and Protected VMs report that display zero protected VMs.

• Under certain conditions ConnectWise Manage configurations cannot be created.
• Under certain conditions not all products created in ConnectWise Manage are accessible for mapping when using the billing function.  

Solution

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

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

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

More Information

Challenge

The following conditions are met:

1. Nutanix AOS is upgraded up to 5.8.0.1 within STS (Short Term Support) release branch;
2. Affinity rules are configured for the affected machines:

​​ 

Cause

Solution

Challenge

Two different issues are possible:
 
I. When trying to remove a protection domain containing the virtual machines, which are being backed up by Veeam Availability for Nutanix backup appliance, you may get the following message:

Specified protection domain has third-party backup snapshot(s)

II. You may start receiving the following warning in your cluster for a few protection domains or virtual machines:

Aged third-party backup snapshots present

Cause

Veeam Availability for Nutanix backup proxy appliance creates and keeps snapshots for each virtual machine in the backup job for the change block tracking purposes. It is not possible to remove a protection domain containing such snapshots. The default warning threshold for the third-party snapshots is equal to seven days, therefore you may start receiving warnings if any of the third-party snapshots is older than this threshold.

Solution

I. To resolve the first issue you need to delete the snapshots first. The snapshots will be automatically dismissed for the virtual machine once you remove the entire backup policy or stop processing the virtual machine by the backup job. You may follow the next steps to achieve the latter:

1. Go to the backup job settings in Veeam Availability for Nutanix backup proxy web interface;
2. Remove the virtual machines protected by this domain.

These actions will delete the third-party snapshots created by our backup proxy appliance for these machines and will allow you to remove the protection domain finally.

II. To resolve the second issue, you may increase the warning threshold in your cluster or change the schedule of your backup job to have it running within this threshold. You may also safely ignore the warning.

More Information

If the steps described above do not help, please contact Veeam Support for further investigation.

Challenge

Cause

Solution

More Information

Challenge

This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Agent for Microsoft Windows support case.

Solution

Gather logs using the four sections below. Once logs have been gathered, upload them to the FTP provided by the Veeam Support engineer. After the upload is completed you must notify the Veeam Support engineer.

If you need to use a secure FTP, this article contains secure FTP instructions.

All steps below are to be done from within the OS of the machine that is having an issue.

1. Veeam Agent guest logs

Navigate to and ZIP the contents of this folder:

C:\%programdata%\veeam\endpoint (This folder is hidden by default, please copy, paste provided path and achive this folder)

2. VSS Diagnostics

Run the following commands from administrative command prompt, then zip the resulting files.

vssadmin list writers > C:\vss_writers.log
vssadmin list providers > C:\vss_providers.log
vssadmin list shadows > C:\vss_shadows.log
vssadmin list shadowstorage > C:\vss_shadow_storage.log

Once submitted to Veeam Support, these log files can be deleted.

3. Event Logs

Export the logs in .evtx format, with Display Information.

Export the System and Application logs as follows:

1. Open Event Viewer (eventvwr.msc).
2. Locate the log to be exported in the left-hand column.
3. Right-click the name of the log and select Save All Events As.
4. Enter a file name that includes the log type and the server it was exported from.

   For example, when exporting the Application event log from a server named HV01, enter Application_HV01.

5. In Save as type, select Event Files.
6. Include the display information.

7. Be sure to include the LocaleMetaData folder when packaging the logs for upload.

4. File System Minifilter Diagnostics

Run the command below from an administrative command prompt. 

fltmc instances > C:\filter.log

Once submitted to Veeam Support, this log can be deleted.

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

To improve Veeam ONE SQL database performance, partitioning can be used. Note, that SQL Server Enterprise Edition is required to use partitioning. Partitioned tables and indexes are created by two scripts. Download them here.

NOTE: It is not recommended to use partitioning against Always On Availability Groups.

Before running the scripts, it is recommended to create a backup of Veeam ONE database. The scripts can be executed in any order. Before applying them, you will need to specify the following values:

1. Locate %UserName% parameter in the script and specify DB admin (sa or any domain account that has full control permissions to Veeam ONE DB).
2. Locate %Path% parameter and specify directory where database partitions will be created/stored.
3. If Veeam ONE database name is different from default, then change the name of the database (VeeamOne) in both scripts manually
4. Make sure SQL Agents are running before executing the scripts

After successful script execution you should see new functions and partition schemes: 



SQL Server agent will have two maintenance jobs created:



The directory specified for database partitions will have files like this:

VeeamOneLow_FG1.ndf
...
VeeamOneLow_FG13.ndf

VeeamOneMed_FG1.ndf
...
VeeamOneMed_FG15.ndf

More Information

Challenge

Solution

1. Launch the Veeam ONE Settings utility available under the following path:
   
   C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

2. In the menu on the left, select General, open the Database tab and make the necessary changes in the SQL Server section.
   

3. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for performance data collection.

4. Click the Test Connection button to check whether new configuration settings are correct.

5. Save changes.

6. Restart Veeam ONE Monitor Server service.

Then modify connection settings for Veeam ONE Reporter and Business View. To accomplish that, follow the next steps:

1. In the list of services, locate Veeam ONE Reporter Server service and choose to modify its properties. Open the Log On tab and specify the necessary account for the service in the Log on as section.

2. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for data collection.

3. Launch the Veeam ONE Settings utility available under the following path:
   
   C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

4. In the menu on the left, select General, open the Web Identity tab and make the necessary changes in the Web identity section.
   

5. Make sure this account has sufficient privileges on the Veeam ONE database on the SQL Server side, as it will be used for overall Web UI operation and reports creation.

6. Save changes.

7. Restart Veeam ONE Reporter Server service.

IMPORTANT!

• Should the database be connected to a different Veeam One installation, make sure there is no version\build mismatch. Otherwise, the application will fail.
• Starting with Veeam One v8, database partitioning became an option. If this option has been in place on the previously used SQL server, follow the steps described in this KB article to implement it on the new SQL server. 
• Starting with Veeam One v9.5, index defragmentation maintenance job for Veeam One database has been implemented. To create this job on the new SQL server download and run this script.

NOTE: 
Veeam One database partitioning jobs (VeeamOneSqlMaintenance_Med and VeeamOneSqlMaintenance_Med) and index defragmentation maintenance job (VeeamOne Maintenance Job) will remain intact on the old SQL server under SQL Server Agent > Jobs node and need to be removed manually.

More Information

Challenge

Cause

Solution

There are several ways of creating a backup of the database.

Using Veeam ONE Settings Utility (works for local SQL instances only)

To open Veeam ONE Settings utility use one of the options presented below:

• Open VeeamOneSettings.exe in C:\Program Files\Common Files\Veeam\Veeam ONE Settings

• Open the utility via Veeam ONE Monitor client > Options > Server Settings > Other Settings. Once you open the tab, you will find Support utility section. Click the Launch button.

1. Open Microsoft SQL Server Management Studio with administrator permissions (may need to be installed separately KB1761). 
2. Connect to the ServerName\Instance of the server that has the DB you want to back up.
3. Expand the Databases tab to get to the DB you want to back up. 
4. Right click the desired DB > Tasks > Back Up.
5. Set Backup Type to Full
6. Specify the database file destination by choosing Back up to Disk option > Add the destination path to save the database backup.
7. Go to Backup Options and set Set backup compression to Compress backup to reduce the database file size (the option is not mandatory).
8. Click OK to start the Backup process.

1. Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam database name. Alternatively, check the same via Veeam ONE Settings Utility. See Using Veeam ONE Settings Utility (above) for access instructions. 
2. Open Windows command line or PowerShell prompt and run the following command to create a backup file:
   for default instances:

   sqlcmd -S SqlServerName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"
   

   
   for named instances:

   sqlcmd -S SqlServerName\SqlInstanceName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

sqlcmd -U Username -S SqlServerName\SqlInstanceName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

Challenge

Cause

Solution

1. Stop all Veeam jobs and Veeam services
2. Copy these files and folders to an alternate location from the backup server and all backup proxies to have a backup:

   C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_6_5
   C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_6_7
   C:\Program Files (x86)\Veeam\Backup Transport\x64\VeeamAgent.exe

3. Replace the files on the backup server and all backup proxies listed in the previous step with those found in the hotfix package
4. Start all Veeam services

More Information

Challenge

Cause

Solution

There are several ways of creating a backup of the database.

Using Veeam ONE Settings Utility (works for local SQL instances only)

To open Veeam ONE Settings utility use one of the options presented below:

• Open VeeamOneSettings.exe in C:\Program Files\Common Files\Veeam\Veeam ONE Settings

• Open the utility via Veeam ONE Monitor client > Options > Server Settings > Other Settings. Once you open the tab, you will find Support utility section. Click the Launch button.

1. Open Microsoft SQL Server Management Studio with administrator permissions (may need to be installed separately KB1761). 
2. Connect to the ServerName\Instance of the server that has the DB you want to back up.
3. Expand the Databases tab to get to the DB you want to back up. 
4. Right click the desired DB > Tasks > Back Up.
5. Set Backup Type to Full
6. Specify the database file destination by choosing Back up to Disk option > Add the destination path to save the database backup.
7. Go to Backup Options and set Set backup compression to Compress backup to reduce the database file size (the option is not mandatory).
8. Click OK to start the Backup process.

1. Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam database name. Alternatively, check the same via Veeam ONE Settings Utility. See Using Veeam ONE Settings Utility (above) for access instructions. 
2. Open Windows command line or PowerShell prompt and run the following command to create a backup file:
   for default instances:

   sqlcmd -S SqlServerName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"
   

   
   for named instances:

   sqlcmd -S SqlServerName\SqlInstanceName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

sqlcmd -U Username -S SqlServerName\SqlInstanceName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

Challenge

You need to move Veeam Backup & Replication or Enterprise manager software and/or database to a new server.

Solution

Veeam Backup & Replication migration

Note: This section will refer to the server where Veeam Backup & Replication is installed prior to the move as the “old server”, and the location after the move as the “new server”.

There are two methods to perform Veeam Backup & Replication migration task:

• Migrate using Configuration Backup (recomended)
• Migrate using SQL Backup

Migrate using Configuration Backup

Perform the following steps on the old server:

1. Stop and disable all jobs.
2. Manually perform a configuration backup.
3. Close Veeam GUI and stop all Veeam Services.

Perform the following steps on the new server:

1. Install Veeam Backup & Replication with a brand new DB.
2. Apply the latest patch to Veeam Backup & Replication: http://www.veeam.com/patches.html
3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
4. Perform configuration backup restore:
   Note: It will be necessary to re-enter the password for every account during restore of non-encrypted configuration backups.
5. Run a test job to make sure everything moved correctly.

Migrate using SQL Backup

IMPORTANT: Use this option only if Configuration Backup is not available. If encryption was used on the previous installation, a newly installed backup server will not be able to decrypt such information if attached to the existing database, so any encrypted information will have to be supplied manually – existing encrypted backups have to be re-imported to provide the password.

Perform the following steps on the old server:

1. Stop and disable all jobs.
2. Close Veeam GUI and stop all Veeam Services.
3. Create backup of the SQL database. (http://vee.am/kb1471)
   
   To find out where the VeeamBackup database is located, open regedit on the old server and navigate to: [HKLM\SOFTWARE\Veeam\Veeam Backup and Replication]
    
   There you will find 3 dword values:
   • SqlServerName
   • SqlInstanceName
   • SqlDatabaseName

Perform the following steps on the new server:

1. Install Veeam Backup & Replication with a brand new DB.
2. Apply the latest patch to Veeam. http://www.veeam.com/patches.html
3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
4. Restore the Veeam database to the instance on the new server or on a SQL server which will host Veeam DB.
   Click (here) for information regarding restoring databases.
5. To associate Veeam with the restored database, please use the DBConfig Utility to change the Database that Veeam is connecting to.
6. Restart Veeam Services to apply the changes.
7. Open the Veeam console and using the “Manage Credentials” button from the main menu and check the passwords for every account to confirm they are up to date.
8. Run a test job to make sure everything moved correctly.

Enterprise manager migration

Note: This section describes how to move the Enterprise Manager (EM) database to a different SQL if the EM is installed separetly from the Backup & Replication.

1. Relocate VeeamBackupReporting DB to the new SQL server. See http://vee.am/kb1250
2. On the Veeam Backup & Replication server, open the following directory:
   C:\Program Files\Veeam\Backup and Replication\Backup
3. On the EM server, open the following directory:
   C:\Program Files\Veeam\Backup and Replication\Enterprise Manager
4. Сopy the following files from the VBR folder to the EM one:
   • Veeam.Backup.Configuration.Tool.exe
   • Veeam.Backup.DBConfig.exe
   • Veeam.Backup.Tool.Core.dll
   • Veeam.Backup.Backup.UI.dll
5. Run the copied ‘Veeam.Backup.DBConfig.exe’ as Administrator
6. Follow the steps described here to connect the EM to the new DB location: https://helpcenter.veeam.com/docs/backup/hyperv/using_dbconfig_utility.html?ver=95

More Information

In situations where physical local storage is used please see the following KB that details how to relocate Veeam Backup and Replication backup file locations: https://www.veeam.com/kb1729

For steps on migrating the Veeam database to another SQL Instance or Server, please refer to KB1250.

Challenge

Error: The remote server returned an error: (500) Internal Server Error.
Error: The remote server returned an error: (409) Conflict.

Cause

Solution

Challenge

Cause

Solution

Challenge

Product Information:

Product Family: Scality Ring
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: Scality Ring
Storage Category: Scale-out File and Object Storage
Drive quantity, size, type: 72 – 1TB 7200 RPM HDD, 6 – 500GB SSD
Storage configuration: ARC 9+3
Firmware version: 7.4.0.0
Connection protocol and speed: 10GbE
Additional support: All models and configurations of Scality Ring with specifications equivalent or greater than the above.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536
Veeam Settings:

• Repository Type: Shared Folder
• Deduplication: Yes
• Compression: Optimal
• Storage Optimization: Local Target
• Per-VM Backup Files: Yes
• Decompress before storing: No
• Align backup file blocks: No

Veeam Recommended Backup Copy Job Setting:

• Only full backup copy jobs are recommended to archive data to Scality
  "Read the entire restore point from source backup instead of synthesizing it from increments"

Vendor recommended configuration:

Hardware configuration used

• Storage Servers : 6x HPE Apollo 4530 Chassis, Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz, 128GB RAM
• Connector Server : 1x VM, 8x vCPU Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz, 32GB RAM

More Information

Company Information:

Company name: Scality
Company overview: Scality, the world leader in object and cloud storage, bridges the gap between application vendors and industry standard hardware providers to meet your cost-effective storage scale, durability, cloud and performance requirements.

Challenge

2018-01-08 03:00:10.3791 ERROR 5984 18 EXCEPTION: Permission to perform this operation was denied. 
2018-01-08 03:00:12.9585 ERROR 5984 18 EXCEPTION: Failed to RetrieveProperties: "". Insufficient privileges. You need to have 'System.Read' privilege on 'Folder:group-d1' object.

Cause

Solution

More Information

Challenge

This article describes the procedure of moving a Veeam Backup for Microsoft Office 365 v1.5 or v2.0 server installation to a new server.

Solution

Prerequisites:
The following prerequisites are required to carry out the procedure:

• The new server ready for VBO installation should have the same version of Windows
• If the repository is a network share, then the target server should have access to that share.
• If the repository is an iSCSI drive then it is important to disconnect it from the source first to avoid the two iSCSI initiators issue. Then connect it to the target server.
• Your license file should be available.

Procedure:
Veeam Backup for Microsoft Office 365 server migration.

1. Install the same version of Windows on the new server.
2. Install Veeam Backup for Office 365 on this new server.
3. Stop all the VBO services on the original site before moving any data.
4. Copy the repository data to the repository location on the new server.
5. Add the repository (from new location) to the new server.
6. Add the same organization on the new server.
7. Add a proxy from the original site (optional):

8. Create a backup job and point it to the added repository.
9. Run your job(s) to see if they succeed.
10. Run a test restore from a restore point created on the old VBO server to verify that you can recover.

 
Note: Restore points from the previous VBO server are available as soon as the organization is added to the console.

More Information