Maintenance Procedures NSRJB ( 8 ) NAME nsrjb − NetWorker jukebox control command SYNOPSIS nsrjb [ −C ][−j name ][−s server ][−v ][−f device ][−S slots | −T Ta gs | volume names ] nsrjb −L [ −j name ][−s server ][−gimnqvG ][−Y | −N ][−R | −B ][−b pool ][−f device | −J hostname ][−e forev er ][−c capacity ][−o mode ][−S slots | −T tags | volume names ] nsrjb −l [ −j name ][−s server ][−nvqrG ][−R [ −b pool ]][−f device | −J hostname ][−S slot | −T tags | volume names ] nsrjb −u [ −j name ][−s server ][−qv ][−f device ][−S slot | −T tags | volume names ] nsrjb −I [ −j name ][−s server ][−Evpq ][−I | −f device ][−S slots | −T tags | volume_names ] nsrjb −p [ −j name ][−s server ][−vq ][−f device ][−S slot | −T tag | volume name ] nsrjb −o mode [ −j name ][−s server ][−Y ][−S slots | −T tags | volume names ] nsrjb −H [ −j name ][−s server ][−EHvp ] nsrjb −h [ −j name ][−s server ][−v ] nsrjb −U uses [ −j name ][−s server ][−S slots | −T tags ] nsrjb −V [ −j name ][−s server ] nsrjb −d [ −j name ][−s server ][−v ][−N ][−Y ][−P ports ][−S slots ][−T tags ][volume names ] nsrjb −w [ −j name ][−s server ][−v ][−N ][−Y ][−P ports ][−S slots | −T tags | volume names ] nsrjb −a [ −j name ][−s server ][−vd ][−T tags |[−T tags ] volume names ] nsrjb −x [ −j name ][−s server ][−vwX ][−T tags | −S slots ] nsrjb −F [ −j name ][−s server ][−v ] −f device DESCRIPTION The nsrjb program manages resources in two broad classes of jukeboxes, remotely managed jukeboxes and locally managed jukeboxes. Remotely managed jukeboxes are controlled through an external agent. nsrjb communicates with this agent to gain access to jukebox resources. The agent allows multiple appli- cations, including multiple NetWorker servers, to share resources in the jukebox. Examples of agents are AlphaStor and StorageTek’s ACSLS . nsrjb communicates directly with a locally managed jukebox, there is no intervening agent. Resources in a locally managed jukebox can be used by only one NetWorker server. NetWorker 7.3 Last change: Dec 02, 05 1 Maintenance Procedures NSRJB ( 8 ) For a locally managed jukebox, the jukebox resource is used to track the state of the entire jukebox. The resource records the number of drives and slots in the jukebox. It is also used to track whether devices are loaded, whether there is media residing in the slots, the name of any volume on the media, as well as other information. See nsr_jukebox(5). The jukebox resource for a remotely managed jukebox does not reflect the current state of the entire juke- box, only NetWorker’s view. Media in remotely managed jukeboxes must be allocated before NetWorker may access it. For more details, see the description of the −a option. The number of slots in a remote juke- box resource increases as media is allocated for NetWorker’s use and decreases as media is deallocated after NetWorker has no further use for the media. The order in which media is listed in the jukebox resource does not necessarily reflect physical location within the jukebox. The number of drives in a remote jukebox is an upper bound on the number of volumes in the jukebox that NetWorker may access simultaneously. The nsrjb command is used to manage all jukeboxes for a NetWorker server. Use this command, rather than nsrmm(1m), to label, load, and unload the volumes contained within a jukebox. Multiple nsrjb com- mands may access a jukebox at any giv entime. A nsrjb command which requires use of jukebox resources does not directly perform the requested opera- tion. Instead the command makes a request of the NetWorker server process, nsrd, which forwards the request to nsrmmgd for processing. Since nsrjb does not perform the operation directly, killing nsrjb will not cause the operation to be aborted. Provision for operation cancellation is built into nsrjb via an interrupt handler that is tied to SIGINT. This means that if you have a nsrjb command running, and you want the operation to be cancelled, then you may do it either by means of Control-C against the nsrjb process, or using the UNIX ’kill’ command to send a SIGINT signal. A single Control-C or SIGINT will cause the operation to be cancelled, with nsrjb still monitoring the sta- tus of the appropriate NSR jukebox operation status resource until it is clear that the operation has in fact terminated. A second Control-C or SIGINT will tell nsrjb to exit without waiting for confirmation of the operation’s termination. A NSR jukebox operation status resource will be automatically generated and managed by nsrd for each jukebox operation that is created, regardless of whether that operation was initiated automatically by nsrd or is created explicitly by invoking nsrjb This NSR jukebox operation status resource tracks the current state of the operation, holds all messages (error, informational, or verbose) related to the operation, and generally acts as a communication path between the nsrjb process that invoked the operation, and the various Networker programs that carry the operation out. See the nsr_op man page for more details on this resource. A volume resides on a side of a physical piece of media. Examples of piece of media are tape cartridges or optical disks. Tape cartridges have one side and therefore have one volume residing on each cartridge. Optical media may have two sides with a volume residing on each side of the media. Each volume within a jukebox and each jukebox has a name recognized by NetWorker. A volume name is specified when the vol- ume is first labeled by NetWorker. You can change the volume name when a volume is relabeled. Net- Worker refers to volumes by their volume names. For example, when requesting the mount of a volume, NetWorker asks for it by volume name. Before using nsrjb, the jukebox and its device resources must be added to the NetWorker server. Use jbconfig to add the jukebox resource and its device resources to the NetWorker server. The jukebox resource is described in nsr_jukebox(5). NetWorker 7.3 Last change: Dec 02, 05 2 Maintenance Procedures NSRJB ( 8 ) When a NetWorker server requires a volume for backup or recovery and an appropriate volume is not already mounted, the server checks the media database to verify whether a jukebox contains a volume that satisfies the media request. If so, nsrd sends a request to nsrmmgd to load the media into an idle device. The Available Slots attribute specifies the slots containing volumes available to automatically satisfy Net- Worker requests for writable volumes. When automatically selecting a writable volume for backup, Net- Worker only considers volumes from the list of available slots. It is important to note that the Available Slots attribute does not limit what slots the user running nsrjb can operate on. nsrjb attempts to determine which jukebox to use based on the options −j , −f , or a volume name . If one or more of these options do not uniquely identify a jukebox and one must be selected, the nsrjb program prompts you to select a jukebox. You can set the NSR_JUKEBOX environment variable to the name of the jukebox you want the nsrjb program to use by default. OPTIONS Options are separated into two groups. The first are the options which specify the operation to be per- formed, e.g. label or load media. The second group list the additional options which provide arguments for the operation, e.g. specifying the media to be labeled or loaded. Note that option arguments that have spaces, for example, pool name, must be enclosed in double quotes. OPERATION OPTIONS −a This option is used in conjunction with the −T tags option, to allocate volumes in a remotely man- aged jukebox. A volume must be allocated before it can be labeled and used by a NetWorker server. For STL silos a −d option can be added for silos that support depositing (also known as importing or entering) tapes from their I/O ports. The −d must appear after the −a on the command line. This function is usually handled by the silo management software, but is added here for ease of use. This option may not be supported on all silos supported by NetWorker. There are two types of volumes which may be allocated or added to an AlphaStor jukebox resource: scratch or in-use. The term scratch is used to indicate volumes currently not being used by NetWorker. An in-use volume is one that was already used by NetWorker before being imported into AlphaStor. Use −a in conjunction with −T tags option to allocate volumes for NetWorker’s use. Both scratch and in-use volumes can be allocated this way. By specifying the barcode or physical cartridge label with this option, volumes from specific media cartridges may be allocated. In-use volumes will be discovered by the jukebox inventory operation. Use −a in conjunction with −T tags and volume names to directly add in-use volumes to an AlphaStor jukebox resource. The tag is the name given to the volume when it was imported into AlphaStor. The volume name is the volume name recorded in NetWorker’s media database. See −x for a description of how volumes are removed from a remote jukebox’s list of volumes available for use by a NetWorker server. −C Displays the current volumes in the jukebox and the devices associated with the jukebox. This is the default command option, used if no other command options are specified. It displays a list of slot numbers, volume names, media pools, optional bar code information, volume ids and volume modes. If the jukebox attribute Bar Code Reader is enabled and there are bar code labels on the media volumes, then the bar code label is included in the list.