SEP Disaster Recovery and Backup Restore: Best Practices
Who We Are Established, HW Development Development of Logistics SW Logistic Software Relag Develop Backup and Data Protection Software -- VMS (92) Spin Off Logistic SW Backup SW Data Protection and Logistics Patented Processes Development sesam2000 Backup for NT/Unix/Linux Define Linux Strategy Establish SEP Software Inc. Software Only SEP sesam 2000 International Expansion 1980 1990 2000 2010 2
Product Integration Product Integration Application level Hypervisor Bare Metal Online database Modules Operating System / Filesystem 3
SEP sesam Install Sesam Server Main memory 1-2 GB Java 1.6 (Sun, IBM or openjdk) PostgreSQL on 64-bit Linux Sesam VAR area size between 30 and 50 GB or more Depends on the backup and media strategy Storage Hardware On Linux: all SCSI/SAS- and FC-HW direct connected will work On Windows: Manufacturer drivers have to be installed If the hardware is visible to the operating system, Sesam can use it 4
SEP sesam on the Network Local Network Local Disk Tape Library 4 3 Network Disk 2 1 Sesam Server Storage Area Network Virtual Host Web Server Internet File Server Oracle Server Local SAP Server email Server Directory Server Remote Site Remote LTO Drive 5 Sesam RDS email Server File Server 5
Architecture SEP sesam Master GUI SEP sesam Backup Clients VMS OS/2 UNIX NetWare/ OES Network Unlimited Parallel Data Streams SEP sesam Backup Server 6
Architecture SEP sesam Bare System Recovery Restore on Dissimilar Hardware Firewall Network SEP sesam Remote Device Server SEP sesam Backup Client 7
Architecture SEP sesam GUI SEP sesam ONE Server CTRL/VPN or SSH SEP sesam Data Encryption Network Network SEP sesam Backup Clients SEP sesam Backup Client with Remote Device 8
Architecture SEP sesam SAN Option LAN Free Backup DB Server Storage SAN Network Virtual Machines SEP sesam VMware ESX Backup Client ESX Server SAN App. Server SEP sesam Backup Server Storage 9
Backup in Virtual Environments Citrix XENserver Online hot and warm module using the XENserver API Agent-Less Technology VMware vsphere/esx Directly via ESX host VCB-Proxy vstorage APIs for Data Protection (VADP) MS Hyper-V File consistency with VSS Open source Xen Backup using LVM snapshots (RedHat and SuSE KVM scheduled for Nov 2012) 10
Virtual Guest Online Backup Complete Backup Job Pre Processing sbc_pre on Xen host Backup Post Processing sbc_post on Xen host Create LVM Snapshot Mount LVM Snapshot Backup Unmount LVM Snapshot Delete LVM Snapshot 11
Virtual Server Restore Multinode Aware Can Restore to any node in a farm Or to another Virtual Host Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 12
Virtual Server Restore Multinode Aware Can Restore to any node in a farm Or to another Virtual Host Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 13
Virtual Server Restore Multinode Aware Can Restore to any node in a farm Or to another Virtual Host Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 14
Virtual Server Restore Multinode Aware Can Restore to any node in a farm Or to another Virtual Host Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 15
External Backup (e.g., Oracle DB) Manually or Scheduled Command Event Call Script Remote Task with -Name -Type References Taskname Backup on Media Script: -Call RMAN with Sesam Environment - Sesam_Server -Media Pool -Taskname Sesam Server Oracle Server 16
Backup in a Novell Environment Backup over Novell Storage Management Services (SMS) and Target Service Agents (TSA) There is no Sesam client needed for OES NetWare, it uses the TSA The backup server or One OES2 Linux host has to work as Data Mover There must be a valid SLP configuration to backup cluster resources 17
Data Mover Work Principle Data Mover Backup Targets Sesam Client SMDR TSAFS TCP OES Netware TSAFS Sesam Novell Client LAN SMDR OES2 Linux TSAFSGW TSAIF SMDR SMDR TSAFS TSANDS OES2 Linux OES Netware 18
SEP sesam Cloud Backup Solutions Backing up to the Cloud using SEP sesam The SEP sesam backup recovery solution has been certified to work in any cloud environment. It is especially suited for Amazon S3 type Cloud solutions and gives an extremely high level of reliability to anyone who wants to provide cloud based backup to their customers. Basis A standard cloud solution consists of a Standard Server running, currently any Linux O/S and a Cloud Server license installed at the cloud providers location. It is controlled at the customer site, but can also be controlled by the reseller by installing a SEP sesam Cloud Server license 19
SEP sesam Cloud Backup Solutions SEP sesam Cloud Server Technology The Manage Service Provider (MSP) can provide a turn-key backup solution to customers without ever going on site. The system administrator installs software at the customer s site. The customer can have the full software running locally and back-haul important data to the Cloud Provider, or they can simply backup everything to the Cloud. Security Security is provided with AES256 encryption for all data, while logfiles and encryption keys are sent over secure SSH for storing in the Cloud. 20
SEP sesam Cloud Server Technology Add new servers quickly and easily MSP s can add a server to a Group without reconfiguring the new device. Templates are supported in the form of backup groups and can be easily controlled from a central cloud location. Email Notification MSP s can set notifications for themselves or their customers. Notifications include: Backup Successful, Backup Successful with errors, Backup Failed. 21
SEP sesam Cloud Server Technology Upgrades are handled simply and easily. Scripts allow the MSP s to keep their customers at the newest revision of software. Remote Monitoring Using the SEP sesam GUI all functions can be performed remotely from any user authorized to provide system management functions. 22
SEP sesam Cloud Server Technology Easy Installation A cloud solution can be installed in just minutes on customer s computers. Rapid Deployment means Rapid Returns The ease of setup, the low overhead of data transfers, and the rapid response times means that the MSP will see immediate impact on their bottom line. 23
Novell Cluster Services Backup with SEP Backing up Novell Cluster Services using SEP sesam The SEP sesam backup recovery solution has been certified by Novell for use on all platforms. The Novell cluster backup arena is a reliable and important part of the backup solution provided to customers and partners. SEP has more features than our largest competitors: Syncsort, NetBackup, Legato, Tivoli., at a price that compares with BackupExec Basis A Novell cluster consists of several physical cluster nodes, sharing common access to the storage device(s). Services such as iprint, GroupWise and NSS will be referred to as Resources. 24
Backup in Novell Cluster Services GroupWise PO1 File Resource GroupWise PO2 iprint ifolder 2 nd File Resource *2 R1 *2 R2 *2 R3 *2 R4 *2 R5 *2 Rn *3 Node 1 *3 Node 2 *3 Node m SAN SAN *2 = Cluster Resource SAN/Storage *3 = Physical Node 25
Create Tasks Using the SEP sesam GUI the cluster resources will show up under the cluster object 26
SEP Backup using One Server SEP sesam backup server is OES Linux Running Novell services : Novell-sms SEP sesam Server (Data Mover) Running SEP sesam services: Sep sesam Server SEP sesam novell-client (Data mover) SCSI/iSCSI/SAN Backup Storage File Resource GroupWise iprint ifolder *2 R1 *2 R2 *2 R3 *2 R4 *2 R5 *2 Rn *3 Node 1 *3 Node 2 *3 Node m Running Novell services on each cluster node: TSAFS, TSAGWFS, TSAIF, TSANDS, and novell-smdrd Running SEP sesam services: Sep sesam client *2 = Cluster Resource *3 = Physical Node SAN/Storage = LAN = SAN = Meta data = Backup data Data Traffic: R n over internal network protocol to Node m From Node m (TSA) over novell-sms to SEP sesam server novell-smdrd = Storage Connection 27
SEP Backup using Windows Running Novell services on OES-Linux: Novell-sms SEP sesam Data Mover OES SEP sesam Server Windows Running SEP sesam services: Sep sesam Server SEP sesam novell-client (Data mover) SCSI/iSCSI/SAN Backup Storage File Resource GroupWise iprint ifolder *2 R1 *2 R2 *2 R3 *2 R4 *2 R5 *2 Rn Running Novell services on SEP sesam Server: Running SEP sesam services: SEP sesam advanced Server Windows *3 Node 1 *3 Node 2 *3 Node m Running Novell services on each cluster node: TSAFS, TSAGWFS, TSAIF, TSANDS, and novell-smdrd Running SEP sesam services: SEP sesam client *2 = Cluster Resource *3 = Physical Node SAN/Storage = LAN = SAN = Storage Connection = Meta data = Backup data Data Traffic: R n over internal network protocol to Node m From Node m (TSA) over novell-sms to SEP sesam server novell-smdrd. From SEP sesam data mover over SEP sesam stp protocol to SEP sesam Server. 28
LAN Free Backup Remove backup traffic from the main network with SEP sesam backing up a Novell cluster to a SAN disk or tape Gain performance advantages on the network by removing backup traffic and increase backup performance by backing up with SAN speeds This can all be done on a Novell cluster (or other SAN attached nodes) by using the SEP sesam SAN Remote Device module. 29
LAN Free Backup SEP sesam backup server can be Linux or Windows the data mover and RDS is installed on the cluster nodes. SEP sesam Server (Data Mover) SCSI/iSCSI/SAN Backup Storage File Resource GroupWise iprint ifolder *2 R1 *2 R2 *2 R3 *2 R4 *2 R5 *2 Rn *3 Node 1 *3 Node 2 *3 Node m Running Novell services on each cluster node: TSAFS, TSAGWFS, TSAIF, TSANDS, and novell-smdrd Running SEP sesam services: Sep sesam client *2 = Cluster Resource *3 = Physical Node SAN/Storage = LAN = SAN = Meta data = Backup data Data Traffic: R n over internal network protocol to Node m From Node m (TSA) over novell-sms to SEP sesam server novell-smdrd = Storage Connection 30
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. Novell, Inc. may make improvements in or changes to the software described in this document at any time. Copyright 2011 Novell, Inc. All rights reserved. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.