You are on page 1of 334

Virtual Tape Library

VTL User Guide

Sun Microsystems, Inc. www.sun.com


Part No. 96267 Mar 2008, Revision F Submit comments about this document at: glsfs@sun.com

Copyright2008 SunMicrosystems,Inc.,4150NetworkCircle,SantaClara,California95054,U.S.A.Allrightsreserved. SunMicrosystems,Inc.hasintellectualpropertyrightsrelatingtotechnologythatisdescribedinthisdocument.Inparticular,andwithout limitation,theseintellectualpropertyrightsmayincludeoneormoreoftheU.S.patentslistedathttp://www.sun.com/patentsandoneormore additionalpatentsorpendingpatentapplicationsintheU.S.andinothercountries. Thisdocumentandtheproducttowhichitpertainsaredistributedunderlicensesrestrictingtheiruse,copying,distribution,and decompilation.Nopartoftheproductorofthisdocumentmaybereproducedinanyformbyanymeanswithoutpriorwrittenauthorizationof Sunanditslicensors,ifany. Thirdpartysoftware,includingfonttechnology,iscopyrightedandlicensedfromSunsuppliers. PartsoftheproductmaybederivedfromBerkeleyBSDsystems,licensedfromtheUniversityofCalifornia.UNIXisaregisteredtrademarkin theU.S.andinothercountries,exclusivelylicensedthroughX/OpenCompany,Ltd. Sun,SunMicrosystems,theSunlogo,Java,AnswerBook2,docs.sun.com,andSolarisaretrademarksorregisteredtrademarksofSun Microsystems,Inc.intheU.S.andinothercountries. AMDOpteronisatrademarkorregisteredtrademarkofAdvancedMicrodevices,Inc. AllSPARCtrademarksareusedunderlicenseandaretrademarksorregisteredtrademarksofSPARCInternational,Inc.intheU.S.andinother countries.ProductsbearingSPARCtrademarksarebaseduponanarchitecturedevelopedbySunMicrosystems,Inc. TheOPENLOOKandSunGraphicalUserInterfacewasdevelopedbySunMicrosystems,Inc.foritsusersandlicensees.Sunacknowledges thepioneeringeffortsofXeroxinresearchinganddevelopingtheconceptofvisualorgraphicaluserinterfacesforthecomputerindustry.Sun holdsanonexclusivelicensefromXeroxtotheXeroxGraphicalUserInterface,whichlicensealsocoversSunslicenseeswhoimplementOPEN LOOKGUIsandotherwisecomplywithSunswrittenlicenseagreements. U.S.GovernmentRightsCommercialuse.GovernmentusersaresubjecttotheSunMicrosystems,Inc.standardlicenseagreementand applicableprovisionsoftheFARanditssupplements. DOCUMENTATIONISPROVIDEDASISANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONSANDWARRANTIES, INCLUDINGANYIMPLIEDWARRANTYOFMERCHANTABILITY,FITNESSFORAPARTICULARPURPOSEORNONINFRINGEMENT, AREDISCLAIMED,EXCEPTTOTHEEXTENTTHATSUCHDISCLAIMERSAREHELDTOBELEGALLYINVALID. Copyright2008SunMicrosystems,Inc.,4150NetworkCircle,SantaClara,Californie95054,EtatsUnis.Tousdroitsrservs. SunMicrosystems,Inc.alesdroitsdepropritintellectuelsrelatantslatechnologiequiestdcritdanscedocument.Enparticulier,etsansla limitation,cesdroitsdepropritintellectuelspeuventinclureunouplusdesbrevetsamricainsnumrshttp://www.sun.com/patentsetun oulesbrevetsplussupplmentairesoulesapplicationsdebrevetenattentedanslesEtatsUnisetdanslesautrespays. Ceproduitoudocumentestprotgparuncopyrightetdistribuavecdeslicencesquienrestreignentlutilisation,lacopie,ladistribution,etla dcompilation.Aucunepartiedeceproduitoudocumentnepeuttrereproduitesousaucuneforme,parquelquemoyenquecesoit,sans lautorisationpralableetcritedeSunetdesesbailleursdelicence,silyena. Lelogicieldtenupardestiers,etquicomprendlatechnologierelativeauxpolicesdecaractres,estprotgparuncopyrightetlicencipardes fournisseursdeSun. DespartiesdeceproduitpourronttredrivesdessystmesBerkeleyBSDlicencisparlUniversitdeCalifornie.UNIXestunemarque dposeauxEtatsUnisetdansdautrespaysetlicencieexclusivementparX/OpenCompany,Ltd. Sun,SunMicrosystems,lelogoSun,Java,AnswerBook2,docs.sun.com,etSolarissontdesmarquesdefabriqueoudesmarquesdposesde SunMicrosystems,Inc.auxEtatsUnisetdansdautrespays. AMDOpteronestunemarquedefabriqueouunemarquedeposeedeAdvancedMicrodevices,Inc. TouteslesmarquesSPARCsontutilisessouslicenceetsontdesmarquesdefabriqueoudesmarquesdposesdeSPARCInternational,Inc. auxEtatsUnisetdansdautrespays.LesproduitsportantlesmarquesSPARCsontbasssurunearchitecturedveloppeparSun Microsystems,Inc. LinterfacedutilisationgraphiqueOPENLOOKetSunatdveloppeparSunMicrosystems,Inc.poursesutilisateursetlicencis.Sun reconnatleseffortsdepionniersdeXeroxpourlarechercheetledveloppementduconceptdesinterfacesdutilisationvisuelleougraphique pourlindustriedelinformatique.SundtientunelicensenonexclusivedeXeroxsurlinterfacedutilisationgraphiqueXerox,cettelicence couvrantgalementleslicenciesdeSunquimettentenplacelinterfacedutilisationgraphiqueOPENLOOKetquienoutreseconformentaux licencescritesdeSun. LADOCUMENTATIONESTFOURNIEENLTATETTOUTESAUTRESCONDITIONS,DECLARATIONSETGARANTIESEXPRESSES OUTACITESSONTFORMELLEMENTEXCLUES,DANSLAMESUREAUTORISEEPARLALOIAPPLICABLE,YCOMPRISNOTAMMENT TOUTEGARANTIEIMPLICITERELATIVEALAQUALITEMARCHANDE,ALAPTITUDEAUNEUTILISATIONPARTICULIEREOUA LABSENCEDECONTREFAON.

RevisionHistory

Short Name

Part Number

Dash

Date

Comments

VTLUserGuide

96267

A B C D E F

Nov2006 Jan2007 Mar2007 Aug2007 Nov2007 Feb2008 Mar2008

Basedocumentsuppliedbythevendor. Majorrevision. Published.EC131376. Majorrevision. Minorrevision. MajorrevisiontocoverVTLPlus2.0 Majorrevisiontothecommandlineappendix

Contents

RevisionHistory Contents About this book 1. Introduction:VTLappliancesandenterprisedataprotection Features AdvantagesofVTLtapevirtualization Shorterruntimesandreduceddependencyonbackupwindows Shorterruntimesfornonsequentialbackupjobs Improvedreliability Betterutilizationoftapesubsystems Improvedutilizationofbackupmedia Truetapevirtualizationwithdynamicallyallocateddiskspace KeyVTLfeaturesandoptions NDMPsupport VTLhighavailabilityoption AutomatedTapeCaching Virtualtapereplication VTLSecureTapeencryptionoption

iii v ix 1 2 3 4 4 5 5 6 6 7 7 7 10 11 12

2.

UnderstandingVTLzoning Zoningforstandardavailabilitysystems Zoningforhighavailabilitysystems

15 15 16 19 20 20 22 24 25 25 26 27 27 33 34 39 53 61 67 71 71 74 76 77 77 94 97

3.

UsingtheVTLconsole RunningtheVTLconsoleapplication Populatingtheconsole UnderstandingtheVTLconsoleinterface VirtualTapeLibrarySystem SANClients Reports PhysicalResources

4.

VTLoperations Managingnetworkconnectivity Managingvirtuallibraries Configuringphysicallibrariesanddevices Configuringandprovisioningvirtuallibraries Creatingvirtualtapes Connectingvirtuallibrarieswithstorageclients BackinguptheVTLsystemconfiguration Recoveringtheserverconfiguration ProtectingVTLmetadata Administeringuseracountsandpasswords Managingtapes Locatingvirtualtapes Replicatingtapes Copyingtapes Movingtapesbetweenvirtualandphysicallibraries

vi

VTL User Guide Mar 2008

Managingtapecaching Creatingandviewingreports Encryptingandshreddingdata WorkingwiththeEventLog UsingtheAttentionRequiredtab ManagingVTLservers 5. 6. InstallingtheVTLconsole Recoveryfollowingasystemfailure Failback Resumingbackupsfollowingafailover/failback 7. 8. A. Configuringemailnotifications UpdatingVTLsoftware VTLcommandlinereference Understandingtypographicalconventions Permissionsandpaths Gettingonlinehelp Generalusage Commonarguments Securityandthecommandline Indexofcommands B. C. Requiredports Troubleshooting Problemsduringconsoleoperations Problemsaffectingphysicalresources Problemswithvirtualresources
Contents

109 112 116 124 127 129 131 135 135 146 147 153 157 157 158 158 158 159 159 160 267 269 269 272 273
vii

Problemsduringimport/exportoperations TakinganXrayfortechnicalsupport D. E. SNMPtraps ILOMcommandreference

277 279 283 319

viii

VTL User Guide Mar 2008

Aboutthisbook
Thisbookintroducestapevirtualizationandguidesyouthroughtheadministrationof SunStorageTekVirtualTapeLibrary(VTL)solutions,includingVTLPlus2.0andVTL Valuesystems.ItstartswithahighlevelexplanationofVTLtechnology,common deploymentarchitectures,andspecialfeatures.Itthenprovidesdetailedinstructions forcarryingoutthetaskscommontoVTLadministrationaccordingtoSunVTLbest practices,including:

SANzoning usingtheVTLConsolegraphicaluserinterface(GUI)andinstallingcopieson managementstations administeringlocalareanetwork(LAN)connections designing,creating,andmanagingvirtuallibrariesandvirtualtapes usingspecialfeatureslikeautomatictapecaching,automatictapearchiving,and tapereplication usingencryptionanddatacompressionfeaturestobestadvantage handlingfailbackafterahighavailabilitysystemhasfailedover reporting configuringandusingemailnotifications

Finally,appendicesprovideadditionalinformationthat,whilenotessentialtoanormal installation,mayproveusefulinspecialcircumstances. Thedocumentistaskoriented,organizedaroundtheworkyouhavetodoratherthan aroundthefeaturesorcomponentsoftheproduct.Eachchapterandsectionbegins withalistofthetasksitcontains.Tasksarepresentedinorder,andthestepsineach processarenumbered,inthesequenceinwhichtheyaretobeperformed.Conditional steps(stepsthatyouperformonlyinspecifiedcircumstances)beginwiththecondition (IfA...)andendwiththecorrespondingaction(...doB);iftheconditiondoesnot apply,yousimplyskipthestep.Eachtaskendswithareferencetothenexttaskinthe sequence: Nexttask:Installing...onpage 3. Whenthesetupprocessbranches,thetaskendswithconditionalalternatives: Nexttask: If the customer does not plan to run the management console from a host on the local area network (LAN), press Skip, and go to the next task. Otherwise, carry out the procedure Configuring the Ethernet LAN on page 57.
96267 F ix

Whenyouhavefinishedasequenceoftasks,thisisclearlynoted: Stop here. Tominimizethetimeyouspendswitchingbetweenpublicationsorbetweenmajor sectionsofthedocument,wehavemadeanefforttoavoidcrossreferencestoexternal informationwhereverpossible.Ifyouneedtohaveafigure,atable,oraprocedure,it shouldalwaysbe,atworst,onaneighboringpage.

Takingadvantageofthisbookshypertextfeatures
Ifyouchoosetoviewthisbookonline,ratherthaninprintedform,youcanjump quicklytoanypartofthebookbyclickingonthecorrespondingentryunderthe BookmarkstabontheleftsideoftheAdobeAcrobatinterface.Inaddition,clickingon entriesinthetableofcontents,crossreferences,orreferencestosubsequenttaskswill takeyoudirectlytotheindicatedpartofthedocument.Youcanthenusetheback arrowontheAdobeAcrobatReadertoreturn,ifdesired,tothepointyouleft.In addition,clickingonmostUniformResourceLocators(URLs)andonmostreferences toonlineresourceswillopenyourdefaultwebbrowsertothecorrespondingwebpage, sothatyoucan,ifnecessary,obtainarequireddownloadimmediately(beaware, however,URLstospecificpageschangefrequentlyandmaynotalwaysbeaccurate).

Understandingtheconventionsusedinthisbook
Thetablebelowillustratestheconventionsthatrepresentliteralandvariablevalues, commands,andpropertynamesinthisbook.
Convention Meaning Examples

AaBbCc123

Fixedwidthtextisusedforliteralvalues, includingnamesofcommands,files,directories, literalcomputerinputs/outputs,andUniform ResourceLocators(URLs) Obliquetextisusedforvariablesthatstandfor realnamesorvaluesandforbooktitles. Bold,sanseriftextindicatescalloutsin illustrations. Numberedparagraphsindicatestepsinaprocess thatshouldbeexecutedinsequentialorder. Bulletedparagraphsindicatelistsofalternatives orcomponents. acommandlineprompt

Edityour.loginfile. Use ls -a tolistfiles. % You have mail. Todeleteafile,type: rm filename. Click Submit (A below).

AaBbCc123
AaBbCc123

ABCD
1. [VTL_Plus]#

Obtainingthelatestinformationandsupportingresources
TheSunStorageTekSupportportal<www.support.storagetek.com>provideslinks tothelatestdocumentation,softwareupdates,andlicensingresourcesforVTLPlus solutions.Alwayschecktheportalforupdatestothisdocumentbeforeproceeding. DocumentsdistributedonCDROMmaynotreflectthelatestchangestoVTLhardware, software,andservices.

VTL User Guide Mar 2008

F 96267

Note TheCustomerResourceCenterwillbemigratingtoserverswithintheSunSolve supportenvironmentshortlyafterthisdocumentappears.ButtheaboveURLwillbe automaticallyredirectedtothenewlocation.

UsingtheVTLWikitoobtainadditionalinformation
TheVTLWiki<http://wikihome.sfbay.sun.com/vtlwiki/Wiki.jsp>hosts linkstoawiderangeofmarketing,support,andtechnicalresources,documents,and tools,aswellasanextensiveFAQsectionwithanswerstoFrequentlyAskedQuestions.

Commentingonthisbook
Sunwelcomesyourcommentsandsuggestionsforimprovingthisbook.Contactusat glsfs@sun.com. Pleaseincludethetitle,partnumber,issuedate,andrevision:VTL User Guide,partnumber96267(Mar2008revision F).

96267 F

xi

xii

VTL User Guide Mar 2008

F 96267

CHAPTER

Introduction:VTLappliancesand enterprisedataprotection
SunStorageTekVirtualTapeLibrary(VTL)technologymakesthebenefitsofdiskto disktotapearchitectureavailabletocomplexbackupenvironmentsthatcannot readilyaccommodatethedisruptionsandadministrativeburdensthatoften accompanymajorchangestoinformationmanagementenvironmentsandprocesses. VTLsolutionsmakediskmediaavailabletoapplicationsthatareconfiguredtowork withtape.VTLsoftwarepresentsyourexistingtapecentricbackuparchitecturewith whatappeartobefamiliartapelibraries,drives,anddatacartridgeswhilemanaging thecomplexitiesoftheimplementationdiskarrays,RAIDgroups,andlogical volumesinternally. Suchtransparencyisabsolutelycriticalwhenbackupisjustoneaspectofan enterprisewidebusinesscontinuityplan.Whenlegacysystemsandmultiple, interdependentapplications,procedures,policies,and/orserviceprovidersare involved,evenmodestchangestoabackuparchitecturecanhaveunforeseen,far reachingconsequences. Theadvantagesthatdisktodiskbackuphastoofferarenolesscriticalincomplex environments.Heavyworkloads,tightschedules,andmultipledependenciesoften makebackupwindowsverytightornonexistent.Jobsthatfailtocompletecannot, inmostcases,beretried.Tapebasedbackupsystemsperformwellwhenhandling bigjobs,likefullbackupsoflargefilesandfilesystemsthatcanstreamlarge amountsofsequentialdata.Butmuchofthecurrentbackupworkloadconsistsof intermittent,essentiallyrandomI/Oincrementals,fullbackupsofheterogeneous smallserversandworkstations,andsmallfiles(suchasthoseassociatedwithemail systems).Tapedrivesperformpoorlyundertheseconditions.Butdiskbasedstorage isideallyplacedtohandlethistypeofI/O. Theremainderofthischapterprovides:

abriefsummaryofVTLFeaturesonpage 2 adetaileddiscussionoftheAdvantagesofVTLtapevirtualizationonpage 3 amoreindepthlookatselected,KeyVTLfeaturesandoptionsonpage 7.

96267 F

Features

Features
TheSunStorageTekVTLsolutionhasthefollowingfeatures:

Emulationofmostwidelyusedtapelibraries,drives,andmediatypes,including thelatestSunStorageTekT10000seriesdrivesandmedia Dynamicallocationofdiskcapacity VTLsoftwarecanallocatediskspacetovirtualtapesin5GBincrements,upto thefull,ratedcapacityoftheemulatedmedia.Thisminimizeswastedspace, providesnaturalloadbalancing,andoptimizestheperformanceofthediskarray.

AutoArchivefeature TheAutoArchiveoptionwritesdatatophysicaltapewheneverabackup applicationorutilitymovesavirtualtapefromavirtuallibrarytoan import/exportslot.Thephysicaltapelibrarymustsupportbarcodes:theVTL softwarehastofindamatchingbarcodeinthephysicallibraryinordertoexport avirtualtapetoaphysicalcartridge.

ReplicationoftapestolocalandremoteVTLsystems VTLsoftwaresupportsmanualcopyingandbotheventandpolicydriven automaticreplicationmethods.

AutomatedTapeCachingoption Withtheoptionaltapecachingfeature,VTLsoftwarecanautomaticallysavea singlevirtualvolumewithasinglebarcodeintwophysicalforms,oneondisk andoneonphysicaltape.Thetapecachingfeaturemanagesretentionand migrationofthephysicalimages,underthecontrolofuserspecifiedpoliciesand schedules.Thisletsuserskeepspaceinthediskcachefreefornewbackupsets whileretainingthetapeimagesofoldervirtualvolumes.Whenavirtualvolume nolongerresidesinthediskcache,apointerinthecacheseamlesslyredirects requeststothetapeimage.

Highavailabilityoption Anoptional,highavailabilityconfigurationprovidesintelligentfailover,with duplicate,selfmonitoringVTLservernodesandredundant,primaryandstandby pathsbetweenbackupapplicationsandVTLdata.

Encryptionandsecuredatadestruction Toensurethatthedatathatyouexporttophysicaltapeisconfidentialandsecure, VTLoffersaSecureTapeOptionthatusestheAdvancedEncryptionStandard (AES)algorithmpublishedbytheNationalInstituteofStandardsandTechnology, anagencyoftheU.S.government.

VTL User Guide Mar 2008

F 96267

Advantages of VTL tape virtualization

TheShredfeatureinsuresmilitarystandard,securedatadestructionby overwritingvirtualtapewithrandombitpatterns.Datadestructionjobsare queuedsothattheshredprocessdoesnothaveanexcessiveimpactupon performance.

Softwarebaseddatacompression CompressionsoftwarebasedontheLZOalgorithmcan,whennecessary,increase theamountofdatathatwillfitonavirtualtapeofagivencapacity.Compression ratioscanapproach2:1fordatasetsmadeupofhighlycompressiblefiletypes, suchasplaintextanduncompressedbitmappedimages.Conversely,asignificant proportionofincompressiblefiletypes,suchasZIParchives,GIFimages,and JPGimageswillreducetheattainablecompressionsignificantly.

SupportforSunStorageTekACSLSandLibraryStationlibrarymanagement software ACSLSandLibraryStationsupportmakesahighdegreeofintegrationpossible betweenVTLsolutionsandcomplexenterprisestorageenvironmentsthatinclude largelibrarieswithmultiplepartitionsandmixedopensystemsandmainframe systems.

CallHomesupport TheVTLCallHomefeaturemonitorsanextensiblesetofpredefinedcritical systemfunctionsandautomaticallynotifiesalocalsystemadministratorbyemail. YoucanextendormodifytheCallHomemonitoringscriptstocustomize monitoringforyourneeds.

Xraydiagnostics TheXrayfeaturecombinessnapshotsofthecurrentstateoftheappliance,its configuration,anditsenvironmentwithsystemeventlogsandsavestheresultin astandard,tapearchive(tar)format.

KeyVTLfeaturesarediscussedinmoredetaillaterinthischapter.

AdvantagesofVTLtapevirtualization
AddingSunStorageTekVirtualTapeLibraryappliancestoanexistingtapebased backuparchitecturecanthusrealizethefollowingadvantages:

Shorterruntimesandreduceddependencyonbackupwindowsonpage 4 Shorterruntimesfornonsequentialbackupjobsonpage 4 Improvedreliabilityonpage 5 Betterutilizationoftapesubsystemsonpage 5 Truetapevirtualizationwithdynamicallyallocateddiskspaceonpage 6.

96267 F

Chapter 1 Introduction: VTL appliances and enterprise data-protection

Advantages of VTL tape virtualization

Shorterruntimesandreduceddependencyon backupwindows
VTLappliancescanhandleanarrowbackupwindowbyusingnumbersofvirtual drivesoperatinginparallel,somethingthatwouldbehighlyimpracticalwith physicaltapedrives.Inthisway,thecritical,firstcopyoftheprimarydataisreliably transferredtodiskbasedvirtualtapeinminimumtime.Thereafter,vaulting softwareand/orVTLtapecachingfeaturescancopythebackupfromvirtualto physicalmediausingasmaller,moreeconomicalnumberofphysicaldrives.Seethe figurebelow:
Multiple virtual drives speed backup during the critical backup window

primary storage

virtual library

physical library

virtual tape drives

physical tape drives

backup window Back up to multiple virtual tape drives during the critical backup window At other times, copy virtual tapes to physical media using one or two dedicated tape drives

Shorterruntimesfornonsequentialbackupjobs
DiskbasedVTLsystemsreduceruntimewhenstorageoperationsarepoorly matchedtotheoperationalcharacteristicsoftapebackupsystems.Properly configured,streamingtapebackupsachievetransferratesthatareashighasor higherthanthoseattainablebydisktechnology.Butmanycommonjobssuchas incrementalsandfullbackupsofworkstationsproducesemirandomI/O.Non sequentialI/Okeepstapedrivesbusymounting,unmounting,andpositioning media,greatlyreducingthroughput.Diskbasedsecondarystorageismuchbetter suitedtothesesemirandombackupjobs.

VTL User Guide Mar 2008

F 96267

Advantages of VTL tape virtualization

Improvedreliability
DiskbasedVTLsystemscansignificantlyincreasethereliabilityofthebackup process.Backupjobsaremorelikelytosucceedthefirsttime,becausethecritical stepthecreationofacopyofthedataisasimple,fastwritetoaRAIDsubsystem. Jammedtapes,lackofreadymedia,andofflinedrivesnolongerruinjobs.Seethe figurebelow:
Backup is more reliable with virtual tape libraries backup window

primary storage

physical library FAILURE!

A backup to physical tape can fail when a tape drive jams or media breaks, because a retry may not be possible before the backup window closes. A backup to disk-based virtual media always succeeds, so all data is copied to secondary media before the backup window closes.

SUCCESS! virtual library physical library

Virtual volumes are subsequently copied to physical media outside the backup window. If problems arise, copy jobs can be retried later.

Betterutilizationoftapesubsystems
DiskbasedVTLsystemscanimproveutilization,performance,andreliabilityof tapestoragesubsystems.WhennonsequentialI/Oisbackeduptodisk,tapecanbe reservedforsequentialjobsthatcanstreamaphysicaltapedrive.Largescalefull backupscan,forinstance,godirectlytotape,insuringmaximumperformance.Jobs thatproduceintermittentornonsequentialI/O,suchasincrementalsandbackupsof workstations,arecopiedtotapeonlyaftertheyhavebeenbackeduptodiskand incorporatedintolarge,sequentialbackupsets.Thisapproachusestapedrives continuously,atclosetotheirmaximumthroughput.Thedrivesspendlesstimeidle, sincetheymountandrepositionlessoften.Fewerdrivesandtapesareneededfora givenworkload.Devicesandmediasufferlesswearandtear.

96267 F

Chapter 1 Introduction: VTL appliances and enterprise data-protection

Advantages of VTL tape virtualization

Improvedutilizationofbackupmedia
Tapevirtualizationletsyoucreateemulatedtapevolumesthataremorecloselysized totheaveragesizeofyourbackupmedia.Ifyoudonotdecidetousetapecaching (seeAutomatedTapeCachingonpage 10),yousetthemaximumcapacityofyour virtualtapesto5060GBortotheaveragesizeofyourbackupjobs(whicheveris larger).Thisapproachminimizeswastedspaceinthecriticaldiskcache,wherethe firstcopyofeachbackupjobisstored,andmakesamaximumnumberofcartridges availableforbackupjobsatanygiventime.Yourcopy/vaultsoftwarecanthen consolidatethesesmallervolumesontofullsizedphysicaltapecartridgesoutside thebackupwindow. Ifyouadopttapecaching,youcannotsizevirtualtapesthisway,since,asweshall see,thediskandphysicaltapeimagesofthevirtualtapemustbelogicallyidentical.

Truetapevirtualizationwithdynamically allocateddiskspace
Correctlyconfigured,dynamicallysizedvirtualtapevolumesprovidethehighest capacityandperformance.WhentapesarecreatedwiththeVTLCapacityOn Demandfeatureenabled,theVTLsoftwareallocatesspaceasdataiswrittentodisk ratherthanallatonce.Forinstance,aphysicaltapewithacapacityof400GBcanbe emulatedwithoutallocatinganyspaceinitially,andthereafterenlargedasneededin 5GBincrements(seethefigurebelow).
= 2-MB tape archive files Space is not allocated on disk until data is written 400-GB virtual tape 02B10001 400-GB virtual tape 02B10000 400-GB physical tape 01A00001 400-GB physical tape 01A00002 = 5-GB header/data segment = 5-GB data segment

Thisapproachtospaceallocationhastwomajoradvantages.First,itminimizes wasteddiskcapacity.Second,andperhapsmoreimportantly,itmaximizesarray performanceandreliability.Dividingdataintomultiplesegmentsdistributesitmore evenlyacrossthearray,involvesmorevolumegroupsineachI/O,andreducesthe averagelengthofeachseekduringI/O.

VTL User Guide Mar 2008

F 96267

Key VTL features and options

KeyVTLfeaturesandoptions

NDMPsupportonpage 7 VTLhighavailabilityoptiononpage 7 AutomatedTapeCachingonpage 10 Virtualtapereplicationonpage 11 VTLSecureTapeencryptionoptiononpage 12.

NDMPsupport
SunVTLvirtualtapelibrarySANclientscanincludeNetworkAttachedStorage (NAS)filers.NDMPagentsoftwareonthefilermovesdataovertheSANtothe virtualtapevolumesmountedbythebackupmediaserver:
NDMP
SAN fabric media server VTL appliance virtual tape library physical tape library NAS filer Data-mover software on NAS filer copies data over SAN to virtual tapes. SAN fabric

Ethernet LAN

Ethernet LAN

InstallationofNDMPagentsoftwareontheVTLapplianceitselfisnotsupported.

VTLhighavailabilityoption
InaVTLhighavailabilitysystem,intelligentselfmonitoringsoftware,redundant hardware,andhighavailabilityLANandSANconfigurationsprotectboththedata pathandyourabilitytomanagestorage.Tohelpyoutobetterunderstandthesteps inthefailoverconfigurationprocess,thissectionprovidesahighleveldescriptionof thethreekeycomponentsofthehighavailabilityVTLsolution:

Servernodefailoveronpage 8 Managementpathfailoveronpage 9

96267 F

Chapter 1 Introduction: VTL appliances and enterprise data-protection

Key VTL features and options

Storagepathfailoveronpage 9.

Servernodefailover
TheSunStorageTekVTLhighavailabilityoptionusestwoservernodes,each configuredtomonitoritscompanion.Eachmemberofthepairservesastheprimary serverforitsownstorageclientsandasthesecondary,standbyserverforthoseofits companion.Toprotectagainstserverfailures,eachserversendsheartbeat informationtoitssecondaryusingaserviceIPaddress.Ifheartbeatinformation indicatesafatalerrorinacompanionserversprocesses,thehealthyservernotifies itscompanionthatitisassumingprimaryserverresponsibilityforbothsetsof clientsandinitiatesfailover.Iftheheartbeatinformationstopsaltogether,the healthyserverimmediatelyinitiatesfailover.Finally,ifaprimaryserversown,self monitoringroutinesdetectastoragedeviceconnectivityfailureandcannot determineifthefailureislocal,theprimaryreportsthefailuretoitscompanionvia theheartbeatsignal.Ifthecompanion,secondaryservercanaccessalldevices, includingthedeviceinquestion,thefailureislocaltotheprimary,andthe secondaryinitiatesfailover.Ifthesecondarycannotaccessdevices,theoutageis global,andnofailoveroccurs.
Service IP addresses carry heartbeat information between VTL nodes and management IP addresses carry commands between nodes and VTL management consoles

management_IP_address_1 heartbeat service_IP_address_1 management console 1

service_IP_address_2 heartbeat management_IP_address_2 management console 2

VTL User Guide Mar 2008

F 96267

Key VTL features and options

Managementpathfailover
WhenahighavailabilityVTLsystemfailsover,thefailoverserverautomatically inheritsthefailedserversmanagementIPaddress,sothatremotemanagement consolescanstillreachtheVTLsystem.
If the heartbeat signal is lost, the management IP address for the failed node transfers to the healthy node

management_IP_address_1 management_IP_address_2 service_IP_address_1 management console 1

service_IP_address_2 management console 2

management_IP_address_2

Storagepathfailover
InastandardavailabilityVTLsystem,thereisonelogicalpathfromaVTLclientto VTLstorage,andeveryFibreChannelportiseitheratargetportforaVTLclientor astoragefacinginitiator.Butinahighavailabilitysystem,therearetwopaths,a primaryandasecondaryorstandbypath,asshownbelow.
Fibre Channel path failover in high-availability VTL systems

Primary server for A

WWPN x1

Primary path from A Secondary path from B

WWPN x2 Secondary server for B VTL client A

Secondary server for A WWPN y1 Secondary path from A VTL client B

Primary server for B

WWPN y2

Primary path from B

96267 F

Chapter 1 Introduction: VTL appliances and enterprise data-protection

Key VTL features and options

Failoverduringreplication
Ifareplicationoperationisinprogresswhenfailoverorfailbackoccurs,replication stops.Oncefailover/failbackhascompleted,replicationresumeswiththenext normallyscheduledoperation.

Mirroringandfailover
Ifmirroringisinprogressduringfailover/recovery,afterthefailover/recoverythe mirroringwillrestartfromwhereitleftoff. IfthemirrorissynchronizedbutFibreChannelconnectivityislostbetweenthe serverandstorage,themirrormaybecomeunsynchronized.Itwillresynchronize automaticallyafterfailover/recovery. Asynchronizedmirrorwillalwaysremainsynchronizedduringarecoveryprocess.

AutomatedTapeCaching
TheAutomatedTapeCachingoptionpresentsbackupapplicationswithvirtualtape volumesthatarephysicallyimplementedondisk,tape,orboth.Thiskeepsthe implementationsimplethebackupapplicationmanagesonlythevirtualtape volumesandvirtuallibrarieswhilegivingthebackupadministratortheabilityto finetunethephysicalimplementationforbestperformanceandreliability. VTLsoftwarecanimplementvirtualtapevolumesandvirtuallibrariesusingan optimalcombinationofresources:diskarrays,physicaltapes,physicallibraries,and physicaltapedrives.VTLpoliciesspecifywheredatashouldresideondiskforfast randomaccess,ontapeforlongertermstorage,oronbothformaximum redundancyandforhowlong.Underpolicycontrol,VTLsoftwarecan automaticallycopybackupsetsfromdisktotape,outsideofthebackupwindow.It canretainthebackupsetsinthediskcacheforaspecifiedperiod,sothatuserscan rapidlyrestoredataduringtheperiodwhentheneedishighest.Itcanthenfreeup thediskcachefornewbackupsetswhileretaininganimageontape.Ifarestoreis necessary,apointerinthediskcachepointstherequesttothephysicaltapeimage, transparentlyandautomatically.TheAutomatedTapeCachingoptionthus simplifiesandautomatesmanagementofthediskcache,insuringadequatecapacity withminimumdiskresources. Policiescanbebuiltaroundthenumberofdaysthatdatasetsresideondisk,around adiskcapacityhighwatermark,oraroundaspecifiedeventortimeofday.Physical tapeI/Ocanthusberunasabackgroundprocessthatdoesnotinterferewith productiondatacenteroperations.

10

VTL User Guide Mar 2008

F 96267

Key VTL features and options

Note AutomatedTapeCachingandAutoArchive/Replicationcannotbeusedat thesametimeonthesamevirtuallibrary.

Virtualtapereplication
Replicatingdataprovidesadditionalprotectionfortheinformationonavirtualtape bymaintainingacopylocallyoronanotherVTLserver.VTLsoftwaresupports threereplicationmethods,twoofthemautomaticandoneamanualprocessthatcan beusedifyouarenotusingtheautomaticmethods. Seethefollowingsubsectionsforadditionalinformation:

AutoReplicationonpage 11 Replicationonpage 11 RemoteCopyonpage 12.

AutoReplication
TheAuto Replicationoptioncopiesvirtualtapesfromavirtuallibraryto anotherVTLserverwheneverabackupapplicationorutilitymovesavirtualtapeto animport/exportslot. YouenableAutoReplicationatthelibrarylevelwhenyoucreateavirtualtape library(seeSettinguptheAutoReplicationoptiononpage 49).Youcanthen selectivelyenablethefeatureonatapebytapebasisastapesarecreated.Youcannot altertheAutoReplicationstatusofanexistingvirtualtape.

Replication
TheVTLReplicationfeaturemaintainssynchronizedreplicaresourcecopiesof virtualtapesonadesignatedVTLserver.Attheendofapolicydefinedreplication interval,VTLsoftwarecopiesdatathathaschangedandisnotcurrentlyinusefrom theprimaryvirtualtapestothereplicaresources. Duringnormaloperation,backupclientshavenoaccesstoreplicaresourcesthe latterarepurelyinternalprotectionswithintheVTLsystem.Iftheprimaryvirtual tapeiscorruptorotherwiseunusable,however,administratorscanpromotereplica resourcesaspartoftheirdisasterrecoveryprocess.Oncepromoted,thereplica resourcebecomestheprimaryvirtualtape,withthesamebarcodeandattributes. Backupclientscanthususeitforrecoveryasifitwere,infact,theoriginalcopy. YoucanconfiguretheVTLReplicationfeatureforeither:
96267 F Chapter 1 Introduction: VTL appliances and enterprise data-protection 11

Key VTL features and options

RemoteReplicationor LocalReplication.

RemoteReplication
RemoteReplicationmaintainssynchronizedcopiesofvirtualtapevolumesonthe storagearraysofapairofVTLappliancesthatareconnectedacrossEthernetlocal areanetworks(LANs)orWideAreaNetworks(WANs).Dataisthustransferredat LAN/WANspeed,butisnotsubjecttothedistancelimitationimposedbyFibre Channelstorageareanetwork(SAN)technology.

LocalReplication
LocalReplicationmaintainslocal,synchronizedcopiesofvirtualtapevolumeson thestoragearraysofasingleVTLappliance.DataistransferredatSANspeedover distanceslimitedtothemaximumpossiblewithaFibreChannelSAN.

RemoteCopy
RemoteCopycopiesasinglevirtualtapetoanotherserverondemand.

VTLSecureTapeencryptionoption
TheVTLSecureTapeoptionusestheAdvancedEncryptionStandard(AES) algorithmtoprotectphysicalmediathatmightotherwisebevulnerabletotheftor diversionduringtransit.VTLsoftwareencryptsdatawhenitisexportedtophysical tapeanddecryptsitwhenitisreimportedtovirtualtape.

Keymanagement
TheSecureTapefeatureprovidesforflexiblecryptographickeymanagementthat canbeadaptedtolocalsecurityrequirementsandpolicies.Administratorscan generateasinglekeyforallexportedtapesormultiple,uniquekeysfordifferent tapesorsetsoftapes.Multiplekeysaremoresecureinthesensethatthe compromiseofasinglekeyexposesfewertapes.Butkeysarehardertomanage. Administratorsmustkeeptrackofwhichkeyappliestowhichtape,becauseusing thewrongkeywillcauseindecipherabledatatobeimportedintothevirtuallibrary. Tofacilitatecentralizedkeymanagement,keyscanbeexportedtoanexternalkey packagefile.Keypackagescanbecentrallygeneratedanddistributed,bysecure means,toremotesiteswheredataisimportedtoorexportedfromVTLsystems.

12

VTL User Guide Mar 2008

F 96267

Key VTL features and options

Passwordprotection
Foradditionalsecurity,eachkeyispasswordprotected.Administratorsmust providethecorrectpasswordbeforechangingakeyname,password,orpassword hint,andbeforedeletingorexportingakey.

96267 F

Chapter 1 Introduction: VTL appliances and enterprise data-protection

13

Key VTL features and options

14

VTL User Guide Mar 2008

F 96267

CHAPTER

UnderstandingVTLzoning
Zoningisthecrucialfirststepwhenintegratingastoragesystem,suchastheVTL appliance,intoaFibreChannelstorageareanetwork(SAN).Whilespecificzoning recommendationsmustvaryfromSANenvironmenttoSANenvironment,this chapterdescribesthebasicrequirementsthatallsuccessfulVTLdeploymentsmust address.

Zoningforstandardavailabilitysystemsonpage 15 Zoningforhighavailabilitysystemsonpage 16.

Zoningforstandardavailabilitysystems
ThebasiczoningrequirementforVTLsolutionsthatdonotimplementthehigh availabilityfeatureisthateachSANzonecontainonlyoneinitiatorandonetarget, asshowninthefigurebelow.
SAN
Client VTL server node Zone A

T I

I T

YouzonestandardavailabilityVTLsystemsthesameway,regardlessofthetypeof zoningyouuse.InasoftzonedSAN,eachtargetandinitiatorisdefinedbyalogical WorldWidePortName(WWPN),whileinahardzonedSAN,targetandinitiator aredefinedbyphysicalportnumbers.But,ineithercase,youhaveoneclient initiatorandoneVTLtargetperzone.

96267 F

15

Zoningforhighavailabilitysystems
Zoningahighavailabilitysystemisslightlymorecomplexthanzoningastandard system,duetotheneedforredundantpathsbetweeninitiatorsandtargets.Once again,eachSANzonecanhaveonlyoneinitiatorandonetarget.Butthetotal numberofzonesyouneeddependsonwhethertheSANissoftzoned(byWorld WidePortName)orhardzoned(byportnumber).See:

WWPNzoning(softzoning)onpage 16 Portzoning(hardzoning)onpage 17.

WWPNzoning(softzoning)
AsoftzonedSANmapsinitiatortotargetusingalogicalWorldWidePortName (WWPN),ratherthanaphysicalhardwareaddress.Thisnametonamezoning establishesalogicalroutethatmaytraversevaryingphysicalportsandvarying physicalpathsthroughtheSAN.Toaccomplishfailover,wethusneedonlyasingle zonefortheclientinitiator,theactiveVTLtarget,andthestandbyVTLtarget. SeethefigurebelowshowsasoftzonedSANbeforeVTLfailover:
SAN
Active VTL server node A WWPN2 Zone A Client A WWPN1

T I
WWPN3 Standby VTL server node B Standby VTL server node A WWPN5

I
Client B

T
Active VTL server node B WWPN6 Zone B

I
WWPN4

Duringfailover,thezonestillcontainsonlyoneinitiatorandonetargetatatime.But thetargetWWPNisremappedfromaportonthefailedservernodetoaphysical portonthestandbyserver.ThestandbyphysicalportspoofstheWWPNofthe failedport,sozoningdoesnotchange.ThefigurebelowshowsasoftzonedSAN afterVTLfailover,withastandbyportspoofingtheWWPNofthefailedport:

16

VTL User Guide Mar 2008

F 96267

SAN
Failed VTL server node Client

T I
Active VTL server node A
W * N2 WP n Zo eA

T T
WWPN6 Active VTL server node B Zone B

Client B

I
WWPN4

Portzoning(hardzoning)
AhardzonedSANmapsinitiatortotargetusingaphysicalportaddress.Thisport toportzoningestablishesafixed,physicalroutethroughtheSAN.So,sinceeach SANzonecancontainonlyoneinitiatorandonetarget,youmustprovidetwozones foreachinitiatingclient.ThefigurebelowshowsahardzonedSANbeforeVTL failover:
SAN
Active VTL server node A Client A WWPN2 Zone A port2 port1

T I
Standby VTL server node B port3
n Zo eC

Standby VTL server node A port5

I T
port6 Active VTL server node B

Zo ne

Client B

I
Zone B port4

Astheabovefigureshows:

onezonedefinesthepathtotheprimaryVTLservernode theotherzonedefinesthepathtothestandbyserver.

96267 F

Chapter 2 Understanding VTL zoning

17

Duringfailover,thestandbyportbecomesactivebyspoofingtheWWPNofthe failedport.ThefigurebelowrepresentsahardzonedSANafterVTLfailover:
SAN
Client A port2 port1

T
e on port3 2* Z PN W W port5

I
A

Active VTL server node A

T T
port6 Active VTL server node B Zone B

Client B

I
port4

18

VTL User Guide Mar 2008

F 96267

CHAPTER

UsingtheVTLconsole
TheVirtualTapeLibraryconsoleapplicationisthegraphicaluserinterfacethatyou usewhenadministeringandmanagingtheVTLsystem.Theconsoleprovidesyou withfullcontrolovervirtuallibraryoperations,fromcreatinglibrariesandtapesto managingdiskstorageanddatamigrationfromdisktophysicaltape. TheVTLconsolesoftwareisinstalledonamanagementworkstationthatyou provideandcommunicateswiththeapplianceviayourlocalareanetwork(LAN).In mostdeployments,yourSunservicerepresentativewillinstalloneinstanceofthe consoleforyou(youcaninstallasmanyadditionalinstancesasyourequireonother machines,thoughnomorethantwoinstancescanaccessthesameVTLserveratthe sametime).Forinformationoninstallingadditionalinstancesoftheconsole,see InstallingtheVTLconsoleonpage 131. Thefollowingsectionsexplainhowyouusetheconsoleapplication:

RunningtheVTLconsoleapplicationonpage 20 Populatingtheconsoleonpage 20 UnderstandingtheVTLconsoleinterfaceonpage 22.

Note Forinformationonthetextbased,VTLcommandlineuserinterface,see Appendix A,VTLcommandlinereferenceonpage 149.

96267 F

19

Running the VTL console application

RunningtheVTLconsoleapplication
LaunchingtheVTLconsole
1. TolaunchtheconsoleonaSunSolarisworkstation,openaterminalwindowand enterthecommandshownbelow:
% /usr/local/vtlconsole/vtlconsole &

2. OnaMicrosoftWindowssystem,presstheStartbartoaccessthemainmenu system,andselectAll Programs > Sun Microsystems > VTL 5.0 > VTL Console. 3. TolaunchtheconsoleonaLinuxworkstation,openaterminalwindowandenter thecommandshownbelow:
% /usr/local/vtlconsole/vtlconsole &

Stophere.

Populatingtheconsole
Oncetheconsoleisrunning,youcanspecifytheVTLserversthatyouwanttoseein theobjecttreeattheleftsideoftheVTLconsole.Youcandiscover,add,orremove servers:

DiscoveringVTLservernodesonpage 20. Addingaservernodetotheconsoletreeonpage 21 Deletingaservernodefromtheconsoletreeonpage 22

DiscoveringVTLservernodes
WheneveraVTLserverisaddedtothesubnetmanagedbyaVTLconsole,youcan discoverthenewadditionanditspropertiesusingtheprocedurebelow.

20

VTL User Guide Mar 2008

F 96267

Populating the console

1. Fromtheconsolemainmenu,selectTools(A below),thenselectDiscover VTL Serversfromthesubmenu(B).


A B

2. WhentheDiscover Virtual Tape Library Serverdialogappears,enterthe subnetfilter(F below)andsubnetmask(G)fortheVTLappliance.Thenpress OK (H).

C D E

subnet_of_VTL_node subnet_mask_of_VTL_node

Afterashortwait,theVTLconsoleapplicationdiscoverstheapplianceandaddsit tothelistontheleftsideofthegraphicaluserinterface(GUI). Stophere.

Addingaservernodetotheconsoletree
1. InthetreeviewoftheVTLconsole,rightclickonVTL Servers(A below).

A B

2. Fromthecontextmenu,selectAdd(B above).

96267 F

Chapter 3 Using the VTL console

21

Understanding the VTL console interface

3. WhentheVTL User Login dialogappears,entertheVTL Serverhostnameor IPaddress(C above)andtheUser Name,andPassword(D),andpressOK(E). Stophere.

Deletingaservernodefromtheconsoletree
1. InthetreeviewoftheVTLconsole,rightclickonthenameoftheserveryouwish todeletefromtheconsoleview. 2. Fromthecontextmenu,selectDelete. 3. Whentheconfirmationdialogappears,selectYes. Stophere.

UnderstandingtheVTLconsole interface
TheVTLconsoleinterfaceconsistsoffourmainparts:amainmenu,alefthand mainwindowpane,arighthandmainwindowpane,andastatusbaratthebottom oftheinterface.TheVTLmainmenusystem(A below)letsyoucontroltheconsole andcarryouttheadministrativefunctionsitsupports.ThelefthandpaneoftheVTL consoleinterfacerepresentsthecomponentobjectsoftheVTLsystemasthe branchesofatree(Band Cbelow).Itcontainsthefollowingmajorbranches:

VirtualTapeLibrarySystemonpage 24 SANClientsonpage 25 Reportsonpage 25 PhysicalResourcesonpage 26.

ClickingontheiconforaVTLserver(B below)opensthelogindialog.

22

VTL User Guide Mar 2008

F 96267

Understanding the VTL console interface

D B

Onceyouhaveloggedintotheserver,clickingontheplus(+)symbolnexttothe iconexpandstheserverbranchoftheinterface,revealingthesubcomponentsofthe VTLsystem:theVirtual Tape Library System,SAN Clients,Reports,and Physical Resources(C above). Clickingontheplus(+)symbolnexttoanyiconexpandsthecorrespondingbranch oftheobjecttree,revealingthesubcomponentsandsubbranchesthatliebeneathit. Clickingontheminus(-)symbolcollapsesthebranch. Selectinganobjectinthetreedisplaysatabbedpropertysheetfortheobjectinthe righthandpaneoftheconsole(D above).Rightclickinganobjectopensacontext menusystemthatletsyouchangethepropertiesoftheobjectorperformtaskswith theobject(E). Thestatusbaratthebottomofthewindow(F above)displaysversioning informationforthelocallyinstalledconsolesoftware.Adropdownboxdisplays consolesessioninformation.

96267 F

Chapter 3 Using the VTL console

23

Understanding the VTL console interface

VirtualTapeLibrarySystem
TheVirtual Tape Library Systembranchoftheobjecttreeistheprimary managementtoolforroutineVTLoperations.Rightclickingonthesubbranchesof theVirtual Tape Library Systemgivesyouaccesstocontextsensitivemenus thatcontrolmostofthecommonVTLmanagementoperations.

VirtualTapeLibrarySystemicons
Thefollowingtableexplainstheiconsthatrepresentvirtualtapedrivesandvirtual tapesintheconsoleobjecttree.
Icon Description

The Ciconindicatesthatavirtualtapedrivehascompressionenabled. The Aiconindicatesthatavirtualtapeisacacheforaphysicaltape.Requires theAutomatedTapeCachingoption. The Siconindicatesadirectlinktape(alinktothephysicaltape).Requiresthe AutomatedTapeCachingoption.

ThestructureoftheVirtualTapeLibrarySystem
TheVirtual Tape Librariesbranchliststhevirtualtapelibrariesthatare currentlydefined.Eachvirtualtapelibrarycontainsavirtualtapedrivebranch containingoneormoredrivesandavirtualtapebranchcontainingoneormore tapes,sortedinbarcodeorder.RightclickingonthemembersoftheVirtual Tape Librariessubbranchbringsupacontextmenulistingoperationsthatcanbe performedonthebranch.Theseinclude:

assigningvirtualtapelibrariesand/ordrivetoSANclients(backupservers). creatinganddeletingvirtualtapes creatinganddeletingvirtualtapedrives enablingreplicationorautoarchivingfeaturesfortapesinthelibrary settingAutomatedTapeCachingpolicies(ifyouareusingthisoption) enabling,disabling,orconfiguringthetapecapacityondemandfeature movingvirtualtapesbetweenslots,drives,andthevirtualvault modifyingtapeproperties,suchasbarcodesandwriteprotection

TheVirtual Tape Drivesbranchliststhestandalonevirtualtapedrivesthatare currentlydefined.RightclickingonthemembersoftheVirtual Tape Drives subbranchbringsupacontextmenulistingoperationsthatcanbeperformedonthe branch.

24

VTL User Guide Mar 2008

F 96267

Understanding the VTL console interface

TheVirtual Vaultbranchliststhevirtualtapesthatarecurrentlybeingstored outsidethevirtualtapelibraries,inbarcodeorder.Virtualtapesinthevaultcanbe replicated,exportedtoaphysicaltape,ormovedtoavirtuallibraryorstandalone drive.Thenumberoftapesthatcanbestoredinthevaultislimitedonlybythe availablediskstoragespace. TheImport/Export Queuebranchliststheimportandexportjobsand AutomatedTapeCachingjobsthathavebeensubmitted.Ifneeded,youcancancela pendingjobfromhere.Youcanhaveupto32concurrentimport/exportjobs running,dependinguponthenumberofphysicaltapedrivesattachedtoyourVTL. ThePhysical Tape Librariesbranchliststhephysicaltapelibrariesthatare availabletoVTL.Rightclickingonthemembersbringsupacontextmenuthatlets youinventoryslots,import/exportormovephysicaltapes,copythephysicaltapeto virtualtape,orlinkphysicaltapetovirtualtapefordirectaccess. ThePhysical Tape Drivesbranchliststhestandalonephysicaltapedrivesthat areavailabletoVTL.Rightclickingonthemembersbringsupacontextmenuthat letsyouejectphysicaltapes,copyphysicaltapestovirtualmedia,orlinkphysical tapestovirtualmediafordirectaccess. TheReplica Resourcesbranchliststhevirtualtapesthathavebeenreplicated fromaremoteserver.Clientsdonothaveaccesstoreplicaresources. TheDatabasebranchcontainsconfigurationinformationfortheVTL.Thedatabase canbemirroredforhighavailability.

SANClients
TheSAN Clients branchoftheVTLobjecttreeliststhebackupserversthatback updatatoVTLlibraries.Byrightclickingonthisbranchanditssubbranches,you canaddSANclients,assignthemtolibraries,unassignthem,viewclient properties, etc.

Reports
The Reports branchoftheVTLobjecttreeholdsreportsthatyougenerate. Reportscancover:

throughput physicalresourceallocationandconfiguration diskspaceusage FibreChanneladapterstatusandconfiguration replicationstatus


Chapter 3 Using the VTL console 25

96267 F

Understanding the VTL console interface

virtualtapeandlibraryinformation jobstatus

Byrightclickingonthisbranch,youcanselectandgeneratereports.

PhysicalResources
ThePhysical ResourcesbranchoftheVTLobjecttreelistsFibreChannelHBAs andstoragedevicesattachedtotheVTLserver.Storagedevicesincludethedisk volumesthatholdvirtualtapes,physicaltapelibrariesandphysicaltapedrives. Rightclickingonthisbranchoritssubbranchesbringsupcontextmenusthatletyou scandevicesorpreparedevicesforuseasvirtualtape. Thefollowingtabledescribestheiconsthatdescribephysicalresourcesinthe consoleobjecttree:
Icon Description

The Tinterfaceiconindicatesthatthisisatargetport. The Iinterfaceiconindicatesthatthisisaninitiatorport. The Dinterfaceiconindicatesthatthisisadualportinterfacecard. Theredarrowindicatesthatthisinterfacehasnoaccesstostorage.Eitheradevice isnotconnectedtotheinterface,orthedeviceisdown. The Viconindicatesthatthisdiskhasbeenvirtualized. The Diconindicatesthatthisisaphysical(Direct)device. The Ficonindicatesthatthisissharedstorageandisbeingusedbyanother server.The Owner fieldliststheotherserver.

26

VTL User Guide Mar 2008

F 96267

CHAPTER

VTLoperations
Thischaptercoversroutineconfiguration,administration,andmanagementof servernodes,virtualtapelibraries,drives,andtapes,including:

Managingnetworkconnectivityonpage 27 Managingvirtuallibrariesonpage 33 Managingtapesonpage 76 Managingtapecachingonpage 109 Creatingandviewingreportsonpage 112 Encryptingandshreddingdataonpage 116 WorkingwiththeEventLogonpage 124 ManagingVTLserversonpage 129.

Managingnetworkconnectivity
VTLappliancesuseyourEthernetlocalareanetwork(LAN)forsystemmanagement andadministrationandyourstorageareanetwork(SAN)forconnectingtothe systemsstorageclients(yourbackuphosts).Sunservicespersonnelestablish requiredconnectivityduringthesysteminstallationprocess.However,ifyou subsequentlymakechangestoyournetworkconfigurations,youcanupdatetheVTL configurationusingtheproceduresinthissection.

Configuringlocalareanetworkconnectionsonpage 28 SettingtheVTLservernodehostnameonpage 30 ObtainingSANinterfaceconfigurationinformationonpage 31 AdministeringSANclientconnectionsonpage 32.

96267 F

27

Managing network connectivity

Configuringlocalareanetworkconnections
1. IntheNetwork Configurationpropertysheet,entertheDomain name (A below).ChecktheAppend suffix to DNS lookupcheckbox(B)ifthe customerneedstoappendthedomainnametothemachinenameduringDNS lookup.

A domain_name B
nnn.nnn.nnn.1

nnn

. nnn . nnn . nnn

NIC_name

2. EnterIPaddressinformationfortheDomainNameServer(ifused)intheDNS section(C above),usingtheAddandEditbuttons. 3. EntertheIPaddressoftheDefault gateway(D above). 4. SelecttheNIC_nameEthernetinterface,andpushtheConfig NICbutton (E above). NIC_nameisnge0onVTLPlussystemsande1000g0onVTL Valuesystems. OnVTLPlussystems,donotchangetheconfigurationoftheotherEthernet interfaces.Theyarereservedforsystemuse.Fordetails,seetheappendixonVTL privatenetworkaddresses.

28

VTL User Guide Mar 2008

F 96267

Managing network connectivity

5. WhentheIP Address Configurationpropertysheetappears,clicktheStatic radiobutton(F below).


F

NIC_name nnn.nnn.nnn.nnn

G H J

6. ClicktheEditbutton(G above),andentertheIPaddressthatthecustomer provided. 7. LeavetheMTUtextfield(H above)assetbythefactory. 8. PressOK(J above). YoureturntotheNetwork Configurationpropertysheet. 9. IfNetworkTimeProtocol(NTP)isinuse,pressConfig NTP(K above).Whenthe NetworktimeProtocolServersdialogappears,usethecontrolsprovided(L)to entertheNTPserverIPaddresses.ClickOK(M).
NIC_name

ntp_server_name

96267 F

Chapter 4 VTL operations

29

Managing network connectivity

NotetheEnable SSH,Enable FTP,andAllow root to login in telnet sessioncheckboxes.Whilesshisenabledbydefault,ftpandremote loginby rootaredisabledforsecurityreasons.Sunrecommendsthatyouleavetheseoptions settothedefaults.Forsecureremoteaccess,usethevtladminaccountwithsshor sftp.Then,ifrootprivilegesarerequired,usethesucommandafterloggingin. 10. Whenyoureturntothe Network Configuration propertysheet,clickOK (N above). 11. Whenyouarepromptedtorestartthenetwork,press Yes (O below).

Thenetworkshouldrestartautomatically. 12. ReconnecttotheVTLservernode. Stophere.

SettingtheVTLservernodehostname
1. WhentheSet Hostnamedialogappears,enteravalidnameforyourVTL appliance(A below).

A B

Validcharactersincludeletters,numbers,underscores,anddashes. 2. PressOK(B above).

30

VTL User Guide Mar 2008

F 96267

Managing network connectivity

3. Whenpromptedtorestartthenetworkandserver,press Yes (Cbelow).

4. Logbackintotheservertocontinueworking. Stophere.

ObtainingSANinterfaceconfigurationinformation
YoucanobtaintheconfigurationinformationforanyoftheFibreChannelhostbus adaptersontheVTLserverbyexaminingtheobjectintheVTLconsole. 1. InthetreeviewpaneoftheVTLconsole,selectPhysical Resources (A below) andStorage HBAs (B).

A B C

96267 F

Chapter 4 VTL operations

31

Managing network connectivity

2. SelecttheHBAthatyouwishtocheck(C above),and,inthepaneatright,usethe tabstolocatetherequiredinformation(D). Stophere.

AdministeringSANclientconnections
YoucanobtaintheconfigurationinformationforanyofaVTLserversSANclients byexaminingtheobjectintheVTLconsole,asdescribedbelow. ToaddaSANclient,seeConnectingvirtuallibrarieswithstorageclientson page 61. 1. InthetreeviewpaneoftheVTLconsole,selectSAN Clients (A below)and clickonthenameoftheclient(B).

A B

2. Inthepaneatright,usethetabstoseeadapterinformation(C above).

32

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

3. Toseevirtualdeviceassignments,expandtheclientnode(D below)andFibre Channelprotocolnode(C)ofthetreeview.

D E

4. Rightclickingontheclientnode(D above)orFibre Channelprotocol(C)node opensamenuofadministrativeactions(F). Usingthecontextmenu,youcanAssignvirtualdevicestoclients,Unassign virtualdevicesfromclients,Delete theclientorprotocol,Detachdevices,and vieworrefreshclientproperties. Stophere.

Managingvirtuallibraries
Thissectioncoverstheessentialconfigurationtasksthatareperformedwhenever virtuallibraries,devices,andmediaareaddedtotheVTLsystem.Duringinitial configuration,thetasksinthissectionarerunsequentiallybytheVTLconfiguration wizard.Duringroutinesystemmaintenance,youmayalsorunthemindependently, asdescribedbelow:

Configuringandprovisioningvirtuallibrariesonpage 39(includesCreating virtualtapelibrariesonpage 41andCreatingvirtualtapesonpage 53) Connectingvirtuallibrarieswithstorageclientsonpage 61.

96267 F

Chapter 4 VTL operations

33

Managing virtual libraries

Configuringphysicallibrariesanddevices
VTLsoftwaresupportseitherdirectattachedlibrariesor,optionally,sharedlibraries managedbyACSLS/LibraryStationsoftware.

Ifyouareusingadirectattachedlibrary,seeManagingdirectattachedphysical tapestorageonpage 34. Ifyouareusingasharedlibrary,seeManagingACSLSandLibraryStationtape poolsonpage 38.

Managingdirectattachedphysicaltapestorage
Ifyouhaveadirectattachedlibraryordevice,youmustassignthelibraryordevice toVTLusingtheVTLconsolesoftware.Carryoutthefollowingtasks:

Preparingphysicallibrariesanddevicesforassignmentonpage 34 Assigningdirectattachedphysicaltapelibraries/devicesonpage 37.

Preparingphysicallibrariesanddevicesforassignment
1. Ifyouhavenotaddedanewphysicallibraryortapedevice,stophereandgoto thenexttask.

34

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

2. Otherwise,intheobjecttreeoftheVTLconsole,rightclickthePhysical Resourcesnode(A below),andselectPrepare Devicesfromthecontext menu (B).

A B

3. WhentheSelect a Preparation Operationdialogappears,clickthe Prepare Device(s) radiobutton(C below).

C D

4. SelectReserved for Direct DevicefromtheDevice Categorylistcontrol (D above),andpressNext(E).

96267 F

Chapter 4 VTL operations

35

Managing virtual libraries

5. Whenthe Select Physical Devicespanelappears,usethecheckboxes and/ortheselectionbuttons(F below)toselectthelibrariesordevicesthatyou wanttoassigntotheVTLsystem.PressNext(G). IfyouareconfiguringanIBMiSeries/AS400solution,assignIBMMagstar3590E11, 3592,orUltriumLTO1,LTO2,orLTO3physicaldrivestothevirtualtapelibraryfor useinimportandexportoperations.

A B

6. WhenthePrepare Devicepanelappears,pressFinish. Nexttask: Assigningdirectattachedphysicaltapelibraries/devicesonpage 37.

36

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Assigningdirectattachedphysicaltapelibraries/devices
1. IntheobjecttreeoftheVTLconsoleapplication,openthebranchfortheVTL server(A below).

A B

D C

2. OpenthebranchfortheVirtual Tape Library System(B above). 3. RightclickonthePhysical Tape Librariesbranch(C above),andselect Assign fromthecontextmenu(D). 4. WhentheSelect Libraries or Drivesdialogappears,usethecheckboxes andorselectionbuttons(E below)toassignphysicaltapedrivestotheVTL system.

5. PressFinish(F above). Stophere.


96267 F Chapter 4 VTL operations 37

Managing virtual libraries

ManagingACSLSandLibraryStationtapepools
WhentheVTLsoftwaresACSLS/LibraryStationoptionisenabled,SunStorageTek ACSLSManagerorLibraryStationsoftwaremanagesthephysicallibraryandthe tapevolumesintheVTLsystemsassignedtapepools.Youmerelyneedtoupdate theVTLconsoleviewwhenevertapesareaddedorremovedfromthepool.Proceed asfollows.

InventoryingACSLS/LibraryStationlibrariesfromVTL

whenevertapesareaddedtoorremovedfrompools
WhenyouaddorremovetapesfromanACSLS/LibraryStationpool,inventorythe tapesthroughtheVTLConsole: 1. IntheobjecttreeoftheVTLconsole,openthebranchfortheVTLserver (A below). 2. OpenthebranchfortheVirtual Tape Library System(B below). 3. OpenthebranchforthePhysical Tape Libraries(D below). 4. Rightclickonthenameofthephysicallibrary(D below),andselectInventory fromthecontextmenu(E).

A B

E C D

Stophere.

38

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Configuringandprovisioningvirtuallibraries
Thissectiondescribestheproceduresforcreatingandmaintainingvirtuallibraries, withtheirvirtualdrivesandmedia.Itdocumentsthefollowingprocedures:

Settingvirtuallibrarysystempropertiesonpage 39 Creatingvirtualtapelibrariesonpage 41 Settingupoptionalfunctionality(seeConfiguringAutomatedTapeCachingon page 44,SettinguptheAutoArchivefeatureonpage 48,orSettingupthe AutoReplicationoptiononpage 49) Generatingthevirtuallibraryonpage 50 Creatingvirtualtapesonpage 53.

Settingvirtuallibrarysystemproperties
1. InthetreeviewattheleftoftheVTLconsole,rightclicktheVirtualTape Library System(A below),andselectPropertiesfromthecontextmenu(B).

2. WhentheChange VirtualTape Librarypropertiessheetappears,ifyouwish touseVTLcompressionsoftware,checktheEnable Virtual Tape Library compression mode checkbox(C below). Consideryourrequirementscarefullybeforeenablingsoftwarecompression. Softwarecompressionisacomputationallydemandingoperationthatconsumes processorcyclesthatwouldotherwisebeusedtomovedata.Whenyouenablethe feature,youthustradethroughputperformanceforcapacity.MostVTLsolutionsare aimedatincreasingbackupperformance.VTLstorageisusedasafast,temporary repositoryfordatathatwillbemovedtophysicaltapeforlongtermstorage.Insuch cases,thehardwarebasedcompressioncapabilitiesofphysicaltapedrivesprovide

96267 F

Chapter 4 VTL operations

39

Managing virtual libraries

boththeneededlongtermstoragecapacityandthefastestpossibletransfertotape media.Compressionhardwarecannotfurthercompressdatathathasbeen compressedbysoftware,sotheendtoendbackupprocessissignificantlyslower. Ontheotherhand,theVTLsoftwarecompressionfeatureisvaluablewhenitistruly needed:

whendataisstoredontheappliancelongterm,ratherthancachedpending migrationtolongtermstorageonphysicaltape whendatahastobereplicatedacrossaslowWANlink.

D
85

3. Ifyouplantousetapecaching,usethespinnercontroltoadjusttheTape Caching Policy Disk Capacity Thresholdto85%(D above). Whenusingautomatictapecaching,youhavetomakesurethatthediskneverfills up,preventingyoufromcreatingnewvirtualvolumes.The75%thresholdhasbeen foundtoofferagoodmarginofsafety. 4. PressOK(E above). Stophere.

40

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Creatingvirtualtapelibraries
1. WhentheCreate Virtual Library Wizardappears,selectthetypeoflibrary thatyouwanttoemulate(A below),enteraVirtual Library Name(B)oruse thedefault,andpressNext (C). Selectthe Sun VTL librarytypeforcompatibilitywithmajorbackupapplications, suchasSymantecNetBackup.ForcompatibilitywithIBMiSeries/AS400clients, choosetheIBM3590,IBM3584,orIBM3583librarytype.

B A-SUN-VTL-02255

A C

Managementiseasierwhenyougivelibrariesandthevirtualtapestheyholda commonalphabeticalprefix,suchastheA-prefixshownintheexample(A above). 2. WhentheEnter Virtual Drive Informationdialogappears,selectthetype oftapedriveyouwanttoemulate(D below),andenteraVirtual Drive Name Prefix (E).

E F

96267 F

Chapter 4 VTL operations

41

Managing virtual libraries

IfyouplantoattachaphysicaltapelibrarytotheVTLappliancefortapeimportor export,emulatethephysicallibrarysothatvirtualtapeswillbecompatiblewith theirphysicalcounterparts. 3. SelecttheTotal Virtual Drivesusingthespinnercontrol(F above),andpress Next (G). ToinsurethatthefourtargetportsonaVTLappliancearefullyandevenlyutilized, createonevirtuallibraryandatleastfourvirtualtapedrivesforeachclient(backup server)thatconnectstotheVTLsystem. 4. Ifyouaregoingtousetapecaching,checktheEnable Automated Tape Cachingcheckboxwhenthedialogappears(H below).PressNexttoenterthe change(J).Thenstophere,andgototheNext tasklistattheendofthisprocedure.

5. Ifyouarenotgoingtousetapecaching,pressNext(K below)toskipoverthe Enable and configure tape caching policydialog.

TheAuto Archive/Replicationdialogappears.

42

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

6. Ifyoudonotintendtoimplementautoarchivingorreplication,pressNext (L below)toskipovertheAuto Archive/Replicationdialog.

TheAuto Archiveoptionwritesdatatophysicaltapewheneverabackup applicationorutilitymovesavirtualtapefromavirtuallibrarytoanimport/export slot.Thephysicaltapelibrarymustsupportbarcodes:theVTLsoftwarehastofinda matchingbarcodeinthephysicallibraryinordertoexportavirtualtapetoa physicalcartridge(youdonotneedtospecifywhichphysicallibrary). TheAuto Replicationoptioncopiesvirtualtapesfromavirtuallibraryto anotherVTLserverwheneverabackupapplicationorutilitymovesavirtualtapeto animport/exportslot. Nexttask:

Ifyouaregoingtoconfiguretapecachingonthisvirtuallibrary,goto ConfiguringAutomatedTapeCachingonpage 44. Ifyouaregoingtousetheautomaticarchivingfeatures,gotoSettingupthe AutoArchivefeatureonpage 48. Ifyouaregoingtousetheautomaticreplicationfeature,gotoSettingupthe AutoReplicationoptiononpage 49 Otherwise,gotoGeneratingthevirtuallibraryonpage 50.

96267 F

Chapter 4 VTL operations

43

Managing virtual libraries

ConfiguringAutomatedTapeCaching
YouconfigureAutomatedTapeCachingforthevirtuallibrarybydefininga migrationpolicyandareclamationpolicy.AVTLpolicyissimplyasetofcriteria (triggers)thatcontrolhowandwhenVTLsoftwareautomaticallymovesdatafrom itsphysicaldiskcache.Usingtheconfigurationdialogs,youcanspecifysimple schedulesormorecomplexstateandeventdrivenpolicies. MigrationpoliciescontrolwhenVTLcopiesdatafromthediskcachetophysical tape.Goodmigrationpoliciesmaximizetheperformanceandreliabilityofthedisk cachebyminimizingsimultaneousreadsandwrites.Simultaneousreadsand writescrossI/Oforcediskarraystoswitchbackandforthbetweenmultiple, competingI/Osteams,reducingthroughputandsubjectinghardwaretoexcessive wear.Sobestpracticeistoschedulemigrationassoonaspossibleafterabackup ANDatatimewhenotherbackupjobsarenotrunning. ReclamationpolicescontrolwhenVTLreleasesthediskspacethatisusedbyadata setthathasalreadymigratedtotape.Promptandefficientreclamationprevents oversubscriptionofthediskandconsequentbackupfailuresandsystemdowntime, whileminimizinginvestmentincachecapacity.Bestpracticeistoreclaimspaceas soonasthehighestdemandforrestoreshaspassedtypicallyafterthreetofive days.Thisapproachstrikesthebestbalancebetweentakingadvantageofthespeed andconvenienceofadiskbasedrestoreandminimizingconsumptionofcache space. Tocreateamigrationpolicy,selectoneofthefollowingapproaches:

Creatingsimplescheduledrivenmigrationpoliciesonpage 44 Creatingstateandeventbasedmigrationpoliciesonpage 45.

ThengotoCreatingareclamationpolicyonpage 47.

Creatingsimplescheduledrivenmigrationpolicies
WhenthePlease select migration trigger(s)dialogappears,proceedas follows. 1. ClicktheTime Basedradiobutton(A below). 2. Tomigratedataeveryday,clicktheDaily Migration Scheduleradio button (B below).Usingthecontrolsprovided(C),enterthetimewhenmigration shouldbegin.

44

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

3. Tomigratedataeveryweek,clicktheWeekly Migration Check Schedule radiobutton(D below),andspecifythedayoftheweekandtimeofdaywhen migrationshouldbegin(E).

A B E C

4. PressNext (F above). Nexttask: Creatingareclamationpolicyonpage 47.

Creatingstateandeventbasedmigrationpolicies
WhenthePlease select migration trigger(s)dialogappears,proceedas follows. 1. Tomigratedatabasedonthestateofdataand/orvirtualstorage,clickthePolicy Basedradiobutton(A below).

96267 F

Chapter 4 VTL operations

45

Managing virtual libraries

2. TomigratedatawhenALLofoftheconditionsspecifiedaresatisfied,clickthe Andradiobutton(B below).

A B D C

G H J

3. TomigratedatawhenONEORMOREoftheconditionsspecifiedissatisfied, clickthetheOrradiobutton(C above). 4. Totriggermigrationbasedontheageofthedata,checktheAge Basedcheckbox, andusethespinnercontroltoselectthedesirednumberofdays(D above). 5. Totriggermigrationbasedondiskusage,checktheDisk Capacity Based checkbox(E above). 6. Totriggermigrationbasedontheendofabackupjob,checktheEnd of Backup checkbox(F above).Ifyouwanttheendofabackpjobtotriggermigrationonly whenatapeisfull,alsochecktheOnly When Tape Is Fullcheckbox (G above). 7. Todelaymigrationforaspecifiedperiodfollowinganothertriggeringevent, checkthecheckDelay Migration Unitlcheckbox,andenterthenumberof hoursandminutesforthedealyintheboxprovided(H above). 8. PressNext(J above). Nexttask: Creatingareclamationpolicyonpage 47.

46

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Creatingareclamationpolicy
Thereclamationpolicydetermineswhenexpiredvirtualvolumesarereleased. Proceedasfollows. 1. WhenthePlease select a reclamation triggerdialogappears,clickthe radiobuttonthatcorrespondstothedesiredtriggeringcondition(A below).

2. IfyouchoosetospecifyaRetention Period,usethespinnercontrol(B above) tospecifythenumberofDay(s). 3. ThenpressNext(C above). Nexttask: Generatingthevirtuallibraryonpage 50.

96267 F

Chapter 4 VTL operations

47

Managing virtual libraries

SettinguptheAutoArchivefeature
1. WhentheAuto Archive/Replicationdialogappears,checktheAuto Archive/Replicationcheckbox(A below).

A B C D E

2. SpecifyAutoArchivebyclickingtheAuto Archiveradiobutton(B above). 3. SelectthedesiredarchivingbehaviorbyclickingeithertheMoveradiobutton (andsettingthegraceperiodusingthespinnerandlistcontrolsprovided)orthe Copyradiobutton(C above). TheCopyoptioncopiesthevirtualvolumetophysicalmedia,leavingthevirtual volumeondisk.TheMoveoptiondeletesthevirtualvolumefromdiskoncethe specifiedgraceperiodhasexpired. 4. Ifyouwishtoejecttapestoimport/exportslots,checktheEject physical tapes to I/E slots after exportcheckbox(D above). 5. Ifyouwishtoencryptthearchiveddata,checktheEncrypt data...checkbox, andselectakeyfromthelistcontrolprovided(E above). 6. PressNext(F above). Nexttask: Generatingthevirtuallibraryonpage 50.

48

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

SettinguptheAutoReplicationoption
1. WhentheAuto Archive/Replicationdialogappears,checktheAuto Archive/Replicationcheckbox(A below).

B C D F G E

2. ClicktheAuto Replicationradiobutton(B above). 3. Tocopyvirtualmediatothetargetlibrarywhileleavingthesourcevirtualmedia inthesourcelibrary,clicktheCopyradiobutton(C above). 4. Tomovevirtualmediatothetargetlibrary,deletingthesourcevirtualmedia,click theMoveradiobutton(D above).Ifyouwanttoretainthesourcevolumesinthe sourcelibraryforaspecifiedperiodbeforedeletingthem,defineagraceperiod usingthespinnerandlistcontrolsatright(E). 5. SelecttheRemote server namefortheserverthatwillhostthereplicateddata. Selectanamefromthelistcontrolprovided,orpressAddtoaddaservertothe list(F above). 6. PressNext(G above). Nexttask: Generatingthevirtuallibraryonpage 50.

96267 F

Chapter 4 VTL operations

49

Managing virtual libraries

Generatingthevirtuallibrary
1. WhentheEnter Virtual Library Informationdialogappears,entera Barcode Startsvalueinthetextfieldprovided(A below). Enterexactlysix(6)characterswhenemulatingSunStorageTeklibrariesneither morenorless. Hint:managementiseasierwhenyougivelibrariesandthevirtualtapestheyholda commonalphabeticalprefix,suchastheAprefixshownintheexamplebelow.

A B

2. EnteraBarcode Endsvalueinthetextfieldprovided(B above). 3. PressNext(C above). Donotchangeproperties(suchasthenumberofslots)ifyouhavechosento emulateaparticularphysicallibrary(suchasaSunStorageTekSL500)ratherthan thegenericSunVTLlibrary.Fromanapplicationorclientpointofview,virtualand physicalinstancesofagivenlibraryshouldbefunctionallyidentical.Iftheyarenot, clientsandapplicationsmaybehaveinunanticipatedways.

50

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

4. WhentheEnter virtual tape propertiesdialogappears,checktheTape Capacity On Demandcheckbox(D below).

Werecommendcapacityondemandformostusers. 5. Ifyouhaveenabledsoftwarecompression,usethespinnercontrol(E above)to reducetheMaximum Capacityto8590%oftheuncompressedcapacityofthe selectedmedia. Intheexampleabove,wewouldreducemaximumcapacityto3436GBwhenusing compression. Leavingtherecommendedmarginisimportant,becausethecompressionratio possiblewithanygivendatasetisdifficulttopredict.Adatasetthathappensto containasignificantnumberofincompressiblefiletypes(suchasZIPandRAR archives,PDFdocuments,GIFandJPGimages,andmanybinaryfiles)willnot compressasmuchasadatasetthatcontainsonlycompressibledata. 6. Otherwise,acceptthedefaultvaluesforallsettings.Inparticular,donotincrease Maximum Capacity beyondthecapacityoftheemulated Media Type.Ifyou do,youriskoversubscribingthedisk,andclientsandapplicationsmaybehavein unanticipatedways. 7. PressNext(E above).

96267 F

Chapter 4 VTL operations

51

Managing virtual libraries

8. Whentheconfirmationscreenappears,pressFinish(F below).

9. WhentheBatch Creation Statuspanelappears,pressOK(G below).

Nexttask: Ifyoudecidedtocreatetapes,gotoCreatingvirtualtapesonpage 53.

EnablingAutoReplicationonanexistinglibrary
1. IntheobjecttreeoftheVTLconsole,expandthenodefortheVTLserver. 2. UndertheVTLserver,expandtheVirtual Tape Library Systemand Virtual Tape Librariesnodes. 3. UndertheVirtual Tape Librariesnode,rightclickonthevirtualtapelibrary thatyouwanttoenable,andselectProperties.

52

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

4. WhentheChange Virtual Library Propertiespropertysheetappears, checktheAuto Archive/Replicationcheckbox(A below),andclicktheAuto Replicationradiobutton(B).

B C

5. SelectthedesiredreplicationmethodbyclickingtheCopyradiobuttonorby clickingtheMoveradiobuttonandenteringagraceperiodusingthelistand spinnercontrolsprovided(C above). 6. SelecttheRemote server namefortheserverthatwillhostthereplicateddata. Selectinganamefromthelistcontrolprovided,orpressAddtoaddaservertothe list(D above). 7. PressOK(E above). Stophere.

Creatingvirtualtapes
Followtheproceduresoutlinedbelow:

96267 F

Chapter 4 VTL operations

53

Managing virtual libraries

Enablingtheadvancedtapecreationmethodonpage 54 Settingreplicationparametersforvirtualtapevolumesonpage 58 Launchingthevirtualtapebatchcreationprocessonpage 61.

Enablingtheadvancedtapecreationmethod
1. Ifyouhavenotalreadydoneso,fromtheconsolemainmenu,selectTools (A below),thenselectConsole Options (B)fromthesubmenu. 2. WhentheConsole Options propertysheetappears,makesurethatthe Enable advanced tape creation method checkbox(E above)ischecked, andpress OK (F).

C D

TheadvancedtapecreationmethodisenabledbydefaultstartingwithVTL Plus 2.0. Sunrecommendstheadvancedtapecreationmethodbecauseitmakesiteasierto avoidcreatingmorevirtualtapesthantheavailablediskspacecanholdandmakes iteasiertomanagemultiplevirtualtapesinmultiplelibraries. Whentheadvancedmethodisenabled,tapecreationdialogsdisplaytheavailable diskspacealongsidethecontrolsthatspecifyinitialtapesizeandthedesired numberoftapes.Usingthisvalue,youcancalculatethemaximumnumberoffull cartridgesthatyoucancreatewithoutoversubscribingthedisk.WhileVTLsoftware triestocalculatethisvalueforyou,itdoessousingthecurrentlyallocatedsizeofthe virtualtapes.IfyouareusingthecapacityondemandfeatureoftheSunVTL,the currentlyallocatedsizeistheincrementsize(typically5 GB),notthefullcapacityof theemulatedmedia(forexample,40GBforSunStorageTek9840Ccartridges).Asa
54 VTL User Guide Mar 2008 F 96267

Managing virtual libraries

result,thesoftwarewillletyoucreateasmanyincrementsizedtapesaswillfitinthe availablediskspace,uptothemaximumnumberofslotsdefinedforthelibrary(658 fortheSun VTLlibrarytype).Ifyouacceptthisnumberandcreatethetapes,the systemwillrunoutofdiskspacelongbeforethetapesappeartobefull. Theadvancedmethodalsoaddsacontroltothetapecreationinterfacethatletsyou assignprefixestotapenames.Byassigningthesameprefixtoboththevirtual libraryandeachofitsvirtualtapes,youcangreatlysimplifysubsequentlibrary management. Nexttask: Creatingvirtualtapesonpage 55.

Creatingvirtualtapes
1. WhentheSelect Physical Devicesdialogappears,pressSelect All (A below).

A B

2. PressNext (B). Nexttask: atthispoint,thebehavioroftheconfigurationwizarddependsonthe configurationofthevirtuallibrary:

IfthenewvirtualtapeswillresideinalibrarythathastheAutoArchiveoption enabled,thewizarddisplaystwoadditionaldialogsatthispoint,Select a Physical Tape LibraryandSelect Physical Tapes.SogotoSetting AutoArchiveparametersforvirtualtapevolumesonpage 56. Otherwise,thewizardskipsdirectlytotheSpecify Batch Mode Informationdialog.SogotoAllocatingdiskspacetovirtualtapesonpage 57.

96267 F

Chapter 4 VTL operations

55

Managing virtual libraries

SettingAutoArchiveparametersforvirtualtapevolumes
IfthenewvirtualtapeswillresideinalibrarythathastheAutoArchiveoption enabled,proceedasfollows. 1. IntheSelect a Physical Tape Librarydialog,checktheCreate virtual tape(s)tomatchphysicaltape(s)...checkbox(A below).PressNext (B).

nnn.nnn.nnn.nnn ...

nnn.nnn.nnn ...

CheckingtheCreate virtual tape(s) to match physical tape(s) ... checkboxinsuresthatthebarcodesofthenewvirtualtapeswillmatchthoseofthe physicaltapes,thusfulfillinganessentialprerequisiteforautoarchiving. 2. IntheSelect Physical Tapesdialog,selectphysicaltapesusingthecheck boxes(C below)and/orbuttoncontrolsprovided(D ).ThenpressNext(E).

Nexttask: Allocatingdiskspacetovirtualtapesonpage 57.

56

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Allocatingdiskspacetovirtualtapes
1. WhentheSpecify Batch Mode Informationpanelappears,entera descriptiveprefixforthevirtualtapelabels(A below). Managementiseasierwhenyougivelibrariesandthevirtualtapestheyholda commonalphabeticalprefix,suchastheAprefixshownintheexampleabove(A).

2. IfyouonlyplantocreateonevirtuallibraryforyourVTLsystem,youcanuseall oftheavailablediskcapacityfortapes.EntertheMaximum(B below)asthenew valuefortheNumber of Virtual Tapes(C below).

B C

D E

96267 F

Chapter 4 VTL operations

57

Managing virtual libraries

3. Otherwise,ifyouplantocreateadditionallibrarieslater,dividetheMaximum (B above)betweenthelibraries,andenterthenumberallocatedtothislibraryas the Number of Virtual Tapes (C). ThenewvaluehastobelessthantheMaximum,sothatcapacityisreservedfor creatingtapesfortheadditionallibraries. 4. ChecktheUse Default ID for Starting Numbercheckbox(D above).Press Next(E). 5. WhentheSet Barcode Range Option panelappears,checktheUse the following barcode range for this batchcheckbox(F below),andpress Next(G).

Nexttask:

IfyouareusingtheAutoReplicationfeature,gotoSettinguptheAuto Replicationoptiononpage 49. Otherwise,gotoLaunchingthevirtualtapebatchcreationprocesson page 61.

Settingreplicationparametersforvirtualtapevolumes
IfthenewvirtualtapeswillresideinalibrarythathastheAutoReplicationoption enabled,proceedasfollows.

58

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

1. WhentheSelect Target Server for Auto-Replication Optiondialog appears,checktheAutomatically replicate the virtual tape(s) to the selected target servercheckbox(A below).

C B

2. Selecttheremoteserverfromthelist(B above),orpressAddtoaddaservertothe list(C).PressNext(D). 3. WhentheTarget Server Informationpanelappears,pressNext(E below).

remote_server_IP

96267 F

Chapter 4 VTL operations

59

Managing virtual libraries

4. WhentheSpecify Replication Timeout and Retry Policypropertysheet appears,configuretimeoutandretryintervalsusingthespinnercontrolsprovided (F below).ThenpressNext(G).

5. WhentheSpecify the Options for Data Transmissionpropertysheet appears,checktheCompress Data(H below)checkboxtoenablecompression. Compressionsoftwarecanbevaluablewhentransmittingreplicadataoverslow links.However,assessrequirementscarefully.Considertheoperationalimpactof theadditionalprocessorworkloadandconsequentreductionsinthroughputbefore enablingthisoption.

6. ChecktheEncrypt Datacheckbox(J above)toenableencryptedtransmissions. Encryptionsoftwareisoftennecessarywhenreplicatingdataoverinsecurelinks. However,assessrequirementscarefully.Considertheoperationalimpactofthe additionalprocessorworkloadandconsequentreductionsinthroughputbefore enablingthisoption.

60

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

7. PressNext(K above). Nexttask: Launchingthevirtualtapebatchcreationprocessonpage 61.

Launchingthevirtualtapebatchcreationprocess
1. WhentheCreate Virtual Tapessummaryscreenappears,pressFinish (A below).

B A

2. WhenthebatchjobfinishesandtheVirtual Tape Batch Creation Status panelappears,pressOK(B above). Notethattapecreationcantakesometime,sothestatuspanelwillnotappear immediately. Stophere.

Connectingvirtuallibrarieswithstorageclients
Toconnectvirtuallibrarieswithclientmachines(typicallybackupapplicationor NDMPagenthosts),carryoutthefollowingtasks:

StartingtheAddClientWizardonpage 62

96267 F

Chapter 4 VTL operations

61

Managing virtual libraries

AddingSANclientsonpage 63 Assigningvirtuallibrariestostorageclientsonpage 66.

StartingtheAddClientWizard
1. InthetreemenuoftheVTLconsole,selecttheVTLserverbranch. 2. RightclicktheSAN Clientsbranch(A below). 3. SelectAddfromthecontextmenu(B below).

A B

Nexttask: AddingSANclientsonpage 63.

62

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

AddingSANclients
1. WhentheEnter the Generic Client Namedialogappears,entertheclient nameinthetextfieldprovided(A below).PressNext(B).

2. WhentheSelect Client Protocolsdialogappears,checktheFibre Channel checkbox(C below),andpressNext(D).

96267 F

Chapter 4 VTL operations

63

Managing virtual libraries

3. WhentheSet Client Fibre Channel Propertiespropertysheetappears, selecttheWorldWidePortName(WWPN)oftheinitiatorbycheckingthe correspondingcheckbox(E below),orpresstheAddbutton(F),enteranew Initiator WWPN,andpressOK(G).ThenpressNext(H).

F H

4. WhentheFibre Channel Optionpanelappears,checkthecheckboxesforany optionalsupportthattheclientrequires(J below).ThenpressNext(K).

64

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

5. WhentheAdd the Generic Clientsummaryscreenappears,pressFinish (L below)toaddtheclient.

client_name

WWPN

Nexttask: StartingtheAssignaVirtualTapeLibraryWizardonpage 65.

StartingtheAssignaVirtualTapeLibraryWizard
VTLstorageclientsarethebackupapplicationhoststhatmanageyourbackupjobs. Toassignlibrariestoclients,proceedasfollows. 1. OpentheAssign a Virtual Tape Library Wizardbyrightclickingonthe objecttreenodeforvirtuallibrary,andselectingAssignfromthecontextmenu (A below).

A B

2. PressNext(B above). Nexttask: Assigningvirtuallibrariestostorageclientsonpage 66

96267 F

Chapter 4 VTL operations

65

Managing virtual libraries

Assigningvirtuallibrariestostorageclients
1. WhentheAssign a Virtual Tape Library Wizardappears,checkthe Assign the tape library and all drives...checkbox(A below),select aclient(B),andpressNext(C). Asageneralrule,assignonelibraryperclient.

virtual_library_name A
client_x

B client_y
client_z

2. WhentheSelect a Fibre Channel Targetpanelappears,selecttheTarget WWPNthatyouwillzonetotheclientfromthelist(D below),andpressNext(E). ToinsurethatthefourtargetportsontheVTLappliancearefullyandequally utilized,assignaminimumoffourvirtualtapedrivesperclient.

virtual_library_name

66

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

3. WhentheAssign a Fibre Channel Client to the Virtual Tape Libraryconfirmationscreenappears,pressFinish(F).

virtual_library_name
client_name

4. LogintoeachVTLclient(eachbackupserver),andscanfornewFibreChannel devices. Stophere.

BackinguptheVTLsystemconfiguration
WheneveryouchangetheVTLconfiguration,youshouldbackuptheconfiguration toasecurelocationonanothermachine.Thisprocesspreservesthevirtualtape libraries,virtualtapedrives,clients,clientassignments,replicationconfigurations, andfailoverconfigurationsfortheserver.Youcandothisineitheroftwoways:

ManuallysavingtheVTLconfigurationonpage 68 AutomaticallybackinguptheVTLconfigurationonpage 68.

96267 F

Chapter 4 VTL operations

67

Managing virtual libraries

ManuallysavingtheVTLconfiguration
1. IntheobjecttreeoftheVTLconsole,highlighttheVTLservernode(A below).
B

C E

2. FromtheVTLmainmenu,selectTools(B above). 3. Fromthesubmenu,selectSave Configuration(C above). 4. WhentheSavedialogappears,supplyafilename(D above),andpressSave (E). Stophere.

AutomaticallybackinguptheVTLconfiguration
ToinsurethattheVTLconfigurationisalwayprotected,usetheAutoSavefeatureto periodicallycreateapointintimesnapshotoftheVTLconfigurationonanother server.

68

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

1. IntheobjecttreeoftheVTLconsole,rightclickonthetheVTLserverbranch (A below).

2. Fromthecontextmenu,selectProperties(B above).

96267 F

Chapter 4 VTL operations

69

Managing virtual libraries

3. SelecttheAuto Save Config tab(C below).

C D E

H J

4. CheckEnable Auto Save Configuration File checkbox(D above). 5. Inthefieldprovided,entertheFtp Server Nameforthemachinethatwillhost thebackupconfigurationfiles(E above). ThetargetservermusthaveFTPserverinstalledandenabled. 6. EntertherelativepathtotheTarget Directoryinthefieldprovided(F above). Thespecifiedpathshouldberelativetotherootdirectoryoftheftpserver.Donot useanabsolutepath. 7. Enterhostlogoninformationfortheremoteserverinthefieldsprovided (G above). Thespecifiedusermustbeanftpuserontheremotehostandmusthaveread/write accesstothespecifiedtargetdirectory. 8. SpecifyareplicationIntervalusingthelistcontrolsprovided(H above). 9. SpecifytheNumber of Copiesthatshouldberetainedusingthespinner provided(J above). 10. ClickOK(K above).

70

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Stophere.

Recoveringtheserverconfiguration
IftheVTLserverconfigurationislostorcorrupt,youcanrecoveritfromabackup fileusingtheprocedurebelow.

Caution Thisisadisasterrecoveryprocedureonly.Neverexecuteitduringdayto dayoperationoftheserver.Restoringaconfigurationoverwritesexistingvirtual deviceandclientconfigurationsanddoesnotrestoreVTLpartitioninformation.

Restoringtheconfiguration
1. IntheobjecttreeoftheVTLconsole,selectthebranchfortheVTLserverthathas lostitsconfigurationinformation. 2. FromtheVTLmainmenu,selectTools. 3. Fromthesubmenu,selectRestore Configuration. 4. ClickOKtoconfirm. 5. Whenprompted,locatethebackupconfigurationfile. TheVTLserverrestarts. Notes:

Resourcesaddedaftertheconfigurationwassavedwillshowupinthe Virtual Vaultaftertheconfigurationisrestored. Deletedresourceswillbedisplayedinthevirtualtapelibrarywithareddot, indicatingincompletestatus.

ProtectingVTLmetadata
TheVTLdatabaseholdsthemetadatathatmapsdatastoredonvirtualtapeto locationsonthephysical,randomaccessdiskmedia.Withoutthiscritical information,virtualtapedatacannotberecovered,soprotectingitisessential. SunStorageTekVTLappliancesprotectthismetadatabystoringitonaRAID system,asetofstoragedisksconfiguredtosurvivethelossofanysinglememberof thesetwithoutlossofdata.

96267 F

Chapter 4 VTL operations

71

Managing virtual libraries

Mirroringsuppliesanadditionallayerofprotection.Mirroreddatabasesmaintain twoseparate,synchronizedcopiesofthemetadata,eitherofwhichcanprovide accesstovirtualtapedataonitsown.

MirroringtheVTLdatabase
1. IntheobjecttreeoftheVTLconsole,expandthebranchfortheVTLserver (A below). 2. ExpandtheVirtual Tape Library System branch(B below). 3. RightclickontheDatabaseobject(C below).

A B

E D C

4. Fromthecontextmenus,selectMirror(D above)andAdd(E).

72

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

5. WhentheSelect a Creation Methoddialogappears,selectExpress (F below),andpressNext(G).

TheExpressmethodtakesadvantageoftheintelligencebuiltintotheRAID subsystemtomakebestuseofdiskresources.

96267 F

Chapter 4 VTL operations

73

Managing virtual libraries

6. Whentheconfirmationdialogappears,confirmthatallinformationiscorrect,and thenclickFinishtocreatethemirrors. TheVTLsoftwarecreatesandsynchronizesthemirrordatabase.Whentheprocess completes,thevalueoftheMirror Synchronization Statusfieldofthe databasepropertysheetbecomesSynchronized(H below).

Stophere.

Removingamirrorconfiguration
1. Rightclickonthedatabase. 2. SelectMirror>Remove todeletethemirroredcopyandcancelmirroring.You willnotbeabletoaccessthemirroredcopyafterwards. Stophere.

Administeringuseracountsandpasswords
YoucanperformthefollowingtasksfromtheVTLconsole:

Managingadministratorsonpage 75 Changingadministratorpasswordsonpage 76.

74

VTL User Guide Mar 2008

F 96267

Managing virtual libraries

Managingadministrators
OnlytherootusercanaddordeleteaVTLadministratororchangean administratorspassword. 1. IntheobjecttreeoftheVTLconsole,rightclickontheservername(A below),and selectAdministratorsfromthecontextmenu(B).

A B
vtl

Therearetwotypesofadministrators:

VTL AdministratorsareauthorizedforfullVTLconsoleaccess. VTL Read-Only UsersareonlypermittedtoviewinformationintheConsole. Theyarenotauthorizedtomakechangesandtheyarenotauthorizedforclient authentication.

2. WhentheVTL User/Administrator Managementdialogappears,usethe controlsprovidedtomanageadministratoraccounts(C above). Whenyouaddanadministrator,thenamemustadheretothenamingconventionof theoperatingsystemrunningonyourVTLServer.Refertoyouroperatingsystems documentationfornamingrestrictions. Youcannotdeletethevtluserorchangethevtlpasswordfromthisscreen.Use theChange Passwordoptioninstead. Stophere.

96267 F

Chapter 4 VTL operations

75

Managing tapes

Changingadministratorpasswords
1. RightclickontheVTLservernodename(A below),andselectChange Password fromthecontextmenu(B).

2. Whenthedialogappears,enterthepasswordthatyouneedtochangeinthe Old Password textbox(C below).

C D E

3. Enterthechangedpasswordinthe New Password and Confirm Password textboxes(D above). 4. PressOK(E). Stophere.

Managingtapes
Thissectionaddressesthefollowingtopics:

Locatingvirtualtapes Copyingatapetoaremoteserver.

76

VTL User Guide Mar 2008

F 96267

Managing tapes

Locatingvirtualtapes
Tolocateavirtualtape,proceedasfollows.

Searchingforvirtualtapesbybarcode
1. Tolocateavirtualtape,selectEditfromthemainmenu. 2. ThenselectFindfromthecontextmenu. 3. Whenprompted,enterthefullbarcodeforthevirtualtape,andpressSearch. Theconsoleopenstheobjecttreeatthevirtualtape. Stophere.

Replicatingtapes
Thissectioncoverscreatingandworkingwithsynchronizedreplicasofvirtualtapes onlocaland/orremoteVTLservers.Topicsinclude:

Settinguptapereplicationformultipletapesonpage 77 Settingupreplicationforindividualtapesonpage 83 Manuallysynchronizingreplicas(manualreplication)onpage 89 Stoppingareplicationthatisalreadyunderwayonpage 89 Manuallysynchronizingreplicas(manualreplication)onpage 89 CheckingreplicationstatusfromthetargetVTLserveronpage 91 Checkingreplicationstatuswithareportonpage 91 Changingreplicationpropertiesonpage 92 Deletingareplicationconfigurationonpage 93 Promotingareplicaresourceonpage 93.

Settinguptapereplicationformultipletapes
1. Beforecontinuing,makesurethatyouhavewriteaccesstoboththeprimary (local)andtarget(remote)VTLserversandthatthereisenoughspaceavailableon thetargetforthereplicaresourcesyouintendtocreate. 2. IntheobjecttreeoftheVTLconsole,expandtheVTLservernode. 3. UndertheVTLserver,expandtheVirtual Tape Library System and Virtual Tape Librariesnodes.
96267 F Chapter 4 VTL operations 77

Managing tapes

4. UndertheVirtual Tape Libraries node,rightclickonthevirtualtape libraryforwhichyouwanttoenablereplication(Abelow). 5. Fromthecontextmenus,selectReplication(B below),Add(C).

6. WhentheSelect Virtual Tapes to enable Replication...panel appears,usethecheckboxes(D below)and/orselectionbuttonstoselecttapes(E). PressNext(F).

78

VTL User Guide Mar 2008

F 96267

Managing tapes

7. WhentheSpecify the Target server Typepanelappears,clicktheradio buttonforaRemote or Local Server(G below).ThenpressNext(H).

8. WhentheSelect Target Serverpanelappears,usethelist(J below)toselect orserverorpressAdd(K)toaddonetothelist.PressNext(L).

J H

96267 F

Chapter 4 VTL operations

79

Managing tapes

9. IfyouchosetheRemote Serveroptionabove,inStep 7,edittheIPaddressof theremoteVTLserverinthespaceprovided(M below),ifnecessary,thenpress Next(N).

10. IfyouchosetheLocal Serveroptionabove,inStep 7,pressNext(O below).

80

VTL User Guide Mar 2008

F 96267

Managing tapes

11. WhentheSelect the Replication Policy ...panelappears,usethecheck boxes,listboxes,andspinnercontrolsprovidedtodefinethepolicyyouwantto apply(P below).PressNext(R).

12. WhentheSelect the Replication Timeout and Retry Policypanel appears,usethespinnercontrolsprovidedtodefinethepolicyyouwanttoapply (S below).PressNext(T).

96267 F

Chapter 4 VTL operations

81

Managing tapes

13. WhentheSpecify the Options for Data Transmissionpanelappears,use thecheckboxesprovidedtoselecttheoptionsyouwanttouse(U below).Press Next(V). RememberthatcompressionandencryptionareCPUintensivesoftwareprocesses thatreducesystemthroughput.Usethemjudiciously,whennecessary.

14. Whentheconfirmationpanelappears,pressFinish(W below).

Stophere.

82

VTL User Guide Mar 2008

F 96267

Managing tapes

Settingupreplicationforindividualtapes
1. IntheobjecttreeoftheVTLconsole,expandtheVTLservernode,theVirtual Tape Library Systemnode,andtheVirtual Tape Librariesnode. 2. Thenopenthenodeforthelibrarythatholdsthetapeyouwanttoreplicate (A below),andopentheTapesnode(B).

A B C

3. Rightclickonthevirtualtapeforwhichyouwanttoenablereplication(Cabove). 4. Fromthecontextmenus,selectReplication(D above),thenselectAdd (E).

96267 F

Chapter 4 VTL operations

83

Managing tapes

5. WhentheSpecify the Target server Typepanelappears,clicktheradio buttonforaRemote or Local Server(F below).ThenpressNext(G).

6. WhentheSelect Target Serverpanelappears,usethelist(H below)toselect orserverorpressAdd(J)toaddonetothelist.PressNext(K).

J H

84

VTL User Guide Mar 2008

F 96267

Managing tapes

7. IfyouchosetheRemote Serveroptionabove,inStep 7,edittheIPaddressof theremoteVTLserverinthespaceprovided(L below),ifnecessary,thenpress Next(M).

8. IfyouchosetheLocal Serveroptionabove,inStep 7,pressNext(N below).

96267 F

Chapter 4 VTL operations

85

Managing tapes

9. WhentheSelect the Replication Policy ...panelappears,usethecheck boxes,listboxes,andspinnercontrolsprovidedtodefinethepolicyyouwantto apply(N below).PressNext(P).

10. WhentheSelect the Replication Timeout and Retry Policypanel appears,usethespinnercontrolsprovidedtodefinethepolicyyouwanttoapply (Q below).PressNext(R).

86

VTL User Guide Mar 2008

F 96267

Managing tapes

11. WhentheSpecify the Options for Data Transmissionpanelappears,use thecheckboxesprovidedtoselecttheoptionsyouwanttouse(S below).Press Next(T).

RememberthatcompressionandencryptionareCPUintensivesoftwareprocesses thatreducesystemthroughput.Usethemjudiciously,whennecessary. 12. WhentheSelect a Creation Methodpanelappears,clicktheExpressradio button(U below),andpressNext(V).

TheSunStorageTekVTLapplianceincludesanintegratedRAIDdevice,sothereis noadvantagetomanuallyselectingtargetvolumesusingtheCustommethod.The Custommethodmayalsoresultinloadbalancingproblemsandsignificantlygreater managementoverhead.

96267 F

Chapter 4 VTL operations

87

Managing tapes

13. WhentheEnter the Virtual Tape Replica Namepanelappears,entera nameoracceptthedefault(W below),andpressNext(X).

14. Whentheconfirmationpanelappears,pressFinish(Y below).

Note Onceyoucreateyourreplicationconfiguration,youshouldnotchangethe hostnameofthesource(primary)server.Ifyoudo,youwillneedtorecreateyour replicationconfiguration.


Stophere.

88

VTL User Guide Mar 2008

F 96267

Managing tapes

Manuallysynchronizingreplicas(manualreplication)
Youcansynchronizereplicasmanually,whennecessary.Todoso,proceedas follows. 1. Rightclickontheprimaryvirtualtape,andselectReplicationfromthecontext menu. 2. SelectSynchronizefromthefollowingcontextmenu. Stophere.

Suspendingandresumingreplication
Youcanmanuallysuspendforthcomingreplicationsthatwouldotherwisebe launchedautomaticallyfromyourreplicationpolicies(currentlyactivereplications areunaffected).Todoso,proceedasfollows. 1. Rightclickontheprimaryvirtualtape,andselectReplicationandSuspend fromthecontextmenus. 2. Ifdesired,youcansynchronizereplicasmanuallyduringthesuspensionperiod byrightclickingontheprimaryvirtualtape,andselectingReplicationand Synchronizefromthecontextmenus. 3. Tocontinuewithnormalreplication,rightclickontheprimaryvirtualtape,and selectReplicationandResumefromthecontextmenus. Stophere.

Stoppingareplicationthatisalreadyunderway
1. Tostopareplicationthatiscurrentlyinprogress,rightclickontheprimary virtualtape. 2. SelectReplicationfromthecontextmenu. 3. SelectStopfromthefollowingcontextmenu. Stophere.

96267 F

Chapter 4 VTL operations

89

Managing tapes

CheckingreplicationstatusfromtheprimaryVTLserver
1. IntheobjecttreeoftheVTLconsole,drilldowntotheTapesnode,andselectthe primaryvirtualtape(Abelow).

2. Inthepropertiessheetattheright,selecttheReplicationtab(B above). 3. ScandownthesheetuntilyouseetheReplication Statusrow(C above). Stophere.

90

VTL User Guide Mar 2008

F 96267

Managing tapes

CheckingreplicationstatusfromthetargetVTLserver
1. IntheobjecttreeoftheVTLconsole,drilldowntotheReplica Resources node(Abelow).

D A B

2. Selectthereplicaresourcecorrespondingtotheprimaryvirtualtape(B above)) 3. Inthepropertiessheetattheright,selecttheGeneraltab(C above). 4. ScandownthesheetuntilyouseetheReplication Statusrow(D above). Stophere.

Checkingreplicationstatuswithareport
1. UsetheprocedureinCreatingareportonpage 113tocreateaReplicationStatus Report Whileareportcanbegeneratedforasingletape,itismostusefulforassessingthe replicationstatusofmultipletapes.Reportscanbecreatedtofitarangeofcriteria, including:

alltapesthathavereplicationenabled alltapesreplicatedfromasourceserver alltapesreplicatedtoatargetserver alltapesinagivenrangeofdates.

96267 F

Chapter 4 VTL operations

91

Managing tapes

alltapesonagroupofservers

Reportscanbefilteredtoexcludeallbutcurrentreplicationconfigurations,allbut deletedorpromptedconfigurations,oranydesiredcombination. 2. Examinethereportforthestatus(A below)ofthejoborjobsyouareinterestedin.

Stophere.

Changingreplicationproperties
Youcanchangethefollowingforyourreplicationconfiguration:

StaticIPaddressofyourtargetserver Policiesthattriggerreplication(watermark,interval,time) Timeoutandretrypolicies Datatransmissionoptions(encryption,compression)

Tochangeproperties,proceedasfollows: 1. Rightclickontheprimaryvirtualtape,andselectReplicationandProperties fromthecontextmenus. 2. Maketheappropriatechanges,andpressOK. Stophere.

92

VTL User Guide Mar 2008

F 96267

Managing tapes

Deletingareplicationconfiguration
1. Rightclickontheprimaryvirtualtape,andselectReplicationfromthecontext menu. 2. SelectRemovefromthefollowingcontextmenu. Thisallowsyoutoremovethereplicationconfigurationontheprimaryandeither deleteorpromotethereplicaresourceonthetargetserveratthesametime. Stophere.

Promotingareplicaresource
Ifaprimaryvirtualtapeisdamagedorcorrupted,administratorscanrestorethe databypromotingtheequivalentreplica.Afterpromotion,thevirtualtapeis placedinthevirtualvaultontheformertargetserver(nowtheprimary).An administratorcanthen:

movethevirtualtapetoavirtuallibraryonthelocalserver replicatethevirtualtapebacktotheoriginalsourceserver.

Oncepromoted,areplicaresourcecannotreverttobeingareplicaresource.You mustcreateanewreplicationconfigurationforthenewprimarytape. TInordertomaintaintheintegrityofrestoreddata,theVTLsoftwarewillnot promoteaninvalidreplicaresource,suchasareplicathathasbeendamagedorleft incompletebyatransmissionfault.Itwilllikewiserefusetopromoteareplica resourcewhileareplicationisstillinprogress. 1. IntheobjecttreeoftheVTLconsole,expandtheVTLtargetservernode,expand theVirtual Tape Library SystemandReplica Resourcesnodes. 2. UndertheReplica Resourcesnode,rightclickonthereplicathatyouwantto promote(Abelow).

96267 F

Chapter 4 VTL operations

93

Managing tapes

3. Fromthecontextmenus,selectReplication(B below),Promote(C).

4. Whentheconfirmationpanelappears,pressOK(D below).

5. RescandevicesfromtheSANclientorrestarttheclientsothatitcanseethe promotedvirtualtape. Stophere.

Copyingtapes
Youcancopythecontentsofasingletapetoaremoteserver,ondemand,usingthe VTLRemote Copyfeature.TheRemote Copyfeaturereplicatesfulltapes.Itdoes notappenddatatoexistingvirtualtapesoroverwritethecontentsoftapes.
94 VTL User Guide Mar 2008 F 96267

Managing tapes

Youcanonlycopytapeswithbarcodesthatarenotfoundontheremoteserver.Ifa copyexistsandyouwishtoproceed,youmustfirstdeletetheexistingremotecopy copy. YoucannotcopyatapethatisconfiguredtotakeadvantageoftheReplication, Auto Replication,orAuto Archivefeatures. Tocopytapestoaremoteserver,proceedasfollows.

Copyingatapetoaremoteserver
1. IntheobjecttreeoftheVTLconsole,expandtheVTLservernode. 2. UndertheVTLserver,expandtheVirtual Tape Library Systemand Virtual Tape Librariesnodes. 3. UndertheVirtual Tape Librariesnode,rightclickonthevirtualtapelibrary thatyouwanttoenable(Abelow),andexpandtheTapesnode. 4. Rightclickonthevirtualtapethatyouwanttocopy(B below),andselectRemote Copyfromthecontextmenu(D).

A B C D

96267 F

Chapter 4 VTL operations

95

Managing tapes

5. WhentheSelect the Target Serverpanelappears,usethelisttoselectthe serverwhereyouwanttocopythetape(E below)orpressAdd(F)toaddaserver tothelist.ThenpressNext(G).

F E

6. WhentheEnter Replication Parameterspanelappears,edittheIPaddress ifnecessary(H below),thenpressNext(J).

nnn.nnn.nnn.nnn

96

VTL User Guide Mar 2008

F 96267

Managing tapes

7. Whenthe Specify a Locationpanelappears,selectalocationontheremote server(K below),andpressNext(L).

8. Whentheconfirmationpanelappears,pressFinish(M below).

Stophere.

Movingtapesbetweenvirtualandphysical libraries
VTLsoftwarecanimportaphysicaltapeasavirtualtapeorexportvirtualtapeto physicaltape,usinganattachedphysicaltapelibraryortapedrive.Youcanthususe theimportandexportfunctionsto:

96267 F

Chapter 4 VTL operations

97

Managing tapes

copyaphysicaltapetoavirtualtapethatemulatesthesametypeofmedia directlyaccessaphysicaltapewithoutcopyingtheentiretape recycleaphysicaltapeafterimportingitscontentstovirtualmedia movedatafromavirtualtapetoaphysicaltapeofthesamemediatype

VTLimport/exportcapabilitiesareparticularlyusefulwhenyouarenotusingthe AutomatedTapeCachingfeatureandwanttomovetapesfromavirtuallibraryto physicalmediaforlongtermstorage.Shouldyousubsequentlyneedtorecoverfiles, youcanaccessthephysicaltapevolumedirectly,inthephysicallibrary,byusingthe VTLimportfunction.Thisgivesthebackupapplicationimmediateaccesstothetape datawithoutwaitingforacompletecopyabigadvantagewhenyouneedto restoreonlyasmallamountofdata. Youshouldnote,however,thatVTLsoftwaresupportsseveralofwaysofmoving datafromvirtualtophysicalstorage,eachofwhichhasadvantagesinparticular situations.InadditiontoVTLsexportfunction,eachofthefollowingmethods supportsmigrationofdatafromvirtualtophysicalmedia:

copyingvirtualtapetophysicaltapeusingthefunctionalityprovidedbyyour backuporcopy/vaultmanagementapplication automaticallycloningvirtualvolumestophysicalmediaaftereachbackupusing theVTLAutoArchivefunction automaticallycloningvirtualvolumestophysicalmediausingthepolicydriven VTLAutomatedTapeCachingoption.

Youshouldthusconsideryouroptionsbeforedecidingonamethod.Automated TapeCachingandAutoArchivecannotbeusedtogether. Upto32import/exportjobscanrunconcurrently,although,inpractice,thisis generallylimitedtosomethinglessbythenumberofphysicaltapedrivesavailable ontheattachedlibrary. Thissectionholdsinstructionsforthefollowingtasks:


Importingaphysicaltapeintoavirtuallibraryonpage 99 ImportingcartridgesinanIBMiSeriesenvironmentonpage 105 Exportingvirtualtapetophysicaltapeonpage 105 ExportingcartridgestothevirtualvaultinanIBMiSeriesenvironmenton page 109.

98

VTL User Guide Mar 2008

F 96267

Managing tapes

Importingaphysicaltapeintoavirtuallibrary
1. IntheobjecttreeoftheVTLconsole,rightclickthenodeforthephysicaltape libraryordrivethatholdsthetapeyouwishtoimport(A below).SelectImport Tapefromthecontextmen(B).

2. WhentheSelect virtual library ...panelappears,usethelisttoselecta virtuallibrarythatholdsvolumesofthesamecapacityasthevolumeyouwantto import(C below).PressNext(D).

VTLexportstapestolikemediaonly.Youcannotexporttoadissimilarphysical tape.

96267 F

Chapter 4 VTL operations

99

Managing tapes

3. WhentheSelect the import mode ...panelappears,clicktheradiobutton thatcorrespondstothebehavioryouwant(E below).

4. Ifthetapeisencryptedandyouwishtodecryptit,checktheDecrypt data ... checkbox(F above),andenterthecorrectkey. Ifthedatawasnotpreviouslyencrypted,importeddataisunusable.Ifyousupply anincorrectkeyorifyouenteraninvalidpasswordwhenchallenged,theimported dataisnotdecrypted. 5. PressNext(G above).

100

VTL User Guide Mar 2008

F 96267

Managing tapes

6. WhentheSelect the physical tape to import ...panelappears,usethe checkboxesand/orselectionbuttonsprovidedtoselectthetape(s)thatyouwant toimport(H below).ThenpressNext(J).

Youcanselectatapebasedonitsbarcodeorslotlocation.Youcanthenusethesame barcodeforthevirtualtapeoryoucanenteranewbarcode.Youcanalsoselectaslot forthevirtualtape. 7. WhentheSelect Virtual Tape Creation Methodpanelappears,clickthe Expressradiobutton(K below),andpressNext(L).

TheSunStorageTekVTLapplianceincludesanintegratedRAIDsubsystem,sothere isnoadvantagetomanuallyselectingtargetvolumesusingtheCustommethod.The Custommethodmayalsoresultinloadbalancingproblemsandsignificantlygreater managementoverhead.

96267 F

Chapter 4 VTL operations

101

Managing tapes

8. WhentheSelect Physical Devicespanelappears,usethecheckboxesand/or selectionbuttonsprovidedtoselecttheLUNsthatyouwishtouse(M below). PressNext(N).

9. WhentheSpecify Batch Mode Informationpanelappears,enteraVirtual Tape Name Prefixthatmatchestheconventionusedintherestofthevirtual library(P below).

102

VTL User Guide Mar 2008

F 96267

Managing tapes

10. SettheVirtual Tape Sizetothefullsizeoftheemulatedmedia(Q below), andTabtoanotherfieldtorecalculatetheMaximumnumberoftapespossiblewith theavailablestorage(S).MakesurethattheNumber of Virtual Tapesthat youwillcreateinordertoimportyourspecifiednumberofphysicaltapes(R) doesnotexceedtherecalculatedMaximum(S).

R S

11. IftheNumber of Virtual Tapesthatyouwillcreateinordertoimportyour specifiednumberofphysicaltapes(R above)exceedstherecalculatedMaximum (S),stophere.Youcannotimportthenumberoftapesyouspecified.

96267 F

Chapter 4 VTL operations

103

Managing tapes

12. Otherwise,resettheVirtual Tape Sizetothedefaultvalueforusingcapacity ondemandwiththistypeofmedia(T below).ChecktheUse default ID for Starting Numbercheckbox(U),andpressNext(V).

U V

13. Verifytheinformation,andpressFinish(W below)toimportthetape.

Nexttask: IfyouareworkinginanIBMiSeries/AS400environment,gotoImporting cartridgesinanIBMiSeriesenvironmentonpage 105.Otherwise,stophere.

104

VTL User Guide Mar 2008

F 96267

Managing tapes

ImportingcartridgesinanIBMiSeriesenvironment
1. Ifyouhavenotalreadydoneso,importtapesintothevirtuallibraryusingthe VTLconsole,asdescribedinImportingaphysicaltapeintoavirtuallibraryon page 99. 2. AttheAS/400,reinventorythetapelibrary.Intheoptionfieldnexttothetape library,enter9 (INVENTORY). 3. Addtapestotheinventorybyenteringeitherofthefollowingatthecommand line:
ADDTAPCTG DEV(library_device_name ) CTG(cartridge_identifier ) CGY(*NOSHARE) CHKVOL(*NO) ADDTAPCTG DEV(library_device_name ) CTG(cartridge_identifier ) CGY(*SHARE400) CHKVOL(*NO)

ThetapestatuschangesfromINSERTtoAVAILABLE. Stophere.

Exportingvirtualtapetophysicaltape
1. IntheobjecttreeoftheVTLconsole,rightclickonthevirtualtapenodethatyou wanttoexport(A below),andselectMove to Vaultfromthecontextmenu(B).

96267 F

Chapter 4 VTL operations

105

Managing tapes

2. WhentheMove Tape to Virtual Vaultdialogappears,selectthetape(s)that youwanttomoveusingthecheckboxesand/orselectionbuttonsprovided (C below).PressOK(D).

3. Now,intheobjecttreeoftheVTLconsole,opentheVirtual Vaultnode,and rightclickthevirtualtapethatyouwanttoexport(E below).SelectExport Tape fromthecontextmenu(F)

106

VTL User Guide Mar 2008

F 96267

Managing tapes

4. WhentheSelect a physical library or drivepanelappears,usethelist toselectthelibraryordevicetowhichyouwantoexportvirtualtape(G below). PressNext (H).

5. WhentheSelectexportmodepanelappears,selectthedesiredexportbehaviorby clickingeithertheMoveradiobutton(andsettingthegraceperiodusingthe spinnerandlistcontrolsprovided)ortheCopyradiobutton(J below).

K L

6. Ifyouwishtomovethephysicaltapestoanimport/exportslotaftertheexport operationiscomplete,checktheEject physical tapes ...checkbox (K above).

96267 F

Chapter 4 VTL operations

107

Managing tapes

7. Ifyouwishtoencryptthephysicaltape,checktheEncrypt data ...checkbox, andsupplyakeyusingthecontrolprovided(L above). 8. PressNext(M above). 9. WhentheSelect Virtual Tape(s)panelappears,selecteachvirtualtapethat youwanttoexportusingthecheckboxesatleft(N below)orusetheselection buttons(P). 10. Foreachtape,checktheSame Barcodecheckbox(Q below)unlessyoudonot wanttopreservethebarcode. IfyouchecktheSame Barcodecheckbox,theVTLsoftwarewillautomatically exporttoaphysicalcartridgewiththesamebarcodeasthevirtualcartridge. Yourbackupapplicationmaynotbeabletorestoredatafromthephysicalbackup tapeifthebarcodediffersfromthatofthevirtualtape. 11. IfyoudidnotchecktheSame Barcodecheckbox(Q below),usethePhysical Tapespinnercontrol(R)toselectthephysicaltapethatwillholdtheexported data. 12. PressNext(S below).

Q R

P S

108

VTL User Guide Mar 2008

F 96267

Managing tape caching

13. WhentheVerify and Export ...panelappears,pressFinish(T below).

Stophere.

ExportingcartridgestothevirtualvaultinanIBMiSeries

environment
1. Exportacartridgebyenteringthefollowingatthecommandline: RMVTAPCTG DEV(library_device_name ) CTG(cartridge_identifier) 2. Ifdesired,usetheVTLconsoletoverifythatthecartridgeshavebeenremoved fromthevirtuallibraryandplacedinthevirtualvault. Stophere.

Managingtapecaching
Inmostcircumstances,theAutomatedTapeCachingfeaturemaintainstapecaches andlinkagesautomatically,providedthatpoliciesaresuitablydefined.However, whennecessary,youcanmanagecachingmanually.Thissectionexplains:

Forcingmigrationtophysicaltapeonpage 110 Manuallyfreeingcachespaceonpage 110 Renewingcacheforadirectlylinkedtapeonpage 110 Relinkingphysicaltapesonpage 111

96267 F

Chapter 4 VTL operations

109

Managing tape caching

Forcingmigrationtophysicaltape
Tomanuallycausedatainacachetobemigratedtophysicaltape,proceedas follows: 1. IntheobjecttreeoftheVTLconsole,rightclickonavirtualtapecache. 2. SelectMigrate to Physical Tapefromthecontextmenu. Notethatalldataonthephysicaltapeisoverwritten. Stophere.

Manuallyfreeingcachespace
1. Ifyouneedtoreleasespaceinasinglecache,intheobjecttreeoftheVTL console,rightclickonavirtualtapecache,andselectReclaim Disk Space. Notethatalldatainthecacheisoverwritten. 2. Toreleasespaceinmultipletapecaches,intheobjecttreeoftheVTLconsole, rightclickontheVirtual Tape Library Systemnode,andselectReclaim Disk Spacefromthecontextmenu. Stophere.

Renewingcacheforadirectlylinkedtape
VTLsoftwareautomaticallyrecachesadirectlinkphysicaltapeifthelinkis overwrittenbyabackupapplication.Tomanuallyrenewthecacheforadirectlink tape,proceedasfollows: 1. IntheobjecttreeoftheVTLconsole,rightclickonthedirectlinktapethatyou wishtorecache. 2. SelectRenew Cachefromthecontextmenu. Stophere.

Disablingapolicy
Todisableatapecachingpolicy: 1. IntheobjecttreeoftheVTLconsole,rightclickonavirtualtapelibrary,and selectAutomated Tape Cachingfromthecontextmenu.

110

VTL User Guide Mar 2008

F 96267

Managing tape caching

2. CleartheEnable Tape Caching Policycheckbox. Alltheoptionsthatyoupreviouslysetareretained,butdatamigrationwillnot occurautomaticallyuntilyouselectthischeckboxagain. 3. ClickOK. Stophere.

Relinkingphysicaltapes
Ifadirectlylinkedphysicaltapeisejectedfromthephysicaltapelibraryafterthe virtualtapehasbeenreleasedfromcache,youhavetorelinkthephysicaltapebefore youcanaccessitfromtheVTLconsole.

Note Oncethephysicaltapeisreloadedinalibrary,thebackupapplicationcan inventoryaccessthelibraryandaccessthetapedirectly,ifnecessary.


1. IntheobjecttreeoftheVTLconsole,rightclickonthevirtualtapelibrary,and selectSync Libraryfromthecontextmenu. 2. Ifyouhavemultiplelibraries,selecttheappropriatephysicallibrary. 3. WhentheSync Librarydialogappears,checkthecheckboxthatcorrespondsto thephysicaltapethatneedstoberelinked(A below)orusetheSelect-All button.

4. PressNext(B above).

96267 F

Chapter 4 VTL operations

111

Creating and viewing reports

5. Whentheselectthemodepanelappears,clicktheCreate Direct Linkradio button(C below).

6. Ifthedatawasencryptedbeforebeingmigrated,checktheUse encryption/decryption on tape(s)checkbox,andsupplytheselectthe appropriatekeyusingthelistcontrolprovided(D above). 7. PressNext(E above),then Finish. Stophere.

Creatingandviewingreports
YoucanworkwithreportsusingtheVTLconsole.See:

Creatingareportonpage 113 Viewingareportonpage 115 Exportingdatafromareportonpage 116.

112

VTL User Guide Mar 2008

F 96267

Creating and viewing reports

Creatingareport
1. IntheobjecttreeoftheVTLconsole,rightclickontheReportsnode(A below), andselectNewfromthecontextmenu(B).

A B

2. WhentheSelect a Report Typedialogappears,selectatypefromthelist (C below).PressNext(D).

96267 F

Chapter 4 VTL operations

113

Creating and viewing reports

3. WhentheSelect Report Optionspanelappears,selectthedesiredreport propertiesusingthecontrolsprovided(Eand Fbelow).PressNext(G).

Notethatdifferentreporttypesofferdifferentoptions. Intheexampleabove,theInclude All SAN Resources and Clientsoption coversallcurrentandpreviousconfigurationsfortheserver(includingphysicaltape libraries/drivesandclientsthatyoumayhavechangedordeleted).TheInclude Current Active SAN Resources and Clients Onlyoptioncoversonlythe physicaltapelibraries/drivesandclientsthatarecurrentlyconfiguredforthisserver. 4. WhentheEnter the Report Namedialogappears,forthereport,enterthe nameinthefieldprovided(H below),andpressNext(J).

114

VTL User Guide Mar 2008

F 96267

Creating and viewing reports

5. WhentheCreate the Reportpanelappears,pressFinish(K below).

Stophere.

Viewingareport
1. IntheobjecttreeoftheVTLconsole,expandtheReportsnode(Abelow)toview thelistofcurrentreports.

A B

2. Selectthecurrentreportthatyouwishtoview(B above). Thedesiredreportappearsintherighthandpaneoftheconsole(C above). Stophere.


96267 F Chapter 4 VTL operations 115

Encrypting and shredding data

Exportingdatafromareport
1. IntheobjecttreeoftheVTLconsole,expandtheReportsnodeandrightclick thenameofthereportthatyouwanttoexport(A below). Youcanexportserveranddevicethroughputandusagereportdatatocommaor tabdelimitedtextfiles.

B D A C

2. Inthecontextmenu.,selectExport(B above). 3. WhentheSavedialogappears,usetheFiles of typelistcontroltoselectthe desiredformat(C above),andpressSave(D). Stophere.

Encryptingandshreddingdata
Toensurethatthedatathatyouexporttophysicaltapeisconfidentialandsecure, VTLoffersaSecureTapeOptionthatusestheAdvancedEncryptionStandard(AES) algorithmpublishedbytheNationalInstituteofStandardsandTechnology,an agencyoftheU.S.government.Withthisoption,youcancreateoneormorekeys thatcanbeusedtoencryptthedatawhenitisexportedtophysicaltapeanddecrypt itwhenitisimportedbacktovirtualtapes.Thedataonthetapecannotberead withoutbeingdecryptedusingtheappropriatekey.

116

VTL User Guide Mar 2008

F 96267

Encrypting and shredding data

Eachkeyconsistsofasecretphrase.Foradditionalsecurity,eachkeyispassword protected.Youmustprovidethispasswordinordertochangethekeyname, password,orpasswordhint,ortodeleteorexportthekey. Youcanapplyasinglekeytoallvirtualtapeswhenyouexportthemtophysical tape,oryoucancreateauniquekeyforeachone.Creatingmultiplekeysprovides moresecurity;intheunlikelyeventthatakeyiscompromised,onlythetapesthat usethatkeywouldbeaffected.However,ifyouusemultiplekeys,youmustkeep trackofwhichkeyappliestoeachtapesothatyouusethecorrectkeytodecryptthe datawhenyouimportthephysicaltapebacktovirtualtape. Note:Ifyouapplyanincorrectkeywhenimportingatape,thedataimportedfrom thattapewillbeindecipherable. Onceyouhavecreatedoneormorekeys,youcanexportthemtoaseparatefile calledakeypackage.IfyousendencryptedtapestootherlocationsthatrunVTL, youcanalsosendthemthekeypackage.Byimportingthekeypackage, administratorsattheothersitescanthendecryptthetapeswhentheyareimported backintovirtualtapelibrariesmanagedbyVTL. Youcanenableencryptionandspecifywhichkeytousewhenyoueithermanually importorexportatapeorwhenyouusetheautoarchive/replicationfeature. Forinstructions,seethefollowing:

Creatingakeyonpage 117 Changingakeynameorpasswordonpage 118 Deletingakeyonpage 119 Exportingakeyonpage 120 Importingakeyonpage 121 Shreddingavirtualtapeonpage 122.

Creatingakey
1. Inthenavigationtree,rightclicktheservernameandclickKey Management. 2. ClickNew. 3. IntheKey Name textbox(A below),typeauniquenameforthekey(132 characters). 4. IntheSecret Phrase textbox(B below),typethephrase(2532characters, includingnumbersandspaces)thatwillbeusedtoencryptthedata. Saveyoursecretphrase.Onceyouhavecreatedakey,youcannotchangethesecret phraseassociatedwiththatkey.

96267 F

Chapter 4 VTL operations

117

Encrypting and shredding data

5. IntheNew Password andConfirm Passwordtextboxes(C below),typea passwordforaccessingthekey(1016characters). Youwillneedtoprovidethispasswordwhenchangingthekeyname,password,or passwordhintandwhendeletingorexportingthekey. Youdonothavetoprovideauniquepasswordforeachkey.Infact,ifyouusethe samepasswordformultiplekeys,youhavetoprovidethepasswordonlyoncewhen youexportmultiplekeysthatallusethesamepassword. 6. InthePassword Hinttextbox(D below),typeahint(032characters)thatwill helpyourememberthepassword. Thishintappearswhenyoutypeanincorrectpasswordandrequestahint.

A B

C D

7. ClickOK(E above). Stophere.

Changingakeynameorpassword
Onceyouhavecreatedakey,youcannotchangethesecretphraseassociatedwith thatkey.However,youcanchangethenameofthekey,aswellasthepasswordused toaccessthekeyandthehintassociatedwiththatpassword.

118

VTL User Guide Mar 2008

F 96267

Encrypting and shredding data

Ifyourenameakey,youcanstillusethatkeytodecryptdatathatwasencrypted usingtheoldkeyname.Forexample,ifyouencryptdatausingKey1,andyou changeitsnametoKey2,youcandecryptthedatausingKey2,sincethesecret phraseisthesame. Tochangeakeynameorpassword: 1. Inthenavigationtree,rightclicktheservername,andclickKey Management. 2. FromtheKey Namelist,clickthekeyyouwanttochange. 3. ClickEdit. 4. IfyouclosedtheKey Managementdialogboxaftercreatingthekey,typethe currentpasswordforaccessingthiskeyinthePasswordtextbox. Ifyoujustcreatedthekey,didnotclosetheKey Managementdialogbox,and subsequentlydecidedtochangethekey,youarenotpromptedforthepassword. 5. Makethedesiredchanges: 6. ClickOK. Stophere.

Deletingakey
Caution:Onceyoudeleteakey,youcannolongerdecrypttapesthatwere encryptedusingthatkeyunlessyousubsequentlycreateanewkeythatusesthe exactsamesecretphrase,orimportthekeyfromakeypackage. 1. Inthenavigationtree,rightclicktheservernameandclickKey Management. 2. FromtheKey Namelist,clickthekeythatyouwanttodelete. 3. ClickDelete. 4. InthePasswordtextbox,typethepasswordforaccessingthiskey. 5. TypeYEStoconfirm. 6. ClickOK. Stophere.

96267 F

Chapter 4 VTL operations

119

Encrypting and shredding data

Exportingakey
Whenyouexportakey,youcreateaseparatefilecalledakey package that containsoneormorekeys.YoucanthensendthisfiletoanothersitethatusesVTL, andadministratorsatthatsitecanimportthekeypackageandusetheassociated keystoencryptordecryptdata. Creatingakeypackagealsoprovidesyouwithabackupsetofkeys.Ifaparticular keyisaccidentallydeleted,youcanimportitfromthekeypackagesothatyoucan continuetoaccessthedataencryptedusingthatkey. 1. Inthenavigationtree,rightclicktheservernameandclickKey Management. 2. ClickExport. 3. InthePackage Nametextbox,typethefilenametouseforthiskeypackage (132characters). 4. IntheDecryption Hinttextbox,typeathreecharacterhint. Whenyousubsequentlyattempttoimportakeyfromthiskeypackage,youare promptedforapassword.Ifyouprovidethecorrectpassword,thedecryptionhint specifiedhereappearscorrectlyontheImport Keysdialogbox.Ifyouprovidean incorrectpassword,adifferentdecryptionhintappears.Youcanimportkeysusing anincorrectpassword,butyouwillnotbeabletodecryptanyfilesusingthosekeys. 5. FromtheSelect Keys to Export list,selectthekey(s)thatyouwantto includeinthekeypackage. WhenyouselectakeyorclickSelect All,youarepromptedtoprovidethe passwordforeachkey.(Ifmultipleselectedkeysusethesamepassword,youare promptedforthepasswordonlyonce,whenyouselectthefirstkeythatusesthat password.) AfteryoutypethepasswordinthePasswordtextbox,thatpasswordappearsinthe Password for All Keys in Package areaontheExport Keysdialogbox. Bydefault,thepasswordisdisplayedasasterisks.Todisplaytheactualpassword, selecttheShow clear textcheckbox. Ifyouselectedakeyandsubsequentlydecidenottoincludeitinthekeypackage, youcanclearthekey.YoucanalsoclearallselectedkeysbyclickingDe-Select All.

120

VTL User Guide Mar 2008

F 96267

Encrypting and shredding data

6. SelectPrompt for new password for all keys in packageifyouwant tocreateanewpasswordforthekeypackage. Ifyouselectthisoption,youwillbepromptedtoprovidethenewpasswordwhen youclickOKontheExport Keysdialogbox.Youwillsubsequentlybeprompted forthispasswordwhenyoutrytoimportakeyfromthispackage.Inaddition,all keysimportedfromthispackagewillusethisnewpasswordratherthanthe passwordoriginallyassociatedwitheachkey. Ifyouclearthisoption,thispackagewillusethesamepasswordasthefirstselected key(whichappearsinthePassword for All Keys in Package area),andyou mustprovidethispasswordwhenyoutrytoimportakeyfromthispackage.You mustalsoprovidethispasswordwhenyousubsequentlychange,delete,orexport anykeyimportedfromthispackage. 7. IntheSave in this directory textbox,typethefullpathforthefile. 8. ClickOK. IfyouselectedthePrompt for new password for all keys in package checkbox,typethenewpassword(1016characters)intheNew Passwordand Confirm Passwordtextboxes,typeahintforthatpassword(032characters)in thePassword Hinttextbox. Afilewiththespecifiedpackagenameandtheextension.keyiscreatedinthe specifiedlocation. Stophere.

Importingakey
Onceyouhavecreatedakeypackage,youcanopenthatpackageandspecifywhich keystoimportintoVTL.Onceyouimportakey,youcanusethatkeytoencryptor decryptdata. Toimportakey: 1. Inthenavigationtree,rightclicktheservernameandclickKey Management. 2. ClickImport. 3. IntheFind Packagetextbox,typethefullpathtothekeypackage. 4. ClickView. 5. TypethepasswordforaccessingthekeypackageinthePasswordtextbox. Note:Afteryouprovidethepassword,makesurethatthedisplayedDecryption Hintmatchesthedecryptionhintspecifiedwhenthekeypackagewascreated.Ifthe hintisnotcorrect,clickPasswordandprovidethecorrectpasswordforaccessing

96267 F

Chapter 4 VTL operations

121

Encrypting and shredding data

thekeypackage.Ifyouprovideanincorrectpassword,youwillstillbeableto importthekeysinthepackage,butyouwillnotbeabletousethemtodecryptany datathatwaspreviouslyencryptedusingthosekeys. 6. FromtheSelect Keys to Import list,selectthekeysthatyouwanttoimport. YoucanselectonlythosekeysthathaveagreendotandthephraseReady for ImportintheStatuscolumn.AreddotandthephraseDuplicate Key Name indicatesthatakeyofthesamenamealreadyexistsinthisinstanceofVTLand cannotbeimported. Ifyouselectedakeyandsubsequentlydecidenottoimportit,youcanclearthekey. YoucanalsoclearallselectedkeysbyclickingDe-Select All.(Youcanclickthis buttononlyiftheShow All Keyscheckboxiscleared.) Note:Akeyofthesamenamemightnotnecessarilyhavethesamesecretphrase. Forexample,youmighthaveakeynamedKey1withasecretphraseof ThisIsTheSecretPhraseForKey1.Ifthekeypackagewascreatedbyanotherinstance ofVTL,itmightalsohaveakeynamedKey1,butitssecretphrasemightbe ThisIsADifferentSecretPhrase.Sincethekeynamesarethesame,youwillnotbeable toimportthekeyinthekeypackageunlessyourenametheexistingKey1.Afteryou renamethekey,youcancontinuetouseittodecrypttapesthatwereencrypted usingthatkey,andyoucanalsoimportthekeynamedKey1fromthekeypackage anduseittodecrypttapesthatwereencryptedusingthatkey. 7. ClickOK. TheimportedkeysappearintheKey NamelistontheKey Managementdialog box.Whenyousubsequentlyexportorimportatape,thesekeynamesalsoappearin theSelect a Keylist. Stophere.

Shreddingavirtualtape
Justasdeletingafilefromyourharddrivedoesnotcompletelydestroythefile, deletingavirtualtapedoesnotcompletelydestroythedataonthetape.Ifyouwant toensurethatthedataisunrecoverable,youmustshredthetape. Shreddingavirtualtapedestroysalldataonthetape,makingitimpossibleto recoverthedata.Tapeshreddingusesamilitarystandardtodestroydataonvirtual tapesbyoverwritingitwitharandompatternsofbits,renderingthedata unreadable. Toshredtapes:

122

VTL User Guide Mar 2008

F 96267

Encrypting and shredding data

1. Movethetape(s)youwanttoshredtothevirtualvault.Intheobjecttreeofthe VTLconsole,startbyrightclickingonatapethatyouwanttoshred(A below), andselectMove to Vault(B)fromthecontextmenu.

C B D E

2. Whenthe Move tape to Virtual Vault dialogappears,usethecheckboxes (C above)andselectionbuttons(D)toselectthetapesyouwanttoshred.Press OK (E). 3. Selectthetape(s)youwanttoshred.IntheobjecttreeoftheVTLconsole,clickon theVirtual Vault(F below).

F G

96267 F

Chapter 4 VTL operations

123

Working with the Event Log

4. Rightclickononeofthetapesthatyouwanttoshred(G above),andselect Tape Shredding(H)andShred Tape(J)fromthecontextmenus.

K L M

5. Whenthe Shred Virtual Tape Resource dialogappears,checkthe Delete After Shredding checkbox(K above)ifyouwishtodeletethetape aftershredding. 6. Inthespaceprovided,type YES (L above)toconfirmtheshreddingoperation, andpress OK (M). Youcanviewthestatusbyhighlightingthevirtualtapeinthevault.Thestatusbar displaystheprogress. Ifyouwanttocanceltheshreddingprocess,rightclickonthetapeortheVirtual VaultobjectandselectTape Shredding>Cancel.

Note Tapeshreddingmayadverselyaffectbackupperformance.Werecommend thatyouperformtapeshreddingwhentherearenobackupsrunning.


Stophere.

WorkingwiththeEventLog
TheEventLogdetailssignificantoccurrencesduringtheoperationoftheVTL Server.TheEventLogcanbeviewedintheVTLConsolewhenyouhighlighta serverinthetreeandselecttheEvent Logtabintherightpane.

124

VTL User Guide Mar 2008

F 96267

Working with the Event Log

Thecolumnsdisplayedare:
Type I:Thisisaninformationalmessage.Noactionisrequired. W:Thisisawarningmessagethatstatesthatsomethingoccurredthat mayrequiremaintenanceorcorrectiveaction.However,theVTL systemisstilloperational. E:Thisisanerrorthatindicatesafailurehasoccurredsuchthata deviceisnotavailable,anoperationhasfailed,oralicensingviolation. Correctiveactionshouldbetakentoresolvethecauseoftheerror. C:Thesearecriticalerrorsthatstopthesystemfromoperatingproperly. Thedateonwhichtheeventoccurred. Thetimeatwhichtheeventoccurred. Thisisthemessagenumber. Thisisatextdescriptionoftheeventdescribingwhathasoccurred.

Date Time ID Event Message

TheVTLconsoleletsyouworkwithlogsinthefollowingways:

Viewinganeventlogonpage 125 Sortinganeventlogonpage 125 Quicklyprintinganeventlogonpage 126 Filtering,exporting,purging,andprintinganeventlogonpage 126

Viewinganeventlog
1. IntheobjecttreeoftheVTLconsole,selecttheserverthatyouwanttocheck. 2. InthepanelontherightsideoftheVTLconsole,clickontheEvent Logtab. Stophere.

Sortinganeventlog
1. OntheEvent Logtab,clickonthecolumnheadthatyouwanttouseasasort key. 2. Ifyouwanttoreversethesortorder,clickonthecolumnheadingagain. Stophere.

96267 F

Chapter 4 VTL operations

125

Working with the Event Log

Quicklyprintinganeventlog
1. FromtheVTLconsolemainmenu,select File. 2. Fromthesubmenu,select Print. Stophere.

Filtering,exporting,purging,andprintinganeventlog
1. Withthe Event Log tab(A below)oftheserveropen,rightclickontheserver iconinobjecttreeoftheVTLconsole(B).

A B

C D

2. Fromthecontextmenu,select Event Log (C above).

126

VTL User Guide Mar 2008

F 96267

Working with the Event Log

3. Fromthesubmenu,selecttheoperationthatyouwishtoperform(Dabove). Ifyouwishtosearchorfilterthelog,the Event Log Options dialog(E below) letsyousetupandapplyyourcriteria.

Stophere.

UsingtheAttentionRequiredtab
Wheneventsthatmayrequireuserinterventionoccur,theVTLconsoleflagsthe servericonwithanexclamationpoint(!)anddisplaysnotificationsinthe Attention Requiredtaboftheserverpropertiessheet.Typicaleventsinclude physicallibraryfailures,appliancehardwareerrors,replicationerrors,and completedimport/exportjobs.TheVTLconsoleletsyoumanageAttentionRequired notificationsnotificationsinthefollowingways:

AccessingtheAttentionRequiredtabonpage 128 ClearingissuesfromtheAttentionRequiredlistonpage 128.

96267 F

Chapter 4 VTL operations

127

Working with the Event Log

AccessingtheAttentionRequiredtab
1. IntheVTLobjecttree,locatetheflaggedserver(A below).

B A

C D

2. Intherighthandpane,selecttheAttention Requiredtaboftheserver propertysheet(B above). Stophere.

ClearingissuesfromtheAttentionRequiredlist
1. Ifyouwanttoclearanentireclassofeventsfromthelist,checkthecheckboxfor theeventtype(C above). 2. Ifyouwanttoclearanindividualevent,checkthecorrespondingcheckbox (D above) 3. ClicktheClearbutton(E above). Stophere.

128

VTL User Guide Mar 2008

F 96267

Managing VTL servers

ManagingVTLservers
TheVTLconsoleletsyoumanagetheservernodeby:

Settingserverpropertiesonpage 129 ConfiguringSNMPtrapsonpage 129.

Settingserverproperties
1. RightclickontheserverandselectProperties. 2. OntheActivity Database Maintenancetab,indicatehowoftentheVTL activitydatashouldbepurged. TheActivityLogisadatabasethattracksallsystemactivity,includingalldataread, datawritten,numberofreadcommands,writecommands,numberoferrorsetc. ThisinformationisusedtogenerateinformationfortheVTLreports. 3. OntheSNMP Maintenancetab,VTLtosendtrapstoyourSNMPmanager. RefertoConfiguringSNMPtrapsonpage 129formoreinformation. 4. OntheAuto Savetab,enterinformationtoreplicateyourVTLconfigurationto anotherserver. ThisprotectsyourconfigurationiftheVTLserverislost.RefertoAutomatically backinguptheVTLconfigurationonpage 68formoreinformation. 5. OntheStorage Monitoringtab,enterthemaximumamountofstoragethatcan beusedbyVTLbeforeyoushouldbealerted. Whentheutilizationpercentageisreached,awarningmessagewillbesenttothe EventLog. Stophere.

ConfiguringSNMPtraps
VTLprovidesSimpleNetworkManagementProtocol(SNMP)supporttointegrate VTLmanagementintoanexistingenterprisemanagementsolution,suchasHP OpenView,CAUnicenter,IBMTivoliNetView,orBMCPatrol. Bydefault,eventlogmessageswillnotbesent,butyoumaywanttoconfigureVTL tosendcertaintypesofmessages.Todothis: 1. IntheConsole,rightclickonyourVTLserverapplianceandselectProperties.

96267 F

Chapter 4 VTL operations

129

Managing VTL servers

2. SelecttheSNMP Maintenancetab. 3. IndicatetheinformationthatshouldbeincludedintrapssenttoyourSNMP manager. SysLocationEnterthelocationthatshouldbeincludedintraps. SysContactEnteranycontactinformationthatshouldbeincludedintraps.This couldbeanameoranemailaddress. 4. Specifythetypeofmessagethatshouldbesent. Fivelevelsofmessagesareavailable:


None:nomessageswillbesent. Critical:onlycriticalerrorsthatstopthesystemfromoperatingproperlywill besent. Error:errors(failuresuchasaresourceisnotavailableoranoperationhas failed)andcriticalerrorswillbesent. Warning:warnings(somethingoccurredthatmayrequiremaintenanceor correctiveaction),errors,andcriticalerrorswillbesent. Information:informationalmessages,errors,warnings,andcriticalerror messageswillbesent.

5. ClickAddtoenterthenameofyourSNMPserverandavalidSNMPcommunity name. 6. ToverifythatSNMPtrapsaresetupproperly,settheleveltoInformational andthendoanythingthatcausesanentrytobeaddedtotheeventlog(suchas loggingintotheVTLconsoleorcreatinganewvirtualtapelibraryorvirtualtape drive). YoushouldseeanSNMPtrapfortheevent. Stophere.

130

VTL User Guide Mar 2008

F 96267

CHAPTER

InstallingtheVTLconsole
TheVirtualTapeLibraryconsoleapplicationcanbeinstalledonafullrangeof operatingplatforms.Inmostcases,aSunservicerepresentativeinstallstheconsole ononecustomerprovidedserveraspartoftheinitialdeployment.Customerscan installasmanyadditionalinstancesasrequiredonothermachines.Note,however, thatnomorethantwo(2)instancesoftheconsolecanaccessthesameVTLserverat thesametime. Toinstalltheconsole,followtheinstructionsfortheselectedhosttype:

Forinformationonthetextbased,VTLcommandlineuserinterface,see Appendix A,VTLcommandlinereferenceonpage 149.onpage 131 InstallingtheconsoleonLinuxplatformsonpage 132 InstallingtheconsoleonMicrosoftWindowsplatformsonpage 132.

Note Forinformationonthetextbased,VTLcommandlineuserinterface,see Appendix A,VTLcommandlinereferenceonpage 149.

InstallingtheconsoleonSolarisplatforms
OnSolarissystems,youinstalltheconsoleusingtheprocedurebelow. 1. Logintothehostastheroot user. 2. UsingSecureFileTransferProtocol(sftp),downloadtheinstallationfilestothe client. Forx86platforms,selectthe i386 package:
% sftp vtladmin@appliance_IP-address sftp> get /software/Solaris/vtlconsole-n.nn-n.nnn.i386.pkg

ForSPARCplatforms,selectthe sparc package:


% sftp vtladmin@appliance_IP-address sftp> get /software/Solaris/vtlconsole-n.nn-n.nnn.sparc.pkg

96267 F

131

3. Ifyouareinstallingtheconsolesoftwareonanx86platform,enterthefollowing command,andrespondtotheonscreenprompts:
% pkgadd -d vtlconsole-n.nn-n.nnn.i386.pkg

4. IfyouareinstallingtheconsolesoftwareonaSPARCplatform,enterthe followingcommand,andrespondtotheonscreenprompts:
% pkgadd -d vtlconsole-n.nn-n.nnn.sparc.pkg

5. Tolaunchtheconsole,enterthefollowingcommand:
% /usr/local/vtlconsole/vtlconsole &

Stophere.

InstallingtheconsoleonLinuxplatforms
OnLinuxsystems,youinstalltheconsolemanually,usingtheprocedurebelow. 1. Toinstalltheconsolesoftware,logintothehostastherootuser. 2. UsingSecureFileTransferProtocol(sftp),downloadtheinstallationfilestothe client:
% sftp vtladmin@appliance_IP-address sftp> get /software/Linux/vtlconsole-n.nn-n.nnn.i386.rpm

3. Toinstalltheconsolesoftware,enterthefollowingcommand,andrespondtothe onscreenprompts:
% rpm -i vtlconsole-n.nn-n.nnn.i386.rpm

Theconsolewillinstallinthe/user/local/vtlconsoledirectory. 4. Tolaunchtheconsole,enterthefollowingcommand:
% /usr/local/vtlconsole/vtlconsole &

Stophere.

InstallingtheconsoleonMicrosoftWindowsplatforms
TheVTLinstallationdirectoryontheserverincludesasetupprogramthatinstalls theconsolesoftwareonWindowscomputers. 1. IfyouarenotamemberofthePower User orAdministratorgroupsonthe host,obtaintherequiredlevelofpermissionsorstophere. YoumustbeaPower User orAdministratortoinstallsoftwareonaWindows host.

132

VTL User Guide Mar 2008

F 96267

2. UsingSecureFileTransferProtocol(sftp),logontotheVTLserver,changetothe usr/vtl/packages/build/Windows/ directory,anddownloadalllisted installationfilestoatemporarydirectoryontheclient:


% sftp vtladmin@appliance_IP-address sftp> cd /software/Windows/ sftp> ls data1.cab ikernel.ex_ layout.bin data1.hdr ISInstall.exe setup.bmp data2.cab ISInstall.ini Setup.exe sftp> get *.*

Setup.ini setup.inx

sftp softwareisnotstandardwithmostversionsofMicrosoftWindows,but various,compatible,thirdpartysftpimplementationsareavailable,notablythe onethatcomeswiththepuTTYopensourceterminalemulationapplication. 3. UsingExplorer,changetothetemporarydirectory,anddoubleclickon setup.exetolaunchtheconsoleinstallationprogram. Stophere.

LaunchingtheVTLconsoleonaremotehost
1. TolaunchtheconsoleonaSunSolarisworkstation,openaterminalwindowand enterthecommandshownbelow:
% /usr/local/vtlconsole/vtlconsole &

2. OnaMicrosoftWindowssystem,presstheStartbartoaccessthemainmenu system,andselectAll Programs > Sun Microsystems> VTL 5.0> VTL Console. 3. TolaunchtheconsoleonaLinuxworkstation,openaterminalwindowandenter thecommandshownbelow:
% /usr/local/vtlconsole/vtlconsole &

Stophere.

96267 F

Chapter 5 Installing the VTL console

133

134

VTL User Guide Mar 2008

F 96267

CHAPTER

Recoveryfollowingasystemfailure
TorecoveraVTLhighavailabilitysystemfollowingafailureononenode,carryout thefollowingtasks:

Failbackonpage 135 Resumingbackupsfollowingafailover/failbackonpage 146.

Failback
Forbestresults,runfailbackasamanualprocess,usingtheprocedureoutlined below.

Initiatingfailback
Forthepurposesofthisdescription,thecurrent,activenodeisVTLPLUSN2,the failovernodeforVTLPLUSN1,thefailed/offlinenode. 1. Openaterminalwindowonthemanagementhost,andsshtotheIPaddressof thecurrentlyactivenode,VTLPLUSN2:
[VTL_Plus]vtladmin# ssh vtladmin@nnn.nnn.nnn.nny Connecting to nnn.nnn.nnn.nny ... Password:

wherennn.nnn.nnn.nnyisthemanagementorserverIPaddressofVTLPLUSN2, thenodethattookoverforthefailedservernode,VTLPLUSN1and vtladmin is theVTLadministratoraccountuserID.

96267 F

135

Failback

2. Makesurethatyouareloggedintotheactual,activenode:
[VTL_Plus]vtladmin# uname -a SunOS VTLPLUSN2 n.nn Generic_nnnnnn-nn i86pc i386 i86pc

Thesystemshoulddisplaytheexpectednodename. 3. Ifyouarenotloggedintothecorrectsystem,youmayhaveaccidentlyloggedinto theservice(monitoring)IPaddressofthefailednode.Closethe ssh session, and ssh totheotherIPaddressforthecurrent,activenode. 4. ChangetothedirectorythatholdstheVTLexecutables:


[VTL_Plus]vtladmin# cd /usr/local/vtl/bin

5. Runthevtl status command:


[VTL_Plus]vtladmin# vtl status Sun Microsystems VTL Server vn.nn (Build nnnn) Copyright 2001-2007 by FalconStor. All Rights Reserve Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status of of of of of of of of of of of of of of of of of VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL SNMPD Module................ QLogic Module............... Authentication Module....... Server (Compression) Module. Server (FSNBase) Module..... Server (Upcall) Module...... Server (Event) Module....... Server (Path Manager) Module Server (Application)........ FC Target Module............ Server VTL Upcall Module.... Server VTL Upcall Daemon.... Server VTL Module........... Communication Module........ Logger Module............... Self Monitor Module......... Failover Module............. [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING]

6. IfoneormoreVTLprocessesarenotRUNNING,stoptheserversoftwareandthen restart:
[VTL_Plus]vtladmin# vtl stop all ... [VTL_Plus]vtladmin# vtl start

136

VTL User Guide Mar 2008

F 96267

Failback

7. Runthesmscommand.Theresultsshouldlooklikethoseshown.
[VTL_Plus]vtladmin# sms Usage: sms {force|nas|nasc|fm|sm|bmr|bmrreset|setroot (sm/fm)|clearreboot(sm/fm) } {value} bmr - to set the BMR health status bmrreset - to reset BMR value nas - to reset the NAS failure status nasc - to set nas health check force - enable force up fm - to set ipstorfm debug level sm - to set ipstorsm debug level Last Update by SM: Sun Jan 28 15:32:39 2007 Last Access by RPC: Sun Jan 28 15:32:35 2007 FailOverStatus: 3(UP) Status of IPStor Server (Transport) : OK Status of IPStor Server (Application) : OK Status of IPStor Authentication Module : OK Status of IPStor Logger Module : OK Status of IPStor Communication Module : OK Status of IPStor Self-Monitor Module : OK Status of IPStor NAS Modules: OK(0) Status of IPStor Fsnupd Module: OK Status of IPStor ISCSI Module: OK Status of IPStor BMR Module: OK( 0) Status of FC Link Down : OK Status of Network Connection: OK Status of force up: 0 Broadcast Arp : NO Number of reported failed devices : 0 NAS health check : NO XML Files Modified : NO IPStor Failover Debug Level : 0 IPStor Self-Monitor Debug Level : 0 Do We Need To Reboot Machine(SM): NO Do We Need To Reboot Machine(FM): NO Nas Started: NO

8. Openaterminalwindowonthemanagementhost,and ssh totheservice (monitoring)IPaddressofthefailednode,VTLPLUSN1:


[mgt_host]user# ssh vtladmin@nnn.nnn.nnn.nnw Connecting to nnn.nnn.nnn.nnw ... Password:

96267 F

Chapter 6 Recovery following a system failure

137

Failback

wherennn.nnn.nnn.nnwistheserviceIPaddressofthefailednode,andvtladmin istheVTLadministratoraccountuserID.Weusetheservice/monitoringaddress becauseitstayswiththehostfollowingfailover(themanagementIPaddressofa failednodetransferstotheremainingactivenodeduringfailover). 9. Makesurethatyouareloggedintotheactual,failednode:


[VTL_Plus]vtladmin# uname -a SunOS VTLPLUSN1 n.nn Generic_nnnnnn-nn i86pc i386 i86pc

Thesystemshoulddisplaytheexpectednodename. 10. Ifyouarenotloggedintothecorrectsystem,youhaveaccidentlyloggedintothe managementIPaddress(whichalwaysconnectstotheactivenode)ratherthanthe service(monitoring)address.Closethe ssh session,and ssh totheotherIP addressforthefailednode. 11. ChangetothedirectorythatholdstheVTLexecutables:
[VTL_Plus]vtladmin# cd /usr/local/vtl/bin

12. Beforeproceedingfurther,makesurethatnoI/Oisbeingsenttothefailednode. Makesurethatallbackupjobshavecompletedandthatfailoverhascompleted successfully.StopI/O,ifnecessary. IfhostI/Oisnotstopped,datamaybelost.

138

VTL User Guide Mar 2008

F 96267

Failback

13. Runthesmscommand,andmakesurethattheFailOverStatusisDOWN (failed overtothestandbyserver):


[VTL_Plus]vtladmin# sms Usage: sms {force|nas|nasc|fm|sm|bmr|bmrreset|setroot (sm/fm)|clearreboot(sm/fm) } {value} bmr - to set the BMR health status bmrreset - to reset BMR value nas - to reset the NAS failure status nasc - to set nas health check force - enable force up fm - to set ipstorfm debug level sm - to set ipstorsm debug level Last Update by SM: Sun Jan 28 15:32:39 2007 Last Access by RPC: Sun Jan 28 15:32:35 2007
FailOverStatus: 3(DOWN)

Status of IPStor Server (Transport) : OK Status of IPStor Server (Application) : OK Status of IPStor Authentication Module : OK Status of IPStor Logger Module : OK Status of IPStor Communication Module : OK Status of IPStor Self-Monitor Module : FAIL Status of IPStor NAS Modules: OK(0) Status of IPStor Fsnupd Module: OK Status of IPStor ISCSI Module: OK Status of IPStor BMR Module: OK( 0) Status of FC Link Down : OK Status of Network Connection: OK Status of force up: 0 Broadcast Arp : NO Number of reported failed devices : 0 NAS health check : NO XML Files Modified : NO IPStor Failover Debug Level : 0 IPStor Self-Monitor Debug Level : 0 Do We Need To Reboot Machine(SM): NO Do We Need To Reboot Machine(FM): NO Nas Started: NO

14. Restartthefailedservernodegracefully,usingtheinit6command:
[VTL_Plus]vtladmin# init6

96267 F

Chapter 6 Recovery following a system failure

139

Failback

15. Oncetherestarthascompleted,openaterminalwindowonthemanagementhost, and ssh totheIPaddressoftherestartednode,VTLPLUSN1:


[mgt_host]user# ssh vtladmin@nnn.nnn.nnn.nnx Connecting to nnn.nnn.nnn.nnx ... Password:

wherennn.nnn.nnn.nnxistheservice(monitoring)IPaddressoftherestarted node,and vtladmin istheVTLadministratoraccountuserID. 16. Makesurethatyouareloggedintotheactual,restartednode:


[VTL_Plus]vtladmin# uname -a SunOS VTLPLUSN1 n.nn Generic_nnnnnn-nn i86pc i386 i86pc

Thesystemshoulddisplaytheexpectednodename. 17. Ifyouarenotloggedintothecorrectsystem,youhaveaccidentlyloggedintothe managementIPaddress(whichalwaysconnectstotheactivenode)ratherthanthe service(monitoring)address.Closethe ssh session,and ssh totheotherIP addressforthefailednode. 18. ChangetothedirectorythatholdstheVTLexecutables:
[VTL_Plus]vtladmin# cd /usr/local/vtl/bin

140

VTL User Guide Mar 2008

F 96267

Failback

19. Runthevtl statuscommand:


[VTL_Plus]vtladmin# vtl status Sun Microsystems VTL Server vn.nn (Build nnnn) Copyright 2001-2007 by FalconStor. All Rights Reserve Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status of of of of of of of of of of of of of of of of of VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL SNMPD Module................ QLogic Module............... Authentication Module....... Server (Compression) Module. Server (FSNBase) Module..... Server (Upcall) Module...... Server (Event) Module....... Server (Path Manager) Module Server (Application)........ FC Target Module............ Server VTL Upcall Module.... Server VTL Upcall Daemon.... Server VTL Module........... Communication Module........ Logger Module............... Self Monitor Module......... Failover Module............. [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING]

20. IfoneormoreVTLprocessesarenotRUNNING,stoptheserversoftwareandthen restart:


[VTL_Plus]vtladmin# vtl stop all ... [VTL_Plus]vtladmin# vtl start

96267 F

Chapter 6 Recovery following a system failure

141

Failback

21. Runthesmscommand,andmakesurethattheFailOverStatusisREADYfor failback:


[VTL_Plus]vtladmin# sms Usage: sms {force|nas|nasc|fm|sm|bmr|bmrreset|setroot (sm/fm)|clearreboot(sm/fm) } {value} bmr - to set the BMR health status bmrreset - to reset BMR value nas - to reset the NAS failure status nasc - to set nas health check force - enable force up fm - to set ipstorfm debug level sm - to set ipstorsm debug level Last Update by SM: Sun Jan 28 15:32:39 2007 Last Access by RPC: Sun Jan 28 15:32:35 2007
FailOverStatus: 2(READY)

Status of IPStor Server (Transport) : OK Status of IPStor Server (Application) : OK Status of IPStor Authentication Module : OK Status of IPStor Logger Module : OK Status of IPStor Communication Module : OK Status of IPStor Self-Monitor Module : OK Status of IPStor NAS Modules: OK(0) Status of IPStor Fsnupd Module: OK Status of IPStor ISCSI Module: OK Status of IPStor BMR Module: OK( 0) Status of FC Link Down : OK Status of Network Connection: OK Status of force up: 0 Broadcast Arp : NO Number of reported failed devices : 0 NAS health check : NO XML Files Modified : NO IPStor Failover Debug Level : 0 IPStor Self-Monitor Debug Level : 0 Do We Need To Reboot Machine(SM): NO Do We Need To Reboot Machine(FM): NO Nas Started: NO

22. LoginusingtheVTLmanagementconsole.

142

VTL User Guide Mar 2008

F 96267

Failback

23. IntheobjecttreeoftheVTLconsole,rightclicktherestartedservernode, VTLPLUSN1,andselectFailover > Stop Takeoverfromthecontextmenu.

24. Openaterminalwindowonthemanagementhost,andagainsshtothe management(server)IPaddressoftherestartednode,VTLPLUSN1:


[mgt_host]user# ssh vtladmin@nn.nnn.nnn.nnx Connecting to nnn.nnn.nnn.nnx ... Password:

wherennn.nnn.nnn.nnxistheasconfiguredIPaddressoftherestartednode,and vtladmin istheVTLadministratoraccountuserID. 25. Makesurethatyouareloggedintotheactual,restartednode:


[VTL_Plus]vtladmin# uname -a SunOS VTLPLUSN1 n.nn Generic_nnnnnn-nn i86pc i386 i86pc

Thesystemshoulddisplaytheexpectednodename. 26. Ifyouarenotloggedintothecorrectsystem,youmayhaveaccidentlyloggedinto theserviceIPaddressoftheothernoderatherthanthemanagement(server) address.Closethetelnetsession,andtelnettotheotherIPaddressforthe restartednode. 27. ChangetothedirectorythatholdstheVTLexecutables:


[VTL_Plus]vtladmin# cd /usr/local/vtl/bin

96267 F

Chapter 6 Recovery following a system failure

143

Failback

28. Runthevtl statuscommand:


[VTL_Plus]vtladmin# vtl status Sun Microsystems VTL Server vn.nn (Build nnnn) Copyright 2001-2007 by FalconStor. All Rights Reserve Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status Status of of of of of of of of of of of of of of of of of VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL VTL SNMPD Module................ QLogic Module............... Authentication Module....... Server (Compression) Module. Server (FSNBase) Module..... Server (Upcall) Module...... Server (Event) Module....... Server (Path Manager) Module Server (Application)........ FC Target Module............ Server VTL Upcall Module.... Server VTL Upcall Daemon.... Server VTL Module........... Communication Module........ Logger Module............... Self Monitor Module......... Failover Module............. [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING] [RUNNING]

29. IfoneormoreVTLprocessesarenotRUNNING,stoptheserversoftwareandthen restart:


[VTL_Plus]vtladmin# vtl stop all ... [VTL_Plus]vtladmin# vtl start

144

VTL User Guide Mar 2008

F 96267

Failback

30. Runthesmscommand,MakesurethattheFailOverStatusisnowUP:
[VTL_Plus]vtladmin# sms Usage: sms {force|nas|nasc|fm|sm|bmr|bmrreset|setroot (sm/fm)|clearreboot(sm/fm) } {value} bmr - to set the BMR health status bmrreset - to reset BMR value nas - to reset the NAS failure status nasc - to set nas health check force - enable force up fm - to set ipstorfm debug level sm - to set ipstorsm debug level Last Update by SM: Sun Jan 28 15:32:39 2007 Last Access by RPC: Sun Jan 28 15:32:35 2007
FailOverStatus: 1(UP)

Status of IPStor Server (Transport) : OK Status of IPStor Server (Application) : OK Status of IPStor Authentication Module : OK Status of IPStor Logger Module : OK Status of IPStor Communication Module : OK Status of IPStor Self-Monitor Module : OK Status of IPStor NAS Modules: OK(0) Status of IPStor Fsnupd Module: OK Status of IPStor ISCSI Module: OK Status of IPStor BMR Module: OK( 0) Status of FC Link Down : OK Status of Network Connection: OK Status of force up: 0 Broadcast Arp : NO Number of reported failed devices : 0 NAS health check : NO XML Files Modified : NO IPStor Failover Debug Level : 0 IPStor Self-Monitor Debug Level : 0 Do We Need To Reboot Machine(SM): NO Do We Need To Reboot Machine(FM): NO Nas Started: NO

31. IntheobjecttreeoftheVTLconsole,makesurethatneithernodenameisshown inred,indicatinganerror. Innormaloperations,servernodenamesaredisplayedinblack.Redindicatesthat theserverhasfailedovertoitsprimary.Greenindicatesthattheserverhastaken overforafailedprimaryservernode.Ayellowmarkerindicatesthatthe administratorhassuspendedfailover. 32. Foreachserver,selecttheservernodeintheobjecttreeoftheVTLconsole,select theFailover Informationtabinthewindowatright,andmakesurethatthe failbackwassuccessful.
96267 F Chapter 6 Recovery following a system failure 145

Resuming backups following a failover/failback

FailovereventsarealsoavailableviatheprimaryserversEventLog. Nexttask: Resumingbackupsfollowingafailover/failbackonpage 146.

Resumingbackupsfollowinga failover/failback
Failover/failbacktakeapproximatelythreeminutestocomplete.Duringthisperiod, I/Oisnotpossible,andanybackup,import/export,replicationjobsthatarelaunched fail. Thereafter,youmayormaynotneedtorestartbackupoperations,dependingonthe applicationusedandthebackuphostoperatingsystem.

146

VTL User Guide Mar 2008

F 96267

CHAPTER

Configuringemailnotifications
YoucanconfigureVTLappliancestosendautomaticnotificationstolocalsystem administratorsviaemailwheneversystemproblemsarise.

Configuringemailnotifications
1. IntheobjecttreeoftheVTLconsole,rightclickontheVTLservernode,and selectOptions > Enable CallHome. 2. WhentheConfigure Email Alerts Wizard appears,enterthenameofthe outgoingmailserver(Abelow),theemailaddressthattheVTLappliancewilluse whensendingnotifications (B),theemailaddress(es)thatwillreceive notificationsforthedesiredconfiguration (C).

SMTP_server_name

B C

account_for_the_vtl_notifications_agent @customer.com account _to_notify@customer.com

96267 F

147

NotethatemailnotificationscannotuseanSSLconnection.Iftheemailserver requiresSSL,configureemailnotificationtousethelocalhostSMTPserver,and makesurethatDNSandSMTParesetupandrunningontheVTLservernode. Theemailaccountpasswordisstoredinplaintext,sosetupanaccountthatthe SMTPserverwilluseexclusivelyforemailnotification. 3. Usethe Interval controlsprovided(D above)tospecifythefrequencywith whichnotificationsaresent.ThenpressOK (E). 4. WhentheSet Email Alerts Signature Properties panelappears,enter theemailsignaturethatshouldappearineachnotification,andpressNext. 5. WhentheSet Email Alerts Trigger Propertiespanelappears,checkthe checkboxesforthescriptsthatshouldtriggeranemail(C below).Thenpress Next(D).

Defaultscriptsincludethefollowing:

chkcore.sh 10 notifiestheadministratorifanewcorefileisfoundintheVTL bindirectory.Newcorefilesarecompressedandtheoriginalsaredeleted,along witholdercompressedcorefilesthatexceedthemaximum(10isthedefault). kfsnmem.sh 10notifiestheadministratorifthemaximumnumberofmemory pageshasnotbeensetorifthenumberofavailablepagesfallbelowapredefined percentage.

memchk.sh 5 notifiestheadministratoriftheavailablesystemmemoryfalls belowapredefinedpercentage. ipstorsyslogchk.shnotifiestheadministratorifanyinstancesofapre definedsetofmessagesappearinthesystemlog

148

VTL User Guide Mar 2008

F 96267

ipstorckcfg check ipstor.conf (VTLconfigurationcheck)notifiesthe administratoriftheVTLsoftwaresXMLconfigurationfile,ipstor.conf, changes.Ifchangesarefoundorifnopreviousversionexists,thescriptcreates acopyofthecurrentfileunderthenameipstorconf.diff.nnn,wherennn isthescriptgeneratedversionnumberofthefile. diskusagechk.sh / 95notifiestheadministratorifrootfilesystem utilizationexceedsapredefinedpercentage.Ifthecurrentpercentageisover thespecifiedpercentage(bydefault,95%).Copiesofthescriptcanbemodified tomonitoranychosenmountpoint. defaultipchk.sh eth0 10.1.1.1notifiestheadministratoriftheIP addressforthespecifiedNICdoesnotmatchaspecifiedvalue.Copiesofthe scriptcanbemodifiedtomonitoradditionalNICs. ipstorstatus.shrunsthevtl statuscommandandnotifiesthe administratorifoneormoreVTLsoftwaremoduleshavestopped.

6. Whenthe Set Email Alerts System Log Check Properties dialog appears,addtheregularexpressionsforanypatternsthatyouwantthe notificationprocesstoparseforwhenexamininglogs.Toaddanexpression,press Add (Hbelow)tobringupadialogbox,thenenterthepatterninthespace provided.Press Next (J) when ready.

96267 F

Chapter 7 Configuring email notifications

149

7. WhentheEmailAlertsEventNotificationConfigurationpanelappears,usethe radiobuttonstoselecttheeventseveritylevelthatshouldtriggernotification (K below),usethespinnercontroltosetthe Maximum event wait time (L), andpress Next (M).

L M

8. Whenthe Verify the Email Alerts Properties panelappears,press Finish. Stophere.

Modifyingemailalertsproperties
Onceemailalertsareenabled,youcanmodifytheinformationasfollows: 1. IntheobjecttreeoftheVTLconsole,rightclickontheVTLservernode. 2. SelectEmail Alerts fromthecontextmenu. 3. Whenthepropertysheetappears,clickontheappropriatetabtomakeyour changes. Stophere.

Customizingemailfields
YoucanoverridethedefaultTarget EmailorSubjectbyspecifyinganemail addresssubjectline.Proceedasfollows:

150

VTL User Guide Mar 2008

F 96267

1. IntheobjecttreeoftheVTLconsole,rightclickontheVTLserver,andselect CallHome > Trigger.

Ifyouspecifyanemailaddress,itoverridesthereturncode:noattachmentsaresent. 2. Tomodifyanexistingtrigger,highlightthetrigger,andpressEdit. 3. Tocreateanewtrigger,pressAdd. Stophere.

96267 F

Chapter 7 Configuring email notifications

151

152

VTL User Guide Mar 2008

F 96267

CHAPTER

UpdatingVTLsoftware
Whensoftwarepatchesbecomeavailable,theyarepostedontheonlineSun StorageTekCustomerResourceCenterwithaccompanying,explanatorytext (readme)files.DownloadthepatchfilestoatemporarydirectoryontheVTL consolehost,andinstallthemusingtheprocessbelow. Ingeneral,youshouldconsultyourSunsupportrepresentativebeforedownloading andapplyingpatches.NeverapplypatchesfromsourcesotherthanSun.

Applyingpatches
Eachpatchfilehasanameoftheform update-vtxxxxxxsolarisnn,where xxxxxxrepresentsthepatchbuildnumberandnnrepresentstheapplicableversion oftheSolarisoperatingsystem.Thecorrespondingtext(readme)fileshavethethe samename,plusthesuffix.txt. AllpatchesareappliedusingtheVTLconsolesoftware,asfollows. 1. Understandthebehaviorofeachpatchbeforeproceeding:readtheaccompanying textfile(thereadme). SomeVTLpatchesrequireaplatformreboot,whileothersmerelystopandrestart theserversoftware. 2. Makesurethatnocriticalprocessesarerunningbeforeyouproceed. Processeswillstopwhentheserversoftwarerestarts.

96267 F

153

3. Then,fromtheVTLconsolemainmenu,selectTools(Abelow).

4. Fromthesubmenu,selectAdd Patch(B above). 5. Whenthewarningnoticeappears,clickOK(C below)tocontinue.

154

VTL User Guide Mar 2008

F 96267

6. Locatethesubdirectorywherethepatchfilesreside(Dbelow),selectthepatchfile (E),andpressOpen(F).

update-vtxxxxxxsolarisnn E

update-vtxxxxxxsolarisnn

Intheexample,thepatchfilesareshowninthestandardlocationwherepatchesare keptontheVTLappliance.Ifyouarerunningtheconsolefromaremotehost,the patchfileswillbeinthetemporarydownloaddirectorythatyouselected. 7. Whentheconfirmationdialogappears,typeYES inthetextbox(Gbelow),and pressOK(H).

update-vtxxxxxxsolarisnn

Description_of_patch

8. Ifthepatchrequiresit,reboottheserver,logbackintoSolaris,andrestartthe VTLconsole. Otherwise,thepatchesinstallandrestarttheVTLservice,loggingyouout.Aftera minuteortwo,youcanreconnect.

96267 F

Chapter 8 Updating VTL software

155

9. ReconnecttotheVTLserverbydoubleclickingontheservernodeintheobject treeattheleftoftheVTLconsole. 10. Verifythatthepatchwassuccessfullyapplied:afteryouhaveconnected,selectthe Version Info tabfortheserver(Jbelow),andmakesurethattheVersion and Build (K)havebeenupdated.

K
N.N

vN.N nnnn

nnnn

156

VTL User Guide Mar 2008

F 96267

APPENDIX

VTLcommandlinereference
TheVTLcommandlineinterface(CLI), iscon,providesanongraphicalalternative totheVTLConsolegraphicaluserinterface(GUI).WhileGUIsaregenerally superiorforoccasionalorhighlyinteractivetasksoverfastlinks,CLIscomeinto theirownwhenautomationorrepeatabilityofcomplextasksisanissueorwhen connectivityislimitedandbandwidthlow.CLIcommandscanbeincorporatedin MicrosoftWindowsbatchfiles,Linux/UNIXshellscripts,orPerlscriptsandcanbe readilyintegratedintomanystandardmanagementenvironments. Foreach iscon command,thisappendixprovidesasummaryofthelongand shortformsofthecommandsyntax,abriefdescriptionofthefunctionalityofthe command,andanexplanationofthemeaningsofrequiredandoptionalparameters.

Understandingtypographicalconventions
Inthecommandlinereference,thefollowingconventionsareusedincommand descriptions:

Pointybrackets(<>)enclosevariablevalues: -s <server-node>. Squarebrackets([ ])encloseoptionalcommandlineparameterstrings: -s <server-node> [-u <username> -p <password>]. Pipecharacters(|)separatealternatives: -A copy|move. Curlybraces({ })groupelementsthatgotogether: {-A copy|move [-Y <days>] [-J]}|{-N replication|remotemove}. Aplus(+)indicateszeroormoreofthesameelement: -F "{{library|drive|tape},}+"

Eachcommandentryshowsthesyntaxfortheshortformofthecommandfollowed bythelongform.Notethat,forclarity,thecommanddescriptionsbelowshow commandsyntaxandexamplesonmultiplelines.Buteachiscon commandmust beenteredonasinglecommandline.

96267 F

157

Permissionsandpaths
Theisconinterfaceisavailableexclusivelytothe root useraccount. Pathstoexecutablescanchangewithlaterbuildsofthesoftware.But,atthetimeof publication,thepathtotheVTLPlus2.0 iscon executableonSolarisandLinux systemsis: /usr/local/vtl/bin OnMicrosoftWindowssystems,thepathis: C:\Program Files (x86)\Sun Microsystems\VTL 5.0\Console\Bin

Gettingonlinehelp
Enteringthe iscon commandonitsowndisplaysalistoftheavailablecommands. Enteringwithiscon withacommandname(iscon<commandname>)displaysa listofthecommandlineparameters(arguments)forthespecifiedcommand.

Generalusage
Followtheconventionsbelowwhenenteringiscon commands:

Entereachcommandonasingleline,withspacebetweenarguments. Useasinglehyphen(-)withtheparametersoftheshortformofacommandand followtheparameterwithitsvalue,separatedbyaspace:


-s <server-node>

Useadoublehyphen(--)withparametersinthelongformofacommandand designatethevaluewithanequalssign(=).
--server-name=<server-node>

Theorderoftheargumentsisnotsignificant. Encloseliteralvaluesthatcontaincontrolcharacters,suchas*,<,>,?,|,%,$,and spaces,indoubleorsinglequotationmarks. Literalscannotcontainleadingortrailingspaces.Leadingortrailingspaces enclosedinquotesarestripped. Shortargumentsarecasesensitive.

158

VTL User Guide Mar 2008

F 96267

Commonarguments
Thefollowingargumentsarecommontomanycommands.
Short Argument Long Argument Value/Description

-s -u -p -c -v

--server-name --server-username --server-password --client-name --vdevid --rpctimeout=<1..30000>

VTLhostnameorIPaddress VTLuseraccount VTLuseraccountpassword VTLclientname VTLvirtualdeviceID RPCtimeout

-X
<1..30000>

The--server-username (-u)and--server-password (-p)argumentsareonly usedwhenloggingintoaserver.Youdonotneedthemfortheremainderofthesession. TheRPCtimeoutparameter(-X)specifiestheamountoftimethatthecommandshould spendonretriesiftheserverdoesnotrespondimmediately.Thevalueisconfigurableto anumberwithintherange 1 to 30000 seconds,withadefaultof30seconds.

Securityandthecommandline
Tousethe iscon interface,youeitherloginwithiscon login (onpage164)orsupply logincredentialsasargumentstoaniscon command.Supplyinglogincredentialsas argumentsonthecommandlinefacilitatesscripting,butitmayalsointroduceasecurity issue,particularlyif iscon commandsareexecutedfrommachinesinnonsecured locations,viaaLocalAreaNetwork(LAN).Whenpassedfromthecommandline, passwordsappearincleartextintheoperatingsystemscommandlinehistoryfile,a hiddenfilethatusuallyresidesintheusershomedirectoryunderanamelike .sh_history(k shellandc shell)or .bash_history (bashshell).Whilethehistory fileisassecureastheusersloginaccount,storingpasswordsparticularlyforremote serversondiskincleartextisnotnormallyabestpractice.Iftheuserspasswordwere compromised,theVTLapplianceswouldbeaswell. Iflocalauditandsecuritypoliciesallow,youcanaddressthisissuebyconfiguring commandshellstoexclude iscon commandsfromthecommandhistoryorbyediting orclearingshellcommandhistorieseachtimeyoucompletean iscon session.Check youroperatingsystemandshelldocumentationforspecificinstructions. Ifyouusethe bash shellonaSunSolarisorLinuxhost,youcansimplysetan environmentvariabletoexcludeiscon commandsfromthehistoryfile:
# export HISTIGNORE="iscon"

96267 F

Appendix A: VTL command line reference

159

Whenyoutakethisapproach,youcancontinuetousethecommandhistory normally.Ifyouusethek shell,youcancleartheentirehistoryfileusingthe followingcommand:


# >.sh_history

Thisapproachwipesouttheentirecommandhistory,soyoucannolongerscroll backtoreusecommands.Moreover,notallshellimplementationssupportthis approach,andyourorganizationsauditand/orsecuritypoliciesmaynotallowit.

Indexofcommands
Topical index Login and logout on page 163 Appliance management on page 166 Client management on page 169 Virtual library, device, and tape management on page 179 Importing to and exporting from virtual libraries on page 201 Automated tape caching on page 211 Replication management on page 218 Physical device management on page 233 Reporting on page 244 Failover management on page 257 Alerting, notification, and troubleshooting on page 263 Alphabetical listing New (N)

addclient (onpage172) addlicense (onpage167) addvirtualdrive (onpage189) assignresourcetovtl (onpage196) assignvdev (onpage175) cancelimportexportjobs (onpage208) createdevicethroughputreport (onpage247) creatediskusagereport (onpage245) createfcaconfreport (onpage253) createjobreport (onpage249) createphyresourcesallocreport (onpage251) createphyresourceallocreport (onpage252) createphyresourcesconfreport (onpage250) createreplication (onpage219) createreplicationstatusreport (onpage254) createscsichannelthroughputreport (onpage 248) createserverthroughputreport (onpage246) createstandalonedrive (onpage190) createvdev (onpage177)
N N N N N N N N N N N

160

VTL User Guide Mar 2008

F 96267

Topical index

Alphabetical listing

New (N) N N

createvirlibinforeport (onpage255) createvirtapeinforeport (onpage256) createvirtuallibrary (onpage186) createvirtualtape (onpage192) deleteclient (onpage173) deleteimportexportjobs (onpage210) deletevdev (onpage178) ejectphysicaltape (onpage241) exportvirtualtape (onpage204) getattentionrequired (onpage265) getclientprop (onpage174) getclientvdevlist (onpage171) geteventlog (onpage264) getfailoverstatus (onpage258) getimportexportjobstatus (onpage209) getpdevinfo (onpage234) getphysicaltapelist (onpage243) getreplicationstatus (onpage230) getsupportedvdrives (onpage184) getsupportedvlibs (onpage183) getvdevlist (onpage170) getvtlinfo (onpage182) getxray (onpage266) importdisk (onpage239) importtape (onpage202) login (onpage164) logout (onpage165) migratevirtualtapes (onpage216) movephysicaltape (onpage242) movevirtualtape (onpage194) plibinventory (onpage195)

96267 F

Appendix A: VTL command line reference

161

Topical index

Alphabetical listing

New (N)

preparedisk (onpage240) promotereplica (onpage221) reclaimdiskspace (onpage217) removelicense (onpage168) removereplication (onpage223) rescandevices (onpage238) resumefailover (onpage260) resumeimportexportjobs (onpage207) resumereplication (onpage226) setreplicationproperties (onpage227) settapecaching (onpage212) settapeproperty (onpage199) startreplication (onpage231) starttakeover (onpage261) stopreplication (onpage232) stoptakeover (onpage262) suspendfailover (onpage259) suspendimportexportjobs (onpage206) suspendreplication (onpage225) syncphysicaltape (onpage214) tapecopy (onpage198) unassignresourcefromvtl (onpage197) unassignvdev (onpage176)
N N N N

162

VTL User Guide Mar 2008

F 96267

Loginandlogout
Whileyoucanenterausernameandpasswordasargumentstoany iscon command,itisoftenlesscumbersometoenterthesecredentialsonceandthenuse theisconinterfacefreelythereafter.isconprovidestowcommandsthatmakethis possible:

login (onpage164) logout (onpage165)

96267 F

Appendix A: VTL command line reference

163

Name: Syntax:

login

iscon login [{-s <server-node> -u <username> -p <password>}|{-e}] [-X <rpc-timeout>] iscon login [{ {--server-name=<server-node> --server-username=<username> --server-password=<password>} | {--environment} }] [--rpc-timeout=<rpc-timeout>] iscon login Please enter login information [format: username:password@servername]:

Description:
ThiscommandlogsyouintothespecifiedVTLServerwithagivenusernameand password.Afterasuccessfullogin,theusernameandpasswordarenotnecessaryfor remainderofthesession. Ifyouloginwithoutsupplyinganycommandlineparameters,thesystempromptsyou:
[<server-node>] # iscon login Please enter login information [format: username:password@servername]: <username>:<password>@<server-node> Command: login executed successfully.

-e (--environment) tells iscon login tolookforthelogincredentialsin environmentvariablesratherthaninstandardinput.Tousethisoption,youmustsetthe followingvariablesinyouroperatingenvironment:


ISSERVERNAME ISUSERNAME ISPASSWORD

164

VTL User Guide Mar 2008

F 96267

Name: Syntax:

logout

iscon logout -s <server-node> [-X <rpc-timeout>] iscon logout --server-name=<server-node> [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandlogsyououtofthespecifiedVTLServer.Onceyoulogout,youcannot entercommandswithoutsupplyinglogincredentials. Ifarenotloggedinwhenyouissuethe logout command, iscon returnserror 0x0902000f.

96267 F

Appendix A: VTL command line reference

165

Appliancemanagement
The iscon interfacealsoallowsyoutomanageappliancesoftwarelicenses.The followingcommandsareavailable:

addlicense (onpage167) removelicense (onpage168)

166

VTL User Guide Mar 2008

F 96267

Name: Syntax:

addlicense

iscon addlicense -s <server-node> [-u <username> -p <password>] -k <license-keycode> [-X <rpc-timeout>] iscon addlicense --server-name=<server-node> [--server-username=<username> --server-password=<password>] --license=<license-keycode> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandaddsalicensekeycode. -k <license-keycode> (--license=<license-keycode>) specifiesthelicense keythatyouwanttoadd.

96267 F

Appendix A: VTL command line reference

167

Name: Syntax:

removelicense

iscon removelicense -s <server-node> [-u <username> -p <password>] -k <license-keycode> [-X <rpc-timeout>] iscon removelicense --server-name=<server-node> [--server-username=<username> --server-password=<password>] --license=<license-keycode> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandremovesalicensekeycode. -k <license-keycode> (--license=<license-keycode>) specifiesthelicense keythatyouwanttoremove.

168

VTL User Guide Mar 2008

F 96267

Clientmanagement
VTLclientsarethebackuphoststhatreadandwritebackupdatatovirtuallibraries andtapes.The iscon interfaceletsyoulistdevicesthatareassignedtoclientsor availableforassignment,manageclients,assignvirtualdevices,andcreatedirect attachvirtualdevicesforclients.Thefollowingcommandsareavailable:

getvdevlist (onpage170) getclientvdevlist (onpage171) addclient (onpage172) deleteclient (onpage173) getclientprop (onpage174) assignvdev (onpage175) unassignvdev (onpage176) createvdev (onpage177) deletevdev (onpage178)

96267 F

Appendix A: VTL command line reference

169

Name: Syntax:

getvdevlist

iscon getvdevlist -s <server-name> [-u <username> -p <password>] [{-l [{-v <vdevid>}|{-n <vdevname>}][-A] [-C] [-M <output-delimiter>]}] [-X <rpc-timeout>] iscon getvdevlist --server-name=<server-name> [--server-username=<username> --server-password=<password>] [{ --longlist [{--vdevid=<vdevid>}|{--vdevname=<vdevname>}] [--long-physical-layout] [--long-client-list] [--output-delimiter=<output-delimiter>] }] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandretrievesanddisplaysinformationaboutallvirtualdevicesoraspecific virtualdevicefromthespecifiedserver.Thedefaultoutputformatisalistwitha heading. -l (--longlist) specifiesdetailedinformationforeachvirtualdevice.Youcanlimit theoutputtoaparticulardeviceusingeitherofthefollowingsubparameters:

-v <vdevid> (--vdevid=<vdevid>) specifiesthedevicebyvirtual

device ID.

-n <vdevname> (--vdevname=<vdevname>) specifiesthedevicebyvirtual

devicename.
Theremainingsubparametersof -l (--longlist)finetunetheparametersfurther:

-A (--long-physical-layout) displaysphysicallayoutdetailsfordevices. -C (--long-client-list) liststheclientstowhichdevicesareassigned. -M <delimiter> (--output-delimiter=<delimiter>) formatstheoutput

byreplacingthenewlinecharacterwiththespecifieddelimiter,astringofup toeight(8)characters.

170

VTL User Guide Mar 2008

F 96267

Name: Syntax:

getclientvdevlist

iscon getclientvdevlist -s <server-node> [-u <username> -p <password>] -c <client-name> [-t <client-type>] [{-l [-M <output-delimiter>]}] [-X <rpc-timeout>] iscon getclientvdevlist --server-name=<server-node> [--server-username=<username> --server-password=<password>] --client-name=<client-name> [--client-type=<client-type>] [{--longlist [--output-delimiter=<output-delimiter>]}] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddisplaysinformationallvirtualdevicesassignedtotheclientfromthe specifiedserver.Thedefaultoutputformatisalistwithaheading.
-c <client-name> (--client-name=<client-name>) specifiesaclientname.If youdonotwishtolimittheoutputtoasingleclient,entertheVTLwildcardcharacter,* (notethatsomeplatformsrequiredoublequotationmarksaroundthe"*"character).

-t <client-type> (--client-type=<client-type>) specifiesoneofthreeclient connectionprotocolsSCSI,FC,orISCSIwhenthe -c (--client-name)switchis settotheVTLwildcardcharacter,*(notethatsomeplatformsrequiredoublequotation marksaroundthe"*"character). -l (--longlist) specifiesdetailedinformationforeachvirtualdevice. -M <delimiter>(--output-delimiter=<delimiter>) formatstheoutputby replacingthenewlinecharacterwiththespecifieddelimiter,astringofuptoeight(8) characters.

96267 F

Appendix A: VTL command line reference

171

Name: Syntax:

addclient

iscon addclient -s <server-node> [-u <username> -p <password>] -c <client-name> [-I <initiator-wwpns>] [{[-a on|off] [-A on|off]}|{-C on|off}] [-X <rpc-timeout>] iscon addclient --server-name=<server-node> [--server-username=<username> --server-password=<password>] --client-name=<client-name> [--initiator-wwpns=<initiator-wwpns>] [ {[--enable-VSA=on|off] [--enable-iSeries=on|off]} | {[--enable-Celerra=on|off} ] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandaddsaclienttothespecifiedserver. -c <client-name> (--client-name=<client-name>) specifiesauniqueclient namewithamaximumlengthof64characters,whichshouldbeenclosedinquotation marksandmustnotincludethefollowingcharacters:<>"&$/\' -I <initiator-wwpns> (--initiator-wwpns=<initiator-wwpns>) specifiesa commadelimitedlistofoneormoreWorldWidePortNames(WWPNs)eachofwhichis a16bytehexadecimalvalue. -a on|off (--enable-VSA=on|off) enables/disablesVolumeSetAddressing, whichis OFF bydefault.When ON isspecified,theC (enableCelerra)switchis automaticallyturnedOFF. -A on|off (--enable-iSeries=on|off) enables/disablessupportforIBM iSeries clients,whichis OFF bydefault.When ON,theC (enableCelerra)switchis automaticallyturnedOFF. -C on|off (--enable-Celerra=<on|off>) enables/disablessupportforEMC Celerra,whichis OFF bydefault.WhenON,thea (enableVSA)andA (enable iSeries)switchesareautomaticallyturnedOFF.

172

VTL User Guide Mar 2008

F 96267

Name: Syntax:

deleteclient

iscon deleteclient -s <server-node> [-u <username> -p <password>] -c <client-name> [-X <rpc-timeout>] iscon deleteclient --server-name=<server-node> [--server-username=<username> --server-password=<password>] --client-name=<client-name> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddeletesaclientfromthespecifiedserver. -c <client-name> (--client-name=<client-name>) specifiestheclientthatyou wanttodelete.

96267 F

Appendix A: VTL command line reference

173

Name: Syntax:

getclientprop

iscon getclientprop -s <server-node> [-u <username> -p <password>] -c <client-name> [-X <rpc-timeout>] iscon getclientprop --server-name=<server-node> [--server-username=<username> --server-password=<password>] --client-name=<client-name> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandgetsclientproperties. -c <client-name> (--client-name=<client-name>) specifiestheclient.

174

VTL User Guide Mar 2008

F 96267

Name: Syntax:

assignvdev

iscon assignvdev -s <server-node> [-u <username> -p <password>] -v <vdevid> -c <client-name> -a R|W|N [-y] [-I <initiatorWWPN>|*] [-T <targetWWPN>|*] [-l <lun>] [-X <rpc-timeout>] iscon assignvdev --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> --client-name=<client-name> --access-mode=<access-mode> [--vlib-only] [--initiatorWWPN=<initiatorWWPN>|*] [--targetWWPN=<targetWWPN>|*] [--lun=<lun>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandpreparesandassignsavirtualdeviceonaspecifiedservertoaspecified client. -v <vdevid> (--vdevid=<vdevid>) specifiesthevirtualdeviceIDofthevirtual tapelibraryorvirtualtapedrivethatyouwanttoassign.
-c <client-name> (--client-name=<client-name>) specifiestheclientthat shouldbeassignedthespecifiedvirtualresource.

-a R|W|N (--access-mode=R|W|N) setsaccesspermissiontoReadonly(R), ReadWrite(W),orReadWriteNonExclusive(N). -y (--vlib-only) overridesthedefaultbehaviorandassignsthevirtualtapelibrary totheclientwithoutassigningallofthevirtualtapedrivesinthelibrary. -I <initiator-wwpn>|* (--initiatorWWPN=<target-wwpn>|*) specifiesthe 16bytehexadecimalWorldWidePortName(WWPN)ofaspecifiedFibreChannel initiator.EnteringtheVTLwildcardcharacter,*,assignsanyWWPN(notethatsome platformsrequiredoublequotationmarksaroundthe"*"character). -T <target-wwpn>|* (--targetWWPN=<target-wwpn>|*) specifiesthe16byte hexadecimalWorldWidePortName(WWPN)ofaspecifiedFibreChanneltarget. EnteringtheVTLwildcardcharacter,*,assignsanyWWPN(notethatsomeplatforms requiredoublequotationmarksaroundthe"*"character). -l <lun> (--lun=<lun>) specifiesaLogicalUnitNumber(LUN)intherange 0-15. IfyoudonotspecifyaLUN,thenextavailableLUNisassigned.

96267 F

Appendix A: VTL command line reference

175

Name: Syntax:

unassignvdev

iscon unassignvdev -s <server-node> [-u <username> -p <password>] -v <vdevid> -c <client-name> [-y] [-f] [-X <rpc-timeout>] iscon unassignvdev --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> --client-name=<client-name> [--vlib-only] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandallowsyoutounassignavirtualdeviceonthespecifiedserverfroma client. -v <vdevid> (--vdevid=<vdevid>) specifiesthevirtualdeviceIDofthevirtual tapelibraryordrivethatyouwanttounassign. -c <client-name> (--client-name=<client-name>) specifiesthenameofthe clientfromwhichyouwanttounassignthelibraryordrive. -y (--vlib-only) overridesthedefaultbehaviorandunassignsthevirtualtapelibrary fromtheclientwithoutunassigningallofthevirtualtapedrivesinthelibrary. -f (--force) unassignsthevirtualdevicewhentheclientisconnectedandthevirtual deviceisattached.Otherwise,thissituationcausesanerror.

176

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createvdev

iscon createvdev -s <server-node> [-u <username> -p <password>] -I <adapter#>:<channel#>:<id#>:<lun#> [-n <vdevname>] [-X <rpc-timeout>] iscon createvdev --server-name=<server-node> [--server-username=<username> --server-password=<password>] --scsiaddress=<adapter#>:<channel#>:<id#>:<lun#> [--vdevname=<vdevname>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandallowsyoutocreateadirectvirtualdevice,suchasvirtualtapelibraryor virtualtapedrive.

-I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) specifiestheSCSIaddressofthevirtual


tapelibraryorvirtualtapedrive.

-n <vdevname> (--vdevname=<vdevname>) specifiesanoptionaldirectvirtual devicenameofupto64characters,whichmaynotinclude<>"&$/\'andmustbe enclosedindoublequotationmarks(leadingandtrailingspacesareautomatically trimmed).Ifanameisnotspecified,thesystemassignsadefaultname.

96267 F

Appendix A: VTL command line reference

177

Name:

deletevdev

iscon deletevdev -s <server-node> [-u <username> -p <password>] -v <vdevid> [-d] [-f] [-X <rpc-timeout>] iscon deletevdev --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--delete-virtual-tapes] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddeletesavirtualtapelibraryorvirtualtapedrivethatisnotconnectedto clients.Youcannotdeleteavirtualtapedrivethatdoesnothavethehighestelement numberinthelibrary,andyoucannotdeletethesolevirtualtapedriveinavirtual library.Additionally,youcannotdeleteavirtualtapethatisconfiguredforreplication unlessyouusethef (force)option(seebelow).

-v (--vdevid=<vdevid>) specifiesthevirtuallibrary,virtualtapedrive,orvirtual tapethatyouwanttodelete.


-d (--delete-virtual-tapes) deletesallassociatedvirtualtapesfromavirtualtape library,astandalonevirtualtapedrive,oraloadedvirtualtapedriveselectedfor deletion.Bydefault,thevirtualtapesarenotactuallydeleted,butmovedtothevaultor, ifloadedinadrive,backtothelibrary. -f (--force) whenusedwiththe-d (--delete-virtual-tapes)switch,forces deletionofavirtualtapethatisconfiguredforreplication.Thecorrespondingvirtual tapereplicaisneitherdeletednorpromoted.

178

VTL User Guide Mar 2008

F 96267

Virtuallibrary,device,andtapemanagement
Youcancreateandmaintainvirtuallibraries,tapedrives,andtapecartridgesfrom the iscon commandline.Thefollowingcommandsareavailable:

enableVTL (onpage180) disableVTL (onpage181) getvtlinfo (onpage182) getsupportedvlibs (onpage183) getsupportedvdrives (onpage184) createvirtuallibrary (onpage186) addvirtualdrive (onpage189) createstandalonedrive (onpage190) createvirtualtape (onpage192) movevirtualtape (onpage194) plibinventory (onpage195) assignresourcetovtl (onpage196) unassignresourcefromvtl (onpage197) tapecopy (onpage198) settapeproperty (onpage199) importtape (onpage202) exportvirtualtape (onpage204) suspendimportexportjobs (onpage206) resumeimportexportjobs (onpage207) cancelimportexportjobs (onpage208) getimportexportjobstatus (onpage209) deleteimportexportjobs (onpage210)

96267 F

Appendix A: VTL command line reference

179

Name: Syntax:

enableVTL

iscon enableVTL -s <server-node> [-u <username> -p <password>] [-I <adapter#>:<channel#>:<id#>:<lun#>] [-c] [-X <rpc-timeout>] iscon enableVTL --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>] [--compression] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcreatesa6000MBrepositoryfortheVirtualTapeLibrarysystem,using specifiedphysicaldevicesifdesired.

-I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) optionallyspecifiestheSCSIaddressof


thephysicaldevicethatyouwanttousefortherepository. -c (--compression) enablescompression,whichisotherwisedisabledbydefault.

180

VTL User Guide Mar 2008

F 96267

Name: Syntax:

disableVTL

iscon disableVTL -s <server-node> [-u <username> -p <password>] [-X <rpc-timeout>] iscon disableVTL --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommanddisablesVTL.Allvirtualtapelibraries,virtualtapedrives,virtualtapes, andtapereplicashavetobedeletedbeforetheVTLcanbedisabled.

96267 F

Appendix A: VTL command line reference

181

Name: Syntax:

getvtlinfo

iscon getvtlinfo -s <server-node> [-u <username> -p <password>] [{-T VLIBS|PLIBS|VDRIVES|VAULT|PDRIVES [-L <tape-library-vid>]}] [-F "{{library|drive|tape},}+"] [{-l [-M]}] [-X <rpc-timeout>] iscon getvtlinfo --server-name=<server-node> [--server-username=<username> --server-password=<password>] [{--vtl-info-type=VLIBS|PLIBS|VDRIVES|VAULT|PDRIVES [--tape-library-vid=<tape-library-vid>]}] [--vtl-info-filter="{{library|drive|tape},}+"] [{--longlist [--output-delimiter=<output-delimiter>]}] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandretrievesVTLinformation. -T VLIBS|PLIBS|VDRIVES|VAULT|PDRIVES (--vtl-info-type= VLIBS|PLIBS|VDRIVES|VAULT|PDRIVES) limitstheinformationdisplayedtothe specifictypethatyouwanttosee.VLIBSdisplaysvirtualtapelibrariesonly.VDRIVES displaysstandalonevirtualtapedrivesonly.VAULTdisplaysvirtualtapevaultonly. PLIBSdisplaysphysicaltapelibrariesonly.PDRIVESdisplaysstandalonephysicaltape drivesonly.The getvtlinfo commanddisplaysallinformationbydefault. -L <tape-library-vid> (--tape-library-vid=<tape-library-vid>) isan optiontospecifythevirtualtapelibrarywhenVLIBSisspecified,ortospecifythe physicaltapelibrarywhenPLIBSisspecified.

-F "{{library|drive|tape},}+" (--vtl-info-filter= "{{library|drive|tape},}+") specifiesacommadelimitedfilterlistenclosedin


quotationmarksandassembledfromthefollowingelements:

libraryincludesphysicaland/orvirtuallibraryinformationintheoutput driveincludesphysicaland/orvirtualdriveinformationintheoutput tapeincludesphysicaland/orvirtualtapeinformationintheoutput.

Thedefaultistodisplayalloftheinformationthatapplies.Specifyingafilterthatdoes notapplytothespecified--vtl-info-type generatesanerror. -l (--longlist) displaysdetailedinformation. -M <delimiter> (--output-delimiter=<delimiter>) withthel (longlist) switchsetreplacesthelinefeedwithaspecifieddelimiterofuptoeightcharacters.

182

VTL User Guide Mar 2008

F 96267

Name: Syntax:

getsupportedvlibs

iscon getsupportedvlibs -s <server-node> [-u <username> -p <password>] [{-l [-t <vendorID>:<productID>] [-c] [-M <output-delimiter>]}] [-X <rpc-timeout>] iscon getsupportedvlibs --server-name=<server-node> [--server-username=<username> --server-password=<password>] [{--longlist [--vlib-type=<vendorID>:<productID>] [--compatible-drive-list] [--output-delimiter=<output-delimiter>] }] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandretrievesinformationaboutallsupportedvirtualtapelibraries. -l (--longlist) providesdetailedinformation.Bydefault,thecommandlists summaryinformation. Thefollowingparametersfinetunetheoutputofthel(longlist)command:

-t <vendorID>:<productID> (--vlib-type= <vendorID>:<productID>) limitstheoutputtoaspecificlibrarytype. -c (--compatible-drive-list) displaysthecompatibledrivesinatabular

formatinsteadofthedefaultlongformat.

-M <delimiter> (--output-delimiter=<delimiter>) replacesthe

defaultlinefeedwithaspecifieddelimiterofuptoeightcharacters.

96267 F

Appendix A: VTL command line reference

183

Name: Syntax:

getsupportedvdrives

iscon getsupportedvdrives -s <server-node> [-u <username> -p <password>] [{-l [-M <output-delimiter>]}] [-X <rpc-timeout>] iscon getsupportedvdrives --server-name=<server-node> [--server-username=<username> --server-password=<password>] [{--longlist [--output-delimiter=<output-delimiter>]}] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandretrievesinformationaboutallsupportedvirtualtapedrives. -l (--longlist) displaysdetailedsupporteddriveinformation.Bydefault,the commandlistssummaryinformation. -M <delimiter> (--output-delimiter=<delimiter>) replacesthedefault linefeedwithaspecifieddelimiterofuptoeightcharacterswhenusedwiththel ( longlist)parameter. Theoutputofthecommandresemblesthatshownbelow:

184

VTL User Guide Mar 2008

F 96267

[<server-node>] # iscon getsupportedvdrives -s <server-node>


Supported Virtual Drives: 30 Vendor Product Revision Media Type Capacity (GB) ------------------------------------------------------------HP Ultrium 1-SCSI E30W ULTRIUM1 100 HP Ultrium 2-SCSI F38W ULTRIUM2 200 HP Ultrium 3-SCSI G27D ULTRIUM3 400 IBM ULTRIUM-TD1 18N2 ULTRIUM1 100 IBM ULTRIUM-TD2 333K ULTRIUM2 200 IBM ULTRIUM-TD3 4C17 ULTRIUM3 400 IBM ULT3580-TD1 22UD ULTRIUM1 100 IBM ULT3580-TD2 333K ULTRIUM2 200 IBM ULT3580-TD3 4C17 ULTRIUM3 400 IBM 03590E11 F26E 3590E 20 IBM 03590B11 F26E 3590B 10 IBM 03590E1A F26E 3590E 20 IBM 03590B1A F26E 3590B 10 IBM 03592J1A 044C 3592 300 QUANTUM DLT7000 2150 DLTIV 35 QUANTUM DLT8000 010F DLTIV 35 QUANTUM SuperDLT1 1414 SDLT1 110 QUANTUM SDLT320 V62 SDLT2 160 SEAGATE ULTRIUM06242-XXX 1460 ULTRIUM1 100 SONY SDX-300C 0101 AIT1 35 SONY SDX-500C 0204 AIT2 50 SONY SDX-700C 0204 AIT3 100 SONY SDZ-100 0200 SAIT 500 SONY SDZ-130 0200 SAIT 500 STK 9840 1.29 T9840A 20 STK T9840B 1.33.309 T9840B 20 STK T9840C 1.35.505 T9840C 40 STK T9940A 1.28 T9940A 60 STK T9940B 1.32.427 T9940B 200 STK T10000A 127 T10000A 500 Command: getsupportedvdrives executed successfully.

96267 F

Appendix A: VTL command line reference

185

Name: Syntax:

createvirtuallibrary

iscon createvirtuallibrary -s <server-node> [-u <username> -p <password>] -t <vendorID>:<productID> [-n <vlib-name>] -d <vendorID>:<productID> [-r <vdrive-name-prefix>] [-R <drives>] [{-A copy|move [-Y <days>] [-J] }|{-N replication|remotemove -S <target-name> [-M <#>D|H|M]}] [-B <barcodes0>-<barcodeN>] [-T <slots>] [-e] [-E <I/E-slots>] [-D -I <initial-size> -C <increment-size>] [-m <max-capacity>] [-L <on|off>] [-k <key-name> -W <key-password>] [-X <rpc-timeout>] iscon createvirtuallibrary --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vlib-type=<vendorID>:<productID> [--vlib-name=<vlib-name>] --vdrive-type=<vendorID>:<productID> [--vdrive-name-prefix=<vdrive-name-prefix>] [--num-of-drives=<drives>] [ {--auto-archive-mode=copy|move [--delay-delete-days=<days>] [--auto-eject-to-ie]} | {--auto-replication=replication|remotemove --target-name=<target-name> [--delay-delete-time=<#>D|H|M]} ] [--barcode=-B <barcodes0>-<barcodeN>] [--num-of-slots=<slots>] [--export-to-ptape] [--import-export-slots=<I/E-slots>] [--capacity-on-demand --initial-size=<initial-size> --increment-size=<increment-size>] [--max-capacity=<max-capacity>] [--auto-loader=<on|off>] [--key-name=<key-name> --key-password=<key-password>] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandcreatesavirtualtapelibraryandassignsitavirtualdeviceID. -t <vendorID>:<productID> (--vlib-type=<vendorID>:<productID>) specifiesthetypeofvirtuallibrarythatyouwanttocreateusingthevendorIDand productID,separatedbyacolon(:). -n <vlib-name> (--vlib-name=<vlib-name>) specifiesanoptionallibraryname. Bydefault,thesystemassignsanameoftheform<vendorID>-<productID>-<vid>. Ifyouusethisoptiontoincludeacommonidentifier(-A,-B,-C,etc.)inthelibrary name,inthenameprefixesofthelibrarystapedrives,andinthebarcodesofthe associatedvirtualtapes(A000000-A999999,B000000-B999999,etc.)youcansimplify librarymanagementsignificantly. -d <vdrive-type> (--vdrive-type=<vdrive-type>) specifiesthetypeofvirtual drivethatyouwanttocreateusingthevendorIDandproductID,separatedbyacolon (:).Seegetsupportedvdrives (onpage184)forinformationonlistingdrivetypes.

186

VTL User Guide Mar 2008

F 96267

-r <vdrive-name-prefix> (--vdrive-name-prefix= <vdrive-name-prefix>) specifiesanoptionalprefixforthevirtualdrivename.By default,thesystemassignsaprefixoftheform<drive-vdendorID>-<driveproductID>-<vid>.Ifyouusethisoptiontoincludeacommonidentifier(-A,-B,-C, etc.)inthelibraryname,inthenameprefixesofthelibrarystapedrives,andinthe barcodesoftheassociatedvirtualtapes(A000000-A999999,B000000-B999999,etc.) youcansimplifylibrarymanagementsignificantly -R <drives> (--num-of-drives=<drives>) specifiesthenumberofvirtualdrives includedinthevirtuallibrary.Thiscanrangefrom 1 (thedefault)uptothemaximum supportedbythelibrary. -A copy|move (--auto-archive-mode=copy|move) enablestheAuto Archive featureandsetsthedesiredmode,copyormove.Theautoarchivingoptionsupportsthe followingtwoparameters:

-Y <days> (--delay-delete-days=<days>) whenusedwiththemove

mode,delaysdeletionofthevirtualtapeforthespecifiednumberofdays,up toamaximumof365daysfollowingtheautoarchiveoperation(thedefault).

-J (--auto-eject-to-ie) ejectsthetapetoanimport/export(I/E)slotafter

theautoarchiveoperationfinishes.
-N replication|remotemove (--auto-replication= replication|remotemove) setsuptheremotereplicationfeaturetoeithercopyor movetapesfromthelocaltoaremoteVTLserver.Thereplicationoptionsupportsthe followingtwooptions:

-S <target-name> (--target-name=<target-name>) namestheremote

serverthatwillhostthereplicated/movedvolumes.

-M <#>D|H|M (--delay-delete-time=<#>D|H|M)delaysdeletionofthe tapeforthespecifiednumberofdays(D),hours(H)orminutes(M).Thedefault is 1D (oneday).

-B <barcodes0>-<barcodeN> (--barcode=<barcodes0>-<barcodeN>) specifies therangeofbarcodestousewhencreatingtapesforthevirtuallibrary,startingwiththe numberontheleftofthehyphen(<barcodes0>)andendingwiththenumberonthe right(<barcodesN>).Barcodesarealphanumericstringsof4to12characters,allof whichareofthesamelength.Thesystemgeneratesadefaultrangeifnoneisspecified. But,ifyouusethisoptiontoincludeacommonidentifier(-A,-B,-C,etc.)inthelibrary name,inthenameprefixesofthelibrarystapedrives,andinthebarcodesofthe associatedvirtualtapes(A000000-A999999,B000000-B999999,etc.),youcansimplify librarymanagementsignificantly. -T <slots> (--num-of-slots=<slots>) specifiesthenumberofslotsinthevirtual library.Thiscanexceedthemaximumnumberofslotssupportedbythespecifiedlibrary typeuptoamaximumof 64000. -E <I/E-slots> (--import-export-slots=<I/E-slots>) cannotexceedthe maximumnumberofimport/export(I/E)slotssupportedbythespecifiedlibrarytype. Thedefaultistousethemaximumnumberofslotssupported. -e (--export-to-ptape) isanobsoleteswitchthatyoushouldignore.

96267 F

Appendix A: VTL command line reference

187

-D (--capacity-on-demand) enablesthevirtualtapecapacityondemandoption. Capacityondemandallocatesasmallinitialamountofdiskspacewhenaclientfirst writestoanewvirtualtapeandthenallocatesspaceincrementally,asneeded,uptothe definedcapacityofthevirtualtapecartridge.Sunrecommendsthisoptionasbest practice,becauseitusesthediskcachemoreefficientlyandbetterdistributesloadsacross thediskarray.But,bydefault,thesoftwarecreatesafullcapacitytape.TheD (capacityondemand)optiontakestwoadditionalparameters:

-I <initial-size> (--initial-size=<initial-size>) specifiesthe

sizeoftheinitialdiskallocation.VTLPlus2.0allocatesthisdiskspacethefirst timethataclientwritetothetape.Earlierversionsofthesoftwareallocatethe isinitialspacewhenthetapeiscreated.Thedefaultvalueistheminimum: 5 GB.Generally,thedefaultvalueworksfine.

-C <increment-size> (--increment-size=<increment-size>)

specifiesthesizeofeachcapacityincrement.Thedefaultis5 GB.Generally, thedefaultvalueworksfine.


-m <max-capacity> (--max-capacity=<max-capacity>) specifiesthemaximum capacityofthevirtualtape.Bydefault,thesystemusesthefullcapacityoftheemulated media,ingigabytes(GB).Sunrecommendsthatyouacceptthedefaultifyouareusing thetapecachingoptiononthislibrary,becausethediskandphysicaltapeimagesofa tapecachedvirtualvolumemustbeidentical.Butotherwise,regardlessofthecapacityof theemulatedmedia,Sunrecommendssettingthisvalueto5060GBortotheaverage sizeofallbackupjobs,whicheverislarger.Settingthevirtualtapesizetothisfigure optimizescacheutilizationandminimizeswastedspace. -L <on|off> (--auto-loader=<on|off>) enablestheautoloaderinlibrariesthat supportthisfeature.ThedefaultvalueisOFF. -k <key-name> (--key-name=<key-name>) specifiesthekeyforencryptingvirtual tapesthatareexportedfromlibrariescreatedwithA(autoarchivemode)set.Specify thekeynameandkeypasswordoftheencryptionkeyifyouwishtoencryptthedata whenexportingthevirtualtapetothephysicaltape.Youmustalwaysspecifyakey passwordwiththeW(keypassword)parameterwhenusingthisoption. -W <key-password> (--key-password=<key-password>) specifiesthepassword foraccessingtheencryptionkeyspecifiedwithk(keyname).

188

VTL User Guide Mar 2008

F 96267

Name: Syntax:

addvirtualdrive

iscon addvirtualdrive -s <server-name> [-u <username> -p <password>] -L <tape-library-vid> [-r <vdrive-prefix>] [-R <num-of-drives>] [-X <rpc-timeout>] iscon addvirtualdrive --server-name=<server-name> [--server-username=<username> --server-password=<password>] --tape-library-vid=<tape-library-vid> [--vdrive-name-prefix=<vdrive-prefix>] [--num-of-drives=<num-of-drives>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandaddsavirtualtapedrivetoaspecifyvirtualtapelibrary. -L <tape-library-vid> (--tape-library-vid=<tape-library-vid>) identifiesthevirtualtapelibrarywillholdtheaddedvirtualtapedrive(s). -r <vdrive-prefix> (--vdrive-name-prefix=<vdrive-prefix>) specifiesan optionalprefixforthenamesofthevirtualtapedrivesinthislibrary.Thedefaultprefix is<drive-vendorID>-<drive-productID>-<vid>. -R <num-of-drives> (--num-of-drives=<num-of-drives>) specifiesthe numberofdrivestoadd.Thedefaultis1.

96267 F

Appendix A: VTL command line reference

189

Name: Syntax:

createstandalonedrive

iscon createstandalonedrive -s <server-name> [-u <username> -p <password>] -d <vendorID>:<productID> [-r <vdrive-name-prefix>] [-R <num-of-drives>] [-D -I <initial-size> -C <increment-size>] [-m <max-capacity>] [-X <rpc-timeout>] iscon createstandalonedrive --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdrive-type=<vendorID>:<productID> [--vdrive-name-prefix=<vdrive-name-prefix>] [--num-of-drives=<num-of-drives>] [--capacity-on-demand --initial-size=<initial-size> --increment-size=<increment-size>] [--max-capacity=<max-capacity>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcreatesastandalonevirtualtapedrive. -d <vendorID>:<productID> (--vdrive-type= <vendorID>:<productID>) specifiesthetypeoftapedrivethatyouwanttocreate. Seegetsupportedvdrives (onpage184)forinformationonlistingdrivetypes. -r <vdrive-name-prefix> (--vdrive-name-prefix= <vdrive-name-prefix>) isanoptiontospecifytheprefixofthevirtualdrive.The defaultprefixis<drive-vendorID>-<drive-productID>-<vid>. -R <num-of-drives> (--num-of-drives=<num-of-drives>) canbespecifiedto createmultipledrivesofthesametype.Thedefaultis 1 ifitisnotspecified.The maximumnumberofdrivesis10. -D (--capacity-on-demand) enablesthevirtualtapecapacityondemandoption. Capacityondemandallocatesasmallinitialamountofdiskspacewhenaclientfirst writestoanewvirtualtapeandthenallocatesspaceincrementally,asneeded,uptothe definedcpacityofthevirtualtapecartridge.Sunrecommendsthisoptionasbestpractice, becauseitusesthediskcachemoreefficientlyandbetterdistributesloadsacrossthethe diskarray.But,bydefault,thesoftwarecreatesafullcapacitytape. TheD(capacityondemand)optiontakestwoadditionalparameters:

-I <initial-size> (--initial-size=<initial-size>) specifiesthe

sizeoftheinitialdiskallocation.VTLPlus2.0allocatesthisdiskspacethefirst timethataclientwritetothetape.Earlierversionsofthesoftwareallocatethe isinitialspacewhenthetapeiscreated.Thedefaultvalueistheminimum: 5 GB.Generally,thedefaultvalueworksfine.

-C <increment-size> (--increment-size= <increment-size>) specifiesthesizeofeachcapacityincrement.Thedefault

is5 GB.Generally,thedefaultvalueworksfine.

190

VTL User Guide Mar 2008

F 96267

-m <max-capacity> (--max-capacity=<max-capacity>) specifiesthemaximum capacityofthevirtualtape.Bydefault,thesystemusesthefullcapacityoftheemulated media,ingigabytes(GB).Sunrecommendsthatyouacceptthedefaultifyouareusing thetapecachingoptiononthislibrary,becausethediskandphysicaltapeimagesofa tapecachedvirtualvolumemustbeidentical.Butotherwise,regardlessofthecapacityof theemulatedmedia,Sunrecommendssettingthisvalueto5060GBortotheaverage sizeofallbackupjobs,whicheverislarger.Settingthevirtualtapesizetothisfigure optimizescacheutilizationandminimizeswastedspace.

96267 F

Appendix A: VTL command line reference

191

Name: Syntax:

createvirtualtape

iscon createvirtualtape -s <server-name> [-u <username> -p <password>] -v <parent-vid> [-g <virtual_tape_size> [-I <adapter#>:<channel#>:<id#>:<lun#>] [-n <vdevname>] [-B <barcode> | <barcode-range>] -t <count>] [{-A -l <plib-vid> -b <physical-tape-barcode> [-J]}|{-N [-S <target-name>] [-U <target-username> -P <target-password>]}] [-X <rpc-timeout>] iscon createvirtualtape --server-name=<server-name> [--server-username=<username> --server-password=<password>] --parent-vid=<parent-vid> [--size-gb=<virtual_tape_size>] [--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>] [--vdevname=<vdevname>] [--barcode=<barcode> | <barcode-range>] [--count=<count>] [ { --enable-auto-archive --plib-vid=<plib-vid> --physical-tape-barcode=<physical-tape-barcode> [--auto-eject-to-ie] } | { --enable-auto-remotecopy --target-name=<target-name> [--target-username=<target-username> --target-password=<target-password>] } ] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcreatesavirtualtape. -v <parent-vid> (--parent-vid=<parent-vid>) isthevirtualdeviceidentifier ofthevirtualtapelibraryorvirtualstandalonetapedrivethatyouwanttocreate. -g <virtual_tape_size> (--size-gb=<virtual_tape_size>) specifiesthesize ofthevirtualtapeingigabytes(GB).Ifasizeisnotspecified,systemsetsthesizetothat specifiedbythevirtualtapelibraryordrive.Theg(sizegb)optionisonlyavailable whencapacityondemandisenabledatparentlevel. -I <adapter#>:<channel#>:<id#>:<lun#>, ... | <<filename>> (--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>,...| <<filename>>) definesacommadelimitedlistoftheSCSIaddressesthatidentifythe specificdiskswherethevirtualtapeswillbecreated.Alternatively,youcanenclosethe nameofatextfilethatcontainsaSCSIaddressoneachlinebetweenpointed brackets (< >).

192

VTL User Guide Mar 2008

F 96267

-n <vdevname> (--vdevname=<vdevname>) specifiesanoptionalvirtualtapename prefixofupto64characters,whichmustbeenclosedinquotationmarksandmustnot includethecharacters<>"&$/\'(leadingandtrailingspacesareautomatically trimmed). -B <barcode>|<barcode-range> (--barcode=<barcode>| <barcode-range>) createsavirtualtapeforeachbarcodeinaspecifiedrangeofone ormorebarcodes.Thespecifiedbarcodesmustfallwithintherangedefinedforthe libraryandmustnotcontainanypreviouslyusedbarcodes.Thevaluesdefinedby B (barcode)andt(count)mustagreeifbothparametersareusedtogether.The A (enableautoarchive)cannotbeusedwithB (barcode),becausetheautoarchive optionobtainsbarcodesfromalistofphysicaltapebarcodesspecifiedbyadifferent parameter,b(physicaltapebarcode). -t <count> (--count=<count>) createsthespecifiednumberofvirtualtapesusing barcodesselectedautomaticallyfromwithintherangedefinedforthelibrary.Thelibrary musthavetherequirednumberoffreeslotsavailable.Thevaluesdefinedby B (barcode)andt(count)mustagreeifbothparametersareusedtogether.The t (count)parametercannotbeusedwithA (enableautoarchive),becauseauto archivingcreatesthenumberoftapesspecifiedbyalistofphysicaltapebarcodes. TheA (enableautoarchive)andN(enableautoremotecopy)parametersare mutuallyexclusive. -A (--enable-auto-archive) enablessupportforparentlibrariesthatsupportauto archiving.Itrequiresthefollowingtwosubparameters:

-l <plib-vid> (--plib-vid=<plib-vid>) identifiesthephysicaltape

librarythatwillholdtheexportedtapes.

-b <physical-tape-barcode> (--physical-tape-barcode= <physical-tape-barcode>) specifiesacommadelimitedlistofthe

barcodesofthephysicaltapesthatwillholdexportedvolumes.
Thefollowingsubparameterisoptionalwhenautoarchivingsupportisenabled:

-J (--auto-eject-to-ie) automaticallyejectstheexportedcartridgetoan

import/exportslotonthephysicallibrary,sothatthephysicaltapecanbe removedforoffsitevaulting.
-N (--enable-auto-remotecopy) enablessupportforparentlibrariesthatsupport theautomatedremotecopyfeature.Itsupportsthefollowingsubparameters:

-S <target-name> (--target-name=<target-name>) canbespecified

whenautoremotecopyoptionisspecified.Thedefaultremoteserverfromthe parentlibraryconfigurationwillbeusedifitisnotspecified.

-U <target-username> (--target-username= <target-username>) specifiestheuserloginaccountforthetargetVTL

server.

-P <target-password> (--target-password= <target-password>) specifiesthepasswordforthespecifieduserlogin

account.

96267 F

Appendix A: VTL command line reference

193

Name: Syntax:

movevirtualtape

iscon movevirtualtape -s <server-node> [-u <username> -p <password>] -v <vdevid> [-L <tape-library-vid> | -D <tape-drive-vid> | -l <slot-no>] [-X <rpc-timeout>] iscon movevirtualtape --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--tape-library-vid=<tape-library-vid> | --tape-drivevid=<tape-drive-vid> | --slot-no=<slot-no>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandmovesavirtualtapetoanewlocation,followingthelogicalpaththata tapewouldfollowifitwereresidentinaphysicallibrary.Forinstance,ifavirtualtape currentlyresidesinaslotordriveinavirtuallibrary,youcanmoveitdirectlytoanother slotordriveinthesamevirtuallibrary.Buttomovethesamevirtualtapetoadifferent virtuallibrary,youmustfirstexportthetapefromthevirtuallibrarybymovingitto thevirtualvault.Fromthevirtualvault,youcanthenmovethetapetothefirstavailable slotinanothervirtuallibraryoryoucanmountitinanavailablestandalonedrive.Ifa virtualtapecurrentlyresidesonastandalonedrive,youcanonlymoveittothevault. -v <vdevid> (--vdevid=<vdevid>) identifiesthevirtualtapethatyouwantto move. Thetargetlocationcanbespecifiedinoneofthreeways:

-L <tape-library-vid> (<--tape-library-vid= <tape-library-vid>) identifiesthevirtuallibrarytowhichyouwanttomove

avirtualtapethatcurrentlyresidesinthevirtualvault.

-D <tape-drive-vid> (--tape-drive-vid=<tape-drive-vid>) identifies

either:

thevirtualtapedriveinthecurrentvirtuallibrarytowhichyouwanttomove avirtualtapethatcurrentlyresidesinanotherslotor thevirtualdriveinthecurrentlibraryorthestandalonedrivetowhichyou wanttomoveavirtualtapethatcurrentlyresidesinthevirtualvault.

-l <slot-no> (--slot-no=<slot-no>) specifiestheslotinthecurrent librarylibrarytowhichyouwanttomoveavirtualtapethatcurrentlyresidesin anotherslotorvirtualdriveinthecurrentlibrary.

Ifnotargetlocationisspecified,thevirtualvaultisthedefault.

194

VTL User Guide Mar 2008

F 96267

Name: Syntax:

plibinventory

iscon plibinventory -s <server-node> [-u <username> -p <password>] [-L <tape-library-vid>] [-X <rpc-timeout>] iscon plibinventory --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--tape-library-vid=<tape-library-vid>] [-rpc-timeout=<rpc-timeout>]

Description:
Thiscommandperformsaninventoryofthephysicaltapesinphysicaltapelibraries. -L <tape-library-vid> (--tape-library-vid= <tape-library-vid>) specifiesthephysicaltapelibrarythatyouwanttoinventory.If youdonotspecifyalibrary,allphysicallibrariesareinventoried.

96267 F

Appendix A: VTL command line reference

195

Name: Syntax:

assignresourcetovtl

iscon assignresourcetovtl -s <server-node> [-u <username> -p <password>] -I <adapter#>:<channel#>:<id#>:<lun#> [-L <tape-library-vid>] [-X <rpctimeout>] iscon assignresourcetovtl --server-name=<server-node> [--server-username=<username> --server-password=<password>] --scsiaddress=<adapter#>:<channel#>:<id#>:<lun#> [--tape-library-vid=<tape-library-vid>] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandassignsaphysicaltapelibraryordrivetoVTL. -I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) identifiesthephysicaltapelibraryor drivethatyouwanttoassigntoVTL. -L <tape-library-vid> (--tape-library-vid= <tape-library-vid>) identifiesapreviouslyassignedphysicaltapelibraryasthe parentofaphysicaltapedrivethatyouwanttoassigntoVTL.Physicaltapelibrary informationcanberetrievedbyissuingthegetvtlinfocommand.

196

VTL User Guide Mar 2008

F 96267

Name: Syntax:

unassignresourcefromvtl

iscon unassignresourcefromvtl -s <server-node> [-u <username> -p <password>] -v <vdevid> [-q] [-X <rpc-timeout>] iscon unassignresourcefromvtl --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--preserve-directlink] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandunassignsaphysicaltapelibraryordrivefromVTL. -v <vdevid> (--vdevid=<vdevid>) identifiesthephysicaltapelibraryordrivethat youwanttounassignfromVTL. -q (--preserve-directlink) maintainsthepointersfromvirtualtapestodirect linkedphysicalmediainphysicaltapelibraries.

96267 F

Appendix A: VTL command line reference

197

Name: Syntax:

tapecopy

iscon tapecopy -s <server-node> [-u <username> -p <password>] -v <source-vdevid> -S <target-name> [-U <target-username> -P <target-password>] [-L <library-vid> | -D <drive-vid>] [-n <vdevname>] [-f] [-X <rpc-timeout>] iscon tapecopy --server-name=<server-node> [--server-username=<username> -server-password=<password>] --source-vdevid=<source-vdevid> --targetname=<target-name> [--target-username=<target-username> --target-password=<target-password>] [--tape-library-vid=<library-vid>|--tape-drive-vid=<drive-vid>] [--vdevname=<vdevname>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcopiesatape. -v <source-vdevid> (--source-vdevid=<source-vdevid>) identifiesthe virtualtapethatyouwanttocopy. -S <target-name> (--target-name=<target-name>) identifiestheserverto whichyouwanttocopythetape. -U <target-username> (--target-username=<target-username>) namesthe userloginaccountthatyouwanttouseontheremoteserver. -P <target-password> (--target-password=<target-password>) specifies thepasswordcorrespondingtothespecifiedloginaccountontheremoteserver. -L <library-vid> (--tape-library-vid=<library-vid>) movesthecopyto thespecifiedvirtuallibraryoncecopyingiscomplete. -D <drive-vid> (--tape-drive-vid=<drive-vid>) movesthecopytothe specifiedvirtualstandalonetapedrivewhenthecopyiscompleted. -n <vdevname> (--vdevname=<vdevname>) specifiesanoptionalvirtualtapename ofupto64characters,whichmustbeenclosedindoublequotationmarksandmustnot includethecharacters<>"&$/\'(leadingandtrailingspacesareautomatically trimmed).Ifyoudonotspecifyaname,adefaultnameiscreatedusingtheprimary serverandsourcevirtualtapenames. -f (--force) copiesatapethatiscurrentlyscheduledfordeletionandclearsthe deletionschedule.

198

VTL User Guide Mar 2008

F 96267

Name: Syntax:

settapeproperty

iscon settapeproperty -s <server-node> [-u <username> -p <password>] -v <vdevid> [-B <barcode>] [-f] [-F] [-w on|off] [{-A copy|move|inherited|none [-Y <days>] [-J on|off]}| {-N localcopy|localmove|replication|remotemove|none -S <target-name> [-U <target-username> -P <target-password>] [-M <#>D|H|M]}] [{-k <key-name> -W <key-password>}|{-d}] [-X <rpc-timeout>] iscon settapeproperty --server-name=<server-node> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--barcode=<barcode>] [--force] [--full-capacity] [--tape-write-protect=on|off] [ --auto-archive-mode=copy|move|inherited|none [--delay-delete-days=<days>] [--auto-eject-to-ie=on|off] | --auto-replication=localcopy|localmove|replication|remotemove|none --target-name=<target-name> [--server-username=<username> --server-password=<password>] [--delay-delete-time=<#>D|H|M] ] [ {--key-name=<key-name> --key-password=<key-password>} | {--disable-key} ] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandsetstapeproperties. -v <--vdevid> (--vdevid=<vdevid>) identifiesthevirtualtape. -B <barcode> (--barcode=<barcode>) specifiesthebarcodeforthetape.The barcodemustbeintherangespecifiedforthelibraryunlessthef(force)switchisset. -f (--force) overridesthebarcoderangespecifiedfortheparentlibraryandassigns thevaluepassedbyB(barcode). -F (--full-capacity) disablesthecapacityondemandpropertyofthevirtualtape andexpandsthevolumetothemaximumcapacityforthemedia. -w on|off (--tape-write-protect=on|off) enablesanddisableswrite protection. -A copy|move|inherited|none (--auto-archive-mode=copy|move| inherited|none) controlsautomaticcopyingofthevirtualtapetophysicalmedia. copyenablesautoarchivingandretainsthevirtualtapeafterthephysicalcopyis complete.moveenablesautoarchivinganddeletesthevirtualtapeonceaphysicalcopy

96267 F

Appendix A: VTL command line reference

199

iscomplete.nonedisables autoarchiving.inheritedenablesautoarchivingonthe tapeifautoarchivingisenabledontheparentlibrary.Theparametersupportsthe followingsubparameters:

-Y <days> (--delay-delete-days=<days>) specifiesadelayofupto365

daysbeforedeletingthevirtualtapewhenusedwithAmove (autoarchivemode=move).Thedefaultis365.

-j (--auto-eject-to-ie) ejectsthephysicaltapecopytoanimport/export

(I/E)slotafterautoarchivingiscomplete.
Youcannotusethe -A (--auto-archive-mode)parameterifthetapehasbeen configuredmanuallyforreplicationorifyouhavesettheN(autoreplication) parameter. -k <key-name> (--key-name=<key-name>) specifiesthekeyforencryptingvirtual tapes.YoumustalwaysspecifyakeypasswordwiththeW(keypassword)parameter whenusingthisoption. -W <key-password> (--key-password=<key-password>) specifiesthepassword foraccessingtheencryptionkeyspecifiedwithk(keyname). -d (--disable-key) disablestapeencryptionforthetape. -N localcopy|localmove|replication|remotemove|none (--auto-replication=localcopy|localmove|replication|remotemove| none) controlsautomaticreplicationofthevirtualtapeonorbetweenVTLservers.The parameterrequiresatleastoneofthefollowingsubparameters:

-S (--target-name) identifiestheremoteserverthatwillhostreplicas. -U (--target-username) suppliesthenameoftheloginaccountforthe

remoteserver.

-P (--target-password)suppliesthepasswordforthespecifiedlogin accountontheremoteserver.
-M <#>D|H|M (--delay-delete-time=<#>D|H|M )delays deletionofthe

tapeforaspecifiednumberofdays (D), hours (H) or minutes (M) up to a maximum of 30 days whenautoreplication=localmove|remotemove.The default is 1D (one day).
YoucannotusetheN(autoreplication)parameterifthetapehasbeenconfigured manuallyforreplicationorifyouhavesettheA(autoarchivemode)parameter.

200

VTL User Guide Mar 2008

F 96267

Importingtoandexportingfromvirtuallibraries
The iscon commandlineinterfacesupportsthefollowingimport/export commands:

importtape (onpage202) exportvirtualtape (onpage204) suspendimportexportjobs (onpage206) resumeimportexportjobs (onpage207) cancelimportexportjobs (onpage208) getimportexportjobstatus (onpage209) deleteimportexportjobs (onpage210)

96267 F

Appendix A: VTL command line reference

201

Name: Syntax:

importtape

iscon importtape -s <server-name> [-u <username> -p <password>] [-M copy|direct-access|recycle] -v <plib-or-pdrive-vid> [{-B <barcode>}|{-l <slot-no>}] -L <tape-library-vid> [-b <virtual-tape-barcode>] -t <virtual-tape-slot-no> [-j <job-description>] [-k <key-name> -W <key-password>] [-X <rpc-timeout>] iscon importtape --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--import-mode=copy|direct-access|recycle] --plib-or-pdrive-vid=<plib-or-pdrive-vid> [{--barcode=<barcode>}|{--slot-no=<slot-no>}] --tape-library-vid=<tape-library-vid> --virtual-tape-slot-no=<virtual-tape-slot-no> [--virtual-tape-barcode=<virtual-tape-barcode>] [--job-description=<job-description>] [--key-name=<key-name> --key-password=<key-password>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandvirtualizesaphysicaltape,assigningitslogicalidentitytoavirtualtape thatcanphysicallyresideondisk,onphysicaltape,oronboth.Onceatapehasbeen imported,backupapplicationsaccessitasavirtualtape,viaaVTLvirtuallibraryand drives. -M copy|direct-access|recycle (--import-mode=copy| direct-access|recycle) controlsthebehavioroftheimportprocess:

Whenyouspecifycopy,VTLcreatesavirtualtapeandcopiesthedatafromthe physicaltapemediaintoitsdiskcache. Whenyouspecify direct-access,VTLwritesapointertothephysicaltape copyintoitstapecache.VTLvirtualizestheoriginaltape,effectivelyreplacingthe physicaloriginalwithasinglevirtualvolumethatisphysicallyinstantiatedon theoriginaltapemedia. Whenyouspecify recycle,VTLcreatesavirtualtape,copiesthedatafromthe physicaltapemediatoitsdiskcache,andthenreleasesthephysicaltapemedia forreuse,sothatthevirtualtapeisphysicallyinstantiatedonlyondisk.

-v <plib-or-pdrive-vid> (--plib-or-pdrive-vid= <plib-or-pdrive-vid>) specifiesthevirtualdeviceIDofthephysicaltapelibraryor physicaltapedrivewherethephysicaltapethatyouwanttoimportresides. Whenyouareimportingatapefromaphysicallibrary,youmustspecifyeitherabarcode oraslotlocationusingoneofthefollowingparameters:

-B <barcode> (--barcode=<barcode>) specifiesthebarcodeofthe

physicalvolumethatyouwanttoimport.

202

VTL User Guide Mar 2008

F 96267

-l <slot-no> (--slot-no=<slot-no>) specifiesthelibraryslotthatholds

thephysicalvolumethatyouwanttoimport.
-L <tape-library-vid> (--tape-library-vid=<tape-library-vid>) isthe virtualdeviceIDofthevirtualtapelibrarytowhichyouareimportingthetape. -t <virtual-tape-slot-no> (--virtual-tape-slot-no= <virtual-tape-slot-no>) specifiesthevitualslotthatwillholdtheimportedtape. -b <virtual-tape-barcode> (--virtual-tape-barcode= <virtual-tape-barcode>) specifiesabarcodeforthevirtualtape.Youmustspecify avirtualtapebarcodeiftheoriginal,physicaltapedoesnothaveabarcodeorifthe originalisimportedfromastandalonephysicaltapedrive.VTLwillotherwiseassignthe barcodeoftheoriginalphysicaltapetothenewvirtualvolume.Buttakecarewhen creatingduplicates:mostapplicationsassumethatbarcodesareuniqueandmaybehave unpredictablyiftheyencounterasinglebarcodeinmultiplelocations. -j <job-description> (--job-description=<job-description>) providesa briefdescriptionofthetapeimportjob. -k <key-name> (--key-name=<key-name>) specifiesthekeyfordecryptingaVTL encryptedtapethatyouaregoingtoimport.Youmustspecifyakeypasswordwiththe W(keypassword)parameterwhenusingthisoption. -W <key-password> (--key-password=<key-password>) specifiesthepassword foraccessingtheencryptionkeyspecifiedwithk(keyname).

96267 F

Appendix A: VTL command line reference

203

Name: Syntax:

exportvirtualtape

iscon exportvirtualtape -s <server-name> [-u <username> -p <password>] -v <vdevid> -L <tape-library-vid> [-M copy|move [-Y <days>]] {-b|-B <barcode>|-l <slot-no>} [-j <job-description>] [-f] [-J] [-k <key-name> -W <key-password>] [-X <rpc-timeout>] iscon exportvirtualtape --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> --tape-library-vid=<tape-library-vid> [--export-mode=copy|move [--delay-delete-days=<days>]] {--same-barcode|--barcode=<barcode>|--slot-no=<slot-no>} [--job-description=<job-description>] [--force] [--auto-eject-to-ie] [--key-name=<key-name> --key-password=<key-password>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandexportstheinformationfromavirtualtapetoaphysicaltape. -v <vdevid> (--vdevid=<vdevid>) identifiesthevirtualtapethatyouwantto exporttophysicaltape.
-L <tape-library-vid> (--tape-library-vid= <tape-library-vid>) identifiesthetargetphysicaltapelibrary.

-M copy|move (--export-mode=copy|move) controlsthebehavioroftheexport process.copymode,thedefault,copiesthevirtualtapetophysicalmedia,leavingthe sourcetapeinthevirtuallibrary.movemodecopiesthevirtualtapetophysicalmedia andthendeletesthevirtualoriginal.Anoptionalsubparameterfinetunesthebehavior oftheM (exportmode)parameter:

-Y <days> (--delay-delete-days=<days>) delaysthedeletionofthe

originalforfrom 1 to 365 daysfollowinga move.Thedefaultvalueis365 days.


Youmustspecifyoneofthethreewaysofselectingphysicaltapes:

-b (--same-barcode) selectsaphysicaltapewiththesamebarcodeasthe

virtualtape,ifsuchaphysicaltapeexists.

-B <barcode> (--barcode=<barcode>) specifiesthebarcodeofan

availablephysicaltapeinthephysicaltapelibrary.

-l <slot-no> (--slot-no=<slot-no>) specifiestheslotnumberofan

availablephysicaltapeinthephysicaltapelibrary.
-j (--job-description) passesabriefdescriptionofthetapeexportjob. -f (--force) overridesthedeletionscheduleandexportsatapethatisscheduledfor deletion. -J (--auto-eject-to-ie) ejectstheexportedtapetoanimport/export(I/E)slot oncethejobcompletes.

204

VTL User Guide Mar 2008

F 96267

-k <key-name> (--key-name=<key-name>) specifiesthekeyforencryptingatape priortoexport.YoumustspecifyakeypasswordwiththeW(keypassword) parameterwhenusingthisoption. -W <key-password> (--key-password=<key-password>) specifiesthepassword foraccessingtheencryptionkeyspecifiedwithk(keyname).

96267 F

Appendix A: VTL command line reference

205

Name: Syntax:

suspendimportexportjobs

iscon suspendimportexportjobs -s <server-name> [-u <username> -p <password>] -j <job-id-list> [-X <rpc-timeout>] iscon suspendimportexportjobs --server-name=<server-name> [--server-username=<username> --server-password=<password>] --job-id-list=<job-id-list> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandsuspendsspecifiedimport/exportjobsthatareintheimport/exportqueue andidle. -j <job-id-list> (--job-id-list=<job-id-list>) isacommadelimitedlist ofIDsforjobsthatyouwanttocancel.

206

VTL User Guide Mar 2008

F 96267

Name: Syntax:

resumeimportexportjobs

iscon resumeimportexportjobs -s <server-name> [-u <username> -p <password>] -j <job-id-list> [-X <rpc-timeout>] iscon resumeimportexportjobs --server-name=<server-name> [--server-username=<username> --server-password=<password>] --job-id-list=<job-id-list> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandresumesspecifiedimport/exportjobsthathavebeensuspendedinthe import/exportqueue. -j <job-id-list> (--job-id-list=<job-id-list>) isacommadelimitedlist ofIDsforjobsthatyouwanttoresume.

96267 F

Appendix A: VTL command line reference

207

Name: Syntax:

cancelimportexportjobs

iscon cancelimportexportjobs -s <server-name> [-u <username> -p <password>] -j <job-id-list> [-X <rpc-timeout>] iscon cancelimportexportjobs --server-name=<server-name> [--server-username=<username> --server-password=<password>] --job-id-list=<job-id-list> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcancelsthespecifiedimport/exportjobs.Thejobsmustbeinthe import/exportqueueandmustberunning. -j <job-id-list> (--job-id-list=<job-id-list>) isacommadelimitedlist ofIDsforjobsthatyouwanttocancel.

208

VTL User Guide Mar 2008

F 96267

Name: Syntax:

getimportexportjobstatus

iscon getimportexportjobstatus -s <server-name> [-u <username> -p <password>] [-j <job-id-list>] [-T IMPORT|EXPORT|OTHER -S FAILED|HOLD|READY|OTHER] [-X <rpc-timeout>] iscon getimportexportjobstatus --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--job-id-list=<job-id-list>] | [--job-type=IMPORT|EXPORT|OTHER --job_status=FAILED|HOLD|READY|OTHER] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddisplaysthestatusoftheimport/exportjobspresentinthequeue.Ifno filtersarespecified,thecommanddisplaysallthejobsthatareinthequeue. -j <job-id-list> (--job-id-list=<job-id-list>) isacommadelimitedlist ofjobIDsthatspecifiesthejobsforwhichyouwantstatusinformation.Otherfiltersare ignored. -T IMPORT|EXPORT|OTHER (--job-type=IMPORT|EXPORT|OTHER) reportthe statusofjobsofthespecifiedtype,wheretypeisIMPORT,EXPORT,orOTHER(which includesallothertypes,suchasscanjobs). -S FAILED|HOLD|READY|OTHER (--job_status=FAILED|HOLD| READY|OTHER) reportsthejobsthathavethespecifiedstatus,whichcanbeFAILED, HOLD,READY,orOTHER(whichincludesallothers,suchaswaitingforatape/driveor cancelled).

96267 F

Appendix A: VTL command line reference

209

Name: Syntax:

deleteimportexportjobs

iscon deleteimportexportjobs -s <server-name> [-u <username> -p <password>] -j <job-id-list> [-X <rpc-timeout>] iscon deleteimportexportjobs --server-name=<server-name> [--server-username=<username> --server-password=<password>] --job-id-list=<job-id-list> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddeletesthespecifiedimport/exportjobsfromtheimport/exportqueue.

-j <job-id-list> (--job-id-list=<job-id-list>) isacomma

delimitedlistofjobIDsforjobsthatyouwanttodelete.

210

VTL User Guide Mar 2008

F 96267

Automatedtapecaching
Youcanenableautomatictapecaching,synchronizediskandphysicaltapeimages ofvirtualvolumes,migrateimagesfromdiskcachetophysicaltapemedia,and reclaimspaceinthediskcacheusingthefollowingiscon commands:

settapecaching (onpage212) syncphysicaltape (onpage214) migratevirtualtapes (onpage216) reclaimdiskspace (onpage217)

96267 F

Appendix A: VTL command line reference

211

Name: Syntax:

settapecaching

iscon settapecaching -s <server-name> [-u <username> -p <password>] -L <library-vid> -t 0|1 [-S <hh>:<mm>] [-W -1|0|1|2|3|4|5|6] [-b 0|1] [[-e][-f]][-c <disk-capacity>] [-d <days-old>] [-R <retention-days>|-I|-M|-N] [-X <rpc-timeout>] iscon settapecaching --server-name=<server-name> [--server-username=<username> --server-password=<password>] --tape-library-vid=<library-vid> --tape-caching-enable=0|1 [--start-time=<hh>:<mm>] [--day-of-the-week=-1|0|1|2|3|4|5|6] [--trigger-combine=0|1] [[--end-of-backup] [--tape-full]] [--disk-capacity=<disk-capacity>] [--days-old=<days-old>] [--retention-days= <retention-days>|--immediately|--no-more-space|--never] [--rpc-timeout=<rpc-timeout>]

Description:
Foraspecifiedlibrary,thiscommandenablesordisablestheAutomatedTapeCaching feature,definesapplicabledatamigrationandcachereclamationpolicies,and/orsets RPCtimeouts. -L <library-vid> (--tape-library-vid=<library-vid>) specifiesthevirtual deviceIDofthetargetvirtualtapelibrary. -t 0|1 (--tape-caching-enable=0|1) disables(0)orenables(1)tapecaching. Tapecachingmustbeenabledtosetorchangemigrationand/orreclamationpolicies: whentapecachingisdisabled,anyothercommandlineargumentsareignored. Youdefinedatamigrationandcachereclamationpoliciesbyspecifyingtriggers, conditionsthat,whensatisfied,causetheVTLapplicationtotakethedesiredaction. Datamigrationpoliciescanspecifytimebasedand/orstatebasedtriggers.Youcanset eitheroftwotimebaseddatamigrationtriggers:

-S <hh>:<mm> (--start-time=<hh>:<mm>) startsdailymigrationsatthe

timespecifiedinhoursandminutes,usinga24hrclock.Thedefaultis00:00.

-W -1|0|1|2|3|4|5|6 (--day-of-the-week=-1|0|1|2|3|4|5|6) starts

weeklymigrationsonthespecifieddayoftheweekat00:00,whereSundayis day0,Mondayis1,Tuesdayis2,Wednesdayis3,Thursdayis4,Fridayis5, andSaturdayis6.Thedefaultvalueis -1,whichdisablestheoption.The optionisignoredifstatebasedtriggersarealsospecified.


Youcanalsosetfourstatebaseddatamigrationtriggers:

-e (--end-of-backup) triggersdatamigrationwhenatapeiswrittenand

thenunloadedfromadrive.

-f (--tape-full) delaysmigrationfollowinganendofbackuptrigger

untilthetapeisfull.

212

VTL User Guide Mar 2008

F 96267

-c (--disk-capacity) triggersdatamigrationwhenpercentagediskusage

exceedstheglobalthresholdsetforthesystem.

-d <days> (--days-old=<days>) triggersdatamigrationonceavirtual

tapehasbeenresidentincacheformorethanthespecifiednumberofdays (uptoamaximumof 3650 days).


Youcancombineastarttimetriggerwithstatebasedtriggersusingthefollowing operator:

-b 0|1 (--trigger-combine=0|1) combinestriggersusinglogicalOR(0)

orlogical AND (1).Thedefaultvalueis 1 (AND).Combiningthestarttime (-S)parameterwithstatebasedtriggersusinglogicalAND (1)delaysthe migrationinitiatedbythestatebasedtriggeruntilthetimespecified.


Reclamationpoliciescanspecifyoneofthefollowingstatebasedtriggers(reclamation triggerscannotbecombined):

-R <retention-days> (--retention-days= <retention-days>) releasesvirtualtapesandreclaimstheassociatedcache

spaceoncethevirtualtapeshavebeenresidentincacheformorethanthe specifiednumberofdays.

-I (--immediately) releasesvirtualtapesandreclaimstheassociatedcache

spaceassoonasdatamigrationiscomplete.

-M (--no-more-space) releasesthelastusedvirtualtapeandreclaimsthe

associatedcachespacewheneverspaceisneededtocreateorexpandavirtual tape.

-N (--never) neverreleasesvirtualtapesandneverreclaimscachespace.

Caution becarefulaboutusingtheN(never)trigger.Keepingvirtualtapesin diskcacheindefinitelyispoorpracticebecauseitincreasestheriskthatyouwillrun outofspaceforbackups.

96267 F

Appendix A: VTL command line reference

213

Name: Syntax:

syncphysicaltape

iscon syncphysicaltape -s <server-name> [-u <username> -p <password>] -l <physical-library-vid> -b <barcode> -L <virtual-library-id> -t <virtual-tape-slot-no> [-M cache|metadata|directlink] [-k <key-name> -W <key-password>] [-I {<adapter#>:<channel#>:<id#>:<lun#>},}+] [-n "<vdevname>"] [-g <number>] [-X <rpc-timeout>] iscon syncphysicaltape --server-name=<server-name> [--server-username=<username> --server-password=<password>] --plib-vid=<physical-library-vid> --physical-tape-barcode=<barcode> --tape-library-vid=<virtual-library-vid> --virtual-tape-slot-no=<virtual-tape-slot-no> [--sync-mode=cache|metadata|directlink] [--key-name=<key-name> --key-password=<key-password>] [--scsiaddress={<adapter#>:<channel#>:<id#>:<lun#>},}+] [--vdevname="<vdevname>"] [--size-gb=<number>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcreatesasynchronizedvirtualtapeforthespecifiedphysicaltape.The physicaltapemustbefromthespecifiedphysicaltapelibraryandthevirtualtapewillbe createdinthespecifiedvirtualtapelibrary.Thevirtualtapelibrarymusthavethetape cachingfeatureenabled. Thefollowing,requiredcommandlineparametersidentifythephysicalandvirtual librariesandthetapethatwillbevirtualized: -l <physical-library-vid> (--plib-vid= <physical-library-vid>) specifiesthevirtualIDofthephysicaltapelibrarywhere thephysicaltapesarelocated. -b <barcode> (--physical-tape-barcode=<barcode>) specifiesthebarcodeof thephysicaltape.Thevirtualtapewillbecreatedwiththesamebarcode.Thebarcode mustnotbeinusebyanyothervirtualtapeinthesystem. -L <virtual-library-vid> (--tape-library-vid= <virtual-library-vid>) canspecifytheIDofthevirtualtapelibrarywherethe virtualtapeswillbecreated. -t <virtual-tape-slot-no> (--virtual-tape-slot-no= <virtual-tape-slot-no>) specifiesanemptydestinationslotforthevirtualtape.It cannotbeusedwithMcachemode. Additional,optionalparametersgiveyoufinercontroloverhowsynchronizationisdone: -M cache|metadata|directlink (--sync-mode= cache|metadata|directlink) assignsanoptionalsynchronizationmode:

cache mode(thedefault)createscache metadata modecreatescacheandcopiesmetadata


F 96267

214

VTL User Guide Mar 2008

directlink modecreatesadirectlink.

-k <key-name> (--key-name=<key-name>) specifiesthenameoftheencryption keythatcandecryptthedataonanencryptedimportedtape.Thek(keyname) parameterisalwaysusedwiththeW(keypassword)parameter. -W <key-password> (--key-password=<key-password>) specifiesthekey passwordthatenablesthekeyspecifiedbythekparameter.The W (keypassword) parameterisalwaysusedwiththek(keyname)parameter. -I {<adapter#>:<channel#>:<id#>:<lun#>},}+ (--scsiaddress= {<adapter#>:<channel#>:<id#>:<lun#>},}+) passesacommadelimitedlistof physicaldeviceaddressesthatspecifiesthephysicaldevicestousewhencreatingthe virtualdevice. -n "<vdevname>" (--vdevname="<vdevname>") canspecifyavirtualtapenameor prefixtousecreatingmorethanonetape.Thetapenameshouldbeenclosedindouble quotesandconsistofamaximumof64validcharacters.Leadingandtrailingspacesare removedandfollowingcharactersareinvalid: <>"&$/\' -g <number> (--size-gb=<number>) canspecifytheinitialsize,ingigabytes(GB), ofthevirtualtapeswhencapacityondemandisenabled.Thedefaultis 1.

96267 F

Appendix A: VTL command line reference

215

Name: Syntax:

migratevirtualtapes

iscon migratevirtualtapes -s <server-name> [-u <username> -p <password>] -T <tape-vid-list> [-f] [-X <rpc-timeout>] iscon migratevirtualtapes --server-name=<server-name> [--server-username=<username> --server-password=<password>] --tape-vid-list=<tape-vid-list> [--tape-full] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandmigratesthespecifiedvirtualtapestothesynchronizedphysicallibraries. Theonlyrequiredparameterisacomma-delimitedlistofvirtualtapeIDs: -T <tape-vid-list> (--tape-vid-list=<tape-vid-list>) isacomma delimitedlistofvirtualtapeID(s). -f (--tape-full) forcesfulltapemigration.Bydefault,migrationisincremental.

216

VTL User Guide Mar 2008

F 96267

Name: Syntax:

reclaimdiskspace

iscon reclaimdiskspace -s <server-name> [-u <username> -p <password>] -T <tape-vid-list> [-X <rpc-timeout>] iscon reclaimdiskspace --server-name=<server-name> [--server-username=<username> --server-password=<password>] --tape-vid-list=<tape-vid-list> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreclaimsthediskspaceoccupiedbythespecified,previouslymigrated virtualtapes.TheonlyrequiredparameterisacommadelimitedlistofvirtualtapeIDs: -T <tape-vid-list> (--tape-vid-list=<tape-vid-list>) isacomma delimitedlistofvirtualtapeID(s).

96267 F

Appendix A: VTL command line reference

217

Replicationmanagement
The iscon commandlineinterfaceprovidesafullrangeoftoolsformanaging virtualtapereplication:

createreplication (onpage219) promotereplica (onpage221) removereplication (onpage223) suspendreplication (onpage225) resumereplication (onpage226) setreplicationproperties (onpage227) getreplicationproperties (onpage229) getreplicationstatus (onpage230) startreplication (onpage231) stopreplication (onpage232)

218

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createreplication

iscon createreplication -s <server-name> [-u <username> -p <password>] -v <source-vdevid> -S <target-name> [-U <target-username> -P <target-password>] [-w <watermark-in-MB>] [-d <YYYY><MM><DD><hh><mm> -i <#>H|M] [[-t <timeout>] [-I <retry-in>] [-C <retry-count>]] [-c on|off] [-n <replica-vdev-name>] [-X <rpc-timeout>] iscon createreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> --target-name=<target-name> [--target-username=<target-username> --target-password=<target-password>] [--watermark=<watermark-in-MB>] [--date=<YYYY><MM><DD><hh><mm> --interval=<#>H|M] [--replication-timeout=<timeout>] [--replication-retry-interval=<retry-in>] [--replication-retry-count=<retry-count] [--compression=on|off] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandconfiguresreplication. -v <source-vdevid> (--source-vdevid=<source-vdevid>) identifiesthe virtualtapethatyouwanttoconfigureforreplication. -S <target-name> (--target-name=<target-name>) identifiestheserverto whichthetapeistobereplicated. -U <target-username> (--target-username=<target-username>) passesa loginaccountnametothetargetserver. -P <target-password> (--target-password=<target-password>) passesthe loginpasswordfortheaccountnamespecifiedwithU (targetusername). -w <watermark-in-MB> (--watermark=<watermark-in-MB>) specifiesthe amountofnewdata(inmegabytes)thattriggersreplicationwhenthetapeisunloaded fromthedrive. -d <YYYY><MM><DD><hh><mm> (--date=<YYYY><MM><DD><hh><mm>) isastring thatspecifiesthedateandtimeatwhichreplicationbegins.Itisusedwiththe i (interval)parameterbelow. -i <#>H|M (--interval=<#>H|M) specifiestheintervalatwhichreplicationrepeats inhours(H)orminutes(M).Itisusedwiththed (date)parameterabove.Thedefaultis 1H (onehour). Threerelatedparameterscontrolreplicationtimeoutsandretries:

-t <timeout> (--replication-timeout=<timeout>) specifiesthe

numberofsecondsafterwhichareplicationattempttimesout.Thedefault is 60.

96267 F

Appendix A: VTL command line reference

219

-I <retry-in> (--replication-retry-interval= <retry-in>) specifiesthenumberofsecondstowaitbeforeretrying

replicationfollowingatimeout.Thedefaultis 60.

-C <retry-count> (--replication-retry-count= <retry-count) specifiesthenumberofmaximumnumberofretries.The

defaultis1.
-c on|off (--compression=on|off) enables(on)ordisables(off)compression whenreplicatingtoaremoteVTLserver. -e (--encryption) enables(on)ordisables(off)encryption. -f (--force) replicatesatapethatwouldotherwisebedeletedandclearsthevirtual tapefromthedeletionschedule.

220

VTL User Guide Mar 2008

F 96267

Name: Syntax:

promotereplica

iscon promotereplica {{-s <server-name> -v <vdevid>}|{-S <target-name> -V <replicaid>}} [-u <username> -p <password> -U <target-username> -P <target-password>] [-f] [-X <rpc-timeout>] iscon promotereplica { {--server-name=<server-name> --vdevid=<vdevid>} | {--target-name=<target-name> --replicaid=<replicaid>} } [ --server-username=<username> --server-password=<password> --target-username=<target-username> --target-password=<target-password> ] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandpromotesavalidtapereplicasothatthereplicacanbeusedasaregular virtualtape.Toinvokethecommand,youspecifyaserverandatapeortapereplica,as describedbelow. Youidentifyvirtualtape/replicapairineitheroftwoways.Youcanidentifythe primary/sourceserverandthevirtualtape:

-s <server-name> (--server-name=<server-name>) identifies

primary/sourceVTLserver.

-v <vdevid> (--vdevid=<vdevid>) identifiesthesourcevirtualtape.

Alternatively,youcanspecifyatarget/replicationserverandreplicaID:

-S <target-name> (--target-name=<target-name>) identifiesthe

target/replicationserver.

-V <replicaid> (--replicaid=<replicaid>) identifiesthetapereplica.

Ifyouhavenotused iscon login tologintobothservers,youmustsupplylogin credentialsforbothservers:

-u <username> (--server-username=<username>) suppliesthelogin

accountnamefortheprimary/sourceVTLserver.

-p <password> (--server-password=<password>) suppliesthe

passwordforthespecifiedloginaccountontheprimary/sourceVTLserver.

-U <target-username> (--target-username=<target-username>)

suppliestheloginaccountnameforthetarget/replicationVTLserver.

96267 F

Appendix A: VTL command line reference

221

-P <target-password> (--target-password= <target-password>) suppliesthepasswordforthespecifiedloginaccount

onthetarget/replicationVTLserver.
-f (--force) promotesaninvalidtapereplicathatstillcontainsusefuldata.ButSun recommendsthatyousynchronizethetapereplicawiththesourcevirtualtapefirst unlessthesourcevirtualtapeisphysicallydefectiveorunavailable.

222

VTL User Guide Mar 2008

F 96267

Name: Syntax:

removereplication

iscon removereplication {{-s <server-name> -v <vdevid>}|{-S <target-name> -V <replicaid>}} [-u <username> -p <password>] [-U <target-username> -P <target-password>] [-f] [-X <rpc-timeout>] iscon removereplication { {--server-name=<server-name> --vdevid=<vdevid>} | {--target-name=<target-name> --replicaid=<replicaid> } [ --server-username=<username> --server-password=<password> --target-username=<target-username> --target-password=<target-password> ] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddeletesthereplicationconfigurationforthespecifiedvirtualtapefromthe primary/sourceVTLserveranddeletesthecorrespondingtapereplicafromthe target/replicationserver(ifeitherserverisunreachable,youcanremovereplicationfrom thereachableserverusingthe -f/--forceoption,asdescribedbelow).Toinvokethe command,youspecifyaserverandatapeortapereplica,asdescribedbelow. Youcanspecifyaprimary/sourceserverandvirtualtapeID:

-s <server-name> (--server-name=<server-name>) identifies

primary/sourceVTLserver.

-v <vdevid> (--vdevid=<vdevid>) identifiesthesourcevirtualtape.

Alternatively,youcanspecifyatarget/replicationserverandtapereplicaID:

-S <target-name> (--target-name=<target-name>) identifiesthe

target/replicationserver.

-V <replicaid> (--replicaid=<replicaid>) identifiesthetapereplica.

Ifyouhavenotused iscon login tologintobothservers,youmustsupply credentialsforbothservers:

-u <username> (--server-username=<username>) suppliesthelogin

accountnamefortheprimary/sourceVTLserver.

-p <password> (--server-password=<password>) suppliesthe

passwordforthespecifiedloginaccountontheprimary/sourceVTLserver.

-U <target-username> (--target-username= <target-username>) suppliestheloginaccountnameforthe

target/replicationVTLserver.
96267 F Appendix A: VTL command line reference 223

-P <target-password> (--target-password= <target-password>) suppliesthepasswordforthespecifiedloginaccount

onthetarget/replicationVTLserver.
-f (--force) letsyoudeleteareplicationconfigurationorreplicawhenthe primary/sourceortarget/replicationserverisunreachable.Ifthetarget/replicationserver isunreachable,f(force)deletesthereplicationconfigurationfromtheprimary/source server.Iftheprimary/sourceserverisunreachable,f(force)deletesthetapereplica fromthetarget/replicationserver.

224

VTL User Guide Mar 2008

F 96267

Name: Syntax:

suspendreplication

iscon suspendreplication -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>] iscon suspendreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandsuspendsscheduledreplicationofthespecifiedvirtualtape(itdoesnot stopreplicationjobsthatarecurrentlyinprogress). -v <vdevid> (--vdevid=<vdevid>) identifiesthevirtualtape.

96267 F

Appendix A: VTL command line reference

225

Name: Syntax:

resumereplication

iscon resumereplication -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>] iscon resumereplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandrestartspreviouslysuspended,scheduledreplicationofthespecified virtualtape. -v <vdevid> (--vdevid=<vdevid>) identifiesthevirtualtape.

226

VTL User Guide Mar 2008

F 96267

Name: Syntax:

setreplicationproperties

iscon setreplicationproperties -s <server-name> [-u <username> -p <password>] -v <source-vdevid> [-w <watermark-in-MB>][-d <YYYY><MM><DD><hh><mm> -i <#>H|M] [[-t <timeout>] [-I <retry-in]>] [-C <retry-for>]] [-c on|off] [-X <rpc-timeout>] iscon setreplicationproperties --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--watermark=<watermark-in-MB>] [--date=<YYYY><MM><DD><hh><mm> --interval=<#>H|M] [--replication-timeout=<timeout>] [--replication-retry-interval=<retry-in>] [--replication-retry-count=<retry-for] [--compression=on|off] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreconfiguresreplicationthespecifiedvirtualtape,providedthattape cachingisdisabled. -v <source-vdevid> (--source-vdevid=<source-vdevid>) identifiesthe virtualtapeforwhichyouareconfiguringreplication. Anycombinationofthefollowingparameterstriggersreplication.Youcandisable individualtriggerspreviouslyspecified,butatleastonetriggermustremainactive.

-w <watermark-in-MB> (--watermark=<watermark-in-MB>) specifies

theamountofnewdata(inmegabytes)thattriggersreplicationwhenthetape isunloadedfromthedrive.Todeletethewatermarktriggerspecify w 0 (watermark=0).

-d <YYYY><MM><DD><hh><mm> (--date=<YYYY><MM><DD><hh><mm>) isa

stringthatspecifiesthedateandtimeatwhichreplicationbegins.Itisused withthei (interval)parameterbelow.Todeleteatimebasedtrigger,replace thedatestringwithNA: d NA (date=NA).

-i <#>H|M (--interval=<#>H|M) specifiestheintervalatwhichreplication

repeatsinhours(H)orminutes(M).Itisusedwiththed (date)parameter above.Thedefaultis 1H (onehour).


Threerelatedparameterscontrolreplicationtimeoutsandretries:

-t <timeout> (--replication-timeout=<timeout>) specifiesthe

numberofsecondsafterwhichareplicationattempttimesout.Thedefaultis 60.

-I <retry-in> (--replication-retry-interval= <retry-in>) specifiesthenumberofsecondstowaitbeforeretrying

replicationfollowingatimeout.Thedefaultis 60.

96267 F

Appendix A: VTL command line reference

227

-C <retry-count> (--replication-retry-count= <retry-count) specifiesthenumberofmaximumnumberofretries.The

defaultis1.

-c on|off (--compression=on|off) enables(on)ordisables(off)

compressionwhenreplicatingtoaremoteVTLserver.

228

VTL User Guide Mar 2008

F 96267

Name: Syntax:

getreplicationproperties

iscon getreplicationproperties -s <server-name> [-u <username> -p <password>] -v <source-vdevid> [-X <rpc-timeout>] iscon getreplicationproperties --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandallowsyoutogetthereplicationpropertiesforavirtualdeviceconfigured forreplication.

-v <source-vdevid> (--source-vdevid=<source-vdevid>) identifies

thesourcevirtualtape.

96267 F

Appendix A: VTL command line reference

229

Name: Syntax:

getreplicationstatus

iscon getreplicationstatus -S <target-name> [-U <username> -P <password>] -V <replicaid> [-X <rpc-timeout>] iscon getreplicationstatus --target-name=<target-name> [--target-username=<username> --target-password=<password>] --replicaid=<replicaid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandshowsthereplicationstatus. -S <target-name> (--target-name=<target-name>) identifiesthetargetserver wherethereplicasreside. -V <replicaid> (--replicaid=<replicaid>) identifiesthetapereplicaforwhich youwantstatusinformation.

230

VTL User Guide Mar 2008

F 96267

Name: Syntax:

startreplication

iscon startreplication -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>] iscon startreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandallowsyoutostartreplicationondemandforavirtualdevice. -v <vdevid> (--vdevid=<vdevid>) identifiesthesourcevirtualtapethatyouwant toreplicatefromtheprimaryservertothetargetserver.

96267 F

Appendix A: VTL command line reference

231

Name: Syntax:

stopreplication

iscon stopreplication -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>] iscon stopreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] -vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandallowsyoustopthereplicationofavirtualtypeafteritisalreadyin progress. -v <vdevid> (-vdevid=<vdevid>) identifiesthesourcevirtualtapewhose replicationyouwanttostop.

232

VTL User Guide Mar 2008

F 96267

Physicaldevicemanagement
Theiscon interfaceprovidescommandsforqueryingandscanningforphysical devices,importingandpreparingphysicaldisksforvirtualization,andejecting, moving,andlistingphysicaltapecartridges:

getpdevinfo (onpage234) rescandevices (onpage238) importdisk (onpage239) preparedisk (onpage240) ejectphysicaltape (onpage241) movephysicaltape (onpage242) getphysicaltapelist (onpage243)

96267 F

Appendix A: VTL command line reference

233

Name:

getpdevinfo

iscon getpdevinfo -s <server-name> [-u <username> -p <password>] [ {-F [{-M}|{-C virtual|service-enabled|direct}] [-o {list|detail|guid|scsi}]} | {[-a] [-A] [-I <adapter#>:<channel#>:<id#>:<lun#>] [-o list|detail|size-only]} ] [-X <rpc-timeout>] iscon getpdevinfo --server-name=<server-name> [--server-username=<username> --server-password=<password>] [ { --config { { --include-system-info } | { --category=virtual|service-enabled|direct } } [--output-format=list|detail|guid|scsi] } | { [--allocated-list] [--available-list] [--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>] [--output-format=list|detail|size-only] } ] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddisplaysconfigurationorallocationinformation(thetwoaremutually exclusive). -F (--config) displaysphysicaldeviceconfigurationinformation,excludingsystem deviceinformationbydefault.Eitheroftwomutuallyexclusivesubparameterscan furtherfinetunetheoutput:

-M (--include-system-info) includessystemdeviceinformationinthe

output.

-C virtual|service-enabled|direct (--category=virtual|serviceenabled|direct) filterstheconfigurationinformation,limitingtheoutputto

virtual (default), service-enabled,or direct devices.

234

VTL User Guide Mar 2008

F 96267

Bydefault,intheabsenceoftheF(config)parameter, iscon displaysbothdevice allocationandavailabilityinformation.Youcanfurtherfinetunetheoutputwiththe followingparameters:


-a (--allocated-list) displaysallocatedphysicaldevices. -A (--available-list) displaysavailablephysicaldevices. -I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) filterstheoutputusingthe

specifieddeviceaddress.
-o (--output-format) specifiesanoutputformatselectedfromacontextdependent list.IntheF(config)context,youcanselectfromlist,detail,guid,orscsi.Inthea( allocatedlist)andtheA(availablelist)context,youcanselectfrom:list,detail,or size-only.

Example(s):
[VTL Plus] # iscon getpdevinfo -s <server-name> Disk Library Server: VTL2_0-1200-A Allocated Physical Devices: Device Name ACSL First Sector Last Sector Size(MB) ------------------------------------------------------------------------------------SUN:CSM200_R 0:0:1:1 12416 18559 3 SUN:CSM200_R 0:0:1:1 18560 12306559 6000 SUN:CSM200_R 0:0:2:0 42395776 42401919 3 ... SUN:CSM200_R 0:0:2:4 10510464 37773439 13312 STK:T10000A 1:0:1:0 0 0 0 STK:T10000A 1:0:1:1 0 0 0 STK:T10000A 1:0:1:2 0 0 0 STK:T10000A 1:0:1:3 0 0 0 Total Allocated Space: 59,128 MB Available Physical Devices: Device Name ACSL First Sector Last Sector Size(MB) -----------------------------------------------------------------------------------SUN:CSM200_R 0:0:1:1 12306560 1951449087 946846 SUN:CSM200_R 0:0:2:0 12416 42395775 20695 ... Total Available Space: 4,705,117 MB Command: getpdevinfo executed successfully.

96267 F

Appendix A: VTL command line reference

235

[VTL Plus] # iscon getpdevinfo -s <server-name> -F Disk Library Server: VTL2_0-1200-A Adapter.0: qla2x00fs_1 Number of Devices: 7 Device Name ACSL Total Sectors Category ------------------------------------------------------------------------------SUN:CSM200_R 0:0:1:1 1951436672 Used by Virtual Device SUN:CSM200_R 0:0:1:5 1951436672 Reserved by Virtual Device ... SUN:CSM200_R 0:0:2:8 1951436672 Reserved by Virtual Device Adapter.1: qla2x00fs_2 Number of Devices: 4 Device Name ACSL Total Sectors Category ------------------------------------------------------------------------------STK:T10000A 1:0:1:0 0 Used by Direct Device STK:T10000A 1:0:1:1 0 Used by Direct Device STK:T10000A 1:0:1:2 0 Used by Direct Device STK:T10000A 1:0:1:3 0 Used by Direct Device ... Command: getpdevinfo executed successfully. [VTL Plus] # iscon getpdevinfo -s <server-name> -F -M Disk Library Server: VTL2_0-1200-A Adapter.0: qla2x00fs_1 Number of Devices: 7 Device Name ACSL Total Sectors Category -----------------------------------------------------------------------------SUN:CSM200_R 0:0:1:1 1951436672 Used by Virtual Device SUN:CSM200_R 0:0:1:5 1951436672 Reserved by Virtual Device ... SUN:CSM200_R 0:0:2:8 1951436672 Reserved by Virtual Device STK:T10000A 9:0:2:0 0 Unassigned Device ... Command: getpdevinfo executed successfully. [VTL Plus] # iscon getpdevinfo -s <server-name> -F -C virtual EMC Disk Library Server: VTL2_0-1200-A

236

VTL User Guide Mar 2008

F 96267

Adapter.0: qla2x00fs_1 Number of Devices: 7 Device Name ACSL Total Sectors Category ------------------------------------------------------------------------------SUN:CSM200_R 0:0:1:1 1951436672 Used by Virtual Device SUN:CSM200_R 0:0:1:5 1951436672 Reserved by Virtual Device ... SUN:CSM200_R 0:0:2:8 1951436672 Reserved by Virtual Device Adapter.1: qla2x00fs_2 Number of Devices: 0 ... Adapter.4: qla2x00fs_3 Number of Devices: 3 Device Name ACSL Total Sectors Category ------------------------------------------------------------------------------SUN:CSM200_R 4:0:1:3 1951436672 Reserved by Virtual Device SUN:CSM200_R 4:0:1:7 1951436672 Reserved by Virtual Device SUN:CSM200_R 4:0:2:9 1951436672 Reserved by Virtual Device ... Command: getpdevinfo executed successfully.

96267 F

Appendix A: VTL command line reference

237

Name: Syntax:

rescandevices

rescandevices -s <server-name> [-u <username> -p <password>] [-a <adapter#-range>] [-i <scsiID-range>] [-l <lun-range>] [-L] [-X <rpc-timeout>] rescandevices --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--adapter-range=<adapter#-range>] [--scsi-range=<scsiID-range>] [--lun-range=<lun-range>] [--sequential] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandallowsyoutorescanthephysicalresource(s)onthespecifiedservertoget theproperphysicalresourceconfiguration.Bydefault,alladaptersarerescannednon sequentially.Butyoucanfinetunethisbehaviorusingthefollowingparameters: -a <adapter#-range> (--adapter-range=<adapter#-range>) rescansthe devicesspecifiedbyanadapternumberorrangeofadapternumbers(intheformat <starting#>-<ending#>). -i <scsiID-range> (--scsi-range=<scsiID-range>) rescansthedevices specifiedbyaSCSIIDorrangeofSCSIIDs(intheformat<startingID>-<endingID>). -l <lun-range> (--lun-range=<lun-range>) rescansthedevicesspecifiedbya LUNorrangeofLUNs(intheformat<startingLUN>-<endingLUN>). -L (--sequential) rescansdevicessequentially.

238

VTL User Guide Mar 2008

F 96267

Name: Syntax:

importdisk

iscon importdisk -s <server-name> [-u <username> -p <password>] {{-i <guid>}|{-I <adapter#>:<channel#>:<id#>:<lun#>}} [-X <rpc-timeout>] iscon importdisk --server-name=<server-name> [--server-username=<username> --server-password=<password>] { {--guid=<guid>} | {--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>} } [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandimportsadiskthatwasvirtualizedandsetupwithVTLlogicalresources onanotherVTLserver.Thismakestheresourcesavailabletoclientswhentheoriginal serverisnolongeraccessible. Toimportadevice,youmustuniquelyidentifyitusingoneofthefollowingparameters:

-i <guid> (--guid=<guid>) passestheuniqueidentifierofthephysical

device.

-I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) passestheSCSIaddressofthe

physicaldevice.

96267 F

Appendix A: VTL command line reference

239

Name: Syntax:

preparedisk

iscon preparedisk -s <server-name> [-u <username1> -p <password1>] [-U <username2> -P <password2>] {{-i <guid>}|{-I <adapter#>:<channel#>:<id#>:<lun#>}} -C unassigned|virtual|direct|service-enabled [-N <new-guid>] [-X <rpc-timeout>] iscon preparedisk --server-name=<server-name> [--server-username=<username1> --server-password=<password1>] [--target-username=<username2> --target-password=<password2>] { {--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>} | {--guid=<guid>} } --category=unassigned|virtual|direct|service-enabled [--new-guid=<new-guid>] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandpreparesaphysicaldiskdeviceforusewiththeVTLsystem.Iftheserver ispartofahighavailability,failoverpair,youmustrescanthepartnerafterrunning iscon preparedisk. Iftheserverispartofatwonode,highavailability,failoverpair,supplylogincredentials forthefailovernodeusingtheparametersbelow:

-U <username2> (--target-username=<username2>) passesthenameof

theloginaccountonthefailovernode.

-P <password2> (--target-password=<password2>) passesthepassword

fortheloginaccountonthefailovernode.
Identifythediskthatyouwanttoprepareusingoneofthefollowingparameters:

-i <guid> (--guid=<guid>) passestheuniqueidentifierofthephysical

device.

-I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) passestheSCSIaddressofthe

physicaldevice.
-C unassigned|virtual|direct|service-enabled (--category= unassigned|virtual|direct|service-enabled) specifiesthetypeofphysical devicethatyouarepreparing. -N <new-guid> (--new-guid=<new-guid>) specifiesanewguidforaphysical devicethatisassignedtothe virtual category.

240

VTL User Guide Mar 2008

F 96267

Name: Syntax:

ejectphysicaltape

iscon ejectphysicaltape -s <server-name> [-u <username> -p <password>] -L <physical-tape-library-vid> -B "<physical-tape-barcode-list>" [-A <acs>:<lsm>:<cap>] [-X <rpc-timeout>] iscon ejectphysicaltape --server-name=<server-name> [--server-username=<username> --server-password=<password>] --tape-library-vid=<physical-tape-library-vid> --tape-barcode-list="<physical-tape-barcode-list>" [--acs-lsm-cap=<acs>:<lsm>:<cap>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandejectsphysicaltapesfromthespecifiedlibrary. -L <physical-tape-library-vid> (--tape-library-vid=<physical-tapelibrary-vid>) passesthevirtualIDofthephysicallibrarywherethetapesare located. -B "<physical-tape-barcode-list>" (--tape-barcode-list="<physicaltape-barcode-list>") passesacommadelimitedlistofthephysicaltapesthatyou wanttoeject,enclosedinquotationmarks. -A <acs>:<lsm>:<cap> (--acs-lsm-cap=<acs>:<lsm>:<cap>) specifiesthe addressoftheCartridgeAccessPort(CAP)whereACSLSwillejecttapesfromashared library.

96267 F

Appendix A: VTL command line reference

241

Name: Syntax:

movephysicaltape

iscon movephysicaltape -s <server-name> [-u <username> -p <password>] -m DriveToSlot|SlotToSlot|SlotToDrive|IESlotToSlot|SlotToIESlot -L <physical-tape-library-vid> {{-B <physical-tape-barcode>}|{-l <from-location-id>}} -t <to-location-id> [-X <rpc-timeout>] iscon movephysicaltape --server-name=<server-name> [--server-username=<username> --server-password=<password>] --move-operation=

DriveToSlot|SlotToSlot|SlotToDrive|IESlotToSlot|SlotToIESlot
--tape-library-vid=<physical-tape-library-vid> { {--physical-tape-barcode=<barcode>} | {--from-location-id=<from-location-id>} } --to-location-id=<to-location-id> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandmovesaphysicaltapetoanewlocation. -m DriveToSlot|SlotToSlot|SlotToDrive|IESlotToSlot|SlotToIESlot (--move-operation=DriveToSlot|SlotToSlot|SlotToDrive|IESlotToSlot |SlotToIESlot) specifiesthetypeofactionthatyouwanttoperform. -L <physical-tape-library-vid> (--tape-library-vid=<physical-tapelibrary-vid>) identifiesthephysicallibrarywherethetargettaperesidesby specifyingavirtualID. Youidentifythephysicaltapethatyouwanttomoveineitheroftwoways:

-B <physical-tape-barcode> (--physical-tape-barcode= <barcode>) identifiesthephysicaltapebyspecifyingabarcode. -l <from-location-id> (--from-location-id= <from-location-id>) identifiesthetapebyitsphysicallocationbyspecifying

aslotnumber,animport/export(IE)slotnumber,orthevirtualIDofaphysical tapedrive.
-t <to-location-id> (--to-location-id) identifiesthelocationwhereyou wanttomovethetapebyspecifyingaslotnumber,animport/export(IE)slotnumber,or thevirtualIDnumberofaphysicaltapedrive.

242

VTL User Guide Mar 2008

F 96267

Name: Syntax:

getphysicaltapelist

iscon getphysicaltapelist -s <server-name> [-u <username> -p <password>] -l <physical-tape-library-vid> [-X <rpc-timeout>] iscon getphysicaltapelist --server-name=<server-name> [--server-username=<username> --server-password=<password>] --plib-vid=<physical-tape-library-vid> [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddisplaysalistofthephysicaltapesinthespecifiedphysicaltapelibrary. -l <physical-tape-library-vid> (--plib-vid=<physical-tape-libraryvid>) identifiesthephysicaltapelibrary.

96267 F

Appendix A: VTL command line reference

243

Reporting
YoucanaccessthepreformattedVTLreportsfromthe iscon interfaceusingthe followingcommands:

creatediskusagereport (onpage245) createserverthroughputreport (onpage246) createdevicethroughputreport (onpage247) createscsichannelthroughputreport (onpage248) createjobreport (onpage249) createphyresourcesconfreport (onpage250) createphyresourcesallocreport (onpage251) createphyresourceallocreport (onpage252) createfcaconfreport (onpage253) createreplicationstatusreport (onpage254) createvirlibinforeport (onpage255) createvirtapeinforeport (onpage256)

244

VTL User Guide Mar 2008

F 96267

Name: Syntax:

creatediskusagereport

iscon creatediskusagereport -s <server-name> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>] iscon creatediskusagereport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreportstheamountofdiskspaceconsumedbythevirtuallibrariesonthe specifiedserver. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamedDiskSpaceUsage-servername-MM-DD-YYYY-hh-mmss[.#],where [.#] isasequencenumberappendedtothenameofeachnewreport filewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

96267 F

Appendix A: VTL command line reference

245

Name: Syntax:

createserverthroughputreport

iscon createserverthroughputreport -s <server-name> [-u <username> -p <password] [{{-z t|y|7|30}|{-D <YYYYMMDD>[-<YYYYMMDD>]}}] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createserverthroughputreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [{ {--report-period=t|y|7|30} | {--date-range=<YYYYMMDD>[-<YYYYMMDD>]} }] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreportsthethroughputperformanceandconfigurationthespecified serverduringaspecifiedperiodoftime. Youspecifyareportingperiodinoneoftwoways:

-z t|y|7|30 (--report-period=t|y|7|30) specifiesapredefinedtime period:t (today,thedefault),y (yesterday),7 (thelastsevendays),30 (thelast thirtydays). -D <YYYYMMDD>[-<YYYYMMDD>] (--date-range=<date-range>) specifiesa

dateorarangeofdates(startingandendingdates,separatedbyahyphen). Specifydatesasnumericstringsstartingwithafourdigityearfollowedbyatwo digitmonthandatwodigitdayofthemonth.Datesareevaluatedusinglocal servertime,andthedaterangecanspanamaximumof30days.


-o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed ServerThroughput-servername-MM-DD-YYYY-hhmm-ss[.#],where [.#] isasequencenumberappendedtothenameofeachnew reportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

246

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createdevicethroughputreport

iscon createdevicethroughputreport -s <server-name> [-u <username> -p <password>] -I <adapter#>:<channel#>:<id#>:<lun#> [{{-z t|y|7|30}|{-D <YYYYMMDD>[-<YYYYMMDD>]}}] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createdevicethroughputreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] --scsiaddress=<adapter#>:<channel#>:<id#>:<lun#> [{ {--report-period=t|y|7|30} | {--date-range=<YYYYMMDD>[-<YYYYMMDD>]} }] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreportsthethroughputperformanceofthespecifieddeviceduringa specifiedperiodoftime.
-I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress=

<adapter#>:<channel#>:<id#>:<lun#>)identifiesthedevice. Youspecifyareportingperiodinoneoftwoways:

-z t|y|7|30 (--report-period=t|y|7|30) specifiesapredefinedtime

period: t (today,thedefault), y (yesterday), 7 (thelastsevendays), 30 (the lastthirtydays).

-D <YYYYMMDD>[-<YYYYMMDD>] (--date-range=<date-range>) specifiesa

dateorarangeofdates(startingandendingdates,separatedbyahyphen). Specifydatesasnumericstringsstartingwithafourdigityearfollowedbyatwo digitmonthandatwodigitdayofthemonth.Datesareevaluatedusinglocal servertime,andthedaterangecanspanamaximumof30days.


-o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed SCSIDeviceThroughput-servername-MM-DD-YYYYhh-mm-ss[.#],where [.#] isasequencenumberappendedtothenameofeachnew reportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

96267 F

Appendix A: VTL command line reference

247

Name: Syntax:

createscsichannelthroughputreport

iscon createscsichannelthroughputreport -s <server-name> [-u <username> -p <password>] [{{-z t|y|7|30}|{-D <YYYYMMDD>[-<YYYYMMDD>]}}] -t <adapter-no> [-o <filename>] [-f] [-X <rpc-timeout>] iscon createscsichannelthroughputreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [{ {--report-period=t|y|7|30} | {--date-range=<YYYYMMDD>[-<YYYYMMDD>]} }] --adapter-no=<adapter-no> [--output-file=<filename>] [--force] [--rpc-timeout=<rpctimeout>]

Description:
ThiscommandreportsthethroughputperformanceofthespecifiedSCSI/Fibrechannel. Youspecifyareportingperiodinoneoftwoways:

-z t|y|7|30 (--report-period=t|y|7|30) specifiesapredefinedtime period: t (today,thedefault), y (yesterday), 7 (thelastsevendays), 30 (the lastthirtydays). -D <YYYYMMDD>[-<YYYYMMDD>] (--date-range=<date-range>) specifiesa

dateorarangeofdates(startingandendingdates,separatedbyahyphen). Specifydatesasnumericstringsstartingwithafourdigityearfollowedbyatwo digitmonthandatwodigitdayofthemonth.Datesareevaluatedusinglocal servertime,andthedaterangecanspanamaximumof30days.


-t <adapter-no> (--adapter-no=<adapter-no>)specifiestheSCSI/FibreChannel adapter. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed SCSIChannelThroughput-servername-MM-DD-YYYYhh-mm-ss[.#],where [.#] isasequencenumberappendedtothenameofeachnew reportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

248

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createjobreport

iscon createjobreport -s <server-name> [-u <username> -p <password>] [{{-z t|y|7|30}|{-D <YYYYMMDD>[-<YYYYMMDD>]}}] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createjobreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [{ {--report-period=t|y|7|30} | {--date-range=<YYYYMMDD>[-<YYYYMMDD>]} }] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreportsthejobsthatexecutedduringaspecifiedperiodoftimeona specifiedserver. Youspecifyareportingperiodinoneoftwoways:

-z t|y|7|30 (--report-period=t|y|7|30) specifiesapredefinedtime

period: t (today,thedefault), y (yesterday), 7 (thelastsevendays), 30 (the lastthirtydays).

-D <YYYYMMDD>[-<YYYYMMDD>] (--date-range=<date-range>) specifiesa

dateorarangeofdates(startingandendingdates,separatedbyahyphen). Specifydatesasnumericstringsstartingwithafourdigityearfollowedbyatwo digitmonthandatwodigitdayofthemonth.Datesareevaluatedusinglocal servertime,andthedaterangecanspanamaximumof30days.


-o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed JobReport-servername-MM-DD-YYYY-hh-mmss[.#],where [.#] isasequencenumberappendedtothenameofeachnewreport filewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

96267 F

Appendix A: VTL command line reference

249

Name: Syntax:

createphyresourcesconfreport

iscon createphyresourcesconfreport -s <server-name> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createphyresourcesconfreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcreatesareportthatlistsallofthephysicalresourcesonthespecified server,includingeachphysicaladaptersandphysicaldevices. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed PhysicalResourcesConfiguration-servernameMM-DD-YYYY-hh-mm-ss[.#],where [.#] isasequencenumberappendedtothe nameofeachnewreportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

250

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createphyresourcesallocreport

iscon createphyresourcesallocreport -s <server-name> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createphyresourcesallocreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreportsphysicalresourceallocationforthespecifiedserver. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed PhysicalResourcesAllocation-servername-MMDD-YYYY-hh-mm-ss[.#],where [.#] isasequencenumberappendedtothenameof eachnewreportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

96267 F

Appendix A: VTL command line reference

251

Name: Syntax:

createphyresourceallocreport

iscon createphyresourceallocreport -s <server-name> [-u <username> -p <password>] -I <adapter#>:<channel#>:<id#>:<lun#> [-o <filename>] [-f] [-X <rpc-timeout>] iscon createphyresourceallocreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--scsiaddress=<adapter#>:<channel#>:<id#>:<lun#>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcreatesareportthatdisplaysthephysicalresourcesallocatedtoa specifiedvirtualdeviceonaspecifiedserver. -I <adapter#>:<channel#>:<id#>:<lun#> (--scsiaddress= <adapter#>:<channel#>:<id#>:<lun#>) identifiesthedevice. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed PhysicalResourceAllocation-servername-MM-DDYYYY-hh-mm-ss[.#],where [.#] isasequencenumberappendedtothenameof eachnewreportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

252

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createfcaconfreport

iscon createfcaconfreport -s <server-node> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createfcaconfreport --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--outputfile=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandcreatesareportthatdisplaystheFibreChanneladapterconfigurationfor aspecificserver. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed FCAdaptersConfig-servername-MM-DD-YYYY-hhmm-ss[.#],where [.#] isasequencenumberappendedtothenameofeachnew reportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

96267 F

Appendix A: VTL command line reference

253

Name: Syntax:
iscon [-u [-r [-o

createreplicationstatusreport

createreplicationstatusreport -s <server-name> <username> -p <password>] [-D <date-range>] TAPE|TAPEReplica -R <resource-list>|<resource-file>] <outputFilename>] [-f] [-X <rpc-timeout>]

iscon createreplicationstatusreport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--date-range=<date-range>] [--repl-resource-type= <resource-list>|<resource-file> --resource-list=<resource-list>] [--output-file=<outputFilename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandreportsthereplicationstatusofthespecifiedresources(virtualtapesor replicas)onthespecificserver. -D <YYYYMMDD>[-<YYYYMMDD>] (--date-range=<date-range>) specifiesadate orarangeofdates(startingandendingdates,separatedbyahyphen).Specifydatesas numericstringsstartingwithafourdigityearfollowedbyatwodigitmonthandatwo digitdayofthemonth.Datesareevaluatedusinglocalservertime,andthedaterange canspanamaximumof30days. -r TAPE|TAPEReplica (--repl-resource-type=TAPE|TAPEReplica) specifiesa typeofresource.TAPE isthedefault. -R <resource-list>|<resource-file> (--resource-list=<resourcelist>|<resource-file>) specifiesindividualresourcesbyvirtualidentifier.Supply eitheracommadelimitedlistofvirtualidentifiersorafilename(enclosedinpointed brackets)thatliststhevirtualidentifiers.Alltheresourcesmustbeofthesametype specifiedbyr(replresourcetype). -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed ReplicationStatus-servername-MM-DD-YYYY-hhmm-ss[.#],where [.#] isasequencenumberappendedtothenameofeachnew reportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

254

VTL User Guide Mar 2008

F 96267

Name: Syntax:

createvirlibinforeport

iscon createvirlibinforeport -s <server-name> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createvirlibinforeport --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandliststhevirtuallibrariesconfiguredonthespecifiedserver. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed VirtualLibraryInfo-servername-MM-DD-YYYY-hhmm-ss[.#],where [.#] isasequencenumberappendedtothenameofeachnew reportfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

96267 F

Appendix A: VTL command line reference

255

Name:

createvirtapeinforeport

iscon createvirtapeinforeport -s <server-node> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>] iscon createvirtapeinforeport --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandliststhevirtualtapesconfiguredonthespecifiedserver. -o <filename> (--output-file=<filename>) suppliesafilenameforthereport. Bydefault,reportsarenamed VirtualTapeInfo-servername-MM-DD-YYYY-hh-mmss[.#],where [.#] isasequencenumberappendedtothenameofeachnewreport filewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

256

VTL User Guide Mar 2008

F 96267

Failovermanagement
Youmanagefailoverandfailbackfromthe iscon commandlineusingthe followingcommands:

getfailoverstatus (onpage258) suspendfailover (onpage259) resumefailover (onpage260) starttakeover (onpage261) stoptakeover (onpage262)

96267 F

Appendix A: VTL command line reference

257

Name: Syntax:

getfailoverstatus

iscon getfailoverstatus -s <server-name> [-u <username> -p <password>] [-X <rpc-timeout>] iscon getfailoverstatus --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommanddisplaysthecurrentfailoverstatusandconfigurationofahigh availabilityVTLappliance,giventheservernameofeitherofthetwonodes.

258

VTL User Guide Mar 2008

F 96267

Name: Syntax:

suspendfailover

iscon suspendfailover -s <server-node> [-u <username> -p <password>] [-X <rpc-timeout>] iscon suspendfailover --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--rpc-timeout=<rpc-timeout>]

Description:
Whenexecutedonasecondary(failover)servernodeofahighavailabilityVTL appliance,thiscommandsuspendsfailoverprotection.

96267 F

Appendix A: VTL command line reference

259

Name: Syntax:

resumefailover

iscon resumefailover -s <server-node> [-u <username> -p <password>] [-X <rpc-timeout>] iscon resumefailover --server-name=<server-node> [--serverusername=<username> --server-password=<password>] [--rpctimeout=<rpc-timeout>]

Description:
Whenexecutedonasecondary(failover)servernodeofahighavailabilityVTL appliance,thiscommandresumesfailoverprotectionfollowingasuspension.

260

VTL User Guide Mar 2008

F 96267

Name: Syntax:

starttakeover

iscon starttakeover -s <server-node> [-u <username> -p <password>] [-f] [-X <rpc-timeout>] iscon starttakeover --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Whenexecutedonasecondary(failover)servernodeofahighavailabilityVTL appliance,thiscommandinitiatesfailoverfromtheprimarytothesecondaryservernode. But,bydefault,thecommanddoesnottakeeffectifyouhaveconfiguredthehigh availabilityapplianceforautomaticrecovery,unlessyouforceittodoso. -f (--force) disablesautomaticrecoveryandforcesfailoverfromtheprimarytothe secondaryservernode.Whenyouareready,youmusttheninitiaterecoverymanually usingstoptakeover (onpage262).

96267 F

Appendix A: VTL command line reference

261

Name: Syntax:

stoptakeover

iscon stoptakeover -s <server-node> [-u <username> -p <password>] [-X <rpc-timeout>] iscon stoptakeover --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--rpc-timeout=<rpc-timeout>]

Description:
Whenexecutedonasecondary(failover)servernodeofahighavailabilityVTL appliance,thiscommandinitiatesfailbackfromthesecondarytotheprimaryserver node.

262

VTL User Guide Mar 2008

F 96267

Alerting,notification,andtroubleshooting
The iscon interfaceletsyouexamineeventlogs,listalerts,andgenerate diagnosticreports:

geteventlog (onpage264) getattentionrequired (onpage265) getxray (onpage266)

96267 F

Appendix A: VTL command line reference

263

Name: Syntax:

geteventlog

iscon geteventlog -s <server-node> [-u <username> -p <password>] [-D <date-range>] [-F csv|txt] [-o <filename>] [-H] [-f] [-X <rpc-timeout>] iscon geteventlog --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--date-range=<date-range>] [--file-format=csv|txt] [--include-heading] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandcopieseventlogdataforaspecifieddateorrangeofdatestothespecified fileandfileformat. -D <YYYYMMDD>[-<YYYYMMDD>] (--date-range=<date-range>) specifiesadate orarangeofdates(startingandendingdates,separatedbyahyphen).Specifydatesas numericstringsstartingwithafourdigityearfollowedbyatwodigitmonthandatwo digitdayofthemonth.Datesareevaluatedusinglocalservertime,andthedaterange canspanamaximumof30days. -F csv|txt (--file-format=csv|txt) specifiestheoutputformat,eithercomma delimitedrecordsorplaintext.Thedefaultiscsv. -H (--include-heading) includeseventlogheadingsintheoutput. -o <filename> (--output-file=<filename>) suppliesafullyqualifiedpathand filenamefortheeventlogdata.Bydefault,outputfilesarenamedeventlogYYYY-MMDD-hh-mm-<servername>[.#],where [.#] isasequencenumberappendedtothe nameofeachnewoutputfilewhenf (force)isnotset(seebelow). -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.

264

VTL User Guide Mar 2008

F 96267

Name: Syntax:

getattentionrequired

iscon getattentionrequired -s <server-node> [-u <username> -p <password>] [-X <rpc-timeout>] iscon getattentionrequired --server-name=<server-node> [--server-username=<username> --server-password=<password>] [--rpc-timeout=<rpc-timeout>]

Description:
Thiscommandsdisplaystheattentionrequiredmessages.

96267 F

Appendix A: VTL command line reference

265

Name: Syntax:

getxray

iscon getxray -s <server-name> [-u <username> -p <password>] [-l <#>|all|<YYMMDDhhmm>[-<YYMMDDhhmm>]] [-r] [-o <filename>] [-f] [-X <rpc-timeout>] iscon getxray --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--get-log=<#>|all|<YYMMDDhhmm>[-<YYMMDDhhmm>]] [--rescan-for-xray] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:
ThiscommandconfiguresandrunstheXraydiagnostictool.Xraygathersserver messagesandtakesasnapshotofthecurrentserverconfigurationandenvironment. CreateanXraywhenaSunsupportrepresentativerequestsone. -l <#>|all|<YYMMDDhhmm>[-<YYMMDDhhmm>] (--get-log=<#>|all| <YYMMDDhhmm>[-<YYMMDDhhmm>]) filtersthelogmessages. <#> displaysafixed numberofmessages. <all> displaysallmessages,withnofiltering. <YYMMDDhhmm>[-<YYMMDDhhmm>]displaysallmessagesforthespecifieddateorrange ofdates(startingandendingdates,separatedbyahyphen).Specifydatesasnumeric stringsstartingwithatwodigityearfollowedbyatwodigitmonthandatwodigitday ofthemonth.Thedefaultis all. -r (--rescan-for-xray) rescansphysicaldevicesbeforeproceedingwiththexray. Bydefault,Xraydoesnotrescandevices. -o <filename> (--output-file=<filename>) suppliesafullyqualifiedpathand filenamefortheXrayoutput.Bydefault,outputfilesarenamed xray-YYYY-MM-DDhh-mm-<servername>.tar.gz. -f (--force) overwritestheexistingfileiftheoutputfilealreadyexists.Bydefault,X rayreturnsanerror.

266

VTL User Guide Mar 2008

F 96267

APPENDIX

Requiredports
Inordertomaintainahighlevelofsecurity,youshoulddisableallunnecessary ports.TheonlyportsrequiredbyVTLare:

TCPport11576UsedforVTLConsoletoVTLServermanagement communication. UDPport11577UsedforIPreplication. UDPport11578Usedforencryption. UDPport11579Usedforencryption. TCPport11580Usedforcommunicationbetweenafailoverpair. UDPport161UsedforSNMPtraps. TCPport161UsedforSNMPtraps. TCP/UDPport3205UsedforiSCSI. TCPport3260UsedforiSCSI.

AlthoughyoumaytemporarilyopensomeportsduringinitialsetupoftheVTL server,suchasthetelnetport(23)andFTPports(20and21),youshouldshutthem downafteryouhavedoneyourwork.

96267 F

267

268

VTL User Guide Mar 2008

F 96267

APPENDIX

Troubleshooting
Thisappendixaddressesthefollowingissues:

Problemsduringconsoleoperationsonpage 269 Problemsaffectingphysicalresourcesonpage 272 Problemswithvirtualresourcesonpage 273 Problemsduringimport/exportoperationsonpage 277 TakinganXrayfortechnicalsupportonpage 279

Problemsduringconsoleoperations
Issue: Indications:

VTLconsoleisunabletoconnecttoaVTLserver
TheVTLconsoledoesnotconnecttotheservernode.ThewordFailedappearsat duringtheconnectionprocess. Determinethecauseofthefailureusingthefollowingprocedure. Case:

Diagnostics:

Connectionfailsbeforelogin

1. Wait for a while. Then attempt to connect again. 2. If you can now connect, stop here. Theserverwasbusyandunabletorespondimmediately. 3. If the IP address of the server changed recently, delete the server from the VTL console. Then re-add it, and try to connect. 4. If you can now connect, stop here. TheVTLconsolewasstillusingtheoldIPaddress.

96267 F

269

5. If you still cannot connect, try to connect using the servers IP address instead of its server name (or vice versa). 6. If you can now connect, stop here. ThehostnameorIPaddressthatfailedmaybeincorrect. 7. If you still cannot connect, check network connectivity. Ping the target server and other machines in the same subnet. 8. If you cannot ping the server or the hosts on the same subnet, there is a network outage. Stop here, and correct the problem. Then reconnect to the VTL server. Case:

Connectionfailsduringlogin

1. Verify the user name and password. Thepasswordiscasesensitive.MakesuretheCapsLockkeyisnotpressedon thekeyboard 2. If the user name or password was incorrect, stop here, and log in using the correct credentials. 3. If the user name and password seem to be correct, make sure they exist on the server. From the machine where VTL console is installed, open a secure shell (ssh) session on the VTL server, and log on using the same user name and password as above. Notethatsshmaybedisablediflocalsecuritypoliciessorequire. 4. If ssh is enabled but you still cannot log in, the user name or password is probably incorrect. Stop here, and obtain proper credentials. 5. If you can log in using ssh, check the status of the VTL server software modules. From the ssh commandline, run the following command:
# ipstor status

6. If a module has stopped, restart it with the following command, and stop here.
# vtl restart <module name>

Case:

Connectionfailswhileretrievingtheserverconfiguration

1. If the connection fails while retrieving the server configuration, note any error messages that appear. 2. Then contact Sun technical support. Case:

ConnectionfailswhilecheckingtheVTLlicense

1. Contact Sun technical support.

270

VTL User Guide Mar 2008

F 96267

Case:

ConnectionfailswhileexpandingtheVTLservernode

1. Check the memory consumption on the console host. 2. If memory consumption is excessive, stop unnecessary processes, and retry. 3. If you can connect, stop here. Avoidrunningmemoryintensiveapplicationsonthishostwhentheconsoleisin use. 4. If you cannot connect or if memory consumption appears to be within normal limits, contact Sun technical support.

Issue: Indications:

RequestedoperationscannotbeperformedfromtheVTLconsole
TheserverexhibitssymptomsofhighCPUutilization,suchasServer Busy or RPCTimeoutmessages. DeterminewhetherhighCPUutilizationisnormal. 1. Check the Event Log or syslog (/var/adm/messages) for CPU-intensive activity on the server. Backupjobsthatbackuptomultiplevirtualorphysicaldevicesinparallel,data compression,andencryptionallplaceheavydemandsontheCPU. 2. If CPU-intensive processes are running on the server, stop here, and retry the console later. TheVTLserverisbehavingnormally. 3. If CPU-intensive processes are not running on the server, if the CPU is not actually busy, or if the problem persists, contact Sun technical support.

Diagnostics:

Issue: Indications: Diagnostics:

VTLconsoleoperationsareveryslow
TheVTLconsoleisabnormallysloworunresponsive. Determinethereason. Case:

Lowhostsystemmemory

1. Check memory utilization for all running processes on the host. 2. Stop unnecessary processes. 3. If no unnecessary processes are running, provide the host with more memory.

96267 F

Appendix C: Troubleshooting

271

Case:

Highserveractivity

1. Check the Event Log or syslog (/var/adm/messages) for CPU-intensive activity on the server. Backupjobsthatbackuptomultiplevirtualorphysicaldevicesinparallel,data compression,andencryptionallplaceheavydemandsontheCPU. 1. Also, try starting a second instance of the VTL console. If the second VTL console cannot establish connections, that means the server is busy with previous RPC operations. 2. If CPU-intensive processes are running on the server, stop here, and retry the console later. TheVTLserverisbehavingnormally. 3. If CPU-intensive processes are not running on the server, if the CPU is not actually busy, or if the problem persists, contact Sun technical support.

Problemsaffectingphysicalresources
Issue: Indications: Diagnostics:

TheVTLconsoledoesnotdisplaysomephysicalstoragedevices
Theconsoledoesnotdisplayallexpectedphysicaldevices. Checktoseeifthedevicesarepresentandaccessible. 1. Rescan physical devices from the VTL console by right-clicking on Physical Resources and selecting Rescan from the context menu. Make sure that Discover New Devices is specified. Specify a LUN Range that you reasonably expect will include the device. 2. If the console now displays the missing devices, stop here. 3. If rescanning does not detect the missing devices, check the system Event Log or syslog (/var/adm/messages) for error messages that may correspond to the rescan operation. Look for failed devices or errors that kept an otherwise discoverable device from being accessed. 4. If the logs reveal a device failure or error, stop here. Correct the device problem. 5. If the logs do not reveal the source of the problem, make sure that the VTL server is powered up and that all cable connectors are securely connected. 6. If the VTL server is not powered up or if cables are not connected, stop here. Correct the problem.

272

VTL User Guide Mar 2008

F 96267

7. If you have still not solved the problem, contact Sun technical support.

Problemswithvirtualresources
Issue: Indications: Diagnostics:

Virtualtapesareshownofflineintheconsole
Virtualtapesareoffline. Locatethephysicalresourcesthatbackthevirtualtapesandassesstheirstate. 1. Identify the physical resources that back the virtual tapes. In the Virtual Tape Library System branch of the VTL object tree, highlight the branch representing the offline virtual tape, select the Layout tab from the property sheet at right, and note the identifying information for the disk that corresponds to the offline tape. 2. In the Physical Resource branch, under the Storage Devices > Fibre Channel Devices, locate the physical resources that you identified in the preceding step. Make sure that each physical device is present, operating normally and accessible. 3. If physical devices appear to be missing, inaccessible, or failing, contact Sun technical support.

Issue: Indications: Diagnostics:

Tapeexpansiondoesnotwork
Thesizeofvirtualtapecannotbeexpanded. Determinethecause. 1. In the Virtual Tape Library System branch of the VTL object tree, highlight the tape in the console, and make sure that the Total Size field is accurate. 2. If the Total Size field is accurate, make sure that client machine has been refreshed to see the updated virtual resource. Rescan devices. Theexpansionhassucceeded,buttheclientmachinedoesnotyetseethenewsize oftheexpandeddevice. 3. If rescanning resolves the problem, stop here. 4. If the Total Size field is accurate or if the problem persists after a rescan, check the Event Log for error messages. Theexpansionprobablyfailed.

96267 F

Appendix C: Troubleshooting

273

5. If you find disk space errors, there may not be enough physical disk space for the expansion. Add more physical storage or change the size of expansion. Then retry. 6. If no disk space problems were found, or if correcting them does not solve the problem, make sure that the physical storage partition is valid. Correct any problems, and retry. 7. If the partition is valid or if correcting it does not solve the problem, look for I/O errors. 8. If I/O errors are found, consult technical support. 9. Otherwise, look for an RPC timeout during execution of the expand command. See if the server is busy by running the top or ps x command on the VTL server. 10. If the server seems excessively busy, stop any unnecessary processes, and retry the expansion operation. 11. If the problem persists or if the event logs show no obviously relevant errors, contact technical support.

Issue: Indications: Diagnostics:

Clientcannotseetapelibrary/drivesprovisionedbyVTL
Aclientoperatingsystemorapplicationdoesnotcorrectlydetectvirtualdevices. Furthercharacterizetheproblem,anddeterminethecause. Case:

Neithertheoperatingsystemnorapplicationsappeartoseethedevice

1. See if the operating system includes the device in its configuration.

OnSunSolarisplatforms,tapelibrariesareusuallyshownintheform /dev/sg<index>,ifthesgmoduleisloaded.Tapedrivesaredisplayed intheform /dev/rmt/<index>,ifthestmoduleloaded. OnLinuxplatforms,tapelibrariesareusuallyshownintheform /dev/sg<index>,assumingthatthesgmoduleisloaded.Tapedrives aredisplayedintheform/dev/st/<index>,/dev/nst/<index>, and /dev/sg/<index>,ifthestmoduleloaded. OnMicrosoftWindowsplatforms,tapelibrariesappearunderMedia ChangersandtapedrivesunderTape drives.Usuallythetapedriveis representedas\tape<index>. HPUXrepresentstapelibrarieswithastringoftheform /dev/rac/cXtXdX,iftheschgrdriverisloaded.Tapedrivesare representedby /dev/rmt/<index>,ifthestapedriverisloaded. AIXdisplaystapedevicesas /dev/rmt<index>(forLTO1/LTO2)or /dev/mt<index>(forDLT/SDLT).

2. If the operating system does not show the device, got to The operating system cannot detect the device on page 275.

274

VTL User Guide Mar 2008

F 96267

3. If the operating system does show the device, go to Applications cannot see the device on page 275. Case:

Theoperatingsystemcannotdetectthedevice

1. If the operating system does not see the device, use the VTL console to check the status of the virtual device. 2. If the virtual device is offline, stop here, and go to Virtual tapes are shown offline in the console on page 273. 3. If the virtual device is online, check the client configuration. In the VTL console, right-click on the client, and examine the Resources tab of the properties sheet in the right-hand pane. 4. If you do not see virtual devices on the Resources tab, assign devices to the client.Make sure that devices that are shared by clients attach in Read/Write non-exclusive mode. On the client, rescan devices. 5. If the client can see the devices after rescanning, stop here. 6. If the client cannot see its assigned devices, check World Wide Port Names (WWPNs). In the VTL console, right-click on the client, and select Properties from the context menu. Record the initiator and target WWPNs. 7. Select the Physical Resources object and locate the HBA that corresponds to the recorded target WWPN. In the property sheet at right, select the SNS table tab and look up initiator WWPN that you recorded in the previous step. If multiple HBAs exist, either from the client host or from the VTL target, look up all entries from all target SNS tables. 8. If the VTL console does not record the correct initiator WWPN, unassign the client and the reassign it using the correct mapping. On the client, rescan devices. 9. If the client can see the devices after rescanning, stop here. Case:

Applicationscannotseethedevice

1. If an application fails to find the device, see The backup application cannot see the device at all on page 275. 2. If an application finds the device in an unexpected location, see The backup software does not see the device in the expected place on page 276. Case:

Thebackupapplicationcannotseethedeviceatall

1. If the operating system sees the device but a backup application does not, check the drivers for the backup software. Make sure the driver is appropriate for the library and tape drive type.

96267 F

Appendix C: Troubleshooting

275

2. If a driver appears to be inappropriate, refer to the backup software manual. Some backup products recommend specific versions of drivers or special settings. Apply the correct driver. 3. If changing the driver solves the problem, stop here. 4. If the recommended driver is installed or if installing it did not help, check the driver version and upgrade as necessary. 5. If upgrading the driver solves the problem, stop here. 6. If the driver is correctly versioned or if upgrading the driver does not help, look for application software conflicts. Multiple backup products on a single server can cause this sort of problem. Case:

Thebackupsoftwaredoesnotseethedeviceintheexpectedplace

1. If the operating system correctly recognizes the device, but the backup software does not see the device in the expected place, suspect a serialization error in the application. Consult the application vendor and documentation, and install applicable software patches or upgrades. Serializationconvertsobjectsintostreamsofsequentialobjectproperties.Ifthe applicationmisinterpretsthesequence,itmayconfusepropertiessuchas ownership.

Issue: Indications: Diagnostics:

Clientseesthetapelibrary/drivebutcannotaccessit
Aclientoperatingsystemorapplicationcannotaccessvirtualdevices. Furthercharacterizetheproblem,anddeterminethecause. Case:

Neithertheoperatingsystemnorapplicationsappeartohaveaccess
MicrosoftWindowsclientscanuse ntutiltocheckemulatedIBMUltrium devices. UNIXsystemscanusethe mtor tarcommandtoaccessthetapedevice (usingasyntaxlike mt -f /dev/rmt/0 status).

1. Obtain an operating system-specific raw device utility that can access tape drives.

2. Stop the backup application. 3. Using the VTL console, load a tape into a virtual drive. Whilemostrawdeviceutilitiesworkwithtapedrives,theycannot,inmostcases, loadtapes.Evenifsomecanmovetapes,youneedtoknowtheexactaddressof thetapeandthedrive. 4. Attempt to access the device using the raw utility.
276 VTL User Guide Mar 2008 F 96267

5. If you cannot access the device, go to The operating system cannot access the device on page 277. 6. If you can access the device, go to The operating system can access the device. on page 277. Case:

Theoperatingsystemcannotaccessthedevice

1. If the operating system cannot access the device, make sure that physical storage resources are accessible and in read/write mode. 2. Check the Event Log or syslog (/var/adm/messages) for I/O errors. I/Oerrormessagesusuallybeginwith log_scsi_error. 3. Make sure that the adapter driver on the client is certified for use with VTL. Case:

Theoperatingsystemcanaccessthedevice.

1. If the operating system can access the device, the backup software is causing the problem. Consult the application documentation and/or application vendor customer support. 2. Make sure that you have the correct drivers.

Problemsduringimport/exportoperations
Issue: Indications: Diagnostics:

Import/Exportdoesnotworkasexpected
Import/exportoperationsfailorresultinunexpectedbehavior. Determinethecause. Case:

Tapedevicesand/ormediatypesaremismatched

1. Make sure that you are importing from or exporting to the same type of media and device. Youcanonlyimportandexportdatabetweenaphysicaltapedeviceandavirtual tapedeviceofthesametype,usingphysicalandvirtualmediaofthesame capacity. 2. If dissimilar physical and virtual devices or media are being used, stop here. Correct the condition, and retry the import/export job. 3. If physical and virtual devices are identical or if making them so does not solve the problem, see if compressed data is being imported/exported.

96267 F

Appendix C: Troubleshooting

277

4. If compressed data is being imported/exported, make sure that virtual and physical media have the same uncompressed capacity. Import/exportoperationsfailifthetargetmediadoesnothaveenoughcapacityto accommodatedecompresseddata. 5. If compression is not an issue, see The export/import job is not complete on page 278. Case:

Theexport/importjobisnotcomplete

1. If dissimilar media capacity is not the problem, make sure that the job is not still running. In the VTL console, select the Import/Export Queue, and search for related export/import jobs. 2. If a related job is found, the job is not yet complete. Stop here, and recheck it later. Jobsareonlylistedinthequeuewhileactive,solistedjobsarestillrunning. 3. If related jobs are not listed in the queue or if the problem persists after the job completes, use the VTL console to examine the Event Log for failure messages. 4. If failure messages are found, stop here, correct the error condition(s), and retry the import/export job. 5. If the problem persists, see Virtual tape barcodes duplicate physical tape barcodes on page 278. Case:

Virtualtapebarcodesduplicatephysicaltapebarcodes

1. If export/import problems persist, make sure that virtual and physical tapes each have their own, unique barcodes. Use the VTL console to Inventory the physical library, and check the results against the virtual tapes. 2. If duplicates are found, stop here. Correct the situation, and retry the import/export operation. 3. Otherwise, see A physical tape library or device is not ready on page 278. Case:

Aphysicaltapelibraryordeviceisnotready

1. Check the status of physical tape drives. 2. If physical tape drives require cleaning, clean them, and stop here. Retry the import/export operation. 3. If cleaning is unnecessary or does not help, see if physical tapes need to be moved and mounted before the import/export operation can continue. 4. If tapes have to be moved, move them, and stop here. Retry the import/export operation. 5. If tapes do not need to be moved, check for other anomalous conditions.

278

VTL User Guide Mar 2008

F 96267

6. It other anomalous conditions are found, correct them, and stop here. Retry the import/export operation. 7. If problems persist, see VTL drive assignments do not reflect library element addresses on page 279. Case:

VTLdriveassignmentsdonotreflectlibraryelementaddresses

1. When you import data, make sure the assignment of drive in VTL follows the element address of the drives in the physical library. Assign the tape drive in the order of their element address. 2. If VTL assigns drives out of element order, unassign and reassign tape drives in the correct order. Stop here, and retry the import/export operation. 3. If drive order is not an issue or if correcting it fails to resolve the problem, see Some other system error is causing the problem on page 279. Case:

Someothersystemerroriscausingtheproblem

1. If problems persist after other possibilities have been exhausted, examine the VTL Event Log or the server syslog (/var/adm/messages) for error messages that relate to the physical tape library or drive. 2. If you find error messages, correct the issues if possible. Stop here, and retry the import/export operation. 3. If you cannot find relevant errors or cannot determine a cause or resolution for an error condition, contact Sun technical support.

TakinganXrayfortechnicalsupport
If,duringatechnicalsupportcall,aSuntechnicalsupportrepresentativeasksyouto takeanXRayofyoursystem,notetheitemsthatyouneedtoinclude.Thenproceed asfollows.

96267 F

Appendix C: Troubleshooting

279

TakinganXRay
1. IntheobjecttreeoftheVTLconsole,rightclickonthebranchrepresentingthe VTLserver(A below),andselectX-Rayfromthecontextmenu(B).

280

VTL User Guide Mar 2008

F 96267

2. WhentheX-Ray Optionsdialogappears,checkthecheckboxescorrespondingto theitemsthatyouneedtoinclude(C below). Thedefaultsareshownbelow:

D E

IfyouselecttheLog Fileoption,youcanfiltertheoutputbyspecifyinganumber ofrecordsoradaterange.YoucanlimittheresultstoVTLsystemrelatedmessages bycheckingtheVTL Messages Onlycheckbox. 3. IntheSave Astextbox(D above),specifyanoutputpathandfilenameforthe XRayarchive. 4. XRaysaresavedasgzippedtararchives. 5. PressTake X-Ray(E above)togeneratetheoutput.

96267 F

Appendix C: Troubleshooting

281

282

VTL User Guide Mar 2008

F 96267

APPENDIX

SNMPtraps
TheVTLproductfamilydefinesthefollowingSimpleNetworkManagement Protocol(SNMP)traps.

Trap

Severity

Message

9 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015

Error Error Error Error Informational Informational Error Error Error Error Informational Informational Error Error Informational Informational Informational

SCSI Port Error -- %1. Socket connection could not be terminated properly -- %1. Socket connection could not be terminated properly due to error during shutdown -- %1. Unexpected interrupt occurred. "VTL Server has detected virtual device[%1] at SCSI %2, channel %3, ID %4, LUN %5." VTL Server has not detected any virtual device. Out of kernel resources. Failed to get major number for VTL SCSI device. Failed to allocate memory. Failed to set up the network connection due to an error in SANRPC_Init -- %1. Failed to set up the network connection due to an error in SANRPCListen -- %1. There are %1 real device(s) associated with virtual device [%2].

Real Device[%1 %2 %3 %4]. Error while writing -- write(%1) result = 0x%2 cmd = 0x%3. Error while reading -- read(%1) result = 0x%2 cmd = 0x%3. VTL Server [Build %1] is running on Linux %2. VTL Server has been shut down. "Maximum SCSI devices reached. command: cat /proc/scsi/scsi" On your VTL Server, verify with the

96267 F

283

Trap

Severity

Message

1016 1017 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1034 1035 1038 1039 1040 1041 1042

Informational Informational Informational Informational Warning Error Informational Informational Informational Informational Informational Informational Error Error Error Error Error Error Error Error Informational Informational

Primary virtual device %1 has failed. VTL is switching to the secondary virtual device. Secondary virtual device %1 has failed. Replication for virtual tape %1 started. Replication for virtual tape %1 finished. Replication has failed for virtual tape %1 -- %2. Failed to connect to physical device %1. Switching alias to %2. Device %1 has attached to the VTL Server. Device %1 has detached from the VTL Server. Replication has been started for virtual tape %1; it was triggered by the watermark. Replication has been started for virtual tape %1; it was triggered by the interval schedule. Replication has been started for virtual tape %1; it was triggered by the time of day schedule. Replication has been started for virtual tape %1; it was manually triggered by the administrator. Failed to start replication -- replication is already in progress for virtual tape %1. Failed to start replication -- replication control area not present on virtual tape %1. Failed to start replication -- replication control area has failed for virtual tape %1. Replication failed for virtual device %1 -- the network transport returned error %2. Replication failed for virtual device %1 -- the local disk failed with error %2. Replication failed for virtual device %1 -- the local server could not allocate memory. Replication failed for virtual device %1 -- the replica failed with error %2. Replication failed for virtual device %1 -- failed to set the replication time. Mirror synchronization started for virtual device %1. Mirror synchronization finished for virtual device %1.

284

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

1043

Error

A SCSI command terminated with a non-recoverable error condition that was most likely caused by a flaw in the medium or an error in the recorded data. Please check the system log for additional information. "A SCSI command terminated with a non-recoverable hardware failure (for example, controller failure, device failure, parity error, etc.). Please check the system log for additional information." Rescan replica has completed for virtual device %1 Rescan replica has failed for virtual device %1 -- the local device failed with error %2. Rescan replica has failed for virtual device %1 -- the replica device failed with error %2. Rescan replica has failed for virtual device %1 -- the network transport returned error %2. Rescan replica cannot proceed -- replication control area not present on virtual device %1 Rescan replica cannot proceed -- replication control area has failed for virtual device %1 Rescan replica cannot proceed -- a merge is in progress for virtual device %1 Rescan replica failed for virtual device %1 -- replica status returned %2 Rescan replica cannot proceed -- replication is already in progress for virtual device %1 Replication cannot proceed -- a merge is in progress for virtual device %1 Replication failed for virtual tape %1 -- replica status returned %2 Replication control area exchange failed for virtual tape %1 -- the error code is %2 Replication control area exchange has completed for virtual tape %1 Replication has finished for virtual tape %1. %2 KB in %3 seconds (%4KB/sec) Replication failed for virtual tape %1 -- start replication returned %2 Rescan replica failed for virtual device %1 -- start scan returned %2 I/O path failure detected. Alternate path will be used. Failed path (A.C.S.L): %1; New path (A.C.S.L): %2

1044

Error

1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061

Informational Error Error Error Error Error Error Error Error Error Error Error Informational Informational Error Error Warning

96267 F

Appendix D: SNMP traps

285

Trap

Severity

Message

1062 1063 1064 1065 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1079 1082 1083 1084

Informational Informational Informational Informational Error Error Error Error Error Error Error Error Error Informational Informational Error Error Error Error

Replication has been started for group %1; it was triggered by the watermark. Replication has been started for group %1; it was triggered by the interval schedule. Replication has been started for group %1; it was triggered by the time of day schedule. Replication has been started for group %1; it was manually triggered by the administrator. Replication cannot proceed -- unable to connect to replica server %1. Replication cannot proceed -- group %1 is corrupt. Replication cannot proceed -- virtual tape %1 no longer has a replica or the virtual tape replica does not exist. Replication cannot proceed -- replication is already in progress for group %1. Replication cannot proceed -- virtual tape %1 no longer has a replica or the virtual tape replica does not exist. Replication cannot proceed -- missing a remote replica device in group %1. Replication cannot proceed -- unable to open configuration file. Replication cannot proceed -- unable to allocate memory. Replication cannot proceed -- unexpected error %1. Starting replication for virtual device %1 of group %2 to replica device %3. Replication for group %1 has completed successfully. Replication for group %1 has failed due to error on virtual device %2 Replication for virtual tape %1 has been manually aborted by user Replication for group %1 has been manually aborted by user A SCSI command terminated with a recovered error condition. This may indicate that the device is becoming less reliable. Please check the system log for additional information. for virtual device %1 has been auto-disabled due to an error. Replication cannot proceed -- failed to load the virtual tape %1. Replication cannot proceed -- virtual tape %1 is in the drive.

1085 1086 1087

Error Error Error

286

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

1088 1089 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 2000 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 10000

Error Informational Warning Informational Error Error Informational Error Error Warning Informational Warning Warning Warning Informational Error Informational Informational Error Error Error Warning Error Error Informational Warning Error Informational

Replication cannot proceed -- failed to set initialization status in VirtualLibrary System for virtual tape %1. No data has been updated to the virtual tape %1 since last replication. Replication is completed without updating the replica. Kernel memory is low. Add more memory to the system if all possible! Restart the host if possible. Path trespassed to %1 successfully. Path failed to trespass to %1. Failed to add path group. ACSL: %1. Activated path successfully: %1. Failed to activate path: %1. Critical path failure detected. Path %1 will be removed. Path %1 does not belong to active path group. Rescan the FC adapters is recommended to correct the configuration. No valid path is available for device %1. No valid group is available. "No active path group found. Storage connectivity failure. Check cables, switches and storage system to determine cause. GUID: %1." Storage device added new path: %1. Failed to add path: %1. Path status has changed : %1 Patch %1 installation completed successfully. Patch %1 failed -- environment profile is missing in /etc. Patch %1 failed -- it applies only to build %2. Patch %1 failed -- you must be the root user to apply the patch. Patch %1 installation failed -- it has already been applied. Patch %1 installation failed -- prerequisite patch %2 has not been applied. Patch %1 installation failed -- cannot copy new binaries. Patch %1 rollback completed successfully. Patch %1 rollback failed -- there is no original file to restore. Patch %1 rollback failed -- cannot copy back previous binaries. VTL Server setup has begun.

96267 F

Appendix D: SNMP traps

287

Trap

Severity

Message

10001 10002 10003 10004 10005 10006 10007 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10100 10101 10102 10200 10201 10202 10206 10207 10208 10209 10210

Error Error Error Error Error Error Informational Informational Informational Informational Informational Error Informational Informational Informational Informational Error Informational Error Error Error Warning Warning Informational Informational Error Informational Error Warning

Insufficient privilege (uid: %1). VTL Server environment is corrupt. Failed to initialize configuration %1. Failed to get SCSI device information. A physical device will not be available because we cannot create a Global Unique Identifier for it. Failed to write configuration %1. VTL Server setup is complete. VTL Server FSID update has begun. "VTL Server FSID update vdev %1, local sect %2, pdev sect %3, from %4 to %5." "VTL Server FSID update pdev a:%1, c:%2, s:%3, l:%4 from %5 to %6." VTL Server FSID update dynamic xml pdev from %1 to %2. VTL Server FSID update error. VTL Server FSID update is complete. Server Persistent Binding update has begun. "Server Persistent Binding update, swap binding %1." "Server Persistent Binding update, set default binding for %1." Server Persistent Binding update error. "Server Persistent Binding update is complete, %1 changes." Failed to scan new SCSI devices. Failed to update configuration %1. Failed to add new SCSI devices. Configuration %1 exists. Overwriting existing configuration %1. Cancelled overwriting configuration %1. Add scsi alias=%1. "Add Adapter %1 failed, not enough memory." "Set Adapter %1 offline, adapter count %2." "Add Physical Device %1 failed, not enough memory." Marked Physical Device [%1] OFFLINE because its GUID: %2 does not match scsi GUID: %3.

288

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

10211 10212 10213 10214 10215 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10496 11000 11001 11002 11003 11004 11005 11006

Warning Warning Warning Warning Warning Error Error Error Error Error Error Error Error Warning Warning Warning Warning Error Error Error Error Error Error Informational Error

"Marked Physical Device [%1] OFFLINE because its wwid %2 does not match scsi wwid %3, [GUID: %4]." "Marked Physical Device [%1] OFFLINE because scsi status indicate OFFLINE, [GUID: %2]." "Marked Physical Device [%1] OFFLINE because it did not respond correctly to inquiry, [GUID: %2]." "Marked Physical Device [%1] OFFLINE because its GUID is an invalid FSID, [GUID: %2]." "Marked Physical Device [%1] OFFLINE because its storage capacity has changed, [GUID: %2]." Missing SCSI Alias %1. Physical Adapter %1 could not be located in /proc/scsi/. Duplicate Physical Adapter number %1 in /proc/scsi/. Physical Device data structure is null. "Invalid FSID, device %1 - the LUN byte (4th byte) in FSID %2 does not match actual LUN." "Invalid FSID, Generate FSID %1 does not match device acsl:%2 GUID %3." "Fail to generate FSID for device acsl:%1, cant validate FSID." "Device (acsl:%1) GUID is blank, cant validate FSID." Remove all scsi alias from %1. Remove missing scsi alias %1 from %2. Remove scsi alias %1 from %2 because their categories are different. Remove scsi alias %1 from %2 because their GUIDs are different. Failed to attach tle repository. Failed to create socket. Failed to set socket to re-use address. Failed to bind socket to port %1. Failed to create TCP service. "Failed to register TCP service (program: %1, version: %2)." VTL communication module started. VTL communication module failed to start.

96267 F

Appendix D: SNMP traps

289

Trap

Severity

Message

11007

Warning

There is not enough disk space available to successfully complete this operation and maintain the integrity of the configuration file. There is currently %1 MB of disk space available. VTL requires %2 MB of disk space to continue. Changed server time to %1. Auto save configuration enabled: ftp_server=%1 directory=%2 interval=%3 copies=%4. Auto save configuration enabled: ftp_server=%1 port=%2 directory=%3 interval=%4 copies=%5. Auto save configuration disabled. Auto save configuration: cannot setup crontab. Auto save configuration: cannot create the running script %1. Auto save configuration: cannot connect to ftp server %1 port %2. Auto save configuration: cannot login user %1. Auto save configuration: directory %1 doesnt exist. Auto save configuration: failed to copy %1 to ftp server. Auto save configuration: failed to delete old file %1 from ftp server. Automated Tape Caching is %1 for virtual library %2. SAN Client (%1): SAN Client added. SAN Client (%1): Failed to add SAN Client. SAN Client (%1): Authentication succeeded. SAN Client (%1): Authentication failed. Too many SAN Client connections. SAN Client (%1): Logged in. SAN Client (%1): Failed to log in. SAN Client (%1): Illegal access. SAN Client (%1): Logged out. SAN Client (%1): Failed to open file %2. SAN Client (%1): Failed to get hostname. SAN Client (%1): Failed to resolve hostname %2. SAN Client (%1): Failed to parse configuration file %2. SAN Client (%1): Failed to restart authentication module.

11010 11020 11021 11022 11030 11031 11032 11033 11034 11035 11036 11037 11100 11101 11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113

Informational Informational Informational Informational Error Error Error Error Error Error Error Informational Informational Error Informational Error Error Informational Error Error Informational Error Error Error Error Error

290

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

11114 11115 11170 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224 11225

Error Error Error Error Error Error Error Error Error Error Error Error Error Informational Error Error Error Error Error Error Error Error Error Error Error Error Informational Informational Informational

SAN Client (%1): Failed to allocate memory. "SAN Client (%1): License conflict -- Number of CPUs approved: %2, number of CPUs used: %3." Failed to virtualize LUN %1 because of mismatching size between configuration file and disk. Please do rescan and try it again. Buffer overflow. Too many Console connections. Console (%1): Illegal access. Console (%1): SCSI device re-scanning has failed. Console (%1): SCSI device checking has failed. Console (%1): Failed to get information for file %2. Console (%1): Failed to allocate memory. Console (%1): Failed to open file %2. Console (%1): Failed to read file %2. Console (%1): Insufficient privilege access. Console (%1): Physical SCSI devices have changed. Console (%1): Failed to save file %2. Console (%1): Failed to create index file %2 for Event Log. Console (%1): Illegal time range (%2 - %3) for Event Log. Console (%1): Failed to get Event Log (%2 - %3). Console (%1): Failed to open directory %2. Console (%1): Out of system resources. Failed to fork process. Console (%1): Failed to execute program %2. Console (%1): Failed to remove file %2. Console (%1): Failed to add device %2. Console (%1): Failed to remove device %2. Console (%1): Failed to add SAN Client (%2) to virtual device %3. Console (%1): Failed to remove SAN Client (%2) from virtual device %3. Console (%1): Logged in with read/write privileges. Console (%1): Logged in with read only privileges. Console (%1): Logged out.

96267 F

Appendix D: SNMP traps

291

Trap

Severity

Message

11226 11227 11228 11229 11230 11231 11232 11233 11234 11235 11236 11237 11238 11239 11240 11241 11242 11243 11244 11245 11246 11247 11248 11249 11250 11251 11252 11253 11254 11255

Informational Informational Informational Informational Informational Error Error Error Error Error Error Error Error Informational Error Informational Error Informational Error Error Informational Error Informational Error Informational Error Informational Error Informational Error

Console (%1): Configuration file %2 saved. Console (%1): Virtual device %2 added. Console (%1): Virtual device %2 removed. Console (%1): SAN Client (%2) added to virtual device %3. Console (%1): SAN Client (%2) removed from virtual device %3. Console (%1): Failed to get CPU status. Console (%1): Failed to get memory status. Console (%1): Failed to map the SCSI device name for [%2 %3 %4 %5]. "Console (%1): Failed to execute ""hdparm"" for %2." Console (%1): Failed to get the VTL Server module status. Console (%1): Failed to get the version information for the message file. Console (%1): Failed to get file %2. Console (%1): Failed to restart the authentication module. Console (%1): Authentication module restarted. Console (%1): Failed to start the VTL Server module. Console (%1): VTL Server module started. Console (%1): Failed to stop the VTL Server module. Console (%1): VTL Server module stopped. Console (%1): Failed to access the VTL administrator list. Console (%1): Failed to add user %2. Console (%1): User %2 added. Console (%1): Failed to delete user %2. Console (%1): User %2 deleted. Console (%1): Failed to reset password for user %2. Console (%1): Password for user %2 reset. Console (%1): Failed to update password for user %2. Console (%1): Password for user %2 updated. Console (%1): Failed to modify virtual device %2. Console (%1): Virtual device %2 modified. Console (%1): Failed to modify virtual device %3 for SAN Client (%2).

292

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

11256 11257 11258 11259 11260 11261 11262 11263 11264 11265 11266 11267 11268 11269 11270 11271 11272 11273 11274 11275 11276 11277 11278 11279 11280 11281 11282 11283 11284

Informational Error Informational Error Informational Error Error Error Informational Error Error Informational Error Error Error Informational Error Informational Error Informational Error Informational Error Informational Error Informational Error Informational Error

Console (%1): Virtual device %3 for SAN Client (%2) modified. Console (%1): Failed to add SAN Client (%2). Console (%1): SAN Client (%2) added. Console (%1): Failed to delete SAN Client (%2). Console (%1): SAN Client (%2) deleted. Console (%1): Failed to get SAN Client connection status for virtual device %2. Console (%1): Failed to parse configuration file %2. Console (%1): Failed to restore configuration file %2. Console (%1): Configuration file %2 restored. Console (%1): Failed to restart IOCore module. Console (%1): Failed to erase partition of virtual device %2. Console (%1): Virtual device %2 partition erased. Console (%1): Failed to update meta information of virtual device %2. Console (%1): Failed to get ID for SAN Client (%2). Console (%1): Failed to add mirror for virtual device %2. Console (%1): Mirror added for virtual device %2. Console (%1): Failed to remove mirror for virtual device %2. Console (%1): Mirror removed for virtual device %2. Console (%1): Failed to stop mirroring for virtual device %2. Console (%1): Mirroring stopped for virtual device %2. Console (%1): Failed to start mirror synchronization for virtual device %2. Console (%1): Mirror synchronization for virtual device %2 started. Console (%1): Failed to swap mirror for virtual device %2. Console (%1): Mirror swapped for virtual device %2. Console (%1): Failed to create shared secret for VTL Server %2. Console (%1): Shared secret created for VTL Server %2. Console (%1): Failed to change device category for physical device %2 to %3. Console (%1): Device category changed for physical device %2 to %3. Console (%1): Failed to get raw device name for physical device %2.

96267 F

Appendix D: SNMP traps

293

Trap

Severity

Message

11285 11286 11287 11288 11289 11290 11291 11292 11293 11294 11295 11296 11297 11298 11300 11301 11302 11303 11304 11305 11306 11307 11308 11309 11310 11311 11312 11313 11314

Error Informational Error Informational Error Informational Error Error Informational Error Error Error Informational Error Error Error Error Error Informational Informational Error Error Error Error Error Error Informational Error Informational

Console (%1): Failed to execute failover command (%2). Console (%1): Failover command executed (%2). Console (%1): Failed to set failover mode (%2). Console (%1): Failover mode set (%2). Console (%1): Failed to restart VTL Server module. Console (%1): VTL Server module restarted. Console (%1): Failed to update meta information of physical device %2. Console (%1): Failed to swap IP address from %2 to %3. Console (%1): IP address swapped from %2 to %3. Console (%1): Failed to get host name. Console (%1): Invalid configuration format. Console (%1): Failed to resolve host name -- %2. Console (%1): Report file %2 removed. Console (%1): Failed to reset cache on target device %2 (ID: %3) for %4 copy. Invalid user name (%1) used by client at IP address %2. Invalid password for user (%1) used by client at IP address %2. Invalid passcode for machine (%1) used by client at IP address %2. Authentication failed in stage %1 for client at IP address %2. User %1 at IP address %2 authenticated. Machine %1 at IP address %2 authenticated. The VTL Administrator group does not exist. User %1 at IP address %2 is not a member of the VTL Administrators group. The VTL Client group does not exist. User ID %1 at IP address %2 is invalid. VTL Client User name %1 does not match with the client name %2. Client agent %1 failed to request license. Client agent %1 requested license successfully. Client agent %1 failed to release license. Client agent %1 released license successfully.

294

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

11400 11401 11402 11403 11404 11405 11406 11407 11408 11500 11501 11502 11503 11504 11505 11507 11508 11509 11510 11511 11512

Error Error Error Error Error Error Error Error Warning Error Error Error Informational Error Error Error Error Informational Error Error Error

Failed to communicate with the Self-Monitor module. Failed to release IP address %1. Failed to read %1. Failed to retrieve authentication information. Failed to merge authentication information. Failed to obtain IP address %1. Failed to prepare the failover configuration package -- %1. Failed to extract the failover configuration package -- %1. Synchronizing the system time with %1. A system reboot is recommended. Out of disk space to expand virtual tape %1. Failed to expand virtual tape %1: maximum segment exceeded (error code %2). Failed to expand virtual tape %1 (segment allocation error code %2). Expand %1 by %2 MBytes. Failed to expand virtual tape id %1 by %2 MBytes. Failed to change virtual tape %1 to direct link mode. Console (%1): Failed to create X-Ray file. Console (%1): Failed to set the properties for the VTL Server. Console (%1): Properties set for the VTL Server. Console (%1): Failed to save report -- %2. Console (%1): Failed to get the information for the NIC. "Console (%1): Failed to add a replica for virtual tape %2 to VTL Server %3 (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8)." "Console (%1): Replica for virtual tape %2 was added to VTL Server %3 (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8)." "Console (%1): Failed to remove the replica for virtual tape %2 from VTL Server %3 (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8)." "Console (%1): Replica for virtual tape %2 was removed from VTL Server %3 (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8)."

11513

Informational

11514

Error

11515

Informational

96267 F

Appendix D: SNMP traps

295

Trap

Severity

Message

11516 11517 11518 11519 11520 11521 11522 11523 11524 11525 11530 11531 11532 11533 11534 11535

Error Informational Error Informational Error Informational Error Informational Error Informational Error Informational Error Informational Error Error

Console (%1): Failed to create the virtual tape replica %2. Console (%1): Virtual tape replica %2 was created. Console (%1): Failed to start replication for virtual tape %2. Console (%1): Replication for virtual tape %2 started. Console (%1): Failed to stop replication for virtual tape %2. Console (%1): Replication for virtual tape %2 stopped. Console (%1): Failed to promote virtual tape replica %2 to a virtual tape. Console (%1): Virtual tape replica %2 promoted to a virtual tape. Console (%1): Failed to run VTL Server X-Ray. Console (%1): VTL Server X-Ray has been run. Console (%1): Failed to back up configuration files. Console (%1): Backed up Configuration files successfully. Console (%1): Failed to restore configuration files. Console (%1): Restored VTL configuration files successfully. Console (%1): Failed to reset the umap for virtual device %2. "Console (%1): Failed to update the replication parameters for virtual tape %2 to VTL Server %3 (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8)." "Console (%1): Replication parameters for virtual tape %2 to VTL Server %3 updated (watermark: %4 MB, time: %5, interval: %6, watermark retry: %7, suspended: %8)." Console (%1): Failed to claim physical device %2. Console (%1): Physical device %2 has been claimed. Console (%1): Failed to import physical device %2. "Console (%1): Host name mismatch (old: %2, new: %3)." Console (%1): Failed to save event message (ID: %2). Console (%1): Failed to remove virtual tape replica %2. Console (%1): Virtual tape replica %2 removed. Console (%1): Failed to modify virtual tape replica %2. Console (%1): Virtual tape replica %2 modified. Console (%1): Failed to mark the replication for virtual tape %2. Console (%1): Replication for virtual tape %2 is marked in sync.

11536

Informational

11537 11538 11539 11540 11541 11542 11543 11544 11545 11546 11547

Error Informational Error Error Error Error Informational Error Informational Error Informational

296

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

11548 11549 11550 11553 11554 11555 11560 11561 11562 11563 11564 11565 11566 11567 11568 11569 11570 11571 11572 11573 11574 11575 11576 11577 11578

Error Error Informational Error Error Informational Error Error Informational Error Informational Error Error Error Error Error Informational Error Error Informational Error Error Informational Error Error

Console (%1): Failed to determine if data was written to virtual device %2. "Console (%1): Failed to set option ""%2 %3.""" "Console (%1): Option ""%2 %3"" set." Console (%1): Failed to get login user list. Console (%1): Failed to set failover option <selfCheckInterval: %d sec>. Console (%1): Failover option <self check interval: %2 sec> has been set. Console (%1): Failed to get licenses. Console (%1): Failed to add license %2. Console (%1): License %2 added. Console (%1): Failed to remove license %2. Console (%1): License %2 removed. Console (%1): Failed to check licenses -- option mask %2. "Console (%1): License conflict -- Number of CPUs available: %2, number of CPUs used: %3." Console (%1): Failed to clean up failover server directory %2. Console (%1): Failed to set (%2) I/O Core for failover -- Failed to create failover configuration. Console (%1): Failed to set %2 to Fibre Channel mode %3. Console (%1): Set %2 to Fibre Channel mode %3. Console (%1): Failed to assign Fibre Channel device %2 to %3 (rolled back). Console (%1): Failed to assign Fibre Channel device %2 to %3 (not rolled back). Console (%1): Fibre Channel device %2 assigned to %3. Console (%1): Failed to unassign Fibre Channel device %2 from %3 (rolled back) and returns %4. Console (%1): Failed to unassign Fibre Channel device %2 from %3 (not rolled back) and returns %4. Console (%1): Fibre Channel device %2 unassigned from %3. Console (%1): Failed to get Fibre Channel target information. Console (%1): Failed to get Fibre Channel initiator information.

96267 F

Appendix D: SNMP traps

297

Trap

Severity

Message

11579 11580 11583 11584 11585 11586 11587 11588 11589 11592 11594 11595 11596 11597 11598 11599 11616 11617 11632 11633 11634

Error Informational Informational Informational Error Informational Error Informational Error Error Error Informational Error Informational Informational Informational Informational Informational Error Error Informational

Console (%1): Failed to set %2 to Fibre Channel authentication mode %3. Console (%1): Set %2 Fibre Channel Properties. Console (%1): Failed to update Fibre Channel client (%2) WWPNs. Console (%1): Fibre Channel client (%2) WWPNs updated. Console (%1): Failed to set Fibre Channel option %2. Console (%1): Set Fibre Channel option to %2. Console (%1): Failed to demote virtual device %2 to a replica. Console (%1): Virtual device %2 demoted to a replica. Authentication failed to connect to client %1 and returned %2. Console (%1): Failed to sync replication status for virtual tape %2 to the new target server. Console (%1): Failed to set CallHome option %2. Console (%1): Set CallHome option to %2. Console (%1): Failed to set hostedbackup option %2. Console (%1): Set hostedbackup option to %2. Console (%1): Failed to set hostedbackup option %2 because of conflicting adapter number %3. Console (%1): Set ndmp option to %2. Console (%1): Replication schedule for virtual tape %2 id %3 suspended. Console (%1): Replication schedule for virtual tape %2 id %3 resumed. "Console (%1): Failed to set failover option on secondary server <heartbeatInterval: %2 sec, autoRecoveryInterval: %3 sec>." "Console (%1): Failed to set failover option on secondary server <heartbeatInterval: %2 sec, autoRecoveryInterval: disabled>." "Console (%1): Failover option on secondary server <heartbeatInterval: %2 sec, autoRecoveryInterval: %3 sec> has been set." "Console (%1): Failover option on secondary server <heartbeatInterval: %2 sec, autoRecoveryInterval: disabled> has been set." Failed to get inquiry string on SCSI device %1. Failed to convert inquiry string on SCSI device %1.

11635

Informational

11648 11649

Error Error

298

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

11650 11651 11652 11653 11654 11655 11656 11657 11664 11666 11669 11674 11675 11680 11682 11685 11687 11689 11691 11693 11694 11695 11696 11699 11702 11703 11704 11705

Error Error Error Error Error Error Error Error Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Error Error Error Error Error Informational Informational Error Error

Failed to get capacity size for SCSI device %1. Medium Test failed for SCSI device %1. "Could not get type for SCSI device %1, because of inquiry string failure." "Discarded scsi device %1, unsupported type ""%2""." "Discarded scsi device %1, missing MTI vendor in inquiry string." "Discarded scsi device %1, bad capacity size." "Discarded scsi device %1, unsupported Cabinet ID." "Discarded scsi device %1, missing ""%2"" vendor in inquiry string." Console (%1): Enable backup for virtual device %2. Console (%1): Disable backup for virtual device %2. Console (%1): Stopped active backup sessions for virtual device %2. Console (%1): Virtual tape %2 is in replication session. Console (%1): Virtual device %2 is in backup session. Console (%1): Cache resource %2 (ID: %3) resumed successfully. Console (%1): Cache resource %2 (ID: %3) suspended successfully. Console (%1): %2 Resource %3 (ID: %4) added successfully. Console (%1): %2 Resource %3 (ID: %4) deleted successfully. Console (%1): Console (%1): Console (%1): successfully. resource %2 (ID: %3) resumed successfully. resource %2 (ID: %3) suspended successfully. policy for resource %2 (ID: %3) updated resource %2 (ID: %3).

Console (%1): Failed to update policy for Console (%1): Failed to get Console (%1): Failed to get

statistic information. status.

Console (%1): Failed to get port mapping for adapter no %2 persistent binding. VirtualTape Library Emulation option was enabled successfully. VirtualTape Library Emulation option was disabled successfully. Console (%1): The configuration file update for %2 %3(s) was rolled back. Console (%1): The disk partition update for %2 %3(s) was rolled back.

96267 F

Appendix D: SNMP traps

299

Trap

Severity

Message

11706 11707 11708 11709 11710 11711 11712 11713 11714 11715 11716 11717 11718 11719 11720 11721 11722 11723 11724 11725 11726 11727 11728 11729

Error Error Informational Error Error Error Error Informational Error Error Error Error Informational Error Error Error Error Informational Error Error Error Error Informational Error

Console (%1): The device creation for %2 %3(s) was rolled back. Console (%1): Failed to create %2 %3(s). Error: %4. Console (%1): %2 %3(s) created successfully. Console (%1): The configuration file update for replication setup for %2 %3(s) was rolled back. Console (%1): The disk partition update for replication setup for %2 %3(s) was rolled back. Console (%1): The replication setup for %2 %3(s) was rolled back. Console (%1): Failed to configure replication for %2 %3(s). Error: %4. Console (%1): Replication for %2 %3(s) configured successfully. Console (%1): The configuration file update for replication removal for %2 %3(s) was rolled back. Console (%1): The disk partition update for replication removal for %2 %3(s) was rolled back. Console (%1): The replication removal for %2 %3(s) was rolled back. Console (%1): Failed to remove replication for %2 %3(s). Error: %4. Console (%1): Replication for %2 %3(s) removed successfully. Console (%1): The configuration file update for deleting %2 %3(s) was rolled back. Console (%1): The disk partition update for deleting %2 %3(s) was rolled back. Console (%1): The deletion of %2 %3(s) was rolled back. Console (%1): Failed to delete %2 %3(s). Error: %4. Console (%1): %2 %3(s) are deleted successfully. Console (%1): The configuration file update for promoting %2 %3(s) was rolled back. Console (%1): The disk partition update for promoting %2 %3(s) was rolled back. Console (%1): The promotion of %2 %3(s) was rolled back. Console (%1): Failed to promote %2 %3(s). Error: %4. Console (%1): %2 %3(s) are promoted successfully. Console (%1): Failed to update replication properties for %2 %3(s). Error: %4.

300

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

11730 11731 11732 11733 11734 11735 11736 11737 11738 11739 11740 11750 11751 11780 11781 11782 11783 11788 11791 11792 11793 11794 11795 11900 11901

Informational Error Informational Informational Error Error Error Informational Error Error Error Informational Informational Informational Informational Error Error Error Error Informational Warning Informational Informational Error Error

Console (%1): Replication properties for %2 %3(s) are updated successfully. Console (%1): Failed to update replica properties for %2 %3(s). Error: %4. Console (%1): Replica properties for %2 %3(s) are updated successfully. Console (%1): Virtual library %2 created successfully. Console (%1): The configuration file update for virtual library creation was rolled back. Console (%1): Adding virtual library to the system was rolled back. Console (%1): Failed to create virtual library. Error: %2. Console (%1): %2 virtual tape drives created successfully. Console (%1): The configuration file update for virtual drive creation was rolled back. Console (%1): Adding virtual tape drives to the system was rolled back. Console (%1): Failed to create virtual tape drives. Error: %2. Console (%1): Add VirtualTape Library Emulation option successfully. Console (%1): Remove VirtualTape Library Emulation option successfully. Tape id %1 [%2] is enabled with auto-replication move mode and will be deleted in %3 at about %4. The scheduled deletion for virtual tape id %1 is cancelled. Barcode [%1] of the source tape id %2 already exist on target server %3. Auto-replication cannot be configured. Failed to setup auto-replication for tape id %1 on target server %2. Error: %3. Appliance Hardware Problem: %1. Failed to re-size virtual tape %1 to %2 MB. Error: %3. Virtual tape %1 is resized to %2 MB successfully. Appliance Hardware Problem: %1. FC client %1 VSA mode is changed from %2 to %3. FC client %1 celerra mode is changed from %2 to %3. Failed to import report request. Failed to parse report request %1 %2.

96267 F

Appendix D: SNMP traps

301

Trap

Severity

Message

11902 11903 11904 11905 11906 11907 11908 11909 11910 11911 11912 12000 12001 12002 12003 12004 12005 12006 12007 12008 12009 12010 12011 13000 13001 13002 13003 13004 13005 13006

Error Error Error Informational Error Error Warning Error Error Informational Informational Informational Error Error Error Error Error Warning Error Error Error Error Error Informational Informational Informational Informational Informational Informational Informational

Undefined report type %1. Failed to allocate memory. Failed to create directory %1. Directory %1 created. Failed to open file %1. Failed to write file %1. File %1 does not exist. Failed to parse log file %1 %2. Failed to create report file %2 (type %1). Report file %2 (type %1) created. %1 property set for the VTL server. VTL logger started. VTL logger stopped. Failed to open directory %1. Failed to open file %1. Failed to create directory %1. Failed to allocate memory. Log size warning. Failed to delete file %1. Wrong file format %1. Missing parameter %1. Invalid parameter %1. Wrong status for file %1. "VTL Failover Module started -- [Primary %1, IP %3, Heartbeat %4][Secondary %2](HBInterval %5)(AutoRecovery %6)" The VTL Console has requested that this server take over for the primary server. Transferring primary static configuration to secondary. Transferring primary dynamic configuration to secondary. Transferring primary credential information to secondary. Taking over tasks for the primary server. The primary VTL Server is recovering.

302

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

13007 13008 13009 13100 13101 13102 13103 13300 13301 13302 13303 13304 13305 13306 13307 13308 13309 13310 13311 13312 13313 13314 13315 13316 13317 13318 13319 13320 13500

Informational Informational Informational Error Error Error Informational Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Informational

Restoring this server to its original configuration. VTL Failover Module stopped. Synchronizing the VTL configuration with the primary server. fail to retrieve primarys heartbeat information. Failed to communicate with primary. Error: %1 Failed to run %1. The system times of the failover pair differ by more than %1 second(s). Failed to authenticate to the primary server -- Failover Module stopped. Failed to authenticate to the local server -- Failover Module stopped. Failed to transfer primary static configuration to secondary. Failed to transfer primary dynamic configuration to secondary. Failed to rename file %1. Failed to write to file %1. Failed to open file %1. Failed to transfer primary credential information to secondary. Invalid failover configuration detected. Failover will not occur. Primary server failed to respond command from secondary. Error: %1. Failed to copy from %1 to %2. Failed to merge static configuration for the primary server. Failed to merge dynamic configuration for the primary server. Out of memory -- %1. Failed to read from file %1. Failed to merge authentication information for the primary server. Fail to add virtual IP address. Error: %1. Fail to release virtual IP address. Error: %1. Failed to restore authentication information for this server. Fail to stop VTL failover module. Host may need to reboot. Failed to update the configuration files to the primary server -%1. VTL Self-Monitor Module started -- (%1)(%2)

96267 F

Appendix D: SNMP traps

303

Trap

Severity

Message

13501 13502 13503 13504 13600 13700 13701 13702 13703 13704 13710

Informational Informational Warning Informational Informational Error Error Error Error Error Warning

all VTL related processes and resources function normally Take back the virtual IP address: %1. No heartbeat request detected for %1 seconds. Stopping Self-Monitor module. Releasing virtual IP address: %1. Failed to allocate memory -- Self-Monitor Module stopped. Failed to release virtual IP address. Error: %1. Retrying the operation. Failed to add virtual IP address: %1. Retrying the operation. Failed to stop VTL Self-Monitor Module. VTL module failure detected. Condition: %1. "The Live Trial period has expired for VTL Server %1. Please contact Sun Microsystems, Inc. or its representative to purchase a license." "The following options are not licensed: %1. Please contact Sun Microsystems, Inc. or its representative to purchase a license." Primary server failure detected. Failure condition: %1 Secondary server will take over primary server operation. Manual failover initiated. Primary acknowledged takeover request. Resources are released. Quorum disk failed to release to secondary. Virtual drives released successfully. IP address released successfully. Failover completed successfully. Primary server restored. Waiting for failback. Primary server failback initiated. Server IP address add successfully. Quorum disk returned to primary. Virtual drives added successfully. Primary server restored. Primary server failback was unsuccessful. Failed to update the primary configuration. Quorum disk negotiation failed.

13711 13800 13801 13802 13803 13804 13805 13808 13809 13810 13811 13812 13814 13815 13816 13817 13818

Warning Critical Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Critical Error

304

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

13820 13821 13822 13823 13824 13825 13826 13827 13828 13829 13830 13831 13832 13833 13834 13835 13836 13837 13838 13839 13840 13841 13842 13843 13844 13845

Warning Error Warning Warning Informational Informational Informational Error Informational Informational Error Informational Error Error Error Error Error Informational Informational Informational Informational Error Warning Error Error Warning

Failed to detect primary server heartbeat. Failed to contact other entities in network. Assume failure in secondary side. Failover not initiated. Secondary will not take over because storage connectivity is not 100%. Primary failed to acknowledge takeover request in time. Secondary will take over forcefully. Environment variable ISFCFORPCTO set to %1 Environment variable ISFOQUORUMREQ set to %1 Environment variable ISFOQUORUMCON set to %1 Fail to stop quorum updating process. PID: %1. Maybe due to storage device or connection failure. "Almost running out of file handlers (current %1, max %2)" "Almost running out of memory (current %1 K, max %2 K)" Get configuration file from storage failed. Get configuration file from storage successful. "Primary server operation is resumed either by user initiated action, or secondary server is suspended.." Failed to backup file from %1 to %2. Failed to copy file out from Quorum repository. Failed to take over primary. Failed to get configuration files from repository. Check and correct the configuration disk. Configuration files retrieved from repository successfully. Successfully copy file out from Quorum repository. Secondary server initiated failback to primary (%1) . Secondary server will take over (%1). Secondary server does not match primary server status (%1). Secondary server will takeover. Primary is still down. Secondary server fail to get original conf file from repository before failback . Failed to write %1 to repository. Quorum disk failure detected. Secondary is still in takeover mode.

96267 F

Appendix D: SNMP traps

305

Trap

Severity

Message

13846 13847 13848 13849 13850 13851 13852 13853 13854 13855 13860 13861 13862 13863 13864 13865 13866 13867 13868 13869 13870 13871 13872 13873 13875 13876 13877

Informational Informational Warning Warning Error Error Informational Informational Informational Informational Error Error Error Critical Critical Informational Error Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational

Force takeover is initiated. Secondary will perform SCSI reserve to lock the storage. Secondary server is performing SCSI release to storage. Primary is already shut down. Secondary will take over immediately. One of the heartbeat channels is down: IP address: %1. "Secondary server can not locate quorum disk. Either the configuration is wrong, or the drive is offline." Secondary server cant take over due to %1 Secondary server is being requested to release its own resources during takeover %1 Secondary notified primary to go up because secondary is unable to take over. Secondary suspended failover for %1 min. Secondary resumed failover. failed to merge configuration file %1 %2. failed to rename file from %1 to %2. failed to write file %1 to repository Primary server is commanded to resume. %1 Primary server operation will terminate. %1 Primary server will resume due to user initiated action. Failed to remove schedule Primary server is resuming and forcing device reset to clear SCSI reservation Secondary server takeover unilaterally. All resources will be released. Primary server reboot is required for recovery. Removing schedule %1 for failover process clean-up. Schedule removal completed Primary server failure condition still exists: %1 Waiting for primary to acknowledge takeover request. May take approx. %1 sec. Waiting for primary to release resources. May take approx. %1 sec. Primary server is starting to activate virtual drives. Primary server has completed activating virtual drives. Secondary server failed to take over.

306

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

13878 13879 15050 15051 15052 15053 15054 15055 16001 17001 17002 17003 17004 17005 17006 17007 17008 17009 17010 17011 17012 17013 17014 17017 17018

Error Critical Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error

Primary server has invalid failover configuration. Secondary server detect kernel module failure, reboot machine may need. Server ioctl call %1 failed on vdev id %2: Invalid Argument (EINVAL). Server ioctl call %1 failed on vdev id %2: I/O error (EIO). Server ioctl call %1 failed on vdev id %2: Not enough memory space (ENOMEM). Server ioctl call %1 failed on vdev id %2: No space left on device (ENOSPC). Server ioctl call %1 failed on vdev id %2: Already existed (EEXIST). Server ioctl call %1 failed on vdev id %2: Device or resource is busy (EBUSY). Console(%1): Converting file system failed: %2. Rescan replica cannot proceed due to replication already in progress. Rescan replica cannot proceed due to replication control area missing. Rescan replica cannot proceed due to replication control area failure. Replication cannot proceed due to replication control area failure. Replication cannot proceed due to replication control area failure. Rescan replica cannot proceed due to replication control area failure. Rescan replica failed. Replication failed. Failed to start replica rescan. Failed to start replication. Rescan replica failed due to network transport error. Replicating replica failed due to network transport error. Rescan replica failed due to local disk error. Replication failed due to local disk error. Rescan replica failed due to replica failed with error. Replication failed due to replica failed with error.

96267 F

Appendix D: SNMP traps

307

Trap

Severity

Message

17019 17020 19000

Error Error Informational

Replication control area exchange failed with error. Replication failed with error. "The replication configuration has been created successfully. Primary Server: %1, Virtual Tape: %2, Target Server: %3, Virtual Tape Replica: %4." "The failover configuration has been created successfully. Primary Server: %1, Secondary Server: %2" "The allocated space at %1MB has reached the threshold, %2% of the total capacity(%3MB)." "[Remote Copy] The configuration for remote copy has been set up successfully. Server: %1, Virtual Tape: %2, Remote Server: %3, Tape Replica: %4." [Remote Copy] The copying of the virtual tape %1 to the remote server has been started. [Remote Copy] The copying of the virtual tape %1 to the remote server has finished. "[Remote Copy] The configuration for remote copy is removed. Server: %1, Virtual Tape: %2, Remote Server: %3, Tape Replica: %4." [Remote Copy] The replica of the virtual tape %1 has been moved to the virtual library %2 on the remote server successfully. "[Remote Copy] The virtual tape has been copied to the remote server successfully. Server: %1, Virtual Tape: %2, Remote Server: %3, Tape Replica: %4." "[Remote Copy] The copying of the virtual tape to the remote server has failed while %1. Error: %2. (Server: %3, Virtual Tape: %4, Remote Server: %5, Tape Replica: %6)" [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- unable to connect to remote server %1. [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- virtual tape %1 no longer has a replica or the replica does not exist. [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- virtual tape %1 no longer has a replica or the replica does not exist. [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- unable to open configuration file. [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- unable to allocate memory.

19001 19004 19050

Informational Warning Informational

19051 19052 19053 19054 19055

Informational Informational Informational Informational Informational

19056

Error

19057 19058

Error Error

19059

Error

19060 19061

Error Error

308

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

19062 19063 19064 19065 19066

Error Error Error Error Error

[Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- unexpected error %1. [Remote Copy] The copying of the virtual tape %1 to the remote server has been manually aborted by user [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- failed to load the virtual tape %1. [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- virtual tape %1 is in the drive. [Remote Copy] The copying of the virtual tape to the remote server cannot proceed -- failed to set initialization status in VirtualLibrary System for virtual tape %1. Console (%1): Failed to get the key list. Console (%1): Failed to get the key. Console (%1): Failed to create key %2. Console (%1): Key %2 has been created successfully. Console (%1): Failed to delete Key %2. Console (%1): Key %2 has been deleted successfully. Console (%1): Failed to update information for key %2. Console (%1): Information for key %2 has been updated successfully. Console (%1): Failed to create key package %2. Console (%1): Key package %2 has been created successfully. Console (%1): Failed to get key package information. Console (%1): Failed to save keys from key package. Console (%1): %2 keys from key package have been saved successfully. SAN/IP driver started. SAN/IP driver stopped. SAN/IP driver failed to initialize. SAN SCSI driver started. SAN SCSI driver stopped. SAN SCSI driver failed to initialize. SAN SCSI received an abort request. SAN SCSI received a reset bus request for a special command. SAN SCSI received a reset bus request.

19200 19201 19202 19203 19204 19205 19206 19207 19208 19209 19210 19211 19212 20000 20001 20002 21000 21001 21002 21010 21011 21012

Error Error Error Informational Error Informational Error Informational Error Informational Error Error Informational Informational Informational Error Informational Informational Error Warning Warning Warning

96267 F

Appendix D: SNMP traps

309

Trap

Severity

Message

21013 21014 21015 21016 21017 21018

Warning Warning Warning Warning Warning Warning

SAN SCSI failed to send a SCSI command. SAN SCSI failed to receive a SCSI reply. SAN SCSI failed to attach to a virtual device. SAN SCSI failed to detach from a virtual device. SAN SCSI failed to connect to a VTL Server. "SAN SCSI received a disconnect request. This may be from the Client Monitor or due to a network failure, VTL Server shutdown/failover, or a change in a virtual device." SAN SCSI received an unsupported request. Fibre Channel Authentication started with %1. "Fibre Channel Authentication error %1, at %2." Fibre Channel Authentication stopped with %1. Fibre Channel Authentication warning from system %1. Fibre Channel Authentication error. Client Name does not match on Server %1. Fibre Channel Authentication error. Signature does not match on Server %1. %1 started. %1 failed to start -- %2. %1 paused. %1 failed to pause -- %2. %1 resumed. %1 failed to resume -- %2. %1 stopped. %1 failed to stop -- %2. %1 shutdown. %1 starting. %1 stopping. Failed to open service manager -- %1. Failed to open service -- %1. Failed to create TCP socket. Failed to bind TCP socket. Failed to create TCP service.

21019 22000 22001 22002 22003 22004 22005 25000 25001 25002 25003 25004 25005 25006 25007 25008 25009 25010 25011 25012 26000 26001 26002

Warning Informational Error Informational Warning Error Error Informational Error Informational Error Informational Error Informational Error Informational Informational Informational Error Error Error Error Error

310

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

26003 26100 26101 26102 26103 26104 26105 26106 26107 26108 26110 26200 26201 26202 26203 26204 26205 26206 26207 26208 26209 26210 27000 27001 27002 27003 27004 27005 27006

Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Error Informational Error Error Error Error Error Error Error

Failed to create TCP thread. Failed to access the %1 driver -- %2. The SAN SCSI driver is the wrong version for this VTL SAN Client. Driver version %1 will not work with client version %2. Failed to open the %1 driver -- %2. Failed to start the %1 driver. Failed to stop the %1 driver. SAN SCSI cannot connect to VTL Server %1 -- %2. SAN SCSI cannot attach to VTL SAN device %1/%2 -- %3. SAN SCSI cannot detach from VTL SAN device %1/%2 -- %3. SAN SCSI cannot disconnect from VTL Server %1 -- %2. Failed to rescan SCSI port %1 -- %2. Failed to access %1 -- %2. Failed to read the drive layout for %1 -- %2. Failed to assign drive %1 to drive letter %2. use. Failed to access drive %1 -- %2. Failed to dismount drive %1 -- %2. Failed to lock drive %1 -- %2. Failed to unlock drive %1 -- %2. Failed to define device %1 -- %2. Failed to undefine device %1 -- %2. Drive %1 is busy and cannot be detached. stop at this time. The SAN Client cannot It is already in

Both %1 and %2 have the same disk signature (%3). Failed to connect to VTL Server %1 -- %2. Failed to get the version of VTL Server %1 -- %2. Failed to get the information for VTL Server %1 -- %2. Failed to get the number of adapters for VTL Server %1 -- %2. Failed to get the information for VTL Server %1 adapter %3 -- %2. Failed to get the number of devices for VTL Server %1 -- %2. Failed to get the information for VTL Server %1 device %3 -- %2.

96267 F

Appendix D: SNMP traps

311

Trap

Severity

Message

27007 27008 28001 28002 28003 28004 28005 29101 29102 29401 29402 29403 29404 29405 29406 40000 40001 40002 40003 40004 40005 40006 40007 40008 40009 40010 40011 40012 40013 40014 40015

Error Error Error Error Error Error Error Informational Informational Informational Informational Warning Warning Error Warning Informational Informational Error Error Error Error Error Error Error Error Error Error Informational Error Error Error

Failed to get the list of IP addresses for VTL Server %1 -- %2. Failed to get the media information for VTL Server %1 device %3 -- %2. Failed to add VTL Server %1 -- %2. Failed to add VTL Server %1 adapter %2 -- %3. Failed to add VTL Server %1 adapter %2 channel %3 -- %4. Failed to add VTL Server %1 device %2 -- %3. Failed to add VTL Server %1 device %2 volume %3 -- %4. VTL Server %1 failed over. VTL Server %1 recovered from failover. Backing up VTL Server %1 device %2. Backed up VTL Server %1 device %2. Backup of VTL Server %1 device %2 failed. "VTL Notify user specified error %1, description %2." "Notify Timeout error, waiting on %1, timeout set to %2." Notify Error waiting on %1. TLE Module Started TLE Module Stopped Block list full on Drive %1 "Corrupt Repository, Rep VID %1" Unsupported device [%1][%2][%3] "Load Drive failed. Lib %1, Drive %2" "TDE get drive info failed, Drive %1, EC %2" "Unload tape from drive failed, Drive %1, EC %2" Failed to create new tape in Virtual Library %1 "HW Error with Move Medium command, Lib %1, SrcEle %2 DestEle %3" Attach to tape %1 failed "Failed to read from Virtual Tape. Tape VID %1, EC %2" Unsupported SCSI command %1 "Export Tape failed, not enough memory. Job id %1" "Read tape info failed. Tape VID %1, EC %2"

"Export tape failed, unsupported block size %1"

312

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

40016 40017 40018 40019 40020 40021 40022 40023 40024 40025 40026 40027 40028 40029 40030 40031 40032 40033 40034 40035 40036 40037 40038 40039 40040 40041

Error Error Error Error Warning Error Error Error Informational Informational Informational Informational Informational Error Error Error Warning Informational Informational Informational Error Informational Informational Error Error Informational

"Failed to write to Virtual Tape. Tape VID %1, EC %2" "Failed to write to Physical Tape. Drive VID %1, EC %2" "Failed to load Physical Tape. Lib VID %1, Drive VID %2, BC %3" "Failed to write to Virtual Tape. Tape VID %1, EC %2" Job %1 cancelled Failed to locate Virtual Library %1 "Failed to get Physical Tape block size. Drive VID %1, EC %2" "Import failed, not enough memory %1" "Import job %1 completed successfully, VLib VID %2, VLib slot %3, DestTape [%4] SrcTape [%5] Throughput %6 MB/min" "Export job %1 completed successfully. SrcTape [%2], DestTape [%3] Throughput %4 MB/min" "Export Job %1 submitted to Physical Library %2. SrcTape [%3], DestSlot [%4], %5" "Direct Access Import completed successfully. VLib VID %1, Physical Drive VID %2, Slot %3, DestTape [%4], %5" "Import job submitted. Job id %1, VLib VID %2, Slot %3, DestTape [%4], %5" Not enough memory to complete the operation "Failed to read from repository. Rep VID %1, EC %2" "Failed to write to repository. Rep VID %1, EC %2" Physical Tape %1 not available to start auto archive job. Waiting for tape... Export job %1 active. Tape Drive used %2 Import job %1 active. Tape drive used %2 Successfully attached to repository %1 Failed to attach to repository %1 "Physical Library assigned to exclusive use for TLE. Vid %1, [%2][%3]" "Physical Library unassigned. Vid %1, [%2][%3]" Read Element command to Physical Library %1 failed. EC %2 Attach to device %1 failed. EC %2 "Physical Tape Drive assigned to exclusive use for VTL. VID %1, [%2][%3]"

96267 F

Appendix D: SNMP traps

313

Trap

Severity

Message

40042 40043 40044 40045 40046 40047 40048 40049 40050 40051 40052 40053 40054 40055 40056 40057 40058 40059 40060 40061 40062 40063 40064 40065 40066 40067 40068 40069 40070

Informational Error Error Error Error Error Error Error Error Error Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Informational Error Error Error Error Error Error

"Physical Tape Drive unassigned. Vid %1, [%2][%3]" "Move Medium command failed in Physical Library %1. SrcEle %2, DestEle %3, EC %4" Unload command failed on Physical Tape Drive %1. EC %2 Read from Physical Tape Drive %1 failed. EC %2 Write to Physical Tape Drive %1 failed. EC %2 Write FM to Physical Tape Drive %1 failed. EC %2 "Mode sense command to Physical device %1 failed. Pagecode %2, EC %3" Mode select command to Physical device %1 failed. EC %2 Rewind command to Physical Tape Drive %1 failed. EC %2 Inquiry command to Physical device %1 failed. EC %2 Inventory of Physical Library %1 completed successfully Virtual Library %1 initialized. [%2][%3] Virtual Tape Drive %1 initialized. [%2][%3] Virtual Tape Drive %1 deleted from Virtual Library %2 Virtual Tape Drive %1 created successfully in Virtual Library %2 Virtual Library %1 created successfully. [%2][%3] Virtual Library %1 deleted successfully. [%2][%3] "Virtual Tape added to Virtual Library %1, slot %2. Total Tapes in Library %3. %4 %5" Stand alone Virtual Tape Drive %1 created successfully. [%2][%3] Stand alone Virtual Tape Drive %1 deleted. [%2][%3] Virtual Tape %1 moved to vault from device %2 Virtual Tape %1 from vault imported to Virtual Library %2 slot %3 Virtual Tape %1 from vault imported to Virtual Tape Drive %2 "Read data from Virtual Tape failed. Attach handle %1, EC %2" "Write data to Virtual Tape failed. Attach handle %1, EC %2" Failed to add Physical Drive %1 to repository %2. EC %3 Cannot create new Tape. EC %1 Cannot expand Tape %1. EC %2 Cannot delete Tape %1

314

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

40071 40072 40073 40074 40075 40076 40077 40078 40079 40080 40081 40082 40083 40084 40085 40087 40088

Error Informational Informational Error Informational Error Error Error Informational Warning Warning Warning Warning Warning Error Error Error

"Cannot import Tape, dest slot %1 in Virtual Library %2 is full" "Properties of Tape %1 has been changed. Barcode %2, MaxCapacity %3 MB" "Tape Created in Stand Alone Virtual Tape Drive. Tape VID %1, Drive VID %2" "Export to Physical Tape failed. Job ID %1, EC %2, SrcTape [%3] DestTape [%4]" "Export Job %1 submitted to Physical stand alone Tape Drive %2, SrcTape [%3], %4" "Import Physical Tape failed. Job ID %1, EC %2, SrcTape [%3] DestTape [%4]" Import Physical Tape failed. Duplicate Virtual Tape Barcode. Job ID %1 DestTape [%2] Import Physical Tape failed. Duplicate Virtual Tape Barcode. Dest Tape [%1] "Deleted tape marked for delayed deletion. Tape [%1], VID %2" Tape drive %1 in physical library %2 not accessible. Locked by other party Tape [%1] in physical library %2 not accessible. Locked by other party Slot %1 in physical library %2 not accessible. Locked by other party Inventory physical library %1: Tape [%2] or Slot %3 not accessible. Locked by other party Tape [%1] is blank. Cannot export blank tapes Reverse block command failed on physical tape drive VID %1 Error [%2] Error in retrieving the hostname of this VTL server. Error: %1 Failure in looking up the IP address of the VTL server (%1). Please verify that DNS is configured correctly for both ACSLS and VTL server. Error: %2 Out of system resources. Couldnt fork a process. Error: %1 Failed to execute a program. Error: %1 Failed to open %1. Error: %2 DNS configuration for VTL server is incorrect. DNS or /etc/hosts is returning %1 as the IP of VTL server (%2)

40089 40090 40091 40092

Error Error Error Error

96267 F

Appendix D: SNMP traps

315

Trap

Severity

Message

40093 40094 40095 40096 40097 40098 40099 40100 40101 40102 40103 40104 40105 40106 40107 40108 40109 40110 40111 40112 40113

Error Error Error Error Error Error Error Error Error Error Error Error Error Error Informational Informational Error Error Error Warning Warning

Failed to successfully query %1 server with IP %2. Error received: %3. Waited %1 seconds to get a response to a query from %2 (%3). Timing out. Failed to mount %1 on drive %2. Error from %3 (%4): %5. Waited %1 seconds to get a response from %2 (%3) after trying to mount %4 on drive %5. Timing out. Failed to dismount %1 from drive %2. Error from %3 (%4): %5. Waited %1 seconds to get a response from %2 (%3) after trying to dismount %4 from drive %5. Timing out. Failed to retrieve drive information in ACS %1. Error from %2 (%3): %4. Waited %1 seconds to get a response from %2 (%3) after trying to retrieve drive information in ACS %4. Timing out. Failed to retrieve volume information in ACS %1 and Pool %2. Error from %3 (%4): %5. Waited %1 seconds to get a response from ACSLS (%2) after trying to retrieve volume information in ACS %3 and Pool %4. Timing out. Failed to retrieve LSM information in ACS %1. Error from %2 (%3): %4. Waited %1 seconds to get a response from %2 (%3) after trying to retrieve LSM information in ACS %4. Timing out. %1: The number of drives %2 is more than max supported (%3). %1: The number of volumes %2 is more than max supported (%3). %1: Successfully mounted %2 on drive %3 %1: Successfully dismounted %2 from drive %3 "Log sense command to Physical device %1 failed. Pagecode %2, EC %3" Failed to retrieve volume information in ACS %1. Error from %2 (%3): %4. Waited %1 seconds to get a response from Library Station (%2) after trying to retrieve volume information in ACS %3. Timing out. Physical Tape %1 not available to start tape caching job. Waiting for tape... A Manual Export job is not allowed because tape <%1> has tape caching set.

316

VTL User Guide Mar 2008

F 96267

Trap

Severity

Message

40114 40115 40116 40117 40118 40119 40120 40121 40122 40123 40124 40125 40126 40127 40128 40129 40130 40131 40132 40133 40134 40135 40136 40137

Warning Informational Error Error Error Informational Warning Warning Informational Error Error Informational Error Informational Error Informational Warning Informational Informational Error Error Error Error Error

The export job is not allowed because physical tape [%1] in library [%2][%3] is being used by tape caching. Please add tapes. Hardware compression failed. EC [ %1 ] Hardware decompression failed. EC [ %1 ] Software decompression of a block compressed using hardware failed. EC [ %1 ] Global [%1] Compression %2 on Repository %3 The tape [%1] has no data. No export job will be submitted. "The direct link tape VID %1, BarCode [%2] has been deleted." "Export Job %1 submitted to Physical Library %2. SrcTape [%3], DestTape [%4], DestSlot [%5], %6" "Failed to load tape because it is a cleaning tape. Lib VID %1, Drive VID %2, BC %3" Write command to Configuration Repository Failed. Please check repository LUNs Disk space allocated for tape VID %1 Barcode [%2] in library VID %3 has been reclaimed successfully Failed to reclaim the tape VID %1 Barcode [%2] in library VID %3. Disk space allocated for tape VID %1 Barcode [%2] in vault has been reclaimed successfully Failed to reclaim disk space allocated for tape VID %1 Barcode [%2] in vault No Free physical drive to load direct link tape VID %1 BarCode [%2]. Unable to renew cache for tape VID %1. Data will be redirected to physical tape [%2]. The tape shredding job is successful on the tape [%1]. The tape shredding job was failed on the tape [%1]. Unable to move tape [%1] to IE slot. Unable to mount tape [%1] in library [%2] VID %3. Unable to dismount tape [%1] in library [%2] VID %3. Space command to Physical Library %1 failed. EC %2. Failed to add import/export job to the job queue. Maximum of 127 jobs reached. Job ID:%1 Physical tape barcode:[%2].

96267 F

Appendix D: SNMP traps

317

Trap

Severity

Message

40138 40139 40140 40141 50000 50001 50002 50003

Informational Warning Informational Informational Error Informational Error Error

The maximum number of slots supported in this library [%1 %2] are %3. Door opened condition reported on Physical Library VID-%1 %2 %3. Start tape shredding on tape [%1] VID:%2. The tape shredding job is cencelled on the tape [%1] VID:%2. iSCSI: Missing targetName in login normal session from initiator %1 iSCSI: Login request to target %1 from initiator %2. iSCSI: Login request to nonexistent target %1 from initiator %2 iSCSI: iSCSI CHAP authentication method rejected. Login request to target %1 from initiator %2

318

VTL User Guide Mar 2008

F 96267

APPENDIX

ILOMcommandreference
ThefollowingtablesummarizesIntegratedLightsOutManager(ILOM)commands youcanusetomanagetheserviceprocessor.FormoreinformationonILOM commands,seetheILOM Administration Guide.

Description User Commands

Command

Addalocaluser. Deletealocaluser. Changealocalusersproperties. Displayinformationaboutalllocalusers. DisplayinformationaboutLDAPsettings. ChangeLDAPsettings.

create /SP/users/user1 password=password role=administrator|operator delete /SP/users/user1 set /SP/users/user1 role=operator show -display [targets|properties|all] -level [value|all] /SP/users show /SP/clients/ldap set /SP/clients/ldap binddn=proxyuser bindpw=proxyuserpassword defaultrole=administrator|operator ipaddress=ipaddress

Network and Serial Port Setting Commands

Displaynetworkconfigurationinformation. ChangenetworkpropertiesfortheILOM. Changingcertainnetworkproperties,likethe IPaddress,disconnectsyouractivesession. Displayinformationabouttheexternalserial port. Changetheexternalserialportconfiguration. Displayinformationabouttheserialconnection tothehost.

show /SP/network set /SP/network pendingipaddress=ipaddress pendingipdiscovery=dchp|static pendingipgateway=ipgateway pendingipnetmask=ipnetmask commitpending=true show /SP/serial/external set /SP/serial/external pendingspeed=integer commitpending=true show /SP/serial/host

96267 F

319

Description

Command

Changethehostserialportconfiguration. Note:Thisspeedsettingmustmatchthespeed settingforserialport0,COM1or/dev/ttyS0on thehostoperatingsystem.


Alert Commands

set /SP/serial/host pendingspeed=integer commitpending=true

DisplayinformationaboutPETalerts.Youcan configureupto15alerts. Changealertconfiguration.


System Management Access Commands

show /SP/alert/rules/1...15 set /SP/alert/rules/1...15 destination=

ipaddress level=down|critical|major|minor
DisplayinformationaboutHTTPsettings. ChangeHTTPsettings,suchasenabling automaticredirectiontoHTTPS. DisplayinformationaboutHTTPSaccess. ChangeHTTPSsettings. DisplaySSHDSAkeysettings. DisplaySSHRSAkeysettings.
SNMP Commands

show /SP/services/http set /SP/services/http port=portnumber secureredirect enabled|disabled servicestate=enabled|disabled show /SP/services/https set /SP/services/https port=portnumber servicestate=enabled|disabled show /SP/services/ssh/keys/dsa show /SP/services/ssh/keys/rsa

DisplayinformationaboutSNMPsettings.By default,theSNMPportis161andv3is enabled.

show /SP/services/snmp engineid=snmpengineid port=snmpportnumbersets=enabled|disabled v1=enabled|disabledv2c=enabled|disabled v3=enabled|disabled

DisplaySNMPusers. AddanSNMPuser.

show /SP/services/snmp/users create /SP/services/snmp/users/snmpusername authenticationpassword=password authenticationprotocol=MD5|SHA permissions=rw|ro privacypassword=password privacyprotocol=none|DES delete /SP/services/snmp/users/snmpusername show /SP/services/snmp/communities/public create /SP/services/snmp/communities/ public/comm1 delete /SP/services/snmp/communities/ public/comm1

DeleteanSNMPuser. DisplayinformationaboutSNMPpublic (readonly)communities. AddthisdevicetoanSNMPpubliccommunity. DeletethisdevicefromanSNMPpublic community.

320

VTL User Guide Mar 2008

F 96267

Description

Command

DisplayinformationaboutSNMPprivate (readwrite)communities. AddthisdevicetoanSNMPprivate community.


Host System Commands

show /SP/services/snmp/communities/private create /SP/services/snmp/communities/ private/comm2

DeletethisdevicefromanSNMPprivate community. Startthehostsystem. Stopthehostsystem. Resetthehostsystem. Startasessiontoconnecttothehostconsole. Stopthesessionconnectedtothehostconsole.


Clock Settings

delete /SP/services/snmp/communities/ private/comm2 start /SYS stop /SYS reset /SYS start /SP/console stop /SP/console

SettheILOMclocktosynchronizewitha primaryNTPserver. SettheILOMclocktosynchronizewitha secondaryNTPserver.

set /SP/clients/ntp/server/1 address=

ntpIPaddress
set /SP/clients/ntp/server/2 address=

ntpIPaddress2

96267 F

Appendix E: ILOM command reference

321

322

VTL User Guide Mar 2008

F 96267

You might also like