Beefalo V2 Service Packs

From SEPsesam
Revision as of 21:28, 7 December 2020 by Sta (talk | contribs) (Added Beefalo V2 SP2 fixes (proposed by EE).)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.

SEP provides the following SPs 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 SP 2 (xxx) of Beefalo V2 (4.4.3.84 SP2) - released: xxth of December, 2020. See SEP sesam Release Versions.
  • Service Pack SP 1 (1716dc3) of Beefalo V2 (4.4.3.84 SP1) - released: 14th of October, 2020.

SEP Tip.pngDownload SP

Known issues

SEP sesam v. 4.4.3.84 SP1 – Hyper-V restore of a virtual machine to a different location with a new name may overwrite the original VM

Problem

With version Beefalo V2 SP1 (4.4.3.84 SP1), 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 Beefalo V2 SP1. Hyper-V restore in the previous versions is working fine.

Workaround

Do not perform a Hyper-V VM relocation restore with SEP sesam Beefalo V2 SP1.

Fixed known issues with SP2

SRC (source)

Hyper-V restore of a virtual machine to a different location with a new name may overwrite the original VM

Problem

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.

Cause

The clustered=... information is stored as part of the source and this leads to misinterpreted relocation pattern during the restore. Therefore an offline original VM might be overwritten.

Hyper-V VM complete restore finishes successfully but VM is not recovered

Problem

Hyper-V virtual machine complete restore finishes successfully but some directories are not recovered and VM does not exist in the Hyper-V Manager.

Cause

The parameter recover=clustered is ignored. It is set in the database, but not used for the restore.

EOL of several media is extended by 3 days if a media timeout is set

Problem

The 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 has been retried even if a 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 error 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 __DISKS__. A directory structure is not correct.

The VMDK mount operation is aborted

Problem

The VMDK (sm_vmdk_interface) mount operation is aborted after several minutes.

Cause

The sm_vmdk_interface does not wait until VMDKs become online.

Problem with mounting VMDKs with the same file name on different data stores

Problem

There is a problem with mounting all VMDKs with the same name on different data stores (or folders).

Cause

The data store name is not added to the VMDK path.

The service pack update of SEP sesam Server fails

Problem

The service pack update of SEP sesam Server via GUI fails or does not work correctly.

Cause

The skel sm_execute_update.cmd is missing in the service pack.

Restoring Oracle controlfile from AUTOBACKUP fails with an error

Problem

Restoring Oracle controlfile from AUTOBACKUP fails with: no AUTOBACKUP found or specified handle is not a valid copy or piece.

Cause

During restore the controlfile from AUTOBACKUP is not considered as a valid backup for restore.

Path restore of a Hyper-V VHDX disk ends 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 it is possible to select VHDX instead of a file item in the Hyper-V VM selection view.

Service pack update of the GUI package might fail with an error

Problem

Service pack update of the GUI package might fail with an error according sm_glbv.

Cause

For the update sm_glbv has been used which is not present on the client and GUI systems.

Data restored from BF64 encrypted savesets does not decrypt files

Problem

There is a problem with the data restored from BF64 encrypted savesets because the files are not decrypted.

Cause

Incorrect password has been used during the backup.

CPIO analyze errors during BF64 encrypted backups

Problem

During the BF64 encrypted backups the CPIO analyze errors occur.

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, a backup process fails to remove the dump files.

Cause

The public folder is moved before the deleting process starts.

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 file read permissions.

Cause

The S3 secret and access keys are not encrypted.

VMware backup fails with the IndexError: list index out of range

Problem

VMware backup fails with the IndexError: list index out of range in the sm_reformat_lis.

Cause

The NOT log is missing.

The sm_auto_conf_hw creates a core dump

Problem

The sm_auto_conf_hw creates a core dump if a single drive is attached.

Cause

The uninitialized variable is used.

Remote installation of Windows service pack fails with an error

Problem

Remote installation of Windows SP fails with the "Found glbv gv_extract_only. Nothing to be done."

Cause

Remote installation of Windows SP does not wait until the extraction is finished, hence ends with an error.

GUI

GUI server fails to start with the most recent OpenJDK versions

Problem

GUI server fails to start with the most recent OpenJDK versions. The SEP sesam database is empty.

Cause

GUI server fails to start because it is unable to access the database.

Incorrect task type for Oracle

Problem

When creating 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 sorted.

Not possible to send emails with legal official certificate chain changed on the REST server

Problem

In case of HTTPS certificate Windows file, it is not possible to send emails with legal official certificate chain changed on the REST server.

Cause

If the HTTPS certificate file is a Windows file (\r\n line endings), the certificate fails to decode because the surrounding markers are not removed correctly.

Problem with AD/LDAP users in the sub groups

Problem

AD/LDAP users in the sub groups (nested groups) are not recognized by SEP sesam or you cannot log in with them.

Cause

When using the AD/LDAP user as administrator user, the user roles are not correctly returned by the LDAP server.

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 convert the dates with just one digit for the day correctly.

Fixed known issues with SP1

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 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 was missing.

The sm_cmd hangs

Problem

The sm_cmd hangs and blocks other processes.

Cause

If a system load was very high, the sm_cmd 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.

Kernel

Remote command hangs if one line is too long

Problem

Remote command hangs if a 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 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.

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