<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Since you're asking for opinions......have you considered Unity Connection? If you are voice mail only, Connection is a strong alternative to the Unity solution. It follows in the "appliance" model, upgrades are pretty painless and it includes voice recognition and text to speech.<br><br>If I'm not mistaken, Cisco will migrate you from Unity to Unity Connection at no charge. I don't believe this offer/programme was time limited.<br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Nick" <csvoip@googlemail.com><br>To: cisco-voip@puck.nether.net<br>Sent: Wednesday, July 15, 2009 6:02:31 PM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] Unity Upgrade and Migration Scenario<br><br><div>I have a scenario where I need to move a Unity 4.2 voicemail only server to a different location and change the hostname and IP address. This is all part of a migration to a new CUCM cluster that has been built separately along side the original cluster. There is also another Unity 4.2 server on the original cluster which may become extinct and the users migrated to the first Unity server. The customer would also like to upgrade to a newer verision at some point. . </div>
<div> </div>
<div>Originally at the time of migration I was looking at backing up the database of the Unity server using DIRT then moving the server to the new location, rebuilding the server with the new IP address and hostname on version 4.2 and then using DIRT to restore the data. Then looking at migrating the users from the 2nd cluster and then upgrading the version from 4.2 to 7.0</div>
<div> </div>
<div>However, I have now been thinking to get another server, build it to version 7.0 at the new site with a different hostname and IP address then use COBRAS to back up the first 4.2 server and restore the data to 7.0. Integrate with the new CUCM cluster and complete testing. Then before the migration takes place use COBRAS again to back up both of the 4.2 servers and restore additional data and subscribers to the new 7.0 server.</div>
<div> </div>
<div>Is the 2nd option a viable solution and if can anyone make any further suggestions on the best route to take?</div>
<div> </div>
<div>Cheers</div>
<div> </div>
<div>Nick</div>
<div> </div>
<div> </div>
<div> </div>
<br>_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
</div></body></html>