How it Works
VERITAS
Loading...
PRI50LP - 50 Litre

VERITAS PRI40LP - 40 Litre, PRI31LP - 31 Litre, PRI50LP - 50 Litre, NetBackupTM 5.0 User Manual And Product Specifications

Download
Page 1
VERITAS NetBackup
™
5.0
Media Manager System Administrator’s Guide
for Windows
N102408
Page 2
The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained her ein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.
VERITAS Legal Notice
Copyright © 1998-2003 VERITAS Software Corporation. All rights reserved. VERITAS, VERITA S Software, the VERITAS logo, VERITAS NetBackup, VERITAS Backup Exec, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation.VERITAS,theVERITASLogo,VERITASNetBackupReg.U.S.Pat.&Tm.Off.Other product names and/orslogans mentioned herein may be trademarksor registered trademarks of their respective companies.
Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.
VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 650–527–8000 Fax 650–527–2901 www.veritas.com
Third-Party Copyrights
ACE 5.2A: ACE(TM) is copyrighted by Douglas C.Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved.
IBM XML for C++ (XML4C) 3.5.1: Copyright (c) 1999,2000,2001 Compaq Computer Corporation; Copyright (c) 1999,2000,2001 Hewlett-Packard Company; Copyright (c) 1999,2000,2001 IBM Corporation; Copyright (c) 1999,2000,2001 Hummingbird Communications Ltd.; Copyright (c) 1999,2000,2001 Silicon Graphics, Inc.; Copyright (c) 1999,2000,2001 Sun Microsystems, Inc.; Copyright (c) 1999,2000,2001 The Open Group; All rights reserved.
Permission ishereby granted, free ofcharge, to any person obtaininga copy of this softwareand associated documentation files (the"Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software,and to permit persons to whom the Softwareis furnished to do so, providedthat the above copyright notice(s) and this permission notice appear in all copies of the S o ftware and that both the above copyright notice(s) and this permission notice appear in supporting documentation.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). JacORB 1.4.1: The licensed software is covered by the GNU Library General Public License, Version 2, June 1991. OpenSSL0.9.6:ThisproductincludessoftwaredevelopedbytheOpenSSLProject*foruseintheOpenSSLToolkit.(http://www.openssl.org/) TAO (ACE ORB) 1.2a: TAO(TM) is copyrighted by Douglas C. Schmidt and his research group at Washington University and University of
California, Irvine, Copyright (c) 1993-2002, all rights reserved.
Page 3
Revision History for NetBackup 5.0
ThefollowingtablesummarizestherevisionsmadetothisdocumentforNetBackup release 5.0. See the release notes for more detailed information.
Release Date Description
NetBackup 5.0 December 2003 Original version for this release.
This guide is intended for use with NetBackup Server and NetBackup Enterprise Server.
Revision History for NetBackup 5.0 iii
Page 4
iv NetBackup Media Manager System Administrator’s Guide for Windows
Page 5
Contents
RevisionHistoryforNetBackup5.0.......................................iii
Preface .............................................................xxv
WhatIsInThisGuide? ....................................................xxv
HowToUseThisGuide ..................................................xxvi
GettingHelp ............................................................xxvi
NetBackupManuals ....................................................xxviii
RelatedResources ........................................................xxx
Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Chapter 1. Introduction to Media Manager . . . . . . . . . . . .......................1
MediaManagerTerminology ................................................1
Glossary............................................................xxx
MediaManagerFeatures ....................................................5
MediaManagerHosts.......................................................7
MasterServers ..........................................................8
MediaServers ...........................................................8
SANMediaServers ......................................................8
VolumeDatabaseHost ...................................................9
GlobalDeviceDatabaseHost..............................................9
MediaManagerStorageDevices.............................................10
MediaManagerVolumes ...................................................10
MountingandUsingVolumes............................................11
v
Page 6
MediaManagerAdministrationUtilities .....................................12
Starting the Media Manager Administration Utilities . . . . . . . . . . . . . . . . . . . . . . . . 12
ShortcutMenus ........................................................14
DeviceandMediaConfigurationOverview...................................14
SecurityIssues ............................................................15
Chapter2.ConfiguringStorageDevices .................................. 17
StartingDeviceManagement ...............................................18
UsingtheDeviceManagementWindow......................................18
MenusandCommands .................................................19
Toolbars ..............................................................21
TreePane .............................................................22
GlobalTopologyPane ..................................................23
TopologyIcons......................................................23
TopologyConnections ...............................................24
SelectingTopologyObjects ...........................................24
DevicesPane ..........................................................25
ManagingtheDevicesPane...........................................25
UsingtheDrivesTab.................................................25
UsingtheRobotsTab ................................................29
UsingtheHostsTab .................................................30
StatusBar .............................................................31
ShortcutMenusandCommands..........................................31
CustomizingtheWindow ...............................................32
ViewingandRearrangingColumns ....................................32
ChangingtheViewoftheTopologyPane ...............................32
AllowableMediaManagerCharacters.....................................34
PerformingInitialDeviceConfiguration......................................34
AdministeringDevicesonOtherServers .....................................36
MediaManagerSecurity ................................................37
vi NetBackup Media Manager System Administrator’s Guide for Windows
Page 7
vmdConsiderations..................................................38
ExampleSERVEREntries .............................................38
TheGlobalDeviceDatabaseHost............................................39
ASingleHostisRequired................................................39
HowThisHostisDetermined ............................................39
ManagingThisHost.....................................................40
UsingtheDeviceConfigurationWizard ......................................41
DeviceDiscoveryandDeviceSerialization .................................41
DeviceConfigurationWizardLimitations ..................................43
Device Mapping File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Using the Device Configuration Wizard to Configure Shared Drives . . . . . . . . . . . 44
StartingtheDeviceConfigurationWizard..................................45
RerunningtheDeviceConfigurationWizard ...............................45
ManagingUnsupportedDevices..........................................45
ManagingPartially-ConfiguredDevices ...................................45
AddingRobots ............................................................46
DialogEntriesforAddingandChangingRobots ............................47
DeviceHost .........................................................47
RobotType .........................................................48
RobotNumber ......................................................49
VolumeDatabaseHost ...............................................49
RobotControlSectionoftheDialog ....................................50
Robotiscontrolledlocallybythisdevicehost............................52
RoboticDeviceFile...................................................52
RobotDevice ........................................................53
LMCPDeviceFile....................................................54
LibraryName .......................................................54
Robotcontrolishandledbyaremotehost...............................55
RobotControlHost ..................................................55
DASServer .........................................................55
Contents vii
Page 8
ACSLSHost ........................................................55
RobotcontrolisattachedtoanNDMPhost .............................56
RobotDevice........................................................56
NDMPHostName ..................................................57
AddingSharedDrives .....................................................57
UsingtheDeviceConfigurationWizardforSharedDrives ...................57
UsingTheSharedDriveWizard..........................................57
AddingDrives ............................................................58
DialogEntriesforAdding(orChangingDrives)............................60
DeviceHostSectionoftheDialog......................................60
DeviceHost.........................................................60
DriveInformationSectionoftheDialog ................................60
DriveName ........................................................60
DriveType .........................................................60
DeviceName .......................................................61
NoRewindDevice...................................................61
CharacterDevice ....................................................62
VolumeHeaderDevice...............................................62
CleaningFrequency..................................................62
DriveIsInARoboticLibrary..........................................63
RoboticDriveInformationSectionoftheDialog .........................63
RoboticLibrary .....................................................63
RobotDriveNumber.................................................64
ACS ...............................................................64
TLH ...............................................................65
TLM ...............................................................65
ManagingYourDeviceConfiguration........................................66
WhentoPerformDeviceConfigurationChanges ...........................66
Using the Device Configuration Wizard for Configuration Changes . . . . . . . . . . . 67
ChangingaRobotConfiguration .........................................67
viii NetBackup Media Manager System Administrator’s Guide for Windows
Page 9
ChangingtheConfigurationofaDrive ....................................67
ChangingaNon-SharedDrivetoaSharedDrive............................68
ChangingtheVolumeDatabaseHostforStandaloneDrives ..................68
DeletingRobots ........................................................69
DeletingDrives.........................................................70
DriveCleaningFunctions ................................................70
PerformingDriveDiagnostics ............................................72
ExecutingDiagnosticTestsforaDrive..................................72
ExitingaDiagnosticTestWhenTestingisComplete ......................74
StoppingaDiagnosticTestandChangingtheDrivetobeTested ...........74
ObtainingDetailedInformationForaParticularTestStep .................74
ManagingaTestStepthatRequiresOperatorIntervention ................74
UsingSANPointControltoInvestigateSANProblems.......................75
PrintingYourDeviceConfiguration .......................................76
RobotandDriveConfigurationExamples.....................................77
Example1:ConfiguringaRobotonaServer................................77
Example2:ConfiguringStandaloneDrivesonaServer ......................79
Example3:ConfiguringaRobotDistributedAmongMultipleServers .........81
ConfigurationontheWindowsServereel ...............................82
ConfigurationontheWindowsServershark.............................83
ConfigurationontheUNIXServerwhale ...............................84
Example4:ConfiguringAnACSRobotonaWindowsServer ................85
Chapter3.ManagingMedia .............................................89
StartingMediaManagement ................................................89
UsingtheMediaManagementWindow ......................................90
MenusandCommands ..................................................90
Toolbars ...............................................................92
TreePane..............................................................93
VolumesPane ..........................................................94
Contents ix
Page 10
VolumePoolsList ...................................................95
VolumeGroupsList .................................................96
RobotsList .........................................................97
VolumesList........................................................98
StatusBar ............................................................102
ShortcutMenusandCommands.........................................102
CustomizingtheWindow ..............................................103
AllowableMediaManagerCharacters....................................103
AdministeringMediaonOtherServers......................................104
VolumeDatabaseBestPractices .........................................104
DeterminingtheVolumeDatabaseHostforaDevice.......................104
ManagingMediaonOtherServers.......................................105
ConfiguringVolumePools ................................................106
AddingaNewVolumePoolorScratchVolumePool.......................107
AddingaScratchVolumePool .......................................108
ChangingtheAttributesofaVolumePool ................................109
ChangingaVolumePoolTobeaScratchVolumePool ..................110
ChangingtheVolumePoolAssignmentforaVolume ......................110
DeletingaVolumePool ................................................111
MethodsAvailableforInjectingandEjectingVolumes ........................112
MethodsforInjectingVolumesintoaRobot...............................112
WhenAddingNewVolumes.........................................112
WhenMovingVolumes .............................................112
When Performing a Volume Configuration Update Using Robot Inventory 113
MethodsforEjectingVolumesFromaRobot ..............................113
WhenMovingVolumes .............................................113
UsingtheEjectVolumesFromRobotCommand........................114
InjectandEjectFunctionsAvailablebyRobotType ........................115
MediaEjectionTimeoutPeriods .........................................116
AddingNewVolumes ....................................................116
x NetBackup Media Manager System Administrator’s Guide for Windows
Page 11
MethodsAvailableforAddingVolumes ..................................117
RoboticVolumes(VolumesLocatedinaRobot) .........................117
StandaloneVolumes(VolumesToBeUsedinStandaloneDrives) .........117
NetBackupCatalogBackupVolumes ..................................118
NotesonLabelingNetBackupVolumes................................118
AddingVolumesUsingaRobotInventoryUpdate .........................119
AddingVolumesUsingtheActionsMenu ................................119
DialogEntriesforNewVolumes .........................................121
MediaType ........................................................121
Robot .............................................................121
FindRobots ........................................................122
NumberofVolumes.................................................122
MediaIDNamingStyle..............................................122
MediaIDorFirstMediaID...........................................123
MediaDescription ..................................................123
FirstSlotNumber...................................................123
MaximumMountsorMaximumCleanings.............................124
VolumeGroup .....................................................124
VolumePool .......................................................125
InjectVolumeIntoRobotviatheMediaAccessPort .....................126
UsingtheVolumeConfigurationWizard ....................................126
VolumeConfigurationWizardLimitations ................................126
WhatToExpectIntheVolumeConfigurationWizard ......................127
BeforeYouStarttheVolumeConfigurationWizard ........................128
StartingtheVolumeConfigurationWizard................................128
MovingVolumes .........................................................128
MovingVolumesUsingtheRobotInventoryUpdateOption ................129
MovingVolumesUsingtheActionsMenu ................................129
DialogEntriesforMoveVolumes ........................................131
VolumestoMove ...................................................131
Contents xi
Page 12
Robot .............................................................132
FindRobots........................................................132
VolumeGroup .....................................................132
FirstSlotNumber ..................................................133
EjectVolumeFromRobotviatheMediaAccessPort ....................134
InjectVolumeIntoRobotviatheMediaAccessPort.....................134
WhentoDeleteVolumes ..................................................134
DeletingVolumes .....................................................135
DeletingaVolumeGroup ..............................................135
EjectingVolumesFromRobots(ActionsMenuCommand).....................136
EjectVolumesDialogType1.........................................136
EjectVolumesDialogType2.........................................137
LabelingMedia ..........................................................137
ErasingMedia ...........................................................139
SCSIQuickErase......................................................139
SCSILongErase.......................................................139
DeassigningVolumes.....................................................140
DeterminingWhichApplicationisUsingaVolume ........................141
DeassigningNetBackupVolumes........................................141
DeassigningNetBackupRegularBackupVolumes ......................141
DeassigningNetBackupCatalogBackupVolumes ......................142
DeassigningStorageMigratorVolumes ..................................142
ChangingtheAttributesforaVolume.......................................142
DialogEntriesforChangeVolumes ......................................143
MaximumMounts..................................................143
ExpirationDate ....................................................144
Description ........................................................145
VolumePool.......................................................145
NumberofCleaningsRemaining .....................................145
ChangingtheVolumeGroupofaVolume ...................................146
xii NetBackup Media Manager System Administrator’s Guide for Windows
Page 13
ExchangingVolumes......................................................146
ExchangingaVolumeandUsingaNewMediaID .........................147
ExchangingaVolumeandUsingtheOldMediaID ........................147
RecyclingVolumes .......................................................148
RecyclingVolumesUsingtheExistingMediaID ...........................148
RecyclingVolumesUsingaNewMediaID................................148
Chapter4.ManagingMediainRobots ...................................151
OverviewofRobotInventoryOperations ....................................151
AccessingtheRobotInventoryDialog ....................................153
ShowingtheContentsofaRobot ...........................................155
ExampleShowContentsReportsforAPIRobots ...........................156
ACSRobots ........................................................156
LMFRobots ........................................................157
RSMRobots........................................................157
TLHRobots ........................................................157
TLMRobots........................................................158
ComparingRobotContentswiththeVolumeConfiguration....................158
CompareVolumeConfigurationReports .................................159
UpdatingtheVolumeConfigurationforaRobot ..............................160
WhentoUseUpdateVolumeConfiguration...............................161
WhenNottoUseUpdateVolumeConfiguration...........................162
UpdatingtheVolumeConfigurationforNon-BarcodedMedia...............163
ProcedureToUpdatetheVolumeConfiguration...........................163
ExampleUpdateVolumeConfigurationReports ........................165
MediaSettingsTab(AdvancedOptions) ..................................168
PropertiesfortheMediaSettingsTab.....................................168
MediaWhichHaveBeenRemovedFromtheRobot... ...................168
MediaWhichHaveBeenMovedIntoorWithintheRobot.................169
UsetheFollowingMediaIDPrefix ....................................170
Contents xiii
Page 14
UseBarcodeRules..................................................172
MediaType........................................................172
VolumePool.......................................................176
BarcodeRulesTab(AdvancedOptions) ..................................177
AddingaNewBarcodeRule .........................................178
ChangingaBarcodeRule............................................179
DeletingaBarcodeRule .............................................179
DialogPropertiesforAddingorChangingBarcodeRules................180
MediaIDGenerationTab(AdvancedOptions) ............................183
AddingaNewMediaIDGenerationRule .............................184
ChangingaMediaIDGenerationRule ................................185
DeletingaMediaIDGenerationRule .................................185
Dialog Properties for Adding or Changing Media ID Generation Rules . . . . 185
MediaTypeMappingsTab(AdvancedOptions)...........................187
HowtheMappingDefaultsShownontheTabareDetermined ...........187
UsingtheTabtoChangeMediaTypeMappings........................187
AddingMappingEntriestovm.conf ..................................189
DefaultandAllowableMediaTypesforAPIRobots.....................189
ExamplesofUpdatingaVolumeConfiguration ...........................194
Example1:RemovingaVolumefromaRobot ..........................194
Example2:AddingExistingStandaloneVolumestoaRobot .............196
Example3:MovingExistingVolumesWithinaRobot ...................198
Example4:AddingNewVolumestoaRobot...........................200
Example5:AddingCleaningTapestoaRobot .........................202
Example6:MovingExistingVolumesBetweenRobots ..................203
Example 7: Adding Existing Volumes when Barcodes are Not Used . . . . . . . 204
RescanningandUpdatingBarcodesforaRobot ..............................206
WhentoUseRescan/Update ...........................................206
WhenNottoUseRescan/Update .......................................207
ProcedureToRescan/UpdateBarcodes ..................................207
xiv NetBackup Media Manager System Administrator’s Guide for Windows
Page 15
Chapter5.MonitoringStorageDevices ..................................209
StartingtheDeviceMonitor ................................................210
UsingtheDeviceMonitorWindow .........................................210
MenusandCommands .................................................211
Toolbars ..............................................................214
GlobalTopologyPane ..................................................215
TopologyImages ...................................................215
TopologyConnections...............................................217
SelectingTopologyObjects...........................................217
DrivesStatusPane .....................................................218
ManagingtheDrivesStatusPane .....................................218
PendingRequestsPane .................................................222
ManagingthePendingRequestsPane .................................223
StatusBar.............................................................225
ShortcutMenusandCommands .........................................225
CustomizingtheWindow...............................................226
AllowableMediaManagerCharacters ....................................227
ControllingtheNetBackupDeviceManagerService...........................228
MonitoringDevicesonOtherServers........................................228
ChangingtheOperatingModeofaDrive ....................................230
ChangingModeExample ...............................................230
ResettingaDrive .........................................................231
DriveCleaningFunctions..................................................232
AddingorChangingaDriveComment......................................234
HandlingPendingRequestsandPendingActions.............................235
PendingRequests......................................................235
PendingActions .......................................................236
ResolvingPendingRequests ...............................................236
ResolvingaPendingRequestExample(DriveinAVRmode) ................238
ResolvingPendingActions.................................................239
Contents xv
Page 16
ResubmittingRequests....................................................240
DenyingRequests ........................................................241
AppendixA.MediaManagerReferenceTopics ........................... 243
NetBackupMediaManagerBestPractices ...................................244
GeneralPractices ......................................................244
MediaandDeviceManagementDomainManagement .....................244
MediaManagement ...................................................245
DeviceManagement ...................................................246
PerformanceandTroubleshooting.......................................247
OtherBestPractices....................................................248
NetBackupandMediaManagerDatabases ..................................248
MediaManagerVolumeDatabase .......................................248
MediaCatalog ........................................................249
NetBackupCatalogs ...................................................249
DeviceDatabases......................................................249
RobotOverview..........................................................250
MediaManagerRobotTypes............................................250
MediaManagerMediaTypes ...........................................251
AlternateMediaTypes ..............................................252
RobotAttributes ......................................................253
Table-DrivenRobotics .................................................265
RoboticTestUtilities...................................................265
RoboticProcesses......................................................265
ProcessExample ...................................................266
ProcessesbyRobotType ............................................267
FrequentlyAskedQuestionsAboutDeviceDiscovery.........................269
CorrelatingDeviceFilestoPhysicalDrivesWhenAddingDrives...............272
OnWindowsHosts....................................................272
OnUNIXHosts .......................................................274
xvi NetBackup Media Manager System Administrator’s Guide for Windows
Page 17
DriveCleaning ...........................................................275
AvailableTypesofCleaning.............................................275
ReactiveCleaning(TapeAlert) ...........................................276
RequirementsforUsingTapeAlertwithMediaManager .................276
TapeAlertandMediaManager .......................................276
TapeAlertandFrequency-BasedCleaning..............................277
Library-BasedCleaning.................................................277
Frequency-BasedCleaning ..............................................277
Frequency-BasedCleaningLimitations ................................278
ManagingFrequency-BasedCleaning..................................278
Operator-InitiatedCleaning .............................................279
UsingaCleaningTape .................................................279
VolumePoolsandVolumeGroups..........................................280
VolumePools .........................................................280
VolumeGroups .......................................................280
RulesforAssigningVolumeGroups...................................280
VolumePoolandVolumeGroupExample ................................281
ScratchVolumePools ..................................................282
ScratchPoolExample................................................283
ScratchPoolUsage..................................................283
MovingVolumes ......................................................284
MoveOperations ...................................................284
PhysicalandLogicalMoves ..........................................285
Barcodes ................................................................285
BarcodeAdvantages ...................................................286
BarcodeBestPractices ..................................................286
BarcodeRules .........................................................287
ExampleBarcodeRules..............................................287
MediaManagerActionsforBarcodes ..................................289
MediaIDGenerationRules .............................................289
Contents xvii
Page 18
UsingthePhysicalInventoryUtilityforNon-BarcodedMedia..................290
WhyUsevmphyinv? ..................................................290
Features...........................................................290
RequirementsandRestrictions .......................................291
WhentoUsevmphyinv ................................................291
HowvmphyinvPerformsaPhysicalInventory ............................292
ObtainingaListofDrivesUsedtoMounttheMedia ....................293
ObtainingaListofMediatobeMounted ..............................293
MountingMediaandReadingtheTapeHeader ........................294
UpdatingtheMediaManagerVolumeDatabase ........................296
MakingChangestoYourHardwareConfiguration ...........................299
ReplacingDevicesinaSSOConfiguration ................................299
DecommissioningaMediaServer .......................................300
LabelingMedia ..........................................................302
Pre-labelingofMedia ..................................................302
MountingandUnmountingofMedia .......................................303
SuspendingMediaOrDowningDevices ....................................303
HowMediaManagerSelectsaDriveforaRoboticMountRequest ..............303
ControllingHardwareCompression ........................................304
HowNetBackupSelectsMediainRobots ....................................304
SpanningMedia.......................................................306
HowNetBackupSelectsMediainStandaloneDrives..........................306
MediaSelectionUsingStandaloneDriveExtensions .......................306
DisablingStandaloneDriveExtensions ................................307
SpanningMedia....................................................307
KeepingStandaloneDrivesintheReadyState..........................308
MediaFormats...........................................................308
Non-QICTapeFormat .................................................309
QICTapeFormat......................................................309
OpticalMediaFormat..................................................309
xviii NetBackup Media Manager System Administrator’s Guide for Windows
Page 19
FragmentedBackups ...................................................310
MultiplexingFormat ...................................................310
SpanningTapes .......................................................311
MediaManagerSecurity...................................................311
NetBackupAuthentication/Authorization ................................311
MediaManagerAuthentication/Authorization ............................312
Novm.confEntryPresent............................................312
vm.confEntryisPresent .............................................313
MediaManagerSecurity(UsingSERVERConfigurationEntries) .............314
PossibleNetBackupandMediaManagerConflicts .........................314
MediaManagerEnhancedAuthorization .................................315
SupportedCommandsandDaemons..................................315
AllowingEnhancedAuthorization ....................................316
EnablingRobotAuthorization ........................................316
AdministratorsQuickReference ............................................316
MediaManagerCommands.............................................317
MediaManagerLogFiles ...............................................319
TheMediaManagerConfigurationFile(vm.conf) .............................320
ACSMediaMapping ................................................320
AdjacentLSMSpecificationforACSRobots ............................320
APIRobotBarcodeRuleEnable.......................................321
AuthorizationRequired..............................................322
AutomaticallyEmptyRobotMAP.....................................322
AVRDScanDelay...................................................322
AVRDPendingStatusDelay .........................................323
BackupExec-MappingMediaTypes..................................323
BackupExec-MappingRobots .......................................324
CleaningDrivesTimeout ............................................324
ClientPortRange ...................................................325
ConnecttoFirewallOptions..........................................325
Contents xix
Page 20
DASClientName ..................................................326
DaysToKeepDebugLogs...........................................326
DeviceHostEntries.................................................327
DisableAutomaticPathRemapping ..................................327
DisallowNon-NDMPRequestonNDMPDrive ........................327
DoNotEjectStandaloneTapes .......................................328
EnableRobotAuthorization..........................................328
InventoryRobotFilter...............................................328
MediaAccessPortDefaultforACSRobots.............................329
MediaIDGeneration................................................330
MediaIDPrefix ....................................................331
NotAllowingaHostToManageDatabases ............................331
PreferredGroup....................................................331
PreventMediaRemoval(forTL8Robots) ..............................332
RandomPortNumbers..............................................332
Cluster Name, Media Manager Name, Required Network Interface . . . . . . . 333
ReturnMediatotheScratchPool .....................................333
RSMMediaMapping ...............................................334
ScratchPoolConfiguration ..........................................334
ServerEntry .......................................................334
SSODARe-registerInterval .........................................335
SSODARetryTime.................................................335
SSOHostName ....................................................335
SSOScanAbilityFactor .............................................336
TLHMediaMapping ...............................................337
TLMMediaMapping ...............................................337
VaultMediaDescriptionReset .......................................337
VerboseMessageLogging ...........................................338
Examplevm.confFile ..................................................338
xx NetBackup Media Manager System Administrator’s Guide for Windows
Page 21
AppendixB.AutomatedCartridgeSystem(ACS) ..........................339
SampleACSConfiguration ................................................340
MediaRequests ..........................................................342
ConfiguringACSRoboticControl...........................................342
ConfiguringACSDrives...................................................342
ConfiguringSharedACSDrives ............................................344
UsingtheSTKSN6000.....................................................345
ShouldSN6000DrivesBeConfiguredasSharedDrives? ....................346
HostsConnectedToaSinglePort .....................................346
HostsConnectedToDifferentPorts ...................................346
AddingVolumes .........................................................347
RemovingVolumes .......................................................347
RemovingVolumesUsingtheSTKUtility.................................348
RemovingVolumesUsingMediaManager................................348
RobotInventoryOperations................................................348
AdvancedACSRobotTopics...............................................350
ACSProcess(acsd).....................................................350
ACSRoboticTestUtility(acstest) ........................................350
RoboticInventoryFiltering..............................................351
InventoryFilteringExample..........................................351
AppendixC.MicrosoftRemovableStorageManager(RSM)..................353
MediaManagerandMicrosoftRSM.........................................353
ConsiderationsWhenUsingMicrosoftRSM ...............................353
TheMicrosoftRSMInterface ............................................354
MediaRequestsInvolvinganRSMRobot ....................................354
ConfiguringRSMRoboticControl ..........................................355
ConfiguringRSMDrivesinMediaManager..................................355
VerifyingaConfiguration...............................................355
ActivatingaConfiguration ..............................................356
Contents xxi
Page 22
AddingVolumes.........................................................356
RemovingVolumes.......................................................358
RobotInventoryOperations ...............................................358
AppendixD.IBMAutomatedTapeLibrary(ATL) .......................... 361
SampleTLHConfigurations ...............................................361
MediaRequestsforaTLHRobot ...........................................364
ConfiguringRoboticControl...............................................365
RoboticControlonaWindowsSystem ...................................365
DeterminetheLibraryName.........................................365
VerifyLibraryCommunications ......................................366
ConfiguretheRoboticLibraryName..................................367
ConfiguringDrivesforTLHRobots.........................................367
CleaningDrives..........................................................368
AddingVolumes.........................................................369
RemovingVolumes.......................................................369
RobotInventoryOperations ...............................................370
RoboticInventoryFiltering ................................................371
Appendix E. ADIC Distributed AML Server (DAS) / Scalar Distributed Library
Controller(SDLC).................................................... 373
SampleTLMConfiguration................................................373
MediaRequestsInvolvingaTLMRobot .....................................374
ConfiguringRoboticControl...............................................375
AllocatingTLMDrivestoMediaManager ...................................375
InstallingADICSoftwarefortheDASClientComponent ...................375
ConfiguringtheDASClientName.......................................376
UseDASADMINtoAllocateDrives .....................................377
ConfiguringTLMDrives ..................................................377
ConfiguringSharedTLMDrives ...........................................378
ConfiguringtheADICDASServer.......................................378
xxii NetBackup Media Manager System Administrator’s Guide for Windows
Page 23
ConfiguringtheADICSDLCServer......................................379
UsingtheDeviceConfigurationWizard ..................................380
ProvidingCommonAccesstoVolumes......................................381
AddingVolumes .........................................................381
RemovingVolumes .......................................................382
RobotInventoryOperations................................................383
Index ...............................................................385
Contents xxiii
Page 24
xxiv NetBackup Media Manager System Administrator’s Guide for Windows
Page 25
Preface
This guide describes using the NetBackup Administration Console to manage Media Manager software and its components on a Windows server. See the NetBackup release notes for information about the supported Windows server platforms for NetBackup.
Media Manager is the component of VERITAS NetBackup manage media, drives, and robots that are used to store and retrieve your backup data.
This guide assumes you are familiar with the operating system of the server on which NetBackup and Media Manager is installed and Windows systems in general.
What Is In This Guid e?
This guide contains the following chapters:
◆ “Introduction to Media Manager” on page 1 provides an overview of Media Manager.
◆ “ConfiguringStorageDevices”on page 17 explains how to attachstorage devices and
configure Media Manager to use them.
◆ “Managing Media” on page 89 contains topics on configuring Media Manager to use
the media (volumes an d volume pools) that Media Manager requires to store backups.
◆ “Managing Media in Robots” on page 151 explains how to configure Media Manager
to use and manage the media in robots (using robot inventory).
◆ “Monitoring Storage Devices” on page 209 explains tasks such as monitoring drives
and media mount requests, and assigning a requested volume to a drive.
TM
that is used to configure and
In addition to these chapters, this guide contains the following appendixes and an index.
◆ “Media Manager Reference Topics” on page 243 provides background information on
important Media Manager features and concepts.
◆ “Automated Cartridge System (ACS)” on page 339 explains how Media Manager
works with StorageTek (STK) Automated Cartridge System robots.
xxv
Page 26
How To Use This Guide
◆ “Microsoft Removable Storage Manager (RSM)” on page 353 explains how Media
Manager communicates with robots under the control of Microsoft Removable Storage Manager.
◆ “IBM Automated Tape Library (ATL)” on page 361 explains how Media Manager
supports robots controlled by the IBM Automated Tape Library.
◆ “ADIC Distributed AML Server (DAS) / Scalar Distributed Library Controller
(SDLC)” on page 373 explains how Media Manager works with the EMASS Distributed AML Server to control Tape Library Multimedia (TLM) robots, including the Grau AML Library.
How To Use This Guide
Keep the following points in mind when using this guide.
◆ This guide is intended for use with NetBackup Server and NetBackup Enterprise
Server. For readability in this guide, the term NetBackup refers to both NetBackup server types unless specifically noted.
◆ Portions of this guide apply only to specific robot types (for example, API, RSM, or
optical robots), server platforms (UNIX or Windows), or NetBackup server type (for example, NetBackup Enterprise Server).
These topics are identified with the use of italics as in the following example:
This step is only applicable for NetBackup Enterprise Server.
◆ This guide is intended primarily for the system administrator, who will probably
want to read every chapter. An operator should read the chapter “Monitoring Storage Devices” on page 209 and
may have an interest in reading the Media Manager overview in the chapter “Introduction to Media Manager” on page 1.
Getting Help
Use the VERITAS Technical support web site to get help for NetBackup if you have questions.
Accessing the VERITAS Te chnical Support Web Site
The VERITAS Technical Support Web site allows you to do any of the following:
◆ obtain updated information about NetBackup, including sys tem requirements,
supported platforms, and supported peripherals
xxvi NetBackup Media Manager System Administrator’s Guide for Windows
Page 27
Getting Help
◆ contact the VERITAS Technical Support staff and post questions to them
◆ get the latest patches, upgrades, and utilities
◆ view the NetBackup Frequently Asked Questions (FAQ) page
◆ search the knowledge base for answers to technical support questions
◆ receive automatic notice of product updates
◆ find out about NetBackup training
◆ read current white papers related to N etBackup
The address for the VERITAS Technical Support Web site follows:
http://support.veritas.com
Using VERITAS Telephone and E-mail Support
Telephone support for NetBackup is only available with a valid support contract. To contact VERITAS for technical support, dial the appropriate phone number listed on the Technical Support Guide included in the product box and have your product license information ready for quick navigation to the proper support group.
▼ To locate the telephone support directory on the VERITAS web site
1. Open http://support.veritas.com in your web browser.
2. Click the Phone Support icon. A page that contains VERITAS support numbers from
around the world appears.
▼ To contact support using E-mail on the VERITAS web site
1. Open http://support.veritas.com in your web browser.
2. Click the E-mail Support icon. A brief electronic form will appear and prompt you to:
◆ Select a language of your preference
◆ Select a product and a platform
◆ Associate your message to an existing technical support case
◆ Provide additional contact and product information, and your message
3. Click Send Message.
Preface xxvii
Page 28
NetBackup Manuals
NetBackup Manuals
The following manuals, along with the online help, comprise the NetBackup documentation set:
For a complete list of related documents, see the NetBackup release notes. Depending on your configuration, other documents may also be required.
◆ VERITAS NetBackup Commands for UNIX
NetBackup_Commands_UNIX.pdf Describes NetBackup commands and processes that can be executed from a UNIX
command line.
◆ VERITAS NetBackup Commands for Windows
NetBackup_Commands_Windows.pdf Describes NetBackup commands and processes that can be executed from a Windows
command prompt.
◆ VERITAS NetBackup Global Data Manager System Administrator’s Gu ide for UNIX and
Windows
NetBackup_AdminGuide_GDM.pdf Explains how to install, configure, and use Global Data Manager (GDM) for
NetBackup products on UNIX and Windows-based operating systems.
◆ VERITAS NetBackup Installation Guide for UNIX
NetBackup_Install_UNIX.pdf Explains how to install NetBackup software on UNIX-based platforms.
◆ VERITAS NetBackup Installation Guide for Windows
NetBackup_Install_Windows.pdf Explains how to install NetBackup software on Windows-based platforms.
◆ VERITAS NetBackup Media Manager Device Configuration Guide for UNIX and Windows
MediaMgr_DeviceConfig_Guide.pdf Explains how to add device drivers and perform other system-level configurations for
storage devices and media servers (or SAN media servers) that are supported by NetBackup Media Manager.
◆ VERITAS NetBackup Media Manager System Administrator’s Guide for UNIX
MediaMgr_AdminGuide_Unix.pdf Explains how to configure and manage the storage devices and media on UNIX
servers running NetBackup. Media Manager is part of NetBackup.
xxviii NetBackup Media Manager System Administrator’s Guide for Windows
Page 29
NetBackup Manuals
◆ VERITAS NetBackup for NDMP System Administrator’s Guide
NetBackup_AdminGuide_NDMP.pdf Explains how to install, configure, and use NetBackup for NDMP to control backups
on an NDMP host.
◆ VERITAS NetBackup Release Notes for UNIX and Windows
NetBackup_Release_Notes.pdf Provides important information about NetBackup on UNIX- and Windows-based
servers, such as the platforms and operating systems that are supported and operating notes that may not be in the NetBackup manuals or the online help.
◆ VERITAS NetBackup SAN Shared Storage Option System Administrator’s Guide for UNIX
and Windows
MediaMgr_AdminGuide_SSO.pdf Provides information on installing and configuring the NetBackup Shared Storage
Option (SSO) on UNIX and Windows-based servers. SSO is an extension to tape drive allocation and configuration for NetBackup Media Manager.
◆ VERITAS NetBackup System Administrator's Guide for UNIX, Volume I
NetBackup_AdminGuideI_UNIXServer.pdf Explains how to configure and manage NetBackup on a UNIX server, including
managing storage units, backup policies, catalogs and host properties.
◆ VERITAS NetBackup System Administrator's Guide for UNIX, Volume II
NetBackup_AdminGuideII_UNIXServer.pdf Explains additional NetBackup features such as a ccess control and enhanced
authorization and authentication. The guide also discusses using NetBackup with AFS and Intelligent Disaster Recovery (IDR).
◆ VERITAS NetBackup System Administrator’s Guide for Windows, Volume I
NetBackup_AdminGuideI_WinServer.pdf Explains how to configure and manage NetBackup on a Windows server, including
managing storage units, backup policies, catalogs and host properties.
◆ VERITAS NetBackup System Administrator’s Guide for Windows, Volume II
NetBackup_AdminGuideII_WinServer.pdf Explains additional NetBackup features such as a ccess control and enhanced
authorization and authentication. The guide also discusses using NetBackup with AFS and Intelligent Disaster Recovery (IDR).
◆ VERITAS NetBackup Troubleshooting Guide for UNIX and Windows
Preface xxix
Page 30
Related Resources
NetBackup_Troubleshoot_Guide.pdf Provides troubleshooting information for UNIX- and Windows-based NetBackup
products, including Media Manager.
◆ VERITAS NetBackup Vault System Administrator's Guide for UNIX and Windows
NetBackup_AdminGuide_Vault.pdf Describes how to configure and use logical vaults and profiles to duplicate backups,
perform catalog backups, eject media, and generate reports.
◆ VERITAS Security Services(tm) Version 4.0 Administrator’s Guide
VxSS_AdminGuide.pdf on the VERITAS Security Services CD-ROM. Explains how to configure and manage core security mechanisms, including
authentication, protected communications, and authorization.
Related Resources
Glossary
If you encounter unfamiliar terminology, consult the NetBackup online glossary. The glossary contains terms and definitions for NetBackup and all additional NetBackup options and agents.
The NetBackup online glossary is included in the NetBackup help file.
▼ To access the NetBackup online glossary
1. In the NetBackup Administration Console (or from the Backup, Archive, and Restore
client interface), click Help> Help Topics.
2. Click the Contents tab.
3. Double-click Glossary.
4. Click NetBackup Glossary of Terms.
The glossary displays in a help window. Use the scroll function to navigate through the glossary.
xxx NetBackup Media Manager System Administrator’s Guide for Windows
Page 31
Accessibility Features
NetBackup contains features that make the user interface easier to use by people who are visually impaired and by people who have limited dexterity. Accessibility features include:
◆ Support for assistive technologies such as screen readers and voice input (Windows
servers only)
◆ Support for keyboard (mouseless) na vigation using accelerator keys and mnem on ic
keys
For more information, see the NetBackup System Administrator’s Guide, Volume I.
Conventions
The following section explains typographical and other conventions used in this guide.
Product-Specific Conventions
Accessibility Features
The following term is used in the NetBackup documentation to increase readability while maintaining technical accuracy.
◆ Microsoft Windows, Windows
Terms used to describe a specific product or operating system developed by Microsoft, Inc. Some examples you may encounter in NetBackup documentation are, Windows servers, Windows 2000, Windows Server 2003, Windows clients, Windows platforms, or Windows GUI.
WhenWindowsorWindowsserversisusedinthedocumentation,itreferstoallof the currently supported Windows operating systems. Wh en a specific Windows product is identified in the documentation, only that particular product is valid in that instance.
For a complete list of Windows operating systems and platforms that NetBackup supports, refer to the NetBackup Release Notes for UNIX and Windows or go to the VERITAS support web si te at http://www.support.veritas.com.
Preface xxxi
Page 32
Conventions
TypographicalConventions
Here are the typographical conventions used throughout the manuals:
Conventions
Convention Description
GUI Font Used to depict graphical user interface (GUI) objects, such as fields,
listboxes, menu commands, and so on. For example: Enter your password in the Password field.
Italics Used for placeholder text, book titles, new terms, or emphasis. Replace
placeholder text with your specific text. For example: Replace filename withthenameofyourfile.Donot usefilenamesthatcontainspaces.
This font is also used to highlight NetBackup server-specific or operating system-specific differences. For example: This step is only applicable for
NetBackup Enterprise Server.
Code Used to show what commands you need to type, to identify pathnames
where files are located, and to distinguish system or application text that is displayed to you or that is part of a code example.
Key+Key Used to show that you must hold down the first key while pressing the
second key. For example: Ctrl+S means hold down the Ctrl key while you press S.
You should use the appropriate conventions for your platform. For example, when specifying a path, use backslashes on Microsoft Windows and slashes on UNIX. Significant differences between the platforms are noted in the text.
Tips, notes, and cautions are used to emphasize information. The following samples describe when each is used.
Tip Used for nice-to-know information, like a shortcut.
Note Used for important information that you should know, but that shouldn’t cause any
damage to your data or your system if you choose to ignore it.
Caution Used for information that will prevent a problem. Ignore a caution at your own
risk.
Command Usage
The following conventions are frequently used in the synopsis of command usage.
xxxii NetBackup Media Manager System Administrator’s Guide for Windows
Page 33
Conventions
brackets [ ]
The enclosed command line component is optional.
Verticalbarorpipe(|)
Separates optional arguments from which the user can choose. For example, when a command has the following format:
command arg1|arg2
In this example, the user can use either the arg1 or arg2 variable.
Navigating Multiple Menu Levels
When navigating multiple menu levels, a greater-than sign (>) is used to indicate a continued action.
The following example shows how the > is used to condense a series of menu selections into one step:
❖ Select Start > Programs > VERITAS NetBackup > NetBackup Administration
Console.
The corresponding actions could be described in more steps as follows:
1. Click Start in the task bar.
2. Move your cursor to Programs.
3. Move your cursor to the right and highlight VERITAS NetBackup.
4. Move your cursor to the right. First highlight and then click NetBackup
Administration Console.
Preface xxxiii
Page 34
Conventions
xxxiv NetBackup Media Manager System Administrator’s Guide for Windows
Page 35
Introduction to Media Manager
Media Manager provides control of tape storage devices and tracks the location of the removable media that are used in these devices. Media Manager is an integral part of NetBackup and is installed with it on every server where NetBackup is running.
This chapter provides an overview of Media Manager and contains the following topics:
◆ Media Manager Terminology
◆ Media Manager Features
◆ Media Manager Hosts
◆ Media Manager Storage Devices
◆ Media Manager Volumes
◆ Media Manager Administration Utilities
◆ Device and Media Configuration Overview
◆ Security Issues
When you are familiar with the features and the administration of NetBackup and Media Manager described in this guide, you should review the list of recommended practices. See “NetBackup Media Manager Best Practices” on page 244.
1
Media Manager Terminology
The following table contains key terms that are used in Media Manager documentation and help.
1
Page 36
Media Manager Terminology
For the complete NetBackup glossary of terms, refer to the glossary that is included in the NetBackup help file. This glossary contains terms and definitions for NetBackup, and all additional NetBackup options and agents.
Term Description
ADAMM database (Advanced Device and Media Management). The Backup Exec
API robots A group of Media Manager robot types where the robot-vendor
database that maintains device and media information.
software or the operating system (in the case of RSM robots) manage their own media.
The following are the supported API robots for the NetBackup server typesonUNIXserversandMicrosoftWindowsservers:
◆ NetBackup Server for Windows: RSM.
◆ NetBackup Enterprise Server for Windows: ACS, RSM, TLH, and
TLM.
◆ NetBackup Server for UNIX: None.
◆ NetBackup Enterprise Server for UNIX: ACS, LMF, TLH, and TLM.
avrd The Media Manager automatic volume recognition daemon on UNIX
and process on Windows servers.
barcode A label attached to the media that associates the media to its slot
location in a robot. The alphanumeric barcode is also usually included on the magnetic label that is written on the media.
barcode rule A rule that specifies criteria for assigning attributes to new robotic
volumes.
device host A host where a drive or robotic control is attached or is defined, that
also has Media Manager installed.
drive status A status indicating the condition or state of a drive.
global device database A database that is the repositoryfor global device configuration
information. This information is used by Media Manager to automate device configuration a nd is the basis for the device configuration presented in the GUIs.
The global device database host is the host where this database is located.
insert A volume is physically placed in a robot without using an add or move
option to update the volume database.
2 NetBackup Media Manager System Administrator’s Guide for Windows
Page 37
Media Manager Terminology
Term Description
labeled volume A volume with a recorded media ID (that is, the volume was labeled by
NetBackup or Backup Exec).
library sharing Applies only to NetBackup Enterprise Server.
Allows different drives in a robot to be connected to different hosts. Also known as robot sharing or remote robot control.
ltid The Media Manager device daemon on UNIX and the NetBackup
Device Manager service on Windows.
Media and Device Management (MDM) domain
Applies only to NetBackup Enterprise Server.
A domain that includes all of the servers listed in the global device database (this domain also includes the global device database host).
The Media and Device Management domain server is the host where the Media Manager volume database, volume pool database, barcode rule database, and global device database for a domain are located.
media ID An identifier used by Media Manager to track media.
media server A server that can back up its own data or other clients on the network
as well to devices.
media type A Media Manager classification of tape or optical media with differing
physical characteristics.
mount request A request for a volume that is displayed in the Pending Requests pane.
This means to make a volume available for reading or writing by placingitinanappropriatedriveandthenassigningtheassociated requesttothatdrive.
NetBackup authentication A NetBackup security level that verifies NetBackup client to server, or
server to server access. Authentication also controls access to the services available on that host.
NetBackup authorization A NetBackup security level that verifies if a NetBackup user (or groups
NetBackup media database A database that contains media attributes (like media state and image
Chapter 1, Introduction to Media Manager
of users) has permission to use the services available on that host. Authorization provides additional security over the security provided by authentication.
expiration date) for media assigned to a particular NetBackup server. There is a media database located on each server that has (or had) drives connected to it and is also running NetBackup.
3
Page 38
Media Manager Terminology
Term Description
no rewind on close A device name that applies to tape drives attached to (or controlled by)
operator A person responsible for performing manual intervention, for example
pending actions Special requests for operator assistance to complete a tape mount
UNIX devices. This type of device remains at its current position on a close operation.
mounting tapes.
request, when the request causes an error.
residence information or residence
Attributes in the Media Manager volume database. This information shows the robotic location and includes the robot host, robot type, robot number, and slot location.
robot control host Applies only to NetBackup Enterprise Server.
The host that is providing the robotic control for a robot.
robot number A unique, logical identification number of a robot.
robot type Media Manager classification of robots, according to one of the
following: the physical characteristics of the robot, the media type commonly used by that class of robots, or the communication methods used by the underlying robotics.
robotic control path The control path to a robot through a SCSI connection.
robotic library or robot A peripheral device that contains a mechanism for the automated
mounting and dismounting of media in tape or optical disk drives. A robot may also be called a robotic library, media changer, automated library, jukebox, or tape stacker.
SAN media server A server that can only back up its own data to devices. Backing up of
data residing on other clients on a network is not allowed.
shared drive Applies only to NetBackup Enterprise Server.
Shared Storage Option (SSO)
standalone drive A drive that is not in a robotic library.
4 NetBackup Media Manager System Administrator’s Guide for Windows
A tape drive that is shared among hosts, when SSO is installed.
Applies only to NetBackup Enterprise Server.
A NetBackup software option that allows individual tape drives (stand-alone or in a robotic library) to be dynamically shared between multiple NetBackup media servers (or SAN media servers).
Page 39
Media Manager Features
Term Description
system administrator A person with typical UNIX or Windows administrator privileges and
responsibilities.
unlabeled volume A volume that does not have recorded media IDs.
user A person or application (for example, NetBackup) that initiates Media
Manager requests.
vmd The Media Manager volume daemon on UNIX and the NetBackup
Volume Manager service on Windows.
volume database The database that is the repository for Media Manager volume
configuration information. The volume database host is a Media Manager host where this database is
located.
volume group A logical grouping that identifies a set of volumes that reside at the
same physical location.
volume pool A logical grouping that identifies a set of volumes by their usage.
Media Manager Features
◆ Robotic and Standalone Drive Support
In Media Manager, a robot is a peripheral device for the automated mounting and dismounting of volumes in tape drives. A standalone drive is a drive that is not associated with a robot.
Media Manager supports a wide range of robots and automates the handling of volumes in these devices. Except for initial setup and loading of tapes or an equipment failure, manual intervention is not required.
Visit the VERITAS support web site for a list of the platforms and peripherals that Media Manager supports.
Media handling in standalone drives is also automated to the extent that Media Manager automatically uses the tape that is in a drive, if it is required by NetBackup.
Capability to perform automated drive cleaning, based on the TapeAlert feature or a frequency-based cleaning schedule. Cleaning tapes that are configured incorrectly are also recognized.
Chapter 1, Introduction to Media Manager
5
Page 40
Media Manager Features
Media Manager running on NetBackup Windows servers does not support optical disk storage devices.
◆ Media Location Tracking
Media Manager maintains a volume database that shows the location of all media (for example, the robot and slot). This information permi ts Media Manager to find media when it is required to satisfy a request.
◆ Media Statistics Tracking
Media Manager keeps a record of statistics that are useful in tracking the useful life of media (for example, an expiration date and the number of times that media has been mounted).
◆ Security
Media Manager vmd security works in conjunction with NetBackup authentication/authorization security to control user access to vmd (the NetBackup Volume Manager service).
The topic, “Media Manager Security” on page 311 explains important security features, including the following topics:
◆ The relationship with NetBackup authentication/authorization security.
◆ Controlling user access to vmd (the Media Manager volume daemon).
◆ Controlling user access to Media Manager robotic daemons and services.
◆ Robot Inventory and Update
Media Manager can inventory a robot, provide reports, and update the volume database to match the results of the inventory. This simplifies administration, by permitting you to quickly determine the contents of a robot. This also automates the configuration process.
Media Manager can also inventory a robotic library that does not support barcodes or that contains volumes that do not have readable barcodes. In these cases, you use the physical inventory utility (vmphyinv).
◆ Automatic Volume Recognition
Media Manager compares the media IDs on media with media IDs that are requested and then assigns the correct media to requests. This is an essential part of providing hands-off operation for both robots and standalone drives.
◆ Automatic Scanning of Media Labels
Media Manager scans the labels of media that are in drives and displays them in the Device Monitor. This is useful if you want to know whether a certain drive contains a particular volume.
◆ Volume Pools
6 NetBackup Media Manager System Administrator’s Guide for Windows
Page 41
Media Manager Hosts
During configuration, you can assign media to pools that are reserved for specific uses. For example, media can be reserved for backups of specific departments. It is also possible to create a scratch pool from which media can be allocated to other pools as they are needed.
A pool named NetBackup is created by defau lt and, unless you specify otherwise in the class or schedule, all NetBackup backup images go to media in the NetBackup pool. You can create other volume pools as desired. Other volume pools that are created by default are named None and DataStore.
◆ Volume Groups
When media is added, it is assigned (or you can assign) a volume group name that corresponds to the physical location of the media (for example, the robot that has the media). This is useful for administering groups of volumes and for tracking location. For example, when media is taken to offsite storage, you can move the media to specific standalone groups.
◆ Graphical User Interfaces for Media and Device Management
Thefollowinginterfaces(ortreenodes)areavailablefromtheNetBackup Administration Console.
◆ Device Monitor shows the current status of all drives and allows you to easily
change the state of a drive. For example, it is possible to set a drive to DOWN to prevent its use by Media Manager or reset it to clear a hang condition. You can also assign requests to drives in those instances when assignment does not occur automatically.
◆ Media provides intuitive and easy-to-use methods for managing your media,
volume pools, and volume groups.
◆ Devices provides intuitive and easy-to-use methods for managing your device
hosts, robots, and drives.
Media Manager Hosts
In the NetBackup Administration Console and in this guide, a Media Manager host (or server) is a UNIX or Microsoft Windows server that has NetBackup and Media Manager software installed. Media Manager software is automatically installed as part of the installation of NetBackup software.
Key Media Manager hosts are described in the following topics.
Chapter 1, Introduction to Media Manager
7
Page 42
Media Manager Hosts
Master Servers
NetBackup and Media Manager support both master server and media servers. A master server manages the NetBackup backups, archives, and restores. Media servers typically provide additional storage by allowing NetBackup to use the storage devices that are attached.
A master server has Media Manager software installed.
The following point applies only to NetBackup Server.
NetBackup master and media server software are both installed on the same host. This is the host where NetBackup is installed. In this case, the host acts as both a master and a media server. All related databases are also located o n that host.
The following point applies only to NetBackup Enterprise Server.
You can have multiple master and media servers in your configuration. Typically a master server controls multiple media servers. You should manage your media servers from the master server point of view .
Media Servers
A host with Media Manager software installed and devices attached is termed a media server. The use of Media servers can increasesystem performance by distributing network loads.
Media servers can also be referred to as device hosts. Regular media servers are licensed by VERITAS, and can back up their own data or data from other network clients. Also see “SANMediaServers”onpage8.
The following points apply only to NetBackup Enterprise Server.
You can have multiple media servers in your configuration. A media server can also just be a host that provides the robotic control for a robot (known
as a robot control host).
SAN Media Servers
This is a NetBackup Enterprise Server topic. VERITAS also licenses SAN media servers that can only back up their own data to shared
drives—no backing up of data residing on other clients is allowed.
8 NetBackup Media Manager System Administrator’s Guide for Windows
Page 43
Media Manager Hosts
Volume Database Host
A volume database host is a Media Manager host where the volume database is located. This database is the repository for all Media Manager volume configuration information about the media in storage devices.
The following point applies only to NetBackup Server.
The Media Manager volume database i s located on the host where NetBackup is installed.
The following points apply only to NetBackup Enterprise Server.
All servers where Media Manager is installed (even if the server does not h ave a ny drives or robots attached) can have volume databases and can contain volume information. VERITAS recommends that you centralize the information on one Media Manager host (this host is usually the NetBackup master server).
Caution Although it is possible to maintain separate volume databases on multiple
hosts, administration of these databases is more difficult, as is merging the databases later. The vmdb_merge command can be used to merge volume, pool, and media databases. See the NetBackup commands guide for details.
Also, shared drive (SSO) configurations require that one volume database host is used for all servers where a shared drive is configured.
Thereshouldbeonlyonevolumedatabasehostperglobaldevicedatabasehost(see “Global Device Database Host” on page 9), and both of these key databases should be located on the same server. This server is known as the Media and Device Management Domain (MDM Domain) server.
Global Device Database Host
This is a NetBackup Enterprise Server topic.
TheglobaldevicedatabasehostisaMediaManagerhostwheretheglobaldevice database is located. This database is the repository for Media Manager device configuration information.
The following methods are typically used to configure devices:
◆ Device discovery (Device Configuration wizard)
◆ Auto-configuration (Device Configuration wizard)
◆ Manual configuration (using the NetBackup Administration Console or tpconfig)
For device configuration to work properly (particularly where devices are connected to many servers) a single host must serve as the repository for this global device configuration information.
Chapter 1, Introduction to Media Manager
9
Page 44
Media Manager Storage Devices
Also, there should be only one volume database host (see “Volume Database Host” on page 9) per global device database host and both of these key databases should be located on the same server. This server is known as the Media and Device Management Domain (MDM Domain) server.
When you install NetBackup, the default option is to have the master server configured to be the global device database host. If your environment contains multiple master servers, you can designate a different server to be your global device database host during the installation.
The tpautoconf command has options to preview and merge existing device databases. See the NetBackup commands guide for details.
Media Manager Storage Devices
Drives and robots must be added to the Media Manager configuration before NetBackup can use them. Devices can be added using either of the following methods with the NetBackup Administration Console:
◆ TheDeviceConfigurationWizard(thisistherecommendedmethod).Thiswizardis
available from the right pane of the NetBackup Administration Console, if you have selected Media and Device Management in the tree pane.
◆ Using Devices (use the new robot and new drive menu items).
You may also use the tpconfig command from the Windows command prompt to add devices(seetheNetBackupcommandsforWindowsreferenceguide).
Media Manager Volumes
The tapes that Media Manager uses are referred to as volumes in NetBackup. Volumes are assigned media IDs and other attributes that are required for tracking and management. You can do the assignment manually or let Media Manager do it automatically.
These methods are explained in the following chapters:
◆ “Managing Media” on page 89.
◆ “Managing Media in Robots” on page 151.
The following are examples of the events that occur when NetBackup requests a volume for a backup:
◆ If NetBackup requests an exis ting volume, Media Manager locates the volume and
performs the steps necessary to have the volume mounted in a drive.
10 NetBackup Media Manager System Administrator’s Guide for Windows
Page 45
Media Manager Volumes
If NetBackup requests a new volume, Media Manager looks for a volume of the
◆
requested density and assigns it to NetBackup before mounting it in a drive. Once a volume is assigned to NetBackup, other applications cannot use it until NetBackup no longer needs the backups on the volume .
◆ If Media Manager does not have a record of a volume suitable for the request, an error
occurs and you must configure a volume to use before the operation can proceed.
Mounting and Using Volumes
Mounting a volume consists of the steps necessary to make it available for reading or writing data. After finding a volume, Media Manager mounts it as follows:
◆ Ifthevolumeisinarobot,MediaManagerissuesthecommandsthatmovethe
volume to a drive, position the heads to the beginning of the volume, and assign it to the request. No manual intervention is required.
◆ Ifthevolumehappenstobeinastandalonedriveandhasbeenrequestedby
NetBackup, Media Manager automatically mounts and assigns it. Again, no manual intervention is required.
◆ If the volume is not in a robot or a standalone drive, Media Manager displays a
pending request in the Device Monitor. The operator must then find the volume and do one of the following:
◆ Check the Device Monitor to find a suitable drive, and mount the requested
volume in that drive.
◆ Move the volume into the robot and update the volume configuration to reflect
the correct location for the media, and resubmit the request.
◆ The administrator or operator can then find the required volume, insert it into the
drive, and assign the drive to the request with the Device Monitor. This situation will exist, for example, if the requested volume happens to be off site.
In robots that have barcode readers, Media Manager verifies the barcode to ensure that the robot loads the correct volume. If the barcode on the volume does not match the barcode in the Media Manager volume database, it is considered an error and the operation is stopped.
Note Media Manager is involved only in backups that are stored on removable media. If
the defined NetBackup storage unit is on magnetic disk, NetBackup sends the backup to the file path specified during configuration of the storage unit and records the location in the NetBackup media database. Media Manager, i n this instance, does not have a record of the storage location.
Chapter 1, Introduction to Media Manager
11
Page 46
Media Manager Administration Utilities
Media Manager Administration Utilities
Utilities for managing media and devices are available in the NetBackup Administration Console.
There are also some operations that may require you to use a command from the Windows command prompt (see the NetBackup commands for Windows reference guide). These operations are not required in the normal use of NetBackup.
Starting the Media Manager Administration Utilities
▼ To Start the administration utilities
1. Log on to a Windows workstation as a member of the Administrators group.
2. From Start > Programs, select VERITAS NetBackup > NetBackup Administration
Console. The NetBackup Administration Console appears on your workstation. The NetBackup Administration Console is the starting point for administering
NetBackup.Theleftpaneoftheconsolewindowhasanodeforeachmajorareaof NetBackup administration (including nodes for optional VERITAS software).
3. Click the Media and Device Management node. This node contains the Media
Manager utilities. The right pane initially contains the key NetBackup wizards that apply to this node.
The following figure shows these Media Manager wizards. These wizards have the following links:
◆ Configure Storage Devices
◆ Configure Volumes
12 NetBackup Media Manager System Administrator’s Guide for Windows
Page 47
Media Manager Administration Utilities
The Media and Device Management node
Media and Device Management wizards
4. Expand Media and Device Management to view the additional Media Manager
nodes. Clicking a node displays information related to that node in the right pane. The menus and buttons contain commands relevant to each selected node.
Note See the NetBackup system administrator’s guide for Windows servers for details on
the other NetBackup Administration Console nodes, other NetBackup administration utilities, and menu commands.
◆ Click Device Monitor. The device monitor has commands for monitoring the
operation of storage devices. “Monitoring Storage Devices” on page 209 explains how to use the Device
Monitor.
◆ Click Media. This node has commands for managing media.
“Managing Media” on page 89 and “Managing Media in Robots” on page 151 explain how to manage your media.
◆ Click Devices. This node has commands for configuring and managing hosts,
robots, and drives.
Chapter 1, Introduction to Media Manager
13
Page 48
Device and Media Configuration Overview
“Configuring Storage Devices” on page 17 explains how to configure robots and drives.
Shortcut Menus
Pressing the right-mouse button while the pointer is over sections of the NetBackup Administration Console, displays shortcut menus. Different menus appear depending on where your pointer is positioned.
Device and Media Configuration Overview
The following summarizes the steps for configuring storage devices and media. Complete your NetBackup policy and storage unit configuration as explained in the NetBackup system administrator’s guide for Windows servers.
▼ To configure devices and media
1. Install NetBackup software by following the instructions in the installation program.
Media Manager is installed as a part of NetBackup.
2. Use the Device Configuration Wizard (select Configure Storage Devices in the right
pane of the NetBackup Administration Console) to configure your robots and non-shared drives. For more information, see “Using the Device Configuration Wizard” on page 41.
Tomanually configuredevices not supportedby this wizard,you must use the menus of the Devices node. See “Configuring Storage Devices” on page 17.
3. This step applies only to NetBackup Enterprise Server.
To configure shared drives (SSO), you can use the Device Configuration Wizardor the the Shared Drive wizard. For more information, see “Adding Shared Drives” on page 57.
4. Use the Volume Configuration Wizard (select Configure Volumes intherightpaneof
the NetBackup Console) to define the media that you will be using in the storage devices. This wizard configures volumes for all supported standalone drives and robots.
When you logically add a new volume (or move volumes) in a robot that supports barcodes, a scan occurs and the Media Manager volume database is updated to reflect the contents of the robotic library.
14 NetBackup Media Manager System Administrator’s Guide for Windows
Page 49
To manually configure volumes for devices, use the menus of the Media node. See “Managing Media” on page 89 and “Managing Media in Robots” on page 151 for advanced robot inventory operations.
Security Issues
See the topic, “Media Manager Security” on page 326 for important information about security.
Media Manager security topics include the following:
◆ The relationship with NetBackup authentication/authorization security.
◆ Controlling user access to vmd (the Volume Manager service).
◆ Controlling user access to Media Manager robotic functions.
Security Issues
Chapter 1, Introduction to Media Manager
15
Page 50
Security Issues
16 NetBackup Media Manager System Administrator’s Guide for Windows
Page 51
Configuring Storage Devices
The device management window allows you to add, configure, and manage the devices that Media Manager uses.
This chapter explains how to attach drives and robotic libraries and configure Media Manager to use them. The topics in this chapter are listed below. If this is the first time you have configured devices, read the topics in the order they are presented in this chapter.
◆ Starting Device Management
◆ Using the Device Management Window
◆ Performing Initial Device Configuration
◆ The following topic applies only to NetBackup Enterprise Server.
Administering Devices on Other Servers
◆ The following topic applies only to NetBackup Enterprise Server.
The Global Device Database Host
◆ Using the Device Configuration Wizard
◆ Adding Robots
2
◆ The following topic applies only to NetBackup Enterprise Server.
Adding Shared Drives
◆ Adding Drives
◆ Managing Your Device Configuration
◆ Printing Your Device Configuration
◆ Robot and Drive Configuration Examples
17
Page 52
Starting Device Management
Starting Device Management
In the NetBackup Administration Console, click Media and D e vice Management > Devices. The device management window similar to the following appears:
Inadditiontothetreepaneontheleft,thefollowingtwopanesaredisplayedontheright when you start device management:
◆ A pane showing global topology.
◆ Apaneshowingdevices.
Using the Device Management Window
The following topics provide an overview of the window’s contents:
◆ Menus and Commands
◆ Toolbars
◆ Tree Pane
◆ Global Topology Pane
◆ Devices Pane
18 NetBackup Media Manager System Administrator’s Guide for Windows
Page 53
Using the Device Management Window
Status Bar
◆
◆ Shortcut Menus and Commands
◆ Customizing the Window
◆ Allowable Media Manager Characters
Menus an d Commands
The device management window has available the menus and commands shown in the following table. Review the Note column for any restrictions.
The items on the menus are enabled based on the objects that are currently selected in the tree pane or topology pane, or which tab is selected in the devices pane. For example, if the robot tab is selected in the devices pane and a robotic library is selected in the list, Inventory Robot is enabled on the Actionsmenu.
Device Management Menus and Commands
Menu Commands Note
File Change Server - Displays a dialog that allows you to change to a
different server that is running NetBackup. See “Administering Devices on Other Servers” on page 36 for details.
New Console - Starts another instance of NetBackup Administration Console.
NewWindowfromHere- Starts another instance of the NetBackup Administration Console node that was active.
Login as New User - Log into NetBackup as a different user without exiting NetBackup. This is useful if a NetBackup Administrator wants to log in again as the Security Administrator to administer Access Management. Controlling access to NetBackup is discussed in the NetBackup system administrator ’s guide.
Backup, Archive, and Restore - Starts the NetBackup backup, archive,and restore interface.
MS SQL Client - Shortcut to access the SQL server NetBackup client, if it is installed on the selected server.
Print Setup - Displays a setup dialog for printing. Print Preview -Previewstheprintimage. Print - Prints the topology pane or devices pane (when one of these
panesisselected).
Close - Closes the current window. Exit - Closes all open windows.
Chapter 2, Configuring Storage Devices
19
Page 54
Using the Device Management Window
Device Management Menus and Commands (continued)
Menu Commands Note
Edit Undo - Allows you to cancel the last action.
Cut, Copy, Paste - Commands for managing items in the display
lists. New - Displays a dialog to add an item of the type that is currently
selected. Change - Displays a dialog for changing the configuration of the
selected items.
Delete - Deletes selected items from the configuration. Find, Find Next, Find Prev, Find All - Commands for finding items
in the display lists.
View Contains commands for specifying your viewing preferencesfor the
device management window, including showing and hiding the toolbar or tree, showing and hiding robots, sorting, filtering, column layout, using the topology window, and refreshingthe display. See “Customizing the Window” on page 32.
Actions New - Displays choices for adding robots or drives to a
configuration.
You can also add shared drives to a configuration. Applies only to
Global Device Database - Displays a sub-menu that allows you to synchronizethe entries in the global device database with the device configuration database. Synchronizing databases is normally not necessary, but can be done if you are experiencing problems and have made recent configuration changes that may not have been recognized.
Also displays choices for adding or removing device hosts from the global device database. See “The Global Device Database Host” on page 39.
Change Standalone Volume Database Host - Displays a dialog to change the volume database host for standalone drives.
Inventory Robot - Displays a dialog with choices for performing an inventory of the selected robot or updating the volume configuration to match the contents of the robot.
NetBackup Enterprise Server.
Applies only to NetBackup Enterprise Server.
Applies only to NetBackup Enterprise Server.
20 NetBackup Media Manager System Administrator’s Guide for Windows
Page 55
Using the Device Management Window
Device Management Menus and Commands (continued)
Menu Commands Note
Configure Shared Drive - Starts a wizard that guides you through the steps involved in adding a shared drive, changing a shared drive, or changing a non-shared drive to a shared drive (SSO option).
Using this wizard is not the preferred method for adding shared drives. See “Adding Shared Drives” on page 57 first, if you are configuring shared drives.
Drive Cleaning - Displays a sub-menu with choices for performing drive cleaning functions.
Diagnose - Displays a dialog with choices for running diagnostic tests on a drive.
Stop/Restart Device Manager Service - Stops and restarts the NetBackup Device Manager service.
View SANPoint Control - Launches VERITAS SANPoint Control This web-based application helps you locate the cause of problems on your SAN or direct fibre-channel attached storage. See “Using SANPoint Control to Investigate SAN Problems” on page 75.
Help Help Topics - Provides online help information for the NetBackup
Console.
Troubleshooter - Helps you to debug errors. VERITAS W eb Page - Displays the VERITAS web page, if the host
has a browser configured. License Keys - Provides information about your active and
registered license keys. About A dministration Console - Displays program information,
version number,and copyright information. You can click More for detailed information.
Current NBAC User -ProvidesNetBackupAccessControl information for the current user. Gives the permissions for the user that you are currently logged in as.
Applies only to NetBackup Enterprise Server.
TM
.
Toolbars
The toolbar buttons of the device management window provide shortcuts for commands that are on the menus. Also see “Customizing the Window” on page 32.
Chapter 2, Configuring Storage Devices
21
Page 56
Using the Device Management Window
▼ To show or hide the toolbar buttons
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Click View > Toolbar.
▼ To customize the toolbar buttons
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Click View > Customize....
In the Customize Toolbar dialog you can reorder the buttons on the current toolbar, add buttons, or remove toolbar buttons. Use Default to reset the buttons on the toolbar.
Tree Pane
ThetreepaneforDevices contains nodes for Hosts, Ro bots,andStandalone Drives.You can select items in the tree pane or the Topology pane in conjunction with the tabs of the Devices pane to filter the lists that are shown in the Devices pane.
The following figure shows just the tree pane and contains an expanded view of the Devices node:
If you select a device host, robot, or Standalone Drives, the Topology pane shows the pertinent connections highlighted and the Devices pane shows information filtered for that specific selection.
Note Selecting an item in the Tree pane (for example, a specific robot) does not enable th e
Robots tab in the Devices pane.
The following point applies only to NetBackup Enterprise Server.
22 NetBackup Media Manager System Administrator’s Guide for Windows
Page 57
Using the Device Management Window
You can view or configure devices on another master or media server. See “Administering Devices on Other Servers” on page 36 for more information.
Global Topology Pane
A description bar is displayed at the top of the topology pane. Tool tips are also provided for all of the objects displayed in the topology pane.
Your view and use of the topology pane can be customized. See “Customizing the Window” on page 32. These commands are also available using the right mouse button in the topology pane.
The topology view shows how devices are configured to the server being administrated, by showing images of servers and devices. The topology information is taken from the Media Manager global device database and is displayed in this pane.
Topology Icons
The following are some of the images that can appear in the topology pane.
Description Topology Image
NetBackup media server (or SAN media server)
Robot
Robotthatispartiallyconfigured
Volumedatabase (robot media)
Drive
Chapter 2, Configuring Storage Devices
23
Page 58
Using the Device Management Window
Drive that is partially configured
Drive that is shared (NetBackup Enterprise Server)
Topology Connections
Connections in the topology indicate physical and logical connections of the devices, as follows:
◆ Media server (or SAN media server) to robotic library and drive relationships are
indicated. A line attaches a robot arm to the media server that has robot control.
◆ Drives that are physically located in a robotic library are shown directly below the
robotic library. Standalone drives are represented as individual drive objects.
◆ A line attaches a drive to the servers that are configured to use it. Robot to server
connections and robot to volume database connections are always shown.
◆ Media is represented as in a robotic library. A line attaches the media to the server
doing media management.
◆ The topology also indicates robotic library to volume database host connections.
Selecting Topology Objects
Selecting objects in the topology pane is also one of the methods to filter the contents of the lists shown in the Devices pane.
Multiple objects of the same type can be selected by pressing the Ctrl key and selecting another object. If the Ctrl key is used and an object of a different type is selected, the selection is allowed and the other objects will not be selected. If the Ctrl key is not used and an object i s selected, the previous selection will be unselected.
Selecting an object will highlight the connecting lines from the object to all other objects to which it is connected, as follows:
◆ Clicking on a drive will highlight the connection to the server where it is attached.
◆ Clicking on a server will highlight connections to all robots, media, and drives that are
connected or configured to the server.
The following point applies to NetBackup Enterprise Server.
◆ Clicking on a shared drive will highlight connections to all servers that are configured
to use the drive.
24 NetBackup Media Manager System Administrator’s Guide for Windows
Page 59
Using the Device Management Window
Devices Pane
ThelowerrightpanecontainstabsforDrives,Robots,andHosts. These tabs allow you to select different views of your configuration. Information in the devices pane is taken from the Media Manager global device database and the local device databases.
You can use the tree pane or the topology pane in conjunction with the tabs to filter the lists shown in this pane. Selecting an item in the tree (for example, a specific robot) does not enable the Robots tab in the devices pane.
Managing the Devices Pane
The Edit and View menus have commands for finding or showing items. These commandsareuseful if you are managing many devices.Some of thecolumns are initially hidden by default.
▼ To rearrange or hide columns
❖ Click View > Columns > Layout
Using the Drives Tab
The drives list allows you to view detailed information about drives configured with NetBackup.
To update the drives list with more detailed information, a drive must be selected in the topology pane. You can select a drive in the topology explicitly or implicitly by selecting a robotic library. The drives list will then be updated with the objects that are selected in the topology.
The following table describes the columns in the drives list. Check the Note column for any restrictions.
Drives List
Column Description Note
Drive Name Contains the configured name of the drive.
If the drive is configured as a shared drive (SSO), the icon for thedriveappearsasashareditem.
If the icon shown for a drive contains a red arrow, the current server is not the volume database host for the drive. In this case, it is recommended to change to the correct server before adding volumes for this drive.
Applies only to NetBackup Enterprise Server.
Chapter 2, Configuring Storage Devices
25
Page 60
Using the Device Management Window
Drives List (continued)
Column Description Note
Device Host Contains the name of the device host (media server) where
this drive is attached.
Drive Type Contains the type of drive. For example, 4MM.
If the drive is partially configured, PCD is shown in this column. See “Managing Partially-Configured Devices” on page 45 for details.
Robot Type Specifies the type of robot that contains this drive. For
example, TL4. NONE in this column means that the drive is a standalone
drive. If the robot is partially configured, PCR is shown in this
column. See “Managing Partially-Configured Devices” on page 45 for details.
Robot Number Contains the number of the robot. If the robot type is NONE,
this column is blank.
Robot Drive
Specifies the number of the drive in the robot.
Number
For ACS, TLH, and TLM robot types, the robot drive number is not displayed.
Applies only to NetBackup Enterprise Server.
Vendor Drive Identifier
ACS Contains the ACS library software index that identifies the
For TLM robots, this column contains the DAS/SDLC drive name.
For TLH robots, this column contains the IBM device number.
robot where this drive is located.
Applies only to NetBackup Enterprise Server.
Applies only to NetBackup Enterprise Server.
LSM Contains the ACS Library Storage Module where this drive is
located.
Applies only to NetBackup Enterprise Server.
Panel Contains the ACS robot panel where this drive is located. Applies only to
NetBackup Enterprise Server.
26 NetBackup Media Manager System Administrator’s Guide for Windows
Page 61
Using the Device Management Window
Drives List (continued)
Column Description Note
Drive Contains the ACS library software physical number of the
drive.
Applies only to NetBackup Enterprise Server.
Drive Path Contains the path for the drive. For example, Tape5.
Serial Number Contains the drive serial number, if the drive reports a serial
number .
World Wide ID Contains a unique identifier that is assigned to each device.
Some drives may not report this identifier.
Shared Yes, means this drive is configured as a shared drive.
No, means the drive is not a shared drive.
Applies only to shared drives (SSO) on NetBackup Enterprise Server.
Drive Status Contains the current status of the drive. Status can be UP or
DOWN.
Port This column contains the SCSI port number of the drive. Applies only to
NetBackup Windows servers.
Bus This column contains the SCSI bus number of the drive. Applies only to
Target This column contains the SCSI target number (or SCSI ID) of
the drive.
Lun This column contains the SCSI logical unit number of the
drive.
Last Mount Contains the last time a volume was mounted in the drive.
Chapter 2, Configuring Storage Devices
NetBackup Windows servers.
Applies only to NetBackup Windows servers.
Applies only to NetBackup Windows servers.
27
Page 62
Using the Device Management Window
Drives List (continued)
Column Description Note
Mount Time Contains the total accumulated mount time (in hours).
Cleaning Frequency
Last Cleaning Time
Cleaning Comment
TapeAlert Enabled
Volume Header Device
Contains the cleaning frequency for the drive (in hours).
Contains a dash (-) for shared drives or robots that do not support frequency-based cleaning.
Contains the date that the drive was last cleaned.
Contains the message, NEEDS CLEANING, if a cleaning frequency was defined for the drive and the value for Mount Time is greater than the frequency; or the TapeAlert CLEAN_NOW flag is set.
Contains Yes, if TapeAlert is enabled.
This column specifies the volume header device path for the drive.
Applies only to NetBackup Enterprise Server.
Applies only to optical disk drives on some NetBackupUNIX servers.
Drive
Contains any user comments added for the drive.
Comments
Inquiry Information
Contains device information returned from the device. This information is used to identify the device. For example, vendor ID, product ID, and product revision.
NDMP Host Contains the name of the NDMP control host.
Drive Index Drive index assigned to the drive during configuration.
28 NetBackup Media Manager System Administrator’s Guide for Windows
Page 63
Using the Device Management Window
Using the Robots Tab
The robots list allows you to view detailed information about robots configured with NetBackup. Initially, all r obots in the global device database are listed in the robot list. However , only information found in the global device database will be displayed in the list.
To update the robot list with more detailed information, a robot must be selected in the topology pane or in the tree pane. You can select a robot in the topology explicitly or implicitly by selecting a drive in the robot or the media server that the robot is connected to. The list will then be updated with the objects that are selected in the topology.
The following table describes the columns in the robots list. Check the Note column for any restrictions.
Robots List
Column Description Note
Robot Name Contains the type and number of the robot, for example
TLD(3). If the robot is partially configured, PCR is shown in this
column. For example, PCR(3). See “Managing Partially-Configured Devices” on page 45 for details.
If the icon shown for a robot contains a red arrow, the current server is not the volume database host for the robot. In this case, it is recommended to change to the correct server before adding volumes for this device.
DeviceHost Containsthenameofthedevicehostwherethisrobotis
attached.
Robot Type Contains the type of robot. See “Media Manager Robot
Types” on page 250 for a list of supported robot types. If the robot is partially-configured, PCR is shown in this
column.
Robot Number Number of the robot.
Volume Database Host
Serial Number Contains the robot serial number, if the robot reports this
Containsthe name of the volume database host that is used to track the volumes in this robot
information.
Applies only to NetBackup Enterprise Server.
Chapter 2, Configuring Storage Devices
29
Page 64
Using the Device Management Window
Robots List (continued)
Column Description Note
Robotic Path Contains the path for the robot if one exists. For example,
changer0.
Robot Control Host
Port This column contains the SCSI port number of the robot. Applies only to
Bus This column contains the SCSI bus number of the robot. Applies only to
Target This column contains the SCSI target number (or SCSI ID) of
Lun This column contains the SCSI logical unit number of the
Inquiry Information
Contains the name of the host that is providing the robotic control.
the robot.
robot.
Contains device information returned from the device that is used to identify the device. For example, vendor ID, product ID, and product revision.
Applies only to NetBackup Enterprise Server.
NetBackup Windows servers.
NetBackup Windows servers.
Applies only to NetBackup Windows servers.
Applies only to NetBackup Windows servers.
Using the Hosts Tab
The hosts list allows you to view detailed information about the servers that are referenced in your Media Manager configuration.
To update the hosts list with more detailed information, a host must be selected in the topology pane or in the tree pane. You can select a host in the topology explicitly or implicitly by selecting a robot. The hosts list will then be updated with the objects that are selected in the topology.
30 NetBackup Media Manager System Administrator’s Guide for Windows
Page 65
Using the Device Management Window
The following table describes the columns in the hosts list:
Hosts List
Column Description
HostName Containsthenameofthedevicehost.
Connection Status Contains the current NetBackup connection status for this server. This
status field can contain Connected, Not Connected, or the text of a connection error message.
Standalone Volume Database Host
Version Contains the NetBackup software version.
Contains the name of the volume databasehost for all of the standalone drives controlled by this device host.
Status Bar
The status bar appears at the bottom of the NetBackup Console window. The status bar
◆ Shows tool tips (when the mouse is over a toolbar icon or an object)
◆ Indicates the name of the master server.
◆ Indicates if you are connected to the master server.
▼ To show or hide the status bar
❖ Click View > Status Bar.
Shortcut Menus and Commands
Shortcut menus work in the context of what device is currently selected in the tree pane or topology pane, or which tab is selected in the devices pane. Shortcut commands are also available on the menus or toolbars.
▼ To display a shortcut menu
❖ Click the right mouse button while the pointer is over a pane or a selection of a pane.
Help for the topology pane is available using the right mouse button in the topology pane (select Topology Info).
Chapter 2, Configuring Storage Devices
31
Page 66
Using the Device Management Window
Short Cut Menu
Customizing the Window
The View menuhasoptionsfor sorting, filtering,and changing the layoutand appearance of the panes.
See the NetBackup administrator’s guide for UNIX or the NetBackup administrator’s guide for Windows for more details.
Viewing and Rearranging Columns
▼ To show or hide co lumns, or rearrange the order of columns
❖ Click View > Columns > Layout.
Changing the View of the Topology Pane
These commands are also available using the right mouse button in the topology pane.
32 NetBackup Media Manager System Administrator’s Guide for Windows
Page 67
Using the Device Management Window
To fit the topology diagram to the pane
▼
Thisprocedurewillfitthediagramtothepane,andnotusethedefaultsizeonstartup.
1. Click View > Options > Devices.
2. Select Fit topology to window on startup.
▼ To enlarge the topology diagr ams
This command can be done multiple times.
❖ Click View > Zoom > Zoom In.
▼ To decrease the size of the topology diagrams
This command can be done multiple times.
❖ Click View > Zoom > Zoom Out.
▼ To size the topology diagram to the si ze of the current pane
❖ Click View > Zoom > Fit to Window.
▼ To select objects and focus on a portion of the topology diagr am
1. Click View > Zoom > Overview Window.
A copy of the topology diagram appears in a secondary window.
2. Use the mouse to select desired objects or portions of objects in the configuration. The
selected objects will be the focus of the main topology pane, allowing you to focus on areas of the topology diagram.
▼ To show only the connection for a selected device
Use this option to show the connection for a selected device, rather than showing all connections in the topology.
❖ Click View > HighLighted Connections Only.
▼ To show all of the connections in the topology
❖ Click View > All Connections.
Chapter 2, Configuring Storage Devices
33
Page 68
Performing Initial Device Configuration
Allowable Media Manager Characters
The following set of characters can be used in user-defined names, such as drive comments, host names, and drive names that you enter when creating these Media Manager entities. These characters must be used even when specifying these items in foreign languages.
Do not use a minus as the first character. Spaces are only allowed in a comment for a drive.
◆ Alphabetic (A-Z and a-z)
◆ Numeric (0-9)
◆ Period (.)
◆ Plus (+)
◆ Minus (-)
◆ Underscore (_)
Performing Initial Device Configuration
▼ To attach devices to a Windows media server
The following steps d escribe a general method for attaching devices to a Windows media server. The device applications on the Windows server that you use in these steps may be different depending on your operating sy stem.
1. Use the appropriate Windows application to obtain information on any currently
attached SCSI devices.
2. If you are attaching a new robotic library or drive to a Media Manager media server,
follow the manufacturer’s instructions for attaching the device.
3. Shut down the media server and physically attach the supported device, ensuring
that SCSI targets and termination settings are consistent with adapter card and peripheral vendor recommendations.
4. Reboot the server and answer the prompts for adapter card peripheral configuration
options. Watch the display to ensure that the adapter card recognizes the attached peripherals.
Note Some devices (for example, Quantum DLT4500) may require that nonzero logical
unit numbers are enabled in the adapter card configuration.
34 NetBackup Media Manager System Administrator’s Guide for Windows
Page 69
Performing Initial Device Configuration
5. If you are adding drives, install tape drivers and use the appropriate Windows
application to verify that the drive was recognized.
Note If you are adding Sony AIT drives, the settingsfor dip switches 1-4 should be left at
the default setting (all switches off).
You can download the latest 32-bit tape drivers and tape installer from http://support.veritas.com. Drivers are also available on the NetBackup installation CD.
Search on the keywords tape device installer. These drivers support the tape devices listed in the compatibility lists on this web site. NetBackupTapeDeviceDriverInstall.exe will run only if NetBackup has been installed.
Also see the Microsoft Windows chapter of the NetBackup Media Manager device configuration guide for more information on 32-bit tape drivers.
6. Add the storage devices to your Media Manager configuration. If this is the first time
you have configured Media Manager devices, note the following:
a. This step applies only to NetBackup Enterprise Server.
If you are adding the device to a remote host, also see “Administering Devices on Other Servers” on page 36.
b. Depending on the type of device you are adding, proceed to one of the following
topics:
◆ “Using the Device Configuration Wizard” on page 41.
◆ “Adding Robots” on page 46.
◆ “Adding Drives” on page 58.
◆ “Adding Shared Drives” on page 57.
c. Make your device configuration changes.
d. If you use the Device Configuration wizard, this step is done by the wizard.
Stop and restart the NetBackup Device Manager service using Actions > Stop/Restart Device Manager.
e. This step applies only to NetBackup Enterprise Server.
In the dialog, the arrow in the Device Host box allows you to select a device host. This dialog also shows the current status of this host.
Chapter 2, Configuring Storage Devices
35
Page 70
Administering Devices on Other Servers
Administering Devices on Other Servers
This is a NetBackup Enterprise Server topic.
Initially, you can manage the storage devices that are configured on the server where you are running the NetBackup Media Manager interface. In the following figure, the administrator is running the NetBackup Administration Console o n server shark and managing devices on host eel.
shark
Media Manager
Device Database
Administration Interface
Drives
eel
Media Manager
Device Database
Drives
yak
Media Manager
Device Database
Robots
Drives
You can administer devices that are attached to other servers, if these servers are in the same hardware configuration and are using the same global device database host. Select thedeviceorhostthatyouwanttoadministerinthetreepaneoftheNetBackup Administration Console.
You can also change from the current server to a different master or media server. If you change from a NetBackup Enterprise Server to a NetBackup Server, the functionality available on the new server is limited to the functionality supported by NetBackup Server.
If you change from a NetBackup Server to a NetBackup Enterprise Server, complete functionality is available on the new server.
▼ To change to a different master or media server
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Click File > Change Server.
36 NetBackup Media Manager System Administrator’s Guide for Windows
Page 71
Administering Devices on Other Servers
(You can also click the arrow to the right of the Change Servericon on the toolbar and select one of the servers shown in the list).
3. In the dialog that appears, do one of the following to specify the server that you want
to monitor.
◆ Enter the name of the server.
◆ Select a server from the servers shown in the list.
◆ Click Browse and select a server.
◆ Login to the current server using a different user name.
◆ Login to a different server using a different user name.
You can also click Remove to delete a server from the list.
4. Click OK.
The name of the new server appears, and the topology and devices panes show device information for the new server.
In addition to using File > Change Server to manage devices on other servers, you can use File > Login as New User. See “Menus and Commands” on page 19.
Media Manager Security
For Media Manager to access media and device management functionality on another host, you may need to add a SERVER entry to the vm.conf file on the remote host.
SERVER entries are used for Media Manager security. If there are no SERVER entries and authentication is not enabled, any host can perform media and device management on the host. You can add entries allowing only specific hosts to remotely access those capabilities.
If the vm.conf File on a Remote Host Contains Then
No SERVER entries and authentication is not enabled
SERVER entries You must add a SERVER entry for the host where you are running
Any host can perform media and device management on this host. It is not necessary to make any additions to vm.conf.
(the server you logged into) the NetBackup Administration Console (if an entry is not present).
Chapter 2, Configuring Storage Devices
37
Page 72
Administering Devices on Other Servers
vmd Considerations
vmd is the Media Manager volume daemon on UNIX servers and the NetBackup Volume Manager service on Windows servers. Device configuration changes, even those made local to a server,may require vmd to be running. It is recommended that vmd be running at all times, including when changes are being made to the Media Manager device configuration.
Media Manager authentication/authorization may affect systems where NetBackup authentication/authorization has been enabled.
Connections to vmd will fail if authentication/authorization are enabled, an AUTHORIZATION_REQUIRED entry is present in vm.conf,andthecallerofvmd does not have the required permission to use vmd functions.
▼ To enable authentication/authorization in NetBackup (but not in Media Manager)
You can do either of the following:
❖ Add SERVER entries in vm.conf.
❖ Have no SERVER and no AUTHORIZATION_REQUIRED entries in vm.conf.
See“MediaManagerSecurity”onpage311formoreinformationonthefollowingtopics:
◆ The relationship with NetBackup authentication/authorization security.
◆ Controlling user access to vmd (the Media Manager volume daemon).
◆ Controlling user access to Media Manager robotic daemons and services.
Example SERVER Entries
Assume that you have three hosts, named eel, yak, and shark; and that NetBackup authentication is not enabled.
You want to centralize device management on host shark and also permit each host to manage its own devices.
◆ The vm.conf file on shark contains the following:
SERVER = shark
The vm.conf file on shark does not require any additional SERVER entries, because all device management for shark will be performed from shark.
◆ The vm.conf file on eel contains the following:
SERVER = eel
38 NetBackup Media Manager System Administrator’s Guide for Windows
Page 73
SERVER = shark
This allows eel to manage its own devices and also permits shark to access them.
◆ The vm.conf file on yak contains the following;
SERVER = yak
SERVER = shark
This allows yak to manage its own devices and also permits shark to access them.
The Global Device Database Host
The global device database is the repository for Media Manager device configuration information.
A Si ngle Host is Required
This is a NetBackup Enterprise Server topic.
The Global Device Database Host
Device discovery,auto-configuration,and manual configuration (for example, tpconfig) are all used by NetBackup and Media Manager to configure devices. For device configuration to work properly (particularly where devices are connected to many servers) a single host must serve as the repository for global device configuration information.
See “Media and Device Management Domain Management” on page 244 and “Frequently Asked Questions About Device Discovery” on page 269.
Note When using the Device Configuration wizard, a global device database host conflict
may be detected during device scanning. This indicates that the hosts you selected to scan do not agree on which host to store the global device information.
Also, the Devices node of the NetBackup Administration Console requires that all hosts that the node references need to be using the same global device database host. The Devices node verifies global device database consistency between any hosts that are included for device management.
The tpautoconf command has options to preview and merge existing global databases. See the NetBackup commands guide for details.
How This Host is Determined
This is a NetBackup Enterprise Server topic.
Chapter 2, Configuring Storage Devices
39
Page 74
The Global Device Database Host
When you install NetBackup, the default option is to have the master server configured to be the global device database host. If your environment contains multiple master servers, you can designate a different server to be your global device database host during the installation.
If you have multiple master servers in your configuration or did not install or upgrade your master servers before the media servers, then more than one host may have been designated as the global device database host. See “To synchronize the database” on page 40 to correct this problem.
You s hould manage your media servers from the master server point of view.
Managing This Host
The following topics explain the commands that are used to manage the global device database host.
▼ To add a device host to the database
This is a NetBackup Enterprise Server topic.
Unless you add a drive or add a robotic library, entries for each device host are not entered in the database (no host entries a re present in the database).
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Select Actions > Global Device Database > Add Device Host.
▼ To remove a device host from the database
This is a NetBackup Enterprise Server topic.
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Select Actions > Global Device Database > Remove Device Host.
▼ To synchronize the database
This procedure updates host settings in the global device database to be consistent with the device configurations of all of the device hosts in your configuration.
Synchronizing the global device database is normally not necessary, but can be done if you are experiencing problems and have made recent configuration changes to your local device hosts that may not have been recognized.
40 NetBackup Media Manager System Administrator’s Guide for Windows
Page 75
Using the Device Configuration Wizard
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Select Actions > Global Device Database > Synchronize Global DeviceDatabase.
▼ To specify a different host as the globa l device database host
This is a NetBackup Enterprise Server topic.
❖ Use the tpautoconf command.to determine the current global device database host
and to specify a different host as the global device database host. See the NetBackup commands for UNIX or NetBackup commands for Windows
reference guide for information about using the get_gdbhost and set_gdbhost options of the tpautoconf command.
tpautoconf is also used by the Device Configuration wizard to automatically discover and configure devices.
Using the Device Configuration Wizard
Using the Device Configuration wizard is the recommended method of configuring most devices. You should use this wizard to configure the following types of devices:
◆ Robots
◆ Drives
◆ Robots and drives attached to NDMP hosts
◆ Shared drives (for NetBackup Enterprise Server SSO configurations only)
Device Discovery and Device Serialization
This wizard uses device discovery to auto-configure devices . This wizard performs better if the robotic libraries and drives that you are configuring all support complete device serialization. To recognize the connected devices, device discovery needs to issue SCSI pass-thru commands to the devices.
Chapter 2, Configuring Storage Devices
41
Page 76
Using the Device Configuration Wizard
The following table shows the supported server platforms for device discovery and the configuration requirements for devices to be recognized. See the NetBackup Media Manager device configuration guide for operating system configuration details.
Server Platform Type Configuration Requirements
Microsoft Windows (Intel only)
Sun Solaris Devices must have device files, which are links to character-specialfiles
HP Tru64 UNIX Device files must exist following the naming conventions described in
HP HP9000 HP-UX Device files must exist following the naming conventions described in
A tape driver must exist for each tape device. Attached devices appear in the registry.In Windows 2000 (and later supported operating system levels), devices may be controlled by the Microsoft Removable Storage Manager (RSM), which has a public API or they may be natively-attached (SCSI-controlled).
NetBackup may be able to discover RSM-controlled devices, but will not automatically configure RSM robots.
with naming conventions that are driver and HBA-dependent. NetBackup installs its own pass-through driver called SG (SCSI Generic).
This driver must be properly configured to create device files for any device used by NetBackup, or performance and functionality is limited. Each tape or optical disk drive device also has a device file that is created for use by the system tape/disk driver interface, which must exist for all read or write I/O capability.
the Media Manager device configuration guide. The operating system creates all device files automatically.
the Media Manager device configuration guide. Some HP SCSI adapters do not support SCSI pass-thru, so devices on these adapters are not auto-discovered.
IBM RS6000 AIX The ovpass driver must be properly configured for SCSI-controlled
SGI IRIX Device files must exist following the naming conventions described in
RedHat Linux Device files must exist following the naming conventions described in
42 NetBackup Media Manager System Administrator’s Guide for Windows
robot discovery and device files must exist following the naming conventions described in the Media Manager device configuration guide.
the Media Manager device configuration guide.
the Media Manager device configuration guide. A built-in pass-thru driver (SG) is available.
Page 77
Using the Device Configuration Wizard
For important background information on device discovery, device serialization, and the Device Co nfiguration wizard, see “Frequently Asked Questions About Device Discovery” on page 269.
The following point applies only to NetBackup Enterprise Server.
When using the Device Configuration wizard a global device database host conflict may be detected during device scanning. This conflict occurs when the hosts you selected to scan in the wizard do not agree on which host stores global device information. See “The Global Device Database Host” on page 39 for more information.
Device Configuration Wizard Limitations
Note When using the Device Configuration wizard in a shared drive (SSO) environment,
the limitations are different than in a configuration without shared drives. See the NetBackup Shared Storage Option system administrator’s guide for details.
The following are limitations for this wizard:
◆ Auto-configuration works better with devices that support device serialization.
For devices to be fully configured by this wizard, each robot and drive must report a unique serial number, and each robot must report the serial number of each of the drives contained within the robot.
◆ To recognize the connected devices, device discovery used by the wizard needs to
issue SCSI pass-thru commands to the devices. Th e supported server platforms may require special operating system configuration. See the NetBackup Media Manager device configuration guide.
◆ All information required for full auto-configuration may not be available on some
systems. In this case, the wizard will do as much as possible with the limited device information. Later you need to manually configure the remaining devices.
◆ If tape drives are in use or offline, they cannot be discovered and will not be
configured.
◆ After adding or removing devices from a SCSI bus, the operating system must be
made aware of the new configuration before auto-discovery can be used. Often this requires a reboot of the operating system.
◆ The wizard can discover RSM changers, but configures them as native SCSI devices
notasRSMrobottypes.
The following points apply to NetBackup Enterprise Server.
◆ To scan and auto-configure a device, all of the device hosts (media servers or SAN
media servers) that you select in the wizard must be running NetBackup release 4.5 or later. The scan for devices will fail on hosts that are running older release levels.
Chapter 2, Configuring Storage Devices
43
Page 78
Using the Device Configuration Wizard
◆ To scan and auto-configure NDMP-attached devices for NetBackup, all of the device
hosts (media servers or SAN media servers) that you select in the wizard must be running NetBackup release 5.0 or later. For other NetBackup hosts, NDMP-attached devices must be configured manually as described in the NetBackup for NDMP administrator's guide.
◆ RemoteNDMP devices cannot be configuredusing this wizard.If you run the wizard,
all devices attached to NetBackup servers are configured as standard N etBackup devices that will not be available for remote NDMP until they are manually configured by using the NetBackup Administration Console.
◆ This wizard does not support complete auto-configuration of LMF robots and drives,
but the wizard can be used to configure drives in these robots as standalone drives.
◆ This wizard does not support complete auto-configuration of ACS or TLM robots and
drives, but the wizard can be used. See “Using the Device Configuration Wizard for Shared Drives” on page 57.
Device Mapping File
This mapping file is used by the Device Configuration wizard to automatically discover and configure new robots and drives.
In some cases, device discovery support for your new or upgraded devices may be accomplished without waiting for a patch from VERITAS. Support for some new devices only requires that you download an updated device mapping file when any device changes are made to your configuration.
Note This file does not indicate support for any of the devices, only the ability to
recognize and automatically configure them.
▼ To obtain the current device mapping file
1. Visit the VERITAS support web site (http://www.support.veritas.com) to
download the latest device mapping file for your devices.
2. Refer to the supplied README file for instructions. The files that you download are
named similar to the following files: Mappings_5_nnnnnn.TAR and Mappings_5_nnnnnn.ZIP.
Using t he D evice Configur ation Wizard to Configure Shared Drives
This is a NetBackup Enterprise Server topic.
44 NetBackup Media Manager System Administrator’s Guide for Windows
Page 79
Using the Device Configuration Wizard
See “Using the Device Configuration Wizard for Shared Drives” o n page 57. For more information on using the Device Configuration wizard in an SSO configuration, refer to the NetBackup SSO system administrator’s guide.
Starting the Device Configuration Wizard
This wizard is available from the list of wizards displayed in the right pane of the Media and Device Management window. In some cases, the wizard may leave some devices
partially configured. See “Managing Partially-Configured Devices” on page 45 for more information.
▼ To start the Device Configuration wizard
❖ Click Media and Device Management > Configure Storage Devices.
Rerunning the Device Configuration Wizard
Rerunning this wizard updates the Media Manager configuration. For example, adding a new SCSI adapter may change the path to a robotic library. A similar change to the configuration may occur if you add a new drive.
This wizard updates the Media Manager configuration to match the new configuration.
Managing Unsupported D evices
To configure devices that are not fully supported by the Device Configuration wizard, see the following topics:
◆ “Adding Robots” on page 46.
◆ “Using the Device Configuration Wizard for Shared Drives” on page 57.
◆ “Adding Drives” on page 58.
Managing Parti ally-Configured Devices
Under certain conditions, for example in the case of an unsupported robotic library or drive, the Device Configuration wizard may leave some devices as partially configured. Also if you deselect a discovered device from the tree view in the wizard, the device will be configured as partially configured.
Partially-configured drives are shown as PCD and partially-configured robots as PCR in the Drives list of the Devices window pane.
Chapter 2, Configuring Storage Devices
45
Page 80
Adding Robots
See “Using the Drives Tab” on page 25 and “Using the Robots Tab” on page 29. If this happens, ensure that you have downloaded the most recent device mapping file
from the VERITAS support web site (see “Device Mapping File” on page 44).
Adding Robots
Note Using the Device Configuration wizard is the recommended method of configuring
robots. See “Using the Device Configuration Wizard” on page 41 for more information and wizard restrictions.
When adding a robotic library and drives, the best method is to add the robot first, as explained in the followi ng procedure and then add the drives (see “Adding Drives” on page 58).
▼ To add a robot
1. Perform the steps explained in “Performing Initial Device Configuration” on page 34.
2. In the NetBackup Administration Console, click Media and Device Management >
Devices.
3. Select Actions > New > New Robot.
46 NetBackup Media Manager System Administrator’s Guide for Windows
Page 81
Adding Robots
A dialog for adding a robotic library appears. The properties that appear in this dialog vary depending on the server platform type and robot type.
4. Specify the properties for the robotic lib rary as explained in “Dialog Entries for
Adding and Changing Robots” on page 47.
5. Click OK.
A prompt appears asking whether you want to stop and restart the NetBackup Device Manager service (this also stops and restarts any robotic processes). If your changes are complete, answer yes to this prompt.
Note It is possible that stopping and restarting this service will stop any backups,
archives, or restores that are in progress.
Dialog Entries for Adding and Changing Robots
The following topics describe the properties that you specify when you add a robotic library or change a robot configuration. Some of these properties apply only to specific types of robots, types of server platforms, or NetBackup server types.
Device Host
Device Host applies only to NetBackup Enterprise Server.
Chapter 2, Configuring Storage Devices
47
Page 82
Adding Robots
▼ To specify a device host
▼ To specify a device host that is not in the list
▼ To specify a robot type
Specifies the host to which you are adding the robotic library .
❖ Click the arrow and select a host from the list.
1. Click New ...
2. In the dialog that appears, enter the name of the host that you want.
Robot Type
Specifies the type of robot that you are adding.
1. Visit the VERITAS support web site (http://www.support.veritas.com)to
locate the robot type to use for specific vendors and models.
2. Click the arrow and select from the list of types that Media Manager supports.
(Specify RSM if you are adding a RSM robot.)
▼ To specify an RSM robot type
❖ Review the following important points about using the Microsoft Windows
Removable Storage Manager (RSM):
◆ Your device host must be running a Windows operating system that supports
RSM.
◆ The Microsoft Removable Storage Manager will be in control of the robot rather
than Media Manager.
◆ A robotic library configured as an RSM ro bot, cannot also be used as a Media
Manager direct-controlled (SCSI) robot (for example, TLD).
◆ For more information on configuring and using RSM robots, see the appendix,
“Microsoft Removable Storage Manager (RSM)” on page 353.
◆ The following point applies only to NetBackup Enterprise Server.
Shared drives cannot be configured in an RSM robot, and RSM robots cannot be shared.
48 NetBackup Media Manager System Administrator’s Guide for Windows
Page 83
Adding Robots
Robot Number
Specifies a unique, logical identification number for the robotic library. This number identifies the robotic library in displays (for example, TLD (21)) and is also used when adding media for the robot to the Media Manager configuration.
▼ To specify a robot number
❖ Click an arrow and select a robot number.
The following points apply only to NetBackup Enterprise Server.
◆ Robot numbers must be unique for all physically-distinct robots on all hosts in the
configuration. This applies regardless of the robot type or the host that controls them. For example, if you have two robots, use different robot numbers even if they are controlled by and configured on different hosts.
◆ If you are adding a robot definition for a robot where the robot control is handled by a
remotedevicehost,besuretousethesamerobotnumberasusedforthatrobotonall other device hosts.
◆ If the robot has its robotic control and drives on different hosts (for example, as
permitted by a Tape Library DLT robot), be certain to specify the same robot number in all references to that library. That is, use the same robot number on the hosts with the drives, as you do on the host that has the robotic control.
See “Example 3: Configuring a Robot Distributed Among Multiple Servers” on page 81.
Volume Database Host
Volume Database Host applies only to NetBackup Enterprise Server. Specifies the name of the host where Media Manager keeps the volume configuration
information about the media in the robotic library. You can specify any host that has Media Manager installed as the volume database host, even if the host does not have any drives or robots attached.
VERITAS recommends that you use one volume database host for all your volumes (robotic and standalone). Although it is possible to maintain separate volume databases on multiple hosts, administration is more difficult.
See “Media and Device Management Domain Management” on page 244 for more information.
“Example 3: Configuring a Robot Distributed Among Multiple Servers” on page 81, shows a configuration where the volume database is on a central host.
Youwill have to know the name of the volume database host when adding volumes to the robotic library.
Chapter 2, Configuring Storage Devices
49
Page 84
Adding Robots
▼ To specify the volume database host
Adding volumes is explained in “Managing Media” on page 89.
❖ Click the arrow and select from the list of hosts.
Robot Control Section of the Dialog
In the Robot control section you specify the control for the robot. Depending on the robot type you are adding and the type of media server, various combinations of the robot control buttons are available in the dialog.
The following table provides an overview of configuring robot control, based on robot type and the media server platform type. The third column in the table indicates the robot control button that is valid for that particular robot type and server platform, as follows:
◆ Robot is controlled locally by this device host (Local)
◆ Robot control is handled by a remote host (Remote)
The following control button applies only to NetBackup Enterprise Server.
◆ Robot control is attached to an NDMP host (NDMP)
Be sure to read your NetBackup release notes or visit the VERITAS support web site for more detailed information on supported robot types, media server platforms, and other NetBackup server limitations.
Also see “Robot Attributes” on page 253 for more information.
Robot Control Configuration Overview
Information Required
Robot Type Media Server Platform Robot Control
ACS All Remote ACSLS host
LMF Solaris Local Library name
LMF Solaris Remote Robot control host
ODL AIX
Solaris HP-UX IRIX
Local Robotic device file
for Configuration
50 NetBackup Media Manager System Administrator’s Guide for Windows
Page 85
Robot Control Configuration Overview (continued)
Robot Type Media Server Platform Robot Control
Adding Robots
Information Required for Configuration
RSM Windows (needs RSM
support)
TL4 UNIX (except Linux) Local Robotic device file
TL8, TS8, TSD UNIX Local Robotic device file
TLD UNIX Local Robotic device file
TSH AIX
Solaris IRIX
TL4, TL8, TLD TS8, TSD
TL8 All Remote Robot control host
TLD All Remote Robot control host
TL8, TLD, TSD, TLH Windows
Windows Local Robot device
AIX Solaris HP-UX
Local Robot device
Local Robotic device file
NDMP NDMP host name
Robot device
TLH AIX Local LMCP device file
TLH UNIX(exceptAIXandLinux)
TLH All(except Linux) Remote Robot control host
TLM All (except Linux) Remote DAS/SDLC server
The following example applies only to NetBackup Enterprise Server.
ThefollowingfigureshowstwoserversusingtwodrivesinaTL8robot.Thisisan example of library sharing. The robotic control for the robot is on the host named eel. One drive in the robot is connected to eel and the other is connected to the host shark.
Chapter 2, Configuring Storage Devices
Local Library name
Windows
51
Page 86
Adding Robots
When you add this robot to the device configuration on eel, you select Robot is controlled locally by thisdevice host. When you add the robot to the device configuration on shark, you select Robot control is handled by a remote host.
Robot Control Host Example
TL8 Robot (Exabyte 440)
TL8 Robotic Control
Control
Drive 1
Drive 2
eel
Local Robot information for the TL8
Robotic Drive informationfor
For Drive 2
Drive 1
Volume Database
shark
Remote Robot information for the TL8
Robotic Drive information for
For Drive 2
Drive 2
Robot is controlled locally by this device host
For this type of robot control, you have the following possibilities based on the robot type that you selected and type of media server platform where you are adding the robot.
◆ “Robotic Device File” on page 52
◆ “Robot Device” on page 53
◆ “LMCP Device File” on page 54
◆ “Library Name” on page 54
Robotic Device File
Robotic Device File applies only when adding a robot to a UNIX device host.
This file is used for SCSI connections and is located in the /dev directory tree on the device host.
52 NetBackup Media Manager System Administrator’s Guide for Windows
Page 87
Adding Robots
To specify the robotic device file path
▼
1. Click Browse.
2. Select a robotic device file from the list that appears in the Devices dialog. When you
click OK, your selection will be placed in Robotic device file.
3. If the browse operation fails to find and display all of the attached robots, click Other
Device to display a dialog that allows you to enter the path of the device file. Your
entry will be placed in Robotic device file. If the browse operation does not find any attached robots you will see an error dialog. If the device file entry does not exist, create the entry as explained in the NetBackup
Media Manager device configuration guide.
Robot Device
Robot Device applies only when adding a robot to a Windows device host.
For information on adding RSM robots to a Windows server, see the appendix, “Microsoft Removable Storage Manager (RSM)” on page 353.
▼ To specify the robot device
1. Click Browse.
If the browse operation does not find any attached robots you will see an error dialog.
2. Select a robot from the list that appears in the Devices di alog.
3. Click OK.
TheresultingvaluethatissetinRobot device depends on the type of Windows device host where the robot is being added. For RSM robot types, a device name is always set in Robot device.
The following table shows the resulting settings in Robot device for different types of Windows device hosts:
Robot Device Setting For this Type of Windows Device Host
SCSIPort,Bus,Target,andLUNnumbers WindowsNTservers.
SCSI Port, Bus, Target, and LUN numbers Windows servers where a changer driver is not
in control of the robot.
Chapter 2, Configuring Storage Devices
53
Page 88
Adding Robots
▼ To specify the LMCP file for TLH robot types controlled from an AIX device host
Robot Device Setting For this Type of Windows Device Host
Device name (for example, Changer1) Windows servers where a changer driver is in
controlof the robot.
LMCP Device File
LMCP Device File applies only to NetBackup Enterprise Server, and when adding a robot to a UNIX AIX device host.
❖ Specify the LMCP (Library Manager Control Point) device file name as it is
configured on the AIX device host.
Library Name
Library Name applies only when adding a LMF or TLH robot on NetBackup Enterprise Server. For more information on LMF robots, see the appendices of the NetBackup Media
Manager system administrator’s guide for UNIX. For more information on TLH robots, see the appendix, “IBM Automated Tape Library
(ATL)” on page 361.
▼ To specify the library name for LMF robots controlled from a UNIX host
1. Use the Fujitsu lmadmin command to determine the library name.
2. Specify the library name.
▼ To specify the library name for TLH robots controlled from a UNIX host (the host is
not AIX or Linux)
❖ Specify the library name that is configured on the UNIX host.
▼ To specify the library name for TLH robots on a Windows host
1. Determine the library name by viewing the C:\winnt\ibmatl.conf file.
The following is an example entry in that file, where 3494AH is the library name: 3494AH 176.123.154.141 ibmpc1.
2. Specify the library name.
54 NetBackup Media Manager System Administrator’s Guide for Windows
Page 89
Adding Robots
Robot control is handled by a remote host
This is a NetBackup Enterprise Server topic. For this type of robot control, you have the following possibilities for the robot control
host (based on the robot type and device host platform that you selected).
◆ “Robot Control Host” on page 55
◆ “DAS Server” on page 55
◆ “ACSLS Host” on page 55
Robot Control Host
Robot Control Host applies only to NetBackup Enterprise Server. For more information on TLH robots, see the appendix, “IBM Automated Tape Library
(ATL)” on page 361. For more information on LMF robots, see the appendices of the NetBackup Media
Manager system administrator’s guide for UNIX.
▼ To specify the robot control host for LM F (UNIX hosts only), TL8, TLD, or TLH
robots
❖ Specify the device host that controls the robot. Enter the name of the device host
where you have defined or will define the robot information for this robot. Referring to the figure, “Robot Control Host Example” on page 52, you would specify
eel as the Robot Control Host when adding a robot to host shark.
DAS Server
DAS Server applies only to NetBackup Enterprise Server. For more information on TLM robots, see the appendix, “ADIC Distributed AML Server
(DAS) / Scalar Distributed Library Controller (SDLC)” on page 373.
▼ To specify the DAS server for TLM robots controlled by an ADIC DAS/SDLC server
❖ Specify the server name of the DAS/SDLC server. This server is an OS/2 workstation
near or within the robot cabinet, or a Windows server near the ADIC Scalar library.
ACSLS Host
ACSLS Host applies only to NetBackup Enterprise Server.
Chapter 2, Configuring Storage Devices
55
Page 90
Adding Robots
▼ To specify the ACSLS host for ACS r obot types
TheACSlibrarysoftwarecomponentcanbeanyofthefollowing:
◆ Automated Cartridge System Library Software (ACSLS)
See “Example 4: Configuring An ACS Robot on a Windows Server” on page 85.
◆ STK Library Station
◆ Storagenet 6000 Storage Domain Manager (SN6000).
This STK hardware serves as a proxy to another ACS library software component (such as, ACSLS).
Note STK LibAttach software must also be installed, if the device host that has drives
under ACS robotic control is a Windows server. LibAttach for Windows is not available for servers running Windows 2003.
For an overview of ACS robots, see the appendix, “Automated Cartridge System (ACS)” on page 339.
❖ Specify the name of the host where the ACS library software resides. On some UNIX
server platforms, this host can also be a Media Manager device host or volume database host.
Robot control is attached to an NDMP host
This is a NetBackup Enterprise Server topic. For this type of robot control, you specify the following two items.
◆ “Robot Device” on page 56
◆ “NDMP Host Name” on page 57
Robot Device
▼ To specify the robot device
1. Enter the name of the robotic device that is attached to the NDMP host.
2. Click Browse to select a robot device from the list in the Devices dialog.
56 NetBackup Media Manager System Administrator’s Guide for Windows
Page 91
NDMP Host Name
▼ To specify the host
❖ Enter the name of the NDMP host where the robot is attached.
Adding Shared Drives
This is a NetBackup Enterprise Server topic. The Device Configuration and the Shared Drive Media Manager wizards can be used to
configure drives for an SSO configuration. These wizards guide you through the steps involved in configuring drives that will be shared among device hosts. Determining which of the two wizards to use depends on the type of robot that controls the drives.
For more information on using these two wizards and for wizard limitations in an SSO environment, be sure to review the NetBackup Shared Storage Option system administrator’s guide.
Adding Shared Drives
Using the Device Configuration Wizard for Shared Drives
This is a NetBackup Enterprise Server topic.
Note When using the Device Configuration wizard in an SSO configuration, the
limitations, supported devices, and device hosts are different than in a configuration without shared drives. See the NetBackup Shared Storage Option system administrator’s guide.
For TL8, TLD, or TLH robot types, VERITAS recommends using the Device Configuration wizard to add shared drives.
For ACS or TLM robot types you can use this wizard to configure shared drives, but some manual configuration is also involved. See “Configuring Shared ACS Drives” on page 344 and “Configuring Shared TLM Drives” on page 378.
See “Using the Device Configuration Wizard” on page 41 for instructions on starting the wizard and “Frequently Asked Questions About Device Discovery” on page 269 for important background information on device discovery, serialization, and the Device Configuration wizard.
Using The Shared Drive Wizard
This is a NetBackup Enterprise Server topic.
Chapter 2, Configuring Storage Devices
57
Page 92
Adding Drives
▼ To start the Shared Drive wizard
The Shared Drive wizard can be used to configure drives in ACS, TL8, TLD, TLH, or TLM robots. This wizard has limited usage and does not configure robots.
Since this wizard does not use device serialization, it requires prior configuration details from you about your configuration before starting. For example: the names of the hosts that will share a drive, drive paths, and the robotic drive parameters and number of the robot that will control the drive.
When using this wizard you can configure only one drive at a time. This may be beneficial if you want to add an individual shared drive without disrupting the other configured drives.
VERITAS recommends the following:
◆ Use the Device Configuration wizard when possible rather than the Shared Drive
wizard.
◆ Use the Shared Drive wizard with caution after initial device configuration.
1. In the NetBackup Administration Console, click Media and Device Management >
Devices.
2. Click Actions > New > Shared Drive.
Follow the prompts for the wizard.
Adding Drives
Note Using the Device Configuration wizard is the recommended method of configuring
drives. See “Using the Devi ce Configuration Wizard” on page 41 for wizard restrictions and more information.
▼ To add drives
1. Complete the steps necessary for the server to recognize the attached drives (see
“Performing Initial Device Configuration” on page 34).
2. In the NetBackup Administration Console, click Media and Device Management >
Devices.
3. Select Actions > New > New Drive.
58 NetBackup Media Manager System Administrator’s Guide for Windows
Page 93
Adding Drives
The properties that appear in this dialog vary slightly, depending on the type of host platform and the robot type.
4. Specify the properties of the drive as explained in “Dialog Entries for Adding (or
Changing Drives)” on page 60.
5. Click OK.
Thedisplaynowshowsthenewdriveinformation.
Note The initial drive status is up, so the drive is available as soon as you add it and
restart ltid. To change the status of the drive, select Device Monitor.
A prompt appears asking whether you want to stop and restart the NetBackup Device Manager service (this also stops and restarts any robotic processes). If your changes are complete, answer yes to this prompt.
Note It is possible that stopping and restarting this service will abort any backups,
archives, or restores that are in progress.
6. This step applies only to NetBackup Enterprise Server.
If the new drive was standalone, verify the volume database host setting and change it if necessary. See “Changing the Volume Database Host for Standalone Drives” on page 68.
Chapter 2, Configuring Storage Devices
59
Page 94
Adding Drives
Dialog Entries for Adding (or Changing Drives)
▼ To specify a different device host
You can specify the following properties when adding a drive or changing the properties of a drive. Note that some of these properties apply only to specific types of drives, server platforms, or NetBackup servers.
Device Host Section of the Dialog
Specifies the media server to which you are adding the drive.
Device Host
Device Host applies only to NetBackup Enterprise Server.
The host that is shown initially in the dialog box is the device host you selected earlier in the tree pane.
❖ Click the arrow and select a host from the list.
▼ To specify a device host that is not in the list
1. Click New ...
2. In the dialog that appears, enter the name of the host.
Drive Information Section of the Dialog
Specifies information about the drive.
Drive Name
This name is used to identify the drive. It is important to note that each drive name must be unique. Descriptive names are recommended.
▼ To specify the drive name
❖ Enteranameforthedrive.
Drive Type
Specifies the type of drive that you are adding.
60 NetBackup Media Manager System Administrator’s Guide for Windows
Page 95
Adding Drives
See “Media Manager Media Types” on page 251 for more information.
▼ To specify the drive type
❖ Click the arrow and select from the list of the drive types that Media Manager
supports.
Device Name
Device Name applies only to drives on NetBackup Windows servers.
▼ To specify the device name
1. Find the device name for the drive from the appropriate Windows application.
2. Enter the name of the drive in the box as it is recognized by the Windows server.
▼ To select from the drives that are currently attached to the Windows server
1. Click Browse ...
2. Select a drive.
No Rewind Device
No Rewind Device applies only to drives on NetBackup UNIX servers.
Although both no rewind and rewind device files are usually available, Media Manager requires only the no rewind on close device file.
Device files are located in the /dev directory on the UNIX host. If the device files do not exist, create them as expl ai ned in the NetBackup Media Manager device configuration guide.
A no rewind device remains at its current position on a close operation. Usually the device file name is preceded or followed by the letter n.
If you are using NDMP drives, see the NetBackup for NDMP system administrator’s guide for configuration information.
▼ To specify the no rewind device file
❖ Enter the no rewind device file path for the drive.
Chapter 2, Configuring Storage Devices
61
Page 96
Adding Drives
▼ To select a no rewind device file
▼ To specify the character device
❖ Click the button on the right to display a dialog from which you can select a device
file.
Character Device
Character Device applies only to optical disk drives on NetBackup UNIX servers.
Character device files are in the /dev directory on the UNIX host. If the entries do not exist, you can create them as explained in the NetBackup Media Manager device configuration guide. Media Manager uses character mode device files.
❖ Enter the character device file path for the drive.
Volume Header Device
Volume Header Device applies only to optical disk drives on NetBackup UNIX servers.
Volume header device files are in the /dev directory on the UNIX host. If the entry does not exist, you need to create it as explained in the NetBackup Media Manager device configuration guide.
▼ To specify the volume header device
❖ Enter the volume header device path for the drive.
Cleaning Frequency
Cleaning Frequency does not apply to shared drives or to any robots that do not support frequency-based cleaning.
If you want to set up a frequency-based cl eaning schedule for the drive, set the number of mount hours between each drive cleaning. When you add a drive or reset the mount time to zero, Media Manager starts recording the amount of time that volumes have been mounted in that drive.
If you do not specify a cleaning frequency (the default frequency is zero), you can still utilize automated drive cleaning with the TapeAlert feature, provided all of the following conditions have been met:
◆ The robot supports TapeAlert.
◆ A cleaning volume has been defined in Media Manager.
62 NetBackup Media Manager System Administrator’s Guide for Windows
Page 97
Adding Drives
The host platform, robot type, and drive support drive cleaning.
◆
If the drive is in a robotic library that supports drive cleaning and a cleaning cartridge is defined in that robotic library, cleaning occurs when the accumulated mount time exceeds the time you specify for cleaning frequency. The mount time is reset when the drive is cleaned.
See “Drive Cleaning Functions” on page 70 for information on resetting the mount time and initiating an operator-initiated cleaning of a drive. You can also perform these drive cleaning functions from the Device Monitor, in addition to setting or changing the cleaning frequency.
▼ To specify a cleaning frequency
❖ Click an arrow and select the number of hours.
Drive Is In A Robotic Library
▼ To specify that a drive is under robotic control
1. Select Drive is in a robotic library.
2. Enter additional information about the drive in the Robotic driveinformationsection
(see “Robotic Drive Information Section of the Dialog” on page 63).
▼ To specify that a drive is a standalone (non-robotic) drive
❖ Clear Drive is in a robotic library.
Robotic Drive Information Section of the Dialog
Specifies information about a drive in a robotic library.
Robotic Library
This dialog box allows you to select any currently configured robotic library that can control the drive.
▼ To specify the library
❖ Click the arrow and select a robotic library from the list.
Chapter 2, Configuring Storage Devices
63
Page 98
Adding Drives
▼ To specify the robot drive number
Robot Drive Number
Robot drive number specifies the physical location in the robot of the drive that you are adding. When adding more than one drive to a robot, you can add the physical drives in any order. For example, in a TS8 robot you can add drive 2 before drive 1.
If you assign the wrong number Media Manager does not detect it, but an error will occur when the robotic control attempts to mount media on the wrong drive.
The following point applies to NetBackup Enterprise Server.
Robot drive number doesnotapplywhenaddingdrivestothefollowingtypesofAPI robots:
◆ ACS robots (Automated Cartridge System). See “ACS” on page 64.
◆ TLH robots (Tape Library Half-inch). See “TLH” on page 65.
◆ TLM robots (T ape Library Multimedia). See “TLM” on page 65.
1. Determine the correct robot drive number. You must determine which physical drive
in the robot is identified by the logical device name (on Windows servers) or the device file (on UNIX servers).
See “Correlating Device Files to Physical Drives When Adding Drives” on page 272 for more information.
2. Click an arrow and select a number for the drive.
ACS
ACS applies only to NetBackup Enterprise Server.
▼ To specify a drive i n an ACS robot
1. Determine the physical location of the drive within the robot. You must know which
physical drive in the robot is identified by the device files that you specified earlier. You establish this correlation during installation.
The appendix, “Automated Cartridge System (ACS)” on page 339, has further information.
2. Select ACS.
64 NetBackup Media Manager System Administrator’s Guide for Windows
Page 99
Adding Drives
3. In the dialog enter the following information:
For Enter
ACS Number The index (in ACS library software terms) that identifies the robot that has
this drive.
LSM Number The Library Storage Module that has this drive.
Panel Number The robot panel where this drive is located.
Drive Number The physical number of the drive (in ACS library software terms).
If you assign the wrong parameters for the drive, Media Manager does not detect it, but an error will occur when the robot mounts media on the wrong drive.
TLH
TLH applies only to NetBackup Enterprise Server.
▼ To specify a drive in a TLH (Tape Library Half-inch) robot
1. Select TLH.
2. In the dialog, enter the IBM device number of the drive within the robot.
If you assign the wrong device number Media Manager does not detect it, but an error will occur when the robot mounts media on the wrong drive.
The appendix, “IBM Automated Tape Library (ATL)” on page 361, has further information.
TLM
TLM applies only to NetBackup Enterprise Server.
▼ To specify a drive i n a TLM (Tape Library Multimedia) robot
1. Select TLM.
2. In the dialog, enter the DAS/SDLC drive name of the drive within the robot.
If you assign the wrong drive name Media Manager does not detect it, but an error will occur when the robot mounts media on the wrong drive.
Chapter 2, Configuring Storage Devices
65
Page 100
Managing Your Device Configuration
The appendix, “ADIC Distributed AML Server (DAS) / Scalar Distributed Library Controller (SDLC)” on page 373, has further information.
Managing Your Device Configuration
The following topics explain how to manage the robots and drives in your configuration:
◆ When to Perform Device Configuration Changes
◆ Using the Device Configuration Wizard for Configuration Changes
◆ Changing a Robot Configuration
◆ Changing the Configuration of a Drive
◆ The following topic applies only to NetBackup Enterprise Server.
Changing a Non-Shared Drive to a Shared Drive
◆ The following topic applies only to NetBackup Enterprise Server.
Changing the Volume Database Host for Standalone Drives
◆ Deleting Robots
◆ Deleting Drives
◆ Drive Cleaning Functions
◆ Performing Drive Diagnostics
◆ Using SANPoint Control to Investigate SAN Problems
◆ Printing Your Device Configuration
Also see “Making Changes to Your Hardware Configuration” on page 299 for advanced configuration topics.
When to Perform Device Configuration Changes
Device configuration tasks should not be attempted when any backups or restores are running. When performing many of the following device configuration tasks, a prompt at the end of the procedure asks if you want to stop and restart ltid.
This action also stops and restarts any robotic processes. ltid is the Media Manager device daemon on UNIX and the NetBackup Device Manager service on Windows servers.
If your configuration changes are complete and you are not in a production environment, answeryestothisprompt.
66 NetBackup Media Manager System Administrator’s Guide for Windows
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use