How to Configure Email Notifications

December 12, 2017, 4:54 am

≫ Next: License cannot be installed in Veeam ONE 9.5

≪ Previous: Veeam Backup & Replication Upgrade Paths

$

0

0

Challenge

E-mail notifications have to be configured.

Cause

Veeam Endpoint Backup 1.5 and Veeam Agent for Windows 2.x allow you to automatically configure email notification settings. Some email services require manual configuration.

Solution

To configure email notifications manually, follow the steps below.

1. Double-click the Veeam Agent for Microsoft Windows icon in the system tray or right-click the Veeam Agent for Microsoft Windows icon in the system tray and select Control Panel.

2. At the top of the window, click the Settings tab.



3. In the Notifications section, select the Enable email notifications check box and click the Configure and test link.

4. Enter the email address (it will be used as from and to address) and mailbox password if your mail server requires authentication.

5. Modify the Subject if needed.

6. Check at least one notification event (Success / Warning / Error).

7. Click Show SMTP server settings to open the advanced SMTP settings.



8. Enter SMTP address. It can be the IP address or DNS name of the server, server’s port number and username if required.

9. If your SMTP server supports SSL or TLS, check the box Use Secure Connection.

10. Click Test Message to send a test email and validate mail settings.



11. Once the settings are validated, you can close this page and start receiving email notifications.
 
Some public email service providers require additional actions to be performed on your mail account. To set the email notifications with a Gmail account you may need to do the following:
 
Open your Google account > Sign-in & security and ensure that Allow less secure apps is set to ON.

Keep in mind that the default implicit SSL port 465 is not supported. The port setting can be changed on the Gmail side.
 

---

License cannot be installed in Veeam ONE 9.5

December 6, 2017, 4:31 am

≫ Next: How to Configure Email Notifications

≪ Previous: How to Configure Email Notifications

$

0

0

Challenge

When installing the license file, the following error message may occur: 
 

License signature is invalid

Cause

Sometimes the license check module is unable to process the license key correctly.

Solution

To resolve the issue, install the GlobalSign certificates manually as per this KB article.

More Information

If you have any questions, contact Veeam Support.

How to Configure Email Notifications

December 12, 2017, 4:54 am

≫ Next: Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."

≪ Previous: License cannot be installed in Veeam ONE 9.5

$

0

0

Challenge

E-mail notifications have to be configured.

Cause

Veeam Endpoint Backup 1.5 and Veeam Agent for Windows 2.x allow you to automatically configure email notification settings. Some email services require manual configuration.

Solution

To configure email notifications manually, follow the steps below.

1. Double-click the Veeam Agent for Microsoft Windows icon in the system tray or right-click the Veeam Agent for Microsoft Windows icon in the system tray and select Control Panel.

2. At the top of the window, click the Settings tab.



3. In the Notifications section, select the Enable email notifications check box and click the Configure and test link.

4. Enter the email address (it will be used as from and to address) and mailbox password if your mail server requires authentication.

5. Modify the Subject if needed.

6. Check at least one notification event (Success / Warning / Error).

7. Click Show SMTP server settings to open the advanced SMTP settings.



8. Enter SMTP address. It can be the IP address or DNS name of the server, server’s port number and username if required.

9. If your SMTP server supports SSL or TLS, check the box Use Secure Connection.

10. Click Test Message to send a test email and validate mail settings.



11. Once the settings are validated, you can close this page and start receiving email notifications.
 
Some public email service providers require additional actions to be performed on your mail account. To set the email notifications with a Gmail account you may need to do the following:
 
Open your Google account > Sign-in & security and ensure that Allow less secure apps is set to ON.

Keep in mind that the default implicit SSL port 465 is not supported. The port setting can be changed on the Gmail side.
 

Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."

December 13, 2017, 6:26 am

≫ Next: VMware Cloud on AWS Support. Considerations and Limitations

≪ Previous: How to Configure Email Notifications

$

0

0

Challenge

Job may report warning: "Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances:  <instance name>. Possible reasons: lack of permissions, or transaction log corruption."

Solution

SQL logs truncation is done under user account specified in AAIP in Job settings, if it fails then GuestHelper tries to truncate transaction logs under LocalSystem account.
In order to understand why SQL logs truncation failed you will need to open the GuestHelper log in Guest VM:
\\GUESTVM\c$\ProgramData\Veeam\Backup\VeeamGuestHelper_%date%.log (for Windows 2008 or higher)
\\GUESTVM\c$\Documents and Settings\All Users\Application Data\Veeam\Backup\VeeamGuestHelper_%date%.log (for Windows 2003)
Then do search within the log using keyphrase "Truncation Statistics"

1) Error: OpenFromInitializationString failed. [Login failed for 'DOMAIN\user'.]  
Solution: give DOMAIN\user permissions  on SQL instance and add db_backupoperator role for all FULL and BULK databases, or give it a sysadmin role.

2) OLEDB Error: 'The server principal "DOMAIN\user" is not able to access the database "DATABASE" under the current security context.', HelpCtx: '0'
Solution: give DOMAIN\user db_backupoperator role for all FULL and BULK databases, or give it a sysadmin role.

3) OLEDB Error: 'BACKUP detected corruption in the database log. Check the error log for more information.', HelpCtx: '0'            
Solution: error points to possible corruption and issues with SQL server

4)  OLEDB Error: 'BACKUP LOG cannot be performed because there is no current database backup.' 
 

As a rule this is an issue with the secondary node of the SQL always on cluster. You can solve this by making a backup of the DB in question via SQL Management Studio. Otherwise, you can set the secondary node as primary for just one run of your backup job. As a result all its DBs will be backed up without "copy only" flag and the error will disappear.

The issue occurs when the secondary node has always been backed up with "copy only" flag and its standalone DBs do not have any full backup. Thus during the truncation of the standalone DB logs we get the above-mentioned message.

The same solution applies if you get this message with regard to the excluded vCenter database / Veeam database.

 

5) "Query timeout expired". If you see this entry in VeeamGuestHelper log, it usually means that we couldn't truncate SQL logs in allotted time (by default timeout is only 60 seconds). Usually you might experience such issues with rather large databases, and with large amount of transaction logs.

Solution: Implement the following registry value in affected VMs in [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\] and [ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication] (if there is no latter, you will need to create it):

SqlExecTimeout

Type: REG_DWORD
Default value: 60 (in seconds, decimal)

Try to expand that value and run a backup afterwards, safe guess here is to set it for 600 seconds.

If you observe the following warning "Failed to truncate transaction logs for SQL instances: MICROSOFT WID" on Veeam B&R version 8.0.0.2084, please contact Veeam Support for the hot-fix.

VMware Cloud on AWS Support. Considerations and Limitations

December 14, 2017, 4:43 am

≫ Next: Veeam Availability Console Migration FAQ

≪ Previous: Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."

$

0

0

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

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 avialble on VMC
Windows Dynamic disks are not suppoIted	Currently, VMC does not allow to process dynamic disks at HotAdd (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

Troubleshooting

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:

1. Create a vCenter User with required rights (Active Directory linked mode) described at https://helpcenter.veeam.com/docs/backup/vsphere/required_permissions.html, or use the cloudadmin@vmc.local user.
2. 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

Veeam Availability Console Migration FAQ

December 6, 2017, 6:54 am

≫ Next: VMware Cloud on AWS Support. Considerations and Limitations

≪ Previous: VMware Cloud on AWS Support. Considerations and Limitations

$

0

0

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, their 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.

VMware Cloud on AWS Support. Considerations and Limitations

December 14, 2017, 5:01 am

≫ Next: HCL - EMC XtremIO

≪ Previous: Veeam Availability Console Migration FAQ

$

0

0

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

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 avialble on VMC
Windows Dynamic disks are not suppoIted	Currently, VMC does not allow to process dynamic disks at HotAdd (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

More Information

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:

1. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
2. 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

HCL - EMC XtremIO

December 14, 2017, 10:48 am

≫ Next: HCL - Spectra Logic SSD

≪ Previous: VMware Cloud on AWS Support. Considerations and Limitations

$

0

0

Challenge

Product Information: 

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

Solution

Product Details: 

Model number: X2-R
Number of Drives: 18 
Drive type: 400 GB SSD
Firmware version: 6.0.1
Connection protocol and speed: 16Gb FC
General product family overview: The XtremIO Storage Array from Dell EMC is an all-flash system that leverages a scale-out architecture. The system is built via building blocks, called X-Bricks, which are SAN appliances that can be clustered together to grow performance and capacity as required. The Dell EMC XIOS operating system balances data across all solid-state arrays and supports features such as deduplication, compression, and snapshots. The all-flash architecture is viable for use cases including virtual desktop infrastructures (VDI), server environments, or database and analytics workloads. 

 

Veeam Details: 

Veeam Build Number: 9.5
Veeam Settings:  
Repository Type: Windows 
Deduplication: No 
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: Dell EMC 
Company overview: As a member of the Dell Technologies family of businesses, Dell EMC serves a key role in providing the essential infrastructure for organizations to build their digital future, transform IT and protect their most important asset, information. Dell EMC enables our enterprise customers’ IT and digital business transformation through trusted hybrid cloud and big data solutions, built upon a modern data center infrastructure that incorporates industry-leading converged infrastructure, servers, storage and cybersecurity technologies. 

Dell EMC brings together Dell’s and EMC’s respective strong capabilities and complementary portfolios, sales teams and R&D. We seek to become the technology industry’s most trusted advisor, providing capabilities spanning strategy development, consultative services and solution deployment and support to help our customers and partners drive the digital transformation of their businesses.

---

HCL - Spectra Logic SSD

December 14, 2017, 12:12 pm

≫ Next: HCL - DataCore SANSymphony 10.0

≪ Previous: HCL - EMC XtremIO

$

0

0

Challenge

Product Information: 

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

Solution

Product Details: 

Model number: Verde 
Number of Drives: 4 
Drive type: 1.7TB SSD 
Firmware version: 4.0.0 
Connection protocol and speed: 10G Fibre 
Additional support: All models and configurations of Verde with equal or above the one outlined above 
General product family overview: The Spectra® Verde® NAS Solution is the optimal disk platform for storage of mid-tier data, including primary storage offload, data staging, backup and archive. Flexible, simple and affordable, the expandable Verde disk solution provides raw storage capacities from 48TB to 7.1PB. Designed for a variety of workloads, a single Verde solution supports three different disk drive types, including 4TB, 8TB and 12TB enterprise drives; 8TB archive drives; and high-performance SSD drives. Reliable, economical and archive-ready, Spectra Verde simplifies the data storage process. 

 

Veeam Details: 

Veeam Build Number: 9.5.0.1038 
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: Spectra Logic 
Company overview: Spectra Logic develops deep storage solutions that solve the problem of long term storage 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 largest information users 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 deep storage—including archive, backup, cold storage, cloud and private cloud. 

HCL - DataCore SANSymphony 10.0

December 14, 2017, 12:28 pm

≫ Next: HCL - Huawei OceanStore 9000 NAS

≪ Previous: HCL - Spectra Logic SSD

$

0

0

Challenge

Product Information: 

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

Solution

Product Details: 

Model number: SANSymphony 
Number of Drives: 4 
Drive type: 450GB SSD 
Firmware version: 10.0 
Connection protocol and speed: 10GB iSCSI 
General product family overview: 

SANsymphony 
https://www.datacore.com/products/datacore-sansymphony
DataCore™ Hyper-converged Virtual SAN 
https://www.datacore.com/products/datacore-hyper-converged-virtual-san

Both products (above) are share a common code base, implementation use case and license keys differentiate products. For this test, SANsymphony and Hyperconverged Virtual SAN were configured using a 10GB iSCSI SAN connection.  However, all popular line speeds found in typical iSCSI SAN environments are available (e.g. 25, 40, 100 Gb/s).    In addition, the SANsymphony family of products is also compatible with the Fibre Channel SANs as deployed in customer environments at all popular speeds (4, 8, 16, 32 Gb/s).  

See the DataCore technical support site for All Qualification and Host Configuration Guides (Previous hyper link references https://datacore.custhelp.com/app/answers/detail/a_id/838) to check DataCore Software's minimum pre-requisites in the General category and the Qualified hardware components in the DataCore Server category for more information. 

 

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: Yes 
• Decompress before storing: No 
• Align backup file blocks: Yes 

More Information

Company Information: 

Company name: DataCore Software Corporation 
Company overview: https://www.datacore.com/company/about 

 

HCL - Huawei OceanStore 9000 NAS

December 14, 2017, 12:31 pm

≫ Next: HCL - Huawei OceanStor V5 Converged Storage

≪ Previous: HCL - DataCore SANSymphony 10.0

$

0

0

Challenge

Product Information: 

Product Family: Huawei OceanStor 
Status: Veeam Ready – Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features. 

Solution

Product Details: 

Model number: 9000 Scale-Out NAS Storage System 
Number of Drives: 24 
Drive type: 600GB SAS 
Firmware version: V3
Connection protocol and speed: 10GbE 
General product family overview: Huawei OceanStor 9000 Scale-out NAS Storage is a scale-out NAS storage system specifically designed for massive data storage. Employs a fully symmetric distributed architecture, supports either file or object storage, and delivers superior performance, extensive scale-out capabilities, and super-large single file system for unstructured data storage.  Widely applied in media, satellite mapping, gene sequencing, energy exploration, scientific research, education, backup and archiving. 

 

Veeam Details: 

Veeam Build Number: 9.5.0.1038
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: Huawei Technologies Co., Ltd. 
Company overview: http://www.huawei.com/en/ 

HCL - Huawei OceanStor V5 Converged Storage

December 14, 2017, 12:47 pm

≫ Next: Veeam ONE Monitor performance data collection times out

≪ Previous: HCL - Huawei OceanStore 9000 NAS

$

0

0

Challenge

Product Information: 

Product Family: Huawei OceanStor 
Status:  Veeam Ready – Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features.    

Solution

Product Details: 

Model number: Huawei OceanStor V5 Converged StorageSystem 
Number of Drives: 25 
Drive type: 600 GB SAS 
Firmware version: V5 
General product family overview: Huawei OceanStor V5 Converged Storage provides Cloud architecture-oriented operating system, high-performance hardware platform, and a complete suite of smart management software. Convergence of file, flash, backup, high-, mid, and low-end storage, and third-party storage – allocate the resources you need, when you need them. Leading active-active integrated SAN and NAS solution, ensuring business continuity for customers. 

 

Veeam Details: 

Veeam Build Number: 9.5 
Veeam Settings:  

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

More Information

Company Information: 

Company name: Huawei Technologies Co., Ltd. 
Company overview: http://www.huawei.com/en/ 

Veeam ONE Monitor performance data collection times out

December 15, 2017, 3:04 am

≫ Next: Downloading Veeam ONE Version 6.5

≪ Previous: HCL - Huawei OceanStor V5 Converged Storage

$

0

0

Challenge

You are facing the following configuration issue:



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

Downloading Veeam ONE Version 6.5

December 8, 2017, 5:53 am

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

≪ Previous: Veeam ONE Monitor performance data collection times out

$

0

0

Challenge

You need to install Veeam One 6.5

Solution

Veeam One 6.5 distribution can be downloaded here.

Patch One for Veeam One 6.5 can be downloaded here.

The documentation pack for Veeam One 6.5 can be downloaded here.

More Information

If you have further questions or issues, open a case with Veeam Support at cp.veeam.com.

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

December 17, 2017, 10:48 pm

≫ Next: Veeam ONE installation fails with "Couldn't create crypto provider" message

≪ Previous: Downloading Veeam ONE Version 6.5

$

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:


Veeam Monitor example:

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:



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 approximately 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 installation fails with "Couldn't create crypto provider" message

December 17, 2017, 10:57 pm

≫ Next: Veeam ONE Monitor Client Cannot Connect to Veeam ONE Monitor Server

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

$

0

0

Challenge

Veeam ONE installation fails with "Couldn't create crypto provider" message.

Cause

One of the known issues with Microsoft update 3000850 as per this MS KB article is the following: Opening Credential Manager fails with error 0x80090345", that also affects creating the crypto provider.

Solution

Follow these steps:

    1. On the Veeam ONE Server: Click Start > Run, type regedit, and then click OK.
    2. Navigate to the following path: HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb.
    3. Create a new DWORD (32-bit value) and name it ProtectionPolicy.
    4. Set the value to 1 and save the changes.
    5. Restart the computer.

If the above-mentioned solution does not help, please follow the next Microsoft article.

More Information

If you have any questions, contact Veeam Support.

Veeam ONE Monitor Client Cannot Connect to Veeam ONE Monitor Server

December 17, 2017, 11:00 pm

≫ Next: VeeamONE Update Failing – The specified path, file name, or both are too long.

≪ Previous: Veeam ONE installation fails with "Couldn't create crypto provider" message

$

0

0

Challenge

Veeam ONE Monitor Client cannot connect to Veeam ONE Monitor Server. The following error occurs when you open the Veeam ONE Monitor console:
 

Cause

Under certain circumstances, Veeam ONE Monitor Client cannot establish connection with Veeam ONE Monitor Server.

Solution

First of all, make sure Veeam ONE Monitor Server service is up and running.

In case the service is running properly, confirm the following:

1. The name of the Veeam ONE Monitor Server is correctly specified in Veeam ONE Monitor client settings.
2. The Veeam ONE Monitor Server is reachable from the machine where Veeam ONE Monitor Client runs.
3. In multi-Monitor Client environment, connection to Veeam ONE Monitor Server may fail with one of the following errors:
 

Service connection failed Address = \\IP_Address\pipe\VeeaMDCS Error = 0xe7
Service connection failed Address = \\IP_Address\pipe\VeeaMDCS Error = 0x5

​
To resolve this issue, add the Veeam ONE Monitor Server service account to the Veeam ONE Administrators security group.
 

4. The ports used by Veeam ONE Monitor Client to connect to the Server have to be opened:

TCP/139
TCP/445
UDP/137

Besides these standard ports, Veeam ONE Client also uses dynamic TCP ports 49152 - 65535. Check if the mentioned ports range is open on the firewall.

NOTE: For versions 6.x-7.x of Veeam ONE, the account that is used to run Veeam ONE Monitor Client must be included in the Veeam ONE Users security group on the Veeam ONE Server.

More Information

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

VeeamONE Update Failing – The specified path, file name, or both are too long.

December 17, 2017, 11:04 pm

≫ Next: Downloading Veeam ONE Version 6.5

≪ Previous: Veeam ONE Monitor Client Cannot Connect to Veeam ONE Monitor Server

$

0

0

Challenge

VeeamONE V9.5 Update # 1 install fails with the following error: “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 Characters, and the directory name must be less than 248 characters.”

Cause

Conflict with BusinessView component installation directory

Solution

1. Remove existing Veeam ONE Business view component from the server manually using VeeamONE installation ISO:
2. Open ISO in File Explorer -> go to “BusinessView” folder -> run “BV_x64.msi” and remove Business View component.
3. Run the same file again and perform a clean Business View installation (specify the same database during the installation);
4. Install the most recent Update.

Downloading Veeam ONE Version 6.5

December 8, 2017, 5:53 am

≫ Next: No VM names for Hyper-V in SCOM

≪ Previous: VeeamONE Update Failing – The specified path, file name, or both are too long.

$

0

0

Challenge

You need to install Veeam One 6.5

Solution

Veeam One 6.5 distribution can be downloaded here.

Patch One for Veeam One 6.5 can be downloaded here.

The documentation pack for Veeam One 6.5 can be downloaded here.

More Information

If you have further questions or issues, open a case with Veeam Support at cp.veeam.com.

No VM names for Hyper-V in SCOM

December 8, 2017, 5:54 am

≫ Next: Uninstalling Veeam Collectors if a System Resource Pool Was Used for Auto-Deployment

≪ Previous: Downloading Veeam ONE Version 6.5

$

0

0

Challenge

The Hyper-V topology is discovered correctly except for the Display Names of Virtual Machines, instead you can see only VM ID like in the screenshot below:



Additionally, error events 3603 are logged in the OperationsManager event log on the Hyper-V server:

"VMDiscovery.js : 'vmid' is null or not an object error number: -2146823281"

Cause

The issue is caused by "ghost" roles for the affected VMs on the Failover Cluster Manager server or the VMM server. When our script discovers the VM names, it checks the VM list in the registry of the Cluster Manager or the VMM server at HKEY_LOCAL_MACHINE\Cluster\Resources

The behavior may manifest itself if a VM has been manually removed from inventory. By design, Hyper-V should be updating the registry appropriately. If this does not happen, the "ghost" VM has no VmID under "Parameters". Here are two examples of invalid configuration:

[HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4]
"Name"="Name of VM Configuration"
"Type"="Virtual Machine Configuration"
"SeparateMonitor"=dword:00000000
 
[HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4\Parameters]
"DependsOnSharedVolumes"=hex(7):61,00,62,00,63,00,33,00,36,00,33,00,32,00,63,\
  00,2d,00,37,00,36,00,36,00,66,00,2d,00,34,00,38,00,61,00,62,00,2d,00,39,00,\
  36,00,61,00,36,00,2d,00,37,00,35,00,62,00,61,00,63,00,65,00,63,00,65,00,34,\
  00,63,00,32,00,38,00,00,00,00,00

or 

[HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f]
"Name"="Name of VM"
"Type"="Virtual Machine"
"SeparateMonitor"=dword:00000000
 
[HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f\Parameters]


 

Solution

The workaround is to remove the Virtual Machines with missing VmID from the registry of the Failover Cluster Manager or the VMM server.

More Information

There is a side effect to the suggested workaround: the failover will no longer work for the VMs that have been removed from registry.

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