Skip to main content

Veeam Management Pack for VMWare - Version 6

Last week Veeam announced the availability of the latest version of their Operations Manager extensions for VMWare. Veeam Management Pack for VMWare Version 6 builds on the previous versions of the product , formerly known as nWorks, and includes a number of new features that will extend the capabilities of System Center further. 

Some of these new features include:-

Capacity planning reports

  • Veeam MP offers four new capacity planning reports, built directly in Microsoft System Center:
    • Host Failure Modeling
    • Performance Forecast for Datastores
    • Performance Forecast for vSphere Clusters
    • Virtual Machine Capacity Prediction

Storage Monitoring Heatmaps
  • New heatmaps for datastore space and datastore performance usage provide an instant visual representation that uses color and graphics to show how rapidly your infrastructure is growing. You can see at a glance which VMs are the biggest, which are the fastest growing and drill down to find out why.

System Center 2012 Dashboards
  • Real-time performance views of critical vSphere systems are presented in new dashboard views—such as ‘Top 10 hosts for CPU’ per-cluster and ‘Top 10 VMs for Disk I/O’ per datastore—that leverage System Center 2012 Operations Manager widgets.

New model for Storage and Network
  • Separate topology views of distributed storage, network and compute environments allow you to quickly browse relationships and dependencies among your critical applications, services and supporting virtual and physical infrastructures. You can link from the topology view directly to real-time dashboards and monitor key metrics, such as latency, provisioning and utilization.

Performance Analysis and Correlation Monitors
  • Monitors accept input from multiple performance metrics and gather correlated data from other vSphere objects to help you solve problems faster. Dynamic correlated data is provided right in the alert description.

And support for Windows Server 2012

To find out more visit Veeam's website, http://www.veeam.com/vmware-microsoft-esx-monitoring.html

Comments

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net