thalika
asked on
Transcation Log's are not cleared even after several NTBackup and BrighStor ArcServ Backup
After several attempt to clear the transcatoin logs of the exchange server 2003 by initiating the full backup using ntbackup and brightstor arcstor i am not able to achive to clear the log files.
There is no error on the backup report (both backups). Once the log partation was almost to full i moved couple of gb's to another free volume too.
Apperciate you prompt reply.
There is no error on the backup report (both backups). Once the log partation was almost to full i moved couple of gb's to another free volume too.
Apperciate you prompt reply.
kieran_b
So you have already moved some of the logs out of the drive? Why?
How did you move the logfiles? Did you move the logfiles randomly selecting? Then it is obvious. ESE engine of the exchange server detects and deletes the transaction logfiles which are in sequence after each full or incremental backup. You would need to delete the logfiles in order from the oldest logfile to recent one. Now you need to delete/move the logfiles manually form oldest date to the recent date maintaing the sequence.
Sekhar
Sekhar
ASKER
Well i dont have anyother open other than to gain some space on that volume because it was about to get full .
I have moved the log files based on the date ..example...i moved all the filed on 26th and 27th to seperate volume to gain space and initiated the full backups.
I have moved the log files based on the date ..example...i moved all the filed on 26th and 27th to seperate volume to gain space and initiated the full backups.
>>Well i dont have anyother open other than to gain some space on that volume because it was about to get full .
No, you did - you could have compressed the files - no need to get defensive, we are just trying to figure out how much damage you have caused.
In all honesty, I would take a good backup, enable circular logging, reboot, manually delete the remaining out of sync transaction logs, disable circular logging and reboot again.
No, you did - you could have compressed the files - no need to get defensive, we are just trying to figure out how much damage you have caused.
In all honesty, I would take a good backup, enable circular logging, reboot, manually delete the remaining out of sync transaction logs, disable circular logging and reboot again.
ASKER
Kirean..
Its happend on weekday morning and i was avoiding the downtime of the messagaing system.. In order for me to do the backup (its take 2 to 3hours) then ok enable the circular logging ,restart...then disable ..takes downtime isnt??
Its happend on weekday morning and i was avoiding the downtime of the messagaing system.. In order for me to do the backup (its take 2 to 3hours) then ok enable the circular logging ,restart...then disable ..takes downtime isnt??
That is the proper solution - what you could have done was simply enabled compression on the location of the transaction logs - you would have got a stack of space back (like 75%)
But, we are past that now - moving forward, we need to kill off the rest of the transaction logs as gracefully as possible.
But, we are past that now - moving forward, we need to kill off the rest of the transaction logs as gracefully as possible.
ASKER
How can i enable the compression on the log folder ...(normal folder compression )
Now what can be done to clear it of the log files..will the full backup will do the cleanup again ...i dont think because i did 3 sucessful full backup.
Now what can be done to clear it of the log files..will the full backup will do the cleanup again ...i dont think because i did 3 sucessful full backup.
ASKER
Kieran.
One more think i forget to mentiond to it...before moving the file i dd a full backup but that backup was not cleand the log file.
One more think i forget to mentiond to it...before moving the file i dd a full backup but that backup was not cleand the log file.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So without doing the circular logging we cannot contiue to clear the logs using the full backup's? any ideas which is this happening? i moved the log files which are pretty much old and there were backups after these log files (not full) and once the full backup failed the logs did not cleard.
you aren't clearing the logs using full backups anyway - it is stuck because you broke the cycle