Main.NoLogFileFound History
Hide minor edits - Show changes to output
March 30, 2005, at 09:13 PM
by
Added lines 27-38:
!!Additional Causes:
The BackupAssist Event Viewer (View > Event Viewer) may contain the following error message:
@@[=The ntbackup process failed (return code 128). Please examine the attached log file for an explanation.=]@@
This can be caused due to an incorrect configuration setting in regards to your Exchange Server backup - please check that the Storage Group setting in the Exchange tab of BackupAssist is correctly configured.
Normally, the storage group is called "First Storage Group" - visit the online help here to determine your storage group name and ensure that your storage group has been correctly input: http://www.backupassist.com/HTMLHelp/Tips_Exchange.htm
October 21, 2004, at 04:44 AM
by
Changed lines 1-27 from:
Describe NoLogFileFound here.to:
!No log file found
!!Example:
Your backup report contains the following:
@@[=No log file could be found. This indicates that the backup did not run successfully.=]@@
!!Explanation:
The problem where there is no backup log seems to indicate that Windows Backup terminated unexpectedly - for example, it crashed. This is usually due to an intermittent hardware problem for fault, or some form of intensive operations. For example, we know that if there is heavy disk usage (eg. Burning a DVD, or virus scanning), this can interrupt the backup process.
Unfortunately this appears to be a Microsoft Windows problem, but it isn't hard to work around this issue.
!!Causes and Resolution:
This error can be caused by the following:
* Intensive disk activity
* Virus scans
* DVD / CD Burning
* Intensive CPU operations
* Killing the NTBackup.exe process manually
Please check to ensure that any scheduled tasks (eg. virus scanning) are set to run after the backup is compelte.