Beefalo V2 4.4.3.86
SEP sesam Beefalo 4.4.3.86 overview
- <version> released: <date>
Tip | |
|
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
Severity: MINOR
|
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.
Fixed issues Beefalo 4.4.3.86
Kernel
Scheduled jobs and external backups fail due to yet uninitilized 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.
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 v. 4.4.3.xx – Check status of 'sbc_com closejob' call before backup is reported 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 the restore. Checksum errors may also be detected, but the backup will still be shown as successful.
Update
SEP sesam v. 4.4.3.85 – 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.
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).
SMS
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.
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
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.
Virtual environment
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 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.
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 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.
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.
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 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
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.
SBC Linux
text
Problem text
SBC Windows
=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.