Monitoring and reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V in a single System Center Operations Manager Console
Post Reply
vrm
Enthusiast
Posts: 34
Liked: 1 time
Joined: Feb 18, 2010 7:51 am
Full Name: Vincent
Contact:

Veeam MP v7 for System Center

Post by vrm »

Why is the VES starting from version 7.0 only supported on a SCOM management server? Is there an alternative available, so that the VES can be installed on Windows server with a SCOM agent?

Vincent
sergey.g
Veteran
Posts: 452
Liked: 76 times
Joined: May 02, 2012 1:49 pm
Full Name: Sergey Goncharenko
Contact:

Re: Veeam MP v7 for System Center

Post by sergey.g » 1 person likes this post

Hi Vincent,

Thank you very much for such a great question.

I'll explain you the benefits of using full featured management server. One of the major functionality we've implemented in v7 is automatic deployment of VMware Collectors. This feature significantly simplify VMware Collectors deployment, even if you already have 6.5 collectors in your environment, auto-deployment feature will simplify collectors version control and deployment of new collectors. This is the direction we would like to maintain and in future we are looking forward to make even more tight integration with SCOM. Integration with SCOM requires access to Operations Manger SDK service and best and most reliable connection to this service is available only on the Management Server itself. Also keep in mind that new version of our VES is absolutely hypervisor-agnostic, you can add Hyper-V sockets into your license and this will automatically enable Hyper-V support, it was possible to create such functionality because we have now this tight integration with SCOM SDK.

Also keep in mind that although VES plays an important role in VMware monitoring, in reality it's a very tiny service which most of the time does almost nothing. It plays a key role when you add a vSphere server for monitoring or in case of collector or vSphere connection failure, but 99,9% of time it's in the Idle state just keeping a record of collectors' health. So since we have this tight integration with SCOM in v7 it was a natural move for us to get it "closer" to the SDK service.

We hope this is not going to create any inconveniences for your environment, we are ready to assist you with any questions you may encounter with upgrading to v7. I would highly recommend you to check the installation guide for the upgrade instructions http://veeampdf.s3.amazonaws.com/guide/ ... LI%2FiA%3D and feel free to ask any other questions regarding the upgrade or v7 in general, here in this forum, we'll try update you asap.

Thanks.
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests