Beefalo V2 Service Packs
Copyright © SEP AG 1999-2020. 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.
- 1 Beefalo V2 Service Packs overview
- 2 Beefalo V2 SP2: Known issues
- 3 Beefalo V2 SP2: Fixed issues
- 3.1 Kernel
- 3.1.1 SEP sesam v. 188.8.131.52 – Hyper-V restore with relocation may overwrite the original VM
- 3.1.2 Hyper-V VM complete restore finishes successfully but VM is not recovered
- 3.1.3 EOL of several media is extended by 3 days if a media timeout is set
- 3.1.4 Hyper-V VM selective restore fails with Failed to find parent file ...q-debian7_1VHD_0.vhdx
- 3.1.5 The VMDK mount operation is aborted
- 3.1.6 Mounting VMDKs with the same file name on different data stores causes conflict
- 3.1.7 Restoring Oracle controlfile from AUTOBACKUP fails with error
- 3.1.8 Path restore of a Hyper-V VHDX disk fails with "No entries found in LIS for..."
- 3.1.9 Service pack Client/GUI update may fail with error
- 3.1.10 Data restored from BF64-encrypted savesets is not decrypted
- 3.1.11 Errors during processing of BF64-encrypted backups
- 3.1.12 Kopano public folder backup does not delete dump files
- 3.1.13 S3 access data is not encrypted
- 3.1.14 VMware backup fails with IndexError: list index out of range
- 3.1.15 The sm_auto_conf_hw creates a core dump
- 3.1.16 Remote installation of service pack on Windows fails with error
- 3.2 GUI
- 3.1 Kernel
- 4 Beefalo V2 SP1: Features
- 5 Beefalo V2 SP1: Fixed issues
- 5.1 Kernel
- 5.1.1 Remote command hangs if one line is too long
- 5.1.2 Backup to tape fails on Linux
- 5.1.3 Mounting a VM with multiple disks on Linux
- 5.1.4 vSphere restore fails with vmx path has no extension
- 5.1.5 Deleting obsolete GLBV
- 5.1.6 VM backup with integer VM name fails
- 5.1.7 Restore read size issue with LTO 7/LTO 8
- 5.1.8 Selective restore on Windows restores wrong files or fails with the MTF error
- 5.1.9 sm_config_hw changes the device name
- 5.1.10 VMDK mount operation
- 5.1.11 EOM during restore
- 5.1.12 SESAM_BACKUP on Windows ends with warning
- 5.1.13 Hyper-V single file restore from RDS fails
- 5.1.14 Restore from the RDX disk drive stalled
- 5.1.15 Concurrent processes created same unique ID
- 5.1.16 MS SQL backup via ODBC fails
- 5.1.17 Update statement of results fails when the source is too long
- 5.2 GUI
- 5.1 Kernel
Beefalo V2 Service Packs overview
SEP provides the following service packs for Beefalo V2. It is highly recommended to install the latest available SP as it includes various performance, stability, and other key customer fixes not available in the initial release of Beefalo V2.
- Service Pack 2 (xxx) of Beefalo V2 (184.108.40.206 SP2) - released: 16th of December, 2020.
- Service Pack 1 (1716dc3) of Beefalo V2 (220.127.116.11 SP1) - released: 14th of October, 2020.
New supported systems
No changes from Beefalo V2, see New supported systems from Beefalo V2.
No changes from Beefalo V2, see Unsupported OS.
Beefalo V2 SP2: Known issues
|Service Pack 2 Beefalo V2 known issues:|
#>sm_main stop node #>cd /opt/sesam #>tar xvzf <hotfix file> #>sm_main start node
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'"
SEP is working on this issue and will provide a solution as soon as possible.
Beefalo V2 SP2: Fixed issues
SEP sesam v. 18.104.22.168 – Hyper-V restore with relocation may overwrite the original VM
The previous SP 1 (Beefalo V2 22.214.171.124) 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 (126.96.36.199).
Do not perform a Hyper-V VM relocation restore with SEP sesam Beefalo V2 SP1 (188.8.131.52).
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
The previous SP 1 (Beefalo V2 184.108.40.206) introduced a 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.
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
The EOL of several media is extended by 3 days if a media timeout is set and there is no media in drive.
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
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.
The problem with the temporary folder __DISKS__ which may contain images from the previous operation, resulting in the incorrect directory structure.
The VMDK mount operation is aborted
The VMDK (sm_vmdk_interface) mount operation is aborted after several minutes.
The sm_vmdk_interface does not wait until VMDKs become online.
Mounting VMDKs with the same file name on different data stores causes conflict
There is a problem with mounting VMDKs if VMDKs on different data stores (or folders) have the same file name.
The data store name is missing in the VMDK path.
Restoring Oracle controlfile from AUTOBACKUP fails with error
Restoring Oracle controlfile from AUTOBACKUP fails with: no AUTOBACKUP found or specified handle is not a valid copy or piece.
During restore the controlfile from AUTOBACKUP 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..."
Hyper-V VHDX restore into the file system (path restore) fails with the error "No entries found in LIS for...".
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
Service pack update of the GUI package may fail with an error due to using sm_glbv.
SP update uses sm_glbv which is not present on the Client and GUI systems.
Data restored from BF64-encrypted savesets is not decrypted
There is a problem with the data restored from the BF64-encrypted savesets as the files are not decrypted.
Wrong encryption password was used during the backup.
Errors during processing of BF64-encrypted backups
During the backup of BF64-encrypted tasks, there are CPIO-related errors.
The BF CPIO header check is missing.
Kopano public folder backup does not delete dump files
If a Kopano public folder backup is configured, the backup process fails to remove the dump files.
S3 access data is not encrypted
The .ini file in the Si3 deduplication store on the RDS contains the S3 credentials in plain text and everyone has read permissions.
The S3 access key is not encrypted.
VMware backup fails with IndexError: list index out of range
VMware backup fails with the IndexError: list index out of range in the sm_reformat_lis.
The NOT log (backup log file) is missing.
The sm_auto_conf_hw creates a core dump
The sm_auto_conf_hw creates a core dump if a single drive is attached.
The uninitialized variable is used.
Remote installation of service pack on Windows fails with error
Remote installation of Windows SP fails with "Found glbv gv_extract_only. Nothing to be done."
Remote installation of SP does on Windows does not wait until the extraction is finished and ends with error.
GUI server fails to start with > version 11 OpenJDK
GUI server fails to start with Java runtimes > version 11 as the data base access components do not load correctly, resulting in empty SEP sesam database.
GUI server won't start as it is unable to access the database.
Incorrect Path task type is set for Oracle
When creating an Oracle backup task and selecting the source, the task type is set to Path instead of Oracle.
The Oracle backup source tree is incorrectly placed under All local file systems.
Sending emails not possible when using the company official certificate
When changing the SSL certificate used by SEP sesam REST services to the company official certificate, it is no longer possible to send emails.
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
AD/LDAP users in subgroups (nested groups) are not recognized by SEP sesam and cannot log in to SEP sesam.
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
The time frame selection (Saved in period option) in restore wizard does not work correctly.
The date converter does not correctly convert the dates with just one digit for the day.
Beefalo V2 SP1: Features
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.
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
Remote command hangs if one line is too long
Remote command hangs if a line is longer than 16382 bytes.
Backup to tape fails on Linux
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
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
vSphere restore fails with vmx path has no extension when the VM name is too long.
The VM information was cut off.
Deleting obsolete GLBV
The obsolete global variables (GLBV) are not deleted.
VM backup with integer VM name fails
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).
The problem occurred with the backup sources (VM names) that consisted of numbers only.
Restore read size issue with LTO 7/LTO 8
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.
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
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).
SSET generated false offset2 for ESET.
sm_config_hw changes the device name
The sm_config_hw changes the device name of tape drive to a wrong value.
VMDK mount operation
VMDK mount operation uses the savesets from failed migration.
EOM during restore
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
SESAM_BACKUP on Windows ends with warning due to thread exit code STATUS_THREAD_IS_TERMINATING with disaster interface.
Thread exit code STATUS_THREAD_IS_TERMINATING is not handled properly.
Hyper-V single file restore from RDS fails
Hyper-V single file restore from RDS fails with the error The system cannot find the path specified.
Hyper-V backup with an incompatible file system was used for mounting.
Restore from the RDX disk drive stalled
Restore from the RDX disk drive stalled and the STPD log generates log files in an endless loop.
Concurrent processes created same unique ID
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
MS SQL backup via ODBC fails with the protocol error.
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
Update SQL statement for DB:results.source fails.
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.
VM restore with vCenter 7 fails
VM restore with vCenter 7 fails with the API version error, i.e., Version incompatible: apiversion '7.0.0' of vCenter.
Enhancement: Support for VMware vSphere 7.0 (ESXi and vCenter) .
Archive adjustment by barcode only does not work
The archive adjustment with the option Adjustment by barcode only does not work.
The value of the -n parameter was missing.
The sm_cmd hangs
The sm_cmd hangs and blocks other processes.
If a system load was very high, the sm_cmd may hung and block other processes.
MS SQL relocation does not work
The relocation of the MS SQL database via GUI does not work.
The MS SQL relocation did not provide logical names.
Hyper-V single file restore fails
Restoring a single file from a Hyper-V (COPY) backup fails.
The restore wizard drives combo box was empty.