Quantcast
Channel: Veeam Support Knowledge Base
Viewing all 4469 articles
Browse latest View live

Veeam One Reporter\Business View installation fails

$
0
0

Challenge

Veeam One installation\upgrade fails on the Reporter\Business View site deployment step.

Cause

Antivirus software may prevent applications from making changes to IIS, which is used by Veeam Reporter and Business View components to deploy their sites.

Solution

Disable antivirus software on the Veeam ONE server during the installation process. After the installation is successfully complete, enable the antivirus.
If the first solution does not help, please log in as Local Administrator and try the installation/upgrade again.

More Information

If you have any questions, contact Veeam Support.

No Data or Old Data in Reports

$
0
0

Challenge

Reports in Veeam ONE Reporter are showing no data or old data when generated

Cause

By default Veeam ONE is configured to run collection task at 3:00 am. Any data which comes after the task completion time will not be available in reports.

A failed Reporter collection tasks could cause the issue as well.

Solution

Running data collection manually

You can run data collection for Veeam ONE Reporter and Veeam ONE Business View manually. This can be required in cases when automatic data collection is disabled, the reports do not show any relevant information or if you want to collect data between scheduled collection sessions.

To manually start a data collection session:

  1. Open Veeam ONE Reporter.
  2. Open the Configuration section.
  3. In the Configuration section menu, click Servers.
  4. Select Object properties collection task and click the Run now button on the toolbar. 
You can also use Scheduling and set the collection start closer to the beginning of the business day. Generally the task can take up to 2 hours to complete. You can also schedule the tasks to run several times per day in case you would like to see the most recent data in reports.

NOTE: When you start Object properties collection task manually, Veeam ONE will collect the data from all connected servers.
NOTE: In case some of the tasks failed, open the Sessions tab and see the details by clicking on the most recent record.

More Information

If you have any questions, please contact Veeam Support.

Veeam ONE Free Edition is asking for a license file

$
0
0

Challenge

Veeam ONE will ask for a license file when running in the Free edition for longer than 90 days.  

Cause

This is due to software design. Veeam ONE requires a license file to run, regardless if it is a free license or a paid license.  

Solution

Go to http://www.veeam.com/monitor-free-key, and fill out the information to acquire your free license to run Veeam ONE Free edition. Once you have the license file, apply it via Veeam ONE Monitor client > Help > License information or Veeam ONE Reporter Web UI > Configuration > License.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.html

Veeam ONE v9.5 Required Ports and Permissions

$
0
0

Challenge

Ports and permissions must be configured for Veeam ONE to function properly.

Cause

The list of required ports and permissions can be found below.

Solution

Required Permissions

Connection to Virtual Servers

The account used to connect virtual servers must have at least the following permissions:

VI Object

Required Permissions

vCenter, ESX(i) host

  • Read-only
  • Host.CIM.CIM Interaction1
  • Host.Configuration.Connection1
  • Virtual machine.Interaction .Answer question2
  • vSphere Tagging.Assign or Unassign vSphere Tag3
  • vSphere Tagging.Create vSphere Tag3
  • vSphere Tagging.Create vSphere Tag Category3
  • Global.Global tag3 (not required for VMware vSphere 6.5)
  • Virtual machine.Interaction.Console interaction4
  • Datastore.Browse datastore5
  • Global.Licenses6

Note: Names of privileges are provided for the latest supported version of VMware vSphere, and may vary for different platform versions.

Hyper-V host, Hyper-V cluster

  • Administrator7

SCVMM

  • Delegated Administrator or Administrator

1 Required for gathering of ESX(i) host hardware data.
2 Required for using VM Console and viewing snapshot information.
3 Required for collecting and updating tags on the vCenter Server side. The privileges must be assigned at the vCenter Server level.
4 Required for accessing VM console from Veeam ONE Monitor.
5 Required for collecting datastore details.
6 Required for collecting license information.
7 A domain account with local Administrator privileges on a host is required. If you connect a cluster, the account must have local Administrator privileges on all hosts in a cluster.

NOTE: If Windows-based virtual servers run on non-domain machines, or machines with an unelevated local Administrator account, you must complete additional configuration steps to allow Veeam ONE perform data collection. For details, see Connection Under UAC.

Connection to Veeam Backup & Replication Servers

The account used for connecting to a Veeam backup server must have local Administrator permissions on the machines running:

  • Veeam Backup Enterprise Manager
  • Veeam Backup & Replication
  • Backup proxy, backup repository, WAN Accelerator, tape server and cloud gateway components (required to collect performance data from these servers)

NOTE: If Veeam backup infrastructure components run on non-domain machines, or machines with an unelevated local Administrator account, you must complete additional configuration steps to allow Veeam ONE perform data collection. For details, see Connection Under UAC.

Veeam ONE Service Account

The service account must have Local Administrator permissions on the machine where Veeam ONE is installed.

Authorizing with Veeam ONE

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

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

NOTE: In the advanced deployment scenario, you must assign the Allow log on locally privilege on the machines that host the Veeam ONE Server and Veeam ONE Web UI architectural components.

Connection to Microsoft SQL Server

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

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

Connection to Microsoft Hyper-V VM Guest OS

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

NOTE: To collect data from non-domain Windows VMs, or VMs with an unelevated local Administrator account, you must complete additional configuration steps to allow Veeam ONE perform data collection. For details, see Connection Under UAC.

Connection Under UAC

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

The affected configurations are:

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

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

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

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

  1. Configure Windows Remote Management.

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

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

Authorizing with Veeam ONE

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

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

NOTE: In the advanced deployment scenario, you must assign the Allow log on locally privilege on the machines that host the Veeam ONE Server and Veeam ONE Web UI architectural components.

Remote Access

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

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

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

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

Remote Access for Multi-Tenant Monitoring and Reporting

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

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


Required Ports

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

From

To

Protocol

Port

Notes

Veeam ONE

vCenter
ESX(i)

SSL

4431

Required to collect data from vCenter Server/ ESX(i) hosts. 
To learn how to check the current state of the vSphere API port, see the VMware vSphere documentation.

TCP

5989

Required to collect ESX(i) host hardware details via CIM XML.

TCP

10080
10443

Default port used to access vCenter Inventory Service (HTTP or HTTPS) and collect vCenter Server tags.

Required for vCenter Server 5.x only.

vCloud Director

SSL

4431

Required to collect data from vCloud Director.

SCVMM

TCP

8100

Default SCVMM Administrator Console to SCVMM server port (required by the Veeam ONE Service).

Hyper-V host

TCP

135,
dynamically assigned ports2

Required to collect data from Microsoft Hyper-V hosts through WMI.

TCP

135
445

Required to gather CPU and memory performance data from Microsoft Hyper-V hosts.4

TCP

445

Required to access remote registry.

Veeam Backup & Replication

TCP

135,
dynamically assigned ports2

Required to collect data from Veeam backup servers through WMI.

TCP

135
445

Required to gather CPU and memory performance data from Veeam Backup & Replication infrastructure servers.4

TCP

445

Required to access remote registry.

Veeam Backup Enterprise Manager

TCP

135,
dynamically assigned ports2

Required to collect data from Veeam Backup Enterprise Manager through WMI.

Veeam backup proxy

TCP

135
445

Required to gather CPU and memory performance data from backup infrastructure servers.4

Veeam backup repository

TCP

135
445

Required to gather CPU and memory performance data from backup infrastructure servers.4

Veeam WAN accelerator

TCP

135
445

Required to gather CPU and memory performance data from backup infrastructure servers.4

Veeam License Update Server (autolk.veeam.com)

TCP

443

Default port used for license auto-update.

Veeam ONE
Monitor Client

Veeam ONE Server

TCP

1393; 
4453

Used by Veeam ONE Monitor Client to communicate with the Veeam ONE Server.

UDP

1373

Workstation 
Web Browser

Veeam ONE Reporter

HTTP

1239

Required to access Veeam ONE Reporter console from a user workstation (a different port number can be chosen during setup).

Veeam ONE
Business View

HTTP

1340

Required to access Veeam ONE Business View console from a user workstation (a different port number can be chosen during setup).

 

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

Failed to load module [veeamsnap] (express version)

$
0
0

Challenge

When running a backup job in Veeam Agent for Linux, the job fails with this error message:
 
Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]

Cause

The veeamsnap module has not been built and installed.

Solution

The veeamsnap is a DKMS module. DKMS modules have 4 states:
  • not in tree;
  • added;
  • built;
  • installed.

In general, the mentioned error message means that the veeamsnap module hasn't been installed. You can check its status by running the following command:
dkms status

If the output contains a line like veeasnap added, this message means that the module has been added, but hasn't been built and hasn't been installed. In the most cases, this status means that your OS does not have the corresponding kernel-devel and kernel-headers for the current kernel. When the missing packages are installed, you can re-install Veeam Agent for Linux in order to execute the DKMS hooks which will rebuild and install veeamsnap. Alternatively, you can rebuild veeamsnap manually by executing the following commands:
dkms remove -m veeamsnap -v 1.0.0.944 --all

dkms build -m veeamsnap -v 1.0.0.944

dkms install -m veeamsnap -v 1.0.0.944

More Information

There is an extended version of this article here. It contains detailed explanations and examples applicable to different Linux distributions.

HCL - Dell EMC Isilon

$
0
0

Challenge

Product Information

Product Family: Dell EMC Isilon 
Status: Veeam Ready Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features. 

Solution

Product Details

Model number: All 
Number of Drives: Any 
Drive type: Any 
Firmware version: OneFS 8.0 
Additional support: Any EMC Isilon configuration with supported firmware. 
General product family overview: THE ISILON ADVANTAGE  
Dell EMC Isilon scale-out NAS is the ideal platform to store, manage and protect unstructured data efficiently while supporting a wide range of applications and workloads.  

Key advantages of Isilon scale-out NAS include:  
• Simple to manage: Single file system, single volume, global namespace  
• Massively scalable: Start small and scale to 10s of petabytes in a single cluster  
• Extreme performance: Support your most demanding file workloads with Isilon solutions that deliver up to 9 million IOPS and up to 540 GB/s aggregate throughput on a single cluster  
• Highly efficient: Over 80% storage utilization with data deduplication options to further reduce storage requirements by up to 30%  
• Ultra-dense hardware design: Provides 4 Isilon nodes in a single 4U chassis and reduces data center space requirements and related costs by up to 75%  
• Storage tiering: Optimize resources with policy-based, automated storage tiering to move data automatically to lower cost tiers, including cloud storage with a choice of cloud storage providers  
• Operational flexibility: Support a wide range of file workloads on a single platform with built-in multi-protocol capabilities including NFS, SMB, HTTP, FTP, and HDFS  
• Enterprise data protection: Isilon storage platforms are highly resilient, with up to N+4 redundancy, and offer proven enterprise-grade back-up and disaster recovery options  
• Robust security options: RBAC, Access Zones, SEC 17a-4 WORM compliance, File System Auditing, Data At Rest Encryption with SEDs, STIG hardening, CAC/PIV Smartcard authentication, and FIPS 140-2 validation  

 

Veeam Details

Veeam Build Number: 9.5.0.823 
Veeam Settings:  

  • Repository Type: Shared folder 
  • Deduplication: Yes 
  • Compression: Optimal 
  • Storage Optimization: LAN Target 
  • Per-VM Backup Files: Yes 
  • Decompress before storing: No 
  • Align backup file blocks: No 

More Information

Company Information

Company name: Dell EMC 
Company overview: Dell EMC, a part of Dell Technologies, enables organizations to modernize, automate and transform their data center using industry-leading converged infrastructure, servers, storage and data protection technologies. This provides a trusted foundation for businesses to transform IT, through the creation of a hybrid cloud, and transform their business through the creation of cloud-native applications and big data solutions. Dell EMC services customers across 180 countries – including 98 percent of the Fortune 500 – with the industry’s most comprehensive and innovative portfolio from edge to core to cloud. 

Veeam Agent for Linux Becomes Unresponsive on Debian

$
0
0

Challenge

When starting any backup job or log export, Veeam Agent  for Linux UI freezes and becomes unresponsive. The /var/log/veeam/Backup folder contains no log files for your configured backup jobs, the related folders are empty.  It may also be observed that veeamservice takes too much time to start/stop and becomes unresponsive.

Cause

It is possible that some of the dependent libraries are missing. The /usr/sbin/veeamjobman binary may not work properly if any dependent library missing. The example below contains the command that can be used to verify the root cause and the output generated in case a dependent library is missing.
 
root@debian:~# veeamjobman
veeamjobman: error while loading shared libraries: libmagic.so.1: cannot open shared object file: No such file or directory
root@debian:~#

The described behavior has been reproduced on Debian 7 and 8. For the most part, the minimal installations are affected.

Solution

The following workarounds are available at the moment.
  • Try to install a package that contains the missing library.
  • Upgrade the current system to the most recent update.
A package that contains the missing library can be found like this:
 
root@debian:~# apt-file find libmagic.so.1
libmagic1: /usr/lib/x86_64-linux-gnu/libmagic.so.1
libmagic1: /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0
root@debian:~#

Here is an example of installing a package that contains the missing library:

root@debian:~# apt-get install libmagic1

More Information

If you need assistance, you are welcome to open a support case with us. It will help if you can provide us with the following additional information.

Log in to shell as root and save the output ofthese commands:
 
dpkg -l
cat /etc/*release

 

Veeam ONE v9.5 Required Ports and Permissions

$
0
0

Challenge

Ports and permissions must be configured for Veeam ONE to function properly.

Cause

The list of required ports and permissions can be found below.

Solution

Required Permissions

Connection to Virtual Servers

The account used to connect virtual servers must have at least the following permissions:

VI Object

Required Permissions

vCenter, ESX(i) host

  • Read-only
  • Host.CIM.CIM Interaction1
  • Host.Configuration.Connection1
  • Virtual machine.Interaction .Answer question2
  • vSphere Tagging.Assign or Unassign vSphere Tag3
  • vSphere Tagging.Create vSphere Tag3
  • vSphere Tagging.Create vSphere Tag Category3
  • Global.Global tag3 (not required for VMware vSphere 6.5)
  • Virtual machine.Interaction.Console interaction4
  • Datastore.Browse datastore5
  • Global.Licenses6

Note: Names of privileges are provided for the latest supported version of VMware vSphere, and may vary for different platform versions.

Hyper-V host, Hyper-V cluster

  • Administrator7

SCVMM

  • Delegated Administrator or Administrator

1 Required for gathering of ESX(i) host hardware data.
2 Required for using VM Console and viewing snapshot information.
3 Required for collecting and updating tags on the vCenter Server side. The privileges must be assigned at the vCenter Server level.
4 Required for accessing VM console from Veeam ONE Monitor.
5 Required for collecting datastore details.
6 Required for collecting license information.
7 A domain account with local Administrator privileges on a host is required. If you connect a cluster, the account must have local Administrator privileges on all hosts in a cluster.

NOTE: If Windows-based virtual servers run on non-domain machines, or machines with an unelevated local Administrator account, you must complete additional configuration steps to allow Veeam ONE perform data collection. For details, see Connection Under UAC.

Connection to Veeam Backup & Replication Servers

The account used for connecting to a Veeam backup server must have local Administrator permissions on the machines running:

  • Veeam Backup Enterprise Manager
  • Veeam Backup & Replication
  • Backup proxy, backup repository, WAN Accelerator, tape server and cloud gateway components (required to collect performance data from these servers)

NOTE: If Veeam backup infrastructure components run on non-domain machines, or machines with an unelevated local Administrator account, you must complete additional configuration steps to allow Veeam ONE perform data collection. For details, see Connection Under UAC.

Veeam ONE Service Account

The service account must have Local Administrator permissions on the machine where Veeam ONE is installed.

Authorizing with Veeam ONE

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

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

NOTE: In the advanced deployment scenario, you must assign the Allow log on locally privilege on the machines that host the Veeam ONE Server and Veeam ONE Web UI architectural components.

Connection to Microsoft SQL Server

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

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

Connection to Microsoft Hyper-V VM Guest OS

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

NOTE: To collect data from non-domain Windows VMs, or VMs with an unelevated local Administrator account, you must complete additional configuration steps to allow Veeam ONE perform data collection. For details, see Connection Under UAC.

Connection Under UAC

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

The affected configurations are:

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

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

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

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

  1. Configure Windows Remote Management.

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

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

Authorizing with Veeam ONE

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

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

NOTE: In the advanced deployment scenario, you must assign the Allow log on locally privilege on the machines that host the Veeam ONE Server and Veeam ONE Web UI architectural components.

Remote Access

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

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

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

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

Remote Access for Multi-Tenant Monitoring and Reporting

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

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


Required Ports

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

From

To

Protocol

Port

Notes

Veeam ONE

vCenter
ESX(i)

SSL

4431

Required to collect data from vCenter Server/ ESX(i) hosts. 
To learn how to check the current state of the vSphere API port, see the VMware vSphere documentation.

TCP

5989

Required to collect ESX(i) host hardware details via CIM XML.

TCP

10080
10443

Default port used to access vCenter Inventory Service (HTTP or HTTPS) and collect vCenter Server tags.

Required for vCenter Server 5.x only.

vCloud Director

SSL

4431

Required to collect data from vCloud Director.

SCVMM

TCP

8100

Default SCVMM Administrator Console to SCVMM server port (required by the Veeam ONE Service).

Hyper-V host

TCP

135,
dynamically assigned ports2

Required to collect data from Microsoft Hyper-V hosts through WMI.

TCP

135
445

Required to gather CPU and memory performance data from Microsoft Hyper-V hosts.4

TCP

445

Required to access remote registry.

Veeam Backup & Replication

TCP

135,
dynamically assigned ports2

Required to collect data from Veeam backup servers through WMI.

TCP

135
445

Required to gather CPU and memory performance data from Veeam Backup & Replication infrastructure servers.4

TCP

445

Required to access remote registry.

Veeam Backup Enterprise Manager

TCP

135,
dynamically assigned ports2

Required to collect data from Veeam Backup Enterprise Manager through WMI.

Veeam backup proxy

TCP

135
445

Required to gather CPU and memory performance data from backup infrastructure servers.4

Veeam backup repository

TCP

135
445

Required to gather CPU and memory performance data from backup infrastructure servers.4

Veeam WAN accelerator

TCP

135
445

Required to gather CPU and memory performance data from backup infrastructure servers.4

Veeam License Update Server (autolk.veeam.com)

TCP

443

Default port used for license auto-update.

Veeam ONE
Monitor Client

Veeam ONE Server

TCP

1393; 
4453

Used by Veeam ONE Monitor Client to communicate with the Veeam ONE Server.

UDP

1373

Workstation 
Web Browser

Veeam ONE Reporter

HTTP

1239

Required to access Veeam ONE Reporter console from a user workstation (a different port number can be chosen during setup).

Veeam ONE
Business View

HTTP

1340

Required to access Veeam ONE Business View console from a user workstation (a different port number can be chosen during setup).

 

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


Failed to load module [veeamsnap] (express version)

$
0
0

Challenge

When running a backup job in Veeam Agent for Linux, the job fails with this error message:
 
Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]

Cause

The veeamsnap module has not been built and installed.

Solution

The veeamsnap is a DKMS module. DKMS modules have 4 states:
  • not in tree;
  • added;
  • built;
  • installed.

In general, the mentioned error message means that the veeamsnap module hasn't been installed. You can check its status by running the following command:
dkms status

If the output contains a line like veeasnap added, this message means that the module has been added, but hasn't been built and hasn't been installed. In the most cases, this status means that your OS does not have the corresponding kernel-devel and kernel-headers for the current kernel. When the missing packages are installed, you can re-install Veeam Agent for Linux in order to execute the DKMS hooks which will rebuild and install veeamsnap. Alternatively, you can rebuild veeamsnap manually by executing the following commands:
dkms remove -m veeamsnap -v 1.0.0.944 --all

dkms build -m veeamsnap -v 1.0.0.944

dkms install -m veeamsnap -v 1.0.0.944

More Information

There is an extended version of this article here. It contains detailed explanations and examples applicable to different Linux distributions.

"VM MAC address conflict" and "VM instance UUID conflict" alarms

$
0
0

Challenge

During replication jobs, Veeam ONE triggers the VM MAC address conflict and VM instance UUID conflict alarms.

Cause

When a VM replica is created, it acquires the same MAC address and UUID as the original VM. This situation is normal because a newly created replica is an absolute copy of the original VM with exactly the same properties.
After a short time, VMware vSphere changes replica’s MAC address and UUID.

Solution

This behavior is by design. However, if you do not want to receive the alarms, disable the VM MAC address conflict and VM instance UUID conflict alarms for source VMs or for the target location.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support

Not getting hardware sensor alerts in a timely manner

$
0
0

Challenge

You do not receive information about specific alerts regarding host hardware sensors quick enough for your environment, both in the Veeam ONE Monitor GUI and e-mails.  For example, a host goes offline and you do not get any alerts for 20 minutes. Or there is another delayed alerting between vCenter Server, or standalone host, and Veeam ONE Monitor.

Cause

Collection interval for host hardware sensor alerts is set to 30 minutes. If problems occur within this time interval, before data is collected, you can get delayed alerts. 

Solution

To resolve the issue, follow the next steps:
  1. On the Veeam ONE Server machine, change the collection interval in the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service
    Create a new DWORD value with the following properties:
    Name = HostRuntimeInfoUpdateInterval
    Base = Decimal
    Value = XXX, where XXX is the required timeout in seconds.

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

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

More Information

If you have any questions, please contact Veeam Support.

Restoring Deleted Alarms

$
0
0

Challenge

All alarms configured in Veeam ONE were deleted by mistake, and you need to get them back.

Solution

The steps below will restore all alarms that were ever configured in Veeam ONE and then deleted.
  1. Execute the following SQL script against the Veeam ONE database:

    UPDATE monitor.Alarm SET delete_time = NULL
    UPDATE monitor.AssignAlarm SET delete_time = NULL

  2. Restart Veeam ONE Monitor Server service.

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.html

How to Disable Monitoring of Specific Performance Counters in Veeam ONE 9.5

$
0
0

Challenge

You need to limit the netwrok traffic between the Veeam ONE server and the virtual infrastructure servers or to decrease the Veeam ONE database growth rate.

 

Cause

Sometimes disabling a number of performance counters can be used to achieve these results.

NOTE: In accordance with Veeam best practices, it is strongly advised not to deploy Veeam ONE behind a limited-performance WAN link due to the significant volume of real-time performance data retrieved from the virtual infrastructure.
NOTE: It is recommended to deploy Veeam ONE database on a dedicated SQL Server to avoid performance issues.
NOTE: Disabling retrieval of certain counters will affect Veeam ONE Monitor graphs and Veeam ONE Reporter reports that depend on these counters.

Solution

To disable collection of certain counters from the virtual infratsruture, follow the next steps:

1. Open the Veeam ONE Settings utility:
  • Run the executable file C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe
OR
  • Open Veeam ONE Monitor client > Options > Server Settings > Other Settings > Support utility section > Launch button
2. After the utility start, open the Scalability tab > Performance Metrics.
User-added image
3. Uncheck the performance counters you would like to stop collecting.
4. Save the settings.
5. Restart Veeam ONE services to apply the changes.

NOTE: Advanced Scalability mode can be activated as an alternative option.

Data collection mode determines what metrics Veeam ONE will collect, and specifies the product configuration in a number of areas. Choosing the appropriate data collection mode allows you to optimize monitoring and reporting performance.
Data Collection Modes comparison table.

More Information

If you have any questions, please contact Veeam Support.

How to Create Veeam ONE Service Dump for Analysis

$
0
0

Challenge

You need to create Veeam ONE service memory dump.

Cause

This is useful when you  have been asked to provide Veeam ONE full memory dump to Veeam Support for further analysis.

Solution

In order to create Veeam ONE Monitor server service full memory dump, perform the following steps:

1. Download ProcDump tool from the Windows Sysinternals page: http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

NOTE: The dumps collected using the ProcDump tool contain more useful information that those created using the default Windows method.

2. Create a new folder where the dumps will be stored (e.g. C:\Dumps\).
3. Extract the files from the archive you downloaded and copy procdump64.exe file to a newly created directory.
4. Open Windows command line as Administrator (Right-click > Run as administrator): Click Start > Run.
5. In the command line console, switch to the folder where the procdump64.exe file is located: cd C:\Dumps.
6. Run the command:
procdump64 VeeamDCS.exe

Veeam ONE Business Shows Irrelevant Data

$
0
0

Challenge

Veeam ONE Business View shows outdated data or no data at all

Cause

Veeam ONE Reporter collection task has stuck or failed

Solution

Running data collection manually

You can run data collection for Veeam ONE Reporter and Veeam ONE Business View manually. This can be necessary when automatic data collection is disabled or Veeam ONE Business View does not show any relevant information.

To manually start a data collection session:

  1. Open Veeam ONE Reporter.
  2. Open the Configuration section.
  3. In the Configuration section menu, click Servers.
  4. Select Object properties collection task and click the Run now button on the toolbar. 
You can also use Scheduling and set the collection start closer to the beginning of the business day. Generally, the task can take up to 2 hours to complete. The exact time depends on the infrastructure size and the current resources usage. You can also schedule the task to run several times a day so that the reporting data is updated more frequently.

NOTE: In case some of the tasks failed, the details can be checked on the Sessions tab.

More Information

Should you have any questions, please contact Veeam Support.

File Name Is Changed During FLR to a Non-original Location

$
0
0

Challenge

When restoring individual files to a location that is different from the original one, the "period" symbols contained in the file name will be removed. For example, file.name.txt will be restored as filename.txt

If such files are restored to their original location, they will not be affected by this behavior.

Cause

This is a known issue with Veeam Backup Browser engine which is used in Veeam Agent for Microsoft Windows and Veeam Backup and Replication products. During recovery, the backup browser performs a forbidden character check using the general vocabulary. As a result some file names may be modified due to the removal of the forbidden character.

Solution

To preserve the existing file names when restoring the files to a non-original location, use Windows Explorer.

Mapping an existing Veeam Agent for Microsoft Windows backup chain to a Veeam Backup & Replication repository

$
0
0

Challenge

You need to map an existing Veeam Agent for Microsoft Windows backup chain to a Veeam Backup & Replication repository.

Cause

There are no features in Veeam Agent for Microsoft Windows that would allow mapping existing backups to Veeam Backup & Replication, however it is possible to copy a local backup chain to a Veeam Backup & Replication repository and continue using it.

Solution

Here is the list of steps for mapping a local backup chain to a Veeam Backup & Replication repository.

1. Create a backup with Veeam Agent for Microsoft Windows at any temporary backup destination of your choice.

If a Veeam Backup & Replication repository was used,
  • remove the existing Veeam Agent for Microsoft Windows backup job from jobs (right lick > Delete)
  • remove the backup files from configuration: right click Disk (backups) > Endpoint Backups > Remove from configuration

2. Place the backup chain into the required folder.

2.1 Example for a non-cloud repository

Backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a Veeam Backup & Replication repository into the following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the account that is used to access the repository. In this example, the account is DOMAIN1\user1, so the folder name would be DOMAIN1_user1.

The complete path to the backup files would be C:\Backup\DOMAIN1_user1\Backup Job 1

2.2 Example for a cloud repository

The backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a cloud Veeam repository into following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the tenant account that is used to access the repository. If the account name is Tenant2, the complete path to the backup files would be C:\Backup\Tenant2\Backup Job 1

If a subtenant is used with the account name Subtenant3, the path will be C:\Backup\Tenant2\users\Subtenant3\Backup Job 1

3. Rescan the Veeam Backup & Replication repository. Here is a brief guide on repository rescan. 
Note: For backups that you are mapping to cloud, rescan the repository hosting the tenant backups on the provider side.

4. The Veeam Agent for Microsoft Windows backup should appear under Disk > Imported.
Note: When a backup chain is mapped to cloud, it will not be displayed under Disk > Imported.

5. Point the Veeam Agent for Microsoft Windows job to the required Veeam Backup & Replication repository. Do not run it immediately, just close the wizard after making the changes.

6. On the Veeam Backup & Replication machine, the backup should be moved from the Imported section to Backup > Disk. Make sure that backups are located in Backups > Disks (not Disk (imported)).

7. Run the Veeam Agent for Microsoft Windows backup job. It should continue the imported backup chain.

Note: The described solution works for Veeam Backup & Replication repository and Veeam Cloud Connect repository.

More Information

NOTE: if local backup encryption was enabled during the initial job configuration, additional steps may be needed to complete the mapping.

For non-cloud repositories
Importing a backup chain to a Veeam Backup and Replication server puts the imported chain in the Disk (encrypted) tab. Before the backup chain can be continued, you will need to right click on the encrypted backup chain and enter the password.

For cloud repositories
In some cases it may be necessary to enter the password in order to continue the backup chain. If entering the password is required, you will be prompted to do so when the job starts.

If you have any questions, open a case with Veeam Support.

vCenter Migration Utility

$
0
0

Challenge

If a Virtual Machines MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would receive the error "Object "vmname" is not found".  Please see KB1299 for more details.

This utility is designed to assist in re-mapping the MoRef ID's of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that backup incremental chains remain intact, after an inventory change in VMware vSphere vCenter. Do not run any jobs before using migration tool otherwise migration process won't be possible.

Please note that this utility is provided as a courtesy, and is not officially supported by Veeam Technical Support.  Use at your own risk.
Cloud Connect jobs are not supported, please perform Active Full backup.

VMware vSphere 6.5 and Veeam 9.5 is supported now!

Cause

Veeam Backup & Replication tracks Virtual Machines in its jobs by a Managed Object Reference ID (MoRef), which will change when moved to another vCenter, or removed and re-added to inventory.

Solution

Please download this bundle: tool and instructions.  Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database
Please note that the utility will work only with a source vCenter migration. If Replication target vCenter is changed, you will need to manually map source VMs to their replicas

More Information

MD5 checksum for the archive: 23934878fe5082a0e5f0481e76bfffde

Repository does not exist

$
0
0

Challenge

When trying to delete a repository, you receive a "the Repository does not exist: <GUID>" error.

Cause

The problem occurs when trying to delete a repository after upgrading from VBO 1.0 to 1.5, if the service was running under a domain account and the repository was located on an SMB share. After upgrading to v1.5, the services run under the local system account.

Solution

Give the account running the services on your VBO server access rights to the repository, and then delete it.

More Information

If the above solution does not resolve the issue, please contact Veeam Support.

Unable to Connect to Veeam ONE DB During Update Installation

$
0
0

Challenge

During upgrade to 9.5 or update installation, Veeam ONE installer is unable to locate the database

Cause

TLS 1.0 is disabled on the SQL Server side or there is an issue with the permissions assigned to the Veeam ONE service account

Solution

1. Make sure that TLS 1.0 is enabled on the SQL Server side. Veeam ONE still requires it to work on the older Windows OS versions.
NOTE: Once you perform the update/installation, you can disable TLS 1.0 if it is not allowed in your infrastructure.

2. Ensure the following permissions for Veeam ONE database are assigned to the Veeam ONE service account:

Public role (default permissions)
  • CREATE ANY DATABASE permissions
  • db_owner role on the Veeam ONE database
  • db_datareader permissions on the master database
  • publicdb_datareaderSQLAgentUserRole permissions on the msdb database
  • [For Always-On Availability Groups] VIEW SERVER STATE permissions
The Named Pipes protocol must be enabled on the Microsoft SQL Server.
 

More Information

If the issue persists, contact Veeam Support for further Technical assistance.
Viewing all 4469 articles
Browse latest View live