Challenge

​The network path was not found.

Cause

Solution

More Information

Challenge

Cause

Solution

• Verify that the account used to connect to Veeam Backup and Replication server in Veeam ONE has correct permissions. To check the account name, go to Veeam ONE Monitor > Data Protection View > right-click on the Veeam Backup and Replication object. Note the specified account.
• On the Veeam Backup and Replication server, verify this account as well as the Veeam ONE service account are added to the Event Log Readers Group and Administrators group in Local Systems and Groups
• Check the firewall ports configuration according to the requirements.
• Based on the alarm details, connect to your Veeam Backup and Replication server, Backup Repository or Backup Proxy to check whether the following services are running: Windows Management Instrumentation, RemoteProcedueCall, RemoteRegistry.

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

• CREATE ANY DATABASE permissions
• db_owner role on the Veeam ONE database
• db_datareader permissions on the master database
• public, db_datareader, SQLAgentUserRole permissions on the msdb database
• [For Always-On Availability Groups] VIEW SERVER STATE permissions

More Information

Challenge

​The network path was not found.

Cause

Solution

More Information

Challenge

Solution

Your License Administrator may obtain a merged license file by following the steps below.
 
NOTE! Licenses can be merged only when they have the same:
• Account Name
• Product Name and Edition
• Product Version
• Support Terms
• License Administrator
• They must all be Active on Support.
 
1. Log on to the Veeam My Account dashboard and go to License management >> Production Licenses (https://my.veeam.com/#/licenses/production)
2. In the Action column for the appropriate product, select Merge


3. From this page, select each of the boxes to the left of all the individual licenses you would like to merge


4. In the box that appears below, select the appropriate version of the key for your software and whether you would like to download the license directly or have a copy of the key emailed to your License Administrator email.

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

1. Place the Exchange Virtual Machines disks on the fastest disks (Datastores) that are available.
2. Disable all background scanning and/or maintenance tasks occurring in Exchange, or any other tools that are being leveraged against the system at the time of backup.
3. Perform the Exchange Backup singularly as opposed to concurrently with other jobs.
4. Adjust Microsoft settings for failover sensitivity (in bold, run from command line):
   1. cluster /prop SameSubnetDelay=2000:DWORD (Default: 1000)
   2. cluster /prop CrossSubnetDelay=4000:DWORD (Default: 1000)
   3. cluster /prop CrossSubnetThreshold=10:DWORD (Default: 5)
   4. cluster /prop SameSubnetThreshold=10:DWORD (Default: 5)
   5. To check settings, use: cluster /prop (see note)
5. Add the line snapshot.maxConsolidateTime = "1" to the .vmx (configuration) file for the primary node. Please note that this is an undocumented vmx alteration, and should be validated by VMware support prior to using.
6. Reduce total amount of disks (.vmdk's) for primary node if possible, reducing impact of snapshot operations.
7. If possible, migrate the virtual machine from NFS type to VMFS formatted storage.
8. Use Network (NBD) mode setting on Source Backup Proxy as opposed to Appliance (hotadd) mode for your backup and/or replication jobs in Veeam.
9. Test snapshot operations directly to ESX(i) host instead of vCenter.  (In some cases, gaps in communication between vCenter and ESX(i) host can impact snapshot operations, including VSS operation timing.)

1. Install-WindowsFeature -name RSAT-Clustering-CmdInterface

1. Get-cluster | fl *subnet  - provides current settings for timeout
2. Altering cluster settings:
   1. (get-cluster).SameSubnetThreshold = 20 (Default 10 in Windows 2012R2)
   2. (get-cluster).SameSubnetDelay = 2000 (Default 1000 in Windows 2012R2)
   3. (get-cluster).CrossClusterThreshold = 40 (Default 20 in Windows 2012R2)
   4. (get-cluster).CrossClusterDelay = 4000 (Default 1000 in Windows 2012R2)

More Information

Challenge

Timestamp 12 (9572) Connecting to organization...
Timestamp 12 (6688) Failed to send heartbeat to controller
Timestamp 12 (6688) Error: Access is denied.

Timestamp 42 (9572) Found: Veeamuser, SMTP: Veeamuser@veeam.com
Timestamp 42 (9572) Trying to obtain license for Veeamuser@veeam.com
Timestamp 42 (9572) Failed to obtain license
Timestamp 42 (9572) Error: Access is denied

Cause

Solution

1. Stop Veeam Backup for Microsoft Office 365 Service and Veeam Backup Proxy for Microsoft Office 365 Service
2. Delete С:\Programdata\Veeam\Backup365\ProxyDb\ and C:\Programdata\Veeam\Backup365\Config.xml from Proxy Server
3. Start Veeam Backup Proxy for Microsoft Office 365 Service*
4. Start Veeam Backup for Microsoft Office 365 Service
5. Proxy ID should be synchronized - run the backup

Challenge

Solution

• Validate the VMs named "W2008", "W2008R2_DC" and "W2K" in the most recent restore point for the backup "Backup Job 1_imported".
  
  Veeam.Backup.Validator.exe /backup:"Backup Job 1_imported" /vmname:W2008 /vmname:W2008R2_DC /vmname:W2K
   
• Validate all virtual machines in the last restore point with ID 3942788C-B309-4FA4-A111-A4C87B3EC63D.
  
  Veeam.Backup.Validator.exe /backup:3942788C-B309-4FA4-A111-A4C87B3EC63D
   
• Validate a VM with the name "Windows 8" in the restore point created on December 5 2012 for a job named “Backup Job 1".
   
  Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"Windows 8" /date:05.12.2012
   
• Validate a VM with the name "VM1" in the restore point created around 16:00 on December 5 2012 for a job named "Backup Job 2".

• Validate a VM with the name "VM2" contained in the VBM file located at C:\Backup\VM2_Backup.vbm
  
  Veeam.Backup.Validator.exe /file:"C:\Backup\VM2_Backup.vbm" /vmname:"VM2"
   
• Validate all VMs in VBK-file (backup file).
  
  Veeam.Backup.Validator.exe /file:"C:\Backup\VM2_Backup.vbk"
   
• Validate a VM with the name "VM3" in the most recent restore point of "Backup Job 1" and create an HTML-report.
  
  Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"VM3" /report:"D:\Reports\Backup_Job_1_Validate_30_09_2014.html"
   
• Validate a VM with the name "VM3" in the most recent restore point of "Backup Job 1" and create XML-report.
  
  Veeam.Backup.Validator.exe /backup:"Backup Job 1" /vmname:"VM3" /report:"D:\Reports\Backup_Job_1_Validate_30_09_2014.xml" /format:xml

• Validate a backup file.
  
  Veeam.Backup.Validator.exe /file:"\\192.168.1.5\TestShare\Empty VM encryptedD2017-09-22T172639.vbk" /username:172.16.16.198\Administrator

More Information

1. The date format that must be used is based on the regional settings of the computer the tool is run on. If the system is configured to have mm.dd.yyyy, as opposed to dd.mm.yyyy, please use that date format
2. Backup Validator must be started with Administrator privileges
3. When files are located on network share you need to specify the whole path (ex.: \\192.168.1.5\TestShare\Empty VM encryptedD2017-09-22T172639.vbk).
4. Mapped network drives (net use z: \\192.168.1.5\TestShare) are not supported.

Challenge

When storage snapshot gets mounted to proxy Windows creates multiple registry records in:
HKLM\SYSTEM\ControlSet001\Enum\MPIO
HKLM\SYSTEM\ControlSet001\Enum\SCSI (when windows mpio is disabled)

The problem is that when storage snapshot gets unmounted Windows does not clean up registry records.
Eventually Windows will not boot when SYSTEM hive reaches 1.5GB (maximum size for system hive).

Cause

This is a known Microsoft bug. 
From Microsoft KB article:
On a computer that's running Windows Server 2003 or a later version of Windows, a storage device that's connected through a fiber channel or through the iSCSI protocol may be connected for only a brief period. When a storage device is connected, Windows creates registry information for the device. Over time, the registry may contain many entries for devices that will never be used again. 

Per Microsoft premier support case no. 117091816357204: Microsoft stated that they do not consider this behavior as a bug.

Solution

More Information

Challenge

Jobs fail with an error message indicating incorrect user name or password. An account associated with Veeam is being locked out in Active Directory.

Cause

Solution

Run services.msc in order to access details of services on the Veeam Backup & Replication and/or Backup Enterprise Manager servers. Sort by service name, and scroll down to find the Veeam services.

Key services (highlighted below) should have administrator credentials entered. This frequently is done with a Veeam service account, but can be any administrator account. If the logged-in user is an administrator, “Local System” can suffice, but in environments with multiple backup operator users, it is recommended to use a service account.


To change the account of a service, right-click the service and select Properties, then the Log On tab. You can enter the account or browse for it in AD, then provide the password.


Credentials are also specified in Veeam for:

• Any Managed Server (aside from “This Server”):

• ​Credentials for CIFS shares

• Credentials for EMC Data Domain and HPE StoreOnce deduplicating appliance repositories

• Guest credentials for Application Aware processing

 

More Information

Challenge

Cause

Solution

Challenge

Solution

• Solution 1:
  In some instances, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
  http://www.veeam.com/kb1198

• Solution 1:
  https://www.veeam.com/kb1775
  Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, remove the disks not owned by this VM without deleting from the datastore. Once deleted, consolidate snapshots on the affected VMs.
   
• Solution 2:
  kb.vmware.com/kb/2003638
  Orphaned Snapshots – Consolidate snapshots on affected VMs
   
• Solution 3:
  http://www.veeam.com/kb1875
  Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter
   
• Solution 4:
  http://www.veeam.com/kb1882
  Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.
  
  Run the following via CMD Prompt on the proxy server:
  diskpart
  automount disable
  automount scrub
  exit
   
• Solution 5:
  http://www.veeam.com/patches.html
  Patching – Please ensure that all VMware and Veeam components are fully up to date.
   
• Solution 6:
  In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.

• Solution 7:
  In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490) may yield positive results if all above testing does not resolve the issue.
• Solution 8:
  Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 
  
  Job.Job_name.log:
  [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB
  
  Agent.Job_name.VM_name.Hotadd.Attacher.log:
  [time stamp] < threadID> vdl| [vddk] time stamp  error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)
  
  The behavior is observed when a Veeam Proxy is replicated with Veeam B&R, the replication process preserves the original VM bios UUID for restore purposes. To work around the issue setup a dedicated VM as a Veeam Proxy, replicating Veeam Proxies is not usually necessary due to ease of deployment.

More Information

• Manual Hotadd - http://www.veeam.com/kb1184
• Hotadd Requirements - http://www.veeam.com/kb1054
• Deploy an additional standalone proxy to isolate failures to a single specified proxy
• To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.

Challenge

Solution

1. Disable the tenant account.
2. Remove tenant backup resources.
3. Re-add tenant backup resources, give a new friendly name. It'll say that the folder already exists, just click yes.
4. Re-enable tenant account.
5. Rescan provider on tenant side.
6. Rescan 'new' repository.
7. Edit job(s), change 'storage' to be the 'new' repository. Click Map Backup and select the appropriate backup chain.
8. Remove 'old' repository from tenant backup infrastructure.
9. Run the job.

Challenge

Cause

Solution

Required Permissions

Authorizing with Veeam ONE

To authorize with Veeam ONE software components (Veeam ONE Monitor, Reporter and Business View), a user must have the Allow log on locally privilege assigned.

By default, this privilege is assigned to users included in the local Administrators group. For users not included in the local Administrators group, you must assign this privilege manually. For details, see this Microsoft TechNet article.

Connection to Microsoft SQL Server

The account used to connect to the Microsoft SQL Server hosting the Veeam ONE database must have the following permissions:

• Public role (default permissions)
• CREATE ANY DATABASE permissions
• db_owner role on the Veeam ONE database
• db_datareader permissions on the master database
• public, db_datareader, SQLAgentUserRole permissions on the msdb database
• [For Always-On Availability Groups] VIEW SERVER STATE permissions 

Connection to Microsoft Hyper-V VM Guest OS

The account used to collect data from guest OSes of Microsoft Hyper-V Windows VMs, must have local Administrator permissions on the guest OS.

Connection Under UAC

Veeam ONE collects data from Microsoft Windows servers using WMI. For some configurations, UAC access token filtering can prevent running WMI commands on connected machines, which in turn will cause data collection failures.

The affected configurations are:

• Non-domain machines (machines in a workgroup)
• Machines with an unelevated local Administrator account (the account that is not Built-in Administrator)

To allow Veeam ONE collect data from these machines, perform the following steps on target virtual servers:

1. Set the network location to private:

1. Log on to a machine as Administrator.
2. Open the Network and Sharing Center.
3. In the list of active networks, click the necessary network and change its location to Private.

In some Windows OS versions, this location is called Home or Work.

1. Configure Windows Remote Management.

To do so, in the command prompt, type winrm quickconfig and press [Enter].

For more details on UAC access token filtering, see User Account Control and WMI.

Authorizing with Veeam ONE

To authorize with Veeam ONE software components (Veeam ONE Monitor, Reporter and Business View), a user must have the Allow log on locally privilege assigned.

By default, this privilege is assigned to users included in the local Administrators group. For users not included in the local Administrators group, you must assign this privilege manually. For details, see this Microsoft TechNet article.

Remote Access

To be able to access Veeam ONE software components installed on a remote machine, you can use one of the following options.

Remote Access to Veeam ONE Reporter and Business View through Web Browser

Veeam ONE Reporter and Business View consoles can be accessed using a web browser on a remote machine. To learn more on how to access Veeam ONE software components, see Accessing Veeam ONE Monitor, Reporter and Business View.

Veeam ONE Reporter and Business View consoles remotely, a user must be a member of the Veeam ONE Administrators or Veeam ONE Read-Only Users group on the machine where Veeam ONE Web UI component is installed. For details on Veeam ONEsecurity groups, see Security Groups.

Remote Access for Multi-Tenant Monitoring and Reporting

Veeam ONE supports multi-tenant access to its monitoring and reporting capabilities. Authorized users can remotely monitor a subset of the vCenter Server or vCloud Director infrastructure and create reports.

To monitor and report on a restricted scope of the virtual infrastructure, a user must have permissions assigned on objects of the vCenter Server or vCloud Director inventory hierarchy. For details, see Veeam ONE Multi-Tenant Monitoring and Reporting.

Required Ports

The following table lists connection settings required for proper communication between Veeam ONE components, virtual infrastructure servers, vCloud Director servers and Veeam Backup & Replication servers.

1 You must open these ports manually
2 To learn about enabling and disabling WMI traffic, see http://msdn.microsoft.com/en-us/library/aa389286(v=vs.85).aspx and http://msdn.microsoft.com/en-us/library/aa822854(v=vs.85).aspx 
3 Associated with the File and Printer Sharing service
4 To gather performance data from Windows Server 2012 and 2012R2, you must additionally enable network discovery.

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

1. On the Veeam ONE Server machine, change the collection interval in the following registry key:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service
   Create a new DWORD value with the following properties:
   Name = HostRuntimeInfoUpdateInterval
   Base = Decimal
   Value = XXX, where XXX is the required timeout in seconds.

2. Once you change the value, restart Veeam ONE Monitor Service.  

3. Perform the necessary tests to make sure you are getting alerts in a timely manner in your environment.  

More Information

Challenge

Solution

1. Execute the following SQL script against the Veeam ONE database:
   
   UPDATE monitor.Alarm SET delete_time = NULL
   UPDATE monitor.AssignAlarm SET delete_time = NULL

2. Restart Veeam ONE Monitor Server service.

More Information

Challenge

Jobs fail with an error message indicating incorrect user name or password. An account associated with Veeam is being locked out in Active Directory.

Cause

Solution

Run services.msc in order to access details of services on the Veeam Backup & Replication and/or Backup Enterprise Manager servers. Sort by service name, and scroll down to find the Veeam services.

Key services (highlighted below) should have administrator credentials entered. This frequently is done with a Veeam service account, but can be any administrator account. If the logged-in user is an administrator, “Local System” can suffice, but in environments with multiple backup operator users, it is recommended to use a service account.


To change the account of a service, right-click the service and select Properties, then the Log On tab. You can enter the account or browse for it in AD, then provide the password.


Credentials are also specified in Veeam for:

• Any Managed Server (aside from “This Server”):

• ​Credentials for CIFS shares

• Credentials for EMC Data Domain and HPE StoreOnce deduplicating appliance repositories

• Guest credentials for Application Aware processing

 

More Information