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

Installing Microsoft SQL Management Studio

$
0
0

Challenge

Sometimes database edits are required to correct issues with the Veeam Backup & Replication software.

Cause

An issue has occurred and Veeam support has requested you to install Microsoft SQL Management Studio to perform troubleshooting steps.

Solution

You can get SQL Management Studio here:

2017: https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms


2014: http://www.microsoft.com/en-us/download/details.aspx?id=42299 (MgmtStudio 64BIT\SQLManagementStudio_x64_ENU.exe)

2012: http://www.microsoft.com/en-us/download/details.aspx?id=29062

2008 R2: http://www.microsoft.com/en-us/download/details.aspx?id=22985
 
2008: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=08e52ac2-1d62-45f6-9a4a-4b76a8564a2b&displaylang=en
 
2005: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796
 
An official Microsoft blog below shows step by step guides on performing this install:
http://blogs.msdn.com/b/bethmassi/archive/2011/02/18/step-by-step-installing-sql-server-management-studio-2008-express-after-visual-studio-2010.aspx

 

VDDK error: 13 - Troubleshooting

$
0
0

Challenge

Backup/Replication jobs fail with:
 
VDDK error: 13.You do not have access rights to this file

Solution

Below is a list of possible solutions to this issue sorted by what transport mode was being using when this error occurred.
Note: There are many causes for VDDK 13, this list is not intended to be all encompassing.

Using Transport Mode: Network Mode
  • Solution 1:
    In some instances, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
    http://www.veeam.com/kb1198
Using Transport Mode: Hotadd Mode
  • Solution 1:
    https://www.veeam.com/kb1775
    Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, remove the disks not owned by this VM without deleting from the datastore. Once deleted, consolidate snapshots on the affected VMs.

     
  • Solution 2:
    kb.vmware.com/kb/2003638
    Orphaned Snapshots – Consolidate snapshots on affected VMs

     
  • Solution 3:
    http://www.veeam.com/kb1875
    Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter

     
  • Solution 4:
    http://www.veeam.com/kb1882
    Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.

    Run the following via CMD Prompt on the proxy server:
    diskpart
    automount disable
    automount scrub
    exit

     
  • Solution 5:
    http://www.veeam.com/patches.html
    Patching – Please ensure that all VMware and Veeam components are fully up to date.

     
  • Solution 6:
    In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.
  • Solution 7:
    In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490) may yield positive results if all above testing does not resolve the issue.
  • Solution 8:
    Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 

    Job.Job_name.log:
    [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB

    Agent.Job_name.VM_name.Hotadd.Attacher.log:
    [time stamp] < threadID> vdl| [vddk] time stamp  error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)

    The behavior is observed when a Veeam Proxy is replicated with Veeam B&R, the replication process preserves the original VM bios UUID for restore purposes. To work around the issue setup a dedicated VM as a Veeam Proxy, replicating Veeam Proxies is not usually necessary due to ease of deployment.
Using Transport Mode: Direct SAN
Solution 1:
When receiving VDDK Error 13 when leveraging DirectSAN access mode, please confirm that the LUNs are presented to the proxy correctly and have the proper permissions. For assistance deploying & troubleshooting DirectSAN please follow the below KB articles:
http://www.veeam.com/kb1895

 

More Information

Additional Troubleshooting(All versions):
  • Manual Hotadd - http://www.veeam.com/kb1184
  • Hotadd Requirements - http://www.veeam.com/kb1054
  • Deploy an additional standalone proxy to isolate failures to a single specified proxy
  • To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.
Additional Troubleshooting (vSphere 5.1 and below):
http://www.veeam.com/kb1777
Backup via Standalone host – Configure backup job to backup via Standalone host rather than through vCenter; this will isolate vCenter as the point of failure. If backup via standalone host is successful, you can attempt restarting the vCenter as well as the management agents on the host(s) where the proxies/VM(s) reside.

Information: Hotadd will only work when the proxy is on the same host as the object being backed up

Additional Troubleshooting (vSphere 5.5):
When attempting to hotadd leveraging a standalone host configuration (that is managed by a vCenter object) with vSphere 5.5 you will receive VDDK Error 13, as well as the error listed below:

Error message: [00680 error 'transport'] Reconfigure attempt failed for VM "2" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")\n

To resolve this particular issue, please leverage Network Mode or Direct SAN transport mode as this configuration is not supported due to limitations of VMware

Information: For more information regarding ‘HostAccessRestrictedToManagementServer’ please see below VMware documentation.

http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.fault.HostAccessRestrictedToManagementServer.html

 

How to re-assign existing Tenant Backup Resources

$
0
0

Challenge

Tenant backup resources need to be re-assigned or rebuilt. There are existing backup files for the tenant that need to be kept and re-used.

Solution

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

Backup jobs fail intermittently with Error observed by underlying BIO:

$
0
0

Challenge

Intermittent network failures when communicating to the VMware host. The errors can vary but all have some variation of: 
“Error observed by underlying BIO: No such file or directoryDetail: 'SSL connect failed in tcp_connect()', endpoint:” 

Guest processing credentials test will also fail over VIX with this error, and you may get a pop up error bellow when editing the Vsphere host: 

User-added image

But on a second try it will continue.

Cause

Unsupported network configuration in VMware.  A vm kernel nic with Management is set on a port group no longer becomes eligible to have vms on it.  If a vmkernel port with management option is added to a network with vms attached you will see the following warning in VMware. 

User-added image

In Veeam we intermittently get the error “Error observed by underlying BIO: No such file or directoryDetail: 'SSL connect failed in tcp_connect()', endpoint:”,  however sometimes the jobs will work if retried enough times. 

Solution

Remove the Management vmkernel port from the vm network, or move the vms to a network without a management vmkernel port.
 

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.

Backup jobs fail intermittently with Error observed by underlying BIO:

$
0
0

Challenge

Intermittent network failures when communicating to the VMware host. The errors can vary but all have some variation of: 
“Error observed by underlying BIO: No such file or directoryDetail: 'SSL connect failed in tcp_connect()', endpoint:” 

Guest processing credentials test will also fail over VIX with this error, and you may get a pop up error bellow when editing the Vsphere host: 

User-added image

But on a second try it will continue.

Cause

Unsupported network configuration in VMware.  A vm kernel nic with Management is set on a port group no longer becomes eligible to have vms on it.  If a vmkernel port with management option is added to a network with vms attached you will see the following warning in VMware. 

User-added image

In Veeam we intermittently get the error “Error observed by underlying BIO: No such file or directoryDetail: 'SSL connect failed in tcp_connect()', endpoint:”,  however sometimes the jobs will work if retried enough times. 

Solution

Remove the Management vmkernel port from the vm network, or move the vms to a network without a management vmkernel port.
 

Using Management Studio Express to Migrate a Veeam Backup database to a new SQL server

$
0
0

Challenge

How do I move the Veeam Backup SQL database to a new SQL Server using either SQL Server Management Studio or the Command Prompt?

Solution

Microsoft has provided us with options for relocation of databases and their associated transaction logs, as well as tools to perform these operations with ease and reliability in both small and large computing environments. Regardless if you have five servers or a complex infrastructure with hundreds of servers, this process will allow for the seamless movement of databases from any compatible operating system.

Moving a database by using detach-and-attach operations involves the following stages:

1) Detaching the database.
Detaching a database removes it from the instance of the Microsoft SQL Server Database Engine, but leaves the database intact with its data files and transaction log files. To detach the database using SQL Management Studio, you will expand the Instance, right-click on the Database you wish to Detach, click Tasks, and then click Detach. Be sure you have selected the correct database performing the Detach action.

2) Moving the database files to the other server or disk.

The database is traditionally stored in the Data location of the SQL Server program folder on the local disk. Each instance contains a “.#” suffix following the MSSQL folder, the default instance contains a 1, followed by each other instance which increases by 1 respectively. In the data folder, you will see the.mdf (database) and .ldf (transactional logs) files.
Both of these files will need to be relocated to their new server They do not necessarily have to be placed in a similar location - they can be placed anywhere as long as the SQL Server has direct access to the storage. It is actually Microsoft's best practice to place these files on different storage volumes as the transaction log file grows indefinitely, and can become significantly larger than the database file.

3) Attaching the database by specifying the new location of the moved file or files.

Once you have successfully logged into the SQL Server instance where you would like the database to be attached to, you will need to expand the instance, right-click on the Database node, and click Properties. Here, you will find the Attach option. Next you can browse to the new location where our original database files now reside. Only the .mdf files will be displayed in this view. You will have the option to verify the location for the .ldf files after click OK.

Detaching the database

User-added image


Locating the Database Files

User-added image

Attaching the database
User-added image


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

More Information

If the Management Studio is not available, we can perform these same steps using the SQLCMD from the 
Command Prompt.  We will need to use the -S parameter to log into the SQL instance. You would use this 
command to log into both the source and target instance.

 Sqlcmd -S <servername\InstanceName>     eg:  sqlcmd -S .\VeeamSQL2012

User-added image
Next connect to the master database

 
Use Master
Go

 
User-added image

We can then use the following command to detach the database
sp_detach_db ‘databasename’    
Go


eg: sp_detach_db ‘VeeamBackup’
go

User-added image

To attach the database to the new instance after following the previously listed steps to connect to the new server/instance use the following command.

 
sp_attach_db 'database name','location of mdf','location of logs'
go


eg: sp_attach_db 'VeeamBackup','C:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2012\MSSQL\DATA\Veeambackup.mdf','C:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2012\MSSQL\DATA\VeeamBackup_log.ldf'

User-added image


Then we can perform this command to login to the remote server:
SQLCMD -S 192.168.85.3\SQLEXPRESS
Followed by this command to perform the attach operation:
EXEC sp_attach_db @dbname = N'VeeamBackup',
 @filename1 = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\VeeamBackup.mdf',
@filename2 = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\VeeamBackup_log.ldf';
GO
User-added image

Now, you can perform this task programmatically or without the help of Microsoft SQL Management Studio.

 

HCL - Pure FlashBlade

$
0
0

Challenge

Product Information

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

Solution

Product Details

Model number: Pure Storage FlashBlade 
Number of Drives: 7 Blades / 8TB per blade 
Drive type: SSD 
Firmware version: Purity//FB 2.1.0 
General product family overview:  

FlashBlade is a fast and dense unstructured data platform from Pure Storage that provides on-premise rapid backup and recovery of archival data. Additionally, Pure Storage FlashBlade provides high-performance in a dense-form factor for other unstructured data primary use cases such as machine learning, deep learning, and electronic design automation (EDA), among others. For more information, please follow this link

 

Veeam Details

Veeam Build Number: 9.5.0.823 
Veeam Settings:  

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

More Information

Company Information

Company name: Pure Storage 
Company overview:  
Pure Storage helps companies push the boundaries of what's possible. Pure's end-to-end data platform - including FlashArray, FlashBlade and our converged offering with Cisco, FlashStack – is powered by innovative software that's cloud-connected for management from anywhere on a mobile device and supported by the Evergreen business model. The company's all-flash based technology, combined with its customer-friendly business model, drives business and IT transformation with solutions that are effortless, efficient and evergreen. With Pure's industry leading Satmetrix-certified NPS score of 83.5, Pure customers are some of the happiest in the world, and include organizations of all sizes, across an ever-expanding range of industries. 


HCL - Spectra Logic Tape Family T-380

$
0
0

Challenge

Product Information

Product Family: Spectra Logic Tape Libraries 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam.  

Solution

Product Details

Model number: T-50e, T-120, T-200, T-380, T-680, T-950 
Library firmware version: BlueScale 12.6.45.3 
Drive firmware version: G9Q0 
Driver for tape drive: IBM Ultrium 7 Tape Driver v 6.2.5.5 
Driver for media changer: 2.0.2.5 
Media Type: LTO-6 
General product family overview: Spectra’s tape library family delivers the industry’s best combination of capacity, performance, scalability, reliability, support and affordability. Spectra’s highly compact tape library architecture and innovative design provides industry-best density. Optimized storage allows users to continually realize dynamic growth, increased performance and energy efficiencies throughout the storage management process and infrastructure. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038 

More Information

Company Information

Company name: Spectra Logic 
Company overview: Spectra Logic develops data storage solutions that solve the problem of short and long-term digital preservation for business and technology professionals dealing with exponential data growth. Dedicated solely to storage innovation for nearly 40 years, Spectra Logic’s uncompromising product and customer focus is proven by the adoption of its solutions by industry leaders in multiple vertical markets globally. Spectra enables affordable, multi-decade data storage and access by creating new methods of managing information in all forms of storage—including archive, backup, cold storage, private and public cloud. 

HCL - SUSE Enterprise Storage v5 SDS

$
0
0

Challenge

Product Information

Product Family: SUSE Enterprise Storage 
Status: Veeam Ready – Archive 
Classification Description: Verified disk archive storage that can be used as a Backup Copy target.  Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported. 

Solution

Product Details

Model number: SUSE Enterprise Storage 5 
Number of Drives: 15 
Drive type: 2TB SATA 
Firmware version: SDS GA 
General product family overview: For most enterprise-level businesses, the demand for data storage is growing much faster than the average price for storage is shrinking. That means you'll be forced to increase your budget dramatically to keep up with your data demands. However, there is another answer—SUSE Enterprise Storage. This intelligent software-defined storage solution, powered by Ceph technology, enables you to transform your enterprise storage infrastructure to reduce costs while providing unlimited scalability. 

 

Veeam Details

Veeam Build Number: 9.5.0.1038
Veeam Settings:  

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

More Information

Company Information

Company name: SUSE 
Company overview: We adapt.  You succeed. 

Veeam ONE Monitor performance data collection times out

$
0
0

Challenge

You are facing the following configuration issue:

User-added image

Veeam ONE Monitor performance graphs show the No Data Available message.

Cause

VeeamDCS.log file contains the following errors:

​Collecting thread has failed to initialize (The operation has timed out) and will be stopped
Collecting thread will exit due to serious error (The operation has timed out)
Reporting DB event: Failed to collect infrastructure topology for object vCenter. The operation has timed out (VeeamInfCollectionFailedEvent)
Unable to collect performance. This operation returned because the timeout period expired

There can be a number of reasons for a timeout.

Solution

To troubleshoot the issue, you can add hosts to Veeam ONE Monitor monitoring scope one by one. This will decrease the amount of data pulled from the vCenter Server and isolate the timeout issue to the vCenter performance:

  1. Remove the affected vCenter Server from Veeam ONE Monitor and then connect it again.
    Important: this will remove historical data from the Veeam ONE database. Please consider this step carefully, as the historical data may not be collected again.

  2. Once the infrastructure tree (child objects) is built, go to Options > Server Settings > Hosts tab and exclude from the monitoring scope all hosts but one (one host should be included into the monitoring scope for this vCenter Server). Save the settings. Check if Veeam ONE Monitor can successfully collect performance data from the monitored host.

  3. If the collection of past performance data has been successful for that host, go to Options Server Settings > Hosts tab and enable monitoring for the next host.

    You can enable monitoring for one or two hosts at a time (the next set of hosts is added to the monitoring scope after the collection for the previously added hosts has been completed).

Alternatively, you can modify the timeout value. In this case, Veeam ONE Monitor will wait for the performance data collection completion for an extended period of time.

To increase the timeout value through the registry:

  1. Log on to Veeam ONE server.
  2. Go to the registry editor.
  3. Create key named Service under HKEY_LOCAL MACHINE - SOFTWARE - Veeam - Veeam ONE Monitor
  4. Create the HistQueryTimeoutSec DWORD registry entry and set it to the decimal value of 3600.
  5. Create the RtQueryTimeoutSec  DWORD registry entry and set it to the decimal value of 900.
  6. Restart Veeam One Monitor Service.

More Information

Note that this solution is not applicable starting with vCenter 5.5 U3. To find out more, refer to this Veeam KB artice.

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

Scheduled automatic dashboard delivery fails

$
0
0

Challenge

In certaing scenarios, scheduled dashboard delivery in Veeam ONE Reporter fails and reports the 'Dashboard Capturing Failed' error in the reporting task session log.

Cause

This issue is usually related to the configured permissions of the Veeam ONE Service account, which makes the dashboard inaccessible during the capture process.

Solution

Follow the steps below to resolve this issue:
  1. Add the Veeam ONE Service account, or the log on as account for the Veeam ONE services, to the Veeam ONE Administrators local security group on the Veeam ONE machine.

  2. If you have deployed Veeam ONE using the advanced configuration scenario, with the Veeam ONE Server components and the Veeam ONE Web UI components on separate machines, add the Veeam ONE Service account to the Veeam ONE Administrators local security group on both machines.

  3. To ensure that the changes have taken full effect, restart both the Veeam ONE Monitor Server and Veeam ONE Reporter Server services on the machine where the Veeam ONE Server components are installed. If you still receive errors in the reporting task log, perform log-on/log-off with the Veeam ONE Service account on the machine(s) where the Veeam ONE Server components and the Veeam ONE Web UI components are installed.
     

More Information

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

Maximum, minimum, average and latest CPU Usage values differ in VMware vCenter and Veeam Monitor

$
0
0

Challenge

The values in the VMware CPU Usage performance graphs and table values are twice as high as those of the Veeam Monitor graphs.

VMware vSphere example:

User-added image

Veeam Monitor example:
User-added image

Cause

VMware calculates these values with Hyperthreading Technology enabled.

The VMware vSphere client shows that “Hyperthreading” is in the “Active” state under the “General” section on the Summary tab for the ESX(i) host within the virtual infrastructure:

User-added image

As a result, the “Advanced” performance page for this host shows total values for all processors but with the Hyperthreading feature enabled 

Once all object are selected under the Chart Option window, the CPU Usage is displayed for all virtual CPUs and the ESX(i) host itself. Summing up the average values of each virtual CPU and then dividing by the number of virtual CPUs produces a value two times smaller than the TOTAL CPU Usage value for the host.

Veeam Monitor calculates the total CPU Usage without using VMware’s “Total CPU Usage for entire host with Hyperthreading enabled” option. It takes each CPU's Usage and then performs calculations as described above. Thus, in Veeam Monitor, the Total CPU Usage value is two times smaller than CPU Usage for the entire host on VMware’s graphs.

Solution

No solution required as this is the expected behavior.

More Information

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

Veeam ONE Fails to Collect Performance Data from a Hyper-V Host

$
0
0

Challenge

Veeam ONE may fail to collect performance data from one or multiple Hyper-V hosts but is able to collect infrastructure and topology data. Veeam ONE may not report an error, however, no performance data is present when viewing the performance graphs in the Veeam ONE Monitor Client.

Cause

There can be several root causes for this.

1. Insufficient permissions for the account used by Veeam ONE to collect the data from the Hyper-V host.
2. Services which Veeam ONE relies on are not running on the Hyper-V host.
3. There is no performance data available in the Microsoft Performance monitor on the Hyper-V host due to either corrupt, modified, or missing Windows performance counters or performance counter sets on the host system. Third-party applications can also be responsible for modifying the default Performance Monitor counter set configuration.
 

Solution

Permissions

To resolve permissions issue, make sure the account follows the requirements specified in Veeam ONE Deployment guide.
 

Services

To fix the issue with services, verify that the following services are up and running on the Hyper-V host: RemoteRegistry, RemoteProcedureCall, Windows Management Instrumentation.
 

Performance counters

Confirm integrity issue
The presence and integrity of the Windows Performance Monitor (perfmon.exe) performance counters and counter sets needs to be verified on the Hyper-V host experiencing the issue to confirm the cause of the issue.

Use one of the two methods for verifying the integrity of the performance counters outlined below:

1. Open perfmon.exe on the host system experiencing the issue, then select Performance Monitor in the navigation panel of the utility and click the green plus sign to open the list of available performance counters. Next, verify that the following performance counter sets are available:
  • Memory
  • Network Adapter
  • LogicalDisk
  • PhysicalDisk
  • Cluster CSV Block Redirection
  • Cluster CSV Coordinator
  • Cluster CSV File System
  • Cluster CSV Volume Cache
  • Cluster CSV Volume Manager
  • Hyper-V Dynamic Memory Balancer
  • Hyper-V Dynamic Memory VM
  • Hyper-V Hypervisor Logical Processor
  • Hyper-V Hypervisor Virtual Processor
  • Hyper-V Virtual Storage Device
  • Hyper-V Virtual Network Adapter
  • Hyper-V Virtual Switch
2. Alternatively, run the following Powershell script on the host system experiencing the issue: 
 
$HvPerfCounters = (
Get-Counter -ListSet Memory, 'Network Adapter', LogicalDisk, PhysicalDisk, 
 'Cluster CSV Block Redirection', 'Cluster CSV Coordinator', 'Cluster CSV File System', 
 'Cluster CSV Volume Cache', 'Cluster CSV Volume Manager', 'Hyper-V Dynamic Memory Balancer', 
 'Hyper-V Dynamic Memory VM', 'Hyper-V Virtual Storage Device', 'Hyper-V Hypervisor Logical Processor', 
 'Hyper-V Hypervisor Virtual Processor', 'Hyper-V Virtual Network Adapter', 'Hyper-V Virtual Switch')
$HvPerfCounters | Format-List -Property CounterSetName, Paths

The cause of the issue can be confirmed as corrupt or missing performance counters or performance counter sets if an error is reported while the script is gathering the included performance counter sets. 

Resolve integrity issue
To resolve the corrupted counters issue, the Performance Counters and Performance Counter Sets on the affected Hyper-V host must be rebuilt by following the instructions outlined below.

1. Open the Administrative (elevated) command prompt on the affected Hyper-V host.

2. Run the following commands in sequence in order to rebuild the counters:
      cd c:\windows\system32
      lodctr /R
      cd c:\windows\sysWOW64
      lodctr /R​

3. Run the following command to re-sync the counters with WMI:
       
WINMGMT.EXE /RESYNCPERF

4. Restart both the Performance Logs and Alerts service and the Windows Management Instrumentation service.

        - Optionally, you may reboot the affected Hyper-V host once steps 2 and 3 have been completed.

5. Check whether the performance counters are available.

More Information

For more information on issues with Windows Performance Counters or rebuilding Windows Performance Counters, refer to the following Microsoft KB Article.

No performance data for vSphere environment

$
0
0

Challenge

Veeam ONE Monitor Client shows the "No data available" message on performance charts for different metrics:

User-added image
 

Cause

The account used for collecting data from vCenter Server or ESX(i) host does not have sufficient permissions on the virtual server.

Solution

To resolve this issue, make sure the permissions are granted for the user account that is used to connect to a corresponding virtual infrastructure object.

More Information

If you have any questions or problems, please contact Veeam Support.

Veeam ONE Backup and Replication Performance Data Collection Failures

$
0
0

Challenge

Veeam ONE raises the Backup performance data collection failure alarm.

Cause

Permissions and firewall ports need to be configured.

The services status should be checked on the Veeam Backup and Replication server.

Solution

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

More Information

If you have any questions, please contact Veeam Support.

Veeam ONE Manual Database Creation

$
0
0

Challenge

Manual creation of Veeam ONE database may be needed in some scenarios

Cause

Here is how Veeam ONE database can be created.

Solution

1. Open SQL Server Management studio.
2. Create a service account for Veeam ONE and assign the following permissions to it:
  • 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
NOTE: The Named Pipes protocol on the Microsoft SQL Server must be enabled.
NOTE: If the Veeam ONE database runs on a remote Microsoft SQL Server instance, with the Microsoft SQL Server and Veeam ONE components residing in the same workgroup, Microsoft SQL Server authentication will be required.
 
3. Create a new database using the account specified above.
4. Run the installation SQL script against the new database. The script can be found on the Veeam ONE ISO: Addons\SQLScript\SQLScript.sql.
5. Install Veeam ONE using the specified Service Account and the database created earlier. If Veeam ONE is already installed, update the existing database name using Veeam ONE Settings utility located in C:\Program Files\Veeam ONE\Veeam One Settings\VeeamOneSettings.exe
6. Install Veeam Reporter packs. See this KB for details.
7. Install the latest Update for Veeam ONE (skip this step in case you completed this requirement during the Reports pack installation).
8. Update websites settings. See this KB article for details.

More Information

NOTE: manual import of report packs will be needed for Veeam ONE Reporter to operate properly. See this KB article for details.

Should you have any questions, contact Veeam Support.

Collecting Additional Diagnostic Information for Oracle Processing Cases

$
0
0

Challenge

An issue with backing up of the Oracle database server and/or removal of Oracle archived logs is suspected. Veeam Technical Support would like to gather some information from your servers and databases in order to investigate this issue.

Cause

Additional logs have to be gathered manually from the guest OS on the VM in question, because they are NOT captured by the Support Wizard automatically.

Solution

NOTE: If Application-Aware Image Processing is disabled, enable it and run the job again to update the log files within the guest OS.
 
The following actions need to be performed within the guest OS of the VM in question. 
NOTE: all Veeam Backup and Replication tasks against the guest in question must be stopped during this collection process. Otherwise the accuracy of the information will be affected.
 
 
For Windows
 
1.  Navigate to the following directory:
 
 %programdata%\Veeam\Backup
  
2.  Collect files and folders matching the following Syntax:
 
VeeamGuestHelper_ddmmyyyy.log
VeeamLogShipper_ddmmyyyy.log
OracleLib.*.log
%backup job name%_Oracle_Redo_Log_Backup - entire folder
 
3.  Open an elevated command prompt and run the following commands:
 
vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
 
4.  Export Windows Event Logs as shown here.

5. Connect to your instance as sysdba:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SQL> select * from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
SQL> select * from dba_role_privs where granted_role='DBA';
 
Save output of above queries in a text file for support engineer.

 
For Linux
 

1.  Navigate to the following directories:
 
/var/log/VeeamBackup
/tmp
 
get all the files with the following filename masks:
 
VeeamOracleAgent.*.log
Agent.LogBackup_cli.*.log
 
2. Login to the server shell with the user credentials specified in 'Guest OS credentials' field as shown here. After that issue the following commands to get basic environment information:
 
cat /etc/*release
uname -a
env
 
3. Collect information about guest components installed on your virtual machine:
 
a) In case of VMware
 
- Login to your Linux server
- Run the following commands
 
# vmtoolsd -v
# service vmtoolsd status
 
or
 
#  systemctl status vmtoolsd
 
b) In case of Hyper-V
 
- Login to your Linux server
- Run the following commands
 
# lsmod | grep hv_utils
# modinfo hv_vmbus
# ps -ef | grep hv
 
- Login to your Hyper-V host where this virtual machine is running
- Run the following command in PowerShell (replace VM with your actual virtual machine name)
 
PS> Get-VMIntegrationService -VMName "VM"
 
4. Connect to your instance as sysdba from same user in shell as it was in step 2:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SQL> select * from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
 
Save the output of above queries in a text file for Veeam Support.
 
5. Get the following files from your Oracle database installation (ask your database administrator if you are not sure about the exact location of these files)
 
oratab (by default it's located in /etc)
inventory.xml (by default it's located in $ORACLE_BASE/oraInventory)
oraInst.loc (by defaults it's located in $ORACLE_HOME)
 
Collect the logs and shell outputs from the steps above, bundle them in a compressed file, and share with Veeam Support. 
 

Failed to send heartbeat to controller

$
0
0

Challenge

Veeam Backup for Microsoft Office 365 Backup jobs fail with the following error:
 
Timestamp 12 (9572) Connecting to organization...
Timestamp 12 (6688) Failed to send heartbeat to controller
Timestamp 12 (6688) Error: Access is denied.

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

Cause

Proxy ID has not been properly reformed during Veeam Backup for Office 365 upgrade from version 1.0 to 1.5

Solution

  1. Stop Veeam Backup for Microsoft Office 365 Service and Veeam Backup Proxy for Microsoft Office 365 Service
  2. Delete С:\Programdata\Veeam\Backup365\ProxyDb\ and C:\Programdata\Veeam\Backup365\Config.xml from Proxy Server
  3. Start Veeam Backup Proxy for Microsoft Office 365 Service*
  4. Start Veeam Backup for Microsoft Office 365 Service
  5. Proxy ID should be synchronized - run the backup
*It is vital to have Veeam Backup Proxy for Microsoft Office 365 Service started before Veeam Backup for Microsoft Office 365 Service, since Controller has the proper information that should be propagated to newly created Proxy database and not a vice-versa.
 

Collecting Additional Diagnostic Information for Oracle Processing Cases

$
0
0

Challenge

An issue with backing up of the Oracle database server and/or removal of Oracle archived logs is suspected. Veeam Technical Support would like to gather some information from your servers and databases in order to investigate this issue.

Cause

Additional logs have to be gathered manually from the guest OS on the VM in question, because they are NOT captured by the Support Wizard automatically.

Solution

NOTE: If Application-Aware Image Processing is disabled, enable it and run the job again to update the log files within the guest OS.
 
The following actions need to be performed within the guest OS of the VM in question. 
NOTE: all Veeam Backup and Replication tasks against the guest in question must be stopped during this collection process. Otherwise the accuracy of the information will be affected.
 
 
For Windows
 
1.  Navigate to the following directory:
 
 %programdata%\Veeam\Backup
  
2.  Collect files and folders matching the following Syntax:
 
VeeamGuestHelper_ddmmyyyy.log
VeeamLogShipper_ddmmyyyy.log
OracleLib.*.log
%backup job name%_Oracle_Redo_Log_Backup - entire folder
 
3.  Open an elevated command prompt and run the following commands:
 
vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
 
4.  Export Windows Event Logs as shown here.

5. Connect to your instance as sysdba:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SQL> select * from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
SQL> select * from dba_role_privs where granted_role='DBA';
 
Save output of above queries in a text file for support engineer.

 
For Linux
 

1.  Navigate to the following directories:
 
/var/log/VeeamBackup
/tmp
 
get all the files with the following filename masks:
 
VeeamOracleAgent.*.log
Agent.LogBackup_cli.*.log
 
2. Login to the server shell with the user credentials specified in 'Guest OS credentials' field as shown here. After that issue the following commands to get basic environment information:
 
cat /etc/*release
uname -a
env
 
3. Collect information about guest components installed on your virtual machine:
 
a) In case of VMware
 
- Login to your Linux server
- Run the following commands
 
# vmtoolsd -v
# service vmtoolsd status
 
or
 
#  systemctl status vmtoolsd
 
b) In case of Hyper-V
 
- Login to your Linux server
- Run the following commands
 
# lsmod | grep hv_utils
# modinfo hv_vmbus
# ps -ef | grep hv
 
- Login to your Hyper-V host where this virtual machine is running
- Run the following command in PowerShell (replace VM with your actual virtual machine name)
 
PS> Get-VMIntegrationService -VMName "VM"
 
4. Connect to your instance as sysdba from same user in shell as it was in step 2:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SQL> select * from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
 
Save the output of above queries in a text file for Veeam Support.
 
5. Get the following files from your Oracle database installation (ask your database administrator if you are not sure about the exact location of these files)
 
oratab (by default it's located in /etc)
inventory.xml (by default it's located in $ORACLE_BASE/oraInventory)
oraInst.loc (by defaults it's located in $ORACLE_HOME)
 
Collect the logs and shell outputs from the steps above, bundle them in a compressed file, and share with Veeam Support. 
 
Viewing all 4469 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>