Gebruiksaanwijzing /service van het product B6960-96035 van de fabrikant HP (Hewlett-Packard)
Ga naar pagina of 422
HP Data Pr ot ec to r A. 06 . 1 0 C o ncepts gui de B6960-96035 P art number : B6 9 60 -9 60 3 5 F irst edition: No vember 2008.
Legal and notice information © Cop yri ght 1 9 99 , 2008 He wlett-P ackar d Developme nt Compan y , L.P . Conf idential compu ter softw are . V alid licens e fr om HP requir ed for pos sessi on, use or cop ying . Consistent with F AR 1 2 .2 1 1 and 1 2 .
C ont ents P ublicati on history .............................................................. 21 Abou t this guide ................................................................. 23 Intended audi ence ..............................................
Media management .......................................................................................... 48 Back up dev ices ................................................................................................. 49 User int er face s ...
Data Pr otector us er grou ps ........................................................................... 75 Data Pr otector us er righ ts ............................................................................. 75 Visib ilit y of back ed up data .
When to sc hedule back ups .................................................................. 107 Stagge r ing full back ups ....................................................................... 107 Optimi zing for r esto re ........................
V aulting ................................................................................................... 151 Re storing f rom medi a in a vault ................................................................... 153 Dev ices .....................
Data Pr otector us er righ ts ........................................................................... 185 5 The Data Pr otect or inte rnal databas e ............................... 187 In this chapter ..............................................
Data Pr otect or log files ........................................................................ 213 Windo ws applicati on log ........................................................................... 213 Jav a -based online r eporting ..........
F ilesy stem bac kup o f databases and appli cations ................................................ 239 Online back up of data bases and applicati ons .................................................... 239 9 Dir ect back up .......................
Local mir ror - dual host .............................................................................. 269 Local mir ror - single host ............................................................................ 270 Re mote mirro r .................
Exam ples of automat ed media cop ying .............................................................. 332 Exam ple 1 : automated media cop ying o f files yst em back ups ........................... 333 Incr1 bac kup ...................................
F igur es Data Pr otector gr aphical us er interface ............................................... 33 1 Back up pr ocess ............................................................................... 39 2 Re stor e pr ocess ........................
Incr emental bac kup s ........................................................................ 95 2 3 Le veled inc rement al back ups ............................................................. 95 2 4 Media needed to r esto r e fro m simple and le veled inc rement al back ups .
Shar ing an ADIC/GRAU or S torage T ek A CS library ........................... 170 50 Sto r age Ar ea Networ k ................................................................... 172 5 1 Loop initi aliz ation pro tocol ...............................
Split mirr or back up concept ............................................................ 266 7 8 Local mir ror - dual h ost (f ull performance , Zer o Dow ntime Back up) ....... 269 7 9 Split mir ror - r emote mirr or (LAN -fr ee remot e back up - data HA ) .
Ove r vi ew of bac kup and a utomated medi a copy ses sions ................... 340 1 05 Concepts gui de 1 7.
T able s E dition history ................................................................................. 21 1 Doc ument con venti ons ...................................................................... 31 2 Back up behav ior ....................
ABC’s Media P ool Usage ............................................................... 325 2 5 The S taggering A pproac h for ABC C ape T ow n .................................. 326 2 6 ABC’s bac kup spec ificati on confi gur ation ..............
20.
P u b lica tion histor y Guide updat es ma y be issued between editi ons to corr ect err ors or doc ument pr oduct change s. T o ensure that y ou rece iv e updated or ne w editions, su bscr ibe to the appr opriat e produc t support serv ice. S ee your HP sale s repr esentati ve f or details.
P ublication his tory 2 2.
About t his gui de This gui de descr ibes Data Pr otect or concepts. Read this man ual to fully under stand the fundamen tals and the model of Data Pr otector . Inte nded audie nce This gui de is intended for u sers inte r ested in unders tanding the concepts of Data Pr otector oper ation and f or people who plan com pan y backu p strategi es.
• HP Data Pr otector inst allation and li censing guide This gui de descr ibes ho w to install the Data Pr otector s oft w are , taking into account the oper ating sy stem and ar chitectur e of y our env ironme nt.
• HP Data Pr otector integr ation gui de for HP R eporter This man ual descr ibes ho w to install, co nfi gure , and use the int egr ation o f D ata Pr otector w ith HP Reporter . It is intended fo r back up administr ators . It discu sses ho w to use the appli cation for Data Pr otector se rvi ce managemen t .
This gui de descr ibes ho w to confi gur e MPE/iX cli ents and ho w to bac k up and r estor e MPE/iX data . • HP Data Pr otector Medi a Operati ons us er's guide This gui de pro vi des tr acking and management o f offline stor age media .
Doc umentati on map Abbr ev iations Abbr ev iations in the doc umentatio n map that follo ws ar e explained belo w . The gui de titles ar e all preceded b y the wor ds “HP Data Prot ector” .
Guide Abbre viation Installati on and licensing guide Install Media Oper ations getting started guide MO G S Media Oper ations pr oduct announcemen ts, so ft war e notes , and r efe rences MO RN Media.
Integr ations Loo k in these gui des for details o f the follo wing int egr ations: Guide Integration IG- OMU , IG- OMW HP Oper ations Manager fo r UNIX/f or Windo ws IG-P M/P A HP P erformance Manage.
Guide Integration IG-R HP Repo rter IG-S IP HP Servi ce Informati on P ortal all ZDB HP Stor age W orks Disk Arr ay XP all ZDB HP Stor age W orks Enter prise V irtual Arr ay (EV A) all ZDB HP Stor age.
Guide Integration IG-V ar S ybase all ZDB EMC Sy mmetri x IG-V ar VMwar e Doc ument con v enti ons and s y mbols T ab le 2 Documen t con v entions Element Conv ention Cr oss-re fere nce links and e -mail addre sses Blue te xt: T able 2 on page 31 web site addres ses Blue , underlined text: h t tp://www .
NO TE: Pr ov ides additi onal inf or mation . TIP: Pr ov ides he lpf ul hints and short cuts . Data Pr otect or gr aphi cal u ser int erface Data Pr otector pr ov ides a c ros s-platform (W indow s and UNIX) gr aphical user interf ace. Y ou can use the or iginal Data Pro tector GUI (W indow s only) or the Data Pr otector Ja va GUI.
Figure 1 Data Protector graphi cal user interface Gener al inf ormati on Gener al infor mation about Data Pr otecto r can be found at h t tp://www .hp .com/go/ datapr otecto r . HP tec hnical su ppor t F or wo rld wi de tec hnical suppo r t info rmati on, see the HP su pport web site: http://www .
Sub sc ripti on se r v ice HP r ecommends that you r egister y our pr oduct at the Subsc riber's C hoice f or Business w ebsite: http://www .hp .com/go/e -updates After r egister ing, y ou w ill recei ve e-mail notifi cation of pr oduct enhanceme nts, ne w dr i ve r versi ons, f irm war e updates , and other produc t res ources .
1 About ba c k up an d Da ta Pr otec tor In this c hapter This c hapter pr ov ides an o vervi ew of bac kup and r esto r e concepts. It intr oduces Data Pr otector ar chitec ture , media management , user in terface s, back up dev ices , and other f eatures .
Data Pr otector can be u sed in en vir onments r anging fr om a single sy stem to thous ands of sy stems on se ver al sites . Due to the netwo rk component concept o f Data Pr otector , elements of the bac kup inf rastr uctur e can be placed in the topology accor ding to user r equire ments.
Data Pr otector ena bles y ou to meet the needs for co ntinued business ope rations ar ound the clock . In today's globall y distribut ed busines s env ironmen t, compan y-wi de informati on re sour ces and c ust omer serv ice applicati ons must alw ay s be av ailable .
The D SI integr ation pr ov ides a se t of sc ripts and conf igur ation f iles fr om whi ch user s are able t o see ho w to add their o wn quer ies u sing Data Pr otector r eporting capab ilities .
Figure 2 Bac k up p rocess In most ca ses , the source is data on a disk , such as f iles, dir ector ies, dat abases, and applicati ons. If the bac kup is e xpected to be us ed for disas ter reco very , it needs to be consiste nt . Softw are that actuall y copies dat a to the destinati on is a back up applicati on.
Figure 4 Network back u p T o accomplish back up of a netwo rk env ir onment y ou need an applicati on that allow s y ou to: • Attac h backu p dev ices to an y sy stem in the netw ork This e nables local bac kup s of s yst ems with lar ge volumes o f data and networ k back ups in or der to r educe back up dev ice cos ts.
The Data Pr otec tor internal database (IDB) keeps tr ack of the f iles yo u back up so that y ou can bro wse and ea sily reco ve r the entir e sy stem or single f iles. Data Pr otector f acilitat es bac k up and res tore j obs. Y ou can do an immediate (or inter acti ve) back up using the Data Pr otect or use r interface .
S yst ems to be back ed up Clie nt sy stems y ou want to bac k up mus t have the Data Pr otect or Disk Agent (D A), also called Backup Agent , inst alled. T o back up online data base int egratio ns, ins tall the Application Agent . In the re st of the manual , the term Disk Agen t will be us ed for both agents .
Figure 6 Bac k up or restore operation Bac ku p sessi ons What is a bac kup se ssion? A back up ses sion, sh ow n in F igur e 7 on page 44, is a proces s that cr eates a cop y of data on s torage medi a.
Figure 7 Bac k up session A typi cal back up sessi on is more com plex than the one sho wn in F igure 7 on page 44. A number o f Disk Agen ts read data f r om multiple disks in par allel and send dat a to one or mor e Media Agen ts. F or more inf ormati on on comple x back up ses sions , see Chapt er 7 on page 219.
Ente rpr ise e n v ir onments What is an ent erpris e env ironmen t? A typi cal enterpr ise netwo rk env ir onment, sh ow n in F igur e 9 on page 45, consists of a number o f sy stems fr om diffe r ent vendor s with diff erent ope rating s yste ms. The s ystems ma y be located in differ ent geogr aphical ar eas and time z ones.
Wh y split large e nv ir onments into multiple cells? • Geogr aphical gr ouping of s yst ems. • Logi cal grou ping of s ystems , for e xample , departments. • Slo w net w ork connecti on between so me sy stems. • P erfor mance consider ations.
Figure 1 1 Man ager-of-Man agers envir onm ent Manager -of-Managers pr ov ides the f ollow ing featur es: • Centrali zed licensing repository This e nables simplif ied licens e management . This is opti onal but usef ul for v er y lar ge env ironmen ts.
Media manage ment Data Pr otector pr ov ides y ou w ith pow erful media managemen t , whic h lets you ea sily and eff ic iently manage lar ge numbers o f media in your e nv ironmen t in the follo wing.
Bac k up de v ice s Data Pr otector def ines and models eac h dev ice as a ph ysi cal dev ice w ith its ow n usage pr operties , such as the def ault pool. T his dev ice concept is us ed because it allo ws y ou to easily and fle x ibly conf igur e dev ices and use the m in conjuncti on w ith back up spec ifi cations.
Us er interf aces Data Pr otector pr ov ides eas y access to all conf igur ation and administr ation tasks using the Data Pr otector G UI on W indow s and UNIX platfor ms. Y ou can use the or iginal Data Pro tector GUI (on W indow s) or the Data Pr otect or Java G UI (on Windo ws and UNIX).
• A Re sults T ab with all the conf igurati on wi zar ds, pr operties and lists . • E asy conf igur ation and management o f the back up of online dat abase a pplications that run in W indow s env.
Figure 1 4 O riginal Da ta Protector GUI Figure 1 5 Da ta Protector Jav a G UI Data Pr otecto r Java G UI The Data Pr otector Ja va GUI is a Ja va-based gr aphical us er interface w ith a About bac ku.
cli ent -serv er arc hitectur e. It enable s back up management w ith the same look and fee l as the or iginal Data Pr otector GUI . The Ja va GUI consis ts of two compone nts: Java G UI Server and Jav a GUI Clie nt. F igur e 1 6 on page 53 sho ws the r elationship be t w een these co mponents.
Benef its of Jav a GUI The Data Pr otector Ja va G UI has the follo wing ad vantages o ver the o riginal Data Pr otector GUI: • P ortability The Data Pr otector Ja va GUI ar chitectur e enables y ou to inst all Jav a GUI Clie nts on all platf orms that su ppor t Ja va R untime En v ironmen t (JRE).
Ov ervi e w of tasks t o set up Data Pr otec tor This s ection pr ov ides an o verv ie w of global tasks to se t up y our Data Pro tecto r back up en vir onment . D epending on the si ze and co mple xity of y our env ir onment , yo u may not need to go thr ough all these st eps.
7 . Inst all and configur e yo ur Data Pr otector en vir onment . • Install the Data Pr otect or Cell Manage r s ystem and u se the Data Pro tecto r user in terface to distr ibute Data Pr otector compo nents to other s yste ms. • Connec t dev ices (tape dr iv es) to the s ys tems that will co ntr ol them.
2 P l anning y our ba c k up stra teg y In this c hapter This c hapter desc ribes bac ku p str ateg y planning. It foc use s on planning Data Pr otector cells, pe rfor mance, and s ecur ity , as we ll as backing up and r estor ing data.
Bac k up str ateg y planning Data Pr otector is simple t o conf igure and adminis ter . How ev er , if you w ork in a lar ge en vir onment w ith div erse cli ent s y stems and h uge amounts of data to bac k up, plan in adv ance. P lanning simplifi es subseque nt configur ation st eps.
The allo w ed do wntime has a si gnifi cant impact on the in ves tments into netw ork infr astru ctur e and equipment needed f or back ups. F or each ty pe of data, lis t the max imum acceptable do wntime f or r ecov er y , that is, h o w long spec ifi c data can be unav ailable befo re r ecov ered f r om a back up.
The time needed f or back up depends on the type o f back up , full or incr emental. F or mor e info rmati on, see “ F ull and incr emental bac kup s ” on page 91. D ata Pr otector also bac ks up some popular online data base applicati ons. F or mor e info rmati on, see the HP Data Pr otecto r integr ation gui de .
The need t o guard pr emises to pr ev ent unauthor i z ed people fr om enter ing. This als o includes saf eguarding all r elev ant data against unauth or iz ed access, using ph ysi cal acces s pr ev ention and elec tr onic pass wor d pr otection .
• Consi der backing up to a disk -based dev ice . Besides othe r benefits , back up to disk r educes the time needed for bac ku p and enables the u se of adv anced back up str ategies suc h as sy nthetic bac ku p and disk staging .
is that it can r equire mor e administrati ve w ork or mi ght e ven r equire a s eparate administr ator for eac h cell. • Si ze o f each cell The si ze o f a D ata Pr otecto r cell affec ts back up perfor mance and the ability to manage the cell . The r ecommended max imum si ze f or a Data Pro tector cell is 1 00 cli ent sy stems .
Installing and main taining cli ent s ys tems If y ou hav e se ver al UNIX and Windo ws c lient s ys tems , an effi c ient mechanism f or the installati on of Data Pr otector becomes im por tant . Local inst allation on e ve r y clie nt is not f easible in lar ge env ironme nts .
that each c lient s yst em is accessible fr om ev ery other cli ent sy stem using the s ame full y qualifi ed node name . Cr eating cells in the W indo ws e nv ir onment Due to the diffe r ent possibl.
W indo ws w ork grou ps Some o f the conf igurati on tasks r equire mor e steps in s ome cases , becaus e ther e are no global use rs as in a domain. S oft w are distr ibution r equir es a unique logon f or ev ery clien t s y stem that y ou install the so ft war e on .
Y ou can conf igur e a single cell ov er geogra phicall y remot e locations . In this case , y ou need to ensure that data transf er fr om each cli ent s y stem t o the corr esponding dev ice is not do ne ov er a W AN. Beca use a W AN network is n ot a stable connecti on, it is possible that connec tions ar e lost .
T o maximi z e performance , use local back up conf igurati ons for hi gh volume datastr eams. Netw ork or serv er ver sus dir ect back ups Sending data o ver a ne t w ork and thr ough a server intr oduces additi onal ov erhead, as the netw ork and the serve r become perfo rmance consider ations .
Hi gh perfo rmance har dw are other than de v ices P erfor mance of computer s ys tems The s peed of computer s ys tems thems elv es dir ectly impac ts performance . The s ys tems ar e loaded during back ups by r eading the disks, handling s oftwar e compr ession , and so on .
3 fas t tape dev ices , consider using 3 dedi cated networ k links bet w een sy stem_A and s ystem_B . • Load Balanc ing Using this Data Pr otecto r featur e , Data Pr otector d ynamicall y determine s whi ch objec t (disk) should be back ed up to w hich de vi ce .
F ull and incr emental bac k ups A basic a pproac h to impro ve perf ormance is to r educe the amount of dat a to bac k up . Car efull y plan y our full and incr emental bac ku ps . Note that y ou may no t need to perf orm all the f ull back ups of all the cli ent sy stems at the same time .
Disk perf ormance All data that Data Pr otector bac ks up resi des on disks in y our sy stems. T her efor e, the perfor mance of disks dir ectly influe nces bac kup perf ormance . A disk is essenti ally a sequen tial dev ice , that is, y ou can read or w rite t o it , but not both at the same time .
impr ov e performance in y our spec ifi c env ironmen t and determine the optimum as ync hr onous r eading settings. S AN per f ormance If lar ge volumes of dat a need to be bac ked up in one s ession , the time needed to tr ansfer the data becomes si gnificant .
Data Pr otector sec urity f eatur es The f ollow ing feature s allow and r estr ic t access to Dat a Pr otector and the bac ked up data . The items in this list ar e desc ribed in detail in the f ollow ing secti ons.
When is the accoun t c heck ed? When a u ser st ar ts the Data Pr otector us er interface , Data Pr otect or chec ks user r ights . User rights are also c heck ed when spec ific ta sks ar e performed b y a user . F or mor e info rmati on, see C hapter 4 on page 183.
V isibility of back ed up data Backing u p data means cr eating a new cop y . Ther efor e , when y ou deal with conf idential inf ormation , it is important to r estr ict acces s to both the or iginal data and to the back up copy itself .
encry pts the data. T hus the back ed up data is enc r ypt ed befor e it is transf err ed ov er the netwo rk and wr itten to media . F igur e 1 7 on page 77 sho ws a basi c inter action dur ing an encrypted bac ku p ses sion w ith the AES 25 6 -bit encrypti on option selec ted.
If a sour ce medium inv olv ed in an automati c media copy se ssion st or es encrypt ed as w ell as non-encrypted data , all data wr itten to the corr esponding t ar get medium w ill be either encry pted or non-encrypted , depending on cur ren t settings f or dr i ve-based enc r ypti on.
the CR S pr ocess is running , or the user spec ified as the o wner in the bac ku p spec ifi cation opti ons. F or instr ucti ons on ho w to spec ify a back up ow ner , see the online Help inde x: "ow nership". Back up o wnership and r esto r e Back up o wnership aff ects the ability of u ser s to see and re stor e data .
Figure 1 9 T ypical c luster Com ponents: • Clus ter nodes (two o r mor e) • Local disks • Shar ed disks (shared betw een nodes) Clus ter nodes Cluster nodes are com puters that compo se a clus ter . The y ar e phy sically connec ted to one or mor e shar ed disks.
y ou can make an appr opri ate determinati on of the o wne rship of the pack age (MC/S G, V er itas Clust er) or gr oup (MS CS) . What is a pac kage or gr oup? A pack age (MC/S G, V er itas C luste r) or a gr oup (MS CS) is a collec tion o f res our ces that ar e needed to run a spec ific cluster-a ware appli cation .
A clu ster -awar e Data Pr otector Ce ll Manager that is r esponsible f or running the IDB and managing back up and r estor e operati ons has many maj or benef its ov er non-clus ter ver sions: High a.
• The Data Pr otector c lien t is installed in a c luster . The Cell Manager (if n ot installed in the clu ster) in su ch a cas e is not fault tole rant; the oper ations in the cell mu st be r estarted manuall y .
Figure 20 Cell Mana ger installed outsi de a cluster When c reating a bac kup s pecif ication , you can s ee three or mor e sy stems that can be back ed up in the c luste r .
The f ollow ing is the expected bac kup be hav ior under this co nfi gurati on. T ab le 3 Bac k u p behavior Result Condition Successf ul back up F ailove r of the node befor e a back up starts Files ystem/disk image backup: The back up sessi on fails.
Figure 2 1 Cell M anager ins talled outside a c luster , de vices connec ted to the c luster nod es When c reating a bac kup s pecif ication , you can s ee three or mor e sy stems that can be back ed up in the c luste r .
NO TE: The diff er ence w ith the p re vi ous e x ample is that ea ch o f the clus ter nodes ha s a Data Pr otect or Media A gent install ed. Additi onally , you need t o use the Da ta Pr otect or load balanc ing func tionality . Includ e both de vi ces in the bac ku p specif icati on.
Data Pr otector c luster c ritical r esour ces ar e defined in the same pac kage (MC/Se rvi ceGuard) or gr oup (Mic ro soft Clus ter Serv er) as the appli cation clu ster cr itical r esour ces.
Figure 2 2 C ell Manag er installed in th e cluster , devices connected to clus ter nodes When c reating a bac kup s pecif ication , you can s ee three or mor e sy stems that can be back ed up in the c luste r .
NO TE: Clu sters d o not support a S CSI b us wit h shar ed tapes . T o br ing high av ailab ilit y also to Media Ag ents, the F ibr e Channel tec hnolog y can be used a s an interf ace to the de vi ce. The d ev ice its elf is not highl y-av ailabl e in this conf igur ation .
Result Condition Files ystem/disk image backup The back up sessi on fails at failo ver of the node w here the f ilesy stem is installed . The completed objec ts fro m the sessi on can be used fo r resto re , the failed (running and pending) ob jects need to be bac k ed up again by r estarting the se ssi on manuall y .
Incremental backup Full backup A r esto r e tak es more time beca use of the number o f media needed. Enables simple and q uick r estor e. Restor e Occu pies les s space in the IDB. Occu pies mor e space in the IDB. IDB impact Data Pr otector can also mak e incr emental bac kup s of online database a pplications .
Incr emental bac kup s depend on the last full bac kup . If you spec ify an incr emental back up and ther e is no pro tected f ull back up, a f ull back up is perfor med instead.
Incr A simple inc r emental back up , show n in F igur e 2 3 on page 95, is based on the last bac kup that is s till pr otected , whic h can be a full back up or an incr emental back up . Incr1 -9 A lev eled incremental backup, sho wn in F igur e 2 4 on page 95, depends on the last bac kup o f the ne xt lo wer lev el that is still pr otected .
Figure 2 3 In cremental bac k u ps Figure 2 4 Lev eled inc remental bac k ups T able 7 on page 95 show s the re lativ e r efer encing o f back up runs w ith var iou s back up types .
Incr3 <---- Incr1 <---- F ull 8 Incr3 <---- Incr2 <---- Incr1 <---- F ull 9 Incr3 <---- Incr2 <---- <---- <---- F ull 1 0 Incr3 <---- <---- <---- <---- <---- F ull 1 1 Ho w to read T able 7 on page 95 • The r o ws in T able 7 on page 95 are independe nt of each other and sh ow diffe rent situations .
TIP: Use t he Data Pr otecto r Appendable on Incrementals Only opti on to k eep dat a fr om full and inc reme ntal back ups (of th e same back up spec ifi cation) on t he same medi a set . Anothe r common u se of the incr emental bac kup concept is indi cated in F igur e 2 6 on page 98.
Figure 2 5 M edia needed to restore from simple and l e veled incremental backups Figure 2 6 Medi a needed to restore from le veled incremental bac k u ps Note that y ou must s et the appropr iate data pr otecti on in orde r to get all needed full and incr emental bac ku ps f or res tore .
K eeping bac k ed up data and inf or mati on about the data Data Pr otector lets y ou spec ify how long t o keep y our back ed up data on the media itself (data pr otection), ho w long to keep inf ormatio n about the back ed up data in the IDB (catalog pr otecti on) , and what le vel o f info rmati on to keep in the IDB (logging lev el) .
Cat alog pr otecti on What is catalog pr otecti on? Data Pr otector sa ves inf ormati on about bac ked u p data in the ID B . Since the info rmati on about the back ed up data is w ritten to the IDB each time a bac ku p is done , the ID B gr ow s with the n umber and the si z e of back ups.
av ailable , but y ou must kno w whi ch media to u se and what needs to be r esto r ed, fo r e xam ple, the e xact f ile name. The IDB also k eeps inf ormati on on ho w long the actual data on the media w ill not be o ve r wr itten.
Exporting media f r om a cell Exporting media fr om a Data Prot ector ce ll r emov es all the infor mation about bac ked up data on the medi a and the media themsel ve s fro m the I DB. Y ou cannot br ow se , selec t or r estor e files f rom e xported media using the Data Pr otector u ser interface .
on UNIX or disk dri ve s on Windo ws s yste ms) and the destinations ar e spec ified (ta pe) dev ices . During the bac kup s ession , Data Pro tecto r r eads the objects , transf ers data thr ough the networ k, and wr ites it to the media r esiding in the de vi ces.
• Desc ription: uni quely de fine s the back up obj ects with i dentical c lient name and mount po int . • T ype: bac kup ob ject type , for e xample f iles ystem o r Or acle. The w ay in w hich a bac kup ob ject is def ined is important to unders tand ho w incr emental bac kup s are done .
Bac ku p sessi ons What is a bac kup se ssion? A back up ses sion is a pr ocess that backs u p data fr om a clien t s ystem t o media. A back up ses sion alw ay s runs on the Ce ll Manager s yst em . A back up ses sion is based on a back up specif icati on and is started w hen a back up is run .
Y ou can comb ine full and incr emental bac kup s when y ou confi gure sc heduled back ups . For e xam ple, y ou may r un a full bac kup o n Sunday s and incr emental back ups e very wo rking day . T o back up a lar ge amount of data and a vo id the high vo lume peak f or the full back ups , use the s taggered appr oach.
This s ection comb ines all thes e concepts b y giv ing some ex amples of bac kup s chedules and some tips f or eff ici ent scheduling . When t o sc hedule back ups T yp ically , you sc hedule back ups to run dur ing lo w est u ser acti vity , usually at ni ght.
incr emental bac kup . For mo re inf ormation on h o w D ata Pr otector s elects media f or back ups , see Selecting media f or back ups . Exam ple 1 F igur e 28 on page 108 dep icts a sc heduling policy bas ed on a full back up plus simple incr emental bac kup s.
Figure 2 9 Full backup with daily le vel 1 incremental ba ckups This po lic y r equires sli ghtly mor e time for bac kup s and also r equir es a little mor e media since y ou back up all the c hanges fr om the last full bac ku p ev ery day .
Figure 30 F ull backup with mix ed inc remental bac k ups This po lic y tak es into account the f act that ther e are not man y changes dur ing w eek ends. Data is bac ked up u sing a combinati on of simple inc r emental back ups and Incr1 (diff ere ntial) back ups to optimi z e back up perfor mance.
• When is the lo we st sy stem usage and u ser acti vity? T yp ically , this is at night and most bac ku ps ar e scheduled to r un during the nigh t.
If y ou need to back up lar ge amounts of data and the bac ku p windo w pres ents a pr oblem, conside r backing u p to disk -based de vice s and using ad vanced bac ku p str ategies suc h as sy nthetic bac kup and disk s taging.
Smart M edia Cop y Media copy Object mirror Object copy No 3 No 2 Y es Y es Appendability of target media Media ide ntical to the sour ce media Media ide ntical to the sour ce media Media containing t.
Figure 3 1 Obj ect copy concept In the f igur e, the r e is an object v ersio n r esulting fr om a back up of objec t A, versi on 1 , and two additi onal copies of the s ame object v ersion .
Selecti on of dev ices Y ou need separ ate de v ices t o be used with the s ource medi a and the target medi a. The de stination de vice s can have a lar ger block si ze than the sour ce dev ices .
Wh y use ob ject cop y? Additi onal copies o f back ed up data ar e cr eated for multiple pur poses: • V aulting Y ou can mak e copies o f back ed up objects and k eep them in se ver al locations.
Figure 3 2 Freeing media Demultiple xing of medi a Multiple xed media cont ain interlea ved data of m ultiple obj ects . Such media ma y ar ise fr om back up sessi ons with the de vi ce concur r ency mor e than 1 . Multiplex ed media ma y compro mise the pri vacy o f back ups and r equir e more time f or re stor e .
Figure 3 3 D emultiple xing a medium Cons olidating a r esto r e chain Y ou can cop y a res tore c hain (all back ups that ar e necess ary for a r estor e) of an objec t ver sion t o a ne w media se t.
Figure 3 4 Disk stagin g concept Disk staging als o eliminates the need f or fr equent back ups o f numer ous small obj ects to tape . Such bac ku ps ar e inconv enient due to f reque nt loading and unloading of media . The use o f disk staging redu ces back up time and pre vents medi a deteri orati on.
The r esult of a succe ssful back up sessi on w ith object mir ror ing is one media set containing the bac ked up ob jects and additional medi a sets containing the mirr or ed objec ts. The mir ror ed objec ts on these media se ts are tr eated as objec t copies .
Figure 3 5 O bjec t mirroring Selecti on of dev ices Obj ect mir r oring is load balanced b y default . Data Prot ector mak es optimum use of the av ailable dev ices b y utili zing as man y dev ices as pos sible.
Back up perfo rmance also depends on f actors suc h as dev ice block si ze s and the connecti on of dev ices . If the dev ices used f or back up and obj ect mir r oring ha ve differ ent bloc k siz es, the mirr or ed data will be r epack aged during the se ssi on , whic h tak es additional time and r esour ces.
Au tomated media cop y ing What is aut omated media copy ing? Au tomated medi a copy ing is an automated pr ocess that c reate s copie s of the media containing bac kup s.
Smart media cop y ing using VLS What is smart media cop ying? In smart media cop ying , the data is firs t back ed up to a virtual tape libr ary (V TL) conf igured on the V irtual Libr ar y S yst em (VLS) .
R est or ing data P olic ies f or res toring data ar e an ess ential part of the o ver all back up str ategy in the compan y . K eep the follo wing in mind: • Backing u p and r estor ing files is es sentiall y the same as copy ing file s. Ther ef ore , ensur e that only auth ori z ed people have the r ights to r esto r e confiden tial data.
Selec tion of the medi a set If an obj ect v ersion that y ou w ant to r estor e ex ists on mor e than one media set , whi ch has been c reated using o ne of the Data Prot ector data dupli cation methods , an y of the media se ts can be used f or the re stor e .
S QL Server , and Mi cr osoft Shar eP oint P ortal Server int egratio ns. Su ch data bases ar e usually back ed up with int er dependent data str eams and, cons equentl y , r estor e must be started w ith the same number o f dev ices a s used during bac ku p .
End us er s ar e allo wed to r estor e Anothe r possible r esto re poli cy is to allo w all or jus t selected end u ser s to res tor e their o wn data . This poli cy pr o v ides suffi ci ent secur ity and may r eliev e the back up oper ator fr om doing a number o f rest ore oper ations .
oper ation can begin. T his includes r epartitioning and/or r efor matting the boot partition and r ecov ery of the oper ating sy stem w ith all the configur ation inf ormatio n that def ines the env ir onment . This has t o be completed in o r der to r ecov er other user dat a.
Disas ter r ecov er y methods Data Pr otector suppo r ts the follo w ing disaster r ecov ery methods: • Manual disa ster r ecov ery This is a ba sic and very fle xible dis aster r ecov er y method .
Alte rnati ve disas ter r ecov er y methods This s ection compar es the Data Pr otector dis aster r ecov er y concept w ith concepts of other v endors.
P lanning your back up str ategy 1 3 2.
3 Medi a man a g ement an d de vices In this c hapter This c hapter desc ribes Dat a Pr otector concepts o f media and de vi ce management . It disc usses medi a pools, de vice s, and lar ge librar ies .
Media managemen t functio nalit y Data Pr otector pr ov ides the f ollow ing media managemen t functio nality that allow s simple and eff ic ient management o f a large number o f media: • Gr ouping.
1 . Pr epar ing media f or back up. This inc ludes initiali zing (for mat ting) media f or use w ith Data Pro tector and assi gning media to media pools , whic h are u sed to tr ack the media . F or mor e info rmati on, see “ Medi a management befo re bac k ups begin ” on page 145.
else , does not matter ; it alw ay s belongs to its pool until it is r ecyc led and exported fr om the cell . Se ver al dev ices can use medi a fr om the same pool .
• s ystem platf orm (one pool f or UNIX s yst ems, o ne fo r Windo ws 2000 s ystems , and one fo r Windo ws XP s ystems) • per s yste m (eve r y sy stem has its ow n pool) • or ganiz ational str.
What is a fr ee pool? A fr ee pool is an au xiliary sour ce of media o f the same type (f or ex ample , DL T) for use w hen all fr ee media in a regular poo l run out .
All f r ee (unprot ected, em pty) media can be gr ouped in a fr ee pool and shared betwee n all media pools that su ppor t fr ee pool usage . • Redu ced oper ator interv enti on f or back up Assuming that all fr ee media ar e shared , the need for mount r equests is r educed.
Media poo l usage e xam ples The e xample s below sho w some conf igur ations y ou ma y wan t to consider w hen choo sing the appropr iate str ategy f or a particular bac ku p en vir onment . Exam ple 1 In the model sho wn in F igur e 3 7 on page 140, all obj ects ar e back ed up to the same media pool .
Figure 38 Configuration of media pools for large libraries Exam ple 3 F igur e 39 on page 142 sh ow s an ex ample w hen data is back ed up to media in a media pool w ith multiple dev ices sim ultaneously . Higher perf ormance is achi ev ed due to the use o f sev eral de vi ces in parallel , regar dless of w hic h pool is used .
Figure 3 9 Multipl e de vices , single medi a pool Exam ple 4 Data is back ed up to medi a in multiple media poo ls on multiple de vi ces simultaneou sly . If y ou want to u se the same dev ice w ith differ ent pools, y ou need to cr eate se ver al back up spec ificati ons.
Figure 40 Multiple dev i ces, multipl e media pools Implemen ting a media r otati on polic y What is a medi a r otation poli cy? A media r otation po licy def ines ho w media are u sed during bac kup , including the fo llo wing .
Media r otation and Data Pr otector Au tomati c media r otation and medi a handling Data Pr otector au tomates media r otatio n and media handling as f ollo ws: • Becaus e media are gr ouped into medi a pools, y ou no longer need to manage single media .
B y no w you sho uld be able to estimate the quan tit y of media r equir ed for a f ull media r otation . Additional medi a will be r equired in ca se you: • Assume 1 0% o ver head added b y Data Pr otector to the dat a on the media for dir ectory and file inf ormation .
Data Pr otector als o assi gns each medium a media ID that uniq uely identif ies this medium. An AN SI X3 .2 7 label is also w ritte n on the tape f or identif ication o n other s yst ems. Data Pr otector w rites the se labels w ith other infor mation to a medium header and to the IDB.
Media manage ment dur ing bac k up ses sio ns What happens dur ing back up? Dur ing a back up ses sion, Dat a Pr otector au tomati cally s elects media f or back up and k eeps trac k of whi ch data is back ed up to w hich medi a.
Media conditi on The co ndition o f the media also influence s whi ch media ar e select ed for bac ku p, f or e xam ple, media in good co ndition ar e used f or back up befo re media in f air condition . F or mor e info rmati on, see “ C alculating media conditi on ” on page 150.
Figure 4 1 Multipl e objects an d sessions per medium, s equential writes F igur e 4 1 on page 149 sho ws an e xample o f eight seq uential wr ites o ver f our sessi ons, using the appenda ble media usage poli cy . The data w as wr itten in four s essions , one obj ect at a time.
conc urr entl y writte n in ses s_7 and the second one in sess_8 . No te that one object can be str etched o ver s ev er al media . The media us age policy is appenda ble.
• media age The age o f a medium is calculated as the n umber of mon ths that hav e elapsed since y ou formatted , or initiali z ed, the medium . Once a medium is older than the thr eshold number of mo nths , it is mark ed as poor . • dev ice er ror s Some de vi ce err ors re sult in the medium being mark ed as poor .
• A r epor t sho wing medi a used for bac ku p within a spec ifi ed time -frame . • A r epor t sho wing w hich bac ku p specif ications have u sed spec ified medi a dur ing the back up . • A r epor t sho wing medi a stor ed at a specif ic location w ith data prot ecti on expir ing in a spec ifi c time .
R estor ing fr om media in a v ault Re storing medi a fr om a vault is no diff erent than r esto ring fr om an y other media . Depending on ho w your dat a and catalog protec tion polic ies ar e defined , you ma y need to do some additi onal steps: 1 .
in Data Pr otector using diff er ent (logi cal) dev ice names , for e xample , one w ithout har dwar e data compr essi on and another one w ith hard war e data compr ession . The f ollow ing secti ons descr ibe some spec ifi c dev ice functi onality and how Data Pr otector oper ates w ith var ious de vice s.
De v ice lists and load balanc ing Multiple dev ices f or back up When conf igur ing a back up spec ifi cation, y ou can spec ify sev eral st andalone dev ices or multiple dr iv es in a library de v ice that will be u sed for the oper ation .
gets full , the back up automati cally continue s on the medium in the next de vice in the dev ice c hain. Ho w load balancing w orks F or ex ample , assume that ther e are 1 00 obj ects confi gured f or back up to four de vi ces w ith concur r ency set to thr ee and with load balanc ing par ameter s MIN and MAX both conf igured at tw o.
Disk agent conc urr ency The n umber of Disk Agents s tar ted f or each Media A gent is called Disk Agent (bac k up) concurrency and can be modif ied using the Ad vanced options f or the dev ice or w hen conf iguring a bac kup . Data Pr otector pr ov ides def ault numbers that ar e suffic ient f or most ca ses .
NO TE: Some ta pe technol ogies place limit ations on th e number of f ile mar ks per medium . Ensure that y our segmen t siz e is not t oo lo w . Figure 4 5 Data format Segment si ze , measur ed in megabyte s, is the max imum si z e of data segments .
Incr easing the bloc k si z e can impr ov e performance . Changing the block si z e should be done bef ore f ormatting tapes . F or e xample , a tape w ritte n w ith the default bloc k si z e cannot be appended t o using a differ ent block si ze . NO TE: Use t he same block si ze f or media tha t can be us ed wit h differ ent de vi ce t ype s.
Ph ysical de vi ce collision When s pec if y ing a dev ice used f or back up , y ou may spec ify one dev ice name in one back up spec ifi cation and another dev ice name of the same ph ysi cal dev ice in a differ ent bac kup s pec ificati on.
install a Data Pr otect or Media A gent on the s ystem w ith the de v ice connec ted. Data Pr otector can det ect and au tomati cally conf igur e most standalo ne dev ices . Dur ing a back up , Data Prot ector issues a mo unt r equest w hen the medium in a dev ice is full .
L ar ge libr ari es What ar e library dev ices? L ibr ar y dev ices ar e automated de vi ces, also called au toloaders, e xc hangers or juk ebox es. In Dat a Pr otector , most libr aries ar e conf igured as S CSI libr ari es .
• Obtain the number o f requir ed media . See “ Implementing a media r otati on polic y ” on page 143. Shar ing a library w ith other appli cations A libr ar y dev ice can be shar ed with othe r applications s toring data t o media in the dev ice .
• Scanning the bar codes of the media in a de vi ce’s r epository is fast er , because Data Pr otector does n ot need to actually load the medi a to a dri ve and r ead the medium header . • A bar code is automaticall y read b y Data Pro tector and us ed to iden tif y the media .
Pr otector int ernall y redir ects the r obotic commands to the s ys tem that manages the r obotics . Figure 4 7 C onnectin g driv es to multiple systems Con trol pr otocols and Data Pr otector Medi a.
• S CSI—f or roboti cs other libr arie s • NDMP—f or NDMP robo tics All f our library r obotic co ntr ol pro tocols ar e implemented in both the Gene ral Media Agen t and in the NDMP Media A gent.
T able 1 1 on page 167 sho w the Data Pro tecto r Media Agent (the Gene ral Media Agen t or the NDMP Medi a Agen t) r equired on a c lient s yste m configur ed for r obotic contr ol of a libr ar y w ith dr i ve s shared among multiple c lient s ys tems .
Figure 48 Sharing a SCSI librar y (robotics at tac hed to a Data Protector Clien t S ystem) F igur e 48 on page 168 sho ws a S CS I libr ar y , with its r obotics attached t o and conf igured on the Data Pr otector c lient s ystem w ith either the Ge ner al Media Agent or the NDMP Medi a Agent installed .
Figure 4 9 Sharin g a SCSI library (robotics a ttac hed to an NDMP S erver) F igur e 49 o n page 169 sho ws a S CSI libr ar y , w ith its roboti cs attached to an NDMP Serve r and conf igured on the Dat a Pr otector c lient s ystem w ith either the Gener al Media A gent or the NDMP Media A gent installed .
Figure 5 0 Sh aring an ADI C/GR AU or Storage Tek A CS library F igur e 50 on page 170 sho ws an ADIC/GRA U or Stor age T ek A CS libr ar y , w ith its r obotics attac hed to an ADIC/GRA U or Stor age T ek A CS Serve r and configur ed on the Data Pr otector c lient s yste m w ith either the Gener al Media Agent o r the NDMP Media A gent installed .
St orage A r ea Net w orks A Sto r age Ar ea Networ k (SAN), depi cted in F igure 5 1 on page 172, is a ne w appr oach to netw ork stor age that separ ates stor age management f r om server management w ith a networ k dev oted to stor age.
Figure 5 1 Storage Area Net wor k F ibre C hannel F ibre C hannel is an ANS I standar d for high-s peed computer inter connection . Using either opti cal or copper cables , it allo ws the bidir ectional tr ansmission o f lar ge data file s at up to 4.
P oint-to -point , loop, and s witc hed F ibre Channe l topologie s can be mix ed to best suit y our connecti v ity and gro wth req uiremen ts. F or a list of supported conf igur ations, s ee the HP Data Pr otector pr oduct announcemen ts, softwar e notes , and re fer ences or h ttp://www .
Figure 5 2 Loop initi alization protocol S w itched topolog y The s w itc hed topolog y pro vi des any-to -any co nnectiv ity bet w een all nodes connect ed to a s witc h. S wit ches ar e easy t o install and u se , because the F ibre Channe l protocol pr ov ides self-conf igur ation and s elf-management .
De v ice shar ing in S AN Data Pr otector suppo rts the S AN concept b y enabling multiple s y stems t o shar e back up de v ices in the S AN env ironme nt. T he same phy sical de vice can be acce ssed fr om multiple s yst ems. T hus , any s yste m can perform a local bac kup o n some dev ice or an y other dev ice .
Figure 5 3 Example multipat h configuration Wh y use multiple paths With pr ev iou s versi ons of Data Pr otector , a dev ice could be acce ssed f rom onl y one cli ent. T o o ve rcome this pr oblem, s eve ral logical de vi ces had to be conf igur ed for a ph ysical de vi ce using a lock name .
Dur ing a r estor e sessio n, the dev ice paths ar e selected in the f ollow ing or der: 1 . P aths that are on the c lient to w hich the ob jects ar e res tor ed, if all obj ects are r estor ed to the same tar get cli ent 2. P aths that wer e us ed f or back up 3.
Indir ect and Dir ect L ibr ar y Acce ss Upon conf iguring Dat a Pr otector w ith a S CS I Libr ar y dev ice , ther e are two w ay s in whi ch cli ent sy stems can acce ss libr ar y r obotics: Indir ect L ibrary Access and Dir ect L ibr ar y Acces s.
Figure 5 4 Indirect Lib rary Access Note that y ou cannot use a shar ed library if the c lient s ys tem that contr ols the roboti cs, castor , in our e xample , fails .
Figure 5 5 Direct Librar y Access De v ice shar ing in clu ster s Clus tering , whi ch is o f ten us ed in combination w ith the S AN concept, is bas ed on shar ing netwo rk re source s (for e xample netw ork names , disks, and ta pes dev ices) betwee n nodes.
F loating dri v es F loating dri ves ar e dev ice that ar e configur ed on a v ir tual hos t , using virtual s yste m names . F loating dri ves sh ould be configur ed for the bac ku p of c luster -aw are applicati ons.
Media managemen t and dev ices 1 8 2.
4 Users and us er gr ou ps In this c hapter This c hapter disc usse s D ata Pr otector s ecur it y , user s, user gr oups, and us er righ ts. It is or ganiz ed as follo ws: “ Incr eased sec urity f .
can see and r estor e the back ed up data. Y ou can mak e data visible to other u sers using the Data Pr otector P ublic option . F or instr uctions , see the Data Pro tector online Help .
Using pr edefined u ser gr oups The f ollow ing default gr oups ar e pro vi ded by Data Pr otector : T ab le 1 2 D ata Protector predefined us er groups Access rights User gr oup Allo wed to conf igure Data Pr otect or and perfo rm bac kup , res tore , and all other a vailable ope rations .
User s and user gr oups 1 8 6.
5 T h e Da ta Protec tor internal da ta ba se In this c hapter This c hapter desc ribes the Dat a Pr otector inte rnal database (IDB) ar chitec tur e, as w ell as its usage and ope ration .
• F ast and con venien t rest ore T he informati on stor ed in the IDB enables y ou to quic kly f ind the media req uired f or a r estor e, and ther ef ore mak es the r esto re muc h faster . It also off ers y ou the con venience o f being able to br ow se for f iles and dir ectori es to be r esto red .
T he I DB on the UNIX C ell Manager IDB location The IDB on the UNI X Cell Manage r is located in the /var/opt/omni/server/db40 dir ectory . IDB for mat The IDB on the HP -UX and Solaris C ell Manager stor es all te xt informati on in AS CII single - and multi-b yte for mats.
F or robu stness consi deratio ns and recommendati ons for optimi zing robu stness b y r elocating some IDB direc tor ies, s ee the online Help index: “ r obustness o f I DB“ . Under ly ing tec hnolog y The MMDB and CDB parts ar e implemented using an embedded dat abase co nsisting of table spaces.
MMDB si ze and gr o wth The MMDB does n ot gro w very bi g in si z e . The large st portion of the MMDB is typi cally occ upied b y informati on about the Data Pr otecto r media . Space consumpti on is in the r ange of 30 MB . Ffor mor e details , see “ IDB si ze e stimation ” on page 203.
whe n one of these f iles starts running out o f space, s o that y ou can add ne w files to e xtend the si z e of the filename s par t of the IDB. Si ze and gr owth f or CD B (obj ects and positions) The CDB r ecords o ther than filenames occ up y a minor shar e of space in the IDB.
DCBF location B y def ault , the DCBF is located in the follo wing dir ectory: • On Windo ws Serve r 2008: Data_Protector_program_data db40dcbf • On other W indow s sy stems: Data_Protector_home d.
Serv erles s Integr ations Binary F iles (S IBF) SIBF r ecords The S er ve rle ss Integr ations Binary F iles stor es r aw NDMP r estor e data. T his data is necess ary for r estor e NDMP objec ts. SIBF si z e and gro wth The S IBF does not gr ow v er y bi g in siz e.
If tr ansaction logging is ena bled, an IDB back up re mo ve s old transac tion logs and starts cr eating ne w ones , whic h are neces sar y fo r an IDB reco very .
R emov ing the detail catalog When the det ail catalog is r emov ed for a spec ifi c medium, its DC binary file is r emov ed. The s ame r esult is achi ev ed by r emov ing the catalog pr otection f or all objec t versi ons and objec t copies on that medium (the ne xt daily maintenance of DC binary file s remo ves the b inar y file).
IDB maintenance Once y ou configur e the I DB, its main tenance is r educed to a minimum , mainly acting on notif ications and r eports. IDB reco very An IDB r ecov ery is needed if some of the IDB file s are missing or co rrupted . The r ecov ery procedur e depends on the le ve l of cor rupti on .
• Gr owth of y our back up en vir onment T he number o f s ystems be ing back ed up in the cell influence s the I DB gr owth . Plan f or the gro wth of y our back up env ir onment .
Figure 5 7 The influence of loggin g le vel and catalog protec tion on IDB gro wt h L ogging le v el as an ID B k ey tuna ble paramete r What is logging le vel? Logging le vel de ter mines the amount o f details about bac k ed up files and dir ector ies wr itten to the IDB.
Log s all detailed inf ormation abou t backed u p dir ector ies (names , ve rsi ons, and attr ibutes). This r epr esen ts appr ox imately 1 0% of all detailed inf ormation abou t backed u p file s and dir ectori es. Log Director ies No infor mation about bac ked up f iles and direc torie s is logged to the IDB.
Catalog pr otecti on as an IDB k ey tunable par ameter What is catalog pr otecti on? Catalog pr otecti on determine s how long the inf ormatio n about bac ked up dat a is av ailable in the IDB. T his is differ ent fr om data pr otecti on, w hich det ermines ho w long the back ed up data is a vailable on the medium its elf.
pr otection is s et for 4 w eeks, then signif icant gr owth of the IDB stops after 4 w eeks. The r efor e, in this ca se , the IDB is 1 3 times larger if the cat alog protec tion is set to Permanent . It is r ecommended that catalog pr otection inc ludes at least the las t full back up .
Spec ifi cs for lar ge cells If the number o f file s gro ws into the t ens of millions , or there ar e tens of thou sands of f iles gener ated on a dail y basis, and y ou use the Log All option , then back up speed and IDB gr owth w ill become a proble m in a relati vel y short peri od of time .
The Data Pr otecto r inter nal database 204.
6 Ser vice man a g ement In this c hapter Serv ice Manageme nt , reporting , and monitoring he lp administrato rs manage the ir back up en vir onments mor e effecti vel y .
Serv ice manageme nt measur es and r eports are a k ey tool I T managers can use to demonstr ate value de liv er ed to the organi zati on and also to maintain co mpetiti ve cost s tructur es.
Figure 5 8 Ser vice mana gement information flow Nati v e Data Pr otec tor f uncti onalit y The f unctionality desc ribed in the f ollow ing secti ons comes w ith Data Pr otect or “ out of the bo x.
send alerts v ia SNMP , it is possible t o integrate v irtually an y applicatio n that can r eceiv e SNMP tr aps. • Data Pr otector bac kup s essi on auditing stor es info rmation abo ut all back up.
centr al operati ons console , such as HP Oper ations Manager s oft w are , paging a s ystem ope r ator , or taking automat ed r emedial acti on to res olv e the pr oblem. T ab le 1 3 ARM fun ctionalit y Usage Additional data logged to ARM (ARM 2. 0) T ransaction description (ARM 1 .
Integr ation w ith HP Oper ations Manage r softwar e F unctionality of the Data Pr otecto r OM int egr ation Data Pr otector int egr ates with HP Ope r ations Manager softw are (OM). OM simplif ies management o f lar ge netw orks by allo wing the oper ator to monitor and adminis ter the netwo rk and the applicati ons fr om a single point .
F rom the monit or’s user in terface , you can abo rt a back up , r estor e, or medi a management s essi on or re spond to “ mount ” r eques ts. If y ou make us e of the Manager-o f-Managers, y ou can monitor se ssions of m ultiple cells simultaneo usl y fro m one use r interface .
• Select f rom man y deli very methods used t o deliv er reports (suc h as e -mail, S NMP , br oadcast (av ailable on Windo ws o nly), wr ite to file , and send to e xter nal command) Y ou can comb ine most of thes e differ ent for mats, deli very methods, s chedule s, and tr igger s.
Data Pr otecto r log f iles Some Se rvi ce Management applicati ons, such a s HP Operatio ns Manager softwar e, allo w you to spec if y whe n and whic h log files should be mo nitor ed for a spec ific log entry . If the spec ified e ntr y is detect ed in the file , an action can be spec ified .
Data Pr otect or chec king and maintenance mec hanism Data Pr otector has a r ic h automated dail y self-chec k and maintenance mec hanism, whi ch impr ov es its oper ational r eliab ilit y and pr edictab ilit y .
• Sending maj or and cr itical Data Pr otecto r eve nts to y our networ k management soluti on, suc h as HP Networ k Node Manager (Data Pro tecto r built -in notif icati on engine sending S NMP trap s) .
• Adminis tr ation R eports • Media P ool R epor ts • P erfor mance An I T Service Pr ov ider can use the se r eports to demonstr ate its SL A compli ance to a c ust omer .
Figure 6 1 O perational error status report Data Pr otec tor O M SIP This in tegrati on also us es SIP to pr ov ide Data Pr otector inf ormation thr ough a w eb-based int erface. It doe s not req uire O VO t o be installed . The integr ation pr ov ides info rmati on through t ables and gauges.
Figure 6 2 Direc t SIP integra tion e x am ple Servi ce management 2 1 8.
7 Ho w Da ta Protector operates In this c hapter This c hapter desc ribes the ope ration o f Data Prot ector . It explains Data Pr otecto r pr ocesses (on UNI X) and servi ces (on W indow s) , back up and re stor e sessions , and media managemen t sessio ns.
CR S The CR S (Cell R equest Serve r) pr ocess (servi ce) runs on the Data Pr otector C ell Manager . It starts and contro ls back up and r estor e sessi ons. T he servi ce is started when Data Pr otector is inst alled on the Cell Manager s yste m and is r estarted each time the s ys tem is r estarted .
Sc heduled and inter acti v e back up se ssi ons Sc heduled back up ses sion A sc heduled backu p sessio n is started by the Data Pr otector S cheduler at the time y ou have s pecif ied. Y ou can vi ew the pr ogres s of the scheduled bac kup s ession in the Data Pr otector monit or .
4. The B SM starts Disk Agents (D As) for each disk t o be back ed up in parallel . The actual numbe r of Disk Age nts started depends on the conc urr ency of Disk A gents conf igured in the bac kup s pecif ication .
T o pre vent Data Pr otect or pr ocesses f rom e xceeding s y stem ca pabiliti es, the max imum number o f conc urre nt back up sessi ons is limited. T he limit is configur able . F igur e 64 on page 223 show s multiple sessi ons running conc urr ently .
Queuing of bac k up ses sio ns Timeo ut When a bac kup s ession is s tarted, Data Pr otector tr ies to allocate all needed r esour ces, suc h as de vice s. T he sessi on is queued until the r equired minim um r esour ces are av ailable. If the r esour ces are still una vailable after the timeo ut , the sessi on is aborted .
Sending notif icatio n to an operator Y ou can conf igur e a D ata Pr otector n otificati on to send an e -mail to the oper ator w ith info rmati on about the mount r equest . The oper ator can tak e the appropr iate acti ons, suc h as manuall y loading the needed media or aborting the ses sion .
A r estor e sessi on is started int eracti ve ly . Y ou tell Data Pr otector w hat to r estor e, let Data Pr otector dete rmine the needed media , select s ome options and start the r estor e. Y ou and other u sers can monito r the pr ogres s of the se ssion .
Figure 6 5 Restore session information flow Ho w many r estor e sessi ons can run conc urre ntl y? A number of r estor e sessio ns can run in the cell at the same time . This number is limited b y reso urces in the cell , such as the C ell Manager and sy stems w ith connected dev ices .
Mount r equests in a r estor e sessi on What is a mount r equest? A mount r equest appear s in a res tor e sessi on when the medi a needed fo r r estor e are not a vailable in the de vice . Data Pr otector allo ws y ou to conf igure a de sir ed action that should happen w hen a mount r equest appear s.
Figure 6 6 Par all el restore session flo w In a par allel res tore , Data Pr otector r eads multiple xed dat a for all selec ted objects and ass embles the parts needed fo r all the obj ects on the fl y , sending the ri ght data to the r ight Disk Agents .
What is an obj ect copy s essi on? An obj ect copy s essi on is a proce ss that c reates an additi onal copy of the bac ked up data on a diff eren t media set . During an obj ect copy s ession , the selected bac ked up obj ects are cop ied fr om the sour ce to the target medi a.
4. The C SM starts the Media Agen ts on the s yste ms w ith dev ices conf igured f or copy ing. The Media Agents load the s ource and tar get media allocated accor ding to the back up polic ies . 5 . Media A gents r ead the data fr om the sour ce media and connect to the Medi a Agen ts loaded w ith the target medi a.
Figure 6 7 Obj ect copy session inf ormation flow Queuing of ob ject cop y ses sions Timeo ut When an ob ject copy s ession is s tar ted , Data Protec tor tri es to allocate all needed r esour ces. The s ession is q ueued until the req uir ed minimum res ources ar e available .
Obj ect cons olidati on se ssi ons This s ection des cr ibes ho w an object cons olidation s ession is s tarted, w hat happens dur ing the ses sion , and the proce sses and serv ices in volv ed.
2. T he CSM opens the IDB , r eads the infor mation about the needed medi a, and wr ites the inf ormation a bout the obj ect consoli dation s ession , such as gene rated mess ages , to the IDB.
av ailable. If the r esour ces are still una vailable after the timeo ut , the sessi on is aborted . The timeo ut per iod can be set using the SmWaitForDevice global option.
2. T he MSM s tar ts the Media A gents (MAs) on the s ys tem that has dev ices u sed fo r the media managemen t session . 3. Media A gents perfor m the reque sted oper ation and send gener ated mess ages to the Data Pr otector u ser interface , whe r e you can tr ack the pr ogres s.
8 Integra tion with d a taba se ap p lica tions In this c hapter This c hapter gi ves a br ief desc ripti on of the integr ation of Data Pr otecto r w ith database applicati ons, suc h as Mic ros oft Exc hange Server , Or acle Serv er , IBM DB2 UDB , and Info rmi x Server .
Figure 6 8 Rela tional da tabase F igur e 68 on page 238 sho ws a ty pi cal r elational databa se with the s truc tures desc ribed belo w . Data files are ph ysi cal file s that contain all of a databas e’s data . The y change r andomly and can be v ery large .
1 . A trans action is f irst r ecorded int o the tr ansaction log . 2. Change s r equired in the tr ansacti on ar e then applied to cac hed pages. 3. F ro m time to time se ts of modif ied pages ar e flushed to data f iles on disk. F iles y stem bac k up o f databa ses and a ppli cations Database s are cons tantl y changing while the y ar e online.
The e ssence of the bac kup int erface is that it pr ov ides the bac kup a pplicati on with consiste nt data (e ven if it ma y not be consisten t on the disk) w hile at the same time k eeping the database oper ational .
• The r e is no need to spec if y the location o f data files . These can be locat ed on differ ent disks . • The logi cal struc tur e of the database can be br o ws ed. It is pos sible to select onl y a subs et of the data base . • Appli cations ar e aw are o f backu p operati on and k eep trac k of whi ch parts ar e back ed up .
Integr ation w ith database applicati ons 2 4 2.
9 Direct ba c k up In this c hapter This c hapter intr oduces the dir ect back up concept and the tec hnologie s that enable it . The chapt er also discu sses the dir ect back up conf igur ations that ar e supported by Data Pr otector .
Dir ect back up ext ends the benef its of HP’s ZDB soluti on by mo ving data dir ectly fr om disk to tape and making the load on the bac ku p serve r negligible or ev en making the back up serv er optional .
Back up types Dir ect back up supports back up of appli cation data f iles and contr ol f iles and of disk images -- eithe r raw disk or ra w logical vo lume .
F igur e 7 0 on page 246 sho ws a basi c dir ect back up confi guratio n. T he Res olve A gent is on a separ ate back up hos t in this configur ation .
• The HP S torage W orks Disk A rra y XP (XP) is confi gured as Bu siness Cop y (BC) w ith mirr ors conf igur ed with eno ugh disk space . • The S AN is proper ly conf igured in o r der to pr ov i.
X Cop y + Res ol ve Pr ior t o Re solv e, y ou needed a server w ith a matching f ile sy stem to ge t this info rmati on. T his w as becau se e ven w ith the ri ght serv er , getting this infor mation.
Database . T he Back up Media A gent (BMA ) w rites catalog s egments and delimiters betwee n data and catalog segments kno wn as f ile -marks. R est ore The r e are two r estor e options w hen using .
Supported conf igur ations T hree h os ts: CM, applicati on , R esol ve This s olution us es three ho sts: one each f or the Cell Manager , Resol ve Age nt, and applicati on.
Figure 7 1 Basic t hree host configuration T w o Hosts: C ell Manager/R esol ve A gent and appli catio n This s olution us es t w o hosts: one f or the Cell Manager and R esolv e Agent and one fo r the applicati on.
Media A gent ma y impact the applicati on database ’s perfor mance (XC opy ’s proces sing r equireme nts ar e negligible) . Note that in this conf igur ation, the h ost mus t be running HP -UX 1 1 .
1 0 Disk bac k up In this c hapter This c hapter intr oduces the concepts ass ociat ed with backing u p data to disk and the tec hnologie s that enable it. It als o discus ses the disk - to -disk back up conf igurati ons that ar e supported by Data Pr otector .
Disk bac k up benef its The r e are man y situations in w hich it is ad vantageou s to use disk -based de vice s when perfor ming back ups. Disk -based de v ices ar e, in f act , spec ific f iles in spec ified dir ectori es, to w hich y ou can back u p data instead o f or in addition to bac king it up to tape .
• Ove rall , disk -based st orage space is becoming inc reasingl y cheaper e ven if compar ed to tape -based s torage . Data Pr otect or disk -based de v ices Data Pr otector has the f ollow ing dis.
of fr ee disk space appr oaches the conf igured minim um amount req uired f or the dev ice to w ork . This enable s y ou to fr ee more disk space in good time for the de vi ce to contin ue sa v ing data .
1 1 S y nt h etic ba c k up In this c hapter This c hapter intr oduces the concept of s yn thetic bac ku p and explains the sy nthetic back up soluti on pro vi ded by Data Pr otector .
ne w , s yntheti c full back up . This can be r epeated indefinit ely , w ith no need to run a full bac kup again . In ter ms of res tore s peed, a s yntheti c full back up is equi valent to a co nv entio nal full back up . The r estor e chain consists of only one ele ment, s o a r estor e is as quic k and simple as pos sible.
The f ollow ing figur es explain the co ncept of s yntheti c back up and virtual full bac ku p . The y sho w how a s ynthe tic full bac k up or a virtual f ull back up is cr eated fr om a full back up and an y number of incr emental back ups .
Figure 7 3 Virtual full bac k u p F igur e 7 3 on page 260 sho ws ho w a virtual full bac k up is cr eated. W ith this t ype o f back up , all the back ups r eside in a single f ile library that use s distributed f ile media fo rmat .
Figure 7 4 Full and inc remental bac k u ps In F igur e 7 4 on page 261, con ve ntio nal back ups w er e perfor med. T o re stor e to the latest po ssible state , yo u need the full back up and all fo ur incr emental bac ku ps . The r estor e chain consists o f fi ve e lements , whic h often r eside on diffe r ent media.
Figure 7 6 Regular synthetic ba ckup F igur e 7 6 on page 262 sho ws a situati on wher e a sy nthetic bac kup w as perfor med after eac h incr emental bac kup . This str ategy ena bles the simplest and qui ck est r esto re to the lates t possible state , or to an y earlier po int in time that was bac ked up .
B y def ault , the last s yntheti c full bac kup in the bac kup c hain is used f or res tore , irr especti ve o f whether the pr eceding back ups ar e still valid or the ir prot ection has alr eady exp ired and the obj ects are r emo ved fr om the IDB.
S yntheti c backu p 2 64.
1 2 S plit mirror concepts In this c hapter This c hapter intr oduces the split mir ror bac kup concept and dis cus ses the conf igurati ons that are suppo rted by HP .
Figure 7 8 Split mirror bac k up con cept The tar g et v olum es in repli ca are typ ically connec ted to a separ ate c lient , whi ch also has tape de vi ces connected to allo w for local bac kup .
• Database s can be put into back up mode • Database s can be taken o ffline • A mount po int can be unmount ed Only w hen this is carr ied out bef ore a r eplica is consist ent .
allo ws up to thr ee repli cas, and eac h can hav e an additional tw o copie s if cascading is used . Dur ing the instant r ecov ery , the data on the spec ified r eplica (left unc hanged for the purpo se of ins tant reco very) is s ync hroni z ed to the applicati on clien t sour ce volume s w ithout re storing f rom a bac kup medium .
Supported conf igur ations L ocal mirr or - dual hos t This s olution us es a local mirr oring func tionality such as B usiness Cop y XP . Both disks ar e in the same disk arr ay , whic h means the I/O infr astruc ture of the RAID s y stem is actuall y shared betw een the applicatio n cli ent (or host) and the bac kup c lient .
databas e into a consistent mode that per mits the split , as w ell as to tak e it out of this mode again. This co nfi gurati on enable s an offline bac ku p of a very lar ge databas e in a short time , as w ell as an online back up that cr eates v er y fe w ar chi ve log f iles, since the bac kup mode time of the databa se is k ept to a minimum.
Figure 80 Split mirror - remote mirr or (L AN -free remote back u p - data HA) The r emote mir ror tr ansfer s data to a ph ysi cally separ ate site whe r e it can be back ed up to locall y available t apes.
r emote disaste r r ecov er y site using har dw are mir ror concepts is wide ly accepted in the industry . L ocal/re mote mirr or combinati on If the c ustomer has a need f or a permanentl y av ailabl.
Other conf igur ations The r e are man y other possible split mir ror co nfigur ations that pr ov ide some partic ular adv antage or fulf ill a spec ific u ser need .
Split mir r or concepts 2 7 4.
1 3 Sna pshot con cepts In this c hapter This c hapter intr oduces the snapsh ot back up concepts and disc uss es the confi gur ations that ar e supported by HP .
allocation o f logical volume s on phy sical disks, but y ou can influence it w ith a choi ce of pr otecti on char acter istic s. RAID Redundan t Arr ay of Ine xpensiv e Disks (RAID) technolog y is used to contr ol the wa y in whi ch the data is distr ibuted acr oss the ph ysical disks w ithin a disk arr ay .
Figure 8 2 Sna pshot backup The bac ku p cli ent is set up as a Data Pr otector c lient w ith tape dev ices connec ted, to allo w a local back up to be perfor med.
• Database s can be put into back up mode • Database s can be taken o ffline • A mount po int can be unmount ed F or an online databas e back up , snapshot data alone doe s not suffi ce for a r estor e. The ar chi ve log f iles fr om the applicati on clien t are also needed .
Instan t reco very Dur ing snapsho t back up ses sions, s ev er al snapsh ot copies of dat a can be produced and can be r etained on a disk arr ay , each po int-in - time cop y in its o wn r eplica. T he r etained snapshot cop ies of data can then be u sed f or var ious purpo ses, suc h as offline dat a proces sing or instan t r ecov ery .
not w ritten to that r eserved s pace until necessary . As the data change s on the sour ce vo lume, the snapsh ot data on the tar get v olume is updated w ith the or iginal data .
Supported conf igur ations Basi c confi gurati on: single disk arr ay - dual hos t Both hos ts are connec ted to the same disk ar ra y , so that the I/O infr astructur e of the RAID sy stem is actuall y shared betw een the applicatio n client and the bac kup c lient .
1 . P ut the database in to a consist ent mode that per mits a snapshot to be tak en. 2. P erfor m a snapshot of the appli cation data . 3. R eturn the databas e to normal oper ating mode.
Figure 8 5 M ultiple ap plication hos ts - single bac k u p host With this soluti on, multiple appli cation hos ts may be connect ed to a single or multiple disk arr ay s, w hic h are , in turn connec ted to a single dedicated bac kup ho st.
Figure 8 6 Disk array(s) - single host In cases w her e no dedi cated bac k up server is a vailable , both functi ons (applicatio n and back up) can be perfo rmed on the same cli ent (or host). Offline bac kup s of mail applicati ons, f or instance , could reduce the do wntime o f the application t o minute s instead o f hours in this w ay .
Figure 8 7 L VM mirroring - HP Storage W orks Virtu al Arra y only In the supported conf igur ations desc ribed pr ev iousl y , only Busine ss Cop y functio nality is possible w ith the HP Stor age W orks Virtual A rr ay integr ation .
Figure 88 Campus C luster with L VM Mirroring - HP Storage W orks Virtual Array only With this co nfigur ation , it is possible to emulat e Con tinuou s Access plus B usiness Cop y functi onalit y , w ith standar d clu ster failo ver f unctionality . This is o f ten r equir ed fo r missi on cr itical appli cations.
In the e ve nt that y ou want t o back u p data in a conf igurati on not listed , this does not mean that it cannot be suppo r ted . P lease contact y our local HP repr esentati ve o r HP Consulting t o in vesti gate the supportability of additional co nfi gurati ons.
Snapshot co ncepts 2 88.
1 4 M i c rosoft V olum e Sha do w Cop y ser vice In this c hapter This c hapter intr oduces the Mi cr oso f t V olume Shadow C opy serv ice (VS S) concept and its r ole in the back up and res tore pr ocess . It also outlines the bac kup and r estor e flo w when u sing this featur e.
VS S V olume Shadow Cop y ser vice (VS S) is a softwar e servi ce introdu ced by Mi cr osoft on Windo ws oper ating sy stems. T his servi ce collaborat es with the bac kup a pplication , applicati ons.
The e xample o f the hard war e pro vide r is disk arra y , whi ch ha s its har dwar e mechanism o f pro viding po int-in - time state o f a disk. A softw ar e pro vide r oper ates on ph ysical disks and uses so f twar e mechanism f or pr ov iding po int -in- time state on a disk.
Figure 8 9 Ac tors of the traditional bac k u p model Figure 9 0 Actors of th e VSS backup model In the tr aditional model, the bac ku p appli cation had to communi cate with eac h applicati on it back ed up indiv iduall y .
VS S benefits The ad vantage s of using V olume Shado w Cop y service ar e as fo llow s • A unifi ed back up interface f or all wr iters. • A unifi ed back up interface f or all shadow cop y pro vi ders. • W riter s pro vi de data integr ity at application le vel .
wr iters , and back up and res tore f unctionality . F or detailed inf ormation on the integr ation , see the HP Data Prot ector integr ation guide . VS S back up In case o f VS S -aw are w riter s’ bac kup , the consistenc y of data is pr o v ided at wr iter lev el and does not depend o n the back up appli cation .
VS S f iles y stem bac k up and r est or e Some appli cations ar e not aw are o f the V olume Shadow Copy s er v ice. Su ch applicati ons cannot guar antee consistenc y of data during the c reati on of a shadow copy . The VS S mechanism cannot coo rdinate the acti viti es of these a pplicati ons in or der to perfor m a consistent bac kup .
• Back ups can be perf ormed at an y time withou t locking out us ers . • The r e is lit tle or no impac t on the perfo rmance of the appli cation s ys tem during the back up pr ocess. Back up and r estor e VS S back up is implemented as an additi onal Windo ws f ilesy stem bac kup o n Windo ws Serve r 200 3 .
A B ac k up s cenarios In this appendi x This A ppendix des cribe s t w o scenari os: one fo r company XY Z and one for compan y ABC. Both co mpanie s plan to enhance their data sto rage s yste ms. T heir c urre nt back up soluti ons are de sc ribed along w ith the inheren t problems .
Def ine the periods o f time during w hic h back ups of spec ifi c sy stems can be done . • Local v ersus ne twor k back ups Deter mine whi ch s yst ems, that the bac ku p dev ices are connec ted to, ar e back ed up locally and w hic h are bac k ed up ov er the networ k.
Deter mine the administr ation and oper ations r ights fo r the back up s yste ms user s. C ompan y XY Z XYZ is a tr anslation agenc y pro viding the f ollow ing service s: • T ranslati on , locali .
Current de vices Pr ojected data (in 5 Y ears) Current data #Clients #Servers Depart. 2 HP Stor age W orks D A T2 4 autoloade rs 6 7 GB 2 2 GB 1 1 UX 1 AIX Other Languages 1 HP Stor age W orks D A T2 4 autoloader 3 1 GB 1 0 GB 5 UX 1 HP -UX Admin F igur e 9 1 on page 300 sho ws ho w the XYZ back up en v ir onment is or ganiz ed.
netwo rk share s. Emplo yees in the Other L anguages Depar tment als o w ork on Satur day s. Pr oblems with the c urr ent soluti on The c urr ent back up solu tion is n ot able to k eep pace w ith the gr owth r ate of XYZ . The ac tual back up proces s is very labor intensi ve .
Bac ku p str ategy r equir ements Req uirements After addr essing the ite ms under “ Consider ations ” o n page 297, the follo w ing r equireme nts hav e been identif ied f or the bac k up solution o f company XY Z: • Back up P olic y • F ull, w eekly back ups will occ ur and be completed w ithin 1 2 hours .
Pr oposed s olutio n Becaus e of the limitati ons of the c urre nt bac k up solutio n for bo th performance and enter prise-wi de management , ther e is a need to r edesign XYZ’s bac kup ar chitec ture and str ategy to meet its bu siness obj ecti ves .
Dev ices Projected Data (In 5 Y ears) Current Data Department * One HP Sto r age W orks D A T2 4 autoloader is c urren tly used to locall y back up the 1 2 GB of data . The other HP St orage W orks D A T2 4 autoloader is us ed to back u p the IDB and conf igur ation file s.
Figure 9 2 Proposed XYZ bac k up topol ogy • The C ell Manager maintains the Catalog Data base (CDB). This pr ov ides a minimum of 20 da ys of f ile and direc tory detail on the cur rent dat abase . Es timating the siz e of the IDB The In ternal Databas e Capac it y P lanning T ool was u sed to estimate the si ze o f the IDB in a year .
Figure 9 3 Inp ut parameters The r esults ar e show n in Fi gure 9 4 on page 306. In one year , the database is e xpected to gr ow to a ppro ximatel y 4 1 9 .7 5 MB. Figure 9 4 Results • Hard war e • Netwo rk All s yst ems should be on the same 1 00TX networ k for max imum perfor mance.
The bac kup de vi ces consist of an HP S torage W orks DL T 4 1 1 5w Libr ar y as w ell as tw o HP Sto r age W orks D A T2 4 autoloaders . Wh y use t he HP Stor ag e W orks DL T 4 1 1 5w Libr ar y? The HP S torage W orks DL T 4 1 1 5w Libr ar y has a single DL T4000 dr iv e with 1 5 slots .
The Data Pr otect or Catalog Data base is appr ox imately 0.4 GB in si z e. It is back ed up locally t o an HP Stor age W orks D A T2 4 autoloader , w hich has a sust ained data tr ansfer r ate of 2 MB/s or 7 GB/h . Data Pr otector b y default chec ks the integrity of the dat abase be for e the database is bac ked up .
T able 1 8 on page 309 sho ws the siz e and time requir ements f or these f ull back ups as o f today , as w ell as the fi ve y ear pro jection . T ab le 1 8 Remote full back u ps to the HP D L T 4 1 .
Wh y use le vel 1 inc r emental back ups? T o res tore the late st data, onl y two media s ets need to be accessed , one for the latest f ull back up and one for the lat est le vel 1 inc remen tal bac k up prio r to the r estor e point-in -time. T his simplifi es and speeds up r estor e consider ably .
Data pr otection de ter mines the amount of time until eac h medium can be r eused . Set data pr otecti on to permanen t so that data on the media is not o ve r wr itten unintenti onally . • Conc urr ency Set to 5 t o allo w up to fi ve Disk A gents to conc urr ently w rit e data to the HP Sto r age W orks DL T 4 1 1 5w Libr ar y .
autoloade rs. All ac tions ex cluding the ac tual mov ing of media to the v ault ar e done b y the softwar e solution , including quer ies done in ter nally in the dat abase to pr ev ent the administr ator fr om hav ing to find media that requir e ejec tion .
1 . Identif ies the medi a needed for r estor e. 2. Br ings the media fr om a vault , enter s the media in the HP Stor age W orks DL T 4 1 1 5w Libr ary or other dev ice and then s cans the media . 3. Selec ts the specif ic obj ect to be re stor ed using the List F rom Medi a option , if the media ar e not in the IDB.
Thr ee departments at ABC C ape T ow n use the Mi cr osoft S QL database to s tore the ir data and the compan y uses M icr osoft Ex change Serv er for mailing se rvi ces. The se databas es, c urre ntl y containing 1 1 GB and 1 5 GB of data, r especti vel y , ar e back ed up to 2 HP S torage W orks D A T2 4 autoloaders .
Back up media ar e denoted b y the name of the department, the name o f the server and fir st and last dates o n whi ch bac k ups we r e per f ormed on the media . At the end of eac h quar ter , media ar e sent for s torage to a ce ntral off site location .
Maximum do wntime T ype of data 6 hours Com pan y r esour ce data 1 day Pr oject data 2 day s P ersonal data This r ecov ery time mainly consists o f the time needed to access the media and the time r equired to ac tually r estor e data to a disk.
Data (in GB) Location 2 2 ABC Pr etori a 1 6 ABC Durban P lans for fu ture gr owth o f the amount of dat a ABC plans to gr o w at 1 5 to 20% per year .
Conf igur e cell A as the MoM cell fo r the ABC Cape T ow n env ir onment , cell D as the MoM cell f or the ABC Pr etor ia env ir onment, and ce ll F as the MoM cell f or the ABC Durban en vir onment . This conf igur ation is depic ted in Fi gure 9 6 on page 318.
The tw o cells at the ABC Durban MoM e nv ironmen t should also shar e a Centr ali zed Media Manageme nt Databas e. T his should be conf igur ed on the MoM of cell F to enable the shar ing of the HP Stor age W orks DL T 4 1 1 5w Libr ar y betw een the cells.
#SAP #UNIX clients #UNIX servers #Windo ws clients #Windo ws servers Cell MoM env ironment 1 2 1 5 1 1 2 B 1 1 2 4 20 2 C 3 3 4 D* ABC Pret oria 3 2 5 6 1 E 30 4 1 0 2 F* ABC Durban 2 9 2 1 1 1 p #S A.
Figure 9 7 ABC Cape To wn enterprise bac k up environment The tw o cells at the ABC Pr etori a MoM env iro nment should shar e a Centr aliz ed Media Manageme nt Databas e.
catalog pr otectio n (3 w eeks) , number of f ull back ups per w eek ( 1 ) , and number of inc rement al back ups per w eek (5). Figure 9 8 Inp ut parameters The r esults ar e show n in Fi gure 9 9 on page 322. In one year , the database is e xpected to gr ow to appr o ximatel y 66 7 .
All s yst ems in the same location should be on the s ame L AN for max imum perfor mance. U se the 1 00TX networ k to connect all the s ys tems in each of the locations and the W AN to connect the cells in the thr ee locations. T he 1 00TX netwo rk has a sustained dat a transfe r rate of 1 0 MB/s , or 36 GB/h , of data .
Wh y use the HP St or age W orks DL T 4 1 1 5w Libr ary? • The HP S torage W orks DL T 4 1 1 5w Libr ar y has a single DL T4000 dr iv e w ith 1 5 slots. It has a tot al compr essed st orage capac ity of 600 GB and a max imum sustained data tr ansfer r ate of 3 MB/s, o r 1 0.
libr ar y has two dr iv es and a sustained dat a tr ansfer r ate of 6 MB/s ( 2 x 3 MB/s) , or 2 1 GB/h. T heref or e , data is back ed up to this libr ar y in up to 5 hours . The pr ojected amo unt of data in fi ve y ears, 1 85 GB , would be bac ked up in 9 to 1 0 hour s, w hich w ould still be w ithin the acceptable 1 2 hours .
Description Location Media pool name IDB Pr etor ia P_DB_P ool HP Stor age W orks DL T 4 1 1 5w Libr ary Durban D_DL T_P ool HP Stor age W orks D A T2 4 autoloade rs Durban D_D A T_P ool IDB Durban D_DB_P ool • Back up Spec ifi cations Conf igur e back up spec ifi cations as f ollow s: • DB_A.
F ull Incr1 Incr1 Incr1 Incr1 Incr1 Ce ll C • SER VERS_A...G Back up spec ifi cations fo r the compan y’s serve rs to pr epar e for dis aster r ecov ery . Eac h time a new se r ver is ins talled, or an e xis ting serv er is upgr aded, this back up spec ifi cation is updated .
Time Backup da y Description Cell Name 2 3:00 Sunday Server s C SERVER S_C 03:00 Satur day IDB D DB_D 03:00 Satur day IDB E DB_E 2 3:00 F rida y Server s D SERVER S_D 2 3:00 Satur day Server s E SERVE.
Set data pr otecti on to 5 year s for all bac ku p spec ifi cations e xcept f or Ex change_A, whi ch is sued to bac k up per sonal mail . Set data pr otection f or this back up spec ifi cation to 3 months . • Conc urr ency Set to 5 t o allo w up to fi ve Disk A gents to conc urr ently w rit e data to the libr ar y .
• Displa y a list of media needed f or res tore and the ph y sical locati ons wher e the media ar e stor ed. • F ilter media fr om the media vi ew based o n spec ifi c cr iter ia , such as medi a w ith expir ed pro tection . • Re stor e • Re stor e by Query Req uests for r esto r es by query w ill be sent to the administr ator .
B F ur t her infor m a tion In this appendi x This a ppendix pr ov ides additi onal inf ormati on about some o f the aspects of Data Pr otector concepts , including back up gener ations , ex amples of automat ed media copy ing, and inter nationali z ation.
Figure 1 00 B ackup generations Y ou conf igur e D ata Pr otector t o automaticall y maintain the desir ed number of bac k up gener ations b y selecting the appr opriat e data and catalog prot ection dur ations, and sc heduling for unattended back ups , both full and incr emental .
Ex ample 1 : auto mated media cop y ing of f iles y stem bac ku ps Y our compan y has a MoM en vir onment w ith t w o cells, eac h containing 1 5 0 compute r s ystems (s er v ers and wo rks tatio ns). On aver age , each s y stem ha s 1 0 GB of data , whi ch means that y ou hav e 3000 GB o f data that you w ant to back up .
hav e 900 GB of dat a to bac k up . The data is di vi ded among back up spec ificati ons in the fo llo wing w ay: • Back upSpec1 (Dr iv e 1 ) - 300 GB • Back upSpec2 (Dr iv e 2) - 300 GB • Back .
Figure 1 0 1 Inc r1 backup and automa ted media copy in g F ull back up Conf igur ing back ups Y ou sc hedule your w eekly f ull back up on F rida y at 6 P M.
Again , you u se post-back up media cop ying to cop y the media used w ith Back upSpec1 and Back upSpec2 , and scheduled media copy ing to cop y media us ed in Back upSpec3 and Bac kupS pec4. The de vi ces and the data pr otecti on settings ar e the same as those u sed for the copy ing of the Incr1 bac kup .
Figure 1 02 Full backup and automated m edia cop ying Y ou sc hedule your monthly f ull back up on Sunda y at 6 AM. This bac kup is int ended fo r ar chi v ing purpo ses , so it is normall y not copied . F igur e 1 0 3 on page 338 pres ents an ov ervie w of the time whe n the dev ices ar e busy .
Figure 1 03 Overvie w of ba ckup and automated medi a cop y s essions Ex ample 2 : automated medi a copy ing of Or acle data base back ups Y our com pan y has an Orac le database of the si z e of 500 GB . Y ou w ant to perfor m a full bac kup o f the database dail y .
F ull back up Conf igur ing back ups Y ou sc hedule your daily full bac kup eac h day f r om Monday to F ri day at 6 P M. T he data pr otectio n is set to 4 wee ks. Y ou ha ve 5 00 GB of data to bac k up . Y ou use Dr i ve 1 , Dri ve 2 , Dri ve 3, and Dr iv e 4.
Figure 1 05 Overvie w of ba ckup and automated m edia cop y s essions Inte rnati onali z ation Inter nationali z ation is a wa y to design and im plement a s oftwar e pr oduct s o that the pr oduct in.
F ile name handling Handling file name s in a heter ogeneous en vir onment (differ ent oper ating sy stems w ith differ ent local settings, all in o ne cell) is a signifi cant challenge .
UNIX incom patibility e xample Thr ee user s wor king on a Solaris s ystem w ithout Data Pr otecto r installed, eac h using a differ ent c haracte r set , cr eate files o n the same files ystem o utside the A SCII c haract er r ange.
• the file s to be res tored ar e select ed in the GUI • Data Pr otector sear ches the tape f or the spec ified data and r estor es it • the or iginal file names (or iginal copi es fr om the tap.
F ur ther inf ormati on 3 44.
G los sar y access rights See us er r ights . ACSLS (S tor age T ek spec ific ter m) The A utomated Cartri dge Sy stem L ibr ar y Server ( A CSLS) softw are that manages the A utomated Cartr idge S y stem ( A CS) . Active Dir ec tory (Windo ws s pecif ic term) T he direc tor y serv ice in a Windo ws netwo rk.
an ar chi ved r edo log is deter mined by the mode the databas e is using: • ARCHI VEL OG - The filled online r edo log file s ar e ar chi ved bef ore the y are r eused . The data base can be r ecov er ed if an instance or a disk f ails. A “hot” bac ku p can be perfor med only w hen the database is r unning in this mode.
ass oc iated w ith managing data and disk and pro vi des str iping and mirr or ing capab ilities t o optimi ze pe rfor mance. automigration (VL S specif ic ter m) The func tionality that allow s data .
located (dr iv e on Windo ws and mount po int on UNIX). Fo r integr ation obj ects — back up str eam identif icati on, indicating the back ed up databas e/application it ems. • Desc ription: F or files y stem ob jects — unique ly de fines obj ects w ith identical c lient name and mount po int.
See also appli cation s yst em , tar get volume , and r eplica . backup types See inc rement al back up , diffe renti al back up , tr ansaction bac ku p , full bac kup , and de lta back up . backup to IAP A Data Pr otector ba sed bac kup to the HP In tegrated A rc hiv ing P latform (IAP) a ppliance.
See also r eplica , sour ce volume , snapsh ot , and CA+BC EV A . BC Proces s (EMC S ymme tri x spec ific t erm) A pr otected sto r age en vir onment soluti on that has def ined spec ially conf igur ed EMC S ymmetr ix dev ices a s mirr ors or B usines s Continuance V olumes to pr otect data on EMC S ymmetr ix st andar d dev ices .
See also BRB ACK UP , and BRRES T ORE . BRBA CKUP (S AP R/3 spec ifi c term) A n SAP R/3 bac kup t ool that allo ws an online or off line back up of the contr ol file , of indi vidual data file s, or of all table spaces and, if nece ssary , of the online r edo log file s.
CAP (Sto r age T ek spec ific te rm) C ar tri dge Access P ort is a port built into the door panel o f a library . The pur pose is t o enter o r ej ect media . catalog protection Def ines how long inf ormati on about back ed up data (suc h as file name s and file v ersi ons) is kept in the IDB .
Database (CMMDB) Change Journal (Windo ws s pecif ic term) A W indow s files ystem f eature that logs a r ecord of eac h change as it occ urs to the f iles and dir ector ies on a local NTF S volume .
client backup with disk disco very A back up of all f ilesy stems moun ted on a c lient . When the back up starts , Data Pr otector disco ver s the disks on the clie nts . Clie nt back up with disk dis cov er y simplif ies back up conf igurati on and impr ov es back up cov erage o f sy stems that often moun t or dismount disks .
betwee n the MoM cell and the other Data Pro tector cells is highl y r ecommended See also MoM . COM+ Registr ation Database (Windo ws s pecif ic term) T he COM+ R egistrati on Database and the Windo ws Regis tr y stor e COM+ a pplication attr ibutes, c lass attribut es, and comput er -lev el at tr ibutes.
the CR S runs under the acco unt of the u ser spec ified at installati on time. On UNI X sy stems, it r uns under the account root . CSM The Data Pr otector C opy and C onsolidati on Sessi on Manager pr ocess contr ols the objec t copy and obj ect consolidati on ses sions and runs on the C ell Manager s yst em.
the y ha ve co mmon char acteris tics and shar e a common CA EV A log . See also cop y set . database server A compute r with a lar ge database sto red on it , such as the S AP R/3 or Mi cr osoft S QL database . A server has a dat abase that can be access ed by cli ents.
a single de v ice gr oup . All dev ices in a de vi ce grou p must be on the same EMC S ymmetr ix unit . Y ou can use a de vi ce group to iden tif y and w ork w ith a subse t of the a vaila ble EMC S ymmetr ix de vi ces. dev ice streaming A dev ice is str eaming if it can feed eno ugh data to the medium to k eep it mov ing forwar d continu ousl y .
directory junction (Windo ws s pecif ic term) Dir ectory junc tions use the r eparse point co ncept of W indow s. An NTF S 5 direc tory junc tion allo ws y ou to redir ect a dir ectory/file r equest to an other location .
the back ed up data , and incr ease the data av ailability and accessib ilit y for r estor e. T he back up stages consist o f backing up data to o ne media type f irst (f or ex ample disk) and later copy ing it to a differ ent media type (f or ex ample tape).
can also r ead the data fr om the medium and send it to the compute r sy stem. dri ve-based encr yption Data Pr otector dr iv e -based encry ption u ses the encry ption func tionality of the dri ve . While perfo rming the back up , the dr i ve e ncry pts both the data and the meta-data that is w ritten to the medium .
and to Data Pr otector u sers w ho are gr anted the Reporting and notifications user r ights . Y ou can vi ew or delet e all ev ents in the Ev ent L og. Ev ent Logs (Windo ws s pecif ic term) F iles in whi ch W indow s logs all ev ents, suc h as the starting or st opping of serv ices and the logging on and off of u sers.
bi-dir ectional tr ansmissi on of lar ge data file s and can be deplo y ed betwee n sites kilome ters a par t . Fibr e Channel connec ts nodes using thr ee ph ysical topo logies: point-to -point , loop, and s witc hed.
See also pr imary v olume and MU number . flash reco very area (Or acle spec ific t erm) F lash reco very ar ea is an Or acle 1 0g/1 1g managed dir ectory , files ys tem, or A utomatic S torage Management disk gr oup that serv es as a centr aliz ed stor age ar ea for f iles r elated to back up and reco very (r ecov er y file s) .
the dir ectory Data_Protector_program_data ConfigServerOptions (Windo ws S er ve r 2008), Data_Protector_home ConfigServerOptions (other Windo ws s ystems), or /etc/opt/omni/server/options (HP -UX or Solar is sy stems).
hosting s ystem A w orking Data Pr otector c lient used f or Disk Deliv ery Disaster Reco very w ith a Data Pro tecto r Disk Agent installed . HP Operations Manager HP Oper ations Manager pr ov ides po werf ul capabilitie s for oper ations management o f a lar ge number of s yst ems and applicati ons in a networ k.
info rmati on or method inv ocation , and retur ns standardi zed r esponses . See also HP S torage W orks EV A SMI-S Agent and C ommand Vi ew (CV) EV A . HP Stor ag e W orks Virtual Arr ay L UN A logical partitio n of a ph ysi cal disk within an HP S torage W orks Virtual Ar ra y .
See also bac kup ty pes . incremental mailbo x bac k up An inc remen tal mailbo x back up backs up all the c hanges made to the mailbo x af ter the las t back up of any ty pe. incremental1 mailbo x bac k up An inc remen tal1 mailbo x back up backs up all the c hanges made to the mailbo x af ter the las t full back up .
Information S tore (M ic ro soft Ex change Serv er specif ic ter m) The Mic ro soft Ex change Server s er v ice that is re sponsible for s torage management . Infor mation St or e in Micr osoft Ex change S er ve r manages tw o kinds of st or es: mailbox s tores and pu blic folde r stor es.
ISQL (S ybase spec ific te rm) A S ybase utility us ed to perform s ys tem administr ation tasks o n S ybase S QL Ser v er . Jav a GUI Client The Jav a GUI Clie nt is a compo nent of the Ja va GUI that con tains only u ser interface r elated functi onalities and r equire s connection to the Ja va G UI Server to f unction .
library Als o called autoc hanger , juk ebox , autoloader , or ex changer . A libr ar y contains medi a in r epository slots. E ach slot ho lds one medium (fo r e xam ple, DDS/D A T). Media are mo ved betw een slots and dr iv es by a r obotic mechanism , allow ing random access to medi a.
An L CR copy is us ed for disas ter reco very becaus e you can s witc h to the L CR copy in a fe w seconds . If an L CR copy is us ed fo r back up and if it is located on a diff erent disk than the o riginal data , then the I/O load on a produc tion databas e is minimal.
login ID (Micr osoft S QL Server spec ifi c term) T he name a user u ses to log on to Mi cr osoft S QL Server . A login ID is vali d if Mic r osoft S QL Server has an entry f or that user in the s yst em table s yslogin .
mailbo x store (Mi cr osoft Ex change Serve r spec ific t erm) A part of the Info rmati on Stor e that maintains inf ormati on in user mailbo xes . A mailbo x stor e consists o f a binar y r ich-te xt .edb file and a str eaming nativ e interne t conten t .
Dur ing a r estor e sessi on , a Media Agent locate s data on the back up medium and sends it to the Disk A gent. T he Disk Agent then w rites the data t o the disk. A Medi a Agent also manages the r obotics contr ol of a libr ar y . media allocation policy Deter mines in w hich seq uence media ar e used f or back up .
merging T his defines one mode to r esol ve f ile conflicts dur ing re stor e. If the file t o be r estor ed alread y ex ists at the destinati on, the one w ith the more r ecent modif icati on date is kept . F iles not pr esent on the disk ar e alw ay s re stor ed.
MMD The Medi a Management Daemon pr ocess (serv ice) runs on the Data Pr otector C ell Manager and contr ols media management and dev ice oper ations .
OBDR capable dev ice A dev ice that can em ulate a CD-ROM dr iv e loaded with a bootable disk and can th us be used as a bac kup or boot de vi ce fo r disast er reco very purpos es.
per iod (sev er al minut es or hours). F or instance , for back up to tape , until str eaming of data to the ta pe is finished . • F or ZDB methods, the data base is also pu t into the quies cent state , but f or the peri od of the data repli cation pr ocess onl y (se ver al seconds) .
• F or ZDB methods, bac kup mode is r equir ed for the short per iod of the data r eplication pr ocess onl y (sev er al seconds). Normal dat abase ope ration can the n be resumed f or the r est of the back up pr ocess. In some cas es, tr ansaction log s may also ha ve t o be back ed up to allo w a consistent data base to be r estor ed.
ov er write A n option that def ines one mode to re solv e file confli cts during r estor e. All f iles ar e rest ored fr om a back up ev en if they ar e older than e xisting f iles. See also mer ging . ow n ership Back up ow nership affec ts the ability of user s to see and re stor e data .
COP Y - The mirr or ed pair is cur rentl y re-sy nchr onizing . Data is tr ansferr ed fr om one disk to the other . The disks do not contain the s ame data . • • P AIR - The mir ror ed pair is completel y sy nchr oni zed and both disks (the pr imary volume and the mirr ored v olume) contain i dentical data .
pre-ex ec A back up option that e xec utes a command or sc ript bef ore the back up of an ob ject or bef ore the en tire se ssi on is started . Pr e -e xec co mmands ar e not supplied b y Data Pr otector . Y ou need to cr eate your o wn . The y can be writte n as e xec utables or batc h files on W indow s and as shell sc ripts o n UNIX.
instance tr anslates the commands int o a sequence o f low le vel S CSI commands . ra wdisk backup See disk image bac k up . RCU See R emote Contr ol Unit (R CU) . RDBMS Re lational Database Manage ment S ys tem. RDF1/RDF2 (EMC S ymme tri x spec ifi c term) A type of SRDF de vi ce group .
Reco very M anager (RMAN) (Or acle spec ific t erm) An Or acle command-line interf ace that dir ects an Orac le Server pr ocess to bac k up, r estor e, or r ecov er the databas e it is connected to . RMAN uses e ither the reco very catalog or the contr ol file to sto r e informati on about back ups .
is r eplicated. Ho w ev er , if a vo lume manager is us ed on UNIX, the wh ole volume or disk gr oup cont aining a back up obj ect (logical v olume) is repli cated. If partitions ar e used on W indow s, the wh ole phy sical vo lume containing the s elected partition is r eplicated.
RSM (Windo ws spec ifi c ter m) Re mova ble Stor age Manager (RSM) include s a media management serv ice that fac ilitates communi cation among appli cations , roboti c changer s, and media libr arie s. It enables multiple a pplications to shar e local r obotic media libr arie s and tape or disk dri ve s and to manage r emov able media.
shadow cop y (Mi cr osoft VS S spec ific te rm) A volume that r epr esen ts a duplicat e of the ori ginal vo lume at a certain poin t in time. The data is then bac ked up f rom the shado w copy and n ot fr om the or iginal volume .
number . T o read a medium , a robo tic mec hanism mov es the medium fr om a slot into the dr iv e. SMB See split mir ror bac kup . smart copy (VLS spec ifi c term) A cop y of the back ed up data cr eated fr om the v ir tual tape to the ph ysi cal tape library .
use . Ho w ev er back gr ound copy ing proces ses nor mally con tinue after cr eation. See also sna pshot . source (R1 ) device (EMC S ymme tri x spec ifi c term) An EM C Sy mmetri x dev ice that partic ipates in SRDF operati ons with a tar get (R2) de v ice.
split mirr or restor e (EM C S ymmetr ix and HP S torage W orks Disk A rra y XP spec ific ter m) A pr ocess in whi ch data bac k ed up in a ZDB- to - tape or a ZDB-to -disk+tape sessi on is re stor ed fr om tape media t o a split mirr or r eplica, w hich is the n s ynchr oni z ed to the sour ce volumes .
fo r a single -dri ve de vi ce and multiple S CS I entri es are r equir ed fo r a multi-dr iv e library dev ice . stackers De vice s with multiple slots f or media sto r age usuall y with onl y one dr iv e. A stac ker s elects media fr om the stac k sequentiall y .
s ynthetic backup A back up soluti on that produ ces a s yntheti c full back up , an equi valent to a con ven tional full bac kup in te rms of data , withou t putting str ess on the pr oduction s er v ers or the netwo rk . A s yntheti c full back up is cr eated fr om a pr ev iou s full back up and an y number of incr emental bac ku ps .
tablespace A part of a databas e stru cture . E ach databas e is logicall y di v ided into one or mor e tablespace s. E ach t ablespace ha s data file s or ra w volumes e xc lusiv ely as soci ated with it . tapeless backup (ZDB specific term) See ZDB to disk .
TNSNAME S.OR A (Or acle and S AP R/3 specif ic ter m) A net w ork conf igurati on file that co ntains connec t desc riptors ma pped to service name s. The f ile may be maint ained centr ally or locall y , for us e by all or indi vidual c lients . transaction A mechanism f or ensur ing that a set of acti ons is tr eated as a single unit of w ork .
UIPro xy The Jav a GUI Server ( UIProxy s ervi ce) runs on the Data Pr otector C ell Manager . It is respo nsible for communi cation betwee n the Java GUI C lient and the Cell Manage r , moreo ver , it perfor ms business logi c operatio ns and sends only impo rtant info rmati on to the clie nt .
user r ights . Users ha ve the acces s r ights o f the user gr oup to whi ch the y belong. vaulting media The pr ocess o f stor ing media to a saf e and remot e place . The media ar e bro ught bac k to the data cen ter w hen they ar e needed fo r r estor e or are r eady f or reu se in subseque nt bac k ups.
virtual tape (VLS spec ific te rm) A n ar chi val stor age techn ology that backs up data to disk dr iv es in the same w ay as if it w ere being stor ed on tape . Benef its of virtual tape s ystems inc lude impr ov ed back up and r ecov ery speed and lo w er operating cos ts.
See also r es ync mode , sour ce vo lume , primary v olume (P -V OL) , r eplica , secondary volume (S-V OL) , and replica s et rot ation . VxF S V eritas Jo urnal F ilesy stem . VxVM (V eritas V olume Manag er) A V eritas V olume Manager is a s ys tem for managing disk space on Solar is platfor ms.
XBS A inter face (Informi x Server s pecif ic term) ON-Bar and Data Pr otector communi cate with eac h other thro ugh the X/Open Back up Serv ices A pplication Pr ogramme r's Interf ace (XBS A).
ZDB to tape (ZDB spec ific te rm) A for m of z ero do wntime bac kup w her e data in the r eplica pr oduced is str eamed to a bac k up medium, typi cally tape . Instant r ecov ery is not possible f rom suc h a back up , so the repli ca need not be re tained on the disk ar ray after bac k up completion .
Gloss ary 40 2.
Ind e x A adding data to medi a dur ing back ups , 148 ADIC (EMAS S/GR A U) AML , 162 admin user gr oup , 185 alarms , 208 alter nati ve disast er reco very methods , 131 oper ating sy stem v endors , 131 thir d-par ty tools , 131 ANS I X3.
back up w ith disk discov ery , 225 Back up Agen ts , 42 back up cli ent split mirr or back up , 267 back up cli ent as failo ver s er ve r snapsho t backu p , 286 split mirr or back up , 268 back up .
benef its disk back up , 254 s yntheti c backu p , 258 V olume Shadow C opy serv ice , 293 benef its of online integr ations , 240 block si ze back up de vice s , 158 def ault , 158 dev ices , 158 per.
cli ent sy stems , 42 cli ents , 42 installing , 64 maintaining , 64 clu ster heartbeat , 80 clu ster (def inition) , 79 clu ster integr ations o ve r vi ew , 82 clu ster node , 80 clu stering , 79 - .
cr eating cells mi xed en vir onment , 66 UNIX en vir onment , 64 Windo ws domains , 65 Windo ws w ork gr oups , 66 Windo ws en vir onment , 65 CR S , 220 D daily main tenance IDB operati on , 196 dat.
databas e on the UNIX Cell Manager s IDB for mat , 189 IDB location , 189 databas e on the Windo ws Cell Manager IDB for mat , 188 IDB location , 188 databas e arc hitectur e , 189 databas e gr owth a.
dev ice lists , 155 dev ice loc king , 159 dev ice shar ing in clus ters , 180 dev ice shar ing in SAN , 175 dr i ve s , 177 r obotics , 177 dev ice str eaming (def inition) , 156 dev ices , 49, 68, 1.
Dir ect Libr ary Access , 179 dirty dri ve detecti on , 164 disast er , 128 Disast er Reco very Phase 3 , 129 disast er reco very , 129 Disast er Reco very concepts , 128 o ve r vi ew , 128 Phase 1 , .
e x change rs , 162 See also libr ari es e xpir ed catalog pr otecti on , 201 e xporting media , 102 IDB operati on , 195 r emov ed objects , 195 F fac tors affec ting rest ore dur ation , 125 fac tor.
I IDB , 187 adv antages , 187 ar chitectur e , 189 Catalog Data base , 191 Detail Cat alog Binary File s , 192 in the Manager -of-Managers en vir onment , 189 management , 196 Media Manageme nt Databa.
incr emental bac kup s , 71 types , 93 Indir ect Sto r age Are Netw orks , 178 Indir ect Libr ary Access L ibr ar y Acces s , 178 Indir ect Libr ary Access , 179 influence o f logging leve l and catal.
lock name s , 159, 177 log all detailed inf ormation Catalog Data base , 100 log dir ectory names only Catalog Data base , 100 log lev el of inf ormation , 104 logging lev el IDB siz e and gro wth , 1.
media pools , 135, 309, 325 def ault , 136 pr oper tie s , 136 usage e xample s , 140 Media A gents , 42 Gener al Media Agen t , 165 media allocati on polic ies , 144 media allocati on polic ies , 136.
monitor ing , 38, 210, 211 mount pr ompt handling , 111 mount r equests , 224, 232, 235 automating , 224 notif ication , 224 r esponding , 224, 228 mount r equests (r estor e sessi ons) , 228 MSM , 23.
planning cells , 62 - 67 Cell Manager s , 64 Installati on Server s , 64 number o f cells , 62 planning perfor mance , 67 - 73 back up types , 71 compr essio n , 68 dev ices , 68 dir ect back ups , 68.
r epor ting , 38, 211 r epor ting and notif ication , 311, 329 br oadcasts , 207 e -mail , 207 e xam ples , 212 HTML , 207 SNMP , 207 r equireme nts Dir ect back up , 249 r esponse time , 208 r estor .
Serv ice Manageme nt , 37, 205 - 215 Appli cation R esponse Mea surement , 207 monitor , 210 notif ication , 211 oper ativ e analys es of tr ends , 206 o ve r vi ew , 205 r epor ting , 211 serv ice ma.
snapsho t backu p , 275 applicati on clie nt , 277 ar chi ve log bac ku p , 278 back up cli ent , 277 back up cli ent as failo ver s er ve r , 286 concepts , 276 conf igurati on, Cam pus Clu ster w it.
standalone de vi ces , 161 standalone de vi ces , 160 standalone f ile dev ice , 255 standar d re stor e vs par allel r estor e , 228 standar d back up vs disk dis cov ery , 225 stati c dri ves , 180 .
V va ulting , 134, 151 - 153, 311, 329 def inition , 151 r estor ing , 153 r estor ing fro m a v ault , 312, 330 va ulting usage ex ample , 152 V eritas C luster , 79 v ir tual clu ster n odes , 84, 8.
Een belangrijk punt na aankoop van elk apparaat HP (Hewlett-Packard) B6960-96035 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen HP (Hewlett-Packard) B6960-96035 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens HP (Hewlett-Packard) B6960-96035 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding HP (Hewlett-Packard) B6960-96035 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over HP (Hewlett-Packard) B6960-96035 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van HP (Hewlett-Packard) B6960-96035 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de HP (Hewlett-Packard) B6960-96035 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met HP (Hewlett-Packard) B6960-96035 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
