I have had more experience that I wanted restoring Exchange 5.5, sp4, using BE 8.6. I did not have circular logging enabled either.
Make sure you are doing a full backup of the volumes, along with a full backup nightly of the IS and Directory databases. If so, you will be able to restore everything to the point of the backup. This is my understanding of how BackupExec 8.6 does it... 1. Backs up the database and logs separately. 2. Commits logs to the databases and erases after the backups complete. If you do a restore, there are specific steps you have to take to restore correctly, depending on what you are restoring, the complete OS and Exchange, or just the databases. If it's just the databases, stop the Exchange services and rename all of the mdbdata, mtadata, dsadata, etc. directories to old. Choose the 'Loss Restore' in BackupExec. It restores the databases and logs to disk, starts the services (prompts you first), and then commits any uncommitted log files to the database. > -----Original Message----- > From: Bob Peitzke [SMTP:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 3:50 PM > To: MS-Exchange Admin Issues > Subject: Repost: Question on log files with online backup > > I posted this a couple of weeks ago, and got no response. But nobody > flamed > me either, so assuming y'all just weren't listening, I thought I'd try > again > ... > > We are doing full online backups of our Exchange 5.5/SP3 server, using > BackupExec 8.6 with BE Exchange Agent, but not using the OFO. Circular > logging is disabled. > > I get the following messages in our nightly backup logs: > > - - - - - - - - - - - - - - - - - - - - - - - - - > - > IMS Volume: > -------------------- > Directory \exchsrvr\DSADATA > Unable to open the item \exchsrvr\DSADATA\temp.edb - skipped. > Directory \exchsrvr\dxadata > Directory \exchsrvr\imcdata > Unable to open the item \exchsrvr\imcdata\queue.dat - skipped. > . . . > Directory \exchsrvr\mdbdata > Unable to open the item \exchsrvr\mdbdata\tmp.edb - skipped. > Directory \exchsrvr\MTADATA > Unable to open the item \exchsrvr\MTADATA\AP0.LOG - skipped. > Unable to open the item \exchsrvr\MTADATA\BF0.LOG - skipped. > Unable to open the item \exchsrvr\MTADATA\EV0.LOG - skipped. > . . . > Log Files Volume: > ---------------------------- > Directory \exchsrvr\DSADATA > Unable to open the item \exchsrvr\DSADATA\edb.log - skipped. > Directory \exchsrvr\MDBDATA > Unable to open the item \exchsrvr\MDBDATA\edb.log - skipped. > - - - - - - - - - - - - - - - - - - - - - - - - - > - > > In the Info Stores volume, we select the Information Store and Directory > (entries available because we use BE Exchange Agent) but not the > file-level > priv.edb or pub.edb, of course, as they are open. > > The Exchange DR white paper says that committed log files are backed up > then > purged, specifically referencing NTBACKUP only for incrementals. > > Now I'm worried that we're not backing up everything we need to restore a > current system in case of failure. If I restore the database but not > uncommitted logs, have we just lost some recent messages? > > Advice? > > TIA > > Bob Peitzke > Information Systems Manager > Sander A. Kessler & Associates > Santa Monica, CA, USA > [EMAIL PROTECTED] > > Accepting flames off-line ;o) > > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
