Forum Discussion

k_yong's avatar
k_yong
Level 3
13 years ago

Backup Fail - Corrupt file.

Server Info:
OS: Windows Server 2003 SE SP1
Backup Exec 2010 R2


Error: Saturday backup
Database Consistency Checks is completed without any error.

Click an exception below to locate it in the job log
WARNING: "Server1\Database1" is a corrupt file. This file cannot verify.
WARNING: "Server1\Database2" is a corrupt file. This file cannot verify.

Backup- System?StateThe .DR file that is required for Intelligent Disaster Recovery is not updated.
Backup- \\server1\System?StateThe .DR file that is required for Intelligent Disaster Recovery is not updated.
Backup- \\server2\System?StateThe .DR file that is required for Intelligent Disaster Recovery is not updated.

Verify- Failed
Server1\Database1
Server1\Database2

At Friday all backup was successful and all database is backuped. but it show the DB corrupted as saturday.
All the Database is working fine, but the Backup Exec detect it as corrupted. this normally happen 2-3 time in a week (i backup database everyday)

anyone know what was happen?

 

sorry for my bad english.
 

  • Hi

     

    Please check for your Antivirus setting , if you have got SEP or any other Antivirus please exclude backupexec directory from Online scan and check

     

    Thanks

  • Hi

     

    Please snure you are on updated version of backup exec , Right now you are on R2 build please upgrade to more stable build than R2 which is BE 2010 r3

    http://trialware.norton.com/files/fc/Backup_Exec_2010_13.0.5204_MultiPlatforms_Multilingual_DVD.iso

    You can download ISO for BE 2010 r3 from above link, Once done please install on top of current version & the with live update install sp2 & updates after it & then upgrade your remote agent on remote server too

     

    Also you can check link below for your issue

    http://www.symantec.com/docs/TECH53367

     

    Thanks

  • Thanks for your reply and answer, but the Database Consistency Checks did not show any error.
    it check all my 9 Database, all completed.
     

    Can this problem be solved without any updating? it was working fine before this. it just recvently have this errors.


    By the way,
    Before backup the database, below errors also show in the Database Server, same drive (D:)

    WARNING: "D:\file1.xdb" is a corrupt file. This file cannot verify.
    WARNING: "D:\file2.ddb" is a corrupt file. This file cannot verify.
    Unable to open the item D:\file1.xdb - skipped.
    Unable to open the item D:\file2.ddb - skipped.
    Unable to open the item D:\file3.xdb - skipped.

    Directory Folder\folder1\ was not found, or could not be accessed.
    None of the files or subdirectories contained within will be backed up.
    V-79-57344-33967 - The directory or file was not found, or could not be accessed.

    V-79-57344-65033 - Directory not found. Cannot backup directory Directory Folder\folder1\text and its subdirectories.
    V-79-57344-65033 - Directory not found. Cannot backup directory Directory Folder\folder2\ and its subdirectories.
    V-79-57344-65033 - Directory not found. Cannot backup directory Directory Folder\folder3\ and its subdirectories.
    V-79-57344-65033 - Directory not found. Cannot backup directory \Scheduler and its subdirectories.
    V-79-57344-65033 - Directory not found. Cannot backup directory \SQL2000 and its subdirectories.

  • Hi

     

    Please check for your Antivirus setting , if you have got SEP or any other Antivirus please exclude backupexec directory from Online scan and check

     

    Thanks

  • okay, i will exclude the SEP to scan the backupexec.
    how about the Datebase file, the SPE scanning will caused the Database backup failed?

  • Hi

     

    It should not but then it is good you can exclude them too for isolation & check

     

    Thanks

     

  • ...I think you're getting that message because SEP is blocking the backups of these files. If you don't need to back it up, deselect them!

  • it was a intermittent problem, after i exclude the backup exec from SEP, so far , i didnot get the same error anymore. still continue monitor it. thanks you all