Beefalo V2 4.4.3.86: Difference between revisions
No edit summary |
(In progress.) |
||
Line 23: | Line 23: | ||
===Severity: CRITICAL=== | ===Severity: CRITICAL=== | ||
;[[File:Warning sign.png|20px]]Possible data loss due to non-executed updates of the entries in the SEP sesam database at extremely high system load. | ;[[File:Warning sign.png|20px]]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 | :*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. | :::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible. | ||
;SEP sesam v. 4.4.3.84 – (''Linux'') Backup to VTL library* completed successfully | ;Backup jobs fail with MTF analyze errors | ||
:*After updating to 4.4.3.86, several backups end with ''553 STOR Failed. MTF analyze error [Error: Invalid MTF descriptor block checksum. (53)]''. | |||
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible. | |||
;Backup to tape succeeds despite IO error, but restore fails | |||
:*An IO error can occur during a backup, for example, if the tape is forcibly unloaded from the drive. A backup is still successful, splitting the saveset between two tapes. However, the restore fails with ''Error: Cannot read from remote archive''. | |||
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible. | |||
;SEP sesam v. 4.4.3.84 – (''Linux'') Backup to VTL library* completed successfully although media write errors were reported and the backup could not be completed | |||
:*(''Applies only to Linux'') When backing up to VTL, the VTL library cannot continue writing to the underlying block device due to insufficient space and tracks error. [[Special:MyLanguage/SEP_sesam_Glossary#SMS|SMS]] ignores the error and continues writing the data to VTL without sufficient space. Backup log shows backup completed successfully although it actually failed and no data was written to backup media. <br />(*''This behavior is seen with the QUADStor VTL only.'') | :*(''Applies only to Linux'') When backing up to VTL, the VTL library cannot continue writing to the underlying block device due to insufficient space and tracks error. [[Special:MyLanguage/SEP_sesam_Glossary#SMS|SMS]] ignores the error and continues writing the data to VTL without sufficient space. Backup log shows backup completed successfully although it actually failed and no data was written to backup media. <br />(*''This behavior is seen with the QUADStor VTL only.'') | ||
:::'''Workaround:''' Download the hotfix from [http://download.sep.de/servicepacks/4.4.3/4.4.3.84/hotfix/linux/ SEP Download Center] to your Linux server or RDS and install it by executing the following commands as ''root'' in a terminal session. '''Attention:''' This operation will stop all running backups. | :::'''Workaround:''' Download the hotfix from [http://download.sep.de/servicepacks/4.4.3/4.4.3.84/hotfix/linux/ SEP Download Center] to your Linux server or RDS and install it by executing the following commands as ''root'' in a terminal session. '''Attention:''' This operation will stop all running backups. | ||
Line 66: | Line 74: | ||
== Enhancements and changes Beefalo 4.4.3.86 == | == 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 start-up. | |||
=={{anchor|86}} Fixed issues Beefalo 4.4.3.86== | =={{anchor|86}} Fixed issues Beefalo 4.4.3.86== | ||
=== Sesam DB === | === Sesam DB === | ||
====SEP sesam v. 4.4.3.84 – If connection limit to PostgreSQL database is reached, SEP sesam Server | ====SEP sesam v. 4.4.3.84 – If the connection limit to the PostgreSQL database is reached, SEP sesam Server stops running==== | ||
'''''Problem''''' | '''''Problem''''' | ||
By default Sesam DB instance runs with default | 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 on database access errors and reaching the maximum connection limit. | ||
====SEP sesam v. 4.4.3.xx – Check status of 'sbc_com closejob' call | ====SEP sesam v. 4.4.3.xx – Check status of 'sbc_com closejob' call before backup is reported as successful==== | ||
'''''Problem''''' | '''''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. If, for example, the copy of the SGM file fails, the saveset will not be found during restore. Checksum errors may also be detected, but the backup is still shown as successful. | |||
SEP sesam external backup modules (Oracle, Hana...) report backups as successful after data transfer is | |||
=== Update === | === Update === | ||
====SEP sesam v. 4.4.3.85 – | ====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''''' | '''''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. | |||
=== STPD === | === STPD === | ||
====If a backup is | ====If a backup is aborted, STPD does not write the metadata (LIS and SGM file), making the saveset invisible and unable to be deleted ==== | ||
'''''Problem''''' | '''''Problem''''' | ||
''(Applies only to Windows)'' STPD (Sesam Transfer Protocol Server) | ''(Applies only to Windows)'' STPD (Sesam Transfer Protocol Server) does not write metadata (LIS and SGM file), causing a saveset to become invisible and unable to be deleted, even though it occupies the space. | ||
=== SMS === | === SMS === | ||
====On sayFUSE, EOM is not recognized==== | ====On sayFUSE, EOM is not recognized==== | ||
'''''Problem''''' | '''''Problem''''' | ||
The EOM (End of Media) (EOM) parameter is not recognized on sayFUSE, causing backups to fail seemingly | The EOM (End of Media) (EOM) parameter is not recognized on sayFUSE, causing backups to fail for seemingly no reason. | ||
====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 during IO rrror is successful but restore fails==== | |||
'''''Problem''''' | |||
Backup to tape during IO error is successful, but restore fails with ''Error: Cannot read from remote archive''. | |||
=== Media=== | === Media=== | ||
====Wrong start time is | ====Wrong start time is displayed for readability check ==== | ||
'''''Problem''''' | '''''Problem''''' | ||
''Start time for media readability check is | ''Start time for media readability check is set in the past. | ||
=== Virtual environment=== | |||
====Restored OpenNebula VM does not boot==== | |||
'''''Problem''''' | |||
Restored OpenNebula virtual machine fails to boot because the restored 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. | |||
===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) thus the matching file cannot be found and excluded. | |||
===Migration=== | |||
====Core dump occurs after starting the migration==== | |||
'''''Problem''''' | |||
The migration is terminated (core dump of ''sm_sms_copy'') with exception 0xc0000417 after a [[Special:MyLanguage/SEP_sesam_Glossary#NEWDAY|NEWDAY]] event occurred. | |||
===xxx=== | |||
====Core dump occurs after the migration was started==== | |||
'''''Problem''''' | |||
The migration is terminated (core dump of ''sm_sms_copy'') with exception 0xc0000417 after a [[Special:MyLanguage/SEP_sesam_Glossary#NEWDAY|NEWDAY]] event has occured. | |||
===SBC Linux=== | |||
====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 as "-*.ini" (- prefix), but the filename is not extracted correctly (e.g., /debug.ini instead of debug.ini) thus the matching file cannot be found and excluded. Another example of the erroneous exclude filtering is failing to reset after the first match so all the following items are excluded, too. | |||
<!-- | |||
=={{anchor|SP2}} Fixed issues == | =={{anchor|SP2}} Fixed issues == | ||
=== Kernel === | === Kernel === | ||
Line 917: | Line 970: | ||
'''''Cause''''' | '''''Cause''''' | ||
The restore wizard drives combo box was empty. | The restore wizard drives combo box was empty.--> |
Revision as of 20:39, 17 June 2021
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
#>sm_main stop node #>cd /opt/sesam #>tar xvzf <hotfix file> #>sm_main start node 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 start-up.
Fixed issues Beefalo 4.4.3.86
Sesam DB
SEP sesam v. 4.4.3.84 – If the connection limit to the PostgreSQL database is reached, SEP sesam Server stops running
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 on 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 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. If, for example, the copy of the SGM file fails, the saveset will not be found during restore. Checksum errors may also be detected, but the backup is still 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.
STPD
If a backup is aborted, STPD does not write the metadata (LIS and SGM file), making the saveset invisible and unable to be deleted
Problem (Applies only to Windows) STPD (Sesam Transfer Protocol Server) does not write metadata (LIS and SGM file), causing a saveset to become invisible and unable to be deleted, even though it occupies the space.
SMS
On sayFUSE, EOM is not recognized
Problem The EOM (End of Media) (EOM) parameter is not recognized on sayFUSE, causing backups to fail for seemingly no reason.
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 during IO rrror is successful but restore fails
Problem Backup to tape during IO error is successful, but restore fails with Error: Cannot read from remote archive.
Media
Wrong start time is displayed for readability check
Problem Start time for media readability check is set in the past.
Virtual environment
Restored OpenNebula VM does not boot
Problem Restored OpenNebula virtual machine fails to boot because the restored 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.
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) thus the matching file cannot be found and excluded.
Migration
Core dump occurs after starting the migration
Problem The migration is terminated (core dump of sm_sms_copy) with exception 0xc0000417 after a NEWDAY event occurred.
xxx
Core dump occurs after the migration was started
Problem The migration is terminated (core dump of sm_sms_copy) with exception 0xc0000417 after a NEWDAY event has occured.
SBC Linux
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 as "-*.ini" (- prefix), but the filename is not extracted correctly (e.g., /debug.ini instead of debug.ini) thus the matching file cannot be found and excluded. Another example of the erroneous exclude filtering is failing to reset after the first match so all the following items are excluded, too.