• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 682
  • Last Modified:

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
0
halejr1
Asked:
halejr1
1 Solution
 
KenMcFCommented:
What backup program are you using?
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.

0
 
jaredrowlingCommented:
what is the location of the logfiles? this information will help to pinpoint the application responisble
0
 
Rob WilliamsCommented:
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
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
halejr1Author Commented:
The log files are exchange logs..... The backup program is windows backup that comes with sbs.....

Last full backup said completed successfully no errors...

0
 
Rob WilliamsCommented:
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.
0
 
halejr1Author Commented:
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
0
 
Rob WilliamsCommented:
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.
0
 
halejr1Author Commented:
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...."
0
 
halejr1Author Commented:
Problem solved.....
Dis/Unmounted information stores
Moved all log files to folder
Mounted IS
Ran backup
Deleted folders with log files
Gained 49gig


 
0
 
Rob WilliamsCommented:
"consistency check failed " may indicate you still have a problem with the Exchange database". See how the next backup goes.
Cheers!
--Rob
0
 
halejr1Author Commented:
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...
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now