Release of Service Pack 1 of Beefalo V2: Difference between revisions
(Draft for SP1 Beefalo V2 release (proposed by EE), in progress.) |
(In progress.) |
||
Line 1: | Line 1: | ||
__NOTOC__ | |||
{{Draft}} | {{Draft}} | ||
Service Pack 1 of [[SEP_sesam_Release_Versions|''Beefalo V2'']] (4.4.3.84 SP1) is now available. It is highly recommended to install SP1 as it includes various performance, stability and key fixes | Service Pack 1 of [[SEP_sesam_Release_Versions|''Beefalo V2'']] (4.4.3.84 SP1) is now available. It is highly recommended to install SP1 as it includes various performance, stability, security, and key fixes not available in the [[Release_Notes_4.4.3_Beefalo_V2|initial release of ''Beefalo V2'']]. | ||
[https://download.sep.de/ Download SP1]. | |||
== Fixed known issues and limitations == | == Fixed known issues and limitations == | ||
=== GUI === | === 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''''' | |||
Version check for VMware vCenter 7 does not work. | |||
====Archive adjustment ''by barcode only'' does not work==== | |||
'''''Problem''''' | |||
The archive adjustment with the option ''Adjustment by barcode only'' does not work. | |||
'''''Cause''''' | |||
The value of the <tt>-n</tt> parameter is missing. | |||
====The <tt>sm_cmd</tt> hangs==== | |||
'''''Problem''''' | |||
The <tt>sm_cmd</tt> hangs and blocks other processes. | |||
'''''Cause''''' | |||
If a system load is very high, the <tt>sm_cmd</tt> may hang and blocks other processes. | |||
====MS SQL relocation does not work==== | |||
'''''Problem''''' | |||
Relocation of MS SQL database via GUI does not work. | |||
'''''Cause''''' | |||
MS SQL relocation does 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 is empty. | |||
=== Kernel === | === Kernel === | ||
====Remote command hangs if one line is too long==== | |||
'''''Problem''''' | |||
Remote command hangs if one line 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 is cut off. | |||
====Deleting obsolete GLBV==== | |||
'''''Problem''''' | |||
The obsolete 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 VM name consists only of numbers. | |||
====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 variable after write operation with LTO 7/LTO 8. | |||
'''''Cause''''' | |||
The restore read size is incorrect. Consequently, 2 blocks are read in one read operation. | |||
====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 generates 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 incompatible file system was used for mounting. | |||
====Restore from the RDX disk drive stalled==== | |||
'''''Problem''''' | |||
Restore from the RDX disk drive stalled and STPD log generates log files in endless loop. | |||
====The same unique ID is created during processes==== | |||
'''''Problem''''' | |||
Concurrent processes create the same unique ID. Compilation with Visual Studio 2019 failed due to unresolved time zone and daylight. | |||
====MS SQL backup via ODBC fails==== | |||
====Restore from the RDX disk drive stalled==== | |||
'''''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. | |||
====Update statement of results fails when source is too long==== | |||
'''''Problem''''' | |||
Update SQL statement for ''DB:results.source'' fails. | |||
'''''Cause''''' | |||
The size of SQL command string is too long. |
Revision as of 16:41, 13 October 2020
Service Pack 1 of Beefalo V2 (4.4.3.84 SP1) is now available. It is highly recommended to install SP1 as it includes various performance, stability, security, and key fixes not available in the initial release of Beefalo V2.
Fixed known issues and limitations
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
Version check for VMware vCenter 7 does not work.
Archive adjustment by barcode only does not work
Problem
The archive adjustment with the option Adjustment by barcode only does not work.
Cause
The value of the -n parameter is missing.
The sm_cmd hangs
Problem
The sm_cmd hangs and blocks other processes.
Cause
If a system load is very high, the sm_cmd may hang and blocks other processes.
MS SQL relocation does not work
Problem
Relocation of MS SQL database via GUI does not work.
Cause
MS SQL relocation does 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 is empty.
Kernel
Remote command hangs if one line is too long
Problem
Remote command hangs if one line 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 is cut off.
Deleting obsolete GLBV
Problem
The obsolete 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 VM name consists only of numbers.
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 variable after write operation with LTO 7/LTO 8.
Cause
The restore read size is incorrect. Consequently, 2 blocks are read in one read operation.
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 generates false offset2 for ESET.
sm_config_hw changes the device name
Problem
The sm_config_hw 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 STATUS_THREAD_IS_TERMINATING with disaster interface.
Cause
Thread exit code STATUS_THREAD_IS_TERMINATING 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 incompatible file system was used for mounting.
Restore from the RDX disk drive stalled
Problem
Restore from the RDX disk drive stalled and STPD log generates log files in endless loop.
The same unique ID is created during processes
Problem Concurrent processes create the same unique ID. Compilation with Visual Studio 2019 failed due to unresolved time zone and daylight.
MS SQL backup via ODBC fails
Restore from the RDX disk drive stalled
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.
Update statement of results fails when source is too long
Problem
Update SQL statement for DB:results.source fails.
Cause
The size of SQL command string is too long.