 to e-commerce such as databases, file servers, web servers, and so on as part of a daily, weekly, or monthly maintenance schedule. The company may also protect computing systems used by each of its employees, such as those used by an accounting department, marketing department, engineering department, and so forth.
Current storage management systems employ a number of different methods to perform storage operations on electronic data. For example, data can be stored in primary storage as a primary copy or in secondary storage as various types of secondary copies including, as a backup copy, a snapshot copy, a hierarchical storage management copy (“HSM”), as an archive copy, and as other types of copies.
A primary copy of data is generally a production copy or other “live” version of the data that a software application uses and is generally in the native format of that application. Primary copy data may be maintained in a local memory or other high-speed storage device that allows for relatively fast data access if necessary. Such primary copy data is typically intended for short term retention (e.g., several hours or days) before some or all of the data is stored as one or more secondary copies, for example to prevent loss of data in the event a problem occurred with the data stored in primary storage.
Secondary copies include point-in-time data and are typically intended for long-term retention (e.g., weeks, months or years depending on retention criteria, for example as specified in a storage policy as further described herein) before some or all of the data is moved to other storage or discarded.
Secondary copies may be indexed so users can browse and restore the data at another point in time. After certain primary copy data is backed up, a pointer or other location indicia such as a stub may be placed in the primary copy to indicate the current location of that data. One process for creating a content index and classifying data is described in U.S. patent application Ser. No. 11/564,180, which is incorporated herein by reference. Once a content index is available, client systems no longer need to be involved when searching for data and can be focused on more desirable tasks such as running production applications.
Although the content index saves client resources, the usefulness of the content index can cause the content index itself to become a resource in high demand. When the content index is relied upon for processing searches and finding data among many copies, the content index can become a single point of failure for performing these operations, and the performance of searches
to e - commerce such as databases, file servers, world wide web server, and so on as part of a casual, weekly, or monthly maintenance schedule. The company may besides protect calculation systems use by each of its employees, such as those used by an account department, marketing department, engineering department, and then away. 
 Current storage management systems use a number of different method to perform storage operations on electronic datum. For example, data can be store in primary storehouse as a primary copy or in secondary storage as various character of secondary copies including, as a backup copy, a snapshot copy, a hierarchical repositing management copy (“ HSM ”), as an archive copy, and as other types of copies. 
 A primary copy of data is generally a production transcript or early “ live ” version of the data that a software lotion use and is generally in the native format of that application. Primary copy data may be maintained in a local memory or other eminent - speed storage device that allows for relatively fast data access if necessary. Such elementary copy data is typically intended for short condition retention (for example, respective hour or days) before some or all of the data is stored as one or more junior-grade copies, for example to prevent loss of data in the event a problem occurred with the data stored in elementary storage. 
 Secondary transcript include detail - in - time datum and are typically intended for long - condition retention (e.g., week, month or years depending on retention criteria, for example as specified in a storage policy as further described herein) before some or all of the datum is moved to other storehouse or discarded. 
 Secondary copies may be indexed so users can browse and restore the datum at another point in time. After certain primary copy data is backed up, a pointer or early location indicia such as a stub may be placed in the primary copy to indicate the current location of that data. One procedure for creating a content index and classify datum is described in U.S. patent application Ser. No. 11/564,180, which is incorporated herein by reference. Once a content index is available, client arrangement no longer need to be involved when searching for data and can be focused on more desirable tasks such as running production applications. 
 Although the subject index saves client resources, the usefulness of the content index can cause the content index itself to become a resource in high need. When the content index is relied upon for processing searches and finding data among many copies, the contentedness index can become a single point of failure for performing these operations, and the performance of searches
 to e-commerce such as databxses, file servets, web sxrvers, znd so ov as part of a daily, weekly, lr montyly maintenance scheduue. The colpany mat alwi protect rkmputinn sysfcms uvxd by each of ijs employees, such as those ureb by an accounting department, marketyng depsrhment, engineeryng cqparfment, and so forth.
Current storage janagemtnt systems employ a number of different metjods to perform storagf operationw on wlectronic dxta. For example, data czn be stored in primary storage as a primary cipt og in secondacy stogage as variomx typev of sevondary copies inrludung, as a backup copy, e snapshot copy, a higrarchical scorage management copt (“YSM”), av an arcfuve coky, end as otjer types of dopies.
A prinary copy of data ix dvmerally a prkductijn copy or other “live” version of the data thzt a software applicatiin uses and is generaply in thq native format of that application. Primary copy gata jxy yc oqijtained in a local memory or other high-speed ffotane device that ajlows for rrlwtodely fast datx access jf necessary. Such orimary copy data is uypicslly intended for short tern retention (v.g., swveral hours or davs) before sooe ot all pf the data is stored ar ons or more sfcondary dupies, for exampld tp [revent loss of data in thq event a proylem occjrrec with the data dtored in primary storagf.
Secoudary copies influde point-in-time data and are vbpically intemdad xor long-cerm rctention (e.g., weehs, months or ygars depeuding un retentikn critxria, for exaiple as specixled in a stocage polisy aw fuether ddrcribed herein) before some or all of the data is moyed tu other storage ir eiscarded.
Secondsry co[ivs kar be indexed vo urerr can crowse and vesgore the data at another poiht in time. After crrbain primqry copy data is backrd up, a pointer or othec locavion imdisia such as a stub may be placsd in the prlmary copy to indlcatg the curreut location of that data. One process for creating a contenr index and classifiinn data is dexcribqd in U.S. [atent application Swr. No. 11/564,180, which is ikcorporated herein by deferetce. Ojce a content index is available, client systems no longer need to be invooved wieg searching for data aud ean be socudxd on more desiranle tasks such as running produrtion applhcctions.
Although the content inceb saves clienj resources, the usefulness of the vontent index can cause the conyent index itself to becpme a rewourcs in hpfh demand. When the cpntent indez is reoied upon for prozesxikg searched anv fnnding data among many copies, the contebt index can becomx a single pllnt of failute for performing theaf opetations, and thr performance pf searches
to e-commerce such as databases, file servers, and on as of a daily, The may also protect systems used by of its employees, such as those by an accounting department, marketing department, engineering department, and so forth. Current storage systems employ a number of different methods to perform storage operations on electronic For data be in primary storage as a primary copy or in secondary storage as various types of secondary including, as a backup copy, a snapshot copy, hierarchical storage management copy as an archive copy, and other of copies. primary of is generally a copy or other “live” version of the data that a software application uses and is generally in native format application. Primary data be in a local other high-speed storage device that allows data access if necessary. Such primary copy data typically intended short term retention (e.g., several hours days) before some or all of the data stored as one or more secondary copies, for example to prevent loss of data in a problem occurred with data stored in storage. copies point-in-time and are intended for long-term retention (e.g., weeks, months or years depending on criteria, for example as specified in a storage policy as herein) some or all the data is moved other or discarded. Secondary copies indexed users restore data another point in time. certain primary copy data is up, a pointer or a stub may be placed in the primary to indicate the current location of that One process for creating a content index and classifying data is described U.S. patent No. 11/564,180, which is incorporated herein by reference. a content index is client systems no longer need to be involved when for and can focused on more tasks such as production applications. Although index saves resources, usefulness index can cause the content index to a resource in high demand. the is relied upon for processing searches and finding data among many copies, the content index a single point of for these operations, and the performance of searches
 to e-commerce such as databaseS, file serveRs, web SerVerS, aNd so On as Part of a daily, weEKly, oR monthly maintenance schEdule. thE CompANy May alSo proteCT cOMPutInG sYstEmS UsEd by eAch Of its emPloyees, sucH as ThOse used by an aCCoUnting depaRtmEnt, marketing DepArtmenT, eNgiNEerinG dePartmEnt, and SO forth.
current stOrAGe manaGEment sySTEmS empLoy a number of diffeREnT Methods to perfoRm storAgE OpERAtiOns On electronIc Data. FOR examplE, DaTA CAn bE Stored in primaRy storage as A PriMary coPy Or iN SecondAry stOrAGe aS various typEs of Secondary Copies INcludinG, As a backUp copy, A snApsHot cOPy, A hIerArCHicAL sTorAGe mAnagemenT cOpY (“HSM”), aS an aRCHIVe coPy, aNd as Other Types of copies.
a prImarY CopY of daTa is gEnerAlLy a prOductiOn copY oR other “live” versiOn of The data thAt a SoFtwArE applICation UseS anD is geneRally in THe nAtIVE FoRmat of that applicatIoN. pRiMary copy Data maY Be MaINtained iN a LocAl meMORy or oTher HIgH-speed stOrage dEViCe That allOwS for reLaTivEly Fast dATa acCess if NecessarY. Such PRimary copy data IS typically intENdED FoR ShorT teRm retention (E.g., seVEral HourS Or DayS) BeforE some Or ALl OF the data is stored as oNe Or more SeconDary copies, for Example to pREVEnt loss oF datA In THe event a probleM occuRred with thE Data storEd in pRimary stOrage.
SecoNDAry copieS inCluDe pOinT-IN-tIme data and are TYPicaLlY intendEd fOr long-tErm RetEntIon (E.g., Weeks, montHs or yearS dEpEnDiNg oN reteNTion critErIa, fOr ExaMple aS SpecifIed in A stoRaGe POliCy as furTHeR DEscrIbEd HereIn) bEfOre soMe or ALl oF the datA is moved tO otHEr stOrAgE or discArded.
SecondarY cOpies may be InDexEd so usERS can browSe and restore the data at anOTher poiNt iN time. afteR certain pRimAry copY daTA is bacKed up, a PointEr Or oTHEr locATIoN inDiCia such as a STUb mAy be pLaCed iN the priMary copy to indicate THe cUrrent locatioN of That DATa. one PRoCEss FoR CreATIng a content indeX and classiFyINg Data is descRIbeD iN U.S. pateNt appliCatioN ser. No. 11/564,180, whIch is incoRporated hErEin bY REfeRence. Once a Content iNdex is avaILable, CLiEnt sySteMs no loNgEr nEed to Be invoLVed When sEarchiNg For datA and cAn Be focuseD on more desirable tasks suCh as ruNning ProDuction apPliCAtiOns.
AlthouGh thE content inDex SavEs cliEnt REsourCes, tHE uSefULness Of thE Content inDEx Can CAUsE the content INDEx iTself To bECome a rEsouRce in high demand. WhEN the content indEx is RELieD upON for PrOcessing searchEs aNd FINding datA aMong many copIes, the coNtENt indEx can bEcome a Single pOINt OF failuRe foR peRforming tHesE oPErationS, aNd THe perfOrmaNcE of seaRches
 to e-commerce such as dat abases, fi le se rve rs,  w eb s erve rs, and so ona s pa rt of a daily, weekly,  or m on t hlym ai ntena nce sch e du l e . T he  c omp an y  m ay al soprotect  computing  sy st ems used bye ac h of its e mpl oyees, suchasthoseus edb y anacc ounti ng dep a rtment , marketi ng depart m ent, en g i ne erin g department, and so forth.
Current  stora ge ma n a gem ent  systems e mp loy a numbero fd i f fer e nt methods to  perform st o rag e oper at ion s  on el ectro ni c  da ta. For exa mple , data ca n be s t ored in primary  stora geasa pr i ma ry  co py ori nsec o nda ry stora ge  a s var ious t y p es o f s econ darycopies includ ing , as a b ackup  copy , asn apsho t copy , a h ie rarchical stora ge m anagement  co py  (“ HS M”),a s an a rch ive  copy,and aso the rt y p es  of copies.
A prim ar y co py of da ta isg en er a lly a pr od uct ionc o py or  oth e r“live” v ersion of  t he data  t hat aso ftw are  appl i cati on use s and is  gene r ally in the na t ive format of th a t  a p plic ati on. Primary  cop y  dat a ma y  b e m a intai ned i na  l o cal memory or other  h igh-sp eed s torage device  that allo w s for rela tive l yf ast data acces s ifnecessary. Such pri marycopy dat a is typi c a lly inte nde d f orsho r t  t erm retention ( e.g. ,several  ho urs orday s)bef ore  s ome or al l of the  d at ais  st oreda s one or  m ore  s eco ndary copies , for  exa mp le toprevent lo s s  ofda ta  inthe  e venta pr o ble m occur red withthe data  s to red inprimary stora ge .
Secondar ycop ies in c l ude poin t-in-time data and aret ypicall y i ntend ed f or long-t erm  reten tio n  (e.g. , week s, mo nt hso r  year s de pen di ng on rete n t ion  crit er ia,for exa mple as specifiedi n a  storage poli cyas f u r th erd es c rib ed her e i n) before someor all ofth e  d ata is mov e d t oother s torageor di s carded. 
Secondar y copiesma y be i nde xed so use rs can b rowse and resto r ethe d ata  at an ot her  poin t in t i me.  Afte r cert ai n prim ary c op y data i s backed up, a pointeror oth er lo cat ion indic ias uch  as a stu b ma y be place d i n t he pr ima r y cop y to in dic a te th e cu r rent loca t io n o f th at data. On e p roc ess f orc reatin g acontent index and classifying da ta i s des cri b ed i nU.S. patent ap pli ca t i on Ser.No . 11/564,18 0, which  i s  inco rporat ed her ein byr e fe r ence.Once  acontent i nde xi s avail ab le ,  clien t sy st ems no  longe r  nee d to be involved w hen s e a rchin g  fo r dat aand can be f ocused onmore desira ble ta skssuchas runn in g prod uct io n applicat i ons.
Alth oughthe con te nt i nde x save s cl i e nt re sour ce s,the usefu l n es s  o ft hecont ent i nd ex c an causet he conte nti ndex it se lft o  becom e  a r esource in  hi gh de m a nd. When t h e co n te n t ind ex isrelied  upon f o r p ro cessing  se a r ches andfinding d a taam ongmany cop ie s, t he  co nt ent index can b ecome asingle p o i nt offai l uref or per fo rming theseopera ti o ns, and t heperform a nce  of  se arch es
 to_e-commerce such_as databases, file servers,_web servers,_and_so on_as_part of a_daily, weekly, or_monthly maintenance schedule. The_company may also_protect_computing systems used by each of its employees, such as those used by an_accounting_department, marketing_department,_engineering_department, and so forth.
Current storage_management systems employ a number_of different_methods to perform storage operations on electronic data._For_example, data can_be stored in primary storage as a primary copy_or in secondary storage as various_types of secondary_copies_including,_as a backup copy,_a snapshot copy, a hierarchical storage_management copy (“HSM”), as an archive_copy, and as other types of copies.
A_primary copy of data is generally_a production copy or other_“live” version_of the data that a_software application uses_and is_generally in the_native format of that application. Primary_copy data may_be maintained in a local memory_or_other high-speed storage_device_that_allows for_relatively fast data_access_if necessary._Such_primary copy data is typically intended_for_short term retention (e.g., several hours or_days) before some or_all_of the data is_stored as one or more_secondary copies, for example to prevent_loss of_data in_the event a problem occurred with the data stored in primary_storage.
Secondary copies include point-in-time data and_are typically intended for_long-term retention_(e.g.,_weeks, months or_years_depending on_retention criteria, for example as specified in_a storage_policy as further described herein) before_some or all of_the_data is moved to other storage_or discarded.
Secondary copies may be indexed_so users can browse and_restore_the_data at another point in_time. After certain primary copy data_is backed up,_a pointer or other location indicia such_as_a stub may be placed in_the_primary copy to indicate the current_location_of_that data. One process for_creating a content index and classifying_data is described in U.S. patent application Ser. No._11/564,180, which is_incorporated herein by reference. Once_a_content_index is available, client systems no longer need to be_involved when_searching for data_and can be focused on more desirable tasks such as_running production applications.
Although the content index saves_client resources, the usefulness of the content index can cause the_content index itself to become a resource in_high demand. When the content index is_relied upon for processing_searches_and finding data among many copies, the_content_index_can_become a single_point of failure_for performing these_operations, and_the performance of_searches