SEP Disaster Recovery and Backup Restore: Best Practices

Size: px

Start display at page:

Download "SEP Disaster Recovery and Backup Restore: Best Practices"

Steven Stewart
8 years ago
Views:

1 SEP Disaster Recovery and Backup Restore: Best Practices Shane Brown Snr. Technical Support Manager (USA) SEP Software Inc. / sb@sepusa.com Lanai Bayne VP of Business Development SEP Software Inc. / lb@sepusa.com

2 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 SEP sesam 2000 Establish SEP Software Inc. Software Only International Expansion

Logistics Patented Processes Development sesam2000 Backup for NT/Unix/Linux Define Linux Strategy

3 Hypervisor Bare Metal Product Integration Product Integration Application level Online database Modules Operating System / Filesystem 3

4 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

Depends on the backup and media strategy Storage Hardware On Linux: all SCSI/SAS- and FC-HW direct

5 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 Server Directory Server Remote Site Remote LTO Drive 5 Sesam RDS Server File Server 5

Server Internet File Server Oracle Server Local SAP Server email Server

6 SEP sesam Backup Clients Architecture SEP sesam Master GUI VMS UNIX Unlimited Parallel Data Streams Network OS/2 NetWare/ OES SEP sesam Backup Server 6

7 SEP sesam Bare System Recovery Architecture SEP sesam Remote Device Server Network Restore on Dissimilar Hardware SEP sesam Backup Client 7

8 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

9 SEP sesam SAN Option LAN Free Backup Virtual Machines ESX Server Architecture DB Server Storage SAN Network SEP sesam VMware ESX Backup Client SAN App. Server SEP sesam Backup Server Storage 9

10 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 10

Directly via ESX host VCB-Proxy vstorage APIs for Data Protection (VADP)

11 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

sbc_post on Xen host Create LVM Snapshot Mount LVM

12 Virtual Server Restore Multinode Aware SEP sesam Backup Server looks at the cluster and will talk to all the hosts and determine where the guest is for the backup Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 12

where the guest is for the backup Virtual Cluster Shared Storage

13 Virtual Server Restore Multinode Aware After the backup is found, the communication stream will be isolated to the correct host Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 13

correct host Virtual Cluster Shared Storage Virtual Host

14 Virtual Server Restore Multinode Aware A host can be specified to direct the restore to a specific location Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 14

Virtual Cluster Shared Storage Virtual Host Hypervisor

15 Virtual Server Restore Multinode Aware SEP sesam can be used to keep virtual guests synchronized between hosts or virtual clusters This can be used with the remote device server to synchronize servers between locations Virtual Cluster Shared Storage Virtual Host Hypervisor 1 Virtual Host Hypervisor 2 SEP sesam Backup Server 15

remote device server to synchronize servers between locations Virtual Cluster

16 Backup Oracle Environments Oracle Database, Tablespace and Data File level Backup and Restores XML Archiving Capable of arching Oracle in XML format Wizard based configuration 16

17 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 SEP sesam Backup Server Oracle Server 17

Task with - Name - Type References Taskname Backup on Media Script:

18 Backup in SQL Environments Microsoft SQL Uses standard Windows Agent to support Full Copy, Differential and Incremental backups VSS aware Point in Time Restore Cross Restore of Databases into one another or another instance Log backups can be done with or without truncate options 18

Point in Time Restore Cross Restore of Databases into one another or

19 Backup in SAP Environments SAP software Close partner Working together for over 15 years Highest level of certification of any third party vender Off Host Backup Supports other SAP R/3 Applications: Oracle DB on SUN, Oracle DB on Reliant Unix, Oracle DB on Tru64, MaxDB on AIX, MaxDB on Windows 2003 &

Host Backup Supports other SAP R/3 Applications: Oracle DB on SUN, Oracle DB

20 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 20

NetWare, it uses the TSA The backup server or One OES2 Linux host has to work

21 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 21

22 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. 22

23 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 23

24 Create Tasks Using the SEP sesam GUI the cluster resources will show up under the cluster object 24

SEP Backup using One Server SEP sesam backup server is OES Linux Running Novell services : Novell-sms Running SEP sesam services: Sep sesam Server SEP sesam novell-client (Data mover) SEP sesam

25 SEP Backup using One Server SEP sesam backup server is OES Linux Running Novell services : Novell-sms Running SEP sesam services: Sep sesam Server SEP sesam novell-client (Data mover) SEP sesam Server (Data Mover) SCSI/iSCSI/SAN Backup Storage GWise PO1 File Resource GWise 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 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 25

26 SEP Backup using Windows Running Novell services on OES-Linux: Novell-sms Running SEP sesam services: Sep sesam Server SEP sesam novell-client (Data mover) SEP sesam Data Mover OES SEP sesam Server Windows SCSI/iSCSI/SAN Backup Storage GWise PO1 File Resource GroupWise iprint ifolder *2 R1 *2 R2 *2 R3 *2 R4 *2 R5 *2 Rn 2 nd File Resource 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. 26

27 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. 27

28 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 (Windows or Linux) GWise PO1 File Resource GWise PO2 iprint ifolder 2 nd File Resource *2 R1 *2 R2 *2 R3 *2 R4 *2 R5 *2 Rn Backup Storage *3 Node 1 *3 Node 2 *3 Node m SAN/Storage Running Novell services on each cluster node: TSAFS, TSAGWFS, TSAIF, TSANDS, and novellsmdrd Running SEP sesam services: Sep sesam Remote Device Server SEP sesam novell-client (Data mover) *2 = Cluster Resource *3 = Physical Node = 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 local novellsmdrd to SAN attached Storage 28

29 Question and Answer

30 Thank you. 30

31 Corporate Headquarters 1800 South, Novell Place Provo, Utah (Worldwide) (Toll-free) Join us on: 31

32 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.

SEP Disaster Recovery and Backup Restore: Best

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)