OmniBack II 4.0 News Subject to be changed without notice Nsmdnt3.bbn.hp.com:\\public\omniback\projects\OB40-Mambo\Slides\OB40-Functionality15.

$Page 1: OmniBack II 4.0 News Subject to be changed without notice Nsmdnt3.bbn.hp.com:\\public\omniback\projects\OB40-Mambo\Slides\OB40-Functionality15.$
OmniBack II 4.0 News

Subject to be changed without notice

Nsmdnt3.bbn.hp.com:\\public\omniback\projects\OB40-Mambo\Slides\OB40-Functionality15

2


Newest Features of OmniBack II 4.0

• Significantly improved internal database scalability & performance

• One unified GUI across all platforms (Windows, HP-UX)

• NDMP support for direct disk-to-tape backup (Netapp) • Integration with EMC Fastrax • Open File Manager for Windows2000 / NT and

NetWare • HP SureStore XP split-mirror solutions for Solaris and

Windows2000 • Support for MS Exchange 2000 incl Single Mailbox

Restore • Support for new devices: SuperDLT, LTO Ultrium

3


IDB - Internal Database Benefits• Breakthrough Scalability

– Single point control for many more systems– Keep catalog data of many million files and many backup session for convenient restore

browsing for a long time• Much higher Performance

– Less CPU load, higher insertion rate, less disk IO– Many more systems / disks can be backed up in parallel while tracking the catalog data for convenient

restore browsing.

• Close to Maintenance free– Very low IDB administration effort (in average start purge once per year)– Very low system load for IDB maintenance

• High reliability & robustness– Convenient restores at any time – Backups on tapes are never doomed to bit garbage– Administrators can sleep well

• Easy Disaster Recovery– Even in case of a disaster the IDB can be restored to the point in time of the disaster

• Automated “on-line” migration– Easy migration from OmniBack II 3.x to 4.0

4


OmniBack II 3.x Internal Database

Media ManagementDB:•devices•libraries•media pools

Catalog DB:•objects (hostnames, mount-points, DB)•sessions & messages•directory names•file names - 10% space consumption

•file versions= more than 80%space consumptionMax.: 8 GB= 138 Mio

5


OmniBack II 4.0 Internal Database

Media ManagementDB:•devices•libraries•media pools

Catalog DB:•objects (hostnames, mount-points, DB)•directory names•file names

Flat files for:•File versions•Session logging

Backup Slide

6


Database Design ChangesOmniBack II 3.x versus 4.x

How topurge

expiredversionsfrom DB

OB 3.xVelocis DB

File“A”

Vers.1

Vers.3

Vers.2

File“B”

Vers.1

Vers.3

Vers.2

Fileversionsin oneflat file

permedia

OB 4.xVelocisDB

File“A”

Vers.1

Vers.3

Vers.2

File“B”

Vers.1

Vers.3

Vers.2

7


Database - The Solution DetailsFile“A”

File“B”

VelocisDB Fast Purge

Just to free somedisk space

DELETE

Backup Slide

Media 3

Attributes(18 bytes per row)

Directory indexingFilename indexing

Media 1





Media 2



“A”

1 32

“B”

1 32

8


OB 4.0 Database - Strengths• Scalability

– Number of file versions scales 7 times higher than OmniBack II 3.x (maximum tested configuration)

– 20 million file-names and 1 billion file-versions can be stored in the Internal Database (maximum tested and supported configuration, not a real hard limitation)

– Significant less disk space required (now 24 bytes per file version compared to 64 bytes)

– IDB can be distributed over multiple mount points / disks -> higher performance

• Higher performance– About 5 times faster writing to the Internal Database during backup allows 5 times

more backup drives to be used in parallel– Cell Manager CPU load reduced by 90%– Significantly Faster Media Import (30 minutes to 1 hour instead of 5 hours (DLT 7000) for catalog details

import of all objects from a full media)

• Less maintenance– File version purge in seconds instead of hours

9


OB 4.0 Internal Database - Strengths are caused by

• Robustness & Transaction Logging – Semi-Automatic Complete IDB Disaster Recovery

• Quick internal database (IDB) consistency check before IDB backup• Replay transaction logs of objects since the last IDB backup

– Out of space handling

• Purge– File version purge frees disk space– File version purge (delete the media file [one file per media] in one step) ->

seconds instead of hours– No database fragmentation caused by file version purge

• Fewer pointers– No Velocis database inherent forward and backward links for file versions– About 38 bytes pointer information saved per file version– Less IO -> More backup sessions in parallel are possible.

10


OB 4.0 Database - Drawback• Slight drop in restore browsing performance

– However, the user can specify a search time interval which will make it faster

• Slight drop in search filenames performance– However, the user can specify a search time interval which will

make it faster

• Cellmanager needs more memory– Min 256MB, Recommended is 512 MB.

• Adoption of many IDB utilities for file versions required– Important IDB maintenance tools need to be re-engineered

• IDB migration required

11


OB 4.0 Database - Stress Free Migration from 3.x to 4.0

• Semi-automatic / guided migration process

• Only 30 to 60 minutes OmniBack II downtime required

• About 15 hours for a 6 GB DB on-line (background) migration with OmniBack II up and running.

12


Database - 3.x versus 4.0OmniBack II 3.x OmniBack II 4.0

Number of file versions 138 Mio8GB

1,000 Mio32 GB

Number of files on UX-CM 74 Mio4 GB

150 Mio8 GB

Number of files on NT-CM 53 Mio4 GB

110 Mio8 GB

Number of recommendedbackup sessions in parallelfor midrange systems usingthe “log_all” option

10 Min. 20,High (want) 40

File name search performance reference a little slower thanreference

File name write performance(66bytes)

900,000 per hour Better than 3.x

File version wrt. performance 1,400,000 per hr 7,000,000 per hr

Database transaction CPUload during backup

reference 10% of ref

Number of backup driveswhich can be used in parallelfor backup

ref 400% of ref

Note: NT ref sys: HP NetServer LPr Pentium II, 400MHz, 256 MB RAM, 2 Seagate ST318275LW SCSI disks UX ref sys: HP 9000 R-Class R380, 1 way PA 8000, 64 bit, 180 MHz, 256 MB RAM, 2 Seagate ST318275LW UW2 SCSI disks

13


Database - 3.x versus 4.0Database purge

OmniBack II 3.x OmniBack II 4.0Purge time 500,000 file versions

per hourna

Fast Purge - purge of fileversion attributes

na 500,000 file versions in lessthan one minute

Disk space freed by purge None Yes, file version attributes(24 bytes per file version)

Purge progress indicator None YesFilename purge frequency Daily Yearly

File name purge needs to bestarted manually after

OmniBack II provides anotification

File version purge Yes, daily File version purge on the fly.Purge report Yes YesPurge in parallel to backup No No

14


Database - 3.x versus 4.0Database de-fragmentation

OmniBack II 3.x OmniBack II 4.0Database de-fragmentationand free disk-space tool

Yes, Write-ASCII –Read-ASCII

Yes, Writedb –Readdb

Required de-fragmentationfrequency

Few time a year No real need

Database check - DBCHECKDefault Quick DBCHECKtime for a 8 GB DBRead everything, checkconnections forobjects, session and mediaonly

1 to 5 hours 0.5 to 2.5 hoursno file versions read, however

checks presence and size offile version files

Complete DBCHECKfor a 8 GB DB (same asQuick DBCHECK plus:check connections for fileversions, file names, andmessages

10 to 80 hours 2 to 10 hours

DBCHECK progressindicator

None No, however estimatedmaximum expected duration,

start time, and activityindicator

DBCHECK automation Yes, quick DBCHECKbefore each database

backup

Yes, quick DBCHECK beforeeach database backup

15


Media Management

• Free media pools– Sharing of free media between multiple media pools (of the same type)

– Less operator intervention required

• Improved eject from libraries– Scheduled eject based on media reports– Queue in case more media to eject than free mail slots available

SAP Pool (DLT) Exchange Pool (DLT) PC Backup (DLT)

Free Pool (DLT)(free, unprotected media)

allocation

deallocation allo

catio

n

allo

catio

n

deal

loca

tion

16


Microsoft Windows 2000• On-line backup for

– Microsoft Exchange Server 2000 (Platinum)including single mailbox restore (based on brick backup)

– Microsoft SQL Server 2000– SAP R/3– Oracle 8, 8i– Lotus Notes/Domino 5 (via new backup API ????)

• Cluster backup– File system– Microsoft Exchange Server 2000– Microsoft SQL Server 2000

• More supported HP XP256 configurations• Image & split mirror backup

– Win 2000 NTFS5,– Solaris UFS, VxFS

– Win 2000 mount points

• Windows 2000 certification– MSI package to leverage Windows 2000 software distribution– Windows Data Center

17


Microsoft Exchange Server Backup

• Single mailbox restore• Single restore of individual objects:

– Mail including attributes and attachments– Calendar– Tasks– Notes

• Exchange MAPI based brick backup for single mailbox and single object restore

• Full and incremental? brick backup• Exchange backup API based backup

for fast mail server disaster recovery

(about 8 times faster than brick backup & restore)

• Windows NT 4.0 and Windows 2000

18


HP-UX - New Consistent Native Cross Platform GUI

• New X11/Motif GUI consistent with the Windows NT / 98 / 2000 GUI

• All NT GUI features & ease of use now available for X11/Motif

– Reporting for Media management– Templates– Only one window via pinned tabs instead of the

“windows overflow”– Object and task oriented usage– Guided through task via “next” instead of clicking

from menu to menu– Next Step Wizard

• Runs native on HP-UX and Solaris (Solaris: OmniBack II 3.6 “Sunrise” project)

• Tradeoff: Replaces old X11/Motif GUI

Next Step Wizard

19


Parallel Data Streams• Multiple parallel data streams from the same mount

pointfor Windows NT, 2000 too– Via multiple Backup Agents in parallel:

• Improves the backup performance

Disk Disk Disk

Single Mount Point:

20


Backup Session Restore• Restore template generated

out of the backup specification– Easy selection of objects

required to restore a system with many mount points (for example 80 mount points)

21


NDMP support• NDMP - Network Data Management Protocol• Backup of Network Appliance filers via NDMP• The Network Appliance filer is the “NDMP Server”

Cell ManagerDevice

Server

Backup Agents

Application Agent

+Manager-

of-Managers

User Interface

OmniBack II Cell

NDM

P

NDMP Server

NDMP ClientRobotic control of libraries via pass through

22


Other New Functionality

• Fast multiple single file and directory restore– Restore latest required file version of subsequent files

immediately– Fast positioning to subsequent files located in different

blocks on the media

• Defect backup devices can be switched into a maintenance mode

• Backup through firewalls are supported • Unsupported Tools on CD-ROM

23


New Devices• LTO Ultrium

– OmniBack II media management data in the LTO Cartridge Memory -> Benefit: data is not lost after media export:

Medium label Medium location Pool label Date of last access Date of last write Number of writes

Use LTO LCD display to show OmniBack II status information One Button Disaster Recovery

• SuperDLT• VXA

24


New PlatformsOmniBack II S u p p o r t e d O p e r a t i n g S y s t e m

Cell Manager HP-UX 11.x

Backup DeviceServer incl. robotic

control

Novell NetWare 5.x SUN Solaris 2.8 Linux - Red Hat Distribution 6.x (Intel/AMD) Linux - SuSE 6.x (Intel/AMD)

Backup DeviceServer withoutrobotic control

Above list plus: IBM AIX next version HP MPE/iX 6.0

Backup Agents Novell NetWare 5.x HP MPE/iX 6.0 SUN Solaris 2.8 IBM AIX next version SGI IRIX next version Linux - Caldera (Intel/AMD)

25


New Integrations

ApplicationAgents

S u p p o r t e d D a t a b a s e s / I n t e g r a t i o n s

Oracle Oracle 8.1.x/Recovery Manager, 32-bit (SUN Solaris 8)

Informix Informix Dynamic Server.2000, 32-bit and 64-bit (HP-UX 11.0) Informix Dynamic Server.2000, 32-bit (Windows 2000 (Intel/AMD))

Sybase Sybase Adaptive Server new version, 32-bit (HP-UX 11.x; SUN

Solaris 8, Windows NT 4.0 and 2000 (Intel/AMD based))

SAP SAP R/3 5.0, using backint and RMAN mode 32-bit / 64-bit (HP-UX

11.x) SAP R/3 5.0, using backint mode 32-bit (AIX new version; SUN

Solaris 8, Windows NT 4.0 and 2000 (Intel/AMD based))

26


New unique OmniBack II 4.0 features to remember

• Breakthrough scalability combined with file catalog browsing for convenient restores down to single file level and very low disk space consumption

• One consistent cross-platform GUI running native on UNIX, Windows NT, 98, 2000

• Most comprehensive split mirror backup solutions

OmniBack II 4.0 News Subject to be changed without notice Nsmdnt3.bbn.hp.com:\\public\omniback\projects\OB40-Mambo\Slides\OB40-Functionality15.

Documents