If this is the case, perhaps you (or the exchange administrator) should
spend an evening with eseutil (exchange 5.5) or edbutil (prior versions)
and defrag your database.    Exchange's online defragging doesn't work very
well.  If you take the database offline and defrag it, the database will be
much smaller afterwards.   Exchange information stores only grow unless you
take them offline and defrag them.

Christian Klein
IT Server Operations
Amsouth Bancorporation
cklein AT amsouth DOT com





"Feng, Sherry" <FengS AT AEGISLIMITED DOT COM> on 07/19/99 09:44:47 AM


Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Christian Klein/BIRMINGHAM/AL/AMSOUTH BANK)
Subject:  Re: Backup Exchange fail




Thank you very much. I will try to adjust IS maintenance schedule time
to see if this can help.

I have another reason causing Backup Exchange fail is end of tape error.
My exchange IS is 10G and 6G backup to tape after compression. I have to
update backup tape to read-only everyday to let next backup goes to new
tape. Otherwise I will get following error and backup fail.
Is this a bug on Exchange Agent or I did something wrong. If IS is
bigger than 10G(My tape is 10G each). How can I do?


07/18/1999 00:27:43  ANR8263W End of tape detected on 3590 volume C10429
in
                      drive TAPMLB01 (TAP02) of library 3494LIB.
07/18/1999 00:27:43  ANR1411W Access mode for volume C10429 now set to
                      "read-only" due to write error.
07/18/1999 00:27:43  ANR0523W Transaction failed for session 29 for node
                      EXCHNGSVR1_AGENT (WinNTDB) - error on output
storage
                      device.
07/18/1999 00:27:44  ANR7808W CLOSE TAPE C10429 returned exception
CPF4405.
07/18/1999 00:27:56  ANR0403I Session 29 ended for node EXCHNGSVR1_AGENT
                      (WinNTDB).