Backup completed with errors

Use this forum for help with AISBackup
Post Reply
lmeyer
Posts: 27
Joined: Fri Feb 27, 2009 9:34 am

Backup completed with errors

Post by lmeyer »

Hello Barry,
I have one more question about my Server 2008 x64 installation.
My solution is now as follows:
  • Backup the system partition weekly with MS Backup solution
    Backup the file server shares with AISBackup.
Since VSS doesn't work on x64, I unchecked in the Backup Job settings 'Backup opened exclusive files'. I expected AISBackup to skip all exclusively opened files in order to get no error. Nevertheless I get this error mail:

AISBackup job: win2008
Backup completed with errors

74 Files could not be backed up
5 Files were deleted prior to backup
357 Files were backed up and tested successfully Scheduled Backup:
74 Files could not be backed up
A full restore using this session may not be safe

Log file attached.


All these 74 files were simply opened during backup, but instead of being skipped according to my settings, they cause an error. It would be nice if I got only an error mail in case of a real error.
Barry
Site Admin
Posts: 1529
Joined: Tue Aug 20, 2002 3:16 pm

Errors with excluded opened exclusive files

Post by Barry »

I will look at relegating these errors to warnings as I think it is still a good idea to log the names of files that were not backed up. AISBackup will not then log as failed if there are only warnings.

I am able to use AISFAM on the Windows 64bit server 2008 here, please send me details about the blue screen error so that I can pass this on to VW solutions.

Barry
Barry
Site Admin
Posts: 1529
Joined: Tue Aug 20, 2002 3:16 pm

Update

Post by Barry »

Please try build 339: This version logs excluded in-use files that cannot be backed up as warnings and does not increase the error count. This version also corrects more errors with network access on 64-bit Windows.

http://www.aiscl.co.uk/dl.php?b=339

Barry
lmeyer
Posts: 27
Joined: Fri Feb 27, 2009 9:34 am

Post by lmeyer »

Thanks alot. I will try this build and give you the news. (Next week)

Here additional info about the blue screen and application hang, as I can find it in Windows Problem Reports and solutions:
1. 2x FAM hangs:
Product: FileAccessManager.exe
Problem: Stopped working
Date: 27.02.2009 16:33
Problem signature
Problem Event Name: APPCRASH
Application Name: FileAccessManager.exe
Application Version: 0.0.0.0
Application Timestamp: 48fa2c2a
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a783
Exception Code: c0000005
Exception Offset: 00036af6
OS Version: 6.0.6001.2.1.0.272.7
Locale ID: 4108
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

2. 12x Bluescreen
Product: Windows
Problem: Shut down unexpectedly
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.272.7
Locale ID: 4108
Files that help describe the problem (some files may no longer be available)
Mini022009-01.dmp
sysdata.xml
Version.txt

The following part differs somehow, but only on one line:
Extra information about the problem
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF800019450AC
OS Version: 6_0_6001
Service Pack: 1_0
Product: 272_3

All variations of the line BCP4:
BCP4: FFFFF80001B30844
BCP4: FFFFF80001B36844
BCP4: FFFFF80001AFB844
BCP4: FFFFFA60057D2FD8
BCP4: FFFFF80001B48844
BCP4: FFFFFA60012B4C6F
BCP4: FFFFF80001AE7844
BCP4: FFFFF800019350AC
BCP4: FFFFF80001AE547F
BCP4: FFFFF80001AF147F

Once, it was completely different:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFFA800B6FFB06
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF


I have no idea if this information can be useful. I never dealt with bluescreens before.
If you expected something else as additional info to the bluescreen, please tell me.
lmeyer
Posts: 27
Joined: Fri Feb 27, 2009 9:34 am

Build 339 corrected all my issues

Post by lmeyer »

Hello, thanks for your good work on build 339.
With backup of opened files disabled:
It not only changed the logging of opened files from error into warnings, but it also handles VSS correctly and gives no more errors in the Windows event logs.
Post Reply