Inherited Mitel Role - Question regarding maintenance best practices

[jshri]

Hi!
  So happy to find this community!  I recently have temporarily inherited administration of our Mitel system after a coworker left.  Management is looking for a replacement but in the mean time I'm just trying to maintain the system.  We are migrating our VMs to new hardware and as a result I'll need to shut down the Mitel VMs.  My question is, does it matter what order the VMs come back up?  I seem to remember my coworker mentioning something about a reboot order but I can't find documentation saying for sure.  Here's what we have for VMs:

• 2 Mitel Border Gateways, one Main, one secondary
• MiCollab Voicemail
• MiVoice Business Controller
• Teleworker

The migration process involves replicating on the new nodes, then cloning the VM exactly, including MAC address.  I really appreciate any guidance provided,  I'm definitely out of my comfort zone.  Apologies if I left out any relevant information!

Thanks!
  Jshri

[johnp]

Should not matter. Would say if sip trunks having the MBG up first might be good. MiCollab does take a while to fully function and newer MiVB takes more time than previous versions. IMHO, MiVB could be the last to start but that may not make it the last to become fully active.

[TPH68]

AS for the reboot order, the way you listed should be ok. 

The migration process involves replicating on the new nodes, then cloning the VM exactly, including MAC address.

I would have a back-up plan regarding your migration.  In my past experiences, moving a "clone" or "snapshot" of a VM to a new host would rarely work and if it did work I would see many callbacks from clients on issues caused by copying VM's to a new host.  I believe anytime I ran into this scenario in the past, Mitel Support would say to deploy a new VM from their OVA's and restore from a database backup.

[Dogbreath]

Given how easy the "Restore from running server" process makes it to deploy a new instance, I would always choose that path if there was any doubt at all about being able to replicate the VM exactly.