<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
If informix used transaction replication dblhelper and synchronous
sequential replication would be an option.<br>
<br>
Unfortunately informix does not. Thus 'is replication working' or 'is
database 'in sync' become very complex questions.<br>
<br>
These are not excuses, just the state of things. We are working on
them, but your feedback to the Cisco PM's is invaluable.<br>
<br>
/Wes<br>
<br>
Jonathan Charles wrote:
<blockquote
cite="mid:5d093f9a0802281713w54a741e0v24c38b0bf38013f3@mail.gmail.com"
type="cite">
<pre wrap="">What seems really silly here is that if you had DBLHelper you could
just resync the SQL subscription and be good to go...
Jonathan
On Thu, Feb 28, 2008 at 7:11 PM, Erick Bergquist <a class="moz-txt-link-rfc2396E" href="mailto:erickbee@gmail.com"><erickbee@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The bug id saids this effects 5.x also. How does one tell if an
existing subscriber server is ok after publisher rebuild if they did
not know about this issue and things are working fine?
On Thu, Feb 28, 2008 at 2:59 PM, Riley, Andrew
<a class="moz-txt-link-rfc2396E" href="mailto:Andrew.Riley@getronics.com"><Andrew.Riley@getronics.com></a> wrote:
>
>
>
>
> Thanks to all for your feedback.
>
>
>
> Hopefully someone got a good talking to for missing that one in QA testing
>
>
>
>
>
> From: Wes Sisk [<a class="moz-txt-link-freetext" href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>]
> Sent: Friday, 29 February 2008 3:23 AM
> To: Lelio Fulgenzi
> Cc: Riley, Andrew; <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
>
>
> Subject: Re: [cisco-voip] One of the worst CCM bugs! - CM 6.1
>
>
>
>
>
> Actually, one point of clarification. It is not necessary to reinstall
> servers in same order as they were originally installed.
>
> /Wes
>
> Lelio Fulgenzi wrote:
>
>
> ...and here I thought not being able to forward secondary lines was bad.
>
>
>
>
>
> Lelio
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo." WJR
>
>
>
> ----- Original Message -----
>
>
> From: Wes Sisk
>
>
> To: Riley, Andrew
>
>
> Cc: <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
>
>
> Sent: Thursday, February 28, 2008 9:58 AM
>
>
> Subject: Re: [cisco-voip] One of the worst CCM bugs! - CM 6.1
>
>
>
>
> There is currently no fix for this. Work is in progress to address this
> issue. We too find it very painful.
>
> /Wes
>
> Riley, Andrew wrote:
>
> This is a comment I received from Cisco regarding the replacement of a
> publisher for CM 6.1
>
> "There is no way to reinstall or replace the publisher without reinstalling
> all the subscribers. Also if you are reinstalling publisher, then the
> subscribers need to be reinstalled in the same order as they were initially
> done so as to maintain proper functioning of the system. This is due to a
> bug which has not yet been resolved in CUCM 6.1.
>
> <a class="moz-txt-link-freetext" href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsj90196">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsj90196</a>"
>
>
> Change DRS process to not require sub rebuild/restore
>
>
> Symptom:
> CM5.x and 6.x disaster recovery currently requires subscriber reinstall.
> CM3.x and 4.x did not require subscriber reinstall after BARS restore.
>
> Conditions:
> Perform DRS restore on CM cluster.
>
>
> Workaround:
> After DRS restore on publisher reinstall each subscriber in the cluster.
>
> Further Information
> Reference CSCsh31645 for history.
>
> I have a customer with 5000 users and 8+ servers across 3 sites… a cluster
> rebuild won't go down very well!
>
> Does anyone know if there is a solution/ES available to get over this issue.
>
> Andrew Riley
> Technical Consultant - Communication Services
> CCIE # 18285 Voice
>
> Getronics Australia Pty Limited
> Getronics combines the service capabilities of the original Dutch company
> with those of Wang Global, acquired in 1999, and of the Olivetti systems and
> services division. We are ranked second worldwide in network and desktop
> outsourcing and fourth in network consulting and integration (Source: IDC
> 2002-2003).
>
> 2 Minna Close
> Belrose NSW 2085
> Australia
> Tel: +61 2 9847 7309
> Fax: +61 2 9847 7378
> Mobile: +61 402 894 793
> Email: <a class="moz-txt-link-abbreviated" href="mailto:andrew.riley@getronics.com">andrew.riley@getronics.com</a>
>
> Communication Services | Security Services | Application Services |
> Workspace Management Services | Technology Transformation Services
>
>
>
> Please note that whilst we take all care, neither Getronics nor the sender
> accepts any responsibility for viruses and it is your responsibility to scan
> for viruses. The contents are intended only for use by the addressee and may
> contain confidential and/or privileged material and any use by other than
> the intended recipient is prohibited. If you received this in error, please
> inform the sender and/or addressee immediately and delete the material.
> ________________________________
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
> <a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
>
>
> ________________________________
>
>
> _______________________________________________
> cisco-voip mailing list
> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
> <a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
> _______________________________________________
> cisco-voip mailing list
> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
> <a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
>
>
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</body>
</html>