Beefalo V2 Service Packs

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

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.

Contents

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 (952b2ad) for Beefalo V2 (4.4.3.84 SP2) - released: 16th of December, 2020.
  • Service Pack 1 (1716dc3) for Beefalo V2 (4.4.3.84 SP1) - released: 14th of October, 2020.
SEP Tip.png 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.
  • Installing either Windows or Linux-specific distributions is pretty straightforward. For Linux systems, SEP provides special service pack executables that ease the installation; see Applying Service Packs on Linux.
  • Download the latest SP.

New supported systems

No changes from Beefalo V2, see New supported systems from Beefalo V2.

Discontinued systems

No changes from Beefalo V2, see Unsupported OS.

Beefalo V2 SP2: Known issues

Service Pack 2 Beefalo V2 known issues:

Severity: CRITICAL

Warning sign.pngSEP 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. 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.
    (*This behavior is seen with the QUADStor VTL only.)
Workaround: Download the hotfix from 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

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 sm_execute_update.cmd file.
Workaround: Download the sm_execute_update.cmd file manually from the Linux service pack directory and copy it to the skel directory of the SEP sesam Linux Server, for example, sesam:/opt/sesam/skel # ls -l sm_execute_update.cmd.
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 lib file for Debian Stretch is required
  • After SP2 is installed, there is an issue with the Python lib file for Debian Stretch on the SEP sesam Server.
Workaround: After the SP 2 installation is complete, you must download and manually copy the Python lib file for Debian Stretch to /opt/sesam/bin/sesam on SEP sesam Server: 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 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.
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

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 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 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 __DISKS__ which may contain images from the previous operation, resulting in the incorrect directory structure.

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.

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 AUTOBACKUP fails with 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 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 sm_glbv.

Cause

SP update uses sm_glbv 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 sm_reformat_lis.

Cause

The NOT log (backup log file) 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 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.

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

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.

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