halejr1
asked on
Sbs 2k8 - ran complete backup but still have a shit load of log files......why?
I found my backup was broken and assumed this is why I was running out of disk space (over 60gig of log files)
I fixed backup
Ran successful last night
Still 60 gig of logs????
Went wrong?...
What
I fixed backup
Ran successful last night
Still 60 gig of logs????
Went wrong?...
What
what is the location of the logfiles? this information will help to pinpoint the application responisble
Which log files, there are some known issues with massive space loss due to log files:
http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx
http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx
ASKER
The log files are exchange logs..... The backup program is windows backup that comes with sbs.....
Last full backup said completed successfully no errors...
Last full backup said completed successfully no errors...
Did you use the SBS backup? If you use the full SBS backup from the SBS console it should clear those logs and deleted mail items. If you use the manual Windows Backup tool it may not depending on the selections you made.
ASKER
Yes used the sbs backup.... If the database file priv*.mdb gets backed up can't I just delete those file manually?
The location is c:/program files/Microsoft/exchange.. ./mailbox/ first storage group
The location is c:/program files/Microsoft/exchange..
You need to make sure the log files are written to the database or you can loose or corrupt data.
I would try another backup. Others may have more 'efficient' solutions.
I would try another backup. Others may have more 'efficient' solutions.
ASKER
actually I have had multiple backups. Upon further investigation I have found that the backup did report errors in that "exchange may not be restored .....consistency check failed for component Microsoft Exchange Server...."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"consistency check failed " may indicate you still have a problem with the Exchange database". See how the next backup goes.
Cheers!
--Rob
Cheers!
--Rob
ASKER
Found solution through a little surfing. Simpler than most people thought. Log files are not necessary except in the instance of db recovery. Knowing how to safeguard that data is very important. A full backup negates the necessity for prior log files. When IS is mounted it creates base level log files.
Thanks to those who tried...
Thanks to those who tried...
Are these Exchange logs?
if they are excnage logs make sure you are using a exchange aware backup program and doing a full backup of the database. Once you do a full backup of the database with a exchange aware backup program it will flush all the logs.