[cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0
Wes Sisk
wsisk at cisco.com
Wed Aug 12 21:20:58 EDT 2009
Technically yes, but it's not really recommended. It generates
significant database activity, consumes some CPU, and generates
reasonable disk i/o. It is MUCH less intrusive if you exclude CDR's.
It only runs on the publisher so if you don't have phones registered to
ccm.exe on the pub you can run most any time.
Note there have been a few impactful issues with previous versions of
DMA, CSCsz63731 comes to mind. This would clearly impact a production
environment.
/Wes
On Wednesday, August 12, 2009 8:20:25 PM , Lelio Fulgenzi
<lelio at uoguelph.ca> wrote:
> Can you run the DMA process itself during business hours?
>
> ---
> 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: "Justin Steinberg" <jsteinberg at gmail.com>
> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
> Cc: "Wes Sisk" <wsisk at cisco.com>, cisco-voip at puck.nether.net
> Sent: Wednesday, August 12, 2009 6:56:08 PM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0
>
> Keep in mind Wes always sees the problem childs... :)
>
> I've done many 4.1 to appliance upgrades including some with AD
> integration and have never had any significant problems. I've had to
> deal with some DMA warnings but I can usually work them out.
>
> That being said, I would definitely run DMA well in advance of your
> upgrade to make sure it is completing successfully prior to your
> upgrade window. You can then rerun DMA during your upgrade window to
> get a new current copy of the 4.1 DB and use that for your upgrade.
>
> BAT can export some phone data, but you'll lose things like ccmuser
> speed dials, pab/fd, etc - one of the reasons I always try to use DMA.
>
> On Wed, Aug 12, 2009 at 12:04 PM, Lelio Fulgenzi <lelio at uoguelph.ca
> <mailto:lelio at uoguelph.ca>> wrote:
>
> thanks Wes.
>
> i think we'll start DMA sooner rather than later.
>
> ---
> 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: "Lelio Fulgenzi" <lelio at uoguelph.ca <mailto:lelio at uoguelph.ca>>
> Cc: cisco-voip at puck.nether.net
> <mailto:cisco-voip at puck.nether.net>, "Mike O" <mikeeo at msn.com
> <mailto:mikeeo at msn.com>>
> Sent: Wednesday, August 12, 2009 10:04:48 AM GMT -05:00 US/Canada
> Eastern
> 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
>
>
>
> _______________________________________________
> 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/614fbdb0/attachment.html>
More information about the cisco-voip
mailing list