Archive for February, 2011

Virtualizing Lync

its a topic i talked about a while back… and i think needs to be emphasised to the end user / customer / whoever you are!

lets take a look at this very simply  and i think the point will be made….

if you look at the hardware specs for Lync you are will see that you will require 2 x Quad core proc’s and around 8 gb ram….

No problem i hear you see… but hey hang on hyper-v on supports 4 vCPU

and there in lies the problem… (i am not bashing hyper-v by the way i know 8 vcpu will be on the way soon enough)

straight away you are limiting the amount of resources you can giving to a production environment!

so again i will say before you do it, please consider it….

Lync is designed as a pbx replacement and if this is going to be your MAIN production pbx consider that point….

and by the way i am all for virtualizing lync it does make sense just be aware of the potential issues…


just an addition on to the event the other day, i was browsing the web as we do… Smile

and came across a very good blog serious about Cloud for IT Pro and gives some good explanations etc…


take a read here



So one of the things i like about my job is that i get to play with technology but it can also be a problem as when you get your hands on it problems can often occur!

So this week it was a c3000 blade chassis with flex 10 virtual connect in it.

The blades were brand spanking new bl465c G7 with NM551 flex nics

The whole purpose of this kit is to build the Private cloud on HP Hardware using Microsoft Technologies…

But i did come across this strange issue which was awkward to fix and is documented no where!

the configuration of the system was pretty intuitive but when i enabled the virtual connect config nothing worked!

so to troubleshoot the problem i logged into the open administrator you see a little information icon beside your blade saying “not configured for virtual connect”

then i logged into the virtual connect manager and see big red X’s and failed messages against server profiles!

after much searching it turns out the “prebuilt” chassis firmware’s don’t work with each other!

so the OA had 3.11 and the Virtual connect had 2.33

apparently 2.33 for virtual connect has no support for NM551 nic’s and that were the other messages come from.

So you think easy enough i will just upgrade the firmware…. So you download the latest firmware 3.15 and begin the upload and another error message “file too big to handle”

so tried the virtual connect support utility and i get plenty of timeouts and failures no specific error messages…..

anyway i could go on about the problems but one way or another they resemble the issues above

the fix!

download 2.34 firmware and upload via the gui and activate… then download the latest virtual connect support utility and download 3.10 and update via the command line

then download 3.15 and repeat!

3.15 supports the NM551 nics and now flex 10 is rocking away!


I am an outright advocate of DPM 2010, i love the product and have spent a lot of time pushing it and showing people the ease of use of the product and how powerful it can be.

One of things that is important when planning for a backup solution is the backup window

how much time you actually have to backup the data without impacting the performance of the system. This window is narrowing every single day with the more common mobile workforce and enhanced methods of application delivery and remote access…

DPM is a disk based backup solution which can then send it to tape for long term storage BUT the initial backup is done to disk. This is important as you are not waiting on the tape drive to write the data to the tape which although much better now is still pretty slow compared to a hard disk write.

Obviously how quick the data can get to the dpm server is limited to how fast the disks can write but more importantly it is limited to the network backbone

So i think this technet article is very useful for DPM bandwidth requirement planning and understanding your backup windows