We are having problem with our excahnges erver, we never ran defrag at all over 18 months / zero maintenance.exchange 2007 serveron windows 2003 OS.Now started seeing problems..edb file is 38 GB and transaction log files are almost 135 GB close to 140,000 transaction log files are present in the same folder where .edb file is.How to run a backup on exchange 2007, is there a backup software already built into it ?Or will i have to install a thirs party backup software, please help.I read somewhere while doing the backup we can specify to delete all transaction logs once after a successful backup is done, is that correct?Thank you all very much for the helpful info.

You can use ntbackup feature of the windows 2003. Take a full back up of the information store which will purge the logs into the database. Follow this http://www.petri.co.il/backup_exchange_2000_2003_with_ntbackup.htmIf you wnat , you can use backupexec from symantec which can do the same for you.If you want to manually remove the log files follw these stepshttp://support.microsoft.com/default.aspx?kbid=240145Raj

Raj has pointed you to some links for Exchange 2003. The NT Backup tool basically works the same with Exchange 2007 on Windows 2003. Petri's description is more detailed, and still applies to Exchange 2007. Here's a shorter version for Exchange 2007Backing Up an Exchange 2007 Mailbox Server (by Henrik Walther)http://www.msexchange.org/tutorials/Configuring-Exchange-Server-2007-Preview-Chapter9-Disaster-Recovery-Exchange-Server-2007.html Another free tool comes with Exchange 2007 SP2. However, if you have not upgraded to Exchange SP2 yet, first thing first: Do a backup that will purge your transaction log files.Uncovering the new Exchange 2007 SP2 Volume Snapshot (VSS) Plug-in (Part 1)http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/uncovering-new-exchange-2007-sp2-volume-snapshot-vss-plug-in-part1.html Uncovering the new Exchange 2007 SP2 Volume Snapshot (VSS) Plug-in (Part 2)http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/uncovering-new-exchange-2007-sp2-volume-snapshot-vss-plug-in-part2.html The VSS snap-in that comes with Exchange 2007 SP2 allows for recovery to a recovery storage group (described above), however not as easy as with NT Backup or Symantec Backup Exec:Symantec Backup Exec for Windows Servershttp://www.symantec.com/business/backup-exec-for-windows-serversAdditionally you will needthe Exchange agent, allowing recovery of individual messages, folders and mailboxesin seconds with patent-pending Granular Recovery Technologyhttp://www.symantec.com/business/products/agents_options.jsp?pcid=pcat_business_cont&pvid=57_1 This is definitely the easiest and mot versatile backup application to use:Symantec Backup Exec for Windows Servers - Voted MSExchange.org Readers Choice Award Winner - Exchange Backup & Recovery (May 27, 2009 )http://www.msexchange.org/news/general/MSExchange-Readers-Choice-Award-Exchange-Backup-Recovery-Symantec-Backup-Exec-Windows-Servers-Apr09.html It is available for a free 60-day evaluation.My recommendation would be:* purge those transaction logs with NT Backup or the free download of Backup Exec.* don't try to delete the log files manually* you don't need an offline de-fragmentation of your database (you probably never will)* Implement an automated daily backup routine with either NT Backup, the VSS Snapin or Backup ExecAs to maintenance tasks: Basic maintenance is by default implemented with Exchange 2007. Take a look here for more advanced options:Exchange 2007 Online Maintenance Database Scanning (Part 1)http://www.msexchange.org/articles-tutorials/exchange-server-2007/monitoring-operations/exchange-online-database-scanning-part1.html Exchange 2007 Online Maintenance Database Scanning (Part 2)http://www.msexchange.org/articles-tutorials/exchange-server-2007/monitoring-operations/exchange-online-database-scanning-part2.htmlMCTS: Messaging | MCSE: S+M | Small Business Specialist

Hello Raj,Thank you very much for the helpful links:Our exchange server does'nt have a backup tape drive.Is it possile to backup on the same machine on another drive?Where we have almost 250 GB of space.I am really fedup with the transaction log files, theye are almost 140,000 eacjh one 1 MB in size, want to get rid of those and enable circular logging. i guess that option will not not create this many log files.

Hi, You can put the backup data on a drive on the same machine no probs.. once done copy the backup file to a different machine through network.Hari Bylapudi

yes , you can do that. You can do it either on network drive or the same drive oif the system.I will not reommnend to switch on the cicular loggin. Instead make sure you haveproper backup system in place that will keep purging the log files and you will not have any issue. Raj

Already said, enabling circular logging is not a good idea. These transaction logs can be used for database recovery purposes. If you have storage space constraints you may opt for incremental backups which will help you purging the commited log files and at the same time backing up the ones which are not commited. That way you can get rid of huge number of transaction logs and yet maintain your chances of recovery. Milind Naphade | MCTS:M (Exchange 2007 and 2010) | http://www.msexchangegeek.com

Hello,if i use teh rugular winodws backup utility via program / accessories.Once the backup is done successfully and created .bkf file.if after backup is done, what if the transaction log files are still present and did'nt get purged.can i delete them manually, since the backup job is done successfully?Thank you all very much for the helpful info.Raj

Raj,Though you can delete them manually its not recommended as you may end up deleting uncommited files as well in stead of deleting them you can fix the problem of files not being purged. Here are few resource:http://social.technet.microsoft.com/forums/en-US/exchangesvravailabilityandisasterrecovery/thread/17a25ee4-e433-42b0-a2e1-9d0f78e739b7/Milind Naphade | MCTS:M (Exchange 2007 and 2010) | http://www.msexchangegeek.com

I would probably commit the files using "eseutil" or "isinteg" before manually deleting them. You can delete them, but what happens when the database ask for "E00001983D.log" for instance.

I would probably commit the files using "eseutil" or "isinteg" before manually deleting them. You can delete them, but what happens when the database ask for "E00001983D.log" for instance.

I would probably commit the files using "eseutil" or "isinteg" before manually deleting them. You can delete them, but what happens when the database ask for "E00001983D.log" for instance.