SEP sesam BSR 2.3
Copyright © SEP AG 1999-2015. 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.
- 1 Introduction
- 2 System Requirements
- 3 Installing the SEP sesam Client
- 4 Installing SEP BSR
- 5 CBMR Driver validation
- 6 Configuring a SEP BSR Backup
- 7 Disaster Recovery and Restore with SEP BSR
- 8 Booting BSR with USB
- 9 Known Issues
- 10 Troubleshooting
- 11 Further Links/Literature
To perform a Bare Metal backup additional Software must be installed on the Server system (Sesam BSR). After installation the configuration, scheduling of the backups and processing is performed centralized by the Sesam Server (via GUI). BSR backups only the system partition and Active Directory to grant a higher flexibility for DR restore. To perform a consistent disaster restore of Servers with active databases (like Exchange, SharePoint, MS-SQL e.g.) further steps are necessary, therefore also an statement from Cristie: http://support.cristie.com/cgi-bin/kb.cgi?do=read&id=127&lang=en
Steps to prepare a Windows Database-Server (Exchange, MS-SQL, SharePoint etc.) for a Disaster-Recovery:
- BSR-Backup of the system partition
- if applicable path-backup of further partitions without the databases
- ONLINE backup of all databases with the corresponding backup modules
Therefore the restore has to be performed in this order:
- BSR-Recovery of the system partition
- Restore of other partitions
- Restore and recovery of the databases
- Supported Versions
- SEP sesam Server Version 220.127.116.11 or later
- SEP sesam Client Version 18.104.22.168 or later
- SEP BSR Windows CD from Version 2.3 with Windows Kernel x86_64 and x86_32
- A fully functional DNS Server
- Before starting SEP BSR Windows you must perform a 'Driver Control' operation to determine required drivers for the recoverable system. This is described in the CBMR Driver validation section.
Installing the SEP sesam Client
- A fully installed and functional SEP sesam Client for Windows is required before using SEP BSR Windows extension. The installation package can be found here.
Installing SEP BSR
- Insert the SEP sesam BSR Disk into the CD drive of the system where the Disaster Recovery mode will be used.
SEP BSR software can be downloaded from here (just extract the ISO image for client installation and burn it on a CD in case of a restore)
The 'Installation Program' should start automatically. If the program does not start automatically please use the command:
AUTORUN.EXE and select CBMR.
Next, please select the required installation (i.e. Server or Desktop) and choose OK. Now select the full Installation along with Standard Configuration.
During the Installation you should not change any settings in the dialogue boxes. Also when the program prompts you for the User Account, this should be left empty.
- Answer the question after the start of the CBMR Schedulers with "YES" and click Continue.
- The installation path can be set depending on your system environment. The installation will not require more than 30 MB of disk space.
- After the successful installation you must copy the license file data from SEP Software Inc. purchased license from the Basis Directory to SEP BSR, e.g. C:\Program Files\Cristie\CBMR thus overwriting the demo license file.
- After the installation of SEP BSR you must start the CBMR program. Use either the Desktop symbol CBMR or the command: Start>Programme>Cristie>CBMR and confirm with OK. Then click on Configuration and open Backup Locations and close the program.
CBMR Driver validation
After the installation of SEP BSR it is absolutely necessary to systematically follow the next steps to insure an error-free restore of the system environment and backed up data.
This test should be carried out per server model. It takes about 5 minutes per system. (Preferred way)
- Boot server with the latest BSR PE CD
- Testing of network card and storage controller
- Storage Controller:
- Command Line to open by pressing ALT + S in the main menu
- Run Diskpart
- Run the diskpart prompt, type "list disk"
- Now, when the existing disc is displayed, the Storage Controller supports the recovery
- Network card:
- On the Tools menu, go to "Configure the network"
- There via DHCP or manually assign an IP
- Change to the still open command line and a "ping" settle on another server on the network.
- If another server responds on the network, the Supported network card for recovery
- Storage Controller:
- If the Network tool cannot be opened or the hard disk not be detected, missing the temporary driver for the recovery on the BSR PE CD. This can be from the Tools menu and point "Load a driver" will be loaded. The driver can be loaded for example by USB stick or from a network share. The current PE CD is based on the Vista SP1 x86 kernel and therefore should the temporary lack of drivers for Windows Server 2003 x86 be recharged. In some cases, a Windows Server 2008 x86 driver fit. If the drivers are loaded successfully could, the disc should be recognized or the network tool leave open. Please send us the driver reloaded at firstname.lastname@example.org, so we build it into the next version can.
An alternative way, run the included program Driver validation found in the directory Programme\cristie, which was installed with the previous procedure.
In this screenshot several Hardware Components have been included under one Yellow Dot. The Yellow Dots indicate that drivers have been included in the BSR Boot-CD. In case of a Red Dot appears it is up to the system administrator to determine if the missing driver is required for a successful disaster recovery. If the 'Red Dot' indicates a Network I/F Card or a Disk/SATA/Raid Controller special action should be taken. If a Data Restore is performed without first testing the manual Driver Installation the restore is not covered under warranty or guaranteed. It is possible as in a normal Window's Installation using the Install CD to install these drivers using "F6" during the bootup operation. To assure that this report has been technically verified, SEP offers the opportunity to create a logfile using the switch Create Driver Info. Attach the relevant customer information and date and label "SEP AG" and forward it to email@example.com and copy 'CC' firstname.lastname@example.org. Our partner Cristie will issue a technical statement regarding this event.
Configuring a SEP BSR Backup
As a starting point it is important to consider the following: The Backup is started as in every SEP sesam backup, on the Server. It can be included under a Group and in the scheduler (SEPuler) and can be performed within the standard backup routines.
Configuring a BSR Task using the SEP Sesam GUI
- Include the target backup client as O/S Type: Windows
- In the event the client lies within a fire walled DMZ you must select the necessary firewall option in the GUI
- Create a Test File Backup (e.g. from C:\temp) to assure the validity of the client backup task
- Now, set up the SEP BSR task
Within the SEP sesam GUI under the Menu Tasks/Clients you must select SEP BSR Client and create a new task.
Disaster Recovery and Restore with SEP BSR
To begin the Disaster Recovery process the SEP BSR CD must be inserted and the server must be configured to boot from DVD/CD drive. After booting, the Welcome screen from Cristie will appear.
After the successful boot up procedure follow the subsequent directions.
- The Restore is started by clicking the "Recovery Manager" Button.
- Skip the next Window by clicking "next".
- In the next menu (see Picture) you will need to select the backup location and configure it within the network>
- Using the Button "Network setup" you will be able to set up the IP Configuration at "IP Addresses". In this location you will enter the IP Address of the recovered Server, this is used in the event there is no DHCP Server.
- If there is a DHCP Server, you should enter the correct host name and the subsequent set in the last section "Network Identification" .
- If there is no DHCP Server all additional data should be entered correctly in these fields.
- All these Settings must be confirmed by selecting 'Apply' and checking 'OK' when prompted.
- After confirming all Network settings you will return to the next menu window. Select here the first choice "Stored with the backup data".
- Hit "next" and in the next menu and "SEP sesam Location".
- Select "next" and click "create new" and enter the settings as they are in the next screenshot.
Name: Hostname for the backed up Computer SESAM Servername: Hostname of the SEP sesam Server SESAM Task: SEP Sesam Taskname of the BSR Backup. (Note: Case Sensitive!) Mediapool: Name of the SEP sesam configured Mediapools (Case Sensitive!)
- Click "OK" to verify input. With the newly created location and "Next" you will come to the selection of the available SEP sesam backups.
- Select the desired backups continue by clicking "Next".
Now the BSR client will select "SM_STPD" or "System Information" prepared via the SEP sesam. Using this function allows the user to select all partitions required from within the chosen backup. With one right click on the partition in the window on the right you have the possibility to select a further option format or do not format. The disk size and partitions can be adapted also.
- If different hardware is used, the Plug and Play Manager detects this and asks in the next step for the appropriate path for the driver. If the drivers are on a network path, this path can be mounted via the Network Setup. If the drivers are just not yet available, this step can be skipped and be started manually after the restore.
- In the next step the chosen partitions will be formatted and prepared for restore to the server.
- After partitioning all data from the SEP sesam Server is transferred using the SEP sesam STPD Protocol to the BSR client (Disaster Recovery Target!).
- Close the status window after successful restore.
Before the first reboot a driver validation must be performed.
- The required Reboot may now be selected from the Main Menu.
In the event that a new activation of the operating systems is required it is possible that a hardware device has been changed.
If you have any restore issues or problems please contact us at email@example.com
Additionally, if you have any problems with or recommendations for our documentation and procedures please report them to firstname.lastname@example.org
Booting BSR with USB
Instructions to make a bootable USB stick for BSR
1 Open CMD and use diskpart on a Windows Vista or newer operating system.
a Select "List Disk" to enter the number of the USB stick (example: 1)
b. Sel disk 1 (number of USB stick) (Disc 1) Select
c. Clean (disk clean up)
d create par primary (primary partition on disk 1 create)
e sel par 1 (partition 1) Select
f act (as Active)
g format fs = fat32 (format partition to FAT32 )
h Assign (to assign a drive letter, happens automatically)
i Exit (Exit)
a extract the BSR ISO file to a temporary folder, for example C: \ BSR
b. xcopy C:\ BSR \*.* F:\*.* /s (example: When BSR/WINPE installation files are in C:\BSR and the purified bootable flash drive is the drive letter F:)
- Backup to media pool with more than 15 characters does not work. This issue is related to Cristie and we're waiting for a solution of Cristie (created Nov 12 2013).
Starting a CMD for debugging purposes
While being in the BSR Live CD Main Menu it is possible to start a command Line box using the key combination "ALT"+"S". It allows you to check your network configuration by using the proper tools like ping or nslookup.
Currently unsupported hardware
- Systems with UEFI 'Bios'
Unable to load BackupManager, code = 40002037
This Error appears if no Cristie licence is inserted.
- A BSR Backup stops with the following error message
Error: Operation failed:
--> source the sesam profile on the SEP sesam Server and type in the following command
sm_db "INSERT INTO defaults (key,user_name,value,host,protection) VALUES ('bsr_task_result_limit','sesam','30',NULL,NULL)"