Forum Discussion

shahriar_sadm's avatar
9 years ago

Sybase Backup failed with status 3

Hi dear all, please help me to solve this case



07/10/2016 10:31:28 - estimated 0 kbytes needed
07/10/2016 10:31:28 - Info nbjm (pid=2946) started backup (backupid=SAPBISBX_1468130487) job for client SAPBISBX, policy test-for-sybase-db, schedule sybase-policy on storage unit media-nbkp-srv3-hcart3-Qi6K-tld-2
07/10/2016 10:31:28 - started process bpbrm (pid=338)
07/10/2016 10:31:29 - connecting
07/10/2016 10:31:29 - connected; connect time: 0:00:00
07/10/2016 10:31:31 - end writing
07/10/2016 10:31:36 - Info bpbrm (pid=338) SAPBISBX is the host to backup data from
07/10/2016 10:31:36 - Info bpbrm (pid=338) reading file list for client
07/10/2016 10:31:37 - Info bpbrm (pid=338) starting bphdb on client
07/10/2016 10:31:38 - Info bphdb (pid=7764) Backup started
07/10/2016 10:31:39 - Error bpbrm (pid=338) from client SAPBISBX: ERR - Script <"C:\sybase-test-sc.cmd"> failed with status: <3>
07/10/2016 10:31:39 - Error bpbrm (pid=338) from client SAPBISBX: ERR - bphdb exit status = 6: the backup failed to back up the requested files
07/10/2016 10:31:39 - Info bphdb (pid=7764) done. status: 6: the backup failed to back up the requested files
the backup failed to back up the requested files  (6)

5 Replies

  • Hi, I fix this issue but now I have new problem backups failed and I have below


    CT-LIBRARY error:
        ct_connect(): protocol specific layer: internal Client Library error: There is a tds login error. The installed encryption handler returned a status that was not CS_SUCCEED.


  • You have not given us any background on how exactly configuration on NBU master and on the client was done.

    It is impossible to troubleshoot by just looking at the error messages.

    Please go through the NetBackup for Sybase Administrator's Guide and then list exact steps that were followed on the server and Sybase client.

    Also have a look at the Troubleshooting section in above manual to see which log folders to create on master, media server and Sybase client.

  • During a routine review of a customer's environment I discovered that their most recent catalog backup failed with status code 2 (none of the requested files were backed up). A quick check revealed the horrifying condition that the catalog backups had been failing for a week and the last catalog backup had just expired.

    I checked the most recent bpdbm logs (in /usr/openv/netbackup/logs/bpdbm) and noticed the following curious entries:
    <16> backup_dbspaces: ODBC connection failed.
    <16> backup_dbspaces: ErrMsg [Sybase][ODBC Driver][SQL Anywhere]Database server not found, ErrCode -1, Sqlstate 08001

    Google searches revealed that the /usr/openv/db/data/vxdbms.conf file had been a culprit for some people. Apparently this file contains parameters for backing up the NetBackup catalog database. In my case, I immediately noticed the file pointed to a server other than the master server.

    It seemed reasonable that I had found the root cause of the failed catalog backups, though I had no idea how or why the file might have changed. Also, never having the occasion to edit the vxdbms.conf file I wanted to be sure I was doing the right thing, so I opened a support case.


    LTO 5 Tapes

  • This discussion has nothing to do with NBU Catalog backup...