Hi Adrian, With 57,000 1M (not 1G) log files, it will take a while to run. This indicates that you have done some heavy migrations or that you have not run a backup for a long time (or ever). When circular logging is off, it is imperative that you run regular FULL or INCREMENTAL backups to clear the log space.
At this point, dismount the database, turn circular logging on, remount the database, make sure the log file space get cleared, and then run a full backup. If you are doing mailbox migrations, keep it like this until they are complete. After that, you can turn circular logging back off. And after all that, run a regular FULL or FULL+INCREMENTAL backup strategy. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 10/01/2010 09:04:18 AM: >> From: Adrian Compton <acomp...@aspenpharma.com> >> To: ADSM-L@vm.marist.edu >> Date: 10/01/2010 09:05 AM >> Subject: Re: TDP for Exchange 6.1.2 >> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> >> >> Hi Del,, >> >> >> Its making more sense as you and I chat. >> There is a 47GB data store, BUT!!!!! 57000 x 1GB log files... I >> presume this is why the integrity check is taking so long. >> Circular logging is off as well. >> >> I presume I should turn the circular logging on, to reduce the >> number of log files and then after first successful backup we could >> turn it on again, as the Exchange admin is adamant it should be on? >> >> Being the TSM admin to make this work I am caught between a rock >> and a hard place so to speak..
