Hints for beta testing

From SEPsesam
Jump to: navigation, search
Information sign.png Note
IMPORTANT – READ CAREFULLY

SEP sesam provides SEP sesam 4.4.3 Beefalo beta version as a test program. This means that 4.4.3 Beefalo beta is provided on an "as is" basis and without warranty! Beta version may contain errors and bugs and may cause problems that could lead to system failures and data loss. THEREFORE, SEP sesam BETA IS NOT INTENDED OR SUITED FOR PRODUCTIVE USE! By downloading, installing and using SEP sesam beta software, you acknowledge that you are aware of the beta release version status and agree that the use of the beta version is entirely at your risk. SEP AG excludes all liability for any claims, losses and damages arising out of use of beta version. Also excluded is the liability for used third-party products and for any data loss due to SEP sesam beta software-related system or hardware failures. If you do not agree to this terms, DO NOT INSTALL OR USE THIS BETA VERSION.

Testing SEP sesam 4.4.3 Beefalo beta

If you are interested in testing the beta version, please register as a beta tester by email to beta@sep.de. To learn about new features, check the Release Notes 4.4.3 Beefalo. Then read the following notes and hints that can help you to get started with your BETA test.

Known issues and limitations

Information sign.png Note
Antivirus programs may disrupt network communication and cause SEP sesam processes, such as backup and replication, to fail. One program that is known to cause SEP sesam processes to terminate is Sophos Firewall with IPS (Intrusion Prevention System) enabled. Make sure that there are no antivirus, firewall, IDS or IPS programs preventing interaction with SEP sesam.
4.4.3 Beefalo known issues:
SEP sesam v. 4.4.3.70–72 – When several paths are specified for Linux or Windows path backup, only the last path is backed up
  • Linux and Windows path backups may incorrectly back up only the last backup source, if a SEP sesam Server v. 4.4.3.70–72 Beefalo is used together with a SEP sesam Client v. 4.4.3.64 Grolar and at least two backup sources are defined for a path backup. For example, if there are more sources specified, such as /var/www, /root, /etc, only the last backup source /etc is backed up, but the backup finished successfully without any errors.
Resolution: If not yet done, upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.
SEP sesam v. 4.4.3.70–72 – Migration from saveset on sayTEC-sayFUSE leads to error 'Checksum of saveset copy does not match'
  • In case of VMware VMDK saveset, migration from tape (sayFUSE) to tape (sayFUSE) ends with checksum error 'Checksum of saveset copy does not match'.
Resolution: If not yet done, upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.
SEP sesam v. 4.4.3.72 – BSR restore on Windows from a bootable image does not work
  • Restoring BSR on Windows from a bootable image does not work, when the BSR ISO boot image is created on the GUI installation installed on the D: volume.
Workaround: Install BSR Pro to the system volume C: or use the SEP sesam Server installation package for GUI installation, see SEP sesam Quick Install Guide. SEP is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.70–72 – Linux BSR backup fails if the task type is selected manually
  • If you select the Linux BSR task type manually from the drop-down list when creating a backup task for Linux BSR backup, the backup will fail. However, if you select the Linux BSR backup source by browsing and let the task type to be set automatically, the backup will work.
Resolution: If not yet done, upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.
SEP sesam v. 4.4.3.70–72 – Si3 service does not start if key Log_Levels is missing in stpd.ini
  • Si3 service fails to start after update because the command sm_dedup_interface exits with error message "STATUS=ERROR MSG=No such node (STPD_Logging.Log_Levels)"
  • Backups on Datastore fail with error message "Error: Could not access data store. No such node (STPD_Logging.Log_Levels) No such node (STPD_Logging.Log_Levels)"
Workaround: Locate the stpd.ini file (<SESAM_ROOT>/var/ini/stpd.ini) on the SEP sesam Server/RDS, open it using a text editor and set the log setting Log_Levels=0 1 2 under [STPD_Logging]. Execute the command sm_config_drives afterwards to regenerate the drive configuration.
Resolution: Upgrade the SEP sesam Server to version 4.4.3.72 and then install a service pack, available under http://download.sep.de/servicepacks/4.4.3/4.4.3.72.
SEP sesam v. ≤ 4.4.3.71 – SQL injection vulnerability in SEP sesam versions ≤ 4.4.3.71
  • The SQL injection vulnerability can pose a major security threat to SEP sesam as it can completely paralyze SEP sesam operations.
Resolution: Fixed with version 4.4.3.72.
SEP sesam v. 4.4.3.71 – Using Microsoft deduplication-enabled volume for SEP sesam data store might result in data loss
  • SEP sesam data store check function does not recognize deduplicated data files correctly and will report the corresponding backups as missing. If clean-up of a database is selected, all unrecognized (deduplicated) files will be removed from the data store.
Resolution: Fixed with version 4.4.3.72.
SEP sesam v. 4.4.3.70–71 – Restoring a Hyper-V VM with setting a target path results in restore to original VM
  • Restoring a Hyper-V VM with setting a target path for a VM leads to restoring to the original VM. This may cause permanent data loss if the original VM is online and it still exists in the specified location as all its data may be overwritten.
Resolution: Fixed with version 4.4.3.72.
SEP sesam v. 4.4.3.71 – Hyper-V VM restore reports error although successfully executed
  • When restoring a Hyper-V VM, the restore process may report an error message, such as "DB Module: [ [ CHyperVManagementShell::ImportVM: IHyperVManagemenentShell:_ImportVM - System.NullReferenceException: Object reference not set to an instance of an object." However, the import of the VM is actually successful, but an attempt to trace the property of the restored VM may fail.
Resolution: Fixed with version 4.4.3.72.
SEP sesam v. 4.4.3.68–71 – Setting task option Descend directories on other file systems has no effect for newly created or modified backup tasks
  • When creating a new backup task (or modifying an existing task) in v. 4.3.68–70 with the option Descend directories on other file systems enabled, nothing from the underlying file systems (mount points) is backed up due to incorrect setting of DB entry.
Resolution: Fixed with version 4.4.3.72.
SEP sesam v. ≤ 4.4.3.70 – Restoring a Hyper-V VM to the original location might lead to corruption of other VMs
  • When restoring a Hyper-V VM on Windows to the original location which is also used for other VMs, the restore process tries to merge all AVHDX files to their parent VHDX files. This might lead to corruption of all VMs in the same target location.
Workaround: Do not restore any VMs to original location with v. 4.4.3.70; update to a newer version (≥ 4.4.3.71) of SEP sesam.
Resolution: Fixed with version 4.4.3.71.
SEP sesam v. ≤ 4.4.3.70 – IBM Domino backup on Windows ends with a warning
There are 2 known problems with SEP sesam 4.4.3.70 IBM Domino backup on Windows.
  • Problem 1: IBM Domino full backup on Windows with source all may not truncate the transaction log files and backup ends with "The specified transaction log file is not in the list of files to be archived."
  • Problem 2: IBM Domino backup on Windows by using the Exclude List may skip non-excluded items and backup ends with warnings, such as: [6716] DB Module: [finishBackupFile(): file full path [ows] is not valid.] or [6716] Retrieving of standard attributes for item [D:\DData\dbdirman.ntf]: [WIN32 API error: 2 - The system cannot find the file specified. ] failed.
Workaround: Do not use SEP sesam v. 4.4.3.70 for IBM Domino backup on Windows; update to a newer version (≥ 4.4.3.71) of SEP sesam.
Resolution: Fixed with version 4.4.3.71.
SEP sesam v. 4.4.3.60–70 (Univention UCS ≥ 4.3) – Backup on Univention UCS 4.3 and higher may fail due to incomplete SBC logging
  • Running backups on Univention UCS ≥ 4.3 may fail due to a different OpenSSL version that remained linked to SBC. The following error is shown: "SBC logging without final state message."
Fixed: Note that you should only apply the following patch for your Univention UCS ≥ 4.3 (not on Debian or any other Linux distribution) and only if your backups are failing with the above error. The patch is available under https://download.sep.de/servicepacks/4.4.3/4.4.3.64/linux/ucs/ or directly by clicking UCS patch.
SEP sesam v. 4.4.3.70–71 – User-defined calendar configuration is not working
  • With the Beefalo release support for Java 11 was introduced in SEP sesam. Both Oracle Java 11 or OpenJDK 11 no longer include JavaFX. As the user-defined calendar is JavaFX-based, it is no longer working.
Workaround: Use List All Calendars instead. SEP support is working on this issue and will provide a solution with the next version of SEP sesam Beefalo. When using Java 8 the user-defined calendar still works.
SEP sesam v. ≤ 4.4.3.70 – Mounting a backup via VFS does not display the correct content (not all subfolders are shown)
  • When mounting a backup via VFS (virtual file system), the subfolders are not shown due to errors in sm_vfs that result in displaying the wrong content. This problem also applies to Exchange Recovery Pro.
Resolution: Fixed with version 4.4.3.71.
SEP sesam v. 4.4.3.70 – Hyper-V restore from a powered-on VM fails with VSS API error
  • The restore of a Hyper-V backup from a powered-on VM to another Hyper-V server fails with: VSS API error: NHyperV::FindSingleObject: Failed to enumerate objectsClass name is "Msvm_ComputerSystem"
Workaround: You can only restore a Hyper-V VM to another server if the VM is powered off. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. ≥ 4.4.3.xx – NDMP selective restore fails to restore empty directories
  • When performing a selective NDMP restore to restore a directory and its contents and there are also empty directories on the restore list together with normal directories and files, no empty directories are restored (created) on the target.
Known issue: Closed as a known issue as it is too minor to warrant fixing. Will not be fixed in this release.

Feedback

As you come across things that you miss or are not working properly during testing, spot various bugs and issues or have another comment, please send your feedback to beta@sep.de. We will be happy to hear about your overall experience and are looking forward to your suggestions for improvement.

Thank you for your partnership and for devoting your time to SEP sesam beta testing.

See also

Release Notes 4.4.3 BeefaloSEP sesam Release Versions