Skip to main content

How to prevent Backup Exec from failing a backup operation when encountering corrupt files (excluding Microsoft Exchange files)

One day one of my colleague from International region called me for Back Exec problem. He was not able to complete backup operation for his FNP server due to error.

WARNING: "" is a corrupt file.
This file cannot verify.

When Backup Exec (tm) encounters a corrupt file, the job will fail. Following is observed in the failed backup job log:

 While investigation came to know that backup is failing because of one of the .Pst file which is online. I mean in use & someone kept that file on FNP for being backup & can be accessible from any location.

We can’t remove the file because that is what our business requirement was but at the same time  we want to complete the backup jobs.

 To Avoid such cases & to run backup jobs successfully in the Backup Exec follow some tips which are mentioned below.

 Create a Reg_Dword key called Fail Jobs on Corrupt Files in following location as per you backup exec version.

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup [For versions 9x and 10x]

HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec for Windows\Backup Exec\Engine\Backup [For versions  11x and above]

 

http://www.symantec.com/business/support/index?page=content&id=TECH5633

Happy Blogging,

 
Labels:

Comments

Post a Comment

Popular posts from this blog

"kerberos: the specified credentials were rejected by the server", "unreachable": true" Ansible

Hello Friends, I was getting following Error while deploying my Ansible script, Basically my credential were getting rejected by server. SSH password: PLAY [Playbook_Name] ***************************************************************02:00:30 TASK [Gathering Facts] *********************************************************02:00:30 fatal: [Server_Inventory_Name]: UNREACHABLE! => {"changed": false, "msg": "kerberos: the specified credentials were rejected by the server", "unreachable": true} PLAY RECAP *********************************************************************02:00:30 Server_Inventory_Name    : ok=0    changed=0    unreachable=1   failed=0  It was resolved using one additional parameter in Inventory  i.e  "ansible_winrm_server_cert_vaildation:ignore"
1 comment
Read more

NBSUTIL commands

Frustrated with syntax finding hence decided to post all NBSTLUTIL related commands so people will not face same problem. Common SLP Related Commands Show EMM Image list of Images that were backed up to an SLP STU [ -I / -U ] nbstlutil list nbstlutil list –lifecycle <name> nbstlutil list –backupid <id_value> nbstlutil list -image_state <value> nbstlutil list -copy_state <value> nbstlutil list -frag_state <value> nbstlutil list –mediaid <media_id>_–state 3 Activate /Inactivate SLP operations nbstlutil inactive –lifecycle <lifecycle name> nbstlutil inactive –backupid <backupid> nbstlutil active –lifecycle <lifecycle name> nbstlutil active –backupid <backupid> Cancel pending operations on selected image nbstlutil cancel -backupid <backupid> nbstlutil cancel -lifecycle <lifecycle> Show status on Incomplete copies of Lifecycle Managed images nbstlutil stlilist –lifecycle <lifecycle name> nbstlutil stlil...
Post a Comment
Read more

OSD or Onscreen menu is locked.

OSD or Onscreen menu is locked. I am having HP 20 Inch monitors on my Desk and was not able to change brightness and Sleep Timer etc for my monitor and was not able to get into the menu due to On Screen menu locked error. I know it's irritating issue. fix what i found for this is "Just hold menu button for 30 Sec and it will be solved. :)
Post a Comment
Read more