Skip to Content

Second backup server does partially write to logfile.

Hi there,

[Environment]

  • Adaptive Server Enterprise/15.7/EBF 24641 SMP SP134 /P/X64/Windows Server/ase157sp133x/3925/64-bit/OPT/Sat May 02 00:22:51 2015
  • Backup Server/15.7 SP134/EBF 24641/P/X64/Windows Server/ase157sp133x/4782/64-bit/OPT/Fri May 01 22:04:03 2015

I have configured a second backup server.

rem
rem Backup Server Information:
rem  name:                          ST_PROD_BS_1
rem  errorlog:                      D:\app\sybase\Software\ASE-15_0\install\ST_PROD_BS_1.log
rem  interfaces:                    D:\app\sybase\Software\ini\sql.ini
rem  location of multibuf:          D:\app\sybase\Software\ASE-15_0\bin\sybmbuf.exe
rem  language:                      us_english
rem  character set:                 cp850
rem
rem
"D:\app\sybase\Software\ASE-15_0\bin\bcksrvr.exe" -SST_PROD_BS_1 -e"D:\app\sybase\Software\ASE-15_0\install\ST_PROD_BS_1.log" -I"D:\app\sybase\Software\ini\sql.ini" -M"D:\app\sybase\Software\ASE-15_0\bin\sybmbuf.exe" -Lus_english -Jcp850 -V0 

added this to the sql.ini

[ST_PROD_BS_1]
master=NLWNSCK,CSSYB99,5045 
query=NLWNSCK,CSSYB99,5045

added the server to sysservers (XXXXX out real names for security reasons)

1> sp_addserver ST_PROD_BS_1
2> go
Adding server 'ST_PROD_BS_1', physical name 'ST_PROD_BS_1'
Server added.
(return status = 0)
1> select * from sysservers
2> go
 srvid  srvstatus srvname                        srvnetname
                                         srvclass srvsecmech                     srvcost srvstatus2 srvprincipal
 ------ --------- ------------------------------ -----------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------- -------- ------------------------------ ------- ---------- --------------------------------
------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------
      1         8 SYB_BACKUP                     XXXXXX
                                                7 NULL                              NULL          2 NULL
      2      1024 SYB_EJB                        EJBServer
                                               10 NULL                              NULL          2 NULL
      0         9 XXXXX                        XXXXXX
                                                0 NULL                                 0          2 NULL
      3         9 XXXXX_XP                     XXXXX_XP
                                               11 NULL                              1000          2 NULL
      4         9 ST_PROD_BS_1                   ST_PROD_BS_1
                                                7 NULL                              1000          2 NULL

When dumping to disk using the 'at ST_PROD_BS_1' option the only thing added to the backup log is:

Nov 09 16:02:43 2016: Backup Server/15.7 SP134/EBF 24641/P/X64/Windows Server/ase157sp133x/4782/64-bit/OPT/Fri May 01 22:04:03 2015
Nov 09 16:02:43 2016: Confidential property of Sybase, Inc.
Copyright 1987, 2015
Sybase, Inc. All rights reserved.
Unpublished rights reserved under U.S. copyright laws.
This software contains confidential and trade secret information of Sybase,
Inc. Use, duplication or disclosure of the software and documentation by
the U.S. Government is subject to restrictions set forth in a license
agreement between the Government and Sybase, Inc. or other written
agreement specifying the Government's rights to use the software and any
applicable FAR provisions, for example, FAR 52.227-19.
Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
Logging Backup Server messages in file 'D:\app\sybase\Software\ASE-15_0\install\ST_PROD_BS_1.log'
Nov 09 16:02:43 2016: Backup Server: 1.78.1.1: The interfaces file used by the backup server is 'D:\app\sybase\Software\ini\sql.ini'.
Nov 09 16:02:43 2016: Backup Server: 1.88.1.1: The hosts authentication file used by the backup server is 'D:\app\sybase\Software/hosts.allow'.
Nov 09 16:02:43 2016: Backup Server: 1.79.1.1: The backup server name is 'ST_PROD_BS_1'.
Nov 09 16:02:43 2016: Backup Server: 1.70.1.1: Configuring the maximum shared memory usage to 48 MB.
Nov 09 16:02:43 2016: Backup Server: 1.69.1.2: Configuring the number of service threads to 48.
Nov 09 16:02:43 2016: Backup Server: 1.70.1.3: Configuring the maximum shared memory per stripe to 1048576 bytes.
Nov 09 16:08:10 2016: Backup Server: 2.23.1.1: Connection from Server ST_PROD_BS_1 on Host with HostProcid 7052.
Nov 09 16:08:10 2016: Backup Server: 4.41.1.1: Creating new disk file E:\backup\tmp\CNSPLINTER_RAPP_1.dmp.
Nov 09 16:08:11 2016: Backup Server: 6.28.1.1: Dumpfile name 'RAPP163140E2EA ' section number 1 mounted on disk file 'E:\backup\tmp\CNSPLINTER_RAPP_1.dmp'

And it stops after that. When issuing a new dump it adds the first few lines and stops logging again.

Does someone know how to enable full logging? (-V0) does not work.

Regards,

Harry

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Nov 09, 2016 at 06:30 PM

    Some background:

    * ALL dump/load commands are processed by the SYB_BACKUP server (or rather the backupserver that is aliased to SYB_BACKUP).

    * It doesn't matter how many backupservers you may add (via sp_addserver), ASE will always use SYB_BACKUP to process a dump/load command. [Net result is that adding backupservers to ASE - via sp_addserver - has no effect on dump/load commands.]

    * When you perform a remote dump/load (ie, you include the 'at <remote_BS_name>' clause), SYB_BACKUP will open communications with <remote_BS_name> ... assuming SYB_BACKUP can find <remote_BS_name> in its interfaces file. [Net result is that <remote_BS_name> does not have to be added to the ASE's sysservers table, ie, no need to run sp_addserver <remote_BS_name>.]

    I went into a bit more detail on this topic a few years ago if you've got nothing better to do : Mark's ramblings on backupservers, sybmultbuf processes and compressed dumps

    ------------

    Back to your issue ...

    You're attempting to perform a remote dump.

    In this scenario your backupserver (aliased as SYB_BACKUP) will handle the initial dump command.

    SYB_BACKUP will then initiate communications with your remote backupserver (ST_PROD_BS_1).

    Each backupserver (SYB_BACKUP, ST_PROD_BS_1) will write various messages to its own errorlog. [Net result is that you'll need to look at both backupserver errorlog files to see the whole operation.]

    NOTE: You should be able to sp_dropserver ST_PROD_BS_1 and still be able to perform a remote dump (or load) as long as ST_PROD_BS_1 is defined in the interfaces file used by your SYB_BACKUP backupserver.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 10, 2016 at 01:08 PM

    Hi Mark,

    thanks for your answer. I have a good understanding of the communication concept now through SYB_BACKUP.

    for communication with the ST_PROD_BS_1 via isql i will need the server added to sysservers. But i read that it is, as you stated, not necessary.

    Regards,

    Harry

    Add comment
    10|10000 characters needed characters exceeded