Main.NTBACKUPFailures History
Hide minor edits - Show changes to output
February 07, 2005, at 10:34 PM
by
Changed line 31 from:
Thanks once again to Paul for his valuable input.to:
'''Thanks once again to Paul for his valuable input.'''February 07, 2005, at 10:33 PM
by
Changed line 9 from:
It can often be the case that if your backup process timed out the fault lies with ntbackup stalling or hanging during the backup process. It can often be the case that ntbackup has reported an error on the backup machine which requires some form of user interaction (alert box, change of tape, etc). Without the required interaction, the backup process will eventually time out.to:
It is usually the case that if your backup process timed out the fault lies with ntbackup stalling or hanging during the backup. It can often be the situation that ntbackup has reported an error on the backup machine which requires some form of user interaction (alert box, change of tape, etc). Without the required interaction, the backup process will eventually time out.Changed line 21 from:
@@[=Each time BackupAssist ran it was prompting for the office 2000 CD to update settings.=]@@to:
@@[=The NTBACKUP.EXE process is started by the BAExecutor service but nothing happens. Eventually the backup times out after the 600 minute timeout period.=]@@Added lines 24-25:
Each time BackupAssist ran it was prompting for the office 2000 CD to update settings.
February 07, 2005, at 10:31 PM
by
Changed lines 1-32 from:
Describe NTBACKUPFailures here.to:
!NTBackup process hangs
!!Example:
@@[=Your backup job log will report that the backup process timed out.=]@@
!!Explanation:
It can often be the case that if your backup process timed out the fault lies with ntbackup stalling or hanging during the backup process. It can often be the case that ntbackup has reported an error on the backup machine which requires some form of user interaction (alert box, change of tape, etc). Without the required interaction, the backup process will eventually time out.
!!Causes and Resolution:
BackupAssist will attempt to capture a screen shot if an error occurs and automatically email this to the backup administrator. Unfortunately, however, the screenshot feature in BackupAssist will not work if your Windows screen is locked or if there is a screensaver running - this is a security feature of Windows and nothing to do with BackupAssist. If you leave the desktop logged in and disable your screensaver, then you should see screenshots.
Failing this, you can always login to the backup machine and check for any errors manually.
!!Specific Case Example:
The following scenario involved one of our customers encountering a failure with ntbackup during the backup procedure and we would like to thank Paul Strayhorn for his input concerning this issue.
@@[=Each time BackupAssist ran it was prompting for the office 2000 CD to update settings.=]@@
!!Resolution:
If I logged into the console as administrator (the account BA is configured to run as), I could see the prompts.
As soon as I hit cancel to the CD request, the Backup Executor popped up and tried to run the backup.
So to fix the problem I removed Outlook 2000 (not needed) from the server, rebooted, and everything's working like it should now.
Thanks once again to Paul for his valuable input.