Forum Discussion

shahriar_sadm's avatar
8 years ago

Sybase backup success with no child

Hi dear all, 

I create a sybase backup script on windows client when I run backup mannual backup successful with no child and no kilobyte written. 

this is client bphdb log

SYBACKUP_SERVER = master
SYBACKUP_POLICY = policy 
SYBACKUP_SCHED = sybase-policy
SYBACKUP_CLIENT = client
SYBACKUP_SCHEDULED = 1
SYBACKUP_USER_INITIATED = 0
D:\sybase\BIS\OCS-15_0\bin\isql -Uxxxxxxxx -Pxxxxxxxx -ID:\sybase\BIS\ini\sql.ini -SBIS -i "D:\syb_BIS_dump"
Backup Server: 4.172.1.4: The value of 'allocated pages threshold' has been set
to 40%.
Backup Server session id is: 8. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume change
request from the Backup Server.
Msg 103, Level 15, State 9:
Server 'BIS', Line 1:
The device that starts with 'sybackup::-SERV master -CLIENT client -POL
policy  -SCHED Default-Application-Backup -STAT_FILE D:\status.log'
is too long. Maximum length is 127.
Contents of "D:\syb_BIS_dump"
dump DATABASE BIS to "sybackup::-SERV master -CLIENT client -POL policy -SCHED Default-Application-Backup -STAT_FILE D:\status.log"
go
go
go
go
Execution of isql command completed successfully - exiting

 

P.S: I have similar issue in MSSQL backup, initiate from client backup resolve that, how can I initiate sybase backup from client.

 

Thanks

3 Replies

  • There seems to be something wrong with your configuration as per this error message:

    The device that starts with 'sybackup::-SERV master -CLIENT client -POL
    policy  -SCHED Default-Application-Backup -STAT_FILE D:\status.log'
    is too long. Maximum length is 127.

    Please tell us how you and the Sybase dba went about configuring the client, the script and the NBU policy.

    Have you gone through the NetBackup for Sybase Administrator's Guide ? 
    Especially the section that deals with Client Service logon? 

     

    • shahriar_sadm's avatar
      shahriar_sadm
      Level 6

      Yes I gone through administration guide for sybase windows.

      just i changed dump file path 

      I have some failed like below on media server bpbrm. 

       

      db_getCLIENT: db_CLIENTreceive: no entity was found 227

      vnet_check_user_certificate: [vnet_vxss_helper.c:3643] vnet_get_user_credential_path failed 35 0x23

      verify_client: ../bpbrm.c.42461: db_getCLIENT failed for CLIENT: SAPBISBX

      verify_client: ../bpbrm.c.42649: db_getCLIENT failed: 227 227 0x000000e3

      • Marianne's avatar
        Marianne
        Level 6

        You changed the dump path? Really?

        The way I read the NBU for Sybase manual is that the NetBackup plugin becomes the dump-device.

        Extract from page 13: 

        The dump-device string of the Sybase DUMP and LOAD commands is extended to
        support the archive API. The following syntax instructs Sybase backup server to
        use the NetBackup archive device to transfer data to and from NetBackup:
        "sybackup::"
        The Sybase DUMP command is as follows:
        dump database model to "sybackup::"

        The way I interpret the change of dump file path is that you are bypassing the NBU plugin.

         

        PS:
        Snippets of logs do not help. 
        All info associated with particular job is needed to interpret messages in the right context.

        Logs in .txt format can be uploaded using the 'Choose File' link.