Challenge

Cause

Solution

More Information

Challenge

Cause

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. Download private fix for Veeam Backup & Replication 9.5 U4 and extract on the Veeam Backup Server. 
2. Right-click on the installation file and click "Run as administrator"
3. Go through the wizard to install private fix.
4. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.

More Information

Challenge

Product Information:

Company name: Spectra Logic
Product Family: Spectra Logic Tape Libraries
Status: Veeam Ready - Tape
Classification Description: Tape solution where available hardware features have been tested to work with Veeam.

Solution

Product Details:

Model number: Spectra Stack
Library Firmware Version 1.80
Drive firmware version: J4D1
Driver for tape drive: Microsoft LTO Tape Driver (Ver. 10.0.14393.1794)
Driver for media changer: Microsoft Medium Changer (Ver. 10.0.14393.0) (Veeam Option: Use native SCSI commands instead of Windows driver)
Media type tested: LTO-8 drive, LTO8 media (read/Write), LTO7 media (read/write)

General product family overview:
Spectra Stack Tape Library from Spectra Logic will meet your backup, archive and perpetual storage requirements. Designed to be easily installed, expanded and managed, the Spectra Stack is rated at a 100% duty cycle – meaning it is one of the only stackable libraries built to perform in a 24/7 environment. Spectra Stack starts as a 6U library with 1 to 6 LTO tape drives and 10 to 80 LTO tape slots. Each module of the Spectra Stack holds an additional 10 to 80 tape slots and 1 to 6 tape drives. Scalable from 10 to 560 tape slots and 1 to 42 tape drives, users can store more than 6.7PB (uncompressed) of data in a fully expanded Spectra Stack library. The Spectra Stack accommodates multiple tape generations with backwards compatibility, including M7 media which expands LTO-7 tape capacity when read by an LTO-8 drive.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2615

Challenge

This KB article was created to document how to create a case with Veeam Support via the customer portal.

Note:  In order to create a support case for Veeam Endpoint Backup, open the application and choose "Support" tab. 

In order to open a new case you must be designated as a Case Administrator. For more information on how to setup Case Administrators review  https://www.veeam.com/kb2211 .

Solution

Any information you can provide regarding the issue you are experiencing could have a significant impact on how fast the issue is diagnosed and resolved. You will be asked to provide the following information:

• Issue description, impact on your system and business operations, issue severity, and the exact text of error messages and diagnostic details.
• Steps to reproduce the problem, known workarounds
• Contact number where you can be reached
• Best time to reach you, and contact method (i.e. email/phone)

1. Go to https://my.veeam.com  (or directly to our customer portal  https://my.veeam.com/#/open-case/step-1 )
2. Enter your credentials and click Sign In

3. Click on "Open Case" button in the menu on the left side. Please note that you must be a Case Administrator or License Administrator to submit a case via the Portal. If you aren't currently a Case Administrator or License Administrator, please follow this guide to learn how to become one for your Account or call us if you have an urgent issue. 
4. On the right side of the page you need to fill in all the required details. Please remember to include the exact error message that is occurring. Screenshots inclusion can often help expedite resolution.

5. After clicking "Next" you will be taken to a page listing several KB articles that may be related to your issue. You may want to save them, but anyway, please click "Next" again.
6. On the next page you will be asked to add attachments to your case. It is on this page that you will attach the logs related to the issue, and any screenshots you have gathered.

   If the log package is large there will be an upload completion percentage listed in the status of the browser.
   

7. On the last page of case creation you will have an opportunity to review all details provided and provide specific contact details.

After you have created a case you will be contacted within the time set forth in the SLA agreement for the severity you specified.



To view your Production Licenses are discover what email is assigned as the License Administrator please click here: https://my.veeam.com/#/licenses/production

More Information

Challenge

Solution

──────────────────────────────────────────────────────────
1. Launch Multi-OS FLR
──────────────────────────────────────────────────────────
 
Launch the Multi-OS FLR, and wait for the backup browser to appear.

 
──────────────────────────────────────────────────────────
2. Get IP address of helper appliance (if DHCP was used)
──────────────────────────────────────────────────────────
 
Connect to the console of the VeeamFLR appliance that was created as part of the restore.
 
Log in using the user name root and the password set in the credentials section.
 
Note: In VMware environments you can also find the IP address of the VeeamFLR appliance on its summary tab.



──────────────────────────────────────────────────────────
Step 3. Connecting to the FLR appliance
──────────────────────────────────────────────────────────

Challenge

Cause

Solution

More Information

[[DOWNLOAD|DOWNLOAD NOW|https://www.veeam.com/send_license/virtualization-management-one-solution/]]
MD5: 9BFC92B616BA040A515B8737C19F7D65
SHA-1: 1E2F9030DE69E388932E9A6B67B8B4616D14739C
SHA-256: 1BD615507AE3F353CDD363B151081FF9B012010693CD4320D204B9545694603A

Should you have any questions, contact Veeam Support.

Challenge

Product Information:

Company name: NetApp
Product Family: FAS
Status: Veeam Ready - Integrated
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:

Model number: FAS2520
Drive quantity, size, type: 12 - Mix of Flash, SAS, NL-SAS
Firmware version: 8.1.0 - 8.3.2
Connection protocol and speed: 10Gb
Additional support: Any array running Data ONTAP with firmware versions above.

Whatever the size of your enterprise, you need powerful, flexible storage that manages growth and maximizes the long-term value of your IT investment. The NetApp® FAS series running ONTAP®software simplifies storage operations and builds a foundation for a data fabric that flows data seamlessly across flash, disk, and cloud. Its unified architecture supports a broader set of SAN and NAS workloads—with faster setup than other entry-class hybrid arrays.

Veeam testing configuration:

Veeam Build Number: 9.0.0.1715

Challenge

Cause

Solution

More Information

[[DOWNLOAD|DOWNLOAD NOW|https://www.veeam.com/send_license/virtualization-management-one-solution/]]
MD5: 9BFC92B616BA040A515B8737C19F7D65
SHA-1: 1E2F9030DE69E388932E9A6B67B8B4616D14739C
SHA-256: 1BD615507AE3F353CDD363B151081FF9B012010693CD4320D204B9545694603A

Should you have any questions, contact Veeam Support.

Challenge

The upgrade to Veeam Backup & Replication U4 fails with "Database version downgrade detected ... Reboot and restart the setup". You may find following error in the C:\ProgramData\Veeam\Setup\Temp\BackupSrvLog.log:

***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Database version has been incremented to <5186>
***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Executing version command (ContentType=[Schema], Version=<5186>)
***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Adding trusted hosts (InitialCatalog=[VeeamBackup], DatabaseVersion=<5186>)
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] declare @id uniqueidentifier;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] set @id = '52107791-e0ff-4538-a26e-4717962aef77';
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] declare @usn bigint;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] exec IncrementUsn @usn output;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] BEGIN
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] INSERT INTO [dbo].[Backup.Model.HostSshFingerprint]
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] (
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] [id], [network_name], [accepted_fingerprint], [current_fingerprint], [public_key], [agent_id], [network_name_hash], [last_update_time], [usn]
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] )
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] VALUES  
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] (
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] @id, '<IP Address>', '', '', '', '00000000-0000-0000-0000-000000000000', '', '<Day>/<Month>/Year <time>', @usn
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] )
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] END;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] GO
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM|ERROR] Conversion failed when converting date and/or time from character string. (System.Data.SqlClient.SqlException)

Cause

1. System time format uses a.m. and p.m. (in small symbols with dots)
2. Application-aware processing, or guest OS file indexing is enabled for a Linux machine.

Solution

1. Open Control Panel.
2. Click on the Clock, Language, and Region link.
3. Click on the Change date, time, or numbers formats link.
4. Under the Formats tab, click on the Additional settings... button
5. Under the Time tab, please set AM symbol: AM
6. Under the Time tab, please set PM symbol: PM
7. Click Apply.
8. Click OK.
9. Click Apply.
10. Click OK.

Challenge

Cause

• each guest VM should have the cluster feature installed
• all members of guest cluster should be on-line
• VHDSet shouldn't be used as Cluster Shared Volume (CSV)
• folder on CSV containing VHDSet files should have proper permissions settings
• guest operating system should be Windows 2016
• All VHDSet files must reside on CSV or SMB shares
• Microsoft supports legacy shared VHDX on Windows 2016, but this feature cannot be used like a workaround, because it cannot be included in application-consistent checkpoints, therefore Veeam doesn't support backup of such disks on Windows Server 2016

Solution

1. Determine the GUIDS of all VMs that use the folder. To do this, start PowerShell as administrator, and then run the following command: 

   get-vm | fl name, id

   sample output: 

   Name : BackupVM
   Id : d3599536-222a-4d6e-bb10-a6019c3f2b9b
   Name : BackupVM2
   Id : a0af7903-94b4-4a2c-b3b3-16050d5f80f

2. For each VM GUID, assign the VMMS process full control by running the following command:

   icacls <Folder with VHDS> /grant "NT VIRTUAL MACHINE\<VM GUID>":(OI)F

   Example:

   icacls "c:\ClusterStorage\Volume1\SharedClusterDisk” /grant "NT VIRTUAL MACHINE\a0af7903-94b4-4a2c-b3b3-16050d5f80f2:(OI)F"
   icacls "c:\ClusterStorage\Volume1\SharedClusterDisk” /grant "NT VIRTUAL MACHINE\d3599536-222a-4d6e-bb10-a6019c3f2b9b:(OI)F"

Challenge

The upgrade to Veeam Backup & Replication U4 fails with "Database version downgrade detected ... Reboot and restart the setup". You may find following error in the C:\ProgramData\Veeam\Setup\Temp\BackupSrvLog.log:

***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Database version has been incremented to <5186>
***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Executing version command (ContentType=[Schema], Version=<5186>)
***Veeam***  SRV: [31.01.2019 11:39:43]:<00000001> [VEEAM] Adding trusted hosts (InitialCatalog=[VeeamBackup], DatabaseVersion=<5186>)
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] declare @id uniqueidentifier;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] set @id = '52107791-e0ff-4538-a26e-4717962aef77';
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] declare @usn bigint;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] exec IncrementUsn @usn output;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] BEGIN
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] INSERT INTO [dbo].[Backup.Model.HostSshFingerprint]
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] (
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] [id], [network_name], [accepted_fingerprint], [current_fingerprint], [public_key], [agent_id], [network_name_hash], [last_update_time], [usn]
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] )
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] VALUES  
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] (
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] @id, '<IP Address>', '', '', '', '00000000-0000-0000-0000-000000000000', '', '<Day>/<Month>/Year <time>', @usn
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] )
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] END;
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM] [SQL|ERROR] GO
***Veeam***  SRV: [31.01.2019 11:39:44]:<00000001> [VEEAM|ERROR] Conversion failed when converting date and/or time from character string. (System.Data.SqlClient.SqlException)

Cause

1. System time format uses a.m. and p.m. (in small symbols with dots)
2. Application-aware processing, or guest OS file indexing is enabled for a Linux machine.

Solution

1. Open Control Panel.
2. Click on the Clock, Language, and Region link.
3. Click on the Change date, time, or numbers formats link.
4. Under the Formats tab, click on the Additional settings... button
5. Under the Time tab, please set AM symbol: AM
6. Under the Time tab, please set PM symbol: PM
7. Click Apply.
8. Click OK.
9. Click Apply.
10. Click OK.

Challenge

Cause

Solution

• Veeam Agents Backup Monitoring and Reporting. Monitoring and reporting for Veeam Agent for Windows and Veeam Agent for Linux
• Location Tag Support. Veeam ONE pre-defined reports and Monitor UI now support location tags for VMs, hosts, computers configured in Veeam Backup & Replication to observe data sovereignty.  
• Microsoft SQL Server 2017 Support. Veeam ONE now fully supports Microsoft SQL Server 2017.
• Microsoft Windows Server 2016 Version 1709 Support.  Veeam ONE now fully supports Microsoft Windows Server 2016, version 1709

• Veeam Agent Jobs Monitoring. Veeam ONE now monitors Veeam Agent backup jobs configured in Veeam Backup & Replication servers
• Veeam Agent Policies Monitoring. Veeam ONE now monitors Veeam Agent backup policies configured in Veeam Backup & Replication servers
• Enhanced Veeam Backup Data Collection. With Update 3, users will experience faster data collection from Veeam Backup & Replication servers, especially in large-scale deployments.
• Enhanced Hyper-V Data Collection. With Update 3 users will experience more stable data collection from Microsoft Hyper-V, especially in large-scale deployments.
• Veeam ONE Server Load Alarm. This alarm notifies user of high Veeam ONE server load to ensure stable workload.
• Performance Cache Path Setting. Veeam ONE now allows to change the performance cache location in Monitor Client UI.

• Protected Computers Report. This report lists all protected and unprotected computers running Veeam Agent.
• Data Sovereignty Overview. This report lists all protected objects, backups and replicas grouped by location tag
• Data Sovereignty Violations. This report shows potential data sovereignty violations for all protected objects.
• Location-Based Reporting.  Veeam ONE now provides an option to generate reports based on the location tags configured in Veeam Backup & Replication
• New VM Metrics. Veeam ONE now includes “VM Used Space per Datastore” and “VM Provisioned Space per Datastore” counters to identify how much space a VM and its corresponding files take up on the datastore.
• Enhanced Backup Custom Infrastructure Report. “Last Run Duration (sec)” has been added to the report parameters list.  

• Cloud Connect Inventory Report Enhancement.  This report now displays per-VM license key usage.
• Enhanced vCloud Director integration. Veeam ONE now caches user credentials to allow faster log-ins to the Monitor client. 
• Tenant Credentials Caching. This feature Veeam ONE saves permissions check time over infrastructure each time a tenant logs in.

• Performance graphs do not handle daylight saving time

• Under certain conditions tape server summary displays incorrect number of processed VMs.

• Guest OS disk usage alarm is reset to its default thresholds after product update.

• Some performance-based alarms ignore custom “Time period” values.
• CSV datastores with the same name managed by the same SCVMM server display incorrect values.

• Report scheduling does not handle daylight saving time
• Several reports miss data in Advanced Scalability mode
• Direct links to Veeam ONE dashboards and reports integrated to 3rd party monitoring and reporting applications stop working after upgrade.
• Deleted VMs are not considered in performance-based chargeback reports

• Under certain conditions Cloud Connect User Report (Backup) shows incorrect number of Days Left to Reach Quota.
• VM Change Rate History report shows not accurate number of incremental backups
• Latest Backup Job Status report treats job retries as individual job runs

• Capacity Planning report shows incorrect datastore usage

• Some reports show wrong vCPU count for VMs using NUMA
• Under certain conditions Host Resource Usage Chargeback report uses VM Disk size in TB instead of GB what makes VM cost calculation results incorrect
   

• Tags are not collected from distributed vCenter Server 6.x when Platform Service Controller is installed as a dedicated server
• Under certain conditions VMs with long VM Folder path cannot be categorized

• Dashboard scheduling doesn’t work in distributed Veeam ONE installation when security certificates are missing from the server with Veeam ONE Web UI. To resolve this problem, import security certificates that are installed to Veeam ONE server to the server where Veeam ONE Web UI is deployed.
• Performance collection of CSV under Hyper-V cluster stops after volume is renamed. To resolve this problem, restart Veeam ONE server service.
• Data Sovereignty Violations report requires Microsoft SQL Server 2012 or newer.

More Information

Challenge

• Instant VM Recovery
• Windows and Linux File Level Recovery
• Cloud Tier
• Cloud Mobility
• DataLabs
• SureBackup
• Staged Restore
• Universal Restore (U-AIR)
• On-Demand Sandbox
• Secure Restore
• Backup and Backup Copy Jobs when configured with one of the following:
• Health Check
• Compact processing
• Synthetic Fulls
• Forever Forward Incremental (Merges)
• Reverse Incremental
• Backup to Tape Jobs, specifically when performed with synthesized fulls
• Replication when performed from backup as a source
• Backup Copy Job processing on source side

Cause

Solution

• Best Practices for HPE
• Best Practices for Exagrid
• Best Practices for Quantum

Challenge

If a Virtual Machine's MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would receive the error "Object "vmname" is not found". Please see KB1299 for more details.

This utility is designed to assist in re-mapping the MoRef ID's of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that backup incremental chains remain intact, after an inventory change in VMware vSphere vCenter. Do not run any jobs before using the migration tool otherwise, the migration process won't be possible.

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.

This tool cannot fix jobs targeting a Cloud Connect repository. You must perform an Active Full backup.

Important! If you are migrating to a 6.5U2 VCSA, VMware has a new migration utility, which could preserve existing VM MoRef IDs:
https://blogs.vmware.com/vsphere/2016/09/vcenter-server-migration-tool-vsphere-6-0-update-2m.html
https://blogs.vmware.com/vsphere/2017/01/vcenter-server-appliance-6-5-migration-walkthrough.html
This VMware utility only works for a 5.5 VC to a 6.5U2 VCSA!

Cause

Veeam Backup & Replication tracks Virtual Machines in its jobs by a Managed Object Reference ID (MoRef), which will change when moved to another vCenter, or removed and re-added to inventory.

Solution

Please download this bundle: tool and instructions.
Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database.

Note:

• The utility will work only with a source vCenter migration. If Replication target vCenter is changed, you will need to manually map source VMs to their replicas.
• If for some reason you have already added the new vCenter or ran any jobs which will have added new Ref-IDs to the database, you can roll the Veeam Backup & Replication database back using the Configuration Restore function.

If you use the VMware provided VCSA Migration tool, you will need to remove and re-add VMs to jobs manually through the new VCSA after adding it to Veeam.

VMware highly recommends migrating to a VCSA, as they are phasing out the Windows based vCenter.
https://blogs.vmware.com/vsphere/2017/08/farewell-vcenter-server-windows.html

More Information

Challenge

Cause

Solution

Important! Please note that this process will automatically restart the Veeam Backup Service.

Ensure no Backup/Replication Jobs or Restores are running before applying these steps.

The current workaround is manual generation of a new certificate (if a self-signed certificate is used) as described here.

If you use your own certificates, you will need to import renewed certificates:

Please note that if you do not apply the above fix, after one month you will begin to see errors with Veeam's Agent Management functionality, as well as with granular restores of any type, so it is recommended that you schedule a maintenance window at your earliest convenience to apply the fix. If you were not able to apply the fix and issues appeared, schedule a Backup & Replication server reboot to clean old certificate cache, it will also help to sort these issues out.

The issue is fixed in Veeam Backup and Replication 9.5 Update 4.

 

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

Solution

• <mydataboxno>.microsoftdatabox.com;
• blob.<mydataboxno>.microsoftdatabox.com;
• <storageaccountname>.blob.<mydataboxno>.microsoftdatabox.com