Exchange SCR keeps creating logs on the source server even though SCR has been disabled.

I recently setup SCR between two Standalone server; a physical and virtual server. The physical server was the source and the VM server was the target. We decided we no longer needed the virtual server so I diabled replication, removed exchange from the virtual server and deleted the virtual sever.

Logs are still being created on the source server even though Get-storagegroupstatus command reports that Summary copy status = disabled.

Any ideas on how I can get this logging to stop? I've tried reboot the server but the issue still exists...
NTS_SupportAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TyBeattyCommented:
Exchange creates logs regardless of Cluster config.  Are you seeing the Transaction logs created?  Those are created for every action done in Exchange for Restore purposes.

Are these the logs you are seeing??
0
NTS_SupportAuthor Commented:
These are logs in the storage group folder. Here is an example of a log name: E000004ED12.log. They are each 1 MB.

 Didn't think that these were here before replication but can't be sure. These go back several days. Replication would clear all of them out other than 100 or so. I'm up to 1700 files after I manually cleaned these out two days ago.

Did a full exchange backup this morning as well hoping this would clear them but no luck.
0
TyBeattyCommented:
Yes those are the Exchange log files.  Those are created no matter what or how you are running Exchange.  Basically it keeps those as a "transaction log" so that any time a server where to fail you can restore the last backup and all logs since that.  You can then replay them and have your data back up today.

Backups will truncate the logs as long as you are using an Excange away backup solution.  How did you back it up?

But either way those logs are going to be there no matter what, they are a normal component of exchange, they even dropped from 5mb to 1mb in Exchange 2007 to help facilitate SCR and log shipping form clusters.

Thanks,
Tyson
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

TyBeattyCommented:
Some other things you can look at just to be sure...  (again assuming you are using an Exchange Aware Backup Solution)


Check the application log for errors that say that there's a missing log file. If there's a gap in the log file sequence the log files won't purge on backup.

Check the E*.chk file for problems (eseutil /mk <checkpointfilename>).  Perhaps the checkpoint file says that there are log files that no
longer exist on the server. That, too, will prevent the log files from purging.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
NTS_SupportAuthor Commented:
We are using NTBackup. I believe it is exchange aware. I'll check the event logs as I haven't done that yet.
0
TyBeattyCommented:
If you are using NTBackUp and actaully selecting the Exchagne via it's "Agent" so you are physically going to exchange and selecting the Storage Group/Database...   It should truncate the logs on successful completion.  As long as your not just doing a file type backup of the DB.
0
NTS_SupportAuthor Commented:
This server has run a full backup everyday for the past two years and logs have never built up like this. I can't see anything in the app event log about a  missing log file. I attempted to look at the .chk file but got a "cannot find" error. Did I get the command format correct?
1.JPG
0
TyBeattyCommented:
Command is correct, but you are going to have to give the path to E00.chk

The way you ran it, the only place it is looking is the local directory.
0
TyBeattyCommented:
Are you running NTBackup local to the Exchange server?  If I recall right that is the only way that NTBackup will allow you to select the "Information Store" and run correctly to clear the logs and such.
0
NTS_SupportAuthor Commented:
Yes. We are running NTBackup on the local exchange server. System state and information store are being backed up.  I'm going to run the job manually just in case the scheduled job doesn't have the correct parameters. It's been so long since I set the job up that I can't remember.

Here are the results of the checkpoint job.
2.JPG
0
TyBeattyCommented:
Yeah everything looks good.  There is no reason really that NTBackup shouldn't be truncating the logs.  The only other thing I can think of would be if the cluster did something to it that is causing it not to remove, but that should not be the case.  The logs are created the same either way, difference is they are not shipping over to another cluster node anymore.

But at the end of the day ever in an active cluster the logs truncate on backup.
0
TyBeattyCommented:
If you are running low on space this is a good article to cover how to manually and safely remove the log files.

It also may not be an all bad idea to do this just to get everything back to a "from scratch" sort of state with the logs and then see if your problem persists.
0
TyBeattyCommented:
sorry actually you can scratch that last post.  That is for 2003 not 2007.  Lost my mind there for a moment, sorry.
0
NTS_SupportAuthor Commented:
Most days I wish I were still working with 2003 :) I'll let you know how the backup goes. My guts stilll says that SCR did not disable properly.
0
TyBeattyCommented:
It is very possible.  Like I said the logs would still be there, but the should be Trunc'ing for you.  The only way to really not have many logs is to use circular logging, but personally I don't think there is ever a good reason to use that!!  Lol

E2K7 is nice but it certainly complicated some things!!!!
0
NTS_SupportAuthor Commented:
Manual backup failed to truncate logs. Looks like it time to open a ticket with microsoft. I'll award you points since you were the only one to post and had some good ideas.
0
TyBeattyCommented:
Thank you much appreciated.  Yeah, will be interested to see what they have to say.  Since I use to work for the team you are going to be calling I have an idea what they are going to tell you...  :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.