process name (process id) instanceThe backup has stopped with error error code.

The backup has

stopped with an error [error #].

The cause depends on the Error listed at the end of the

Description section of the event. The most frequent causes are as follows:

• Error -521 = 0xfffffdf7 = 4294966775 =

  JET_errInvalidBackupSequence = Backup call out of sequence. This is a

  generic error with several causes and it has been seen when

  anti-virus software is running on the server and scanning the folder where

  affected databases were. The error has been seen when anti-virus software is

  scanning the M: drive. The error has been seen when 3rd Party backup

  software is running on the server and a problem with the software is causing

  the error.

• Error -1032 =  0xfffffbf8 = 4294966264 =

  JET_errFileAccessDenied = Cannot access file – the file is locked or in use.

  This error can occur if the account performing the backup does not have enough

  permissions to perform the backup.

• Error -612 = 0xfffffd9c = JET_errLogReadVerifyFailure =

  Checksum error in log file during backup. This indicates a corrupt

  transaction log file. A backup cannot be made of a corrupt log file and the

  backup will fail. A checksum

  Jet error indicates a hardware root cause and is caused by hardware,

  controller, or file system level problems related to hardware.

• Error -521 –

  the resolution depends on the actual cause. If anti-virus software is

  running on the server, do a comprehensive and exhaustive check on which

  subfolders the software is running against and remove the Exchange databases,

  log files, and check files and remove the M: drive from the scan. If you

  are using 3rd Party backup software, attempt a backup with NT Exchange-aware

  backup. If it succeeds, check with your vendor for any patches,

  updates, or fixes for your software.

• Error -1032 –

  ensure the account performing the backup has enough permissions to perform the backup.

• Error -612 –

  Check the Application log carefully for related events and patterns

  that may relate to this event. Check the System log carefully for related

  events and patterns including any errors related to hardware, drives,

  controllers, or the file system. If there are any such errors, replace the

  hardware, update the hardware system files, or repair the file system to

  prevent any future errors. If the information store database is running,

  it is suggested that you ExMerge your data to .pst files. You then may

  be able to stop the information store. If the database is consistent

  with Eseutil /MH, you can then remove all the log files and check file, start

  the information store, and perform a successful online backup.