Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for SAP Administrator's Guide
  3. Performing backups and restores of SAP
  4. Restarting failed NetBackup for SAP backups and restores
  5. Restarting NetBackup for SAP backups
Veritas NetBackup™ for SAP Administrator's Guide

Restarting NetBackup for SAP backups

The brbackup command initiates the backup for SAP on Oracle databases. The brbackup command calls the NetBackup for SAP agent (backint) with appropriate options and gives a list of files for backup. Backups can be either successful or unsuccessful.

The results are as follows:

  • For a successful backup:

    For each file that is backed up successfully, backint sends the following message to brbackup:

    #SAVED BID filename

    For each SAVED ... message that brbackup receives, brbackup writes the following information to its log file:

    UNIX or Linux:

    #FILE..... /home1/orasap/inp/file1
    #SAVED.... VXF1134574401

    Windows:

    #FILE..... C:\oracle\SUD\sapdata1\file1.dbf
    #SAVED.... VXF1134574401
  • For an unsuccessful backup:

    For each file that is not backed up successfully, backint sends the following message to brbackup:

    #ERROR filename

    For each ERROR ... message that brbackup receives, brbackup writes the following message to its log file:

    UNIX or Linux:

    BR0233E Backup utility has reported an error while saving
    file /home/orasap/inp/filename

    Windows:

    BR0233E Backup utility has reported an error while saving
    file C:\oracle\SUD\sapdata1\file1.dbf

A backup can fail for several reasons that are unrelated to NetBackup operations:

  • The tape library ran out of tapes

  • A network connection problem occurred

  • The user killed the backup but wants to restart it sometime later

For situations like these, NetBackup for SAP saves the partial image for the files that have been already backed up.

Catalog entries in the NetBackup catalog are also saved. It returns the following messages:

  • #SUCCESS BID filename - For the files that were backed up

  • #ERROR filename - For the files that were not backed up

If a backup has terminated because of any problems that are not related to NetBackup, you do not have to repeat a complete backup again. Use the brbackup command and the -f logfile parameter. The brbackup command automatically determines the files that still need to be backed up. The next section describes how to use the -f parameter to restart a backup.

Feedback

Was this page helpful?
Previous

Restarting failed NetBackup for SAP backups and restores

Next

Configuring the checkpoint restart option in a NetBackup for SAP policy

Feedback

Was this page helpful?