Exchange reserr and valerr

Use this forum for help with AISBackup
Post Reply
InterfaithIT
Posts: 2
Joined: Tue Dec 23, 2008 6:27 pm

Exchange reserr and valerr

Post by InterfaithIT »

Currently we are in the trial period for this software and really like what we see, but we have been having some problems baking up our exchange server. Our exchange server is on a Windows Server 2003 OS with VSS enabled. We have unchecked the NTFS securities box and have it using VSS. The following is a copy of the log that states that these files failed the restore validation test. When searching we could not find any documentation regarding RESERR or VALERR and what could cause this to happen when backing up exchange. Can anyone give some information on where to start figuring out this problem or a possible solution?

LOGSTART
9:21:56 AM SSTART Backup Session: 1 Started on Tuesday, December 23, 2008 at 9:21:56 AM Version: 2.6.2 (327)
9:21:56 AM INF Platform: Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
9:22:00 AM STAT Files Selected For Backup: 170 (11,032.72 MB)
9:22:00 AM STAT Already Backed up: 0
9:22:00 AM STAT Excluded From Backup: No files or folders have been excluded.
9:22:00 AM DEST Backup destination: \\192.168.1.30\f$\Backups\exchange\exchange.zip
9:22:00 AM INF 13 New Folders.
9:22:00 AM INF Test Method: File Integrity Method.
9:22:00 AM INF Backing up: 170 Files of 11,032.00 Megabytes
9:22:00 AM INF Excluding: 0 Files (See Modify Files and Folders/Exclusions)
9:22:00 AM INF Already on Backup: 0 Files
9:22:00 AM INF Compression Level: High
9:22:00 AM STAT Estimated Size of Backup: 6.11 GB
9:23:55 AM INF Backing up 7 Exclusively Opened Files
9:24:06 AM INF Initialised Volume Shadow Copy Service for Drive: D:\
9:52:35 AM INF Testing Backup
9:53:09 AM VALERR Test Failed: D:\Exchange\MDBDATA\E0003D3D.log from [exchange_6.zip]
9:54:21 AM VALERR Test Failed: D:\Exchange\MDBDATA\pub1.edb from [exchange_13.zip]
9:54:21 AM ZIP Backup zip file exchange_13.zip empty: Deleted
10:04:18 AM VALERR Segment: 4 of D:\Exchange\MDBDATA\priv1.edb: Failed restore test
10:04:18 AM RESERR 2 Files could not be restored when tested
10:04:18 AM RESERR 1 Large file segment could not be restored when tested
10:04:18 AM RESINF 168 Files were backed up and tested successfully
10:04:18 AM RESULT 2 Files could not be restored when tested
1 Large file segment could not be restored when tested
A full restore using this session may not be safe
10:04:19 AM INF Backing up Backup Contents File Database Files
10:04:19 AM STAT Time Calculating Backup: 3 Seconds
10:04:19 AM STAT Time Backing up: 30 Minutes 35 Seconds
10:04:19 AM STAT Time Testing Backup: 11 Minutes 42 Seconds
10:04:19 AM STAT Total Time: 42 Minutes 20 Seconds
10:04:19 AM STAT Backed up at 360.71 MB per minute
10:04:19 AM STAT Compression Ratio: 42%
10:04:19 AM STAT Not Compressible 6710.63 MB 61% (Not included in compression ratio)
10:04:19 AM STAT Tested backup at 942.09 MB per minute
10:04:20 AM SESSEND Backup Session Ended: Tuesday, December 23, 2008 10:04:20 AM
LOGEND
Barry
Site Admin
Posts: 1529
Joined: Tue Aug 20, 2002 3:16 pm

Network backups

Post by Barry »

VALERR means that the validation of the file, or in the case of very large files (files over 4GB are spilt).

The RESERR message is the count of errors found.

The is occasionally problems backing up to some NAS devices or even MS servers over some networks where the data is corrupted somehow – this should not happen and if the test phase of AISBackup was not run you would not know there was a problem until you come to restore – not too good I’m sure you’ll agree.

NAS devices we have tested and some servers (possibly with faulty Network Interface cards) often work if the backup files are created locally and then transferred to the server using Microsoft’s Copy File API, to set this option in AISBackup:

Manage Backup / Change Backup Job Settings / check Create backup file then copy to media.

There is quite a lot of random access writes when creating zip format files because the compressed file size is stored before the actual compressed data, and the size of the compressed data is not known until after it has been written to the file. Using the Create backup file then copy to media does all the zip file creation on the local PC / Server instead of the remote NAS / Server over the network. Obviously there is some overhead to this, however the network traffic is reduced - which may be a good thing.

Perhaps you could also try an external drive directly cconnected to the server?

Barry
Post Reply