Interpreting Error Messages

From SEPsesam
Jump to: navigation, search

Other languages:

Copyright © SEP AG 1999-2020. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo. For previous documentation version(s), check documentation archive.

How to interpret SEP sesam's backup module's error messages?

SEP sesam backup modules are designed to produce extended error messages which may return information from 5 layers: SBC – XBSA – FTP – SMS – operating system. SEP sesam scans the protocol files for warnings and errors after backup and restore. In the event of a warning or an error, the first identified message is printed in the summary at the end of the protocol.

Every backup module uses the X/Open Backup Services API (XBSA) standard. SEP sesam XBSA is based on FTP implementation. The backup module connects to SEP sesam's FTPD daemon implementation – Sesam Transfer Protocol Daemon (STPD). STPD is a service that requests and delivers the backup data from or to the SMS Server and manages the data flow between the SEP sesam Server and a client. During a restore STPD receives the data from the SMS Server and sends it to the client, which then restores the data to the target system. Sesam Multiplex Stream (SMS) is a service that receives the backup data from STPD and writes the data to the backup media. During a restore, it reads the data from the backup media and sends it to STPD. Additionally, the SEP sesam backup client (SBC) module executes backup, migration and restore tasks. SBC collects and consolidates backup data on the client system and delivers it to STPD. A list of all SBC messages (C header file) can be found at SBC Messages.

An error message is composed of the messages from the triggering layer up to the upper layers. If an operating system returns an error, the error code and the operating system message are added to the SEP sesam error message. Because of this, error messages can also help troubleshoot problems that are not caused by SEP sesam (for example, OS problems).

Typical backup protocol

The following example shows a typical backup protocol. It is composed of 4 sections: about module, operational parameters, processing, and a summary.

2009-06-26 10:28:16: sbc-3036: Info:    # SESAM BACKUP CLIENT FOR Windows NT FILE SYSTEMS, VERSION: 3.2A17 Build
Revision: 1.257 (x64), Released: Jun 25 2009 #
2009-06-26 10:28:16: sbc-3063: Info:    -------------------- Operation Parameters --------------------
2009-06-26 10:28:16: sbc-3019: Info:    OS info:          Microsoft Windows Server 2008, Build: 6001 Service Pack 1 (x64)
2009-06-26 10:28:16: sbc-3100: Info:    Program PID:      42900
2009-06-26 10:28:16: sbc-3030: Info:    Operation:        BACKUP, Level: COPY
2009-06-26 10:28:16: sbc-3031: Info:    Storage Host:     qsbox3:11001,0-0:SESAM_SECURE_AUTHENTICATION:****
2009-06-26 10:28:16: sbc-3032: Info:    Control Host:     qsbox3:11001:SESAM_SECURE_AUTHENTICATION:*
2009-06-26 10:28:16: sbc-3040: Info:    Device:           SMS:disk1:SHARE:64
2009-06-26 10:28:16: sbc-3064: Info:    --------------------- Operation Messages ---------------------
2009-06-26 10:28:16: sbc-3002: Info:    Building file list from: [C:\SEPsesam\var\ini]
2009-06-26 10:28:16: sbc-3022: Info:    Command line ["sbc" "-b" "-C" "qsbox3:11001" "-S" "qsbox3:11001" "-l" "copy" "-s"
"SF20090626102812" "-d" "SMS:disk1" "-t" "weekly00001:1" "-j" "TEST_BACKUP" "-i" "job=TEST_BACKUP,nod=qsbox3,cmd=sbc,src=C/ /SEPsesam
/var/ini,ptf=WNT,typ=Path,exc=" "C:/SEPsesam/var/ini" ]
2009-06-26 10:28:16: sbc-3003: Info:    Opening saveset: SF20090626102812
2009-06-26 10:28:18: sbc-3104: Info:    Saveset info: [SEGMENT=3]
2009-06-26 10:28:18: sbc-3004: Info:    Begin writing to saveset...
2009-06-26 10:28:18: sbc-3074: Info:    Backup start time [20090626102818]
2009-06-26 10:28:18: sbc-3143: Info:    Starting with drive C:
2009-06-26 10:28:18: sbc-3006: Info:    Saveset size: 98304 bytes. Throughput: 189.820 MB/Hour.
2009-06-26 10:28:18: sbc-3005: Info:    Closing saveset.
2009-06-26 10:28:18: sbc-3052: Info:    Items processed correctly: [25]. Not processed or incorrectly processed items: [0].
2009-06-26 10:28:18: sbc-3007: Info:    Operation successful.
2009-06-26 10:28:19: sbc-3001: Info:    Exiting.

Backup error summary

The error message summary is prefixed by a short information string. The full error message is composed as follows:

{status}/{amount}/{saveset ID}/{SBCstart}/{message}

The components of this string have the following meanings:

{status} {amount} {saveset ID} {SBCstart} {message}

0 - successful
1 - warning
2 - empty LIS
3 - broken during backup
C - broken before data transfer
X - failed

Amount of data stored on media Automatically generated saveset ID Starting time on the client Message about the error

The following example shows a backup error summary with all 5 layers prefixed by a short information string.

X/0/SF20060629233007/20060629232907/Error: XBSA Call BSAEndData (closing saveset) failed:
System detected error, operation aborted. TRANSIENT or PERMANENT NEGATIVE reply:
553 STOR Failed. 1037: Writing data block on tape failed (23): Data error (cyclic redundancy check).
1039: Writing of Saveset Trailer failed.

The amount of details provided for backup or restore is defined by the log level.

See also

Error Messages Guide