Challenge

Veeam Agent for Microsoft Windows copies transaction log files from the log archive destination (set by the Microsoft SQL Server administrator) to a temporary folder on the Veeam Agent computer file system. By default the path is: C:\ProgramData\Veeam\Endpoint\SqlLogBackup. In case if the default destanation should be changed, you can specify it in SqlTempLogPath(STRING) registry key.

Solution

Important: the key should be created on the Veeam Agent for Windows machine!

SqlTempLogPath
KEY: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
TYPE: REG_SZ
VALUE: path to desired location (should be without \ in the end)

Challenge

This article documents antivirus exclusions that have been found to help prevent Veeam Availability Console from blocking for proper functioning.

Cause

In some instances, antivirus can prevent certain executables, processes, or agents from being correctly deployed or leveraged from the Veeam Server.

Solution

Antivirus Exclusions:

Folders on the Veeam Availability Console Server including Web UI:

C:\Program Files\Veeam
C:\ProgramData\Veeam
C:\Windows\Veeam
C:\Program Files\Common Files\Veeam
C:\Program Files (x86)\Common Files

Folders on the Veeam Availability Console Agents:

C:\Program Files\Veeam
C:\ProgramData\Veeam
C:\Windows\Veeam
C:\Program Files\Common Files\Veeam
C:\Program Files (x86)\Common Files
\\localhost\admin$\Veeam
\\localhost\admin$\Veeam\Availability Console\Agent for Windows\VeeamAgentWindows.exe

Files:

VeeamAgentWindows.exe
ManagementAgent.exe
VAC.CommunicationAgent.x64.msi
VAC.CommunicationAgent.x86.msi

Due to the complex nature of antivirus software, some additional exclusions may be needed.
If your antivirus has a logging or history system please review this to see actions it may have taken that may affect Veeam Availability Console operations.

More Information

Should you have any question, contact Veeam Support.

Challenge

Understanding the difference between Optimized for Typical Deployment, Optimized for Advanced Scalability Deployment and Backup Data Only data collection modes.

Cause

Data collection mode determines what metrics Veeam ONE will collect, and specifies the product configuration in a number of areas. Choosing an appropriate data collection mode allows you to optimize monitoring and reporting performance and improve user experience in Veeam ONE.
You can choose of the following Veeam ONE data collection modes:

Optimized for Typical Deployment mode is recommended for small to medium environments up to 100 hosts and 1500 VMs. In this mode, Veeam ONE collects all inventory, configuration and performance metrics, and makes collected data available in dashboards, reports and alarms. This mode provides the greatest data granularity level, but results in a greater load on the Veeam ONE server and a larger size of Veeam ONE database.
Optimized for Advanced Scalability Deployment mode is recommended for large environments with more than 100 hosts and 1500 VMs. In this mode, Veeam ONE collects all metrics required for alarms and reports. This mode provides a lesser data granularity level than the Typical Deployment mode, and results in a lower load on the Veeam ONE server and a smaller size of the Veeam ONE database.
Backup Data Only mode is recommended for users who want to focus on Veeam Backup & Replication monitoring and reporting, and do not need a deep visibility of the virtual infrastructure. In this mode, Veeam ONE collects all inventory, configuration and performance metrics from Veeam Backup & Replication servers. It also collects inventory and configuration metrics from virtual infrastructure servers, but skips virtual infrastructure performance metrics. As a result, Veeam ONE dashboards, reports and alarms display backup-related data only; for VMware vSphere and Microsoft Hyper-V objects, performance data is not available. This mode results in the least possible size of the Veeam ONE database and the lowest load on the Veeam ONE server.

Solution

To switch between the modes:

Open Veeam ONE Monitor.
On the toolbar, click Options and select Server Settings. Alternatively, you can press [CTRL+S] on the keyboard.
Open the Other Settings tab.
In the Support utility section, click Launch.
In the Veeam ONE Settings menu, select Scalability.
Choose the necessary data collection mode and click Save.
Restart Veeam ONE Monitor Server and Veeam ONE Reporter Server services.

NOTE that the previously collected data will not be revisited.

More Information

For the list of settings and metrics affected by the deployment mode change, please refer to this deployment guide page.

If you have any questions, contact Veeam Support.

Challenge

Understanding the difference between Typical and Advanced scalability modes.

Cause

Depending on the size of the managed virtual environment, you can choose of the following Veeam ONE installation types:

Typical — this type of installation is recommended for small to medium environments, with up to 100 hosts and 1500 VMs
Advanced Scalability — this type of installation is recommended for large environments with more than 100 hosts and 1500 VMs

Installation type is defined by a set of configuration parameters that determine Veeam ONE behavior in a number of areas, such as data collection and other. Choosing the appropriate installation type allows you to optimize monitoring and reporting performance and improve user experience in Veeam ONE.

Solution

To switch between the modes, on Veeam One server run "C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe" > Deployment Configuration > Save > Restart Veeam One Monitor and Veeam One Reporter services.

NOTE that the previously collected data will not be revisited.

User-added image

More Information

Changing between data collection modes affects the following Veeam ONE settings.

Configuration Option	Description	Optimized for Typical Deployment	Optimized for Advanced Scalability Deployment	Backup Data Only
VMware real-time performance	Timeout for collecting VMware vSphere real-time performance data.	300 seconds (5 minutes)	1200 seconds (20 minutes)	300 seconds (5 minutes)
VMware real-time performance	Sampling renewal interval for real-time counters.	20 seconds	900 seconds (15 minutes)	20 seconds
VMware historical performance	Sampling renewal interval for historical counters (older than one hour).	5 minutes	30 minutes	5 minutes
VMware historical performance	Sampling renewal interval for historical counters (older than one week).	2 hours	2 hours	2 hours
MinTreeCheckInterval	Updating the object inventory tree in Veeam ONE Monitor.	10 seconds	1 minute	10 seconds
PageUpdateDelay	Loading data after choosing an object in the object inventory tree.	0.5 second	1.5 second	0.5 second
GetVmsnapshottimeout	Timeout for collecting data about VM snapshot files from datastores.	900 seconds (15 minutes)	3600 seconds (1 hour)	900 seconds (15 minutes)
Collectthreadtimeout	Timeout for collecting data from servers by Veeam ONE Reporter.	6 hours	12 hours	6 hours
DahboardCapturetimeout	Timeout for capturing the dashboard for a scheduled dashboard delivery.	3600 seconds (1 hour)	7200 seconds (2 hours)	3600 seconds (1 hour)
Virtual machines files data collection	Collecting information about VM files (for the Garbage Files report).	Yes	No	No

For new modes implemented with version 9.5, refer to this KB article.

Challenge

When Backing up or Replicating the Veeam Server, some considerations must be taken before beginning the operations.

Cause

Depending on the settings of the Backup and Replication jobs, the backups and/or replicas containing the Veeam Database may not be consistent with changes made to the production database since the last run of the jobs. Should recovery or failover be required, you may require Veeam Support's assistance before the servers can take over normal operations.

Solution

Preparation: The server hosting the Veeam Database should be processed in isolation from other jobs, ideally when no other data is processing. The server hosting the Veeam Database should have sufficient resources to ensure that VSS processing is fast and does not cause interruptions.

On Restore or Failover: It is recommended that you rely primarily on the built in Configuration Backup as a means for backing up and recovering the Veeam Configuration. This will preserve the current state of the Veeam Database and all job and infrastructure related configurations within Veeam.

If the Configuration Backup was taken more recently than the last backup or replica, be sure to Restore from the Configuration Backup to ensure that the most recent state of the Veeam Database is used.
You may need to contact Veeam Support for assistance should you experience any difficulties when restoring from a backup or failing over to a replica of the Veeam Server/Database.

Challenge

This article provides a method to change the repository where backup files are stored.

Solution

To manually move Veeam Backup and Replication backup files and continue using the same job to create a new backup chain, follow these steps:

1. In Backup Infrastructure > Backup Repositories, create a new repository for the new location where backup files will be located.

2. Manually move the backup files to the new repository path. This should include the Metadata file (.vbm), the needed full backup files (.vbk), and any needed incremental files (.vib or .vrb).

It is recommended to move all backup files, but you can omit incremental files if needed.

If you decide to not move/copy all backup files to the new storage, you will need to use the “Forget Missing Restore Points” setting to clear any references to backup files that were not moved/copied
User-added image

The Forget Missing Restore Points setting can be found here: https://helpcenter.veeam.com/docs/backup/vsphere/remove_missing_point.html?ver=95

Also keep in mind that there will be folders created inside the directory/path for job names.

If your repository is declared as E:\Backups, Job A will go to E:\Backups\Job A.

3.Rescan the new repository.
User-added image

4. If your backup files are encrypted, you will need to specify the password under Backups > Encrypted on the Backup and Replication tab. If your backup files are not encrypted, skip this step.

5. Edit the backup job. Go to the Storage tab, and from the drop down menu, select the new repository.
User-added image

If you encounter the following error: “Move all backup files to the new backup repository first”. You may have left the backup files in the original location.

When encountering this error, follow the steps outlined below to map to the backup files in the new repository.

To map the existing backup files to a new or different job, follow these steps:

1. Under Backups > Disk, right click the job you are changing repository for, and do either Remove From Backups (v8) or Remove from Configuration (v9).
User-added image

2. In Backup Infrastructure > Backup Repositories, create a new repository for the new location where backup files are located if you have moved the backup files. If you have not moved backup files to a new location, skip this step.

3. Rescan the repository where the backup files are located.
User-added image

4. If your backup files are encrypted, you will need to specify the password under Backups > Encrypted on the Backup and Replication tab. If your backup files are not use encrypted, skip this step.

5. Edit the backup job. Go to the Storage tab, and from the drop down menu, select the repository if it has changed in Step 2.
User-added image

6. Click Map Backup and select the existing backup chain
User-added image

More Information

If you are attempting to manually seed a backup copy job, please see the following KB: https://www.veeam.com/kb1856

Challenge

You need to move Veeam Backup & Replication software and database to a new server.

Solution

Note: This section will refer to the server where Veeam Backup & Replication is installed prior to the move as the “old server”, and the location after the move as the “new server”.

Performing migration using Configuration Backup:

Perform the following steps on the old server:
1. Stop and disable all jobs.
2. Perform configuration backup:
http://helpcenter.veeam.com/backup/80/vsphere/index.html?vbr_config_manually.html?ver=95
3. Close Veeam GUI and stop all Veeam Services.

Perform the following steps on the new server:

1. Install Veeam Backup & Replication with a brand new DB.
2. Apply the latest patch to Veeam Backup & Replication: http://www.veeam.com/patches.html
3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
4. Perform configuration backup restore:
http://helpcenter.veeam.com/backup/80/vsphere/index.html?vbr_config_restore.html?ver=95
Note: It will be necessary to re-enter the password for every account during restore of non-encrypted configuration backups.
5. Run a test job to make sure everything moved correctly.

Performing migration if Configuration Backup is not available:
Note: Use this option only if Configuration Backup is not available. If encryption was used on the previous installation, a newly installed backup server will not be able to decrypt such information if attached to the existing database, so any encrypted information will have to be supplied manually – existing encrypted backups have to be re-imported to provide the password.

Perform the following steps on the old server:

1. Stop and disable all jobs.
2. Close Veeam GUI and stop all Veeam Services.
3. Create backup of the SQL database. (http://www.veeam.com/kb1471)

To find out where the VeeamBackup database is located, open regedit on the old server and navigate to:
HKLM\SOFTWARE\Veeam\Veeam Backup and Replication

There you will find 3 dword values:

- SqlServerName
- SqlInstanceName
- SqlDatabaseName

Perform the following steps on the new server:

1. Install Veeam Backup & Replication with a brand new DB.
2. Apply the latest patch to Veeam. http://www.veeam.com/patches.html
3. Make sure all local drives that were being used as repositories on the old server are now attached with the same drive letters on the new server.
4. Restore the Veeam database to the instance on the new server or on a SQL server which will host Veeam DB. (link)
5. To associate Veeam with the restored database, please use the DBConfig Utility to change the DB and settings that Veeam is connecting to.
Please refer to this user guide page on using the DBConfig Utility:
https://helpcenter.veeam.com/docs/backup/hyperv/using_dbconfig_utility.html?ver=95
6. Restart Veeam Services to apply the changes.
7. Open the Veeam console and using the “Manage Credentials” button from the main menu and check the passwords for every account to confirm they are up to date.
8. Run a test job to make sure everything moved correctly.

More Information

In situations where physical local storage is used please see the following KB that details how to relocate Veeam Backup and Replication backup file locations: https://www.veeam.com/kb1729

For steps on migrating the Veeam database to another SQL Instance or Server, please refer to KB 1250:
https://www.veeam.com/kb1250

Cause

Identify with what bandwidth the WAN Accelerator feature within Veeam Backup & Replication will be most effective and calculate the needed Cache sizes for both Source and Target WAN Accelerators.

Solution

As a general rule we recommend the following guidelines for deciding when to use WAN accelerator and for setting expectations for performance:

Global Cache on Spinning Disk
Link <3Mb/s - WAN likely saturated; processing rate dependent on data reduction ratio (estimated 10x)
Link >3Mb/s and <50Mb/s - WAN will not be fully utilized; expect ~5MB/s processing rate but less bandwidth
Link >50Mb/s - WAN will not be fully utilized, using direct mode copy will use more bandwidth but likely be faster

These numbers are to be considered as a base line , “Your mileage may vary”. The performance of the underlying storage where the Global Dedupe Cache is located can greatly impact the performance of the WAN Accelerator function.
Tests show that there are no significant performance differences in using spinning disk drives as storage for the target WAN accelerator cache rather than flash storage. However, when multiple source WAN accelerators are connected to a single target WAN accelerator (many-to-one deployment), it is recommended to use SSD or equivalent storage for the target cache, as the I/O is now the sum of all the difference sources.

WAN Accelerator Cache/Digest Provisioning

If we assume that we have 3 VMs, each with unique OSes (for instance, Win 2008R2, Win 2012R2, Solaris 10) each OS requires 10GB to be
allocated for it. The Cache itself is wholly independent from the digests required. That is, the Veeam GUI does not make any determination of
how much you can allocate for a digest and so on. The digest is essentially an indexing of what cached blocks go where. For digest size, 1TB of
VM disk capacity we are backing up should correspond with 20GB of disk space. That is, for 10VMs we are backing up whose capacity is 2TB, you
must account/allocate 40GB for digest data on the Source WAN Accelerator. This limitation is also applied to the Target WAN Accelerator.

Right click on the image to save it to your computer.

Right click on the image to save it to your computer.

For a Many-to-1 setup, the global cache is calculated per 1 Source WAN Accelerator working with the Target WAN Accelerator. Therefore, the
global cache needs to be increased proportionally. If we use the same VMs in the previous example, the cache is only required to be 30GB.
However, since we’re using 3 Source WAN Accelerators, the cache size must be 90GB in response. On the Target WAN Accelerator, not only is the
cache size dictated by the amount of Source WAN Accelerators, but so is the Digest on the target end—in this example, we require 120GB of Digest
space, which added to the cache size (90GB) results in requiring a 210GB volume size at a minimum.

More Information

https://helpcenter.veeam.com/docs/backup/vsphere/wan_accelerator_sizing.html?ver=95
https://helpcenter.veeam.com/docs/backup/hyperv/wan_accelerator_sizing.html?ver=95

Challenge

Veeam Backup and/or replication jobs report that changed block tracking is not working properly.

Solution

Ensure Veeam Backup & Replication is running on the latest build. Latest patches will be visible on the download page for Backup & Replication (https://www.veeam.com/vmware-esx-backup/download.html). You will need to login to the Veeam Customer Portal to obtain any patch.

For a warning message stating “failed to flush changed block tracking” when backing up VMs on a Hyper-V cluster:

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.

If the VMs reside on SMBv3 storage:

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).
Changed block tracking can be reset for a Hyper-V cluster by performing the following steps, should the information above not resolve the issue. To reset changed block tracking, please perform the following:

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

This article describes the procedure of moving a Veeam Backup for Microsoft Office 365 v1.5 server installation to a new server.

Solution

Prerequisites:
The following prerequisites are required to carry out the procedure:

The new server ready for VBO installation should have the same version of Windows
If the repository is a network share, then the target server should have access to that share.
If the repository is an iSCSI drive then it is important to disconnect it from the source first to avoid the two iSCSI initiators issue. Then connect it to the target server.
Your license file should be available.

Procedure:
Veeam Backup for Microsoft Office 365 server migration.

Install the same version of Windows on the new server.
Install Veeam Backup for Office 365 on this new server.
Stop all the VBO services on the original site before moving any data.
Copy the repository data to the repository location on the new server.
Add the repository (from new location) to the new server.
Add the same organization on the new server.
Add a proxy from the original site (optional):

a. Stop all backup jobs that are running on a proxy;
b. Open backup job settings and specify to use another proxy;
c. Remove the proxy from the original VBO365 console;
d. Add the proxy to the new VBO365 server.
Please note: Backup proxy server and Veeam Backup for Microsoft Office 365 server must be deployed within the same or a trusted domain.

Create a backup job and point it to the added repository.
Run your job(s) to see if they succeed.
Run a test restore from a restore point created on the old VBO server to verify that you can recover.

Note: Restore points from the previous VBO server are available as soon as the organization is added to the console.

More Information

Migrating a remote proxy to another host (optional):

1. Stop all backup jobs that are running on a remote proxy.
2. Open backup job settings and specify to use another proxy.
3. Remove the current remote proxy from the VBO365 console.
4. Copy the repository data from the current proxy to a new proxy to the path where the new repository is planned.
5. Add a new remote proxy in the VBO365 console.
6. Add a new repository (specifying the path from step 4) which is associated with the new remote proxy.
7. Open backup job settings and specify to use the new remote proxy if needed.

Challenge

The Update cannot be installed. The installation fails with the error message:

"The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)"

Cause

Veeam ONE websites do not have proper bindings on the Internet Information Services (IIS) side.

Solution

To fix the issue:

1. Open IIS Manager on the Veeam ONE server
2. On the left panel locate the Veeam ONE websites
3. Right-click on the VeeamBusinessView website and select "Edit Bindings" option
4. In the opened window click on the "Add" button
5. Configure the following settings:

Type: HTTPS
IP address: All Unassigned
Port: 1239 (for reporter website), 1340 (for business view website)
Hostname: blank
SSL certificate: Veeam Self-Signed Certificate

6. Do the same steps for VeeamReporter website

7. Start Veeam ONE websites:
Right-click > Manage Website > Start 
8. Install the Update file.

More Information

Should you have any questions, contact Veeam Support.

Challenge

The "Sort by Size" option does not work in the following reports properly:

Virtual Machines. Snapshot Summary (Veeam VMware Analysis Reports pack)
Virtual Machines. Checkpoint Summary (Veeam Hyper-V Analysis Reports pack)

Cause

This is a known issue with the sorting function.

Solution

Please confirm you are running Veeam Management Pack 8.0 Update 5 prior to installing this hotfix. You can check this in Operations Manager console under Administration | Management Packs, the build number should be 8.0.0.2451 or later.

To install the hotfix, import the updated management packs through Operations Manager console > Administration > Management Packs > Import Management Packs.

To obtain Veeam MP 8.0 for System Center - Update 5, please download it here.

More Information

[[DOWNLOAD|DOWNLOAD CUMULATIVE HOTFIX|https://www.veeam.com/download_add_packs/vmware-microsoft-esx-monitoring/kb2643/]]

MD5 checksum for KB2643.zip is 14EF1916D79D68840C8A5122B6A6F5BE

Should you have any questions, contact Veeam Support.

Challenge

During Exchange 2010 application aware backup with “Copy only” option enabled you notice following events in Application event log on Exchange server:

Log Name: Application
Source: MSExchangeIS
Date: 5/10/2018 5:38:39 PM
Event ID: 9782
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Computer: Exchange2010
Description:
Exchange VSS Writer (instance 7333fe6c-94b5-4d0f-b62f-517eec18e04d:2) has completed the backup of database '<Database name>' with errors. The backup did not complete successfully, and no log files were truncated for this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeIS" />
<EventID Qualifiers="49193">9782</EventID>
<Level>2</Level>
<Task>41</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-05-10T14:38:39.000000000Z" />
<EventRecordID>1801912</EventRecordID>
<Channel>Application</Channel>
<Computer><Server name></Computer>
<Security />
</System>
<EventData>
<Data>7333fe6c-94b5-4d0f-b62f-517eec18e04d:2</Data>
<Data><Database name></Data>
<Binary>436F707900</Binary>
</EventData>
</Event>

Cause

Copy only backup does not perform transaction logs truncation which may result in the mentioned event being generated.

Solution

Event can be safely ignored.

Challenge

A user needs to restore a VM across a WAN connection or a location where choosing a specific proxy would allow the restore to work faster.

Cause

A VM is down and needs restored as fast as possible.

Solution

During a Full VM restore you can choose which proxy processes the restore. On the Restore Mode page there is an option to pick the proxy you use to perform the restore. See image below.

User-added image

More Information

Here is more information on Veeam Proxies. http://www.veeam.com/vmware-backup/help-center/vsphere/index.html?backup_proxy.html

Challenge

Product Information:

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

Solution

Product Details:

Model number: B4260
Number of Drives: 15/240
Drive type: SSD/NL-SAS
Firmware version: 1.3.3.1
Connection protocol and speed: 10Gb
Additional support: Any hardware configuration with an equal or greater hardware configuration

General product family overview: InfiniGuard™ - Petabyte Scale Data Protection with Lightning Fast Recovery. InfiniGuard features a fast, reliable data backup and restore for business continuity / disaster recovery. InfiniGuard is built with InfiniBox to optimize the backup and restore performance and to maximize effective capacity for multi-petabyte datasets. InfiniGuard maximizes deduplication efficiency through using an innovative inline & variable block size deduplication technology. InfiniGuard supports the NFS, CIFS, and VTL protocols and offers deep integration with VEEAM Backup & Replication software by creating a VEEAM repository on the InfiniGuard system and a VEEAM agent that runs inside the InfiniGuard process-space, maximizing efficiency.

Vendor Veeam testing configuration:

Veeam Build Number: 9.5.0.1536
Veeam Settings:

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

More Information

Company Information:

Company name: INFINIDAT
Company overview: INFINIDAT was founded in 2011 by a team of storage industry experts focused on helping customers to eliminate compromises between cost, capacity, functionality and performance when it comes to their storage and backup infrastructure, enabling them to focus more on what makes them competitive.

Challenge

To allow communications between Veeam Agents and VBR, TLS certificates are used. By default, Veeam Backup & Replication uses a self-signed certificate.

User-added image

Solution

In order to use a certificate signed by Certification Authority (CA), the following requirements should be met:

Veeam Agents must trust the Certification Authority and the VBR signed certificate (they must be added to the Trusted Root Certification Authority store on the clients)
Certificate revocation List (CRL) should be accessible from Veeam Agents and VBR server

A certificate signed by Certification Authority should have the following key usage to sign and deploy child certificates on Veeam Agents:

Digital Signature
Certificate Signing
Off-line CRL Signing
CRL Signing (86)

E.g., a subordinate CA Certificate template in Windows has the required key usages:

User-added image

After applying the signed certificate on the VBR server according to - https://helpcenter.veeam.com/docs/backup/agents/agents_import_ssl.html?ver=95 , on the next job run Veeam Agents will receive child certificates. The resulting certification path will look like this:

User-added image

More Information

Note: Veeam Agent for Microsoft Windows version 2.1 has a known issue with CRL check if a signed certificate is installed on the VBR server. Please contact technical support in order to obtain a fix.

Challenge

Management Pack fails to display a segment of the environmental topology or a portion of performance information. The vmspi.log (default location: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log) contains the following entries:

+** [VP038] buildInventory failed [***], The tasks array included at least one null element.
+** [VP050] performanceDaemon The tasks array included at least one null element.

Cause

In complex and highly distributed environments collector threads are stalled.

Solution

The hotfix ensures that stalled threads are processed properly. Download the hotfix here.

Follow these steps to apply the fix.

Stop Veeam VMware Collector service.
Make a backup of VeeamCollector.exe (default path: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector).
Unpack the downloaded .zip and replace VeeamCollector.exe with the executable from the archive.
Start Veeam VMware Collector service.

NOTE: In case you installed the Update 5 for Veeam Management Pack and the issue occurred again, reapply the hotfix from this KB article.

More Information

If you have any questions, contact Veeam Support.

Challenge

Management Pack fails to build the environmental topology. The vmspi.log (default location: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log) contains the following entries:

+** System.NullReferenceException: Object reference not set to an instance of an object. at nworksCore.TopologyNode.Clone()

Cause

Some host hardware objects may fail to return mandatory properties, such as NIC MAC address or NIC name. In this case Veeam Colelctor would fail to process such objects.

Solution

The hotfix prevents Veeam Collector from crashing and provides additional output about the object with missing properties.

Follow these steps to apply the fix.

Stop Veeam VMware Collector service.
Make a backup of VeeamCollector.Core.dll (default path: C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector).
Open a cmd prompt on the collector host and run the command:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe /u “<the collector folder path>\VeeamCollector.Core.dll”
In case you have several collectors, run the command for each one.
Unpack the downloaded .zip and replace VeeamCollector.Core.dll with the file from the archive.
Make sure that you have full access right to the replaced .dll file (Permissions: Full Control) and the Unblock option is not activated in the file properties (Properties: General).
Open a cmd prompt on the collector host and run the command:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe /i “<the collector folder path>\VeeamCollector.Core.dll”
"The transacted install has completed" message should appear in case of correct .dll installation. If you have several collectors, run the command for each one.
Start Veeam VMware Collector service.

NOTE: In case you installed the Update 5 for Veeam Management Pack and the issue occurred again, reapply the hotfix from this KB article.

More Information

[[DOWNLOAD|DOWNLOAD THE HOTFIX|https://www.veeam.com/download_add_packs/vmware-microsoft-esx-monitoring/kb2130/]]

MD5 checksum for KB2130.zip is 7f7ba9bd970563b8af0d8e7ef1a058a8

Should have any questions, contact Veeam Support.

Challenge

When attempting to update the Veeam Agent for Linux or veeam-release repository package, an error is encountered:

GPG key signature on key http://repository.veeam.com/keys/RPM-GPG-KEY-VeeamSoftwareRepo.asc does not match CA Key for repo: veeam

The following signatures were invalid: EXPKEYSIG 54706D7C5A382FCD Veeam Software Repository key support@veeam.com

Cause

Veeam repository GPG key has changed, import of a new key is required.

Solution

To resolve this issue please install new GPG keys manually.

For .deb based distributions:

curl http://repository.veeam.com/keys/veeam.gpg | apt-key add

For .rpm based distributions:

rpm --import http://repository.veeam.com/keys/RPM-EFDCEA77

More Information

Alternatively you can download and install the updated veeam -release package from the website or from the repository.

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 Case Administrator Management 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.

User-added image

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.

User-added image

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.

User-added image

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 20 Case Administrators per Support ID.

User-added image

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.

User-added image

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).

User-added image

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.

User-added image

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 belonging to the same account can view your licenses but cannot manage them
Case Administrators cannot view and manage other Case Administrators

Challenge

Solution

Challenge

Cause

Solution

Antivirus Exclusions:

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

Challenge

Solution

More Information

Challenge

Solution

More Information

Cause

Solution

As a general rule we recommend the following guidelines for deciding when to use WAN accelerator and for setting expectations for performance:

WAN Accelerator Cache/Digest Provisioning

More Information

Challenge

Solution

Challenge

Solution

Procedure:Veeam Backup for Microsoft Office 365 server migration.

Note: Restore points from the previous VBO server are available as soon as the organization is added to the console.

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

Challenge

Cause

Solution

More Information

Challenge

Product Information:

Solution

Product Details:

Vendor Veeam testing configuration:

More Information

Company Information:

Challenge

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Solution

How do you assign Case Administrators to a license?

How do you remove Case Administrators from licenses?

What rights do Case Administrators have?

Procedure:
Veeam Backup for Microsoft Office 365 server migration.