Johnny, Something else has that file open. Check for running processes, editors, cmd windows, etc.
Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 09/08/2011 04:02:21 PM: >> From: Johnny Lea <[email protected]> >> To: [email protected] >> Date: 09/08/2011 04:05 PM >> Subject: exefull.log locked in Exchange 2010 >> Sent by: "ADSM: Dist Stor Manager" <[email protected]> >> >> We are moving to Exchange 2010 and backups have been running fine >> since setting them up. Initially I did not allow enough maxscratch >> in the stgpool so the backups failed a couple of nights ago. I >> increase the maxscratch but now the tdpexcc backup command (tdpexcc >> backup /excludedagactive /tsmoptfile=dsm.opt /logfile=excsch.log >> >> excfull.log) fails with error "The process cannot access the file >> because it is being used by another process." >> I was able to determine the file that it couldn't access was the >> excfull.log. It seemed to have gotten "locked" . I sent the >> output of the excfull.cmd to another another log file and backups >> were able to run again. >> Has anyone seen this scenario and know why the log file remained >> locked after the initial failure? >> >> TSM server 6.2 >> TDP for mail 6.1.2 >> >> Thanks, >> Johnny
