Beefalo V2 4.4.3.86

SEP sesam Beefalo 4.4.3.86 overview

• <version> released: <date>

Tip

SEP generally recommends upgrading the SEP sesam Server and Client components to the latest version during the regular upgrade process. For the complete list of releases, see SEP sesam release versions. Installing either Windows or Linux-specific distributions is pretty straightforward. For Linux systems, SEP provides special service pack executables that ease the installation; see Applying Service Packs on Linux. Download the latest release version.

New supported systems

No changes from Beefalo V2, see New supported systems from Beefalo V2.

Discontinued systems

No changes from Beefalo V2, see Unsupported OS.

Known issues

Beefalo 4.4.3.86 known issues:

Severity: CRITICAL Possible data loss due to non-executed updates of the entries in the SEP sesam database at extremely high system load. There may be problems updating entries in the SEP sesam database if the system load is so high that the maximum number of connections is reached (PostgreSQL) or the busy timeout (SQLite) is no longer sufficient. This can result in the backup status being incorrectly set as successful and external applications (e.g. SAP Hana) seeing backups as successful even though they did not complete successfully. In such a case, data loss may occur during a restore. Workaround: SEP is working on this issue and will provide a fix as soon as possible. Severity: MINOR SEP sesam v. 4.4.3.84 SP2 – Automatic SP update of Windows clients on the Linux Server fails When trying to update the Windows clients of the SEP sesam Linux Server, automatic SP update fails or is stuck in a loop due to the missing sm_execute_update.cmd file. Workaround: Download the sm_execute_update.cmd file manually from the Linux service pack directory and copy it to the skel directory of the SEP sesam Linux Server, for example, sesam:/opt/sesam/skel # ls -l sm_execute_update.cmd. Then start the SP2 update of the SEP sesam Linux Server via GUI.

Enhancements and changes Beefalo 4.4.3.86

Consistent export of the SEP sesam Server database

SEP sesam used to export its database table by table without taking care of foreign keys. As foreign keys enforce the database referential integrity and ensure that the relationship between database tables is preserved during the insertion of data, the export is now improved by using pg_dump, resulting in a consistent export and a faster import of the database.

Optimized license check

License check performance has been improved; the license is now checked during startup, reducing noise and clutter in the log with detailed logging of license checks.

SHA-256 for enhanced security

EP sesam now uses SHA -256 to sign all executables in the Windows kit when upgrading or (re)installing SEP sesam.

Fixed issues Beefalo 4.4.3.86

Kernel

Scheduled jobs and external backups fail due to yet uninitialised queue

Problem

• When a new drive is introduced or a new datastore and media pool are created and a backup or other scheduled job is started immediately afterwards, the job fails with an error about the non-existing queue. The same problem can occur if SEP sesam Server starts after the update and backups are started immediately after the server is started, as sm_config_drives has not yet created drive queues.

No error is recorded when the database is locked

Problem

• If an external backup is started and an error occurs when trying to access the database because the database is locked, no error is recorded for the failed backup.

sm_sms_watch crashes when starting the SEP sesam services or a NEWDAY event

Problem

• sm_sms_watch crashes on SEP sesam startup or on startup of a NEWDAY event due to the SM_QM status output that leads to overrun in the stack during drive configuration.

Sesam DB

If the connection limit to the PostgreSQL database is reached, SEP sesam Server stops

Problem

• By default, the Sesam DB instance runs with the default max_connections = 100. When this connection limit is reached, for example to the PostgreSQL database, SEP sesam terminates, but the error log does not contain information about database access errors and reaching the maximum connection limit.

SEP sesam external backup modules (Oracle, Hana...) encounter errors during 'closejob' operation, but backup is reported as successful

Problem

• SEP sesam external backup modules (Oracle, Hana...) report backups as successful after the data transfer is complete. Any problems during the 'closejob' operation are ignored. For example, if the SGM file copy fails, the saveset will not be found during restore. Checksum errors may also be detected, but the backup will still be shown as successful.

Update

Linux update fails due to faulty copy DB file command

Problem

• On some operating systems (e.g., SLES12) the behavior of overlapping string operations is undefined; because the update script uses the same string as source and target in the string operation, the update fails.

Automatic SP update of Windows clients on Linux Server fails

Problem

• attempting to update Windows clients of the SEP sesam Linux Server, the automatic SP update fails or gets stuck in a loop due to the missing sm_execute_update.cmd file.

Windows client update from GUI fails if BSR is already installed on the system

Problem

• If BSR is already installed on the system to be updated automatically from GUI, the update fails due to a syntax error in the cmd file.

Installation of SEP sesam BSR Pro fails due to wrong installation path

Problem

• The installation of SEP sesam BSR Pro fails because of the wrong installation path with wrong double slash in BSR Pro path.

STPD

When a backup is aborted, STPD does not write the metadata (LIS and SGM file)

Problem

• (Applies only to Windows) STPD (Sesam Transfer Protocol Server) does not write the metadata (LIS and SGM file), causing a saveset to become invisible and unable to be deleted even though it occupies the space.

Backup session receives incorrect COM responses (not matching the openjob command)

Problem

• The backup session receives incorrect COM responses during the backup, for example, during Oracle backups using multiple channels or with SAP HANA backups; in the latter case, the backint backup module receives responses that do not match the openjob command and proceeds without backup error. Consequently, backups are performed to the arbitrary media pool with a much shorter retention time than configured, which can lead to data loss (the backup is not available for restore due to the shorter EOL).

STPD log shows cpio errors, but backup is successful

Problem

• STPD log shows cpio errors, for example, ERROR: cpioana_func: read_in_header (2): Synchronization lost, but SBC log shows no error and backup is marked as successful, which may result in a failed restore.

Possible data loss if STPD timeout occurs during backup but backup is successful

Problem

• If the STPD timeout occurred during the backup at the same time as the closing saveset operation, SBC ended with success, which may result in a failed restore.

Restore from HPE StoreOnce fails due to invalid credentials

Problem

• Restore from HP StoreOnce fails with error: RETR Failed. Command error with HPE StoreOnce server [COFC-CZ3935RB01]: OSCLT_ERR_INVALID_CREDENTIALS. because password decryption failed.

Restore from RDX drive fails

Problem

• Restore from RDX disk drive stalls, STPD generates log files in an endless loop, or restore fails with MTF error because ESET metadata is printed with incorrect offset; consequently, restore fails.

SMS

Oracle RMAN multichannel backup fails with failed to create sequential file

Problem

• Oracle RMAN multichannel backup fails with error ORA-19506: failed to create sequential file. This issue is related to the SEP sesam SBT Windows dll that was not thread-safe, causing the RMAN multichannel backup to fail.

Backups and migrations to tape drive hang or fail after media change

Problem

• Write operations to tape that were active during a media change hang with zero throughput, do not start at all, or are aborted after some time.

Backup on VTL that exceeds tape size is shown as successful

Problem

• When backing up to the Quastor VTL library, the backup fails to continue writing to the underlying block device due to lack of storage space; even though the error is tracked in the SMS log, the STPD log shows the data transfer as complete and SEP sesam issues the message Backup completed successfully.

Restore of data split on several tapes fails

Problem

• Restoring data saved on multiple tapes fails with an error: The archive could not be resynchronized. The same incorrect tape block size is automatically used for the second tape, resulting in a failed restore.
• The restore fails due to the data block not being written to the subsequent tape after EOM, resulting in a lost data block.

On sayFUSE, EOM is not recognized and backups fail

Problem

• The EOM (End of Media) parameter is not recognized on sayFUSE, causing backups to fail with "No further tape available" or "Tape not ready" to appear for each session.

Next EOM after EOM IO error sets IO error flag

Problem

• SMS remembers EOM IO error status on subsequent normal EOM handling and incorrectly sets IO error flag on subsequent EOM.

Backup to tape with IO error is successful but restore fails

Problem

• Backup to tape with IO error is successful, but restore fails with Error: Cannot read from remote archive.

Media

Wrong start time is displayed for readability check

Problem

• The media readability check start time is set in the past.

Writing to tape could fail with Error sharing violation

Problem

• If there is no tape trailer on the tape, the first write job to the tape works but it does not set hw_drives.label to DB; consequently, the second job tries to talk to the tape drive while all other jobs fail with Error sharing violation.

OpenNebula

Restored OpenNebula VM does not boot

Problem

• The restored OpenNebula virtual machine does not boot because the recovered image was created with the wrong format setting.

OpenNebula VM restore fails with AttributeError or ONE instance has no attribute 'o'

Problem

• The restore of OpenNebula VM fails with the error message AttributeError: NoneType object has no attribute group or ONE instance has no attribute 'o' due to missing attribute in VM xml.

OpenNebula VM architecture is not restored

Problem

• For OpenNebula virtual machines, the architecture (i386, x86_64) can be specified when the VM is created. During restore, this option is not restored according to the specified VM xml configuration.

Citrix XenServer

When Citrix XenServer CBT backup is started, SEP sesam automatically enables NBD

Problem

• When a Citrix XenServer CBT backup is started, SEP sesam activates NBD on all network interfaces. This becomes a problem if there are interfaces that are inaccessible to the sesam datamover, or when it overrides user settings on some interfaces.

DB modules

Saveset query for external backups (Oracle, SAP...) returns failed backups

Problem

• When searching for savesets related to external backups, savesets with failed status are returned.

Restore

Restore fails with error At current offset 144 (0x90) no valid MTF Stream ID was found

Problem

• Restore fails with error At current offset 144 (0x90) no valid MTF Stream ID was found due to incorrectly set SPAR header length for a zero-ranged file.

Restore from migrated saveset uses wrong transport mode

Problem

• When restoring a migrated saveset, the restore wizard displays the settings of the original saveset with the selected transport mode, then uses the correct RDS without adjusting the protocol of the specified interface (transport mode), for example, FTP mode is used instead of HTTP, resulting in a failed restore.

Restore exclude filter does not work correctly

Problem

• The restore exclude filter does not work correctly. For example, for a selective restore, the exclude filter is set to "-*.ini" (- prefix), but the filename is not extracted correctly (e.g., /debug.ini instead of debug.ini) so the matching file cannot be found and excluded.

Migration

Core dump occurs after starting the migration

Problem

• Migration is terminated (core dump of sm_sms_copy) with exception 0xc0000417 after a NEWDAY event occurred.

Migration from tape fails in case of EOM due to insufficient recorded information on next tape

Problem

• Migration of savesets that exist on two tapes (media_change) back to datastore fails. SMS fetches the next media label over the restore_result table, refers only to the restore and not to a migration task.

Migration is succesful with dabase error

Problem

• Migration results in database error DB_SEL_GETVALUE: Error during DBaccess - return 0. Incorrect szSql variable was used to execute DB select.

NDMP

NDMP restore from tape fails with error RESTORE: Mangled directory

Problem

• NDMP restore from tape failed with NDMP: 1 info: LOG_MESSAGE: 'RESTORE: Mangled directory' due to incorrect buffer handling with the new asynchronous read approach.

NDMP restore via FTP fails with Found a checksum error in header

Problem

• NDMP restore via FTP fails with Found a checksum error in header during data transfer, but works via HTTP; as sbc_ndmp uses an incorrect seek function, the restore fails.

An incorrect task type is displayed in the backup task for Dell EMC Unity NDMP client

Problem

• (Applies to Dell EMC Unity NDMP backup only) When creating a Dell EMC Unity NDMP backup task in the GUI, the task type NetApp is incorrectly displayed.

HCL Domino

HCL Domino backup fails with Problem while loading dynamic link library

Problem

• HCL Domino 11 backup fails with Problem while loading dynamic link library: [dlopen() returned: libgsk8iccs_64.so. This issue occurs due to Domino 9 server upgrade to SLES12SP5 Domino 11.0.1FP1 which does not contain libgsk8iccs_64.so, required by SEP sesam.

SBC Linux

text

Problem text

Windows backup of a volume mounted as folder name fails

Problem

• On Windows, backing up a volume mounted as a folder name (instead as a drive letter) fails with the message Invalid file name in FILE block.