Virtualizing BES...
 

We are currently virtualizing a good number of our physical servers. Our BES was labeled as a good candidate. Is there anything I should be aware of if we are performing a P2V conversion on our BES server?

Nothing special. BES runs wonderfully within a properly configured VM.

excellent. Any thoughts or advice on an upgrade process? This summer we are looking at moving to exchange 2007. Would it be better to upgrade to BES 5 prior to the exchange upgrade or wait until after the exchange upgrade?

I would upgrade Exchange first, but it doesn't really matter all too much.

Actually, I meant exchange 2010. I have 2007 on the mind because I'm working on SCCM 2007 right now. Won't I need to upgrade to BES 5 if we are going to exchange 2010?

Virtualize BES
 

hello,
Did you ever Virtualize your BES? We have similar situation.
We have Physical BES 4.1.6 (MR7) and we will be upgrading to Exch 2010 soon. As requirement for Exchange 2010 is to be on BES 5.0 MR1. to tackle this we are planning to do following:
a. Do a P2V of BES on ESXi server
b. Upgrade to BES 5.0 MR1 before the exchange is upgraded from 2k3 to 2010
Allowing us to roll back in case upgrade to BES5.0 has issues.

Now my question would be what steps should I follow to do a P2V for the BES. Any special advise. Any documentation I can refer.
Thanks,
Virk

When we migrated to ESX, I just built a new VM BES server. Then I moved the users over. But then I'm a nut for clean installs. :razz:

You'd need an additional SRPID and Key to do that.

I've done 6 or 7 P2V moves with BES 4.1+ and haven't had a problem yet. I'm always sure to shut down all services (including database), take a FULL backup, and run the conversion.

My one tip would be to delete your log files, temp files, and other "crap" before making the conversion. It's brutal when you realize you have 25GB of logs from the past 3 years.

Stop the services and set them to disabled before running P2V.

You'll need the reboot the VM a couple of times for device discovery.

Once the VM has stopped discovering hardware, you need to delete hidden devices

Device Manager does not display devices that are not connected to the Windows XP-based computer

reboot once more. reset the IP address. reset the services to automatic. Reboot.

You're good to go.

I appreciate all the input for my question, I feel more confident now. Thanks.
I will be doing P2V of BES this Friday night and follow these steps: (Reference for any future user looking for same information)
a. Stop all the BES services and set them to disable
b. Stop the SQL services
c. Get rid of all the old logs from the server
d. Create full image of the server
e. Run VM converter tool
f. Shutdown the Physical BES
g. Start the VM BES
h. Configure the devices in device manager
i. Reset the IP address
j. Reset the services to automatic
k. Reboot
l. Do a email flow test
Hope all the steps have been included. Did I miss something?

Sounds good. I'd reboot a couple of times between g and h.

Also, don't forget to install the vmware tools.

I should also add. If your P BES has dual sockets, change the hardware definition to single vCPU while doing the P2V.

Yep that is pretty much what I did, when I did my P2V a month ago.

You should be fine following that procedure.

Also depending on how powerful the physical box is, and if you are running your SQL/MSDE on the same VM as the BES is running on, it might be worth while capping off the memory. (After all SQL can be a memory hog after running for a month+ straight)

Once it's virtualized you have the option of taking "Snap shots" before performing MRs, SPs, version updates, make a recovery/roll back plan much simpler. (just remember to manage snap shots appropriately)

My P2V went well and was completed successfully without any issues. The whole idea is to use the snapshot feature while we are doing are upgrade to version5.1 to make BES compatible with Exch 2010.
Thanks again for all the advice.