Microsoft Exchange 2007 -seeding: False Copy:Failed
Hi, I got this error message from exchange server 2007. Any idea how i can fix it..Thanks a lot. I think the log is lot, but no idea using the update-storagegroup copy cmdlet.. how should i do??The log file 3696 for MAIL\First Storage Group is missing on the production copy. Continuous replication for this storage group is blocked. If you removed the log file, please replace it. If the log is lost, the passive copy will need to be reseeded using the Update-StorageGroupCopy cmdlet in the Exchange Management Shell.
December 29th, 2009 4:46am

This is what I found for you: "Now that we know message tracking is enabled by default, where are the log files stored? Those of you familiar with Exchange 2000 and Exchange 2003 will remember that, by default, the message tracking logs are stored in the \Program Files\exchsrvr\{servername}.log folder as shown above in Figure 1. With Exchange 2007, the default folder is a little deeper than before: \Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking. Should you wish to change the location of the message tracking log files, this can be achieved by running the following cmdlet: Set-TransportServer SERVERNAME –MessageTrackingLogPath LOGPATH For example, if you wished to change the tracking log file directory to D:\Tracking Logs on server E2K7, you’d use the following cmdlet: Set-TransportServer E2K7 –MessageTrackingLogPath “D:\Tracking Logs” One useful thing that I found is that if the proposed tracking log file directory does not exist prior to running the cmdlet, it will be created for you when you run the cmdlet. There are several additional things that are worth noting about changing the message tracking directory: After changing the location of the log files, existing logs will remain in their previous location; new logs will be created in the new location. The new location cannot be a UNC path as it must be local to the Exchange 2007 server. Although there are situations where permissions can be set automatically, I still think it prudent to ensure that the proper permissions are set on any new directory that you have created before moving the logs. The Administrator account needs Full Control, System needs Full Control, and Network Service needs Read, Write, and Delete Subfolders and Files."Found Here:http://www.msexchange.org/tutorials/Exchange-2007-Message-Tracking-Part1.html
Free Windows Admin Tool Kit Click here and download it now
December 29th, 2009 5:33am

This link explains how to use the Update-StorageGroupCopy cmdlet:http://technet.microsoft.com/en-us/library/aa998853(EXCHG.80).aspx
December 29th, 2009 6:06pm

Hi,Please suspend the replication for the storage group by running the following command:Suspend-StorageGroupCopy -Identity:Server\StorageGroupNameThen remove database files, all log files, and checkpoint files from the passive node. Remove *.log, *.jrs, *.chk, and the .edb files from the configured directories (logs directory, the system files directory, and the directory hosting the database file).Next run the following command to seed the storage group copy on the passive node.Update-StorageGroupCopy -Identity:<Server\StorageGroupName>Finally, run Resume-StorageGroupCopy -Identity:Server\StorageGroupName.After that, please verify that replication is working correctly by using the Get-StorageGroupCopyStatus.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
December 31st, 2009 11:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics