SBS 2003 in Journal Wrap Error State from Previous Migration
|
Prev: OWA and Documents
Next: Service Packs & Updates
From: JNelsonCPath on 5 May 2010 13:43 I apologize ahead of time if this question was already discussed, I realize it is an older topic, but I couldn't find my particular "offshoot" of the issue so decided to post a question. Here is the history of the problem. I have an SBS 2003 Standard domain. Two years ago, I moved SBS 2003 to more powerful hardware by way of Microsoft's migration procedure. All went well except for the following: When I removed the old SBS from the network, I began getting errors in my file replication log on the new server complaining that it had a journal wrap error (event ID 13568) and could not read from the NTFS USN journal on the other server. Well the error is correct because the old server was removed and no longer exists. I made an assumption that Microsoft's recommended method for migrating SBS 2003 to new hardware would deal with any replication issues when the domain data was transferred, but it did not and the new server has been looking for the old one ever since. For the past two years, the SBS 2003 server has been running tip top and has experienced few issues. We now plan to migrate to SBS 2008 to take advantage of the newer technologies, and this journal wrap error has become important again. I have researched the web for days looking for a solution to my particular situation and cannot find anything that makes sense for this particular problem. All of the solutions, ideas, posts, KB articles, etc... that I have been looking at are solutions and ideas for restoring replication between two or more partners. While these solutions and ideas are talking about the same error message that I am seeing on my server, I have to assume that they don't apply to me becasue there is no location on my network to replicate with. How can I resolve the NTFRS errors I am seeing with no replication partner available? It is important that I resolve this before we migrate. All solutions I have seen say that the server will be removed from the replication set and then re-added to it which is impossible due to the old server being gone. Thank you in advance!
From: Cris Hanna [SBS - MVP] on 5 May 2010 14:23 check this blog http://msmvps.com/blogs/bradley/archive/2009/11/27/burflags-and-journal-wrap.aspx -- Cris Hanna [SBS - MVP] (since 1997) Co-Contributor, Windows Small Business Server 2008 Unleashed http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1 Owner, CPU Services, Belleville, IL A Microsoft Registered Partner ------------------------------------ MVPs do not work for Microsoft Please do not submit questions directly to me. "JNelsonCPath" <JNelsonCPath(a)discussions.microsoft.com> wrote in message news:C9202416-6C5F-4062-B7CC-F3F9BBE005DC(a)microsoft.com... I apologize ahead of time if this question was already discussed, I realize it is an older topic, but I couldn't find my particular "offshoot" of the issue so decided to post a question. Here is the history of the problem. I have an SBS 2003 Standard domain. Two years ago, I moved SBS 2003 to more powerful hardware by way of Microsoft's migration procedure. All went well except for the following: When I removed the old SBS from the network, I began getting errors in my file replication log on the new server complaining that it had a journal wrap error (event ID 13568) and could not read from the NTFS USN journal on the other server. Well the error is correct because the old server was removed and no longer exists. I made an assumption that Microsoft's recommended method for migrating SBS 2003 to new hardware would deal with any replication issues when the domain data was transferred, but it did not and the new server has been looking for the old one ever since. For the past two years, the SBS 2003 server has been running tip top and has experienced few issues. We now plan to migrate to SBS 2008 to take advantage of the newer technologies, and this journal wrap error has become important again. I have researched the web for days looking for a solution to my particular situation and cannot find anything that makes sense for this particular problem. All of the solutions, ideas, posts, KB articles, etc... that I have been looking at are solutions and ideas for restoring replication between two or more partners. While these solutions and ideas are talking about the same error message that I am seeing on my server, I have to assume that they don't apply to me becasue there is no location on my network to replicate with. How can I resolve the NTFRS errors I am seeing with no replication partner available? It is important that I resolve this before we migrate. All solutions I have seen say that the server will be removed from the replication set and then re-added to it which is impossible due to the old server being gone. Thank you in advance!
From: Susan Bradley on 5 May 2010 16:09 JNelsonCPath wrote: > I apologize ahead of time if this question was already discussed, I realize > it is an older topic, but I couldn't find my particular "offshoot" of the > issue so decided to post a question. > > Here is the history of the problem. I have an SBS 2003 Standard domain. > Two years ago, I moved SBS 2003 to more powerful hardware by way of > Microsoft's migration procedure. All went well except for the following: > When I removed the old SBS from the network, I began getting errors in my > file replication log on the new server complaining that it had a journal wrap > error (event ID 13568) and could not read from the NTFS USN journal on the > other server. Well the error is correct because the old server was removed > and no longer exists. I made an assumption that Microsoft's recommended > method for migrating SBS 2003 to new hardware would deal with any replication > issues when the domain data was transferred, but it did not and the new > server has been looking for the old one ever since. > > For the past two years, the SBS 2003 server has been running tip top and has > experienced few issues. We now plan to migrate to SBS 2008 to take advantage > of the newer technologies, and this journal wrap error has become important > again. I have researched the web for days looking for a solution to my > particular situation and cannot find anything that makes sense for this > particular problem. All of the solutions, ideas, posts, KB articles, etc... > that I have been looking at are solutions and ideas for restoring replication > between two or more partners. While these solutions and ideas are talking > about the same error message that I am seeing on my server, I have to assume > that they don't apply to me becasue there is no location on my network to > replicate with. > How can I resolve the NTFRS errors I am seeing with no replication partner > available? It is important that I resolve this before we migrate. All > solutions I have seen say that the server will be removed from the > replication set and then re-added to it which is impossible due to the old > server being gone. > > Thank you in advance! > > See the error message in the event logs? Read it. See what it says to do? See how it says to add an reg key? Do it. It's that easy.
From: JNelsonCPath on 5 May 2010 16:21 Thank you for your response. I have read that blog several times already and from what I understand, I cannot use the burflags option because I do not have a replication partner available. This isnt as easy as a standard replication breaking between two servers; but rather it was a migration that appears incomplete. One piece of advice I was given that sounds promising is to restore the System State data from a backup, however, I need more detail as I think that restoring the System State data would just restore the same problem. "Cris Hanna [SBS - MVP]" wrote: > check this blog > http://msmvps.com/blogs/bradley/archive/2009/11/27/burflags-and-journal-wrap.aspx > > > -- > Cris Hanna [SBS - MVP] (since 1997) > Co-Contributor, Windows Small Business Server 2008 Unleashed > http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1 > Owner, CPU Services, Belleville, IL > A Microsoft Registered Partner > ------------------------------------ > MVPs do not work for Microsoft > Please do not submit questions directly to me. > > "JNelsonCPath" <JNelsonCPath(a)discussions.microsoft.com> wrote in message news:C9202416-6C5F-4062-B7CC-F3F9BBE005DC(a)microsoft.com... > I apologize ahead of time if this question was already discussed, I realize > it is an older topic, but I couldn't find my particular "offshoot" of the > issue so decided to post a question. > > Here is the history of the problem. I have an SBS 2003 Standard domain. > Two years ago, I moved SBS 2003 to more powerful hardware by way of > Microsoft's migration procedure. All went well except for the following: > When I removed the old SBS from the network, I began getting errors in my > file replication log on the new server complaining that it had a journal wrap > error (event ID 13568) and could not read from the NTFS USN journal on the > other server. Well the error is correct because the old server was removed > and no longer exists. I made an assumption that Microsoft's recommended > method for migrating SBS 2003 to new hardware would deal with any replication > issues when the domain data was transferred, but it did not and the new > server has been looking for the old one ever since. > > For the past two years, the SBS 2003 server has been running tip top and has > experienced few issues. We now plan to migrate to SBS 2008 to take advantage > of the newer technologies, and this journal wrap error has become important > again. I have researched the web for days looking for a solution to my > particular situation and cannot find anything that makes sense for this > particular problem. All of the solutions, ideas, posts, KB articles, etc... > that I have been looking at are solutions and ideas for restoring replication > between two or more partners. While these solutions and ideas are talking > about the same error message that I am seeing on my server, I have to assume > that they don't apply to me becasue there is no location on my network to > replicate with. > How can I resolve the NTFRS errors I am seeing with no replication partner > available? It is important that I resolve this before we migrate. All > solutions I have seen say that the server will be removed from the > replication set and then re-added to it which is impossible due to the old > server being gone. > > Thank you in advance! >
From: JNelsonCPath on 5 May 2010 16:52
Thanks, please forgive my ignorance, but I am very nervous to do this as it doesn't appear to fit my situation. Do you have any more detail you can offer me about why this will do the trick in my situation?? The "solution" in the event log removes the server from the replication set and then re-adds it. Is this OK because I only have a single DC? I am also reading way too many posts online about how this procedure harms the SYSVOL folder and removes data from it. If I can get a clear explanation of how to perform this procedure making sure it wont harm my SYSVOL as well as stop the replication set from trying over nad over to reach my old server, I will be happy. "Susan Bradley" wrote: > JNelsonCPath wrote: > > I apologize ahead of time if this question was already discussed, I realize > > it is an older topic, but I couldn't find my particular "offshoot" of the > > issue so decided to post a question. > > > > Here is the history of the problem. I have an SBS 2003 Standard domain. > > Two years ago, I moved SBS 2003 to more powerful hardware by way of > > Microsoft's migration procedure. All went well except for the following: > > When I removed the old SBS from the network, I began getting errors in my > > file replication log on the new server complaining that it had a journal wrap > > error (event ID 13568) and could not read from the NTFS USN journal on the > > other server. Well the error is correct because the old server was removed > > and no longer exists. I made an assumption that Microsoft's recommended > > method for migrating SBS 2003 to new hardware would deal with any replication > > issues when the domain data was transferred, but it did not and the new > > server has been looking for the old one ever since. > > > > For the past two years, the SBS 2003 server has been running tip top and has > > experienced few issues. We now plan to migrate to SBS 2008 to take advantage > > of the newer technologies, and this journal wrap error has become important > > again. I have researched the web for days looking for a solution to my > > particular situation and cannot find anything that makes sense for this > > particular problem. All of the solutions, ideas, posts, KB articles, etc... > > that I have been looking at are solutions and ideas for restoring replication > > between two or more partners. While these solutions and ideas are talking > > about the same error message that I am seeing on my server, I have to assume > > that they don't apply to me becasue there is no location on my network to > > replicate with. > > How can I resolve the NTFRS errors I am seeing with no replication partner > > available? It is important that I resolve this before we migrate. All > > solutions I have seen say that the server will be removed from the > > replication set and then re-added to it which is impossible due to the old > > server being gone. > > > > Thank you in advance! > > > > > See the error message in the event logs? > Read it. > See what it says to do? See how it says to add an reg key? > Do it. > It's that easy. > . > |