Content-type: text/html
Man page of JBEDIT
JBEDIT
Section: Maintenance Commands (8)
Updated: Dec 11, 01m
Index
Return to Main Contents
NAME
jbedit
- Add and delete device definitions to and from a NetWorker jukebox.
SYNOPSIS
- jbedit
-
-a
-f
<device path>
-E
<element addr>
[
-s
server
] [
-j
<jukebox name>
] [
-v
]
- jbedit
-
-a
-f
<device path>
-S
<silo device identifier>
[
-s
server
] [
-j
<jukebox name>
] [
-v
] [
-F
]
- jbedit
-
-a
-f
<device name>
-l
[
-s
server
] [
-j
<jukebox name>
] [
-v
]
- jbedit
-
-d
-f
<device path>
[
-s
server
] [
-j
<jukebox name>
] [
-v
]
- jbedit
-
-h
DESCRIPTION
jbedit
allows a NetWorker user with "Configure NetWorker" privileges to add or delete
drive
and
device
definitions to or from an existing jukebox definition
in the NetWorker database.
A
drive
is defined in NetWorker as "the physical backup object, such as a tape drive,
disk, or file" and a
device
as "the access path to the physical drive." Every
drive
therefore has at least one
device
associated with it, and every
device
has exactly one
drive
with which it can be associated.
The addition of a device, even on an existing
storage node, may require changes to the Dynamic Drive Sharing (DDS) licenses.
jbedit
complements the
reconfigure library
feature available through the
Networker Management Console.
jbedit
can be used as a fallback means of editing library configurations
if, for some reason, the
reconfigure library
program is limited (for example, the library does not return the drive serial
numbers).
jbedit
supports all direct attached SCSI/SJI, SAN, NDMP and AlphaStor libraries as well as Silos.
If the
NSR_JUKEBOX
environment variable is set,
jbedit
uses its value as the name of the jukebox to edit.
This behavior may be overridden by
-j
option.
If neither of these options are present,
jbedit
attempts to retrieve the list of all available jukeboxes on the server, and
prompts for a jukebox to be selected if more than one is available.
To edit the library configuration, the jukebox must be
enabled
and
ready
(see
nsr_jukebox(5)).
jbedit
can be run from any storage node,
however it requires "Configure NetWorker" privileges.
OPTIONS
The following options are supported:
- -a
-
Add a drive/device.
- -d
-
Delete a drive/device.
- -h
-
Display the jbedit options and their usage.
- -E
-
The drive
element address.
This is the data element address of the
drive
with which the
device
is associated.
When a new
drive
or
device
is being added to a jukebox,
jbedit
needs to know the data element address of
the drive/device within the jukebox. The data element address is the
"decimal number" that the jukebox assigns to each of its drives.
Information about drives, data element addresses and
other information associated with a jukebox can be found in
relem(1m),
changers(1m),
sn(1m)
and
sjisn(1m).
- -S
-
The drive's
silo device identifier.
This is the identifier used by the silo controller to identify the
drive
with which the
device
is associated. Typical
silo device identifiers
are:
- ACSLS silos: 0,0,2,4
IBM 3494: 00004040
DAS silos: drive1, sdlt_3, etc.
(DAS administrator defined text up to
a couple of hundred characters)
-
If you get an error like "missing new drive information"
it is likely that the
silo device identifier
you entered does not match anything that the silo actually knows about. You should recheck the value with the silo administrator.
-
Note that jbedit does not verify that the
silo device identifier
that you entered actually corresponds to the
device path
that you entered - only that the
silo device identifier
that you entered exists on the silo in question.
- -F
-
The
FORCE
flag can be used when adding devices to a silo to force jbedit to create the
NetWorker
device for the specified
device path.
Note that we prefer you to use the
Scan for devices
function rather than this option since the scan will collect all of the information needed for proper configuration of
Dynamic Drive Sharing.
The
FORCE
flag will only work if the device you are adding is present on the system that you are running jbedit on.
- -l
-
The device being added is logical.
Logical devices may be added to AlphaStor libraries only.
- -j
-
Name of the jukebox that is to be edited.
- -f
-
Device path to be added or deleted.
A new device/drive instance may be added to a library only if
the device is auto-detected and available as an
unconfigured device
in the
NSR Storage Node
resource,
it is a logical device (see
-l
option), or if it is available as a standalone
NSR device
device.
See
ddmgr(1m)
and
nsr_storage_node_resource(5)
for more information on how to detect devices on a storage node.
See
EXAMPLES
on how to add a new device/drive to a jukebox.
Also see specific format restrictions when adding an NDMP device path.
- -s
-
Name of the NetWorker server.
If not specified, local storage node is assumed as the NetWorker server.
- -v
-
Run in verbose mode.
Multiple
-v
options can be specified to increase the level of verbosity.
The higher the level, the more verbose the output will be.
Currently has a maximum of 5.
EXIT STATUS
jbedit
exits with a 0 on success and with a non-zero value on failure.
EXAMPLES
- Adding a drive/device:
-
To add a new device
/dev/rmt/0cbn
from this storage node:
-
jbedit -s server -j jbname -a -f /dev/rmt/0cbn -E 82
-
To add a new ACSLS silo device
/dev/rmt/13cbn
from this storage node:
-
jbedit -s server -j siloname -a -f /dev/rmt/13cbn -S 0,0,2,3
-
To add a new device
/dev/rmt/0cbn
from storage node "sn":
-
jbedit -s server -j jbname -a -f sn:/dev/rmt/0cbn -E 82
-
To add an NDMP device
nrst0l
from storage node "ndmpsn":
-
jbedit -s server -j jbname -a -f "ndmpsn:nrst0l (NDMP)" -E 82
Please make sure that the device path ends with
" (NDMP)".
-
To add a logical device
ldev01
to an AlphaStor library from storage node "sn":
-
jbedit -s server -j jbname -a -f sn:ldev01 -l
- Deleting a drive/device:
-
To delete device
/dev/rmt/0cbn
from this storage node:
-
jbedit -s server -j jbname -d -f /dev/rmt/0cbn
-
To delete silo device
/dev/rmt/13cbn
from this storage node:
-
jbedit -s server -j siloname -d -f /dev/rmt/13cbn
-
To delete device
\\.\tape0
from storage node "sn":
-
jbedit -s server -j jbname -d -f sn:\\.\tape0
-
To delete an NDMP device
nrst0l
from storage node "ndmpsn":
-
jbedit -s server -j jbname -d -f "ndmpsn:nrst0l (NDMP)"
FILES
- /nsr/res/nsrdb
-
The NetWorker resource database.
SEE ALSO
ddmgr(1m),
changers(1m),
jbconfig(1m),
nsrjb(1m),
relem(1m),
sjisn(1m),
sn(1m),
nsr_device(5),
nsr_jukebox(5),
nsr_storage_node(5),
nsr_storage_node_resource(5),
EMASS_silo(1m),
IBM_silo(1m),
STK_silo(1m)
DIAGNOSTICS
The following are some messages that jbedit might produce
along with their implications and possible solutions.
cannot connect to NSR service on <server name>
-
jbedit was unable to connect to the NetWorker server on
the specified host name.
Check that the server is up and running on the server host and
that it is reachable from the host on which jbedit is running and
retry the operation.
User <user name> on <storage node> does not have
Configure NetWorker privilege on <server name>
-
The user does not have privileges to add/remove devices.
No jukeboxes are currently usable.
-
There are no jukeboxes configured on the server or no configured jukeboxes are
enabled
and
ready.
Please check
nsr_jukebox(5)
for more details on the "enabled" and "ready" states.
Cannot find jukebox <jukebox name> for server <server name>
-
The jukebox name specified with
-j
option is invalid.
Please check that the jukebox name is defined on the server.
Cannot find any jukebox with a device named <device name>
for server <server name>
-
While deleting the device with
-d
option, either the jukebox name specified with
-j
option is invalid or the device name specified with
-f
option is invalid.
Couldn't retrieve NSR Storage Node resource information
for <storage node>
-
The
nsr_storage_node_resource(5)
on which the device is going to be created does not exist on the server.
Create a new storage node for <storage node> and run 'Scan for devices'
before adding any new devices from the <storage node>.
The device <device name> is already part of jukebox <jukebox name>
-
The device name specified with
-f
option already belongs to <jukebox name>.
Cannot find device <device name> in 'unconfigured device names' resource
-
The device name specified with
-f
option is not available from
nsr_storage_node_resource(5).
Please run 'Scan for devices' on the storage node to discover the device. You may also use the
-F
flag to override this error and create a basic NetWorker device if you are using jbedit to add a device to a silo, although the 'Scan' method is preferred as it collects all the information necessary to properly configure Dynamic Drive Sharing.
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- OPTIONS
-
- EXIT STATUS
-
- EXAMPLES
-
- FILES
-
- SEE ALSO
-
- DIAGNOSTICS
-
This document was created by
man2html,
using the manual pages.
Time: 02:37:02 GMT, October 02, 2010