Hints for beta testing

From SEPsesam
Jump to: navigation, search
Information sign.png Note

SEP sesam provides SEP sesam 4.4.3 Beefalo V2 beta version as a test program. This means that 4.4.3 Beefalo V2 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 V2 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 V2. 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 V2 known issues:
SEP sesam v.–79 – (Windows) A data block is not written to tape when EOM is reached together with the segment size, thus making a restore of data referencing this block impossible
  • (Applies only to Windows) When backing up to tape, a data block is not written to tape when the segment size is reached at EOM, therefore a restore of data referencing this block is not possible. While a Path Archive can still be restored until EOM is reached, a complete restore or migration will fail.
Resolution: Fixed with the patch for Beefalo V2, contact SEP sesam support at support@sep.de for assistance.
SEP sesam v. – Loader assignment of sayFUSE drive gets lost after drive configuration
  • After updating a SEP sesam Server where sayFUSE drives are configured, these drives lose the assignment to their virtual loader during drive configuration.
Workaround: SEP is working on this issue and will provide a solution as soon as possible. Do not update or install SEP sesam version (Beefalo V2) in case sayFUSE drives are configured until this issue is solved.
SEP sesam v. – SEP sesam update of a SLES 11 ≤ SP2 client may fail
  • When updating a client with SLES 11 SP2 (or lower) by using the command rpm -U <package name>, the update may fail due to the new signature of the RPM packages. This is a version related issue and does not occur with ≥ SLES11 SP3.
Workaround: Update your SLES 11 SP2 (or lower) client with the command rpm -U --nosignature <sesam package>
SEP sesam v. – SEP sesam installation and update on Windows Server 2012 R2 may fail
  • On some Windows Server 2012 R2 the SEP sesam software cannot be started due to problems while reading output from sub processes.
Workaround: SEP support is working on this issue. Do not update or install SEP sesam version (Beefalo V2) for SEP sesam Server or RDS until this issue is solved.
SEP sesam v. – Backing up Citrix Hypervisor 8.1 might result in error "Unable to create a snapshot [['MESSAGE_REMOVED']]"
  • As creating quiesced snapshots is no longer supported in Citrix Hypervisor ≥ 8.1 and in the version ≥ 9.0.x.x drivers, running hot backups in combination with the COPY backup level results in the above error.
Workaround 1: The SEP sesam version Grolar is not affected by this problem. It is still possible to use a SEP sesam Client as data mover if the SEP sesam software hasn't been upgraded to the Beefalo release yet.
Workaround 2: If you can afford the downtime of your affected virtual machines, you can change the settings from hot backup to cold backup as no snapshot creation is needed in this case.
Workaround 3: If your license allows the use of the CBT feature in Citrix Hypervisor, back up your virtual machines with the FULL/DIFF/INCR backup level instead of COPY.
SEP sesam v. – Cancelling a Citrix XEN backup task does not abort the backup execution
  • Aborting a Citrix Xen backup task does not prevent the backup job from running as SEP sesam does not pass a cancel request to the running sbc_proxy and sbc process. Therefore the backup process will be running without interruption. Be aware that killing the sbc_proxy or sbc process manually will keep the snapshots; in this case, snapshots must be released manually.
Workaround: Only if you have aborted Citrix XEN backups manually by killing the sbc_proxy or sbc process, don't forget to release these snapshots as they are not managed by SEP sesam automatically. SEP is working on this issue and will provide a fix as soon as possible.
SEP sesam v. – The new Install/Update feature might not work as expected 
  • The newly introduced SEP sesam software update feature might not work as expected, e.g., it may not perform the automatic updates during SEP sesam NEWDAY as selected in the update mode.
Workaround: Control your updates manually.
Resolution: Fixed with version
SEP sesam v. ≤ – VMware VM backups might fail due to a new vCenter Server version: 6.7 Update 3b
  • Due to a change in the VMware latest vCenter 6.7 Update 3b (, no VM backups can be performed by SEP sesam. This applies to all SEP sesam versions.
Workaround: Add the the exclude keyword ALL to the exclude list of the affected vmware VM task. If one or more VMDKs are already excluded, add the value separated by a comma (without spaces) at the end, for example: [vmstore] myVM/myVM_1.vmdk,ALL. For details, see VMware Backup - Creating a backup task.
Resolution: Fixed with version
SEP sesam v. – Windows Client major update may lead to problems
  • Installing SEP sesam BSR Pro for Windows together with SEP sesam during a major update requires a chained installation, which may lead to problems. A chained installation is not supported during a major update. Thus it is not possible to perform a major update when SEP sesam BSR Pro for Windows is being installed/updated at the same time.
Resolution: Fixed with version; major update is now supported without limitations. Make sure to install the Beefalo V2 update since it is a prerequisite for future major updates. See also About Installation and Update.
SEP sesam v. – Hyper-V backup on cluster resource may fail
  • When performing a Hyper-V backup on cluster resource, the hosting Hyper-V server may not be retrieved and backup fails with Failed to get Virtual Machine ID.
Workaround: Perform Hyper-V virtual machine backup on the serving Hyper-V server node.
Resolution: Fixed with version
SEP sesam v. – BSR restore on Windows from a bootable image does not work when the boot image is created on the GUI installation on D:
  • 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.


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 Beefalo V2SEP sesam Release Versions