MBG redundancy options

[StilPhone]

We have approximately 12-15 remote workers, 8 of which are in one office, who are currently using MBG to our 3300. We've had a PSU blow in the MBG server resulting in downtime, which, as is always the case, has suddenly become apparently 'business critical' (even though it wasn't at time of implementation), so I'm looking for options as to increase the resiliency.

As far as I can see my options are:

1. New higher spec'd server with built in redundant PSU's etc to allow for more failover.
2. Decrease the number of users on the MBG by installing local 3300's and linking them.

Now obviously option 1 is significantly cheaper, but at what point should we seriously consider moving away from MBG from a numbers prespective?

Finally, I've seen that you can virtualise MBG using VMWare - would this be a better option or am I best sticking with one of the above? We don't currently have any VMWare as we are a fully apple house, and not large enough to warrant it.

Thanks all!

Phil

 

[Billz66]

It all comes down to how much you want to spend

Sounds like its a smallish installation so getting too carried away is going to cost money.

Virtualising will still rely on a server that has a level of redundancy so thats not going to save anything unless you already had that in place or could justify a new more resilient vmware server to host MBG and other things ( depending on whether you have SIP trunks or not you could also virtualise the MCD )

Virtual MBG is easy to deploy and upgrade , you would have to add a physical to virtual license to the arid but thats about it as far as licensing costs.

You can load free esxi and virtualise all mitel servers ( MBG MCD) if you are using sip trunks , that may help swing a low end vmware environment , for a small office it doesnt need to be over the top on specs- some sort of raid array enough ram and redundant PSU connected to UPS
These days a lower end Server from any Name brand ( HP DELL IBM ) will more than likely have enough grunt for a small MCD and MBG running on vmwware .

Failing that , the cheapest option would be a duplicate server for parts
- gives you spare PSU , spare MB , spare RAM , Spare HDD

- site -site VPN connection is a possibility but MBG is probably there due to poor bandwidth at the remote site .



If I never did anything I'd never done before , I'd never do anything.....

and due to an endless stream of MiCollab , MiCC issues
Life would be simpler If only they tested products properly before releasing them .....