nsr_mount_request man page on OSF1

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
OSF1 logo
[printable version]


NSR_MOUNT_REQUEST(5)					  NSR_MOUNT_REQUEST(5)

NAME
       nsr_mount_request - NetWorker resource type "NSR mount request"

SYNOPSIS
       type: NSR mount request

DESCRIPTION
       When  a	nsrmmd	processes  requires  media for a session, e.g. save or
       recover, it sends a request to nsrd. If there  is  no  media  currently
       mounted which meets the requirements of the nsrmmd process, nsrd starts
       a nsrjb command to mount media. Before nsrd starts the nsrjb command  a
       resource of the type NSR mount request is created.  The resource exists
       until the corresponding nsrjb command exits.  This resource and all its
       attributes are read only. A resource of this type may not be created or
       deleted using any administrative interface.   See  nsr_resource(5)  for
       information  on	NetWorker  resources.	To  view the NSR mount request
       resources run:
	      nsradmin -c "type:NSR mount request"
       Be sure to include quotation marks and to insert a space between "NSR",
       "mount", and "request".

ATTRIBUTES
       The  following  attributes  are defined for the resource type NSR mount
       request.	 The information in parentheses describes  how	the  attribute
       values  are  accessed.	Read-only  indicates  that the value cannot be
       changed by an administrator.  Hidden indicates a	 hidden	 attribute  of
       interest	 only  to  programs  or experts.  These attributes can only be
       seen when the hidden  option  is	 turned	 on  in	 nsradmin(8).	Static
       attributes change values rarely, if ever.  Dynamic attributes have val‐
       ues that change rapidly.	 For example, an attribute marked  (read-only,
       static) has a value that is set when the attribute is created and never
       changes.

       name			   (read-only, static)
	      The name attribute corresponds to the instance of the nsrjb com‐
	      mand  that  was  created	to  load  the  media described by this
	      resource. The instance of the nsrjb command is  specified	 using
	      the -O command line option.
	      Example: name: 15;

       nsrmmd id		   (read-only/ static)
	      This  attribute  records	the  number that identifies the nsrmmd
	      process which requested the media.
	      Example: nsrmmd id: 2;

       nsrmmd host		   (read-only/static)
	      This attribute indicates the name of the host on which the  nsr‐
	      mmd process which requested the media is running.
	      Example: nsrmmd host: host1;

       nsrmmd mount id		   (read-only/static/null ok)
	      Some  operations, e.g. cloning, require two nsrmmd processes and
	      two volumes be mounted at the same  time.	  The  value  of  this
	      attribute	 will  be the same for all mount requests submitted by
	      such nsrmmd processes.  When the nsrmmd which requested media is
	      not  participating in an operation which requires another nsrmmd
	      process to complete, the value of this attribute is null.
	      It is possible that only one cooperating nsrmmd process  may  be
	      requesting  media	 be mounted. For example, this may occur while
	      cloning data. If the nsrmmd writing data reaches	end  of	 media
	      while  the  nsrmmd  process reading data is still has data to be
	      cloned, then the nsrmmd process writing data will request a  new
	      volume be mounted.
	      Example: nsrmmd mount id: 5;

       operation		   (read-only/static)
	      This  attribute  indicates  the operation being performed by the
	      nsrmmd requesting media be mounted. The value for this attribute
	      attribute	 can  be  either  reading,  writing, or media.	If the
	      value is set to reading, the nsrmmd process is reading data from
	      media. It could either be recovering data or the process that is
	      reading data from media as part of a cloning operation.  If  the
	      value  is	 set to writing, the nsrmmd process is writing data to
	      media. It could either be saving data or	the  process  that  is
	      writing  data  to	 media as part of a cloning operation.	If the
	      value is set to media, the nsrmmd	 is  performing	 an  operation
	      that involves only the media, e.g. labeling media.
	      Example: operation: writing;

       data operation		   (read-only, static, null OK)
	      This  attribute  has a value when the operation attribute is set
	      to either reading or  writing.  If the  operation	 attribute  is
	      set  to  media  this  attribute  has  no value.  Values for this
	      attribute	 can  be  either  save,	 recover,  archive,  retrieve,
	      migrate, clone, or consolidate.
	      Example: data operation: save;

       media operation		   (read-only, static)
	      This  attribute  indicates  operations  which are expected to be
	      performed on the media after it is loaded into a drive.	Values
	      for  this attribute can be either mount, label, relabel, or ver‐
	      ify.  This attribute may have multiple values. For example media
	      may be labeled and then mounted.
	      Example: media operation: label, mount;

       pool			   (read-only, static)
	      The  pool	 to  which  the requested media belongs or the pool to
	      which the media is to be added if the media operation  attribute
	      includes	label  or  relabel  values.   Valid  values  for  this
	      attribute are any currently defined pool.
	      Example: pool: Default;

       volume			   (read-only, static, null OK)
	      This attribute records the name of  the  volume  being  mounted.
	      The  value  of  the  attribute is NULL if the volume name is not
	      known at the time the operation is started. This can occur  when
	      labeling scratch media.
	      Example: volume: vol1;

       client			   (read-write, static, null ok)
	      This  attribute  is  used	 to  record  the name of the NetWorker
	      client from which data is being read  while  saving  (archiving)
	      data  or	to  which  data	 is  being  written  while  recovering
	      (retrieving) data.
	      Example: client: host1;

       save set			   (read-only, static, null ok)
	      This attribute specifies the data being  read  from  client  and
	      written  to media (save) or the data read from media and written
	      to client (recover).
	      Example: save set: /usr;

       group			   (read-only, static, null ok)
	      If the operation being performed by the nsrmmd  which  requested
	      the  mount  is the result of a command initiated by savegrp (8),
	      this attribute records the name of the group.   Otherwise	 there
	      is  no value.  Valid values for this attribute are any currently
	      defined group.
	      Example: group: Default;

EXAMPLE
       A complete example follows:

		   type:  NSR mount request;
		   name:  10;
	      nsrmmd id:  2;
	    nsrmmd host:  host1;
	nsrmmd mount id:  tape;
	      operation:  writing;
	 data operation:  save;
	media operation:  label, mount;
		 volume:  vol1;
		   pool:  Default;
		 client:  host1;
	       save set:  /usr;
		  group:  Default;

FILES
       /nsr/res/nsrdb - files in this directory should never be edited
       directly. Use nsradmin(8), or NetWorker Management Console instead.

SEE ALSO
       nsr_resource(5), nsr_pool(5), nsr_group(5), nsr_service(5), nsr(8),
       nsrmmd(8), nsradmin(8),

NetWorker 7.3.2			  Aug 23, 06		  NSR_MOUNT_REQUEST(5)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server OSF1

List of man pages available for OSF1

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net