Skip to Content

MaxDB Backup to Networker failing - how to debug?

Hi all,

we have:
- MaxDB 7.9.09 on Windows Server 2016
- Networker Server 18.2, Client 9.1
- Data Domain DDOS 6.0

Backups are failing since several days from different clients.

In dbm.prt I see:2019-01-14 11:07:38      11848 INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 11816 on computer FQDN).
2019-01-14 11:08:24       4288 INF          3 DBMKnl   Received the result of an administrative statement from the database KO1 on computer localhost
                          4288 INF          9 DBMKnl   Statement:  SAVE PAGES QUICK TO  '\\.\pipe\KO1' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'SAP-INC'
                          4288 INF         10 DBMKnl   Returncode: 0
                          4288 INF          7 DBMKnl   Data:       DATE.............. 20190114
                          4288 INF          7 DBMKnl   Data:       TIME.............. 00110430
                          4288 INF          7 DBMKnl   Data:       SERVERDB.......... KO1
                          4288 INF          7 DBMKnl   Data:       SERVERNODE........ 
                          4288 INF          7 DBMKnl   Data:       KERNEL VERSION.... Kernel    7.9.09   Build 007-123-261-455
                          4288 INF          7 DBMKnl   Data:       PAGES TRANSFERRED. 1423384
                          4288 INF          7 DBMKnl   Data:       PAGES LEFT........ 0
                          4288 INF          7 DBMKnl   Data:       NO OF VOLUMES..... 1
                          4288 INF          7 DBMKnl   Data:       MEDIA NAME........ SAP-INC
                          4288 INF          7 DBMKnl   Data:       TAPE NAME......... \\.\pipe\KO1
                          4288 INF          7 DBMKnl   Data:       TAPE ERRORTEXT.... (null)
                          4288 INF          7 DBMKnl   Data:       TAPE LABEL........ PAG_000002348
                          4288 INF          7 DBMKnl   Data:       IS CONSISTENT..... true
                          4288 INF          7 DBMKnl   Data:       FIRST IO SEQUENCE. 182262661
                          4288 INF          7 DBMKnl   Data:       LAST IO SEQUENCE.. (null)
                          4288 INF          7 DBMKnl   Data:       DBSTAMP1 DATE..... 20190114
                          4288 INF          7 DBMKnl   Data:       DBSTAMP1 TIME..... 00110423
                          4288 INF          7 DBMKnl   Data:       DBSTAMP2 DATE..... (null)
                          4288 INF          7 DBMKnl   Data:       DBSTAMP2 TIME..... (null)
                          4288 INF          7 DBMKnl   Data:       BD PAGE COUNT..... 1419497
                          4288 INF          7 DBMKnl   Data:       TAPEDEVICES USED.. 1
                          4288 INF          7 DBMKnl   Data:       DB_IDENT.......... FQDN:KO1_20180423_110008
                          4288 INF          7 DBMKnl   Data:       MAX USED DATA PNO. 0
                          4288 INF          7 DBMKnl   Data:       CONV PAGE COUNT... 130948
2019-01-14 11:08:24       4288 ERR     -24920 DBMSrv   ERR_BACKUPOP: Backup failed
                          4288 INF          0 DBMSrv   The backup tool failed with -1 as sum of exit codes.
2019-01-14 11:08:24       4288 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'backup_start' has ended and failed with return code -24920.

How can I find the root cause for failing backups? Networker's save-command does not create a logfile.

Thanks

Oliver

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

0 Answers