I cannot get the logs to flush after a full backup with Backup exec 11d (set to flush commited logs). Eseutil reports that the database is in a consistant state and even reports a full backup that coinsides with the Backup Exec job. Any ideas?

Are you running in a cluster? I have seen issues where if the cluster is having issues the backup will not flush the logs with BE Check your event logs to see if there are other errors taking place and if so correct them and try a new backup How long has this been going on, i.e. what changed since that time Troy Werelius www.Lucid8.com

1) no cluster 2) no errors 3) a few months, at least This is a new client we picked up recently. The tech onsite states that he doesn't think the logs ever flushed on their own so he just MANUALLY deletes them from time to time. The part that I'm a little fuzzy on is the mechanics of log flushing. Does BE actually do the deleting or is it just telling the Exchange server to do the deleting? Since eseutil is reporting that Exchange knows that a full backup is being completed is this a problem with Exchange? Thanks for your help Troy.

On Sun, 2 Jan 2011 01:13:15 +0000, Alceryes wrote: >1) no cluster 2) no errors 3) a few months, at least > >This is a new client we picked up recently. The tech onsite states that he doesn't think the logs ever flushed on their own so he just MANUALLY deletes them from time to time. The part that I'm a little fuzzy on is the mechanics of log flushing. Does BE actually do the deleting or is it just telling the Exchange server to do the deleting? Since eseutil is reporting that Exchange knows that a full backup is being completed is this a problem with Exchange? The problem may be a damaged Exx.chk file. Dismount the database(s) in the storage group and run "eseutil /mk c:\directory\eXX.chk. Verify that the log files noted in the file exist and that there are no missing log files. I've seen chk files that reference log files that no longer exist and, of that's the case, the system attendant service won't purge the log files. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Rich, couple of Q's... I can't take the database down for any major length of time. Does this check just look at header info? Does it automatically start some type of repair that may take hours to complete? What can I do to repair the .chk file if it is indeed damaged?

Do you have the same problem if you do a backup with NTBACKUP as well?

Haven't done the ntbackup yet. The db has to stay offline during the whole backup so I think I'm going to take it down for a few to check the .chk file first. Also, am I right in assuming that, since Exchange knows that a full backup is being completed, the problem might be with Exchange? This won't be done for a couple of days. I'll let you guys know how it goes.

Haven't done the ntbackup yet. The db has to stay offline during the whole backup so I think I'm going to take it down for a few to check the .chk file first. Also, am I right in assuming that, since Exchange knows that a full backup is being completed, the problem might be with Exchange? This won't be done for a couple of days. I'll let you guys know how it goes. "The db has to stay offline during the whole backup" Only if you are doing it wrong :) If you are doing an online Exchange aware backup, then the store stays online and mounted and the transaction logs that are no longer needed are removed. Are you doing online or offline backups?

As Andy stated, if you are taking the databases offline and then doing file based backups then the logs will not be flushed, however if you are using the Exchange Aware agent in BE then the databases will stay online and the appropriate logs will be flushed at the end of the process.Troy Werelius www.Lucid8.com

On Sun, 2 Jan 2011 14:48:31 +0000, Alceryes wrote: >I can't take the database down for any major length of time. Does this check just look at header info? Yes. It shouldn run for more than a second (and usually only a fraction of that). >Does it automatically start some type of repair that may take hours to complete? Nope. >What can I do to repair the .chk file if it is indeed damaged? You can't (or shouldn't). The safest way to deal with this is to start a new log file generation. Dismount the database(s) in the storage group, run "eseutil /mh" to verify they're in a "clean shutdown" state, and then MOVE (don't copy) the log files and chk file from the log directory. Remount the database(s) and make an immediate full/normal backup. I see Andy's already mentioned trying to use NTBACKUP. That's another alternative and one that would (if it works) point out that the other backup program is at fault. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

So I can run an 'NTBACKUP' to backup the exchange database while it's online? I was referencing this article - http://www.msexchange.org/tutorials/Exchange-2003-Backup-Restore-NTBACKUP.html ...that talks about NTBACKUP not using a VSC service requestor, thereby necessitating the dismounting of the database(?) TIA.

So I can run an 'NTBACKUP' to backup the exchange database while it's online? I was referencing this article - http://www.msexchange.org/tutorials/Exchange-2003-Backup-Restore-NTBACKUP.html ...that talks about NTBACKUP not using a VSC service requestor, thereby necessitating the dismounting of the database(?) TIA. Yes you can run NTbackup while Exchange is online and IF you have the BE Exchange Agent you can backup online with it as well I think if you use SP1 VSC will work with Exchange on 2003, however VSC for 2003 can be a bit challenging at times so IMO I would first look at getting NTbackup or BE for Online backups working properly i.e. just backup to disk or other medium to ensure you are protected. Once you have a good backup in place then I would stair step to utilizing VSC Troy Werelius www.Lucid8.com

This command didn't give me the info I was expecting - LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x53C95,2100,0) FullBackup: (0x52CDB,8,16) FullBackup time: 12/29/2010 16:15:35 IncBackup: (0x0,0,0) IncBackup time: 00/00/1900 00:00:00 Signature: Create time:10/13/2006 13:46:30 Rand:63952 Computer: Env (CircLog,Session,Opentbl,VerPage,Cursors,LogBufs,LogFile,Buffers) ( off, 552, 27600, 3992, 27600, 500, 10240, 229376) Do I need to run it with a different argument?

On Wed, 12 Jan 2011 01:59:58 +0000, Alceryes wrote: >This command didn't give me the info I was expecting - What were you expecting? > >LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x53C95,2100,0) FullBackup: (0x52CDB,8,16) FullBackup time: 12/29/2010 16:15:35 IncBackup: (0x0,0,0) IncBackup time: 00/00/1900 00:00:00 Signature: Create time:10/13/2006 13:46:30 Rand:63952 Computer: Env (CircLog,Session,Opentbl,VerPage,Cursors,LogBufs,LogFile,Buffers) ( off, 552, 27600, 3992, 27600, 500, 10240, 229376) > >Do I need to run it with a different argument? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP