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

Cause

Solution

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

Cause

Solution

More Information

Challenge

Solution

Challenge

Solution

• Ensure none of the cluster nodes are in maintenance mode, have the cluster service stopped, are powered off, or otherwise not accessible.
• Ensure all nodes within the cluster can communicate with each other.  This can be tested by pinging between the nodes and using wbemtest (see http://www.veeam.com/kb1926) to connect between nodes via WMI.  For wbemtest, the two namespaces you want to ensure can be connected to are root\cimv2 and root\virtualization (root\virtualization\v2 for Windows Server 2012+).
• Make sure the hosts are not added to the Veeam console as standalone hosts if they belong to a cluster.  This prevents changed block tracking data from being replicated to all nodes.  The cluster must be added to the Veeam console.

• Ensure the SMB server is added to the Backup & Replication console.

• Ensure the shares are visible in the Backup & Replication console.

• If Hyper-V checkpoints/snapshots are manually created/deleted (merged) on VMs, you will get a message that changed block tracking is not working.  This is because checkpoint/snapshot operations create an additional file (avhd/avhdx) that has to be tracked.  It is added to the list of files to track (or removed in case of deletion/merge of a snapshot/checkpoint) and the changed block tracking warning should resolve the second job run after the snapshot/checkpoint was created/deleted (merged).

• Select the option to disable changed block tracking on all Hyper-V hosts in the cluster.  To do this, right-click on each host in the cluster, select Manage Volumes and then check the box to disable changed block tracking.

 

• Run sc stop VeeamFCT, in an elevated command prompt, on each Hyper-V host in the cluster to ensure the CBT service is stopped.
• Find, export and then delete the following registry key on all Hyper-V hosts in the cluster:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VeeamFCT\Parameters\CTDB
• Go back to the Manage Volumes for each host and uncheck the disable changed block tracking option.  Try the job after this.  Allow a couple of job runs before ensuring CBT is working.
• If the issue persists, reboot each Hyper-V host in the cluster.  This will typically involve migrating VMs from one host to another and rebooting the host once it does not own any VMs.  Repeat these steps for all Hyper-V hosts in the cluster.

Challenge

Solution

Challenge

Cause

Solution

Challenge

Cause

Solution

Challenge

Cause

Solution

More Information

• General purpose storage accounts provide storage for blobs, files, tables, and queues in a unified account. 
• Blob storage accounts are specialized for storing blob data and support choosing an access tier, which allows you to specify how frequently data in the account is accessed. 

Challenge

When attempting to perform a Windows FLR (Guest Files ‘Windows’) the restore fails with:



No disks have been mounted. Either disks of this type aren’t supported or some errors occurred. See log file for details.

Solution

• FAT
• FAT32
• NTFS
• ReFS*

More Information

Challenge

Cause

• Disk space required to store VMware vSphere historical data 
• Disk space required to store Microsoft Hyper-V  historical data 
• Disk space required to store Veeam Backup & Replication historical data"                                

• Virtual infrastructure inventory (number and configuration of objects in your virtual infrastructure)
• Veeam Backup & Replciation infrastructure inventory (number of jobs, VMs in the backup job and job schedule)"     

Solution

1. Investigate your virtual and backup infrastructures to find out the number of hosts, clusters, virtual machines, datastores to monitor as well as their configuration parameters.                                
2. On the Calculator worksheet in the Parameters column,  enter information about your infrastructure inventory, job schedule and number of protected VMs. Note that the green text color in cells indicates user-input values; the grey text color indicates that the values should not be changed.                                

More Information

Challenge

You receive the following error within moments of a job starting:
 
Cannot connect to the host's administrative share. Host:  [VM hostname or IP]. Account: [domain\user].
Win32 error: The network path was not found. Code: 53

NOTE: This applies to both VMware and Hyper-V hypervisors.

Cause

This error means that the Veeam Backup & Replication server cannot connect to the Windows guest’s OS feature to deploy guest processing components. This path will be the ADMIN$ share (\\hostname\admin$) of the guest itself.
 
These components are deployed directly from the Veeam Backup & Replication server. If networking is inherently impossible to the guest from the B&R server (different networks, firewall, etc), processing protocol may require inversion (VMware only).

Solution

• Make sure the Windows time on the Veeam Backup server is the same as in the guest OS.
• Make sure you do not have a firewall in the way (you can try disabling it for testing).
• Make sure you can connect to the admin share (for example, \\Server Name\admin$) with the same credentials as provided to Veeam Backup & Replication for VSS.
• Make sure the VSS writers are set to automatic in the guest OS.
• Make sure you provide Local Administrator (MACHINE\Administrator) or Domain Administrator (DOMAIN\Administrator) account privileges.
• Make sure the guest OS is in the same network as the Veeam Backup server.
• Make sure File and Printer Sharing is enabled in the guest OS.
• If the guest OS is Vista/2008 or later:
  • In the Network and Sharing Center, verify that it is not set for a public domain.
  • Verify that the Remote Registry Service is started.

More Information

Challenge

Solution

1. Log on to the machine where you want to run multiple instances of Veeam ONE Monitor Client.

2. Open registry editor and navigate to the following registry key:
   for v5.0 - HKEY_CURRENT_USER\Software\Veeam\Veeam Monitor for VMware
   for v6.0  and higher - HKEY_CURRENT_USER\Software\Veeam\Veeam ONE Monitor

3. Create a new value with the following settings:

As a result, you will be able to run multiple instances of Veeam ONE Monitor Client on a single machine.

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.

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.
 
If you are a primary or a secondary license administrator, you already have access to case administrators management on My Account. Here you can manage case administrators for all your licenses (Support IDs).

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

• vSphere 6.5 support. Veeam ONE now allows reporting and monitoring on vSphere 6.5 hosts and vCenter Server.
• Asian locales support. Veeam ONE console now supports installation on operating systems with Asian locales. Update 1 has been tested on all most common Asian locales by Veeam QC and validated by local Veeam teams of the corresponding locations.

• Memory demand for Hyper-V 2016 VMs. Veeam ONE now shows memory demand for VMs configured with static memory.

• Enhanced Backup Custom Infrastructure report. More Veeam backup object properties have been added to the report parameters list. 
• Enhanced VM Backup Status report. This report now allows filtering VMs based on the backup copy jobs.

• Veeam ONE Monitor Client is using wrong data samples to show performance graphs in the advanced scalability mode.
• Under certain conditions Veeam ONE service may crash when resolving all triggered alarms at the same time.
• Email notifications are sent only to first user email address specified in the alarms notifications section.
• Aggregation option cannot be switched to another value in the Veeam ONE Monitor Client.

• Backup copy jobs are treated as regular backup jobs for the “Suppress Veeam backup activity” option which leads to activating alarms suppression engine for production VMs.

• Datastore latency performance counter is showing wrong measurement units.
• Guest OS disk usage alarm is triggered for powered-off virtual machines.

• Hyper-V VMs guest OS disk monitoring alarm stops working when default settings are changed.
• Reads/sec, Writes/sec, IOPS performance counters from the Virtual Storage Device sub-system are not collected in the advanced scalability mode.
• "Local volume free space" alarm is falsely triggered during Veeam ONE service restart.
• Under certain conditions Veeam ONE falsely alarms on the age of existing VM snapshots.
• Under certain conditions Veeam ONE falsely alarms on VM snapshots that do not exist.

• Chargeback report pack is missing for users with limited access (tenants) to the virtual infrastructure.
• Alarms overview report cannot be generated after upgrading to Veeam ONE 9.5

• EMC DataDomain repositories are missing from all Veeam backup reports.
• "VMs Backed Up by Multiple Jobs" shows 01.01.0001 00:00 date as the latest job run for some VMs.
• Change Rate Estimation Rate report cannot be generated directly from Veeam ONE Monitor Client.

• Host Resource Usage Chargeback report for Hyper-V infrastructures treats Failover Cluster quorum disk as local. This disk should be ignored when reviewing the report.

• Veeam ONE Business View service attempts to collect virtual infrastructure data under user account which is used during web site login operation.

• 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.
• Guest OS disk usage alarm is reset to its default thresholds after installing Update 1.

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

1. Open Windows Disk Management from Control Panel > Administrative Tools > Computer Management > Disk Management.
2. Identify the volume to shrink. Warning message contains the sequential partition number which can be associated with the volume allocated on the disk. In most cases such partition is the last volume in the disk layout.
3. Calculate the amount of space to shrink. Warning message displays the size in bytes and shrink operation is calculated in Megabytes, so you have to convert bytes to Megabytes and round the result. Divide the value indicated in the warning by 1048576 and round it to get an integer. 
4. Right-click the affected volume and choose Shrink Volume. Specify the value you calculated earlier and click Shrink.
5. When the shrinking operation completes, re-run the backup job to verify the result. 

More Information

1. Right-click the Veeam Endpoint Backup 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

Cause

Solution

Challenge

Solution

More Information