Beefalo V2 4.4.3.86: Difference between revisions

From SEPsesam
(28 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Draft}}
{{Copyright SEP AG|en}}
{{Copyright SEP AG en}}
__TOC__
__TOC__
== SEP sesam Beefalo 4.4.3.86 overview ==
== SEP sesam Beefalo V2 4.4.3.86 overview ==
 
* version: '''4.4.3.86''' released: '''5<sup>th</sup> of July, 2021'''
* <version> released: <date>  


{{tip|
{{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|SEP sesam release versions]].
*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|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 [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]].  
*Installing either Windows or Linux-specific distributions is pretty straightforward. For Linux systems, SEP provides special service pack executables that ease the installation; see [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]].  
*[https://download.sep.de/LINK/ Download the latest release version].}}
*[https://download.sep.de/servicepacks/current/ Download the latest release version].}}
See also the initial release of [[Beefalo_V2_Service_Packs|''Beefalo V2'' ]] and  [[Beefalo_V2_Service_Packs|''Beefalo V2'' Service Packs Releases]].


===New supported systems===
===New supported systems===


No changes from ''Beefalo V2'', see [[Release_Notes_4.4.3_Beefalo_V2#new_systems|New supported systems from Beefalo V2]].
*OpenNebula 5.10.1 and 6.0


===Discontinued systems===
For a complete list of supported OS and databases, see [[4_4_3_Beefalo:SEP_sesam_OS_and_Database_Support_Matrix|SEP sesam Support Matrix]].


No changes from ''Beefalo V2'', see [[Unsupported_OS|Unsupported OS]].
==={{anchor|unsupported_systems}}Unsupported systems===
{{Note|In SEP sesam [[SEP_sesam_Release_Versions|4.4.3.86 ''Beefalo V2'']], SEP announced that it does not support:
<ul><li>SEP sesam Server 4.4.3.86 ''Beefalo V2'' on '''SLES15 SP3'''</li>
Currently, SEP sesam Server ''4.4.3.86'' on '''SLES15 SP3''' is not supported. Upgrading existing SEP sesam installations on SLES15 from older service packs to SP3 may result in data loss.</ul> }}


=={{anchor|known_issues}}  Known issues ==
=={{anchor|known_issues}}  Known issues ==
{{Box Hint Y|Beefalo 4.4.3.86 known issues|
{{Box Hint Y|Beefalo 4.4.3.86 known issues|
===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 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.
:*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.
-----
===Severity: SEVERE===
;SEP sesam v. 4.4.3.86 - VM backup may fail if a backup source path is too long
:*If a source path of a VM backup is too long, the backup may fail with the following error:<br />''Exit code from sbc_com_interface: [1] - warning<br />Error: VM Exception: [Command [sbc_com_interface, -b, openjob...fails].''<br />Note that this only occurs in rare cases when a large number of VMKDs are attached to VM. If no such error is displayed, the VM backup is successful.
:::'''Resolution:''' Already fixed, contact [https://www.sep.de/download-support/support/ support] for help.
;SEP sesam v. 4.4.3.86 – Mount of RHV, Citrix XEN, KVM or OpenNebula backup fails on Windows Host
:* Mounting the virtual disks of RHV, Citrix XEN, KVM or OpenNebula backup fails on Windows host with an error: ''ImportError: sh 1.12.14 is currently only supported on Linux''.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam v. 4.4.3.86 – Core dump of ''sm_stpd'' during closejob operation via FTP on SLES12 PPC
:*  Core dump occurs during closejob operation over FTP on SLES12 PPC due to string variable being too short.
:::'''Workaround:''' Use the network protocols http:// or https:/;  ensure that the interface is correctly added to the client properties (see [[Special:MyLanguage/Configuring_Clients#procedure|Configuring Clients: Procedure]]).
:::'''Resolution:''' Already fixed, contact support for help.
-----
-----
===Severity: MINOR===
===Severity: MINOR===
;SEP sesam v. 4.4.3.84 SP2 Automatic SP update of Windows clients on the Linux Server fails  
;SEP sesam v. 4.4.3.86 Exchange incremental backup fails sporadically with error
:*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 <tt>sm_execute_update.cmd</tt> file.
:* When trying to perform an Exchange INCR backup, it may fail with an error: <nowiki>''STATUS=WARNING MSG=global name 'self' is not defined''</nowiki>.
:::'''Workaround:''' Download the <tt>sm_execute_update.cmd</tt> file manually from the [https://download.sep.de/servicepacks/4.4.3/4.4.3.84/linux/ Linux service pack directory] and copy it to the <tt>skel</tt> directory of the SEP sesam ''Linux'' Server, for example, {{Path|sesam:/opt/sesam/skel # ls -l sm_execute_update.cmd}}.<br />Then start the SP2 update of the SEP sesam ''Linux'' Server via GUI.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
 
;SEP sesam v. 4.4.3.86 – While configuring Si3 deduplication store, ''sm_config_drives'' aborts on Windows Server 2016/2019
:*(''Windows only'') An Si3 deduplication store is created and configured, then another data store is created; ''sm_config_drives'' starts again and terminates.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam v. 4.4.3.86 – Seeding Si3 deduplication store fails with error
:*Using the ''Initial Seed'' option to set up a new Si3 deduplication store for replication results in a seemingly successful setup, but no data is replicated and the ''sm_dedup_server.log'' shows a Java exception.
:::'''Workaround:''' SEP is working on this issue and will provide a fix as soon as possible.
;SEP sesam v. 4.4.3.86 – After database import via GUI, SEP sesam processes ''rmi'' and ''sds'' are offline
:*When ''sm_db_update'' is finished, SEP sesam is restarted, but all running processes are stopped and fail to get restarted. 
:::'''Workaround:''' Execute the following commands after db import:
sm_main start rmi
sm_main start sds
-----
====''Minor GUI issues''====
We are experiencing some minor GUI issues that do not affect SEP sesam's performance and functionality. SEP is working on these issues and will provide a fix as soon as possible.
;SEP sesam v. 4.4.3.86 – When a loader is reconfigured with a new drive, the drive is not shown
:*When a new loader is created and an already configured drive is moved to the new loader, clicking the ''Apply'' button fails to show the drive for the newly created loader.
:::'''Workaround:''' Close the ''Loaders'' view and then open it to refresh the displayed loader configuration.
;SEP sesam v. 4.4.3.86 – ''Send'' button in migration task properties does not work
:*When using the ''Send'' button for the ''Main log'' in the properties of the migration task, sending does not work.
;SEP sesam v. 4.4.3.86 – Starting disaster recovery from the toolbar fails
:*When attempting to start disaster recovery from the toolbar, an error message is displayed and the operation fails. (This button is only displayed if a Defaults ''disaster_recovery'' entry is set with a value of 1.)
;SEP sesam v. 4.4.3.86 – Filtering may not work correctly in some views
:*When using ''Main Selection'' -> ''Scheduling'' -> ''Events as List'' -> ''Filter'' to filter the results for the backup, the results list is empty.
:*When using ''Main Selection'' -> ''Tasks'' -> ''As List'' -> ''Filter'' to filter tasks by their status, selecting ''Execution off'' will only display tasks where both client and task are disabled.
;SEP sesam v. 4.4.3.86 – Copying a backup task fails to copy assigned schedules
:*When copying a backup task, all properties except assigned schedules are copied to the newly created task.
}}
}}


Line 41: Line 78:
=== Optimized license check ===
=== 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.  
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===
SEP sesam now uses SHA-256 to sign all executables in the Windows kit when upgrading or (re)installing SEP sesam.


=={{anchor|86}} Fixed issues Beefalo 4.4.3.86==
=={{anchor|86}} Fixed issues Beefalo 4.4.3.86==


=== Kernel ===
=== Kernel ===
====Scheduled jobs and external backups fail due to yet uninitilized queue ====
==== 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.
 
====Queue manager fails with ''timed out'' when it is busy for more than 12 hours====
'''''Problem'''''
*Submitting a task in a queue for processing times out waiting for a response when the queue is busy for more than 12 hours.
 
====No error is recorded when the database is locked====
'''''Problem'''''
'''''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.
*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====
====''sm_sms_watch'' crashes when starting the SEP sesam services or a NEWDAY event====
'''''Problem'''''
'''''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.  
*''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 ===
=== Sesam DB ===
====If the connection limit to the PostgreSQL database is reached, SEP sesam Server stops.====
====If the connection limit to the PostgreSQL database is reached, SEP sesam Server stops====
'''''Problem'''''
'''''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.
*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====
====SEP sesam external backup modules (Oracle, Hana...) encounter errors during 'closejob' operation, but 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. 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.
*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 ===
=== Update ===
====SEP sesam v. 4.4.3.85 – Linux update fails due to faulty copy DB file command====
====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'''''
'''''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.
*When 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 <tt>sm_execute_update.cmd</tt> file.


====Windows client update from GUI fails if BSR is already installed on the system====
====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.
*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====
====Installation of SEP sesam BSR Pro fails due to wrong installation path====
'''''Problem'''''
'''''Problem'''''
The installation of SEP sesam BSR Pro fails because of the wrong installation path with wrong double slash in BSR Pro path.
*The installation of SEP sesam BSR Pro fails because of the wrong installation path with wrong double slash in BSR Pro path.


=== STPD ===
=== STPD ===
====When a backup is aborted, STPD does not write the metadata (LIS and SGM file)====
====When a backup is aborted, STPD does not write the metadata (LIS and SGM file)====
'''''Problem'''''
'''''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.
*''(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) ====
====Backup session receives incorrect COM responses (not matching the openjob command) ====
'''''Problem'''''
'''''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).
*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====
====STPD log shows ''cpio'' errors, but backup is successful====
'''''Problem'''''
'''''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.
*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.  


====Restore of data split on several tapes fails====
====Possible data loss if STPD timeout occurs during backup but backup is successful ====
'''''Problem'''''
'''''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.
*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.  
*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====
====Delayed start of STPD main process when using HTTP connection====
'''''Problem'''''
'''''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.
*When performing a migration using HTTP, the start of the http process blocks the main STPD process for a longer period of time as it performs various operations (e.g. HPE communication, authorization).  


====Next EOM after EOM IO error sets IO error flag====
====Restore from HPE StoreOnce fails due to invalid credentials====
'''''Problem'''''
'''''Problem'''''
SMS remembers EOM IO error status on subsequent normal EOM handling and incorrectly sets IO error flag on subsequent EOM.  
*Restore from HPE StoreOnce fails with error: ''RETR Failed. Command error with HPE StoreOnce server [COFC-CZ3935RB01]: OSCLT_ERR_INVALID_CREDENTIALS.'' because password decryption failed.


====Backup to tape with IO error is successful but restore fails====
====Restore from RDX drive fails====
'''''Problem'''''
'''''Problem'''''
Backup to tape with IO error is successful, but restore fails with ''Error: Cannot read from remote archive''.
*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.  


=== Media===
=== SMS ===
====Wrong start time is displayed for readability check ====
====Oracle RMAN multichannel backup fails with ''failed to create sequential file''====
'''''Problem'''''
'''''Problem'''''
The media readability check start time is set in the past.
*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.


====Writing to tape could fail with ''Error sharing violation''  ====
====Backups and migrations to tape drive hang or fail after media change====
'''''Problem'''''
'''''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''.
*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.


=== Virtual environment===
====Backup on VTL that exceeds tape size is shown as successful ====
====Restored OpenNebula VM does not boot====
'''''Problem '''''
'''''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''.
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====
====Restore of data split on several tapes fails====
'''''Problem'''''
'''''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.
*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.  


=== DB modules===
====On sayFUSE, EOM is not recognized and backups fail====
====Saveset query for external backups (Oracle, SAP...) returns failed backups====
'''''Problem'''''
'''''Problem'''''
When searching for savesets related to external backups, savesets with failed status are returned.
*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.


===Restore===
====Next EOM after EOM IO error sets IO error flag====
====Restore exclude filter does not work correctly====
'''''Problem'''''
'''''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.
*SMS remembers EOM IO error status on subsequent normal EOM handling and incorrectly sets IO error flag on subsequent EOM.  


====Restore from migrated saveset uses wrong transport mode====
====Backup to tape with IO error is successful but restore fails====
'''''Problem'''''
'''''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.  
*Backup to tape with IO error is successful, but restore fails with ''Error: Cannot read from remote archive''.  


===Migration===
====The restore performance from tape is 2-3 times slower than backup performance====
====Core dump occurs after starting the migration====
'''''Problem'''''
'''''Problem'''''
Migration is terminated (core dump of ''sm_sms_copy'') with exception 0xc0000417 after a [[Special:MyLanguage/SEP_sesam_Glossary#NEWDAY|NEWDAY]] event occurred.
*Restore throughput is at most half (more likely less) compared to backup, which significantly increases the total restore time.


====Migration is succesful with dabase error====
=== Media===
====Wrong start time is displayed for readability check ====
'''''Problem'''''
'''''Problem'''''
Migration results in database error ''DB_SEL_GETVALUE: Error during DBaccess - return 0''. Incorrect ''szSql'' variable was used to execute DB select.
*The media readability check start time is set in the past.
 


===NDMP===
====Writing to tape could fail with ''Error sharing violation'' ====
====NDMP restore from tape fails====
'''''Problem'''''
'''''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.  
*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''.


===SBC Linux===
=== OpenNebula===
====text====
====Restored OpenNebula VM does not boot====
'''''Problem'''''
'''''Problem'''''
text
*The restored OpenNebula virtual machine does not boot because the recovered image was created with the wrong format setting.


===SBC Windows===
====OpenNebula VM restore fails with ''AttributeError'' or ''ONE instance has no attribute 'o'''====
====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''.
<!--
=={{anchor|SP2}} Fixed issues ==
=== Kernel ===
====SEP sesam v. 4.4.3.84 –  Hyper-V restore with relocation may overwrite the original VM====
'''''Problem'''''
'''''Problem'''''
The previous SP 1 (Beefalo V2 4.4.3.84) introduced a critical issue which is '''solved with SP2''': Hyper-V restore of a virtual machine to a different location with a new name may overwrite the original VM, resulting in complete loss of data stored on the original VM. This only happens if the original VM is offline (powered off) at the time of a restore. This issue only applies if you are running ''SP 1 (4.4.3.84)''.
*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.
 
'''''Workaround'''''
 
Do not perform a Hyper-V VM relocation restore with SEP sesam ''Beefalo V2 SP1'' (4.4.3.84).
 
'''''Cause'''''
 
The ''clustered=...'' information is stored as part of the source; this leads to misinterpreted relocation pattern during the restore and may result in the original offline VM being overwritten.
 
====Hyper-V VM complete restore finishes successfully but VM is not recovered====


====OpenNebula VM architecture is not restored====
'''''Problem'''''
'''''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.


The previous SP 1 (Beefalo V2 4.4.3.84) introduced a [[Beefalo_V2_Service_Packs#cluster|Hyper-V VM clustered restore]] issue which is '''solved with SP2''': Hyper-V VM complete restore finishes successfully but some directories are not recovered and the VM does not exist in the Hyper-V Manager.
=== Citrix XenServer===
 
====When Citrix XenServer CBT backup is started, SEP sesam automatically enables NBD====
'''''Cause'''''
 
The clustered property was not set in the Hyper-V Failover Cluster Manager.
 
====EOL of several media is extended by 3 days if a media timeout is set====
 
'''''Problem'''''
'''''Problem'''''
* When a Citrix XenServer CBT backup is started, SEP sesam enabled NBD on all network interfaces. This was a potential problem if there are interfaces that are inaccessible to the Sesam datamover or if user settings were overwritten on some interfaces.
'''''Solution'''''
* As a result, NBD is no longer automatically enabled. See [[4 4 3:Citrix XenServer Requirements and Configuration]] for how to manually enable NBD.


The [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] of several media is extended by 3 days if a ''media timeout'' is set and there is no media in drive.
=== DB modules===
 
====Saveset query for external backups (Oracle, SAP...) returns failed backups====
'''''Cause'''''
 
The initialization of a tape medium is retried even if the media load timeout has been reached.
 
====Hyper-V VM selective restore fails with ''Failed to find parent file ...q-debian7_1VHD_0.vhdx''====
 
'''''Problem'''''
'''''Problem'''''
*When searching for savesets related to external backups, savesets with failed status are returned.


Hyper-V VM selective restore fails with the following error:
===Backup===
Hyper-V VM selective restore fails with
====Backing up a VM from an ESXI host with a restricted license results in a deadlock====
  Unexpected error: Failed to find parent file "C:\ClusterStorage\Volume1\Q-DEBIAN7_1VHD\DISKS\Q-DEBIAN7_1VHD\q-debian7_1VHD_0.vhdx". in the collection.
 
'''''Cause'''''
 
The problem with the temporary folder <tt>__DISKS__</tt> which may contain images from the previous operation, resulting in the incorrect directory structure.
 
====The VMDK mount operation is aborted====
 
'''''Problem'''''
'''''Problem'''''
When backing up a VM from an ESXI host without an applied license, SEP sesam attempts to create a snapshot for a virtual machine and an exception occurs. Because the runner does not exit correctly, it gets stuck in an endless loop.


The VMDK (<tt>sm_vmdk_interface</tt>) mount operation is aborted after several minutes.
===Restore===
 
====Restore fails with error ''At current offset 144 (0x90) no valid MTF Stream ID was found''====
'''''Cause'''''
 
The <tt>sm_vmdk_interface</tt> does not wait until VMDKs become online.
 
====Mounting VMDKs with the same file name on different data stores causes conflict====
 
'''''Problem'''''
'''''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.


There is a problem with mounting VMDKs if VMDKs on different data stores (or folders) have the same file name.
====Restore from migrated saveset uses wrong transport mode====
 
'''''Cause'''''
 
The data store name is missing in the VMDK path.
 
====Restoring Oracle ''controlfile'' from <tt>AUTOBACKUP</tt> fails with error====
 
'''''Problem'''''
'''''Problem'''''
*When restoring a migrated saveset, the restore wizard displays the settings of the original saveset with the selected transport mode, and 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. 


Restoring Oracle ''controlfile'' from <tt>AUTOBACKUP</tt> fails with: ''no AUTOBACKUP found or specified handle is not a valid copy or piece''.
====Restore exclude filter does not work correctly====
 
'''''Cause'''''
 
During restore the ''controlfile'' from <tt>AUTOBACKUP</tt> is not considered as a valid backup for restore.
 
====Path restore of a Hyper-V VHDX disk fails with ''"No entries found in LIS for..."''====
 
'''''Problem'''''
'''''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. 


Hyper-V VHDX restore into the file system (path restore) fails with the error ''"No entries found in LIS for..."''.
===Migration===
 
====Core dump occurs after starting the migration====
'''''Cause'''''
 
In the SEP sesam GUI Hyper-V VM selection view it is possible to select the VHDX for restore instead of exploring it and restoring a file.
 
====Service pack Client/GUI update may fail with error====
 
'''''Problem'''''
'''''Problem'''''
*Migration is terminated (core dump of ''sm_sms_copy'') with exception 0xc0000417 after a [[Special:MyLanguage/SEP_sesam_Glossary#NEWDAY|NEWDAY]] event occurred.


Service pack update of the GUI package may fail with an error due to using <tt>sm_glbv</tt>.
====Migration from tape fails in case of EOM due to insufficient recorded information on next tape====
 
'''''Cause'''''
 
SP update uses <tt>sm_glbv</tt> which is not present on the Client and GUI systems.
 
====Data restored from BF64-encrypted savesets is not decrypted====
 
'''''Problem'''''
'''''Problem'''''
*Migration of savesets that exist on two tapes (media_change) back to datastore fails. SMS fetches the next media label over the ''restore_results'' table, refers only to the restore and not to a migration task. 


There is a problem with the data restored from the BF64-encrypted savesets as the files are not decrypted.
====Migration is successful with database error====
 
'''''Cause'''''
 
Wrong encryption password was used during the backup.
 
====Errors during processing of BF64-encrypted backups====
 
'''''Problem'''''
'''''Problem'''''
*Migration results in database error ''DB_SEL_GETVALUE: Error during DBaccess - return 0''. Incorrect ''szSql'' variable was used to execute DB select.


During the backup of BF64-encrypted tasks, there are CPIO-related errors.
===NDMP===
 
====NDMP restore from tape fails with error ''RESTORE: Mangled directory''====
'''''Cause'''''
 
The ''BF CPIO header check'' is missing.
 
====Kopano public folder backup does not delete dump files ====
 
'''''Problem'''''
'''''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.


If a Kopano public folder backup is configured, the backup process fails to remove the dump files.
====NDMP restore via FTP fails with ''Found a checksum error in header''====
 
====S3 access data is not encrypted ====
 
'''''Problem'''''
'''''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.


The ''.ini'' file in the Si3 deduplication store on the RDS contains the S3 credentials in plain text and everyone has read permissions.
====An incorrect task type is displayed in the backup task for Dell EMC Unity NDMP client ====
 
'''''Cause'''''
 
The S3 access key is not encrypted.
 
====VMware backup fails with ''IndexError: list index out of range'' ====
 
'''''Problem'''''
'''''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.


VMware backup fails with the ''IndexError: list index out of range'' in the <tt>sm_reformat_lis</tt>.
===HCL Domino ===
====HCL Domino backup fails with ''Problem while loading dynamic link library''====
'''''Cause'''''
 
The NOT log (backup log file) is missing.
 
====The <tt>sm_auto_conf_hw</tt> creates a core dump====
 
'''''Problem'''''
'''''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. 


The <tt>sm_auto_conf_hw</tt> creates a core dump if a single drive is attached.
===SBC Windows===
===Windows backup of a volume mounted as folder name fails===
'''''Cause'''''
 
The uninitialized variable is used.
 
====Remote installation of service pack on Windows fails with error====
 
'''''Problem'''''
 
Remote installation of Windows SP fails with ''"Found glbv gv_extract_only. Nothing to be done."''
'''''Cause'''''
 
Remote installation of SP does on Windows does not wait until the extraction is finished and ends with error.
 
=== GUI ===
====GUI server fails to start with > version 11 OpenJDK====
 
'''''Problem'''''
 
GUI server fails to start with Java runtime > version 11 as the data base access components do not load correctly, resulting in empty SEP sesam database.
'''''Cause'''''
 
GUI server won't start as it is unable to access the database.
 
====Incorrect ''Path'' task type is set for Oracle====
 
'''''Problem'''''
 
When creating an Oracle backup task and selecting the source, the task type is set to ''Path'' instead of ''Oracle''.
'''''Cause'''''
 
The Oracle backup source tree is incorrectly placed under ''All local file systems''.
 
====Sending emails not possible when using the company official certificate====
 
'''''Problem'''''
'''''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''.  
When changing the SSL certificate used by SEP sesam REST services to the company official certificate, it is no longer possible to send emails.
   
   
'''''Cause'''''
===GUI===
 
====The license file in the form of ''lic.ZIP '' was not recognized by the GUI====
The HTTPS certificate file is a Windows file ('''\r\n''' line endings); the certificate fails to decode as the surrounding markers are not removed correctly.
 
====Problem with AD/LDAP users in subgroups ====
 
'''''Problem'''''
 
AD/LDAP users in subgroups (''nested'' groups) are not recognized by SEP sesam and cannot log in to SEP sesam.
'''''Cause'''''
 
The user roles are not correctly returned by the LDAP server (the server is not sending the required
attributes).
 
====Time frame selection in restore wizard does not work====
 
'''''Problem'''''
 
The time frame selection (Saved in period option) in restore wizard does not work correctly.
'''''Cause'''''
 
The date converter does not correctly convert the dates with just one digit for the day.
 
=={{anchor|patchSP1}} Features ==
===={{anchor|cluster}}Hyper-V clustered VM is restored as clustered (by default)====
Hyper-V clustered VM is restored as clustered by default. This setting can be switched off in the restore wizard. <br />
By default, when the clustered VM is restored to the original Hyper-V server, it is restored as clustered to the node that owns it. The restore process recreates the VM with the original name and sets the property ''clustered=yes'' in the Hyper-V Failover Cluster Manager.
 
== Fixed issues ==
 
=== Kernel ===
 
====Remote command hangs if one line is too long====
'''''Problem'''''
 
Remote command hangs if a line from the remote program is longer than 16382 bytes.
 
====Backup to tape fails on Linux====
'''''Problem'''''
 
On some Linux systems, a backup to tape fails because of unsupported read block size - ''errno EBUSY''.
 
====Mounting a VM with multiple disks on Linux====
'''''Problem'''''
 
Mounting a VM with multiple disks on Linux mounts only one disk or fails to mount completely.
 
====vSphere restore fails with ''vmx path has no extension''====
'''''Problem'''''
 
vSphere restore fails with ''vmx path has no extension'' when the VM name is too long.  
 
'''''Cause'''''
 
The VM information was cut off.
 
====Deleting obsolete GLBV====
'''''Problem'''''
 
The obsolete global variables (GLBV) are not deleted.
 
====VM backup with integer VM name fails====
'''''Problem'''''
 
VM backup with integer VM name fails with ''../sbccom.py", line 134, in closejob: cannot concatenate str and int objects'' (especially on Proxmox VE and OpenNebula).
 
'''''Cause'''''
 
The problem occurred with the backup sources (VM names) that consisted of numbers only.
 
====Restore read size issue with LTO 7/LTO 8====
'''''Problem'''''
 
The restore fails if the SMS data server does not reset a block size to the variable block size after write operation with LTO 7/LTO 8.
 
'''''Cause'''''
 
The restore read size is incorrect. Consequently, 2 blocks are read in one read operation. Setting a variable block size for LTO drives resolves the problem.
 
====Selective restore on Windows restores wrong files or fails with the MTF error====
'''''Problem'''''
 
Selective restore of a Windows saveset may restore wrong files or it may fail with MTF error due to ESET after a new segment (mainly on the RDX drives).
 
'''''Cause'''''
 
SSET generated false offset2 for ESET.
 
====<tt>sm_config_hw</tt> changes the device name====
'''''Problem'''''
 
The <tt>sm_config_hw</tt> changes the device name of tape drive to a wrong value.
 
====VMDK mount operation====
'''''Problem'''''
'''''Problem'''''
*The license file written with .zip extension as .ZIP is not recognized and accepted by the GUI, because the check for the archived file is done case sensitive. Therefore SEP sesam tried to read the compressed file directly as a text file and the file was not accepted.


VMDK mount operation uses the savesets from failed migration.
====Password length is limited to 27 characters====
 
====EOM during restore====  
'''''Problem'''''
'''''Problem'''''
*When you configure a new SEP sesam client and switch to the Access tab (for example, when configuring OES, ESXi, Citrix, Linux/VM server types, and other virtualization servers), it is not possible to enter a password longer than 27 characters; it is also not possible to re-enter the password unless 1 character is removed from the first password field.


When using a tape media pool, during the tape change (''Write'' operation) the next label is not known and the restore fails.  
====Source-side deduplication cannot be changed for an existing backup event ====
'''''Problem '''''
*It is not possible to change the setting (enable/disable) for source-side deduplication if it is set for an existing backup event; when creating a new backup event for a Si3 media pool, source-side deduplication can be enabled.


====''SESAM_BACKUP'' on Windows ends with warning====
====Deselecting files for selective restore also deselects all parent directories====
'''''Problem'''''
'''''Problem'''''
*Deselecting a subdirectory/subnode in the tree also deselects the parent directory/node - all files above the deselected directory up to the top level are deselected and only the direct parent directory is subselected, so selective restore is not possible.


''SESAM_BACKUP'' on Windows ends with warning due to thread exit code <tt>STATUS_THREAD_IS_TERMINATING</tt> with disaster interface.
====Restore wizard does not recognize migrated saveset settings====
 
'''''Cause'''''
 
Thread exit code <tt>STATUS_THREAD_IS_TERMINATING</tt> is not handled properly.
 
====Hyper-V single file restore from RDS fails====
'''''Problem'''''
'''''Problem'''''
*When restoring from the migrated backup, the last step of the restore wizard displays the settings of the original backup (media pool, RDS...) and not the specific settings of a migrated saveset.


Hyper-V single file restore from RDS fails with the error ''The system cannot find the path specified''.
====Empty target node selection list in restore wizard for OpenNebula restore ====
 
'''''Cause'''''
 
Hyper-V backup with an incompatible file system was used for mounting.
 
====Restore from the RDX disk drive stalled====
'''''Problem'''''
'''''Problem'''''
*There is no client with the virtualization type ''OpenNebula Server''. Therefore, the target node selection list is empty, but no message is displayed and the restore wizard can continue.


Restore from the RDX disk drive stalled and the STPD log generates log files in an endless loop.
====Adding a drive from a different drive group in the datastore dialog results in an error====
 
====Concurrent processes created same unique ID====
'''''Problem'''''
'''''Problem'''''
*When creating a new drive group and trying to add a new drive of another drive group, an error occurs because it is not possible to use two drive groups for a datastore.


Concurrent processes create the same unique ID. Failure during access to database: SQL query. Compilation with Visual Studio 2019 failed due to unresolved time zone and daylight.
====Active backup results do not appear in the results of the task context menu====
 
====MS SQL backup via ODBC fails====
'''''Problem'''''
 
MS SQL backup via ODBC fails with the protocol error.
 
'''''Cause'''''
 
MS SQL backup is not possible, if ''TLS 1.0'', ''SSL 3.0'' and ''SSL 2.0'' are disabled. The problem was the obsolete ODBC SQL Server driver.
 
====Update statement of results fails when the source is too long====
'''''Problem'''''
 
Update SQL statement for ''DB:results.source'' fails.
 
'''''Cause'''''
 
The size of the SQL command string is too long. Resolved with the correct handling of SQL statements using a backup source longer than 1024 or 2048 characters.
 
=== GUI ===
====VM restore with vCenter 7 fails====
 
'''''Problem'''''
 
VM restore with vCenter 7 fails with the API version error, i.e., ''Version incompatible: apiversion '7.0.0' of vCenter''.
 
'''''Cause'''''
 
Enhancement: Support for VMware vSphere 7.0 (ESXi and vCenter) .
 
====Archive adjustment ''by bar code only'' does not work====
 
'''''Problem'''''
 
The archive adjustment with the option ''Adjustment by bar code only'' does not work.
 
'''''Cause'''''
 
The value of the <tt>-n</tt> parameter was missing.
 
====The <tt>sm_cmd</tt> hangs====
 
'''''Problem'''''
 
The <tt>sm_cmd</tt> hangs and blocks other processes.
 
'''''Cause'''''
 
If a system load was very high, the <tt>sm_cmd</tt> may hung and block other processes.
 
====MS SQL relocation does not work====
'''''Problem'''''
 
The relocation of the MS SQL database via GUI does not work.
 
'''''Cause'''''
 
The MS SQL relocation did not provide logical names.
 
====Hyper-V single file restore fails====
'''''Problem'''''
'''''Problem'''''
 
*GUI does not display the entry for active backup results when opening the results from the task context menu after installation. The active state is not selected in the filter.
Restoring a single file from a Hyper-V (''COPY'') backup fails.
 
'''''Cause'''''
 
The restore wizard drives combo box was empty.
=={{anchor|known_issues}} Known issues ==
{{Box Hint Y|Known issues|
===Severity: CRITICAL===
;[[File:Warning sign.png|20px]]SEP sesam v. 4.4.3.84 – (''Linux'') Backup to VTL library* completed successfully even though there were media write errors reported and 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.'')
:::'''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.  
#>sm_main stop node
#>cd /opt/sesam
#>tar xvzf <hotfix file>
#>sm_main start node
-----
-----
===Severity: MINOR===
{{note|For a list of features, enhancements, and fixed issues in the initial release of Beefalo V2 and its service packs, see [[Beefalo_V2_Service_Packs|''Beefalo V2 Release Notes'' ]] and [[Beefalo_V2_Service_Packs|''Beefalo V2'' Service Packs Releases]].}}
;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 <tt>sm_execute_update.cmd</tt> file.
:::'''Workaround:''' Download the <tt>sm_execute_update.cmd</tt> file manually from the [https://download.sep.de/servicepacks/4.4.3/4.4.3.84/linux/ Linux service pack directory] and copy it to the <tt>skel</tt> directory of the SEP sesam ''Linux'' Server, for example, {{Path|sesam:/opt/sesam/skel # ls -l sm_execute_update.cmd}}.<br />Then start the SP2 update of the SEP sesam ''Linux'' Server via GUI.
 
;SEP sesam v. 4.4.3.84 SP2 – After SP2 is installed, additional Python <tt>lib</tt> file for Debian Stretch is required
:*After SP2 is installed, there is an issue with the Python <tt>lib</tt> file for Debian Stretch on the SEP sesam Server. For example, backup savesets are no longer [[Special:MyLanguage/SEP_sesam_Glossary#purge|purged]] (deleted) from data stores.
:::'''Workaround:''' After the SP 2 installation is complete, you must download and manually copy the Python <tt>lib</tt> file for Debian Stretch to {{path|/opt/sesam/bin/sesam}} on SEP sesam Server:  [http://download.sep.de/servicepacks/4.4.3/4.4.3.84/linux/stretch/libpython2.7.so.1.0 download.sep.de/servicepacks/4.4.3/4.4.3.84/linux/stretch/libpython2.7.so.1.0]
 
;SEP sesam v. 4.4.3.84 – Dell EMC Unity NDMP client configuration issue 
:*(''Applies only to Dell EMC Unity NDMP backup client'') When configuring a Dell EMC Unity NDMP client in the SEP sesam GUI, it is not possible to select ''DELL EMC Unity'' as the operating system.
:::'''Workaround  (''SP2 installation is not required''):''' When configuring a new Dell EMC Unity NDMP client, select ''EMC VNX'' as the operating system; for more details, see [[Special:MyLanguage/4_4_3_Grolar:NDMP_Backup#add_client|Adding NDMP host as a SEP sesam client]]. SEP is working on this issue and will provide a solution as soon as possible.
 
;SEP sesam v. 4.4.3.84 – In the backup task for Dell EMC Unity NDMP client, the wrong source is shown 
:*(''Applies only to Dell EMC Unity NDMP backup'') When creating a Dell EMC Unity NDMP backup task in the GUI and browsing for a source, NetApp is incorrectly shown in the ''Client File View'' and must be ignored.
:::'''Workaround (''SP2 installation is not required'')''': Make sure to select the appropriate ''NDMP source'' for Dell EMC Unity NDMP backup. SEP is working on this issue and will provide a solution as soon as possible.
 
;SEP sesam v. 4.4.3.84 SP1 & SP2 – The update status is not updated after manual update installation
:*After manual update of one or several SEP sesam Clients, the Topology view shows incorrect update status. This status cannot be reset and it will continue to display a yellow arrow on the client even though the client is already updated or if the update has failed.
:::'''Workaround:''' As the update-related fields in the client's table are not automatically cleared after the manual update, execute the following command for each affected client and replace the CLIENTNAME variable with the actual name of the client in SEP sesam.
::: {{Path|<nowiki>sm_db "update clients set available_version='',available_number=NULL,servicepack_available_number=NULL,jar_available_version=NULL,jar_available_number=NULL where name='CLIENTNAME'"</nowiki>}} 
:::SEP is working on this issue and will provide a solution as soon as possible.
 
;SEP sesam v. ≥ 4.4.3.82 – (Windows) SEP sesam GUI cannot be opened when the group policy option ''Prevent access to registry editing tools'' is applied
:*(Applies only to Windows) Running the GUI fails after updating SEP sesam to version ≥ [[SEP_sesam_Release_Versions|4.4.3.82]]. This issue seems to be related to the group policy (GPO) setting: if ''Prevent access to registry editing tools'' is applied for a specific user or group, opening the GUI does not work for the users which are prevented from accessing the Registry. In most cases, users with admin privileges will still be able to run the GUI as they are typically exempt for a GPO (and are able to access the Registry). If this policy is disabled (or not configured), the users may access the GUI regardless of their privileges.
:::'''Workaround:''' To enable access to the GUI for the affected users (typically non-admin users), disable the group policy option ''Prevent access to registry editing tools''. Note that only experts should edit the registry; modifying Windows Registry incorrectly might crash your Windows operating system causing data loss.
::#Press the ''Windows key + R'' to open the ''Run'' window.
::#Type ''gpedit.msc'' and press ''Enter''.
::#In the ''Group Policy Editor'' -> ''User Configuration'' -> ''Administrative Templates'' -> ''System'', double-click on ''Prevent access to registry editing tools'' setting in the right panel and select ''Disable''. Then click ''Apply''.
}}
 
=={{anchor|SP2}} Beefalo V2 SP2: Fixed issues ==
=== Kernel ===
====SEP sesam v. 4.4.3.84 –  Hyper-V restore with relocation may overwrite the original VM====
'''''Problem'''''
 
The previous SP 1 (Beefalo V2 4.4.3.84) introduced a critical issue which is '''solved with SP2''': Hyper-V restore of a virtual machine to a different location with a new name may overwrite the original VM, resulting in complete loss of data stored on the original VM. This only happens if the original VM is offline (powered off) at the time of a restore. This issue only applies if you are running ''SP 1 (4.4.3.84)''.
 
'''''Workaround'''''
 
Do not perform a Hyper-V VM relocation restore with SEP sesam ''Beefalo V2 SP1'' (4.4.3.84).
 
'''''Cause'''''
 
The ''clustered=...'' information is stored as part of the source; this leads to misinterpreted relocation pattern during the restore and may result in the original offline VM being overwritten.
 
====Hyper-V VM complete restore finishes successfully but VM is not recovered====
 
'''''Problem'''''
 
The previous SP 1 (Beefalo V2 4.4.3.84) introduced a [[Beefalo_V2_Service_Packs#cluster|Hyper-V VM clustered restore]] issue which is '''solved with SP2''': Hyper-V VM complete restore finishes successfully but some directories are not recovered and the VM does not exist in the Hyper-V Manager.
 
'''''Cause'''''
 
The clustered property was not set in the Hyper-V Failover Cluster Manager.
 
====EOL of several media is extended by 3 days if a media timeout is set====
 
'''''Problem'''''
 
The [[Special:MyLanguage/SEP_sesam_Glossary#EOL|EOL]] of several media is extended by 3 days if a ''media timeout'' is set and there is no media in drive.
 
'''''Cause'''''
 
The initialization of a tape medium is retried even if the media load timeout has been reached.
 
====Hyper-V VM selective restore fails with ''Failed to find parent file ...q-debian7_1VHD_0.vhdx''====
 
'''''Problem'''''
 
Hyper-V VM selective restore fails with the following error:
Hyper-V VM selective restore fails with
  Unexpected error: Failed to find parent file "C:\ClusterStorage\Volume1\Q-DEBIAN7_1VHD\DISKS\Q-DEBIAN7_1VHD\q-debian7_1VHD_0.vhdx". in the collection.
 
'''''Cause'''''
 
The problem with the temporary folder <tt>__DISKS__</tt> which may contain images from the previous operation, resulting in the incorrect directory structure.
 
====The VMDK mount operation is aborted====
 
'''''Problem'''''
 
The VMDK (<tt>sm_vmdk_interface</tt>) mount operation is aborted after several minutes.
 
'''''Cause'''''
 
The <tt>sm_vmdk_interface</tt> does not wait until VMDKs become online.
 
====Mounting VMDKs with the same file name on different data stores causes conflict====
 
'''''Problem'''''
 
There is a problem with mounting VMDKs if VMDKs on different data stores (or folders) have the same file name.
 
'''''Cause'''''
 
The data store name is missing in the VMDK path.
 
====Restoring Oracle ''controlfile'' from <tt>AUTOBACKUP</tt> fails with error====
 
'''''Problem'''''
 
Restoring Oracle ''controlfile'' from <tt>AUTOBACKUP</tt> fails with: ''no AUTOBACKUP found or specified handle is not a valid copy or piece''.
 
'''''Cause'''''
 
During restore the ''controlfile'' from <tt>AUTOBACKUP</tt> is not considered as a valid backup for restore.
 
====Path restore of a Hyper-V VHDX disk fails with ''"No entries found in LIS for..."''====
 
'''''Problem'''''
 
Hyper-V VHDX restore into the file system (path restore) fails with the error ''"No entries found in LIS for..."''.
 
'''''Cause'''''
 
In the SEP sesam GUI Hyper-V VM selection view it is possible to select the VHDX for restore instead of exploring it and restoring a file.
 
====Service pack Client/GUI update may fail with error====
 
'''''Problem'''''
 
Service pack update of the GUI package may fail with an error due to using <tt>sm_glbv</tt>.
 
'''''Cause'''''
 
SP update uses <tt>sm_glbv</tt> which is not present on the Client and GUI systems.
 
====Data restored from BF64-encrypted savesets is not decrypted====
 
'''''Problem'''''
 
There is a problem with the data restored from the BF64-encrypted savesets as the files are not decrypted.
 
'''''Cause'''''
 
Wrong encryption password was used during the backup.
 
====Errors during processing of BF64-encrypted backups====
 
'''''Problem'''''
 
During the backup of BF64-encrypted tasks, there are CPIO-related errors.
 
'''''Cause'''''
 
The ''BF CPIO header check'' is missing.
 
====Kopano public folder backup does not delete dump files ====
 
'''''Problem'''''
 
If a Kopano public folder backup is configured, the backup process fails to remove the dump files.
 
====S3 access data is not encrypted ====
 
'''''Problem'''''
 
The ''.ini'' file in the Si3 deduplication store on the RDS contains the S3 credentials in plain text and everyone has read permissions.
 
'''''Cause'''''
 
The S3 access key is not encrypted.
 
====VMware backup fails with ''IndexError: list index out of range'' ====
 
'''''Problem'''''
 
VMware backup fails with the ''IndexError: list index out of range'' in the <tt>sm_reformat_lis</tt>.
'''''Cause'''''
 
The NOT log (backup log file) is missing.
 
====The <tt>sm_auto_conf_hw</tt> creates a core dump====
 
'''''Problem'''''
 
The <tt>sm_auto_conf_hw</tt> creates a core dump if a single drive is attached.
'''''Cause'''''
 
The uninitialized variable is used.
 
====Remote installation of service pack on Windows fails with error====
 
'''''Problem'''''
 
Remote installation of Windows SP fails with ''"Found glbv gv_extract_only. Nothing to be done."''
'''''Cause'''''
 
Remote installation of SP does on Windows does not wait until the extraction is finished and ends with error.
 
=== GUI ===
====GUI server fails to start with > version 11 OpenJDK====
 
'''''Problem'''''
 
GUI server fails to start with Java runtime > version 11 as the data base access components do not load correctly, resulting in empty SEP sesam database.
'''''Cause'''''
 
GUI server won't start as it is unable to access the database.
 
====Incorrect ''Path'' task type is set for Oracle====
 
'''''Problem'''''
 
When creating an Oracle backup task and selecting the source, the task type is set to ''Path'' instead of ''Oracle''.
'''''Cause'''''
 
The Oracle backup source tree is incorrectly placed under ''All local file systems''.
 
====Sending emails not possible when using the company official certificate====
 
'''''Problem'''''
 
When changing the SSL certificate used by SEP sesam REST services to the company official certificate, it is no longer possible to send emails.
'''''Cause'''''
 
The HTTPS certificate file is a Windows file ('''\r\n''' line endings); the certificate fails to decode as the surrounding markers are not removed correctly.
 
====Problem with AD/LDAP users in subgroups ====
 
'''''Problem'''''
 
AD/LDAP users in subgroups (''nested'' groups) are not recognized by SEP sesam and cannot log in to SEP sesam.
'''''Cause'''''
 
The user roles are not correctly returned by the LDAP server (the server is not sending the required
attributes).
 
====Time frame selection in restore wizard does not work====
 
'''''Problem'''''
 
The time frame selection (Saved in period option) in restore wizard does not work correctly.
'''''Cause'''''
 
The date converter does not correctly convert the dates with just one digit for the day.
 
=={{anchor|patchSP1}} Beefalo V2 SP1: Features ==
===={{anchor|cluster}}Hyper-V clustered VM is restored as clustered (by default)====
Hyper-V clustered VM is restored as clustered by default. This setting can be switched off in the restore wizard. <br />
By default, when the clustered VM is restored to the original Hyper-V server, it is restored as clustered to the node that owns it. The restore process recreates the VM with the original name and sets the property ''clustered=yes'' in the Hyper-V Failover Cluster Manager.
 
== Beefalo V2 SP1: Fixed issues ==
 
=== Kernel ===
 
====Remote command hangs if one line is too long====
'''''Problem'''''
 
Remote command hangs if a line from the remote program is longer than 16382 bytes.
 
====Backup to tape fails on Linux====
'''''Problem'''''
 
On some Linux systems, a backup to tape fails because of unsupported read block size - ''errno EBUSY''.
 
====Mounting a VM with multiple disks on Linux====
'''''Problem'''''
 
Mounting a VM with multiple disks on Linux mounts only one disk or fails to mount completely.
 
====vSphere restore fails with ''vmx path has no extension''====
'''''Problem'''''
 
vSphere restore fails with ''vmx path has no extension'' when the VM name is too long.
 
'''''Cause'''''
 
The VM information was cut off.
 
====Deleting obsolete GLBV====
'''''Problem'''''
 
The obsolete global variables (GLBV) are not deleted.
 
====VM backup with integer VM name fails====
'''''Problem'''''
 
VM backup with integer VM name fails with ''../sbccom.py", line 134, in closejob: cannot concatenate str and int objects'' (especially on Proxmox VE and OpenNebula).
 
'''''Cause'''''
 
The problem occurred with the backup sources (VM names) that consisted of numbers only.
 
====Restore read size issue with LTO 7/LTO 8====
'''''Problem'''''
 
The restore fails if the SMS data server does not reset a block size to the variable block size after write operation with LTO 7/LTO 8.
 
'''''Cause'''''
 
The restore read size is incorrect. Consequently, 2 blocks are read in one read operation. Setting a variable block size for LTO drives resolves the problem.
 
====Selective restore on Windows restores wrong files or fails with the MTF error====
'''''Problem'''''
 
Selective restore of a Windows saveset may restore wrong files or it may fail with MTF error due to ESET after a new segment (mainly on the RDX drives).
 
'''''Cause'''''
 
SSET generated false offset2 for ESET.
 
====<tt>sm_config_hw</tt> changes the device name====
'''''Problem'''''
 
The <tt>sm_config_hw</tt> changes the device name of tape drive to a wrong value.
 
====VMDK mount operation====
'''''Problem'''''
 
VMDK mount operation uses the savesets from failed migration.
 
====EOM during restore====
'''''Problem'''''
 
When using a tape media pool, during the tape change (''Write'' operation) the next label is not known and the restore fails.
 
====''SESAM_BACKUP'' on Windows ends with warning====
'''''Problem'''''
 
''SESAM_BACKUP'' on Windows ends with warning due to thread exit code <tt>STATUS_THREAD_IS_TERMINATING</tt> with disaster interface.
 
'''''Cause'''''
 
Thread exit code <tt>STATUS_THREAD_IS_TERMINATING</tt> is not handled properly.
 
====Hyper-V single file restore from RDS fails====
'''''Problem'''''
 
Hyper-V single file restore from RDS fails with the error ''The system cannot find the path specified''.
 
'''''Cause'''''
 
Hyper-V backup with an incompatible file system was used for mounting.
 
====Restore from the RDX disk drive stalled====
'''''Problem'''''
 
Restore from the RDX disk drive stalled and the STPD log generates log files in an endless loop.
 
====Concurrent processes created same unique ID====
'''''Problem'''''
 
Concurrent processes create the same unique ID. Failure during access to database: SQL query. Compilation with Visual Studio 2019 failed due to unresolved time zone and daylight.
 
====MS SQL backup via ODBC fails====
'''''Problem'''''
 
MS SQL backup via ODBC fails with the protocol error.
 
'''''Cause'''''
 
MS SQL backup is not possible, if ''TLS 1.0'', ''SSL 3.0'' and ''SSL 2.0'' are disabled. The problem was the obsolete ODBC SQL Server driver.
 
====Update statement of results fails when the source is too long====
'''''Problem'''''
 
Update SQL statement for ''DB:results.source'' fails.
 
'''''Cause'''''
 
The size of the SQL command string is too long. Resolved with the correct handling of SQL statements using a backup source longer than 1024 or 2048 characters.
 
=== GUI ===
====VM restore with vCenter 7 fails====
 
'''''Problem'''''
 
VM restore with vCenter 7 fails with the API version error, i.e., ''Version incompatible: apiversion '7.0.0' of vCenter''.
 
'''''Cause'''''
 
Enhancement: Support for VMware vSphere 7.0 (ESXi and vCenter) .
 
====Archive adjustment ''by bar code only'' does not work====
 
'''''Problem'''''
 
The archive adjustment with the option ''Adjustment by bar code only'' does not work.
 
'''''Cause'''''
 
The value of the <tt>-n</tt> parameter was missing.
 
====The <tt>sm_cmd</tt> hangs====
 
'''''Problem'''''
 
The <tt>sm_cmd</tt> hangs and blocks other processes.
 
'''''Cause'''''
 
If a system load was very high, the <tt>sm_cmd</tt> may hung and block other processes.
 
====MS SQL relocation does not work====
'''''Problem'''''
 
The relocation of the MS SQL database via GUI does not work.
 
'''''Cause'''''
 
The MS SQL relocation did not provide logical names.
 
====Hyper-V single file restore fails====
'''''Problem'''''
 
Restoring a single file from a Hyper-V (''COPY'') backup fails.
 
'''''Cause'''''
 
The restore wizard drives combo box was empty.-->

Revision as of 17:02, 24 August 2021

Copyright © SEP AG 1999-2024. 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.

SEP sesam Beefalo V2 4.4.3.86 overview

  • version: 4.4.3.86 released: 5th of July, 2021
SEP Tip.png Tip

See also the initial release of Beefalo V2 and Beefalo V2 Service Packs Releases.

New supported systems

  • OpenNebula 5.10.1 and 6.0

For a complete list of supported OS and databases, see SEP sesam Support Matrix.

Unsupported systems

Information sign.png Note
In SEP sesam 4.4.3.86 Beefalo V2, SEP announced that it does not support:
  • SEP sesam Server 4.4.3.86 Beefalo V2 on SLES15 SP3
  • Currently, SEP sesam Server 4.4.3.86 on SLES15 SP3 is not supported. Upgrading existing SEP sesam installations on SLES15 from older service packs to SP3 may result in data loss.

Known issues

Beefalo 4.4.3.86 known issues:

Severity: CRITICAL

Warning sign.pngPossible 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: SEVERE

SEP sesam v. 4.4.3.86 - VM backup may fail if a backup source path is too long
  • If a source path of a VM backup is too long, the backup may fail with the following error:
    Exit code from sbc_com_interface: [1] - warning
    Error: VM Exception: [Command [sbc_com_interface, -b, openjob...fails].

    Note that this only occurs in rare cases when a large number of VMKDs are attached to VM. If no such error is displayed, the VM backup is successful.
Resolution: Already fixed, contact support for help.
SEP sesam v. 4.4.3.86 – Mount of RHV, Citrix XEN, KVM or OpenNebula backup fails on Windows Host
  • Mounting the virtual disks of RHV, Citrix XEN, KVM or OpenNebula backup fails on Windows host with an error: ImportError: sh 1.12.14 is currently only supported on Linux.
Workaround: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 4.4.3.86 – Core dump of sm_stpd during closejob operation via FTP on SLES12 PPC
  • Core dump occurs during closejob operation over FTP on SLES12 PPC due to string variable being too short.
Workaround: Use the network protocols http:// or https:/; ensure that the interface is correctly added to the client properties (see Configuring Clients: Procedure).
Resolution: Already fixed, contact support for help.

Severity: MINOR

SEP sesam v. 4.4.3.86 – Exchange incremental backup fails sporadically with error
  • When trying to perform an Exchange INCR backup, it may fail with an error: ''STATUS=WARNING MSG=global name 'self' is not defined''.
Workaround: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 4.4.3.86 – While configuring Si3 deduplication store, sm_config_drives aborts on Windows Server 2016/2019
  • (Windows only) An Si3 deduplication store is created and configured, then another data store is created; sm_config_drives starts again and terminates.
Workaround: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 4.4.3.86 – Seeding Si3 deduplication store fails with error
  • Using the Initial Seed option to set up a new Si3 deduplication store for replication results in a seemingly successful setup, but no data is replicated and the sm_dedup_server.log shows a Java exception.
Workaround: SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. 4.4.3.86 – After database import via GUI, SEP sesam processes rmi and sds are offline
  • When sm_db_update is finished, SEP sesam is restarted, but all running processes are stopped and fail to get restarted.
Workaround: Execute the following commands after db import:
sm_main start rmi
sm_main start sds

Minor GUI issues

We are experiencing some minor GUI issues that do not affect SEP sesam's performance and functionality. SEP is working on these issues and will provide a fix as soon as possible.

SEP sesam v. 4.4.3.86 – When a loader is reconfigured with a new drive, the drive is not shown
  • When a new loader is created and an already configured drive is moved to the new loader, clicking the Apply button fails to show the drive for the newly created loader.
Workaround: Close the Loaders view and then open it to refresh the displayed loader configuration.
SEP sesam v. 4.4.3.86 – Send button in migration task properties does not work
  • When using the Send button for the Main log in the properties of the migration task, sending does not work.
SEP sesam v. 4.4.3.86 – Starting disaster recovery from the toolbar fails
  • When attempting to start disaster recovery from the toolbar, an error message is displayed and the operation fails. (This button is only displayed if a Defaults disaster_recovery entry is set with a value of 1.)
SEP sesam v. 4.4.3.86 – Filtering may not work correctly in some views
  • When using Main Selection -> Scheduling -> Events as List -> Filter to filter the results for the backup, the results list is empty.
  • When using Main Selection -> Tasks -> As List -> Filter to filter tasks by their status, selecting Execution off will only display tasks where both client and task are disabled.
SEP sesam v. 4.4.3.86 – Copying a backup task fails to copy assigned schedules
  • When copying a backup task, all properties except assigned schedules are copied to the newly created task.

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

SEP 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.

Queue manager fails with timed out when it is busy for more than 12 hours

Problem

  • Submitting a task in a queue for processing times out waiting for a response when the queue is busy for more than 12 hours.

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

  • When 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.

Delayed start of STPD main process when using HTTP connection

Problem

  • When performing a migration using HTTP, the start of the http process blocks the main STPD process for a longer period of time as it performs various operations (e.g. HPE communication, authorization).

Restore from HPE StoreOnce fails due to invalid credentials

Problem

  • Restore from HPE 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.

The restore performance from tape is 2-3 times slower than backup performance

Problem

  • Restore throughput is at most half (more likely less) compared to backup, which significantly increases the total restore time.

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 enabled NBD on all network interfaces. This was a potential problem if there are interfaces that are inaccessible to the Sesam datamover or if user settings were overwritten on some interfaces.

Solution

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.

Backup

Backing up a VM from an ESXI host with a restricted license results in a deadlock

Problem When backing up a VM from an ESXI host without an applied license, SEP sesam attempts to create a snapshot for a virtual machine and an exception occurs. Because the runner does not exit correctly, it gets stuck in an endless loop.

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, and 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_results table, refers only to the restore and not to a migration task.

Migration is successful with database 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 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.

GUI

The license file in the form of lic.ZIP was not recognized by the GUI

Problem

  • The license file written with .zip extension as .ZIP is not recognized and accepted by the GUI, because the check for the archived file is done case sensitive. Therefore SEP sesam tried to read the compressed file directly as a text file and the file was not accepted.

Password length is limited to 27 characters

Problem

  • When you configure a new SEP sesam client and switch to the Access tab (for example, when configuring OES, ESXi, Citrix, Linux/VM server types, and other virtualization servers), it is not possible to enter a password longer than 27 characters; it is also not possible to re-enter the password unless 1 character is removed from the first password field.

Source-side deduplication cannot be changed for an existing backup event

Problem

  • It is not possible to change the setting (enable/disable) for source-side deduplication if it is set for an existing backup event; when creating a new backup event for a Si3 media pool, source-side deduplication can be enabled.

Deselecting files for selective restore also deselects all parent directories

Problem

  • Deselecting a subdirectory/subnode in the tree also deselects the parent directory/node - all files above the deselected directory up to the top level are deselected and only the direct parent directory is subselected, so selective restore is not possible.

Restore wizard does not recognize migrated saveset settings

Problem

  • When restoring from the migrated backup, the last step of the restore wizard displays the settings of the original backup (media pool, RDS...) and not the specific settings of a migrated saveset.

Empty target node selection list in restore wizard for OpenNebula restore

Problem

  • There is no client with the virtualization type OpenNebula Server. Therefore, the target node selection list is empty, but no message is displayed and the restore wizard can continue.

Adding a drive from a different drive group in the datastore dialog results in an error

Problem

  • When creating a new drive group and trying to add a new drive of another drive group, an error occurs because it is not possible to use two drive groups for a datastore.

Active backup results do not appear in the results of the task context menu

Problem

  • GUI does not display the entry for active backup results when opening the results from the task context menu after installation. The active state is not selected in the filter.

Information sign.png Note
For a list of features, enhancements, and fixed issues in the initial release of Beefalo V2 and its service packs, see Beefalo V2 Release Notes and Beefalo V2 Service Packs Releases.