BSR Pro for Windows Troubleshooting

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2019. 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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo. For previous documentation version(s), check documentation archive.

BSR Pro for Windows

BSR Pro backup fails due to snapshot backup issue


  • BSR Pro backup fails with BSR Pro unknown return code (0X1).

Cause 1

  • On some Windows OS (mainly Windows Server 2008 [R2]) this error could happen due to problems when checking the areas that are not to be compressed.


  • Fixed with version BSR Pro 3.3.185 (released in SEP sesam v. Grolar).

Cause 2

  • On some Windows OS (Windows 2003, Windows Server 2008 and Windows Server 2012) you may receive a "volsnap" error in the Windows Event log: Event ID 25: The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied. This error indicates that the source drive is experiencing a high IO load, which caused VSS to fail and deleted the shadow copy snapshot, as a result causing a BSR Pro backup failure.


  • You have to reduce the IO load on the drive being backed up or configure VSS to use a different drive with more available space (and less load) and ensure that there is sufficient storage space to create and maintain shadow copies. You may want to allocate a separate volume on a separate disk for storing shadow copies, as recommended by Microsoft, to improve performance and eliminate the possibility to delete the shadow copies due to a high I/O load. For details, see Volume Shadow Copy Volsnap Event 25. See also the following Microsoft article: Event ID 25 — Diff Area Integrity

No savesets nor clients exist in SEP sesam after clicking Execute BSR Pro Quick-Start option


  • The list of available save sets at the SEP sesam Server remains empty.

Possible cause

This error typically occurs when the connection to the SEP sesam Server cannot be established due to any of the following:

  1. Problem with name resolution: SEP sesam Server hostname is not known to client, name to IP and IP to name (reverse) resolution is not correct.
  2. The client's name (typically a new host is set up in case of disaster recovery with new IP) cannot be resolved at the SEP sesam Server.
  3. Wrong server name (a fully qualified domain name (FQDN) may be required).
  4. When booting from PE, it may take a little longer until the savesets appear (30-45 seconds).


  1. Check your name resolution on client and SEP sesam Server. Both names must be resolved, the client IP must be resolved to the client name, and SEP sesam Server must be reachable (check the route to it – FQDN may be required to reach it). For reference, see How to check DNS configuration. If the resolution in your network does not work as expected, there might be issues with IPv6 and IPv4.
  2. Add the client's name to the name resolver or add it to the /etc/hosts on SEP sesam Server, or use the GLBV gv_stpd_auth NONE to disable the IP name to IP address check on SEP sesam Server; in the latter case, open a shell on the SEP sesam Server and execute the command below. This command enables you to contact the SEP sesam Server even if the reverse name resolution does not work on the new client.
  3. sm_glbv w gv_stpd_auth NONE
  4. Specify the SEP sesam Server with the FQDN. Open the BSR Pro Settings -> tab Security and in the Authentication table check the settings. Under the Network path/server, a valid sesam:{server} name or interface must be specified.
  5. Examples:

    Network path/server                      Port
    sesam:   11000
    sesam:sep_server2                        11001
    Information sign.png Note
    Only the first entry is used to fill the list of available savesets!

OODIAG cores while creating BootISO (Sesam Grolar - BSR Pro v185)


  • If you try to create a boot ISO with the BSR Pro on a system where the volumes are dynamic volumes, then the OODIAG service cored under certain circumstances.

Possible cause

  • Problem is apparently the system volume. Possibly it is related to the dynamic volume.


  • Maybe it works with a newer version like Beefalo or newer (BSR PRO version should be equal or newer than 14.2.378)
  • If possible, no dynamic volumes should be used.

VSS snapshot for the system volume does not work


  • Typically, VSS is used by default to log changes in data so that unchanged data is included in the backup. But on some systems the VSS snapshot for the system volume does not work.


  • Start SEP sesam BSR Pro (valid for versions ≥ BSR Pro 2.0) with the option -a snap=snapshot. This option creates a special snapshot that does not involve the Microsoft VSS Writer: data changes are logged using the installed filter driver to include the unchanged data in the backup.
  • Usage: -a snap=vss|snapshot
    where <vss> is default

It is not possible to get the error-log for a failed restore in a PE


  • Disk full while accessing X: because dump is written to it.

Possible cause

  • The LOG becomes too large because it is written on continuously.


  • Open the registry in the command shell by using regedit.
  • Add the following reg-key:
  • [HKEY_LOCAL_MACHINE\SOFTWARE\O&O\O&O DiskImage\<version>]
  • After the change the LOG is written to the path E:\DUMPS.

See also

VSS TroubleshootingSEP sesam BSR Pro for Windows