[cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0

[Wes Sisk]

nope, no export natively in  4.1

On Wednesday, August 12, 2009 10:13:48 AM , Mike O <mikeeo at msn.com> wrote:
> Wes,
>  
> With only 50 users am I better off just rebuilding from scratch? All I 
> really need are users and Phone/MAC addresses. Can I export them in 4.1?
>  
> Thanks,
>  
> Mike
>  
> ------------------------------------------------------------------------
> Date: Wed, 12 Aug 2009 10:04:48 -0400
> From: wsisk at cisco.com
> To: lelio at uoguelph.ca
> CC: cisco-voip at puck.nether.net; mikeeo at msn.com
> Subject: Re: [cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0
>
> MANY variables:
> how many times upgraded
> how many interim versions were run
> what native or 3rd party tools attempted to modify the database
> who attempted directly editing the database
> how many dbl/iis problems have been encountered?  Unfortunately 
> transactions were not strictly enforced so when problems occured there 
> were partial commits to the database
> Is enterprise LDAP integration used?  This is probably the largest 
> contributor to errors. When objects move in the enterprise there is no 
> change notification to CM (unity tried but CN from AD appears rather 
> unreliable) so CM ends up with numerous broken pointers in the database.
>
> The other systemic problem is that 4.x enforced business rules via DBL 
> rather than directly in the database.  Think of having a guard in 
> front of your storage room, but your storage room has no shelves.  
> Users must verify with the guard but once inside they have free reign 
> and very little structure.
>
> /Wes
>
> On Wednesday, August 12, 2009 9:07:05 AM , Lelio Fulgenzi 
> <lelio at uoguelph.ca> <mailto:lelio at uoguelph.ca> wrote:
>
>     well, this doesn't sound promising. what kind of garbage exists in
>     4.x databases?
>
>
>
>     ---
>     Lelio Fulgenzi, B.A.
>     Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>     (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     "Bad grammar makes me [sic]" - Tshirt
>
>
>     ----- Original Message -----
>     From: "Wes Sisk" <wsisk at cisco.com> <mailto:wsisk at cisco.com>
>     To: "Mike O" <mikeeo at msn.com> <mailto:mikeeo at msn.com>
>     Cc: cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>     Sent: Wednesday, August 12, 2009 8:49:47 AM GMT -05:00 US/Canada
>     Eastern
>     Subject: Re: [cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0
>
>     imho.  run DMA. it it works for you then that is the shortest path.
>     if DMA reports errors that you cannot easily repair then stare and
>     compare.
>
>     dma has improved significantly and even better with 7.1.  however,
>     there is so much garbage possible in 4.x databases that the
>     migration tool simply cannot always be accurate.
>     /wes
>
>     On Tuesday, August 11, 2009 9:12:39 PM , Mike O <mikeeo at msn.com>
>     <mailto:mikeeo at msn.com> wrote:
>
>         I have to migrate about 50 users/phone, whats the best way?
>         DMA or start from scratch?
>
>         ------------------------------------------------------------------------
>
>         _______________________________________________
>         cisco-voip mailing list
>         cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>         https://puck.nether.net/mailman/listinfo/cisco-voip
>           
>
>
>
>     _______________________________________________ cisco-voip mailing
>     list cisco-voip at puck.nether.net
>     <mailto:cisco-voip at puck.nether.net>
>     https://puck.nether.net/mailman/listinfo/cisco-voip
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090812/2b63c90c/attachment.html>