For a couple years we've backed up our Exchange 2003 Enterprise database to the local hard drive. It would then get picked up by a network attached tape unit.Recently we installed a Data Domain backup unit. We use the NTbackup app included with Windows server 2003 to backup the Exchange database (122 GB) to the network share on the data domain box. The backup succeeds but the verify fails, erroring out at approx 100 GB according to the backup report. We have tried targeting to a different network share and get the same error, again at approx 100GB.The problem is not network bandwidth as we have other servers backing up large volumes of data with no problem. For instance, our 'filecab' server backs up approx 85GB across the network and has no trouble with the verify phase.I suspect the problem is the Exchange database size, 122 GB. But before I take on the not inconsiderable task of breaking the database into two, I would like to know if others have seen problems with backing up large Exchange databases to a network share.

For a couple years we've backed up our Exchange 2003 Enterprise database to the local hard drive. It would then get picked up by a network attached tape unit.Recently we installed a Data Domain backup unit. We use the NTbackup app included with Windows server 2003 to backup the Exchange database (122 GB) to the network share on the data domain box. The backup succeeds but the verify fails, erroring out at approx 100 GB according to the backup report. We have tried targeting to a different network share and get the same error, again at approx 100GB.The problem is not network bandwidth as we have other servers backing up large volumes of data with no problem. For instance, our 'filecab' server backs up approx 85GB across the network and has no trouble with the verify phase.I suspect the problem is the Exchange database size, 122 GB. But before I take on the not inconsiderable task of breaking the database into two, I would like to know if others have seen problems with backing up large Exchange databases to a network share. Hi there,have you tried, see the hd quotas?Marco Enxuto, Lisbon, Amadora, Portugal

What error you are getting while NTBackup verifies the backup? A general recommendation is to keep database size to 50GB in Exchange 2003 for faster & split backup and recovery purpose....Amit Tank | MVP - Exchange Server | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

From the backup job log file:Error: An inconsistency was encountered in the requested backup file.Verify completed on 5/13/2009 at 12:07 AM.Directories: 2Files: 0Different: 0Bytes: 102,810,744,552Time: 1 hour, 4 minutes, and 26 secondsFrom the Windows Application log: NTBackup error: 'An inconsistency was encountered in the requested backup file.'

Check Elvis's response in below thread.... :)http://social.technet.microsoft.com/Forums/en-US/exchangesvravailabilityandisasterrecovery/thread/934b500b-c33b-47c7-baa9-c3a2002fca75Amit Tank | MVP - Exchange Server | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com