Challenge

Cause

Solution

1. On the Formats tab set Format to English (US)
2. On the Administrative tab click Copy Settings and check that Format is set to English for Current user
3. Enable the Welcome screen and system accounts checkbox on the same tab
4. Press OK and restart your machine

More Information

Challenge

Cause

Solution

Challenge

Cause

Solution

1. On the Formats tab set Format to English (US)
2. On the Administrative tab click Copy Settings and check that Format is set to English for Current user
3. Enable the Welcome screen and system accounts checkbox on the same tab
4. Press OK and restart your machine

More Information

Challenge

Solution

• Veeam Backup & Replication must have an Enterprise or Enterprise Plus license to perform this restore.

• On the proxy tab: Put the production NIC of the Virtual lab on the same network as the Veeam server, and either use DHCP if available in your environment or assign it an unused production IP.
• On the networking tab: You will want to use "Advanced Single Host".
• You'll want to configure the internal NIC in the "Network Settings" tab with the same IP address as the production default gateway on the network that the mailbox server and domain controller are connected to.

• export-mailbox –id ‘John Doe’ -PSTFolderPath z:\John.Doe.pst

More Information

Challenge

Cause

Solution

More Information

Challenge

Solution

• Veeam Backup & Replication must have an Enterprise or Enterprise Plus license to perform this restore.

• On the proxy tab: Put the production NIC of the Virtual lab on the same network as the Veeam server, and either use DHCP if available in your environment or assign it an unused production IP.
• On the networking tab: You will want to use "Advanced Single Host".
• You'll want to configure the internal NIC in the "Network Settings" tab with the same IP address as the production default gateway on the network that the mailbox server and domain controller are connected to.

• export-mailbox –id ‘John Doe’ -PSTFolderPath z:\John.Doe.pst

More Information

Challenge

Solution

1. Close the Veeam Backup & Replication console.
2. Open Regedit.exe
3. Navigate to the key HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
4. Add a new DWORD ‘EnableDBExclusions’
5. Set the Value to 1

6. Close the Registry Editor and open Veeam Backup & Replication
7. Open “Database Exclusions” from the Main Menu

10. Specify the Database name (case sensitive) that you wish to exclude from application-aware image processing.

On next job run the specified database will be excluded from the Application-Aware Image Processing freeze task.

Challenge

Cause

Solution

More Information

Challenge

Job fails with the following error message, “Task failed Error: Object <vmname> not found”

Cause

• Reinstallation or creation of a new vCenter server where the old VC database is not reused.
• A VM is removed from inventory and then added back to inventory.
• In rare cases a host crash, which prompts the host to be removed and added back to the VC may cause the VMs on that host get new MOREF IDs.

Solution

Go to the Backup Infrastructure and rescan the vCenter Server.

Remove and re-add VMs affected by this behavior back to the job.

Please note that in version of Veeam Backup & Replication 6.1 and newer, the console session caches the Ref-IDs to make navigation faster. If the Ref-IDs have recently changed, the cache will most likely not have the correct Ref-IDs. To force the Ref-ID cache to be flushed, press the “Add” button and then click the refresh button within the “Add Objects” dialog.



After you have flushed the cache, proceed to re-add the VMs to the job.

After you have added the VMs back to the job, click Finish. Then, open the job once more and repeat the “Recalculate” action.

All VMs should now correctly report their sizes and processes with this will now proceed in your Backup or Replication job.
Please be aware of that if the MOREFs were changed, Veeam sees the VMs as completely new ones, so on the next run Veeam will perform an active full for them.

Challenge

Cause

Solution

1. Create simple repositories, and at least one of them should be a path where backup files to be imported are stored (e.g., if backup files are in D:\Backups\Backup_Job_1\ then create a repository referencing the path D:\Backups).
2. Re-scan the simple repository or repositories, and ensure all backups are imported.
3. Create the SOBR and add the relevant repositories as extents.
4. Within the creation process Veeam will inform via confirmation prompt that “Jobs and backups using this extent will be automatically updated to point to the scale-out backup repository.”
6. If any jobs are not mapped to the backup files now within the SOBR, map them per the standard process.
    

1. Place the backup files to be imported in a temporary path. (e.g., if backup files are in D:\Backups, either copy or move them to D:\Backups-temp. A move is usually much faster.)
2. Create a new simple backup repository that references this path (in our example, D:\Backups-temp).
3. Re-scan the repository, and ensure all backups are imported.
4. You can map the pre-existing job to the backup files’ new location now, or at the end.
5. Edit your existing SOBR and add the new temporary repository to its list of extents.
6. Place the new temporary repository extent in “Maintenance” mode.
7. Evacuate the extent. Veeam will redistribute the backup files to other extents in the SOBR.
8. If you did not map the original job in step 4, do so now.

More Information

• Allowed alphanumeric characters: a-z, A-Z, 0-9
• Allowed special characters: _ - . + = @ ^
• Must not contain spaces; use underscores in their place

• Make sure to copy files from the backup chain from all extents.
• SOBR backup chains are typically per-VM backup files. Simple repositories are typically per-job backup files. The chain will retain this method until an active full is run on the job to enforce the change.
• The VBM file will exist in all extents. All VBMs for a particular backup job within a single SOBR should be identical. As a result, the target simple backup repository needs only contain one VBM.

Challenge

Cause

Solution

More Information

Challenge

"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"

Cause

Solution

More Information

Challenge

Solution

1. Create Veeam ONE service account and assign in the following SQL 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

1. Create a new DB using the Veeam ONE service account that has the permissions specified above assigned.
2. Run Script from Veeam ONE ISO – Addons\SQLScript\SQLScript.sql
3. Install VeeamONE using the specified Service Account and DB. If Veeam ONE is already installed Specify DB using Veeam ONE settings utility located in C:\Program Files\Veeam ONE\Veeam One  Settings\VeeamOneSettings.exe

More Information

Cause

Solution

1. Open SCOM Operations Manager Console.
2. Select Discovered Inventory
3. Filter to Data Warehouse Synchronization server

Cause

Solution

Cause

Solution

More Information

Cause

Solution

1. Open Veeam ONE reporter.
2. Select Configuration Tab
3. Select Object Properties Collection Task
4. Click Run
5. Once complete check report
6. To prevent in future click Scheduling and adjust to a time closer to beginning of business day with an allotment of 1 to 2 hours for collection to complete

Cause

Solution

1. Open Veeam ONE Reporter.
2. Open the Configuration section.
3. In the Configuration section menu, click Extension Modules.
4. Open the Report management tab.
5. Click Import.
6. In the Import reports window, Navigate to the Veeam ONE ISO \Addons\Extension Modules. Then Import each report pack.

More Information

Challenge

"HotAdd is not supported for this disk, failing over to network mode"

Solution

Requirements:

1. If the Veeam Proxy being used to process the source VM is on a VMFS 3 datastore it must be formatted with proper block size to be able to mount the largest virtual disk of the hot added VMs:
   • 1MB block size – 256GB maximum file size
   • 2MB block size – 512GB maximum file size
   • 4MB block size – 1024GB maximum file size
   • 8MB block size – 2048GB maximum file size
2. The Proxy being used to back up the VM must be a Virtual Machine on a host that is able to access the datastore where the source VM’s disks are stored
3. For vSphere 5.1 the maximum supported VMDK size is 1.98 TB
4. For vSphere 5.5 and older the maximum supported VMDK size is 62 TB
5. The disks that are to be hotadd must be SCSI. IDE and pvscsi drives are not compatible with hotadd
6. VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
7. Datastore needs sufficient space for a VM snapshot

Known Issues:

• If the VM disk resides on a Vvol the Hot Add Proxy VM's configuration files must also be on the same Vvol.
• Hotadd may fail if any disk was created with a newer hardware version than the VM being backed up. For example, if a disk was moved from a hardware version 8 VM to a hardware version 7 VM. To resolve, upgrade the hardware version of the VM.
• A single SCSI controller can have a maximum of 15 disks attached. To run multiple concurrent jobs with more than 15 disks, you need to add more SCSI controllers to your Veeam Proxy server that is responsible for hot adding the disks. (kb.vmware.com/kb/1037094)
• In case of standalone host connection (no vCenter added to the console), you can only hot add disks of VMs which are located on the same host as the proxy server.  This may require additional proxy servers to be configured on each host in the environment.
• Hotadd may fail if you are trying to back up the VM through the host added as a standalone server into Veeam Backup Infrastructure but actually being managed by vCenter. The following error message can be found in the source agent log:

  "Reconfigure attempt failed for VM "" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")"

• Hot Add may fail if the VM you are trying to back up and the proxy server are in different clusters.
• Virtual Appliance backup job fails after you’ve cloned or restored your VBR server. The reason for that is incorrect UUID reference for Veeam Backup VM which can be found in the following registry key of the Veeam server. Please see http://www.veeam.com/kb1332
• Hot Add fails if VM disks being backed up don't have unique ddb UUIDs across the Vcenter, for example if such VMs were deployed from a single template to different hosts.  Please refer to this Vmware article for details: http://kb.vmware.com/kb/2006865

Troubleshooting:

• Test to see if the disk of the VM to be backed up can be manually hotadded to the proxy. See: http://www.veeam.com/kb1184
• Check all Veeam Proxies for old hotadded disks and release them manually. See: http://www.veeam.com/kb1775
• Disable automount on the backup proxy, as documented in http://www.veeam.com/kb1882.

More Information

Please contact Veeam Technical Support for further assistance.

Challenge

Cause

Solution

• Dell EMC Data Domain OS 6.0 support, including synthetic full backup performances optimizations, backup retention and health check reliability improvements.
• HPE 3PAR 3.2.2 MU3 support, including multiple storage API interaction improvements for added reliability and performance.
• HPE StoreOnce 3.15.1 support, bringing Instant VM Recovery to Catalyst-based backup repositories.
• Veeam Agent for Linux 1.0 support.
• Veeam Agent for Microsoft Windows 2.0 Public Beta (build 2.0.0.594) support.
• VMware vSAN 6.5 support.
• VMware vSphere 6.5 support (see the next section for details).

• Encrypted VMs support. vSphere 6.5 introduces VMs with encrypted disks. Such VMs can be backed up in hot add and network (NBD) transport modes only, with hot add mode requiring that the backup proxy itself is an encrypted VM. There are no limitations around restores, because backups contain unencrypted VM data (remember to enable backup encryption if that is a concern).
• VMFS6 and VVOLs 2.0 support. vSphere 6.5 introduces the new versions of VMFS and VVOL (Virtual Volumes), which are fully supported with this update. This includes support for advanced functionality such as Backup from Storage Snapshots and Veeam Explorer for Storage Snapshots for VMs with virtual disks residing on VMFS 6 datastores.
• Virtual hardware version 13 support. vSphere 6.5 introduces the new VM hardware version which increases some configuration maximums and adds ability to add NVMe controllers to a VM. This update adds ability to process such VMs.
• NBD compression. VDDK 6.5 adds ability to enable native NBD traffic compression. To control the compression level, create VMwareNBDCompressionLevel (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server with value from 0 (no compression) to 3 (best compression). Please expect significant performance impact from enabling NBD compression unless you’re backing up over slow or busy management network.
• New guest interaction API support. vSphere 6.5 discontinued VIX API that previous Veeam versions leveraged for network-less guest interaction for functionality such as application-aware processing. As part of vSphere 6.5 support effort, we have switched the corresponding functionality to the new vSphere API for guest interaction, so that you can continue using the existing product functionality with vSphere 6.5.
• New VM tag API support. vSphere 6.5 introduces new APIs for programmatic access and management of vSphere tags. With its support by Veeam, you can continue using advanced backup policies based on tags even after you upgrade to vSphere 6.5

• Double-byte support. Double-byte characters are now supported in the virtual infrastructure object names (such as VM name) and Veeam object names (such as job name).
• Export performance improvements. Disk content export from agent-based backups now processes multiple disks in parallel, as opposed to sequentially.

• Performance improvements. Performance of Backup Copy jobs with large number of VMs (hundreds/thousands) was improved.
• Reliability improvements. Added transfer resume functionality for transparent handling of short network connection outages in certain backup copy process phases where they were not previously used.

• Reliability improvements. Added transfer resume functionality for transparent handling of short network connection outages between a source backup repository and a tape server.

• OES 2015 SP1 support. Open Enterprise Server 2015 SP1 support for file-level recovery from NSS volumes with Trustee Index enabled.

• Side by side restore. Tenants are now able to restore VMs and vApps without overwriting the original object by selecting Keep restore option, in which case the restored object will be created with the _restored suffix as opposed to overwriting the original object (which is still possible by selecting Overwrite restore option).
• Job mapping. Added Set-VBRvCloudOrganizationJobMapping PowerShell cmdlet that allows to map a vCloud backup job and associated guest processing credentials to the existing self-service org record to enable tenants to start using self-service portal functionality for the existing jobs and backups.

• Direct SAN transport improvements. Improved direct SAN transport selection on backup proxies with disabled MPIO, added support for parallel restore through multiple Direct SAN backup proxies.
• Restore without storage profile. The newly added Default policy container in the Select Datastore dialog allows restoring, replicating or migrating virtual machines without their virtual disks inheriting an existing storage profile assigned to the target datastore.
• Restore logic improvements. Full VM restore and Instant VM Recovery operations will now preserve workingDir parameter of the original VM.
• Broker service enhancements. Added experimental Broker Service behavior when it does not try to keep the vSphere infrastructure cache up-to-date continuously. Instead, it will query vSphere infrastructure hierarchy changes only when hierarchy data is requested, but no less often than the specified timeout. Using this mode significantly reduces vCenter Server traffic in large environments while only slightly delaying tasks requiring vSphere hierarchy data. To enable this mode, create VmwareForcedHierarchyUpdatePeriod (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server with the value in seconds (900 is the recommended value).

• Asian OS locales support. Veeam Backup & Replication console now supports installation on operating systems with Asian locales, where it was previously unusable due to misplaced UI controls. Update 1 has been tested on all most common Asian locales and validated by local Veeam sales teams of the corresponding regions.
• Experimental high DPI monitors support. We've made the first step towards high resolution monitors support - and while there's still work to be done, the UI is now more usable on DPI settings above 100%. This did require changing the UI font, resizing all dialogs and adjusting placement for some UI controls - so you will notice slightly different UI look after installing the update.
• Wizard improvements. We've renamed the Next button before each step that applies the current settings into the configuration database to Apply in all wizards to make the consequences of clicking Next more obvious.
• Support ID copy. By popular demand, we've enabled you to copy your Support ID from the License Information dialog into the Windows Clipboard.

• Fixed an issue which caused monthly Active Full backup schedule to reset to the default one (First Monday of the month) after upgrading to version 9.5.
• Improved reliability of establishing connections to Linux servers by addressing a number of Linux version-specific issues and updating SSH client.
• Improved Direct Restore to Microsoft Azure proxy appliance deployment and management functionality.
• Improved backup placement logic improvements for reversed-incremental backup jobs targeting scale-out backup repository with per-VM backup file chains disabled.
• Addressed an issue with enabling CBT on a VMware VM when backup server is running on certain non-English locales, for example Turkish.
• Addressed a number of minor issues with Veeam Cloud Connect.

More Information