Netbackup™ 5.0 Administration Fundamentals: Media Configuration and Management

NetBackup™ 5.
0
Administration
Fundamentals
Media Configuration and
Management
At the conclusion of this lesson the participant will be able to:
• Describe a Media Manager ‘volume’ and its characteristics.
• Describe the purpose of the Volume Database and its contents.
• Describe Volume Pools and Volume Groups.
• Describe Barcode Rules, Media ID Generation Rules, and Media
Prefixes and when they would be used.
• Describe the Volume Database Host and how to set it.
• Describe the configuration and use of the Scratch Pool.
• Identify the purposes of the poolDB, ruleDB, volDB, and vm.conf
files.
• Utilize selected GUIs, reports and commands to manipulate
specific volumes.
• Describe how volume usage is tracked.
Volumes
Volume Database
Volume Database Host
• What is a ‘Volume’?
TM
• In NetBackup , a volume is defined as a piece of removable
media. (Volumes are actually Media Manager entities).
• A volume is either a magnetic tape or an optical disk*.
• A volume is a logical unit of data storage. The purpose of most
volumes is to house Client backup images. Other volume types are:
• Volumes used for cleaning heads on tape and optical drives.
TM
• Volumes used for NetBackup database backups
• Volumes used by other applications such as Storage Migrator
• Each volume is known by an identifier known as the ‘media ID’.
• ‘mediaIDs’ are from 1-6 digits in length.
• Information about all ‘volumes’ known to Media Manager is housed
in a Media Manager database, known as the Volume Database.
• The Volume Database is represented by a single file, ‘volDB’.
The Volume Database
• The Volume Database is a Media Manager database which
contains a list of all known ‘volumes’ (‘removable’ media), both
tape and/or optical.
• The Volume Database contains a record for each ‘Volume’ (660
bytes per volume).
• The Volume Database record contains information such as:
 mediaID, ASSIGNED or UN-ASSIGNED, name of Volume Pool
mediaID belongs to, creation date/time, assigned date/time, last
mounted date/time, first mounted date/time, number of mounts,
expiration date (if set), maximum mounts (if set), application to
which media is assigned (owner).
• The Volume Database knows nothing about:
 The actual data on the tape – how much data, what type, which
client the data came from, where the data is
The Volume Database - volDB
• The Volume Database is a file named ‘volDB’
• ‘volDB’ is maintained by the NetBackupTM Volume Management
service/daemon – represented by the process ‘vmd’
• Although a ‘volDB’ file exists on EACH NetBackupTM server system,
VERITAS strongly recommends that only a single Volume Database
(volDB) be active/maintained.
• The system that maintains the Volume Database is known as the
Volume Database Host.
• The ‘volDB file is located at:
 <install path>\VERITAS\volmgr\database\ (Windows)
 <install path>/openv/volmgr/database/ (Unix)
• The ‘volDB’ file contain a 660 bytes record per volume.
 ‘volDB’ files on all other NetBackupTM servers will remain an 8
byte file.
The Volume Database - volDB
TM
Volume Database Host NetBackup
‘volDB’ active Master Server
TM
NetBackup
Media Server
TM
NetBackup
Media Server
volDB volDB
8 bytes 8 bytes
(inactive) (inactive)
TM
NetBackup
TM NetBackup
Clients Clients
The Volume Database Host
• The Volume Database Host is the single system that maintains
the Volume Database - per VERITAS recommendation.
• It is recommended that the NetBackupTM Master server act as the
Volume Database Host.
• On a new installation of NetBackupTM 5.0, the Master server will,
by default, be configured as the Volume Database Host.
 Risk is higher that multiple Volume Database Hosts exist in
installations of older versions of NetBackupTM.
 If merging NetBackupTM Master servers, multiple Volume
Database Hosts will exist. VERITAS consulting services are
recommended when customers are merging environments.
• All queries for media (volumes) or updates made to volume
records are directed to the NetBackupTM Volume Management
Daemon (vmd) running on the Volume Database Host (the
Master server).
The Volume Database Host
Volume information NetBackup
for entire NetBackup domain
Volume Database Host
‘volDB’ active Master Server
maintained in ‘volDB’ file on
NetBackup Master Server. NetBackup
Media Server
NetBackup
Media Server
“Change Volume Database

volDB Host” on these systems
8 bytes (all Media Servers). volDB
(inactive) Set the Volume Database 8 bytes
Host to the Master (inactive)
Server hostname.
NetBackup NetBackup
Clients Clients
Configuring the Volume Database Host – for Robotic Devices
• Using Windows-based NetBackupTM Administration Console
 <install path>\VERITAS\NetBackup\bin\NBConsole.exe
Configuring the Volume Database Host – for Robotic Devices
• Using Java-based NetBackupTM Administration Console
 <install path>/openv/netbackup/bin/jnbSA& (Unix)
Configuring the Volume Database Host – for Standalone Devices
• Using Windows-based NetBackupTM Administration Console
Configuring the Volume Database Host – for Standalone Devices
• Using Java-based NetBackupTM Administration Console
Configuring the Volume Database Host - using ‘tpconfig’
• ‘vmd’ must be stopped/restarted after changes to the configuration
are made for the changes to take effect.
• Use on each Media server system
<install path>/openv/volmgr/bin/tpconfig (Unix)
<install path>\VERITAS\volmgr\bin\tpconfig (Windows)
Configuring the Volume Database Host - using ‘tpconfig’
• On Unix-based platforms, ‘tpconfig’ is menu-based (as below)
• On Windows platforms, ‘tpconfig’ is not a menu-based utility.

 tpconfig –update –robot 0 –vdbhost <master server hostname>
Verifying the Volume Database Host - using ‘tpconfig’
• Verify this setting on all Media Servers.
• Volume Database Host should point to hostname of Master Server.
• Use command - ‘tpconfig –d’
 <install path>/openv/volmgr/bin/tpconfig –d (Unix)
 <install path>\VERITAS\volmgr\bin\tpconfig –d (Windows)

Media IDs - Volume Pools - Volume Groups
Introduction to Configuring Media
• There are a number of important NetBackupTM concepts relating to
media. Among the most important are:
 mediaID
 The ‘mediaID’ is the key method of identifying a volume.
 The ‘mediaID’ is from 1-6 digits in length and must be
unique within a given NetBackupTM environment.
 Volume Pool
 A ‘volume pool’ is a bunch of media having the same
characteristics/purpose.
 Volume Group
 A ‘volume group’ is a bunch of media sharing the same
geography (for instance, located in the same tape library).
• The slides which follow will further define ‘mediaID’, Volume Pools,
and Volume Groups.
The ‘mediaID’
• Configuring media simply involves creation of a record per volume,
in the Volume Database (volDB).
• The ‘name’ of the record for a volume in the Volume Database is
the ‘mediaID’ of the volume.
• NetBackupTM ‘mediaIDs’ are always from one-six digits in length.
• The digits which make up a ‘mediaID’ are all alpha-numeric.
• Examples of valid ‘mediaIDs’ include: A00000, XYZ001, TEST99
• When an application (such as NetBackupTM or Storage Migrator)
requires the use of a piece of media, the application will make a
request for the media by its ‘mediaID’ to the Volume Management
Daemon (vmd).
 ‘vmd’ will look up the record for the ‘mediaID’ in the Volume
Database and provide information about the volume, including
the location of the volume, so that the media can be mounted
on a drive for reading/writing (restore/backup).
The ‘mediaID’
B00001
A00001
• The name of a volume is its ‘mediaID’.
• Each volume has a record in the B00002
A00002
Volume Database (volDB). The name
of the record in ‘volDB’ is the ‘mediaID’ B00003
A00003 • This record is created at the time the
volume is created.
• The record for the volume is modified B00004
A00004
whenever the volume is moved,
mounted, modified, deleted, or when B00005
A00005 the volume is ‘assigned’ or ‘un-
assigned’.
B00006
A00006
Volume Pools
• A Volume Pool is a set (bunch, pile) of volumes defined for a
specific purpose and/or having a common set of characteristics.
 Examples:
 All volumes that are defined to house backups from
workstations in the engineering group could be placed in
the volume pool ‘engrpool’.
 All volumes used for writing backup of the Oracle database
might be placed in the volume pool ‘Oraclepool’.
• Volume Pools are not defined by geography.
 Tapes that belong to the same pool can be located in several
robotic libraries and/or standalone.
• The number of pools required is entirely customer dependent.
• There is no limit to the number of pools that can be created.
• NetBackupTM provides a few ‘standard’ volume pools.
• Every volume is a member of a volume pool.
Volume Pools
B00001
A00001 “Engrpool”
• Each pool has an entry in the Media Manager

A00002 database file “poolDB”. B00002
• As Volumes are created they are assigned to

an existing pool. B00003
A00003
• Every volume is associated with a Pool.
• Volumes may be moved from one volume B00004

A00004
pool to another – provided the volume is ‘UN-
ASSIGNED.
B00005
A00005
B00006
A00006 “Oraclepool”
Why use Volume Pools?
• When NetBackupTM requires a piece of media on which it will write
a backup image, it does not care which specific piece of media it
uses.
• Using Volumes Pools removes the need for NetBackupTM to specify
(or even be aware of) the specific name (mediaID) of a volume
during backup operations.
 Rather than request ‘XYZ001’, NetBackupTM will request an
available volume from pool ‘testpool’ (or some other). There
many be many volumes available in ‘testpool’ to choose from.
 Ultimately, a specific piece of media (mediaID) will be selected
and provided (by Media Manager) to satisfy the request from
the NetBackupTM.
• For certain operations (such as restores) NetBackupTM will request
the specific ‘mediaID(s)’ needed for the operation.
Configuring Volume Pools
• NetBackupTM provides three ‘default’ volume pools: NetBackup,
DataStore, None
• No additional pools are absolutely required – but most customers
will create additional pools, based upon their needs.
• Volume Pools can be created/modified/listed using:
 The NetBackupTM Administration Console (Windows or Java)
 The ‘vmpool’ command line interface
• Media Manager maintains a catalog (database) of Volume Pools
as a single file, named ‘poolDB’.
• ‘poolDB’ is located on the NetBackupTM Master server in:
 <install_path>\VERITAS\volmgr\database\ (Windows)
 <install_path>/openv/volmgr/database/ (Unix)
• NetBackupTM supports a concept called ‘scratch’ pools that will be
described later in this lesson.
• Using the NetBackupTM Administration Console GUI
 NetBackupTM provides three Volume Pools by default
 None
 NetBackup
 DataStore
• Using the NetBackupTM Administration Console – Java-based
 Adding Volume Pools
• Using the NetBackupTM Administration Console – Windows-based
 Adding Volume Pools
• Using the NetBackupTM Administration Console
Volume Pools – using a ‘Scratch Pool’
The problem:
A00001 • This customer has two (or more) primary
“Engrpool” types of backups.
A00002 • The backup administrator has created two
pools (‘engrpool’ and ‘oraclepool’) each
which define the set of tapes that are
A00003 available to each of the backup policies that
will be performing the backups.
A00004  ‘PolicyA’  uses tapes in ‘engrpool’
“Oraclepool”  ‘PolicyB’  uses tapes in ‘Oraclepool’.
• In this example the six (6) volumes have
A00005 been divided evenly between the two pools.
• The problem is deciding how many tapes to
A00006 put into each pool.
 If during backups one pool runs out of
tapes - backups using that pool will fail.
The Solution:
• Implement a ‘scratch’ pool.
• A ‘SCRATCH’ pool is a special volume pool
A00002 from which Media Manager can dynamically
allocate volumes - into other volume pools
- as those other volume pools has need for
A00003 additional media.
“scratchpool” • This concept reduces the need for the
A00004 backup administrator to precisely plan the
amount of media that is required in specific
pools.
A00005 • When implementing a ‘scratch’ pool, the
majority of the customer’s media is placed
A00006 “Oraclepool” in the pool designated as the
‘SCRATCH_POOL’.
Scratch Pool Implementation
• The ‘scratch pool’ can have any name, but
using a name like ‘scratchpool’ is probably a
A00002 good idea, as it is descriptive of the
purpose/function of the pool.
• The pool names to which backups are
A00003 directed probably have a small number of
“scratchpool” volumes assigned to them initially.
A00004 • In this case, as ‘engrpool’ or ‘Oraclepool’
run out of available media, and require
more volumes, Media Manager
A00005 automatically moves volumes from the
‘scratch pool.
A00006 “Oraclepool” • Backups should NEVER be directed
towards the ‘scratchpool’.
Scratch Pool Implementation
• In this case, as ‘engrpool’ or ‘Oraclepool’
run out of available media, and require
A00002 more volumes, Media Manager
automatically moves volumes from the
‘scratch pool.
A00003 • As you can see in this example, volumes
“scratchpool” have been moved from the ‘scratchpool’ to
A00004 both the ‘engrpool’ and the ‘Oraclepool’.
• In recent releases of NetBackupTM (since
v4.5 FP3), volumes which originated in the
A00005 ‘scratchpool’ can be automatically moved
back to the ‘scratchpool’ once all active
A00006 “Oraclepool” backups on the volume have expired.
Configuring Volume Pools – creating a ‘Scratch’ pool
• From NetBackupTM Administration Console (Java-based)
 Adding a ‘scratch’ pool is a simple process
• From NetBackupTM Administration Console (Windows-based)
 Adding a ‘scratch’ pool is a simple process
• Contents of the ‘vm.conf’ file – on a Unix-based Master server
 Located in: <install_path>/openv/volmgr/
• Contents of the ‘vm.conf’ file – on a Windows-based Master server
 Located in: <install_path>\VERITAS\volmgr\
• Command Line Interface for working with Volume Pools – ‘vmpool’
 Located in: <install_path>\VERITAS\volmgr\bin\ (on Windows)
 Located in: <install_path>/openv/volmgr/bin/ (on Unix)
Examples:
vmpool –listall
vmpool –add testpool “just testing” ANYHOST –1 –2
vmpool –delete testpool
vmpool –set_scratch scratchpool
• The Volume Pool Database – ‘poolDB’ file
 Located in <install_path>/openv/volmgr/database/ (Unix)
Default
pools
Customer
added
pools
Pool # version pool name host access UID GUID Description

• The Volume Pool Database – ‘poolDB’ file
 Located in <install_path>\VERITAS\volmgr\database\
(Windows)
Default
pools
Customer
added
pools
Pool # version pool name host access UID GUID Description

Volume Groups
• A Volume Group is a Media Manager entity which defines media
according to their location (geography).
• Generically, media is always located in one of two ‘places’:
 In a ‘robotic’ device. Media is referred to as ‘robotic’.
 Not in a ‘robotic’ device. Media is referred to as ‘standalone’.
• When a volume is placed into a tape library (robotic device) and a
robot inventory is performed, the volume is automatically placed into
a ‘Volume Group’ by Media Manager.
 The ‘names’ of ‘robotic volume groups’ are derived automatically
by Media Manager, based upon the type of ‘robot’ and the ‘robot
number’, for example:
 All tapes in TLD library (Tape Library DLT), robot # ‘0’, are
members of Volume Group  00_000_TLD
 All tapes in TL8 library (Tape Library 8mm), robot # ‘2’, are
members of Volume Group  00_002_TL8
Volume Groups
• When a volume is removed from a robotic device it ceases to be a
member of the ‘robotic volume group’ – it becomes a ‘standalone’
volume.
 By default, Media Manager loses track of ‘standalone’ volumes
because it cannot know where the media is physically located.
 Standalone volumes, by default, are members of no volume
group.
• Media Manager makes a provision to allow the customer to create
‘Volume Groups’ into which media can be placed when they are
ejected from a robotic device.
• The typical application for customer-created ‘Volume Groups’ is in
conjunction with the NetBackupTM Vault Option.
 Since the Vault Option is not covered in this course, we will
only introduce the concept of Volume Groups here.
Volume Groups - Illustrated
NetBackup
Master Server
NetBackup
Media Server NetBackup
‘TLD’ robot ‘0’ Media Server
‘TLD’ robot ‘1’
Tapes are ‘standalone’

(not in a Tape Library) -
Tapes are in Volume Group are members of no Tapes are in Volume Group
’00_000_TLD’ volume group ’00_001_TLD’
Volume Groups – Illustrated
• As viewed from the NetBackupTM Administration Console
These volumes are ‘robotic’

Note the Volume Group -
These volumes are ‘standalone’ Robot # - Slot# columns
Barcode Rules
Media ID Generation Rules
Media Prefix
Methods of Configuring Media
• There are two basic methods for configuring media:
 Automatically
 by performing a ‘robot inventory’
 When utilizing ‘standalone’ tape drives to perform
NetBackupTM operations not requiring specific ‘mediaIDs’
and an un-labelled (no NetBackupTM tape header) is
detected in the standalone tape drive being used.
 Manually
 There are several methods to configure volumes manually:
 via NetBackupTM Administration Console (Windows or Java)
 via command line interface
 via Volume Configuration Wizard
 When configuring media manually the administration is in
complete control of the ‘mediaIDs’ assigned to volumes.
• The next slides discuss issues relating to configuring media.
Volume Identification
• As defined earlier, a ‘volume’ is any piece of ‘removable’ media.
• Each ‘volume’ is known in Media Manager by its ‘mediaID’.
• A ‘mediaID’ is an identifier, 1 to 6 alpha-numeric digits in length.
 This ‘mediaID’ is the identifier by which the volume is referenced
by Media Manager (vmd) and by ‘user’ applications, such as
NetBackupTM and Storage Migrator.
• In addition to the ‘mediaID’ – which is a ‘soft’ identifier – most
volumes (tapes or optical disks) will have an external label that is
used by a human (operator) to physically identify the volume.
 Most often in commercial applications the external label is in the
form of a ‘barcode’ label – which in addition to being readable by
a human – is machine readable.
 Occasionally, the external label on a volume is a handwritten
label affixed to the outside of the media.
• It is always preferred that the ‘external’ label match the ‘mediaID’
Volume Identification and Rules for Configuring Media
• When configuring media there are three kinds of Media Manager
‘rules’ that can be applied:
 Barcode Rules
 Media ID Generation Rules
 Media ID Prefixes
• Each of these ‘types’ of rules have a specific purpose relating to the
creation of media.
• Each of these ‘types’ of rules apply in specific situations.
• The slides which follow will define each of these types of rules.
Volume Identification and Barcode Rules
• What is a ‘barcode’ rule?
 Simply put, a barcode rule tells NetBackupTM how to define a
volume based upon a barcode label that is present on the
exterior of the volume.
 In other words – when a ‘robot inventory’ is performed and
Media Manager detects a ‘barcode label’ on a volume that
matches an existing ‘barcode rule’, Media Manager applies
the contents of the barcode rule to define the characteristics
of the volume, such as the ‘type of media’ (cleaning tape) or
the ‘volume pool’ to which the volume belongs.
 A ‘barcode rule’ does not modify/manipulate the ‘mediaID’ of the
volume that is created. The resulting ‘mediaID’ is the same as
the ‘barcode label’ on the volume.
 Barcode rules apply only during a NetBackupTM ‘robot inventory’.
Volume Identification and Barcode rules
• What is a ‘barcode’ rule?
 During a robot inventory operation, a barcode rule tells
NetBackupTM how to define characteristics of media based upon
a barcode label that is present on the exterior of the volume:
 Volume Pool the volume will be placed into.
 Media Type associated with the volume.
 Maximum mounts or Maximum cleaning (if cleaning media)
 Description field associated with the volume
Volume Identification and Media Labels barcode labels
• ‘Barcode labeled’ media
 A few facts about barcode labels:
 Barcodes labels are coded using X Y Z 1 2 3
various encoding methods (Code
39, UPC, Code 128)
 Barcode readers are available on C L N 1 2 3
most/many tape libraries
 Not all barcodes are six digits long
• ‘Manually labeled’ media J Z N A 5 1 9 9
 Only one rule when media labels are
handmade – there are no rules!
 Humans must read the label – while it
is preferred that the ‘mediaID’ match
the ‘label’ it is the administrations job
to ensure this.
Creating Barcode Rules
• Using NetBackupTM Administration Console GUI (Java-based)
Right-mouse click
• Using NetBackupTM Administration Console GUI (Java-based)
1. Select your ‘robot’.

2. Select ‘Update volume configuration’.
3. Press ‘Advanced Options’ button.
4. On “Advanced Robot Inventory Options’
select ‘Barcode Rules’ Tab.
5. Press ‘New’ button to create a new barcode rule.
• Using NetBackupTM Administration Console GUI (Windows-based)
Right-Mouse Click
• Using NetBackupTM Administration Console GUI (Windows-based)
1. Select your ‘robot’.

2. Select ‘Update volume configuration’.
3. Press ‘Advanced Options’ button.
4. On “Advanced Robot Inventory Options’
select ‘Barcode Rules’ Tab.
5. Press ‘New’ button to create a new barcode rule.
• ‘Barcode rule’ parameters
Windows-based GUI
Java-based GUI
• The ‘Advanced Robot Inventory Options’ ’Barcode Rules’
displays a list of the ‘barcode rules that have been created
Configuring Bar Code Rules
• ‘barcode’ rules database (Unix-based Master servers)
 <install_path>/openv/volmgr/database/ruleDB file
Rule # Version Barcode tag Media Type pool # max mounts comment
(0=none)
Configuring Bar Code Rules
• ‘barcode’ rules database (Windows-based Master servers)
 <install_path>\VERITAS\volmgr\database\ruleDB file
Rule # Version Barcode tag MediaType pool # max mounts comment

(0=none)
Volume Identification and Media ID Generation Rules
• What is a ‘Media ID Generation’ rule?
 During a robot inventory, a ‘Media ID Generation’ rule dictates to
Media Manager how it will interpret a ‘barcode label’ in the
creation of a ‘mediaID’.
 By default, NetBackupTM uses the last six characters of a
barcode label to generate a Media ID during a robot inventory.
This is referred to as the default Media ID generation rule.
 A ‘Media ID Generation’ rule allows NetBackupTM to select and
use barcode label digits other than the last six characters of a
barcode label, when generating a ‘mediaID’ for a volume during
Robot Inventory.
 Most customers will use the ‘standard’ rule (use last six
characters of barcode label in the order read).
Volume Identification and ‘Media ID Generation’ Rules
• Specifics of ‘Media ID Generation’ rules
 Adding ‘Media ID Generation’ rules allows the customer to
choose which six, of up to 13 characters on a barcode label, are
to be used to generate the ‘mediaID’.
 Specific character(s) can also be defined in lieu of using six
characters derived from the bar code label.
 ‘Media ID Generation’ rules may be used, not only to select
which barcode label digits are used, but to change the ‘order’ of
the digits used in the resulting ‘mediaIDs’.
 ‘Media ID Generation’ rules can be tape library specific.
Multiple ‘Media ID Generation’ rules may specify that different
barcode label characters be used to generate the ‘mediaIDs’ for
different tape libraries.
Volume Identification and ‘Media ID Generation’ Rules
• Examples of use of ‘Media ID Generation’ rules for LTO tapes
If ‘Media ID Generation rule’ is: 1:2:3:4:5:6
Resulting Media ID
And barcode is X A N 4 5 9 L 1 XAN459
If ‘Media ID Generation rule’ is: #B:#C:#D:4:5:6
Resulting Media ID
And barcode is X A N 4 5 9 L 1 BC D459
If ‘Media ID Generation rule’ is: 5:6:4:2:1:#Z
Resulting Media ID
And barcode is X A N 4 5 9 L 1 294AXZ
Configuring ‘Media ID Generation’ Rules
• Using the NetBackupTM Administration Console (Java-based)
See ‘default’ rule.

 The ‘rule’ created is displayed on ‘Media ID Generation’ tab
 Results of previous rule – following ‘robot inventory’
NetBackup™ 5.0 Media
• Using the NetBackupTM Administration Console (Windows-based)
See default rule.

 The ‘rule’ created is displayed on ‘Media ID Generation’ tab
 Results of previous rule – following ‘robot inventory’
Configuring Media ID Generation Rules
• ‘Media ID Generation’ rule(s) – stored in ‘vm.conf’
 On Unix-based Master server systems
 <Install_path>/openv/volmgr/ directory
Keyword = [robot #] [barcode length] [genrule]

Configuring Media ID Generation Rules
• ‘Media ID Generation’ rule(s) – stored in ‘vm.conf’
 On Windows-based Master server systems
 <install_path>\VERITAS\Volmgr\ folder
Keyword [Robot Number] [Barcode length] Genrule

Volume Identification and Media ID Prefixes
• What is a ‘Media ID Prefix’?
 While both ‘Barcode Rules’ and ‘Media ID Generation Rules’
apply to situations where barcodes are used during a robot
inventory, the ‘Media ID Prefix’ applies when:
1. A tape library does not have a barcode reader, and/or
2. Media in a tape library does not have barcode labels, or
3. Standalone tape drives are being used, and during a
NetBackupTM operation that requires a non-specific
‘mediaID’, a non-labelled (no NetBackupTM tape header) is
found in the standalone drive being used for the operation.
 The ‘Media ID’ prefix will define the beginning character(s) to be
used by Media Manager in the creation of new ‘mediaIDs’ for
the volume(s). By default, Media Manager uses a ‘Media ID’
prefix of ‘Axxxxx’, so that ‘mediaIDs’ generated will be of the
form A00000, A00001, A00002, and so on.
Volume Identification and ‘Media ID Prefixes’
• Specifics of ‘Media ID Prefixes’
 The default ‘Media ID Prefix’ used by Media Manager is
‘Axxxxx’.
 Volumes created by Media Manager when using the DEFAULT
‘Media ID Prefix’ will have ‘mediaIDs’ beginning at ‘A00000’,
then ‘A00001’, ‘A00002’, and so on.
 Media Manager will keep track of the last ‘mediaID’ created
using the ‘Media ID Prefix’ and will assign the next
sequential ‘mediaID’ when creating the next volume (when
using the ‘Media ID Prefix).
 A customer-generated ‘Media ID Prefix’ overrides the default
and implements the customer’s own ‘mediaID’ naming scheme.
 There is no guarantee, when using a ‘Media ID Prefix’ that the
‘mediaID’ will match the label on the exterior of the volume
cartridge. Careful administration is required.
Configuring ‘Media ID Prefixes’ – for ‘non-robotic’ media
Configuring ‘Media ID Prefixes’ – for ‘robotic’ media
• Results in ‘vm.conf’ file – Unix-based Master servers
 Located in: <install_path>/openv/volmgr/ directory
Configuring ‘Media ID Prefixes’ – for ‘non-robotic’ media
Setting the ‘Media ID Prefix’ on this
screen will cause the prefix to be
applied to all non-barcoded media
during THIS ‘robot inventory’ session
only. The ‘vm.conf’ file is not affected.
• ‘vm.conf’ file – Windows-based Master servers
 Located in: <install_path>\VERITAS\volmgr folder
• Results of setting ‘Media ID Prefix’ in ‘vm.conf’ file
 ‘Prefix’ is applied to name ‘non-barcoded’ media detected
Configuring Volumes
Configuring Volumes (Media)
• Volumes (Media) can configured:
 By configuring volumes manually using the NetBackupTM
Administration Console GUI (Java-based or Windows-based)
 By running a ‘robot inventory’ on a robotic device (tape library)
using the NetBackupTM Administration Console GUI – (Java-
based or Windows-based).
 By running the ‘Volume Configuration Wizard’.
 By using provided Media Manager command line interface
commands.
• Remember, configuring volumes is simply the process of adding
volume records (one record per volume/’mediaID’) to the Volume
Database (volDB).
• Manually adding volumes
 Using NetBackupTM Administration Console (Java-based)
• Manually adding volumes using Java-based GUI
• Create one or more volumes
• If creating multiples volumes
– must specify ‘naming style’.
 ‘mediaIDs’ will be
sequential.
 All will be same ‘media
type’
 All will reside in same
Volume Pool
 All will have same
description (if used)
• If robotic media are created:
 Slot locations will be
sequential
 Take care to match
‘mediaID’ to media label.
• Manually adding volumes using Java-based GUI
‘mediaIDs’ created by
previous operation
• Manually adding volumes
 Using NetBackupTM Administration Console (Windows-based)
• Manually adding volumes using Windows-based GUI
• Create one or more volumes
• If creating multiples volumes
– must specify ‘naming style’.
 ‘mediaIDs’ will be
sequential.
 All will be same ‘media
type’
 All will reside in same
Volume Pool
 All will have same
description (if used)
• If robotic media are created:
 Slot locations will be
sequential
 Take care to match
‘mediaID’ to media label.
• Manually adding volumes using Windows-based GUI
• Adding volumes using the ‘Robot Inventory’
 Possible Preliminary Steps to ‘robot inventory’:
 Creating ‘barcode rule(s)’ is optional, but very common.
 Creating ‘Media ID Generation’ rules is optional
 ‘Media ID Prefix’ is applied only in certain situations.
 The actual ‘robot inventory’ process:
 Show contents of robot. Queries robot for its tape contents
(gathered from library memory).
 Compare robot contents with current Volume Database (volDB)
(results of previous step with current ‘volDB’ contents).
 Preview the volume configuration update (determines what
changes are required to update the ‘volDB’).
 Perform volume configuration update (updates volDB with the
changes).
• Adding volumes using the ‘Robot Inventory’ (Java-based)
• Steps in ‘robot inventory’:
1. Select ‘robot number’ on
which to perform inventory.
2. Show contents.
3. Compare contents with
volume configuration
(volDB).
4. Preview ‘changes’ (to
volDB’).
5. Update volume
configuration (write
Results of ‘Show Contents’ changes to ‘volDB’).
2. Show contents.
(volDB).
4. Preview changes (to
‘volDB’)
5. Update volume
changes to ‘volDB’).
Results of ‘Compare’
2. Show contents.
(volDB).
‘volDB’.
5. Update volume
Results of ‘Preview changes’

2. Show contents.
(volDB).
‘volDB’.
5. Update volume
Results of ‘Update’
These ‘mediaIDs’ were added during ‘robot inventory’ –

both ‘barcode’ and ‘Media ID Generation’ rules were used.
• Adding volumes using the ‘Robot Inventory’ (Windows-based)
2. Show contents.
(volDB).
volDB’).
5. Update volume
Results of ‘Show Contents’ changes to ‘volDB’).
2. Show contents.
(volDB).
volDB’).
5. Update volume
Results of ‘Compare’
• Adding volumes using the ‘Robot Inventory’ (Widows-based)
2. Show contents.
(volDB).
volDB’).
5. Update volume
Results of ‘Preview changes’

2. Show contents.
(volDB).
volDB’).
5. Update volume
Results of ‘Update’
These ‘mediaIDs’ were added during ‘robot inventory’ - ‘barcode

rules’, ‘Media ID Generation’ rules, and ‘Media ID Prefix’ were used.
• Adding volumes using the ‘Volume Configuration Wizard’
 The ‘Volume Configuration Wizard’ - both Java-based a
Windows-based version – provide for the creation of Volumes
(media).
 Can initiate ‘robot inventory’ and/or manually create volumes
 By initiating a ‘robot inventory’
Select the ‘robot’ to be inventoried.

 ‘robot inventory’  selecting ‘drive types’
 ‘robot inventory’  reviewing ‘inventory results’
 ‘robot inventory’  identifying cleaning media
 ‘robot inventory’  updating ‘volDB’ for cleaning media
 Configuring additional volumes (media)
OR
 Configuring ‘Standalone’ volumes (media)
The ‘wizard’ creates

the volumes.
 Configuring ‘Standalone’ volumes (media)
 ‘mediaIDs’ created by ‘wizard’ are based upon ‘media type’ –
here ‘media type’ is DLT2  ‘mediaIDs’ are DL2001-DL2006
Command Line Interface for working
with volumes and pools
Media Manager command line interface
• Media Manager provides a number of commands for working with
volumes, pools, and media-related objects
• Important CLI’s for working with Volumes and Pools
 vmadd
 vmchange
 vmdelete
 vmpool
 vmrule
 vmquery (queries the volDB)
 vmupdate
• If the ‘-h <hostname>’ option is used with any of these commands it
is used to specify the hostname of the system on which the Volume
Database (volDB) will be affected by the command. These
commands should only be used to modify ‘volDB’ information on the
defined Volume Database Host.
• The ‘vmadd’ Command
 Used to add volumes to the Volume Database (volDB).
 There are many command options/arguments available.
 The command below adds a volume as follows:
 ‘mediaID’ is ABC123 (-m ABC123)
 ‘media type’ is DLT (-mt dlt)
 Volume is in the ‘NetBackup’ volume pool (-p 1)
 Volume has a barcode of ABC123 (-b ABC123),
 Volume is resident in a TLD robot (-rt tld)
 robot number 1 (-rn 1)
 ‘robot control host’ Hosta (-rh Hosta)
 Volume is in slot 2 of robot (-rc 2)
vmadd -m ABC123 -mt dlt –p 1 -b ABC123 -rt tld -rn 1 -rh Hosta -rc1 2
• The ‘vmchange’ Command
 Changes volume information in Volume Database (volDB).
 The following command changes the expiration date of volume
ABC123:
vmchange -exp 12/31/04 23:59:59 -m ABC123
 The following command changes the Volume Pool in which the

volume ABC123 resides to pool 1 (which is the ‘NetBackup’
pool). This change takes place in the ‘volDB’ on host ‘dill’ (-h
<hostname>):
vmchange -h dill -p 1 -m ABC123

• The ‘vmdelete’ Command
 Delete volumes from the volume database.
 Only UN-ASSIGNED volumes can be deleted.
 The following command deletes a single volume:
vmdelete -m ABC123
 The following command deletes all volumes with the volume

group name of DELETE_ME:
vmdelete -v DELETE_ME
• The ‘vmpool’ Command
 Use this command to add, change, delete, or list volume
pools.
 The following command lists all pools configured on the host
where the command is executed:
vmpool -listall
• The ‘vmrule’ Command
 Use this command to add, change, delete, or list barcode
rules.
 The following command creates a rule that defines any tape
with a barcode starting with ABC as a DLT tape in the
‘NetBackup’ pool. The tape can be mounted up to 100 times
for writes and is given a description.
vmrule -add ABC dlt NetBackup 100 "DLT cleaning tape"

• The ‘vmquery’ command is used to
 Query the volume database for volume information. The -h, -b,
and -w options are not required, but you must choose only one
of the other (eleven) options.
 The ‘-h <hostname> option is used to specify the system on
which the query of the Volume Database (volDB) will occur. This
should always be used to point to the defined Volume Database
Host.
 The -b or -w option can be used in conjunction with any of the
other eleven options, but the -b or -w options cannot be
specified together. ‘-b’ and ‘-w’ provide different output formats.
 The following command lists all volume information, in brief
format from the volume database on the host named Hosta:
vmquery -h Hosta -b -a
• The ‘vmupdate’ Command
 Inventory the media contents of a robotic library and update
the Volume Database. If no options are specified, the volume
configuration is updated to match the robot contents.
 The following command updates the volume configuration on
the host named Master to match the contents of TLD robot 7
connected to the host Hosta:
vmupdate -rt tld -rn 7 -rh Hosta -h Master

Netbackup™ 5.0 Administration Fundamentals: Media Configuration and Management

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Netbackup™ 5.0 Administration Fundamentals: Media Configuration and Management

Загружено:

Авторское право:

Доступные форматы

NetBackup™ 5.

“Change Volume Database

• On Windows platforms, ‘tpconfig’ is not a menu-based utility.

 <install path>\VERITAS\volmgr\bin\tpconfig –d (Windows)

• Each pool has an entry in the Media Manager

• As Volumes are created they are assigned to

• Volumes may be moved from one volume B00004

Pool # version pool name host access UID GUID Description

Pool # version pool name host access UID GUID Description

Tapes are ‘standalone’

These volumes are ‘robotic’

1. Select your ‘robot’.

1. Select your ‘robot’.

Rule # Version Barcode tag MediaType pool # max mounts comment

If ‘Media ID Generation rule’ is: #B:#C:#D:4:5:6

If ‘Media ID Generation rule’ is: 5:6:4:2:1:#Z

See ‘default’ rule.

See default rule.

Keyword = [robot #] [barcode length] [genrule]

Keyword [Robot Number] [Barcode length] Genrule

Results of ‘Preview changes’

These ‘mediaIDs’ were added during ‘robot inventory’ –

Results of ‘Preview changes’

These ‘mediaIDs’ were added during ‘robot inventory’ - ‘barcode

Select the ‘robot’ to be inventoried.

The ‘wizard’ creates

vmchange -exp 12/31/04 23:59:59 -m ABC123

 The following command changes the Volume Pool in which the

vmchange -h dill -p 1 -m ABC123

 The following command deletes all volumes with the volume

vmrule -add ABC dlt NetBackup 100 "DLT cleaning tape"

vmupdate -rt tld -rn 7 -rh Hosta -h Master

Вам также может понравиться