Re: SCR troubleshooting
Sounds like you missed the -standbymachine parameter of the disable command. Good to know so we don't all start digging through adsiedit... -alex On Mon, Dec 8, 2008 at 6:54 AM, Russ Patterson rus...@gmail.com wrote: FYI - MS got us fixed up - Using ADSIEdit, we went here: CN=[*Storage Group*],CN=InformationStore,CN=[*Server Name*],CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=[*Org*],CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[*Domain*],DC=com Right-clicked the Storage Group that was just below CN=Information Store, in the properties sheet is an attribute: msExchStandbyCopyMachines It had as its value a list with both the old, decommissioned server and the new one we were trying to use as an SCR target. Removing the old server from that list, then restarting the IS and the MSExchangeRepl service and then performing a full backup got rid of all the old TLogs, and started the new target's TLog truncation, too. On Wed, Dec 3, 2008 at 12:35 PM, Russ Patterson rus...@gmail.com wrote: I thought I did - used Disable-StorageGroupCopy - isn't that all there is to stopping it? - then removing the store TLogs viz the file system on the Target (which of course completely went away.) On Wed, Dec 3, 2008 at 12:30 PM, KevinM kev...@wlkmmas.org wrote: Server gone.. did you remove SCR replication settings via the command line when you took down the server? Anytime I've touched SCR I've removed it all, then started from scratch with a reseed to fix whatever I busted. *From:* Russ Patterson [mailto:rus...@gmail.com] *Sent:* Wednesday, December 03, 2008 9:18 AM *To:* MS-Exchange Admin Issues *Subject:* Re: SCR troubleshooting We did NOT remove the SCR source, we removed the SCR Target - which was the machine that lost the trust etc. The SCR source is still here being the source. On Wed, Dec 3, 2008 at 12:05 PM, KevinM kev...@wlkmmas.org wrote: Older should have been Old SCR replica server…. I missed a bunch of words on that one. *From:* KevinM [mailto:kev...@wlkmmas.org] *Sent:* Wednesday, December 03, 2008 8:32 AM *To:* MS-Exchange Admin Issues *Subject:* RE: SCR troubleshooting You removed the older, and created a new one, and the old SCR setup is still there??? *From:* Russ Patterson [mailto:rus...@gmail.com] *Sent:* Wednesday, December 03, 2008 7:01 AM *To:* MS-Exchange Admin Issues *Subject:* SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:00 00:15:00 ExchSrvr4.domain.co... 1 00:30:00 00:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: SCR troubleshooting
FYI - MS got us fixed up - Using ADSIEdit, we went here: CN=[*Storage Group*],CN=InformationStore,CN=[*Server Name*],CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=[*Org*],CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[*Domain*],DC=com Right-clicked the Storage Group that was just below CN=Information Store, in the properties sheet is an attribute: msExchStandbyCopyMachines It had as its value a list with both the old, decommissioned server and the new one we were trying to use as an SCR target. Removing the old server from that list, then restarting the IS and the MSExchangeRepl service and then performing a full backup got rid of all the old TLogs, and started the new target's TLog truncation, too. On Wed, Dec 3, 2008 at 12:35 PM, Russ Patterson [EMAIL PROTECTED] wrote: I thought I did - used Disable-StorageGroupCopy - isn't that all there is to stopping it? - then removing the store TLogs viz the file system on the Target (which of course completely went away.) On Wed, Dec 3, 2008 at 12:30 PM, KevinM [EMAIL PROTECTED] wrote: Server gone.. did you remove SCR replication settings via the command line when you took down the server? Anytime I've touched SCR I've removed it all, then started from scratch with a reseed to fix whatever I busted. *From:* Russ Patterson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 9:18 AM *To:* MS-Exchange Admin Issues *Subject:* Re: SCR troubleshooting We did NOT remove the SCR source, we removed the SCR Target - which was the machine that lost the trust etc. The SCR source is still here being the source. On Wed, Dec 3, 2008 at 12:05 PM, KevinM [EMAIL PROTECTED] wrote: Older should have been Old SCR replica server…. I missed a bunch of words on that one. *From:* KevinM [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 8:32 AM *To:* MS-Exchange Admin Issues *Subject:* RE: SCR troubleshooting You removed the older, and created a new one, and the old SCR setup is still there??? *From:* Russ Patterson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 7:01 AM *To:* MS-Exchange Admin Issues *Subject:* SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:00 00:15:00 ExchSrvr4.domain.co... 1 00:30:00 00:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: SCR troubleshooting
You removed the older, and created a new one, and the old SCR setup is still there??? From: Russ Patterson [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 7:01 AM To: MS-Exchange Admin Issues Subject: SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:0000:15:00 ExchSrvr4.domain.co... 1 00:30:0000:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: SCR troubleshooting
Apparently so, even though I used DIsable-StorageGroupCopy got no errors before we killed the old box. Showing the standbymachines for our SCR source still lists the old, dead server as well as the new target. The main thing I'm worried about (which is why I'm calling MS later) is that the TLogs aren't going away on the source machine, and haven't for several days (since the machine trust was 'lost.') All I've found for logging is Set-EventLogLevel msexchange repl\Service -level 7. Is that ALL there is? On Wed, Dec 3, 2008 at 11:31 AM, KevinM [EMAIL PROTECTED] wrote: You removed the older, and created a new one, and the old SCR setup is still there??? *From:* Russ Patterson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 7:01 AM *To:* MS-Exchange Admin Issues *Subject:* SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:00 00:15:00 ExchSrvr4.domain.co... 1 00:30:00 00:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: SCR troubleshooting
Older should have been Old SCR replica server I missed a bunch of words on that one. From: KevinM [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 8:32 AM To: MS-Exchange Admin Issues Subject: RE: SCR troubleshooting You removed the older, and created a new one, and the old SCR setup is still there??? From: Russ Patterson [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 7:01 AM To: MS-Exchange Admin Issues Subject: SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:0000:15:00 ExchSrvr4.domain.co... 1 00:30:0000:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: SCR troubleshooting
We did NOT remove the SCR source, we removed the SCR Target - which was the machine that lost the trust etc. The SCR source is still here being the source. On Wed, Dec 3, 2008 at 12:05 PM, KevinM [EMAIL PROTECTED] wrote: Older should have been Old SCR replica server…. I missed a bunch of words on that one. *From:* KevinM [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 8:32 AM *To:* MS-Exchange Admin Issues *Subject:* RE: SCR troubleshooting You removed the older, and created a new one, and the old SCR setup is still there??? *From:* Russ Patterson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 7:01 AM *To:* MS-Exchange Admin Issues *Subject:* SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:00 00:15:00 ExchSrvr4.domain.co... 1 00:30:00 00:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: SCR troubleshooting
Server gone.. did you remove SCR replication settings via the command line when you took down the server? Anytime I've touched SCR I've removed it all, then started from scratch with a reseed to fix whatever I busted. From: Russ Patterson [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 9:18 AM To: MS-Exchange Admin Issues Subject: Re: SCR troubleshooting We did NOT remove the SCR source, we removed the SCR Target - which was the machine that lost the trust etc. The SCR source is still here being the source. On Wed, Dec 3, 2008 at 12:05 PM, KevinM [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Older should have been Old SCR replica server I missed a bunch of words on that one. From: KevinM [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 03, 2008 8:32 AM To: MS-Exchange Admin Issues Subject: RE: SCR troubleshooting You removed the older, and created a new one, and the old SCR setup is still there??? From: Russ Patterson [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 03, 2008 7:01 AM To: MS-Exchange Admin Issues Subject: SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:0000:15:00 ExchSrvr4.domain.co... 1 00:30:0000:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: SCR troubleshooting
I thought I did - used Disable-StorageGroupCopy - isn't that all there is to stopping it? - then removing the store TLogs viz the file system on the Target (which of course completely went away.) On Wed, Dec 3, 2008 at 12:30 PM, KevinM [EMAIL PROTECTED] wrote: Server gone.. did you remove SCR replication settings via the command line when you took down the server? Anytime I've touched SCR I've removed it all, then started from scratch with a reseed to fix whatever I busted. *From:* Russ Patterson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 9:18 AM *To:* MS-Exchange Admin Issues *Subject:* Re: SCR troubleshooting We did NOT remove the SCR source, we removed the SCR Target - which was the machine that lost the trust etc. The SCR source is still here being the source. On Wed, Dec 3, 2008 at 12:05 PM, KevinM [EMAIL PROTECTED] wrote: Older should have been Old SCR replica server…. I missed a bunch of words on that one. *From:* KevinM [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 8:32 AM *To:* MS-Exchange Admin Issues *Subject:* RE: SCR troubleshooting You removed the older, and created a new one, and the old SCR setup is still there??? *From:* Russ Patterson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, December 03, 2008 7:01 AM *To:* MS-Exchange Admin Issues *Subject:* SCR troubleshooting Seasons Greetings All - I'm having a bit of trouble with SCR. Anyone have any suggestions about what logging levels to increase to help troubleshoot before I call MS? If anyone's feeling generous/adventurous here's the issue: You may remember I asked this list about an Exchange server who lost the machine trust to the domain a few weeks ago. Apparently, when this happened, the transaction logs stopped getting cleared on the SCR source when backed up by our CommVault BU. The suggestions here were to tear down that machine build a new one. I did so, and before I tore down the old machine, I thought I stopped SCR to that machine. ( I used Disable-StorageGroupCopy : got no errors) Yesterday we started SCR to the replacement, that works, but it appears that the command above didn't work, because when I do this now: [PS] C:\Windows\System32$sg=Get-StorageGroup ExchServ\SCRStorageGroup [PS] C:\Windows\System32$sg.StandbyMachines I get this: NodeName Version ReplayLagTime TruncationLagTime --- - - ExchSrvr2.domain.co... 1 00:30:00 00:15:00 ExchSrvr4.domain.co... 1 00:30:00 00:15:00 the bottom one, ExchSrvr4 is the 'retired' machine (gone for good, no recourse.) It appears that nowhere (target or source) are Transaction logs going away . Tho' since we just started the new SCR target machine yesterday afternoon, maybe it's just not clearing those YET. I'm starting with MS, then CommVault but was hoping you folks could at least help me bump logging levels up so I'd have decent data for PSS. Any suggestions? Thanks! ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
