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.69 – Creating HPE StoreOnce store results in NullPointerException (NPE)
  • Creating the HPE StoreOnce store causes an NPE error that occurs after closing and reopening the GUI; NPE is thrown when clicking the Data Stores in the GUI's Main Selection window.
Workaround: Do not use the Tree view mode for displaying the data stores. Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.69 – Read-only drive is allocated as read/write drive
  • Read-only drive is being periodically incorrectly switched to read/write drive.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.60–69 (≥ 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 Debian or any other system) 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.69 – VMware vSphere FDI restore from StoreOnce Catalyst store fails with error
  • VMware vSphere FDI restore from HPE StoreOnce store fails with "Error: db_write_block: Disk current sector out of range" due to the incorrect file size – caused by the padding bytes added to savesets written into a data store.
Workaround: SEP support is working on this issue and will provide a solution as soon as possible. Please contact SEP sesam support at support@sep.de for assistance.
SEP sesam v. 4.4.3.69 – Changing the HPE StoreOnce store drive properties is not possible
  • Changing the HPE StoreOnce data store drive properties is blocked by a pop-up prompting for specifying a path for the data store, which is not relevant for the HPE StoreOnce store and can therefore not be specified.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.68 – File system consistency check (FSCK) on the SEP Si3 Deduplication store on RDS fails with IOError
  • FSCK on the SEP Si3 Deduplication on SEP sesam RDS does not work due to incorrect return code that causes the IOError: [Errno 0] Error in sm_popen.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.68 – Hyper-V single file restore fails with error when mounting Hyper-V VHDX, while browsing in GUI is still possible
  • Hyper-V single file restore fails with the 102 error, however, no information about the failure is shown in the Mount to device server window while browsing for source is still possible.
Workaround: SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.68 – BSR Pro backup of all volumes fails
  • BSR Pro backup with all volumes selected fails with error "invalid parameter" when trying to backup SystemReserved and C:, D:, E: volumes.
Workaround: SEP support is working on this issue and will provide a fix as soon as possible. Please contact SEP sesam support at support@sep.de for assistance.
SEP sesam v. 4.4.3.68 – SEP sesam GUI Save Layout function does not work correctly
  • When using the Save Layout function, the rearranged layout is not saved and the order and display of tabs is not preserved.
Workaround: Do not use this function until the problem is fixed. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.67 beta – Configuring Hyper-V restore task fails with NPE error
  • When opening the existing Hyper-V restore task and clicking Next or when trying to start a saved restore task by using Immediate start, the operation fails with the NPE error. The problem is caused by not setting the restore option Start / Do not start virtual machine after restore.
Workaround: Manually select one of the following restore options: Start virtual machine after restore or Do not start virtual machine after restore.
SEP sesam v. 4.4.3.67 beta – User-defined calendar configuration is not working
  • SEP sesam user interface is using Java 11 or OpenJDK 11 which does not include JavaFX. As 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 fix with the next version of SEP sesam Beefalo.
SEP sesam v. 4.4.3.67 beta – Hyper-V single file restore from INCR backups fails
  • When trying to restore Hyper-V VM single files from incremental (INCR) backup, the restore job fails with error.
Workaround: You can restore single files from the Hyper-V FULL backups instead, as described in Restoring Hyper-V single files. SEP support is working on this issue and will provide a solution as soon as possible.
SEP sesam v. 4.4.3.67 beta – Mounting a backup via VFS does not display the correct content (no 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.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.67 beta – Wrong warning message during VMware restore
  • VMware restore shows a warning "Set network name '<name>' failed. Network name does not exist on target" even though the network name does exist on the target. In this case, SEP sesam issues a wrong error message, however, restores under these circumstances are successful regardless of the warning.
Workaround: Will be fixed with SEP sesam version 4.4.3.70.
SEP sesam v. 4.4.3.66 – 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.66 – All data store-related actions fail for Path data store on RDS
  • All data store actions, such as purge, checkspace, etc., fail for the Path data store type on RDS with SEP sesam versions < 4.4.3.66 due to the accessibility issues.
Workaround: Update all RDS to SEP sesam version ≥ 4.4.3.69
SEP sesam v. 4.4.3.64 – Automatic update of clients with sm_update_client fails
  • Automatic remote update using the sm_update_client command fails due to files being in use during update.
Workaround: Update SEP sesam clients manually. Will be fixed with SEP sesam version 4.4.3.70.

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