Challenge

Cause

Solution

• remove the existing Veeam Agent for Microsoft Windows backup job from jobs (right lick > Delete)
• remove the backup files from configuration: right click Disk (backups) > Endpoint Backups > Remove from configuration. 

2. Place the backup chain into the required folder.

2.1 Example for a non-cloud repository

Backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a Veeam Backup & Replication repository into the following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the account that is used to access the repository. In this example, the account is DOMAIN1\user1, so the folder name would be DOMAIN1_user1.

The complete path to the backup files would be C:\Backup\DOMAIN1_user1\Backup Job 1

2.2 Example for a cloud repository

The backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a cloud Veeam repository into following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the tenant account that is used to access the repository. If the account name is Tenant2, the complete path to the backup files would be C:\Backup\Tenant2\Backup Job 1

If a subtenant is used with the account name Subtenant3, the path will be C:\Backup\Tenant2\Subtenant3\Backup Job 1

3. Rescan the Veeam Backup & Replication repository. Here is a brief guide on repository rescan.

4. The Veeam Agent for Microsoft Windows backup should appear under Disk > Imported.

5. Point the Veeam Agent for Microsoft Windows job to the required Veeam Backup & Replication repository. Do not run it immediately, just close the wizard after making the changes.

6. On the Veeam Backup & Replication machine, the backup should be moved from the Imported section to Backup > Disk. Make sure that backups are located in Backups > Disks (not Disk (imported)).

7. Run the Veeam Agent for Microsoft Windows backup job. It should continue the imported backup chain.

Note: The described solution works for Veeam Backup & Replication repository and Veeam Cloud Connect repository.

More Information

Challenge

Cause

Solution

More Information

Challenge

Solution

Below are causes and solutions to these common connection problems.

 
1. The connection to the Service Provider Gateway(s) cannot be made with the default port TCP 6180.

Ensure TCP/UDP port 6180 is allowed outbound from the tenant environment (for stateful firewalls only). If the firewall is stateless, a static rule will need added for the return traffic. Similar firewall exceptions with TCP/UDP 6180 need to be applied in the provider's firewall for traffic that is destined for each Cloud Connect Gateway. Additionally, please note that tenant proxies or repositories will connect directly to the Cloud Connect Gateways during job runs.

 
2. The certificate is expired and needs renewed.

 
3. The certificate was incorrectly keyed during the CSR process and needs re-keyed or the private key is missing entirely. 

Ensure the certificate with the private key is installed in the Service Provider Cloud Connect server. It does not need to be installed in the Cloud Connect Gateways if they are separate servers. The issued certificate with the private key will be a file with a .pfx extension.

  
4. The certificate chain has not been fully installed in the Service Provider Cloud Connect server and the chain of trust cannot be found. The connection to the Service Provider Cloud Connect server will not be authenticated unless the Tenant Veeam server can validate a certificate ending in a Root CA certificate.

Ensure the certificate chain is installed in the Service Provider Cloud Connect server, which includes subordinate (intermediate) and root CA certificates. Often the SSL certificate provider will include the chain in a separate file with a p7b extension.

 
5. In some cases, the Root CA certificate for the certificate chain is not installed with the Windows Operating system by default in the Tenant Veeam server, which causes an issue with certificate validation. In these cases, the Root CA and Subordinate certificates can be obtained from the CA's Website, or the certificate chain can be exported (without the private key) from the Service Provider Cloud Connect server and imported into the Tenant Veeam server.
 
 
6. The Cloud Connect Gateway(s) cannot resolve (with DNS) the Cloud Connect Server or the Cloud Connect Gateways cannot communicate internally or via the DMZ to the Cloud Connect Server. 

Ensure DNS can be resolved for the Cloud Connect Server from all Cloud Connect Gateways. Disable any gateways that are not going to be used.

7. In some cases, a firewall will have a type of adaptive security that filters SSL\TLS traffic. For example, some names for this are “deep packet inspection” (dpi), packet inspection, or SSL\TLS inspection. The usage of these features creates a Man-in-the-Middle scenario with the firewall and can cause issues when the certificate is exchanged to the Tenant Veeam Server.
 
8. Some newer certificate formats are only supported in 9.5 update 2 or later, for example, Microsoft Software Key Storage Provider.

More Information

Challenge

Starting in Mar. 2017, only case administrators and license administrators will be able to submit support cases. Please make sure to define valid case administrators for your Veeam licenses.  This change only affects cases submitted via the customer portal.  If you need immediate support, feel free to call in to the support line: https://my.veeam.com/#/support/phone-support


Customers are now able to list people who can manage support tickets on behalf of their company – case administrators. By adding a case administrator, you invite an employee of your company, a reseller or a third-party contractor to join you in managing your cases with the Veeam^® Support Team. Please note that case administrators can open cases, but they cannot manage your existing licenses.

Please also note Veeam Support is not able to change the case administrator for an account. This action can only be performed by license administrators (primary or secondary) for a given account.

To view your Production Licenses or discover what email is assigned as the License Administrator please click here: https://my.veeam.com/#/licenses/production
 
If you are a primary or a secondary license administrator, you already have access to case administrators management on My Account or by going here https://my.veeam.com/#/case-administrators-management. Here you can manage case administrators for all your licenses (Support IDs). Note: If the link for this pages does not load, this means you are not presently a license administrator for any contracts.

If you have lost access to the license administrator account or would like it to be changed, please create a licensing case.

Solution

How do you assign case administrators to a license? 

Click Create case administrator to invite someone to manage your support cases. A case administrator can be an employee of your company, a reseller or a third-party contractor. On the next page you will need to provide their e-mail address.

If the person to whom you would like to give case administrator rights does not have a profile on veeam.com, you may be asked to specify their name and company. If your case administrator's company is not yet registered on veeam.com some additional info may be requested. 

Once all the necessary details are provided you will need to select Support ID(s) to which the newly created case administrator will be associated. By doing so you give them the right to use the Support ID(s) when opening cases on behalf of your company. 

When the changes are saved, the new case administrator will be created and associated with the selected Support ID(s). Please note that if the specified user is not yet registered on veeam.com, they will have to complete the registration by following the corresponding link that they will receive by email. Should this be the case, the newly added case administrator will be able to access My Account and open cases only after confirming the registration.

If you would like to share a Support ID with one or several existing case administrators at the same time, please use the button Add administrator in the License view. Then, select administrators for this Support ID. Please note that the number of case administrators is limited – there can be no more than 10 case administrators per Support ID.  

You can also assign several Support IDs at a time to one of your case administrators. For this please click Add Support ID in the Case administrator view.

How do you remove case administrators from licenses? 

A case administrator can be removed from a license. Once this is done they will no longer be able to manage support cases for this Support ID (pic.1). Please note that you cannot remove other license administrators marked with a lock sign (pic.2).

You can also remove a case administrator from all your licenses at once by following the link Delete administrator in the Case administrator view. Please note that you will not see this link if the user is a license administrator. 

What rights do case administrators have? 

• Case administrators can open, update and close support cases for the licenses assigned to them
• Case administrators can also manage cases created by other case and license administrators 
• Case administrators can view your licenses but cannot manage them 
• Case administrators cannot view and manage other case administrators

More Information

Challenge

Cause

Solution

Challenge

Connect-VBRServer: Cannot connect to backup server because some of its components are out of date.

Cause

Solution

Challenge

Solution

cp /etc/vmware/firewall/service.xml /etc/vmware/firewall/service.xml.bak

chmod 644 /etc/vmware/firewall/service.xml

chmod +t /etc/vmware/firewall/service.xml

vi /etc/vmware/firewall/service.xml

chmod 444 /etc/vmware/firewall/service.xml

esxcli network firewall refresh

esxcli network firewall ruleset set -r "VeeamCiscoFirewall" -e true -a false 

esxcli network firewall ruleset allowedip add -r "VeeamCiscoFirewall" -i "<yourVeeamProxyIP>"

esxcli network firewall ruleset allowedip list | grep -v "All"

esxcli network firewall ruleset list

More Information

Challenge

You receive the following error during the guest processing:

Unable to release guest. Error: Unfreeze error (over VIX): [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{6323fe10-0205-47df-b015-4a5ff60c31e2}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Solution

This error means that the VSS writer responsible for the SQL server doesn’t work correctly. The error itself  is rather generic and can be caused by different reasons. One of them is an update of the Microsoft Azure AD Connect client.

If you recently installed this update, the repair of the SQL installation should fix the issue. If you didn’t, still try the below since it might also resolve another issues.

• Go to Add/Remove Programs
• Select Microsoft SQL Server 2012 Express LocalDB (or your actual SQL version)
• Select Repair

More Information

Challenge

Event ID = 5125, Failover Clustering:

Cluster Shared Volume 'VolumeX' ('VolumeX') has identified one or more active filter drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the filter driver vendor to verify interoperability with Cluster Shared Volumes.

Active filter drivers found:
WIMMount (HSM)

Cause

Solution

1. Reboot the Hyper-V host after the Recovery Media creation to disable the WIMMount driver.
2. Stop WIMMount manually.

SERVICE_NAME: wimmount
        TYPE               : 2  FILE_SYSTEM_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

Direct IO will resume after a while.

More Information

If you have further questions, open a support case as follows:

1. Right-click the Veeam Endpoint Backup / Veeam Agent for Windows icon in the system tray and select Control Panel.
2. Click the Support link at the top of the window.
3. Click Technical Support to submit a support case to the Veeam Support Team directly from the product.

Challenge

Guest VMs will fail to engage VSS when application-aware image processing is enabled generating an error:

 Error    Guest processing skipped (check guest OS VSS state and integration components version) (System.Exception)

Cause

This issue has multiple potential causes, usually related to the Integration Services version of the failing guest server. This issue occurs when Application-Aware image processing is utilized in the Backup or Replication job settings for transactional quiescence using Microsoft VSS

Solution

• Get-VM | ft Name, IntegrationServicesVersion
• Get-VM | select VMName, IntegrationServicesState
   

 

• Make sure that the virtual machine files (VHD files) are not sitting in the root folder of the CSV, as this may prevent correct snapshot creation due to permission restrictions. We strongly recommend to keep virtual machine files in separate folder.
   
  
  Verification
  
  Use these steps to verify whether your troubleshooting has worked without having to run a Veeam backup or replication job. If the Hyper-V writer caption for the VM displays the wrong state, you can contact Veeam Support to verify your troubleshooting based on this article, or contact Microsoft support for additional troubleshooting steps.
   
  
  Perform the following steps on the Hyper-V host that the VM is running on.
  
   
  
  Open an Administrator Command Prompt1.  
  2.  Run the command:
  Diskshadow /L C:\writers.txt
  3.  Run the command:
  list writers
   
  When this completes you can then open writers.txt and locate the VM name in the section for the Hyper-V writer. For each VM there's a "Caption" entry that should read "online" or "child partition", and not "offline" or "saved state".
   
   
   

More Information

PowerShell script to tell you if you need to update your Integration Services
https://blogs.msdn.microsoft.com/virtual_pc_guy/2013/04/29/powershell-script-to-tell-you-if-you-need-to-update-your-integration-services/

Recommended hotfixes for Hyper-V servers:

http://www.veeam.com/kb1838

http://blogs.msdn.com/b/virtual_pc_guy/archive/2009/02/02/looking-at-the-hyper-v-event-log.aspx

http://blogs.technet.com/b/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

Challenge

Solution

To run a SQL script from a command line, please perform the following steps:

1. Save the script as *.sql file (e.g. script.sql) to local disk
2. Make sure that no jobs are running
3. Run the following command:

   sqlcmd -S <SqlServerName>\<SqlInstanceName> -d <SqlDatabaseName> -i PATHTOSCRIPT\script.sql -o c:\resetresult.txt -I

   
   
        HKLM\Software\VeeaM\Veeam Backup and Replication\SqlServerName
        HKLM\Software\VeeaM\Veeam Backup and Replication\SqlInstanceName
        HKLM\Software\VeeaM\Veeam Backup and Replication\SqlDatabaseName
   
        If the script needs to be applied to EM database, please use:
        HKLM\Software\VeeaM\Veeam Backup Reporting\SqlServerName
        HKLM\Software\VeeaM\Veeam Backup Reporting\SqlInstanceName
        HKLM\Software\VeeaM\Veeam Backup Reporting\SqlDatabaseName
4. ​Restart the Veeam services

 
You may also run a SQL script from SQL Server Management Studio, right click on your database and choose the “New query” option, insert the text from the file, and click Execute.
 
SQL Server Management Studio can be found here:
https://www.veeam.com/kb1761
 

Challenge

Product Information: 

Product Family: Promise 
Status: Veeam Ready - Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features. 

Solution

Product Details: 

Model number: VTrak E5320f and VTrak 5300f
Number of Drives: 24 
Drive type: 9 Disks Seagate ST3000NM00 SAS, 3 Disks ST6000NM00 SAS, 4 Disks ST4000NM01 SAS, and 8 Disks HUS7260 SAS 
Firmware version: 11.03.0000.00 
Veeam Build Number: 9.5 
Additional support: Any hardware configuration with an equal or greater hardware configuration  
General product family overview: Storage subsystem with two storage controllers with 4 FC ports on each storage controller 

Veeam Details: 

Veeam Build Number: 9.5
Veeam Settings:  

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

More Information

Company Information: 

Company name: Promise Technology Inc. 
Company overview: Promise Technology Inc. is a recognized global leader in the storage industry and the leading developer of high-performance storage solutions, designed for the data center, surveillance, cloud and rich media markets. Always striving to meet the rigorous demands of our customers, Promise has earned a reputation for developing innovative storage solutions for vertical markets which deliver practical answers to the business challenges facing large enterprise corporations, small to medium businesses, security integrators and creative professionals. 

Promise is focusing on opening up new data storage markets, redefining storage possibilities and seeking opportunities for integrated development. This passion for innovation has kept us at the forefront of the storage industry and led us to form strategic alliances with leading storage-related companies worldwide. Promise has quietly become the preferred storage provider for the world’s top resellers and integrators, who are proud to sell our technology and products through their vertical markets and channels. 

Challenge

Solution

To run a SQL script from a command line, please perform the following steps:

1. Save the script as *.sql file (e.g. script.sql) to local disk
2. Make sure that no jobs are running
3. Run the following command:

   sqlcmd -S <SqlServerName>\<SqlInstanceName> -d <SqlDatabaseName> -i PATHTOSCRIPT\script.sql -o c:\resetresult.txt -I

   
   
        HKLM\Software\VeeaM\Veeam Backup and Replication\SqlServerName
        HKLM\Software\VeeaM\Veeam Backup and Replication\SqlInstanceName
        HKLM\Software\VeeaM\Veeam Backup and Replication\SqlDatabaseName
   
        If the script needs to be applied to EM database, please use:
        HKLM\Software\VeeaM\Veeam Backup Reporting\SqlServerName
        HKLM\Software\VeeaM\Veeam Backup Reporting\SqlInstanceName
        HKLM\Software\VeeaM\Veeam Backup Reporting\SqlDatabaseName
4. ​Restart the Veeam services

 
You may also run a SQL script from SQL Server Management Studio, right click on your database and choose the “New query” option, insert the text from the file, and click Execute.
 
SQL Server Management Studio can be found here:
https://www.veeam.com/kb1761
 

Challenge

All credentials and backup encryption keys may become unusable after manual migration of Veeam Backup and Replication server to another machine.
Manual migration imply two scenarios: 

1. Manual migration of Veeam B&R database and further Veeam B&R software installation on top.
2. ​Migration of Veeam B&R software only and subsequent switch to remote existing Veeam B&R database.

Cause

Solution

• We recommend to use Veeam configuration backup in order to migrate Veeam server.
• If a configuration backup is not available you will need to resupply all encrypted information stored in VeeamBackup database manually:
  • Use "Manage Credentials" option to re-enter all passwords
  • All encrypted backup sets need to be removed from configuration and re-imported afterwards
  • If you are using Enterprise Manager please contact Veeam technical support to remove crypto-info about EM master key from VeeamBackup database
• There is no need to resupply credential data if the Veeam server is restored from image backup or if operating system and Veeam software are reinstalled on the same machine.

Challenge

Product Information: 

Product Family: Oracle ZFS Storage Appliance
Status: Veeam Ready - Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features.   

Solution

Product Details: 

Model number: Oracle ZFS Storage Appliance 
Number of Drives: 38 – 7.2k HDD, 2 - SSD for write cache, 1 - SSD for read cache 
Firmware version: OS 8.7 
Additional support: Any hardware configuration with an equal or greater hardware configuration 
General product family overview: Oracle ZFS Storage Appliance architecture is powered by a multithreaded SMP operating system with massive DRAM caches that can immediately serve 70 to 90 IOs, enabling applications to respond immediately to your queries or your customer’s transactions. Because of its fast responsiveness, the Oracle ZFS Storage Appliance can be used in cloud environments or on premises for a variety of demanding workloads including business analytics and data warehouses, DevTest, data protection and virtualization. 

Veeam Details: 

Veeam Build Number:  9.5
Veeam Settings iSCSI/FC:  

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

More Information

Company Information: 

Company name: Oracle Inc., America 
Company overview: Oracle offers a plethora of applications, databases, servers, storage and cloud technologies to empower modern business. We provide a wide array of software, systems and cloud deployment models – including public, on-premises and hybrid clouds to ensure that the technology flexes to the unique needs of a business.

Challenge

All credentials and backup encryption keys may become unusable after manual migration of Veeam Backup and Replication server to another machine.
Manual migration imply two scenarios: 

1. Manual migration of Veeam B&R database and further Veeam B&R software installation on top.
2. ​Migration of Veeam B&R software only and subsequent switch to remote existing Veeam B&R database.

Cause

Solution

• We recommend to use Veeam configuration backup in order to migrate Veeam server.
• If a configuration backup is not available you will need to resupply all encrypted information stored in VeeamBackup database manually:
  • Use "Manage Credentials" option to re-enter all passwords
  • All encrypted backup sets need to be removed from configuration and re-imported afterwards
  • If you are using Enterprise Manager please contact Veeam technical support to remove crypto-info about EM master key from VeeamBackup database
• There is no need to resupply credential data if the Veeam server is restored from image backup or if operating system and Veeam software are reinstalled on the same machine.

Challenge

Solution

Challenge

Cause

Solution

Challenge

Cause

Solution

Fig 1.1



Fig 1.2

• Run the following command from the Veeam server. * masquerade address

• Connect via the console to the VM in the lab and run:

More Information

Challenge

Cause

Solution