Veeam Support Knowledge Base

Challenge

Release Notes for Veeam Management Pack 8.0 Update 5

Cause

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

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

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

Solution

New in This Release

Support for Ops Mgr and SCVMM 1801
Veeam MP supports Microsoft System Center Operation Manager 1801 and System Center Virtual Machine Manager 1801.

Support for Windows Server 1709 Hyper-V
Veeam MP supports Windows Server 1709 Hyper-V. Windows Server 1709 Hyper-V hosts and clusters will be discovered and monitored by Veeam Hyper-V MP as described in the Veeam MP for Hyper-V User Guide.

Support for vSphere 6.5 TLS 1.2 protocol
Starting with vSphere 6.5, the TLS protocol version 1.2 is enabled by default. Veeam MP supports the new connection protocol for VMware monitoring.
To allow Veeam Virtualization Extensions Service and Veeam VMware Collectors to connect to vCenter Servers that use the TLS 1.2 protocol, you must update Veeam MP core services as described in the Veeam MP for VMware Installation Guide, or in the Veeam KB article.

Morning Coffee Dashboard for Veeam Backup & Replication infrastructure
This dashboard provides at-a-glance real-time overview of your Veeam backup infrastructure. The Morning Coffee Dashboard is available in the root Veeam for Backup and Replication folder.
The dashboard tracks the state of Enterprise Managers (if present), Backup & Replication servers, backup jobs, scale-out backup repositories and backup repositories, proxies, Veeam agents and the overall resource utilization, and immediately displays these changes in a single view.
For more information on the Morning Coffee Dashboard, see the Management Pack for Veeam Backup & Replication User Guide.

Support for Veeam Agent for Microsoft Windows 2.1 and later
Veeam MP discovers and monitors Veeam Agents for Microsoft Windows on all computers that run Veeam Agents and Ops Mgr agents. Within this workflow, Veeam MP provides new objects (Veeam Agents and Veeam Agent Jobs), performance metrics, service monitors, views and performance reports.
For the full list of new Veeam MP features implemented to support Veeam Agents for Microsoft Windows, see the Management Pack for Veeam Backup & Replication User Guide.

Support for Veeam Agent Backup Jobs
When Veeam Backup & Replication server deploys Veeam Agent for Microsoft Windows and Veeam Agent for Linux on computes in your infrastructure, Veeam Backup & Replication creates Veeam Agent Backup Jobs to back up these computers.
Veeam MP discovers and monitors the Veeam Agent Backup Jobs. Within this workflow, Veeam MP provides new performance metrics and state monitors, and extends the existing reports to represent performance and health statistics for the new job types.
For the full list of new Veeam MP features implemented to support Veeam Agent Backup Jobs, see the Management Pack for Veeam Backup & Replication User Guide.

Support for new snapshot storage types on Veeam Backup & Replication server
Veeam MP discovers snapshot storages (3PAR, Nimble, NetApp, IBM, Infinidat, Pure, Huawei and so on) and snapshot-only jobs running on Veeam Backup & Replication servers.

Extended vCenter Appliance monitoring visibility
The root Veeam for VMware folder now includes 2 new views to support vCenter monitoring: _vCenter alarms and _vCenter API Connections. For more information, see the Veeam MP for VMware Operations Guide.

Extended support for Hyper-V storage
Veeam MP includes new features to support Hyper-V storage:
•   New performance metrics for Hyper-V SMB shares and CSVs: Used Space GB and Used Space %.
•   New Performance Forecast for Hyper-V SMB Volumes report that forecasts space resource utilization for SMB shares.
•   Extended Performance Forecast for Hyper-V Cluster Storage report that allows you to forecast resource utilization for Cluster Shared Volumes.
For more information, see the Veeam MP for Hyper-V User Guide.

Support for new vCenter Service Lifecycle Manager service
Starting with vSphere 6.5, vCenter Server services run as child processes of the VMware Service Lifecycle Manager (vmware-vmon) service. Veeam MP provides new rules and monitors to watch the status of the vCenter Service Lifecycle Manager service and report on its performance metrics.

New vSan alarms
Veeam MP includes a set of monitors that track the state of vCenter vSAN alarms and allow you to check Virtual SAN clusters health status. For the full list of new monitors, see Veeam MP for VMware Reference.

New vCenter Server 6.5 alarm monitors
Veeam MP provides a number of new monitors to track vCenter Server 6.5 alarms. For the full list of new monitors, see Veeam MP for VMware Online Knowledge Base.

New dashboards for Veeam Backup Morning Coffee OMS
Veeam Morning Coffee Dashboard for Backup now uses data collected from the Ops Mgr to monitor the state of Veeam Agents and Veeam Agent backup jobs.

Updated Capacity Planning for Azure Hybrid Cloud report
The Capacity Planning for Azure Hybrid Cloud report takes into account new pricing politics for Microsoft Azure cloud resources.

Resolved Issues

All Platforms

Licensing issues
- Under certain circumstances, Veeam MP reports and dashboards started to ignore the Enterprise PLUS license and stopped working

Veeam MP for VMware
- Virtual Machines. Snapshot Summary report shows deleted snapshots
- VMware: Datastore Analysis monitors display incorrect description

Veeam MP for Hyper-V
- Network Switches temporarily represented with GUIDs instead of Network Switches names
- Cluster Disk Performance view does not display latency metrics

MP for Veeam Backup & Replication
- Veeam Backup & Replication retention policies cause Veeam MP dataset processing errors
- No target repositories displayed for snapshot-only jobs
- Protected VMs report considers all VMs to be Unprotected

More Information

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

Challenge

Starting with vSphere 6.5, the TLS protocol version 1.2 is enabled by default.

Cause

To allow Veeam Virtualization Extensions Service and Veeam VMware Collectors to connect to vCenter Servers that use the TLS 1.2 protocol, you must update Veeam MP core services.

Solution

NOTE:
The described procedure applies only to Veeam Virtualization Extensions Service and Veeam VMware Collectors version 8.0.

Update Veeam MP core services by completing the steps below on the machine that runs the Veeam Virtualization Extensions Service and on all machines running Veeam VMware Collector services.

1.   Insert the installation disc into the CD/DVD drive or mount the installation image.
2.   Navigate to the <installation media>\Update folder.
3.   Launch VeeamMP80_Update5_Patch1.exe.
4.   Click Next to start the installation.

User-added image

NOTE:
You will not be able to proceed to the Veeam MP patch installation process if Microsoft .NET Framework 4.5 is not installed. Download Microsoft .NET Framework 4.5 from the Microsoft website, and install it following the instructions provided by Microsoft.

5. Click Install and wait for the update installation process to complete.

User-added image

Challenge

Veeam Availability Console 2.0 Hotfix_1364

Cause

This update resolves the following issues that can be encountered with Veeam Availability Console (VAC) 2.0:

1) Veeam Availability Console server starts using 100% of CPU resources when registering a Company (aka tenant) from the Cloud Connect server.

2) Under certain conditions "Cloud Host Memory Quota" and "Company Cloud Host Storage Quota" alarms are not triggered after breaching the configured threshold.

3) Veeam Agent for Microsoft Windows disappears from the Veeam Availability Console UI after applying a backup policy.

4) Veeam management agents show "Out-of-date" as their version status.

5) Under certain conditions company owner may view failover plans that belong to a different company.

6) Reconfiguring a report may result in the "An item with the same key has already been added" error message.

7) When defining RPO in hours in the "VM without backup" alarm, values above 24 are converted into days.

8) Under certain conditions UsedStorageQuota and UsedTrafficQuota are reported incorrectly through RestAPI.

9) A failed job after a successful retry is still reported as "failed".

10) Under certain conditions RPO is reported incorrectly in the Protected Vms report.

11) Total Gross may not be correctly calculated when specifying VAT for managed services.

12) Tenant Used Storage may be calculated incorrectly in invoices when VMs are backed up to Cloud Connect repository.

13) Unable to delete a company from VAC UI if a tenant has been already deleted in Veeam Cloud Connect.

14) Compute Time Usage may be calculated incorrectly if the "per month" counter is specified.

15) Optimized powershell queries to Veeam Cloud Connect to decrease Veeam.Backup.Satellite processes count.

16) Backup policies may fail to apply against computers with Scandinavian locales due to a different datetime delimiter.

17) Under certain conditions a backup policy may fail to delete.

18) A Protected Computers report may fail to generate due to the total files path field for the File-Level Backup mode exceeding the allowed maximum. By default, backup jobs contain folder names along with their location.

Solution

Before you begin, confirm under Windows > Programs and features that the current product version is 2.0.1.1319 or later.

Download VAC 2.0.1.1364.

To install the fix:

1. Back up VAC database.
2. Log off VAC Web UI.

3. To install the server update, on the VAC server execute VAC.ApplicationServer.x64_2.0.1.1364.msp as administrator, or run this cmdlet as administrator:

msiexec /update c:\VAC.ApplicationServer.x64_2.0.1.1364.msp

4. To install the Web UI update, on the VAC Web UI server execute VAC.WebUI.x64_2.0.1.1364.msp as administrator, or run this cmdlet as administrator:

msiexec /update c:\VAC.WebUI.x64_2.0.1.1364.msp

5. Log in to VAC Web UI.

More Information

You can check whether the update installed successfully opening Windows > Programs and features.
The product version for Veeam Availability Console will be 2.0.1.1364 after applying the update.

Should have any questions, contact Veeam Support.

Challenge

After installing Veeam 9.5 Update 3, SQL logs are truncated during backup, but truncation task is still marked as success in job statistics. SQL Log Backup sessions complete with 0 KB transferred.

You can confirm if any SQL VMs are affected by this change by checking the Guest Helper log located on the Guest VM.

GuestHelper log location: \\GuestVM\c$\ProgramData\Veeam\Backup\VeeamGuestHelper_%date%.log

The specific error you will find in the GuestHelper log if affected is the following:

Description = The UPDATE permission was denied on the object 'backupset', database 'msdb', schema 'dbo'.

Cause

This is due to a change in required SQL Permissions in 9.5 Update 3. These permissions requirements were changed to resolve a previous issue with how Veeam sends requests to SQL to finalize database backup and log truncation. The specific change in permissions is that the msdb system database now requires db_datawriter role, whereas before this was not needed.

Required SQL Permissions for SQL log backup and truncation can be found here:
https://helpcenter.veeam.com/docs/backup/explorers/vesql_permissions.html?ver=95

Solution

To resolve this issue, please give the following SQL permissions to the account credentials specified to use for Guest Processing:

Sysadmin role, or the following can be used if you need to provide only minimal permissions:
- SQL Server instance-level roles: dbcreator and public
- Database-level roles: db_backupoperator, db_denydatareader, public
- For System Databases:
  - master - db_backupoperator, db_datareader, public;
  - msdb - db_backupoperator, db_datawriter, db_datareader, public
- Securables: view any definition, view server state
- For truncation of SQL Server 2012 or SQL Server 2014 database transaction logs, this account should have the db_backupoperator database role (minimal required) or the sysadmin server role.

Challenge

Veeam Availability Console 2.0 Hotfix_1364

Cause

Solution

3. To install the server update, on the VAC server execute VAC.ApplicationServer.x64_2.0.1.1364.msp as administrator, or run this cmdlet as administrator:

msiexec /update c:\VAC.ApplicationServer.x64_2.0.1.1364.msp

4. To install the Web UI update, on the VAC Web UI server execute VAC.WebUI.x64_2.0.1.1364.msp as administrator, or run this cmdlet as administrator:

msiexec /update c:\VAC.WebUI.x64_2.0.1.1364.msp

5. Log in to VAC Web UI.

More Information

Challenge

For troubleshooting or advanced configuration, you may need to log in to a Linux appliance deployed by Veeam Backup & Replication.

Linux appliances are used by Veeam Backup & Replication for several purposes:

In Surebackup, the Virtual Lab proxy appliance routes network traffic between isolated and production networks.
In Multi-OS File Level Restore, the proxy appliance mounts virtual machine disks.
In Cloud Connect Replication, the network extension appliances route traffic between tenant networks and service provider networks.

Solution

You must log in to the appliance as root. You can set a password in the credentials manager, or use the default password.

Setting Passwords

To set the password for the particular type of appliance, edit it in the credentials manager.

To set the password for Surebackup (Virtual Lab) and Multi-OS FLR appliances, edit the record with the description “Helper appliance credentials”.
To set the password for network extension appliances, edit the record with the appropriate description: “Tenant-side network extension appliance credentials” or “Provider-side network extension appliance credentials”. Only Cloud Connect Service Providers can set the password for provider-side appliances.

For Surebackup and Cloud Connect, you must re-deploy the appliance before you can use the new password. The multi-OS FLR appliance does not persist between restore sessions, so to use the new password you only need to close the file browser and restore again.

The password will be applied to all newly-deployed appliances. It is not possible to specify different passwords for different instances of the same appliance type.

Default Password (before version 9.5)

NOTE: Starting from Veeam 9.5, a default password is not used for all appliances but Cloud Connect NEA.

You can only use a default password if no password has been set in the credentials manager.

To determine the default password for a particular appliance:
1) Start with the appliance name as it can be seen in the infrastructure view in the hypervisor;
2) Replace any “.” or "_" or space or parenthesis with “-“, but skip a trailing - (if any);
3) Add “_r” to the end.

For example, if your appliance’s vm name is “network.extension_appliance(cloud connect)”, the default password would be “network-extension-appliance-cloud-connect_r”.

Challenge

VeeamZIP began using a license up in paid versions after 9.5.0.1536.

Cause

This was expected behavior, but the decision has been made to change this behavior in order to allow users to back up VMs with VeeamZIP without using a license.

Solution

This will be fully changed in future updates. There is a fix that will change the behavior in the current version of the software. Please contact support to retrieve this fix.

More Information

https://www.veeam.com/support.html

Challenge

In Surebackup, the Virtual Lab proxy appliance routes network traffic between isolated and production networks.
In Multi-OS File Level Restore, the proxy appliance mounts virtual machine disks.
In Cloud Connect Replication, the network extension appliances route traffic between tenant networks and service provider networks.

Solution

To set the password for Surebackup (Virtual Lab) and Multi-OS FLR appliances, edit the record with the description “Helper appliance credentials”.
To set the password for network extension appliances, edit the record with the appropriate description: “Tenant-side network extension appliance credentials” or “Provider-side network extension appliance credentials”. Only Cloud Connect Service Providers can set the password for provider-side appliances.

Challenge

This is a FAQ page for Veeam Managed Backup Portal (VMBP) to Veeam Availability Console (VAC) migration

Cause

Answers to common questions can be found below.

Solution

Can I upgrade Veeam Managed Backup Portal (VMBP) or VAC Beta to VAC GA?

-   No, we can migrate and install the product to a new VAC server but upgrading over an existing installation is not supported in the GA release.

What versions can be migrated?

-   Currently the version requirement for migration is VMBP 1.0.0.295 or 2.0.0.317. Migrating from the VAC beta is not supported.

Can it be installed on the same server as VMBP?

-   No, you must perform a clean installation of Veeam Availability Console. Do not configure the cloud infrastructure and do not connect the Veeam Cloud Connect server to Veeam Availability Console.
-   Migration is server to server, not on a local install level.
-   Do not uninstall VMBP until you complete the migration process. If VMBP is uninstalled, there will be no way to recover the configuration. A fresh setup of VAC will be required.

How do I install the migration tool and where is it located?

-   Log on to the machine that runs Veeam Managed Backup Portal with a Local Administrator account. Make sure that the Local Administrator accounts on the VMBP and VAC servers have the following rights:

Impersonate a client after authentication
Allow log on locally
Access this computer from the network

-   The installer for the tool is located on the Veeam Availability Console ISO in a folder named Tools.
-   Launch the VAC.MigrationTool setup file.
-   Follow through the steps of the installation wizard.
-   At the last step of the wizard, click Install.
-   VAC Migration Tool installation will start.
-   When the installation completes, click Finish to close the wizard.

More Information

Our official migration guide can be found here.

Challenge

Applying this update to a Veeam Availability Console (VAC) Azure Appliance fails with: "A newer version of this application is already installed on this computer. If you wish to install this version, please uninstall the newer version first. Click OK to exit the wizard."

Cause

Azure appliance installation requires SQL Server name hosting VAC database to be explicitly specified.

Solution

1. Log in to the VAC web UI and navigate to Configuration > Settings > SQL Server Connection.
2. Change Server name from localhost\veeamsql2012 to <servername>\veeamsql2012

3. Apply the update.

More Information

If you have any questions, contact Veeam Support.

Challenge

Migration of Veeam ONE server is needed to install (upgrade) the product on a supported OS.

Cause

The previous version of Veeam ONE was installed on one of the operating systems that is no longer supported by the most recent Veeam ONE version.

Solution

Before you upgrade, be sure to perform a backup of the corresponding SQL database for Veeam ONE, so that you can easily go back to previous version in case of issues with upgrade.

If Veeam ONE is installed on one of the operating systems that is no longer supported by the most recent Veeam ONE version, use the upgrade procedure provided below:

Deployment with a local SQL Server:

1. Stop all Veeam ONE services.

2. If there were any changes made to Veeam registry configuration, export these registry hives manually:

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service]

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise]

3. Back up Veeam ONE database using SQL Management Studio.

4. Install all system prerequisites on the new Veeam ONE server. This procedure can be performed by running Veeam ONE setup wizard.

5. Download and install SQL Server 2012 R2 or above on the new Veeam ONE server.

6. Restore the backed up Veeam ONE database (step 3) to the new server via SQL Management Studio.

7. Run Veeam ONE installation wizard on a supported OS and point to existing SQL Server instance on the database configuration step. Veeam ONE database will be upgraded automatically.

8. Launch Veeam ONE Monitor Client and retype connection account settings to all monitored hosts.

9. Import Veeam ONE configuration registry keys to the new server. This step is not required, if Veeam ONE installation is running with the default settings.

10. Restart Veeam ONE services.

Deployment with a remote SQL Server:

1. Stop all Veeam ONE services.

2. If there were any changes made to Veeam registry configuration, export these registry hives manually:

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service]

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Reporter Enterprise]

3. Back up Veeam ONE database using SQL Management Studio to be able to revert to the previous version of the database in case of issues with upgrade.

4. Run Veeam ONE installation wizard on a supported OS and point to the remote SQL Server instance on the database configuration step. Veeam ONE database will be upgraded automatically.

5. Launch Veeam ONE Monitor Client and retype connection account settings to all monitored hosts.

6. Import Veeam ONE configuration registry keys to the new server. This step is not required, if Veeam ONE installation is running with the default settings.

7. Restart Veeam ONE services.

More Information

Should you have any questions, please contact Veeam Support.

Challenge

Run Veeam Backup and Replication database or Veeam Enterprise Manager database in SQL AlwaysOn Availability Group

Solution

If you want to deploy the Veeam Backup & Replication database (default name VeeamBackup) in SQL AlwaysOn Availability Group, then after running Veeam Backup & Replication setup you should do the following:

Manually add the VeeamBackup database to the corresponding SQL AlwaysOn Availability Group.
On the Veeam backup server, in the registry at HKEY_LOCAL_MACHINE\Software\Veeam\Veeam Backup and Replication specify the AlwaysOn Availability Group listener as the SqlServerName value.

in a similar vein, you can deploy Veeam Enterprise Manager database (default name VeeamBackupReporting) in SQL AlwaysOn Availability Group:

Manually add the VeeamBackupReporting database to the corresponding SQL AlwaysOn Availability Group.
On the Enterprise Manager server, in the registry at HKEY_LOCAL_MACHINE\Software\Veeam\Veeam Backup Reporting specify the AlwaysOn Availability Group listener as the SqlServerName value.

Please be advised that SQL AlwaysOn Availability Groups require the databases to be in Full Recovery mode. Veeam Backup and Replication does not currently truncate it's own database, as we expect it to be in simple recovery mode. This will require you to manually truncate the SQL log file to ensure it doesn't grow too large.

More Information

Contact your database administrator, if necessary.

Challenge

Some of VMware features and permissions are not granted by default at the start of VMware Cloud on AWS (VMC). Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases for VMware Cloud on AWS, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.

Solution

UPDATE: New VMware Cloud on AWS V1.3 (M3) requires updated Veeam Backup & Replication components. Please download the patch for Veeam Backup & Replication 9.5 Update 3 here (instructions included).

Affected Veeam Feature	Limitation	Workaround
Instant VM Recovery	Currently, VMware Cloud on AWS (VMC) does not allow for NFS usage	Use IVMR from a backup copy on-premises. Use a combination of a Veeam backup job and replication job for proactive restore capabilities
Other OS File Level Recovery	Currently, VMC does not allow for NFS	Start Linux File-Level Recovery from a backup copy on-premises
Quick Migration	Quick Migration cannot migrate VMs to VMC if they are running	Use Veeam Replication and permanent failover to achieve similar functionality For Free Edition, shutdown the VM before migration
SureBackup, Sure Replica, OnDemand Labs, Virtual Lab	Currently, VMC does not allow NFS and network manipulation	As for SureReplica, you can perform it if the replication target is a non-VMC vSphere environment (e.g., replicate VM from VMC to on-premises)
VM Guest Interaction and Windows File Restore by VIX or WebService API	Currently, VMC does not allow usage of VMware Webservice API	If you want to perform Veeam Guest processing or Windows File-Level Recovery, then connect to a VM over the network from Veeam Backup & Replication
VM Replication ReIP	ReIP is not available on VMC
Windows Dynamic disks are not supported	Currently, VMC does not allow to process dynamic disks at Hot-Add (Virtual Appliance mode) backup	VMware will provide a hotfix for this soon
Non-Unicode VM names	Currently, VMC does not allow non-Unicode characters for VM names within their APIs used ad VMC
VM Replication based File Level Recovery		Use file restore from backups or use a VM replica on a non VMC environment to start the File recovery

Problem

Impossible to add the VMware Cloud on AWS vCenter server to the managed server, or VMs within this vCenter are not visible in the list of VMs.

Solution

Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmc.vmware.com.

Problem

When working with Restore or VM Replication wizard, users may face some issues accessing VMware Cloud on AWS vCenter server.

Cause

By design, VMware does not provide customers access to the background infrastructure and used datastores.

Solution

For proper operation, you can select the specific areas marked as “Workload” or “Compute”. Avoid using the non-accessible areas, for example:

vsanDatastore datastore
Management VMs folder
Mgmt-ResourcePool resource pool

More Information

VMware Cloud on AWS Firewall Configuration

The Veeam Backup and Replication Server and Veeam proxy server should be connected to the VMware vCenter using HTTPS through TCP port 443. At VMware Cloud on AWS there is no need to open ports to the ESXi hosts itself. As the vCenter Server is by design of VMware Cloud on AWS on another network (Management Network) you need to implement a VPN tunnel to it or configure the following firewall settings:

Open Port TCP 443 from Backup Server and Proxy Server to the predefined vCenter object on the Compute Network.
Allow the Compute Gateway Public IP to communicate over TCP 443 with the predefined vCenter object on the Management Network.

To connect the EC2 Server(s) used as Veeam Repositories the following Firewall configuration is needed:

On the Compute Network
1. Open TCP 22 (SSH) port from Veeam Backup server and Veeam proxy server to the Amazon VPC where the EC2 Server was installed. You can as well define the exact IP addresses of the repository server as Destination.
2. Open TCP 2500-5000 ports for Veeam DAta Transport in both directions for same servers.
  It is recommended to use the ENI Network Tunnel to avoid any traffic costs
Open the same ports on the Inbound Firewall of the Amazon EC2 server used as repository server

Challenge

When opening a support ticket, Veeam Support might request upload of log file data.

Cause

These log files potentially contain information, that falls under the regulation of local data protection law like GDPR or similar.

Solution

The below are types of information in Veeam Backup & Replication log files Veeam considers as sensitive:

Usernames;
Customer specific infrastructure object names: hosts, datastores, VMs, clusters;
VM file names and paths;
FQDN/Hostname or NetBIOS names;
IP addresses: IPv4 and IPv6;
Customer specific paths to backup files;
Backup file names;
SharePoint information: DB names, paths to DBs, SP URL;
Exchange information: DB names, paths to DBs;
SQL information: DB and Instance Name, paths to DBs;
Oracle information: DB name, Home Name, Oracle SID, DB global name, paths to DBs;
File Copy: Customer specific paths and names of files;
File to tape: Customer specific paths and names of files.

Challenge

This KB article documents the procedure for restoring Application Items for Exchange 2003 and Exchange 2007. The Veeam Explorer for Microsoft Exchange does not support these versions of Exchange. In order to restore items for Exchange 2003/2007 you must use the SureBackup + U-AIR restore method.

Solution

Please Note:
• WebDAV must have been enabled on the Exchange 2003/2007 server when the restore point being restored from was created in order to restore using U-AIR.
• If WebDAV was not enabled, or you need a .pst, you can start the SureBackup job and use Outlook installed on the Veeam server to connect the Exchange server in the isolated network to export the data to PST.
• Veeam Backup & Replication must have an Enterprise or Enterprise Plus license to perform this restore.
• You will need the U-AIR wizard for Microsoft Exchange, this package does not come with Veeam Backup & Replication v8. You must contact Veeam Support (support.veeam.com) in order to acquire this package.
• As of April 2017, Microsoft no longer supports Exchange 2007. Therefore, Veeam Support can no longer assist with steps 7 and 8 of the below process.

Once you’ve downloaded the U-AIR Wizard, perform the following to process the restore:
This KB contains the SureBackup Configuration Guide for 8.x https://www.veeam.com/kb2047

1. Create a Virtual Lab.
     http://helpcenter.veeam.com/backup/80/vsphere/index.html?create_vlab.html
     https://www.veeam.com/videos/5-easy-sessions-for-modernizing-your-data-protection-configuring-your-first-virtual-lab-2110.html

2. Create an application group.
     http://helpcenter.veeam.com/backup/80/vsphere/appgroup_create.html

     Add to it the following servers in the order listed here:
     • Domain Controller w/ Global Catalog role
     • Exchange Mailbox server
     • Exchange CAS server (if separate).

     Note: In the application group settings, enable the "Domain Controller" role for the DC and remove all test scripts.
    For the Exchange server, leave all roles unchecked. Disable the IP boot verification tests on all servers in the application group, and set the application initialization timeout for all servers other than the DC to 0 seconds.

3. Create a Surebackup job.
     http://helpcenter.veeam.com/backup/80/vsphere/create_surebackup_job.html

     Configure it to use the Virtual Lab and Application Group configured in the previous steps.
     Note:
     • On the Application Group tab, enable the “Keep the application group running once the job completes” option.
     • Do not configure any Linked Jobs

4. Run the Surebackup job.
     Note: If you need to restore to a specific restore point choose the “Restore to…” option.

5. Wait for the job to report that all VMs in the SureBackup job are “Started”

6. Start the Exchange AIR Wizard.
     From an administrative command line, run the following command:

"C:\Program Files\Veeam\Application Restore\Exchange Restore\Veeam.AIR.Exchange.exe" /admin

7. Specify the DC and Account to be used for the restore.
     Use the Production DC IP address, and an account that has impersonation rights.

8. Specify the account to restore emails from.

9. Specify the Backup CAS.
     Use the masquerade address displayed within the SureBackup statistics window.

User-added image

10. Specify the Production CAS

11. Specify the CAS server version:

12. Complete the U-AIR Wizard
      The next steps are documented here:
      http://helpcenter.veeam.com/backup/70/uair/uair_exch_restore_mailbox.htm

13. Restore Complete and Cleanup
     After the restore is complete you will need to stop the SureBackup job manually.

More Information

Although Veeam v9 is no longer shipped with U-AIR wizards, this method can still be used with v9 and the Exchange AIR wizard from the previous version. To obtain the Exchange AIR v8, please contact Veeam Support.

Challenge

Job using Application-Aware Image Processing fails during VSS processing with:

Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{}]. Instance ID: [{}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Cause

This is a known issue documented in this Microsoft KB: http://support2.microsoft.com/kb/2987610

Solution

Run this query to see if the issue is present:

SELECT 1 FROM SYS.AVAILABILITY_REPLICAS AS AR INNER JOIN SYS.DATABASES AS D ON DB_ID(N'xxxx') = D.DATABASE_ID AND AR.REPLICA_ID = D.REPLICA_ID INNER JOIN SYS.DM_HADR_AVAILABILITY_REPLICA_STATES ST ON AR.REPLICA_ID = ST.REPLICA_ID AND ST.ROLE = 2

If you receive the following, this confirms the issue.

Invalid object name 'SYS.AVAILABILITY_REPLICAS'.

This issue is resolved by the following Microsoft KB: http://support2.microsoft.com/kb/2983175

Challenge

This article contains instructions on backing up your Veeam ONE SQL database.

Cause

This is useful when you have to do a backup before an upgrade or in case you have been asked to provide a backup of Veeam ONE database to Veeam Support for further in-depth analysis.

Solution

There are several ways of creating a backup of the database.

Using Veeam ONE Settings Utility (works for local SQL instances only)

To open Veeam ONE Settings utility use one of the options presented below:

Open VeeamOneSettings.exe in C:\Program Files\Common Files\Veeam\Veeam ONE Settings

Open the utility via Veeam ONE Monitor client > Options > Server Settings > Other Settings. Once you open the tab, you will find Support utility section. Click the Launch button.

To back up the Veeam ONE database to a .BAK file, click Create Backup and specify the location for the database backup file. User-added image

Using SQL Server Management Studio

Open Microsoft SQL Server Management Studio (may need to be installed separately KB1761).
Connect to the ServerName\Instance of the server that has the DB you want to back up.
Expand the Databases tab to get to the DB you want to back up.
Right click the desired DB > Tasks > Back Up.
Set Backup Type to Full
Specify the database file destination by choosing Back up to Disk option > Add the destination path to save the database backup.
Go to Backup Options and set Set backup compression to Compress backup to reduce the database file size (the option is not mandatory).
Click OK to start the Backup process.

Using SQL command line

In case you do not have the Management Studio installed, Veeam database can be collected using the SQLCMD utility:

Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam database name. Alternatively, check the same via Veeam ONE Settings Utility. See Using Veeam ONE Settings Utility (above) for access instructions.

Open Windows command line or PowerShell prompt and run the following command to create a backup file:

for default instances:

sqlcmd -S SqlServerName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

for named instances:

sqlcmd -S SqlServerName\SqlInstanceName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

Note: In case you have SQL server authentication enabled you may define username using '-U' parameter

sqlcmd -U Username -S SqlServerName\SqlInstanceName -Q "BACKUP DATABASE [DbName] TO DISK=N'C:\backups\VeeamONEDB.bak'"

Challenge

When attempting to update the Veeam Backup & Replication or Veeam ONE software, an error is encountered:
This Veeam Backup & Replication/Veeam ONE installation cannot be updated automatically. Please contact Veeam customer support for assistance with manual update.

Cause

Update setup program checks the digital signature of the existing files to ensure their integrity before updating them. All product files are signed using Global Sign certificates. Some Windows installations do not contain Global Sign's root certificates authority as trusted root certificates, or have non-current certificates. This issue is typically observed on servers with locked down security settings, or servers with no internet access or latest updates installed.

Solution

To resolve this issue, please install the below certificates manually on the system:
https://www.digicert.com/CACerts/DigiCertAssuredIDRootCA.crt (DigiCert Assured ID Root CA)
https://secure.globalsign.com/cacert/gscodesigng2.crt (GlobalSign CodeSigning CA - G2)
https://www.digicert.com/CACerts/DigiCertHighAssuranceEVRootCA.crt (DigiCert High Assurance EV Root CA)
https://www.digicert.com/CACerts/DigiCertEVCodeSigningCA-SHA2.crt (DigiCert EV Code Signing CA - SHA2)
https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates (install R1, R2, and R3 certificates)
If your backup server does not have internet access, please download certificate files from another computer.

More Information

To install a certificate:
Right-click on the certificate file in Windows, select "Install Certificate", install on "Local Machine", and select the store "Trusted Root Certification Authorities". When installed properly, "GlobalSign" and "GlobalSign Root CA" should show under Console root -> Certificates -> Trusted Root Certification Authorities -> Certificates.

User Added Image

Challenge

During upgrade/install, the following error occurs, preventing the installer from advancing:

 “Not all privileges or groups referenced are assigned to the caller”

Cause

This is caused by permission/assignment issues within the Global Policy settings. Specifically, the Debug Programs policy is not applied to the credentials being used to execute the installer.

Solution

Open Run and type in secpol.msc to bring up the Local Security Policies
Navigate to Security Settings > Local Policies > User Rights Assignment and locate the policy for “Debug programs”
Right Click the policy and select Properties
The credentials being used to run the install should be listed here, or be included in one of the groups listed.

More Information

Should you have any questions, contact Veeam Support.

Solution

The process for configuring email notifications with Veeam Agent for Windows is documented here.

https://helpcenter.veeam.com/docs/agentforwindows/userguide/settings_enable_email_notifications.html

More Information

For issues specific to using Gmail or Google Apps Mail for notifications, please reference: https://www.veeam.com/kb1974