Challenge

IMPORTANT NOTE: Veeam quality assurance identified that after upgrading to Veeam Backup for Microsoft Office 365 version 4c (build 4.0.1.519) from versions 4.0, 4a, or 4b full backup sync may be performed instead of incremental sync. Build 4.0.1.519 is now recalled and a corresponding fix is expected to be available soon.
 

Cause

• version 3.0 (builds 3.0.0.422 – 3.0.0.480)
• version 4.0 (build 4.0.0.1345)
• version 4a (builds 4.0.0.1553 – 4.0.0.1580)
• version 4b (builds 4.0.0.2516 – 4.0.0.2549)

What's New

• Support for Office 365 tenants using modern app-only authentication with disabled legacy protocols. In the new mode, VBO performs all its backup and restore operations using an Azure AD application instead of user credentials. This new mode addresses the needs of customers using Microsoft Security Defaults in their Office 365 tenant organizations.
• Support for leveraging auxiliary backup applications to enable faster SharePoint Online and OneDrive for Business backups for Office 365 tenants using modern app-only authentication.

Enhancements

• The built-in product auto upgrade feature now automatically installs the new and missing Veeam Explorers that come as part of Veeam Backup for Microsoft Office 365 package, as well as the newest patches for Veeam Backup for Microsoft Office 365.
• Enhanced UI for Backup Accounts Manager allowing for easier selection of a security group and managing dozens of accounts.

Considerations and limitations

When protecting Office 365 tenants using modern app-only authentication, consider the following:

• Discovery Search and Public Folder mailboxes are not supported.
• Dynamic Distribution groups are not supported.
• The type property for shared and resource/equipment mailboxes cannot be resolved. Such mailboxes will be available for backup with a general ‘User’ type.
• SharePoint Web Parts can only backed up if their ‘exportmode’ property is enabled. Non exportable Web Parts are not supported.
• OneNote restore is not supported.
• SharePoint Web Part customized template cannot be preserved upon a restore. All Web Parts will be restored with the default template.
• The ‘Allow multiple responses’ setting in survey lists within team modern sites is not preserved upon a restore.
• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

IMPORTANT NOTE:

• standalone installations of Veeam Backup for Microsoft Office 365
  • version 3.0 (builds 3.0.0.422 — 3.0.0.480)
  • version 4.0 (build 4.0.0.1345)
  • version 4a (builds 4.0.0.1553 (see KB3035) and 4.0.0.1580 (see KB3089))
  • version 4b (builds 4.0.0.2516 (see KB3065) and 4.0.0.2549 (see KB3119))
• installations on top of Veeam Backup & Replication v10 and Veeam Cloud Connect v10

• Veeam Backup & Replication 9.5 Update 4, 4a or 4b
• Veeam Cloud Connect 9.5 Update 4, 4a or 4b

Resolved Issues

General:

• After an upgrade from Veeam Backup for Microsoft Office 365 version 4a to version 4b synchronization between the Proxy and Archiver services fails because of object storage repository status check.
• Applying retention policy fails with the “JetError -1605, JET_errKeyDuplicate, Illegal duplicate key”.
• After a username has been changed in Office 365, a new username is not reflected in the output of the “Get-VBOLicensedUser” PowerShell cmdlet and the built-in License Overview report.
• After existing backup data migration to an object storage repository, old restore points are missing some of the SharePoint data.
• Deleting an organization with configured auxiliary backup accounts from the Veeam Backup for Microsoft Office 365 scope fails with the "Organization with the same name already exists" or “JetError -1809, JET_errPermissionDenied” error.
• Backup data migration from a local backup repository to an Azure Blob storage repository completes with the “Failed to move all objects” warning.
• Under certain conditions, executing of the “Disable-VBOJob” PowerShell cmdlet hangs.
• Cohesity S3 object storage cannot be added as an object storage repository

Backup:

• When downloading attachments during a SharePoint Online site backup, job fails with the “Failed to backup list: File not found in the database” error.
• Backup of a OneDrive account fails with the "Item has been changed during backup" error.
• Under certain conditions, backup of an archive mailbox in a hybrid organization setup fails with the “ErrorInvalidUserPrincipalName” error.

• In the BaaS setup, SharePoint site list explore from a tenant side fails with the "Object synchronization method was called from an unsynchronized block of code" error.
• Under certain conditions, files are skipped during SharePoint Online restore to the original location.
• Under certain conditions, folders cannot be created during SharePoint Online restore to the original location.
• During SharePoint Online restore using REST API, the "GET Libraries" request fails with the "Invalid root web permissions" error.
• OneNote items export fails with the "Failed to create cab file" error.
• SharePoint Online document restore fails with the “A file or folder with the name already exists” and “User ID login not found on SharePoint server” errors, if a folder containing this document has been moved to another location.
• OneDrive export completes with the “No items were saved” message.
• An attempt to start a restore session via REST API fails after numerous attempts to get the new access token for a specific user account.
• Under certain conditions, export of an Exchange item to a PST or MSG fails with the “Value cannot be null” error.

Solution

• Download the ZIP archive: VeeamBackupOffice365_4.0.1.519.zip.
• Run the Veeam.Backup365_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Backup for Microsoft Office 365.
• Run the VeeamExplorerForExchange_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft Exchange.
• Run the VeeamExplorerForSharePoint_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft SharePoint. Note that Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint and will be installed automatically.

Challenge

Cause

az account list output table

For more information on isolation and access control in Azure Active Directory, see Microsoft Docs. For more information on what the Azure CLI is, how to install and use it, see Microsoft Docs.

Solution

Challenge

[08.04.2020 8:26:46.680] <   724> vdl| [vddk] 2020-04-08T20:26:46.680-07:00 error -[00724] [Originator@6876 sub=Default] SSL Async Handshake Timeout : Read timeout after approximately 25000ms. Closing stream <SSL(<io_obj p:0x000001ef0b15eb68, h:1100, <TCP 'x.x.x.x : 49746'>, <TCP 'x.x.x.x : 443'>>)>
[08.04.2020 8:26:51.668] <  5412> vdl| [vddk] 2020-04-08T20:26:51.668-07:00 error -[05412] [Originator@6876 sub=IO] HandshakeCb; <SSL(<io_obj p:0x000001ef0b15eb68, h:-1, <TCP 'x.x.x.x : 49746'>, <TCP 'x.x.x.x : 443'> FD Closed>)>; error: class Vmacore::Ssl::SSLHandshakeTimeoutException(SSL Exception: The file handle supplied is not valid)

Cause

Solution

Challenge

This article describes list of VMware vSphere versions currently supported by Veeam Backup & Replication.

IMPORTANT: It is recommended to always use the latest Veeam version to ensure modern platforms support and security compliance.

Solution

More Information

Challenge

Cause

Solution

• Managed by Agent backup policies do not respect the retention policy setting for Microsoft Windows machines, always forcing it to 7 regardless of the value specified.

• Added support for Cape Town and Milan data center regions in all related functionality.

• Failed GFS full backup transform may result in the job to start failing with the “Failed to process method {Transform.Patch}: There is an item with the specified name and another type” error.

• Under certain circumstances, backup jobs may fail with the “Cannot retrieve physical extents for connecting iSCSI target IQN {0} on proxy IQN {1}” error.

• In the environments where the Network Extension Appliance has the same name as the corresponding Tenant, deleting the appliance will also remove tenant’s replicas.
• Under certain circumstances, task slots may not be released at the end of the job session, resulting in various issues due to lack of available task slots.
• Cloud Connect Replication fails with the “Cannot find an available target” error in vCloud Director environments with multiple clusters due to not searching all available vDC pools for the required vOrg pool.
• Using the UseCachedSshConnections registry value may result in jobs to stop running due to already closed connection erroneously cached. This issue may result in various errors, typically “The session is not open” error.
• Opening the Tenants view takes a long time.

• High CPU consumption on the SQL Server hosting the configuration database caused by the AggregateSqlPointsInfo stored procedure during transaction log backup.

• Mounting a restore point with the dynamic disk fails with the “Invalid secondary GPT partition entry array checksum” error.
• In some environments, mounting a restore point for file-level recovery may fail with the “Invalid secondary GPT header signature” error.

• VSS snapshot fails to be created with the “Access is denied” error for SMB file shares hosted on some NAS devices due to lack of impersonation.
• Backup of different files shares from the same server or NAS may fail with the “Failed to create a VSS snapshot” whenever VSS snapshot creation calls overlap.

• Resource scheduler may experience significant delays issuing the backup infrastructure resources in environments with a large number of agent-based, application plug-in based or host-based backups (with per-VM backup file chains disabled) are stored in a scale-out backup repository.

• High backup server CPU consumption by the Veeam Backup Service in large environments while the user interface is open and no jobs are active.
• High backup server RAM consumption by the UI Service process and slow performance of historical sessions view in environments with very large number of sessions.
• Opening an existing VMware backup job’s settings takes a long time for jobs using a scale-out backup repository with a large number of extents as the target.

• Invalid tenant workloads count is returned by the backup server’s WMI API, resulting in Veeam Service Provider Console to issue false warnings.

• WAN accelerator may deadlock while transferring an increment with large contiguous set of zeroed segments, making the data transfer appear to slow down dramatically.

More Information

Challenge

IMPORTANT NOTE: Veeam quality assurance identified that after upgrading to Veeam Backup for Microsoft Office 365 version 4c (build 4.0.1.519) from versions 4.0, 4a, or 4b full backup sync may be performed instead of incremental sync. Build 4.0.1.519 is now recalled and a corresponding fix is expected to be available soon.
 

Cause

• version 3.0 (builds 3.0.0.422 – 3.0.0.480)
• version 4.0 (build 4.0.0.1345)
• version 4a (builds 4.0.0.1553 – 4.0.0.1580)
• version 4b (builds 4.0.0.2516 – 4.0.0.2549)

What's New

• Support for Office 365 tenants using modern app-only authentication with disabled legacy protocols. In the new mode, VBO performs all its backup and restore operations using an Azure AD application instead of user credentials. This new mode addresses the needs of customers using Microsoft Security Defaults in their Office 365 tenant organizations.
• Support for leveraging auxiliary backup applications to enable faster SharePoint Online and OneDrive for Business backups for Office 365 tenants using modern app-only authentication.

Enhancements

• The built-in product auto upgrade feature now automatically installs the new and missing Veeam Explorers that come as part of Veeam Backup for Microsoft Office 365 package, as well as the newest patches for Veeam Backup for Microsoft Office 365.
• Enhanced UI for Backup Accounts Manager allowing for easier selection of a security group and managing dozens of accounts.

Considerations and limitations

When protecting Office 365 tenants using modern app-only authentication, consider the following:

• Discovery Search and Public Folder mailboxes are not supported.
• Dynamic Distribution groups are not supported.
• The type property for shared and resource/equipment mailboxes cannot be resolved. Such mailboxes will be available for backup with a general ‘User’ type.
• SharePoint Web Parts can only backed up if their ‘exportmode’ property is enabled. Non exportable Web Parts are not supported.
• OneNote restore is not supported.
• SharePoint Web Part customized template cannot be preserved upon a restore. All Web Parts will be restored with the default template.
• The ‘Allow multiple responses’ setting in survey lists within team modern sites is not preserved upon a restore.
• The ‘Measure-VBOOrganizationFullBackupSize’ cmdlet is not supported.

IMPORTANT NOTE:

• standalone installations of Veeam Backup for Microsoft Office 365
  • version 3.0 (builds 3.0.0.422 — 3.0.0.480)
  • version 4.0 (build 4.0.0.1345)
  • version 4a (builds 4.0.0.1553 (see KB3035) and 4.0.0.1580 (see KB3089))
  • version 4b (builds 4.0.0.2516 (see KB3065) and 4.0.0.2549 (see KB3119))
• installations on top of Veeam Backup & Replication v10 and Veeam Cloud Connect v10

• Veeam Backup & Replication 9.5 Update 4, 4a or 4b
• Veeam Cloud Connect 9.5 Update 4, 4a or 4b

Resolved Issues

General:

• After an upgrade from Veeam Backup for Microsoft Office 365 version 4a to version 4b synchronization between the Proxy and Archiver services fails because of object storage repository status check.
• Applying retention policy fails with the “JetError -1605, JET_errKeyDuplicate, Illegal duplicate key”.
• After a username has been changed in Office 365, a new username is not reflected in the output of the “Get-VBOLicensedUser” PowerShell cmdlet and the built-in License Overview report.
• After existing backup data migration to an object storage repository, old restore points are missing some of the SharePoint data.
• Deleting an organization with configured auxiliary backup accounts from the Veeam Backup for Microsoft Office 365 scope fails with the "Organization with the same name already exists" or “JetError -1809, JET_errPermissionDenied” error.
• Backup data migration from a local backup repository to an Azure Blob storage repository completes with the “Failed to move all objects” warning.
• Under certain conditions, executing of the “Disable-VBOJob” PowerShell cmdlet hangs.
• Cohesity S3 object storage cannot be added as an object storage repository

Backup:

• When downloading attachments during a SharePoint Online site backup, job fails with the “Failed to backup list: File not found in the database” error.
• Backup of a OneDrive account fails with the "Item has been changed during backup" error.
• Under certain conditions, backup of an archive mailbox in a hybrid organization setup fails with the “ErrorInvalidUserPrincipalName” error.

• In the BaaS setup, SharePoint site list explore from a tenant side fails with the "Object synchronization method was called from an unsynchronized block of code" error.
• Under certain conditions, files are skipped during SharePoint Online restore to the original location.
• Under certain conditions, folders cannot be created during SharePoint Online restore to the original location.
• During SharePoint Online restore using REST API, the "GET Libraries" request fails with the "Invalid root web permissions" error.
• OneNote items export fails with the "Failed to create cab file" error.
• SharePoint Online document restore fails with the “A file or folder with the name already exists” and “User ID login not found on SharePoint server” errors, if a folder containing this document has been moved to another location.
• OneDrive export completes with the “No items were saved” message.
• An attempt to start a restore session via REST API fails after numerous attempts to get the new access token for a specific user account.
• Under certain conditions, export of an Exchange item to a PST or MSG fails with the “Value cannot be null” error.

Solution

• Download the ZIP archive: VeeamBackupOffice365_4.0.1.519.zip.
• Run the Veeam.Backup365_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Backup for Microsoft Office 365.
• Run the VeeamExplorerForExchange_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft Exchange.
• Run the VeeamExplorerForSharePoint_4.0.1.519.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft SharePoint. Note that Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint and will be installed automatically.

Challenge

[08.04.2020 8:26:46.680] <   724> vdl| [vddk] 2020-04-08T20:26:46.680-07:00 error -[00724] [Originator@6876 sub=Default] SSL Async Handshake Timeout : Read timeout after approximately 25000ms. Closing stream <SSL(<io_obj p:0x000001ef0b15eb68, h:1100, <TCP 'x.x.x.x : 49746'>, <TCP 'x.x.x.x : 443'>>)>
[08.04.2020 8:26:51.668] <  5412> vdl| [vddk] 2020-04-08T20:26:51.668-07:00 error -[05412] [Originator@6876 sub=IO] HandshakeCb; <SSL(<io_obj p:0x000001ef0b15eb68, h:-1, <TCP 'x.x.x.x : 49746'>, <TCP 'x.x.x.x : 443'> FD Closed>)>; error: class Vmacore::Ssl::SSLHandshakeTimeoutException(SSL Exception: The file handle supplied is not valid)

Cause

Solution

Challenge

Solution

Recover Through the Appliance

1. Go to the Protected Data page and find the Veeam Backup for Microsoft Azure virtual machine.
2. Select the Veeam Backup for Microsoft Azure virtual machine and click Restore > VM Restore on the toolbar.
3. Navigate through the restore wizard and confirm the operation.
   Note that a restore to the original location is not available in this scenario because the original VM must be shut down before switching the disks.
   
4. After the restore is complete, shut down the old Veeam Backup for Microsoft Azure instance.
5. Set up the network settings for the restored virtual machine.
   Veeam Backup for Microsoft Azure does not restore the public IP and DNS names. If you want to use the same IP or domain, both must be configured anew.
6. Remove the old Veeam Backup for Microsoft Azure instance from Azure.

Manual Restore

1. After the restore is complete, shut down the old Veeam Backup for Microsoft Azure instance.
2. Tag the restored virtual machine with the same tags as the old Veeam Backup for Microsoft Azure instance.
3. Set up the network settings for the restored virtual machine.
4. Veeam Backup for Microsoft Azure does not restore the public IP and DNS names. If you want to use the same IP or domain, both must be configured anew.
5. Remove the old Veeam Backup for Microsoft Azure instance from Azure.

Challenge

Cause

Last-minute kernel patches for Red Hat Enterprise Linux and its derivatives may cause Veeam Agent for Linux to go unstable (veeam.com/kb2786).

Solution

Veeam Agent for Linux v4:

 
Veeam Agent for Linux v3:

Challenge

Cause

Solution

More Information

Challenge

Product Information:

Company name: Zadara
Product Family: VPSA (Virtual Private Storage Array)
Status: Veeam Ready – Object & Veeam Ready – Object with Immutability
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier and object storage immutability features.

Solution

Product Details:

Model number: VPSA Premium Object Storage
Storage Category: Software Defined Object Storage
Drive quantity, size, type: 72 – 10TB SATA
Storage configuration: 2-way mirror
Firmware version: 20.01
Connection protocol and speed: 40 GbE
Additional support: All models and configurations of VPSA for S3 compatible storage with specifications equivalent or greater than the above. (remove this section if cloud-based solution)

General product family overview:
VPSA Object Storage is Zadara’s object storage service. It is provided on Zadara clouds, side by side with the virtual private storage array that provides block and file storage services.

These are the key properties of Object Storage:

• Unlimited scalability (scaling out) in both capacity and total objects - simply keep adding drives
• User-defined object’s metadata
• 2- or 3-way distributed data protection
• Supports both S3 and Swift REST API
• Comprehensive usage reporting and metering
• Multi-tenancy at both the object storage and account levels

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Challenge

VMware backup jobs fail after update 3, whereas prior to update they have been working.

• The jobs are using Network transport mode
• Source Proxy is Windows 2008SP1/Windows 2008R2

The error message for all jobs in the GUI looks like this one:

Processing VM_Name Error: Failed to open VDDK disk [datastore] VM_Name/VM_Name.vmdk] ( is read-only mode - [true] ) Logon attempt with parameters [VC/ESX: [hosname.local];Port: 443;Login: [administrator@vsphere.local];VMX Spec: [moref=vm-ref];Snapshot mor: [snapshot-ref];Transports: [nbd];Read Only: [true] failed because of the following errors: Failed to open disk for read. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.

Solution

This issue is related to some of the dll files in the Windows ZIP file for VDDK 6.5 with incorrect manifests, making them depend on two Visual C++ 9.0 versions, both 9.0.32709.4148 and 9.0.21022.8. This causes a failure to load vixDiskLibVim.dll with error code = 0x36b1, which means side-by-side configuration is incorrect.

Workaround

Edit failing jobs and configure them to use a proxy running Windows 2012/2012R2/2016 proxy.

Note: The steps to Verify and Correct this issue below are to be performed on the proxy which was used by the failing job.

Verify issue matches this KB:

1. On the source proxy navigate to Veeam logs location (default %ProgramData%\Veeam\Backup)
2. Open the folder that matches the name of the failing Job.
3. Find the log file matching the nomenclature Agent.Job_Name.Source.VM_Name.vmdk.log.
4. Open the file with any text editor and search for:
   VDDK error: 16053 (One or more required subsystems failed to initialize)
   
   Example snippet:

   [DD.MM.YYYY HH:MM:SS] < 12620> cli| ERR |Command 'Open' has failed.
   [DD.MM.YYYY HH:MM:SS] < 12620> cli| >>|VDDK error: 16053 (One or more required subsystems failed to initialize). Value: 0x0000000000003eb5
   [DD.MM.YYYY HH:MM:SS] < 12620> cli| >>|--tr:Failed to open virtual disk [Test_Vol1_LUN3] TEST/TEST.vmdk (flags: 4)
   [DD.MM.YYYY HH:MM:SS] < 12620> cli| >>|An exception was thrown from thread [12620].

5. To further confirm, open event viewer and in Application logs search, Source: 'SideBySide' Event ID: '35'
   ​example event:
   

How to correct this issue:

1. Open Programs and Features and verify that Microsoft Visual C++ 2008 Redistributable Package (x64) is not installed.
2. Download and install Microsoft Visual C++ 2008 Redistributable Package (x64) (https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=15336)
3. Ensure that no other jobs are running, and reboot the proxy.
4. Retry failed jobs.

More Information

Note: This KB article only applies if VDDK error 16053 is found in the logs. If this error is not found in the logs, please contact Veeam support for further troubleshooting.

See also: https://vdc-download.vmware.com/vmwb-repository/dcr-public/2ab18705-4960-45f8-88a5-830c5a308d9e/23ca4c1c-821f-4093-91f6-e38912977e24/vsphere-vddk-651-release-notes.html

Challenge

Product Information:

Company name: Wasabi Technologies
Product Family: Wasabi Hot Cloud Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Object Storage Tiers: Wasabi Hot Cloud Storage (Wasabi currently has one tier of storage)
Object Storage Service Description: Wasabi is a S3-compatible public cloud object storage service

General product family overview:
Wasabi is a cloud-based object storage service for a broad range of applications and use cases. Wasabi is designed for individuals and organizations that require a high-performance, reliable, and secure data storage infrastructure at minimal cost.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Challenge

Cause

Resolved Issues

• After upgrading Veeam Backup for Microsoft Office 365 from versions 4.0, 4a or 4b to version 4c, a full backup sync may be performed instead of an incremental sync.
• OneDrive and SharePoint personal sites backup completes with the “Cannot change WebPart ExportMode to ‘All’. WebPart will be skipped” warning.
• In organizations added with basic authentication, a user with a mailbox placed on Litigation Hold continues to consume the license after their Office 365 license has been removed.
• SharePoint site migration to an object storage repository may fail with the “File '%ID%' version '%number%' has already been committed” error.
• Change token is not preserved for a SharePoint list which processing completed with the “The changeToken refers to a time before the start of the current change log” error.

Solution

• Download VBO4с-KB3194.msp 
• Execute VBO4с-KB3194.msp as administrator on the Veeam Backup for Microsoft Office 365 server. 

More Information

MD5: 54b4e6ceb4f97257071388adaa130aa0
SHA-1: eef5d6278af4a63e1a67acc8960f031cc0778aa2

Challenge

Solution

Challenge

[15.06.2020 11:00:00] <01> Error    Authentication failed because the remote party has closed the transport stream. (System.IO.IOException)
[15.06.2020 11:00:00] <01> Error       at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
...
[15.06.2020 11:00:00] <01> Error       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
[15.06.2020 11:00:00] <01> Error       at Veeam.Backup.Core.CSocketInvokerClient.InvokeImpl(TcpClient client, CSocketInvokerParams args, Int32 threadId)
[15.06.2020 11:00:00] <01> Error       at Veeam.Backup.Core.CSocketInvokerClient.TryInvoke(CSocketInvokerParams invokerParams)

[15.06.202011:00:00] <234> Error    A call to SSPI failed, see inner exception. (System.Security.Authentication.AuthenticationException)
[15.06.202011:00:00] <234> Error       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
[15.06.202011:00:00] <234> Error       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
...
[15.06.202011:00:00] <234> Error       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
[15.06.202011:00:00] <234> Error       at Veeam.Backup.CloudService.CSocketInvokerServerProtocol.InvokeImpl(SPerfomanceCounterInvokerInfo& perfCounterInfo)
[15.06.202011:00:00] <234> Error       at Veeam.Backup.CloudService.CCloudPerfomanceCountersCollector.CollectInvokerPerfomanceCounter(PerfomanceCounterAction invoker)
[15.06.202011:00:00] <234> Error       at Veeam.Backup.CloudService.CSocketInvokerServerProtocol.Invoke()
[15.06.202011:00:00] <234> Error    The specified data could not be decrypted (System.ComponentModel.Win32Exception)

Cause

Solution

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. Choose a Case Type. Technical is for Break-fix issues or any kind of technical questions related to Veeam products. Licensing covers any licensing or related questions and General Inquiry is for feedback or issues related Veeam websites and services, not products. 
5. On the left 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.

6. After clicking "Next" you will be taken to a page listing several KB articles that may be related to your issue. To continue with case creation, please click "Next" again.
7. On the next page you will be asked to add attachments to your case. It is imperative that you provide diagnostic logs when creating a case so that Veeam Support may best assist you.
   •Select the bucket relative to your region.
   •For cases relating to Veeam Backup & Replication please review this article for details on how to collect logs: https://www.veeam.com/kb1832
   •For cases related to Veeam Agent for Windows please review this article for details on how to collect logs: https://www.veeam.com/kb2404
8. On the last page of case creation you will have an opportunity to review all details provided and provide specific contact details. If you have a direct number you can reached at please consider adding it at this point.

After you have created a case you will be contacted within the time set forth in the SLA agreement for the severity you specified.
Veeam's severity system operates similar to the DEFCON system, lower number=high priority.



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

More Information

Challenge

Product Information:

Company name: FAST LTA, AG
Product Family: Silent Brick System
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: FAST LTA - Silent Brick FLASH
Storage Category: Hybrid Storage
Drive quantity, size, type: 12 - SATA FLASH discs 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: SMB Share
• Align backup file blocks: Disabled (Default)
• Decompress before storing: Disabled (Default)
• Per-VM Backup Files: Enabled

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 RAID Z configuration

More Information

Challenge

Product Information:

Company name: SUSE
Product Family: Enterprise Storage
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: Enterprise Storage 6
Storage Category: Software Defined Storage
Drive quantity, size, type: 144 - 7.2k SATA w/RocksDB+WAL offloaded to 24 x 480GB SSDs (6:1 ratio)
Storage configuration: Erasure coded, 3+2
Firmware version: 6
Connection protocol and speed: RBD 40GbE
Additional support: All models and configurations of Enterprise Storage 6 with specifications equivalent or greater than the above

SUSE Enterprise Storage is a software-defined storage solution powered by Ceph designed to help enterprises manage the ever-growing data sets.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Test configuration - Physical Windows 2016 node with Veeam server. ESXi node with test Vms and Veeam proxy (Win 19). Physical SUSE Linux server as a repository
• LACP for 2x links on storage nodes. Veeam Proxy and Linux target use switchless. NIC teaming/mode 6 load balancing (alb)

Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TS-2088XU
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TS-2088XU
Storage Category: RAID Storage Array
Drive quantity, size, type: 5 – 8TB SATA HDD
Storage configuration: RAID 5, no SSD caching
Firmware version: 4.4.2.1310
Connection protocol and speed: NFS 10GbE
Additional support: All models and configurations of TS-2088XU with specifications equivalent or greater than the above

A NAS compute and storage solution in a box, with versatile storage interfaces which can take care of the demands of storage and capacity. The TS-2088XU Extreme Computing Platform is built with Intel® Xeon® W processor supporting multiple graphics/acceleration cards, DDR4 memory, and support for both 2.5” and 3.5” SSDs and SATA SSDs.

Veeam testing configuration:

Veeam Build Number: 10.0.0.4461

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)