Monitoring and reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V in a single System Center Operations Manager Console
Post Reply
Jarv
Influencer
Posts: 20
Liked: 3 times
Joined: Aug 21, 2013 2:45 pm
Full Name: Steve
Contact:

Upgrading 5.7 to 6.0 - a few questions

Post by Jarv »

Hi, I am just looking to upgrade from nworks 5.7 to the v Veeam 6.0 MP

I have done a test upgrade in our offline domain and all seems OK but I just wanted to check a couple of things out...

Our current infrastructure is two SCOM 2012 Management Servers both of which have nworks virtual infrastructure collectors installed. We are monitoring around 600 VMWare machines split roughly half and half over these. According to the installation guide we can upgrade these collectors but after watching the Friday whiteboard series about the new MP Mike Stafford says you really shouldnt put this on the RMS emulator? Is this really the case? If not do I really need a 3rd Management Server or would I really be better looking at two clean servers with just an agent and move away from the whole SCOM server method?

Finally I understand that I can have both the 5.7 and 6.0 MP's installed (in fact the 5.7 is left behind after the upgrade) for histrorical reporting etc. However what I just want to understand is how do the 5.7 alerts stop? Does something in the upgrade override the old 5.7 settings? In other words has 5.7 data collection/alerts completely stopped and with both I am not getting 2 lots of alerts at the console??

Many thanks
Alec King
VP, Product Management
Posts: 1445
Liked: 362 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Upgrading 5.7 to 6.0 - a few questions

Post by Alec King »

Hi Steve,

I'd recommend you continue to use SCOM Management Servers as your Veeam Collectors. That's a good architecture model - the SCOM Management Server scales better and is more stable than a standard Agent when performing this agentless data processing.

Also, I don't think you need another Management Server. You do need to take care not to overload the RMS (or RMS Emulator) - but with 600 VMs spread over two servers, you are well within the scalability limits for v6 MP.
Do note that if you take one of the Management Servers offline, all the VMware monitoring will fail-over to one server. That's still within limits, but I'd probably recommend a 3rd server if you grow the VMware environment in future. Watch the Workflow Count view in our MP to see the real-world load on your Management Servers - we also have a monitor on that - our recommended maximum is 75,000 workflows per server. You can see this counter in view Veeam for VMware / Veeam Collectors / Performance Views / Workflow count.

And you can keep the 5.7 MP in place, if you wish, although unless you have some specific reporting needs I would recommend you remove it once you have installed v6.0. It can be a bit confusing when you are trying to, for example, create your own Groups or Overrides, and you have two sets of 'Veeam VMware' objects available in SCOM for both 5.7 and 6.0. Anyway the v5.x objects will stop generating alerts automatically, as soon as you've upgraded your Collectors to v6, because then you will only have v6-type data coming in.

Hope that answers your questions! Good luck with the upgrade, any issues please let us know.

Cheers,
Alec
Alec King
Vice President, Product Management
Veeam Software
Jarv
Influencer
Posts: 20
Liked: 3 times
Joined: Aug 21, 2013 2:45 pm
Full Name: Steve
Contact:

Re: Upgrading 5.7 to 6.0 - a few questions

Post by Jarv »

Hi Alec, great reply, cleared up all my questions - I will now give all of this a go in our live environment.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest