Nsrlic

NAME

nsrlic − NetWorker license reporting command

SYNOPSIS

nsrlic [ −vi ] [ −s server ]

DESCRIPTION

The nsrlic command generates reports about all license information currently active on a NetWorker

server.

Nsrlic –v –s server

-I interactive mode : use command details to see all informations

Microsoft Windows 2000 [Version 5.00.2195]

C:\Documents and Settings\user5>nsrlic -vi

connecting to bormsback01.emea.borms.com ...

nsrlic: License Summary:

nsrlic: Available: sv=50, ws=0, clu=0, clu_nt=0, clu_unix=0, clu_linux=0, ndmp=

nsrlic: Borrowed: sv_borrowed=0, clu_borrowed_nt=0, clu_borrowed_unix=0, clu_b

orrowed_linux=0

nsrlic: Remaining: sv=42, ws=0, clu=0, clu_nt=0, clu_unix=0, clu_linux=0, ndmp=

nsrlic: Connected Servers: (8)

nsrlic: bormsapp04.emea.borms.com bormsback01.emea.borms.com bormsfs01.emea.roc

he.com bormsfs02.emea.borms.com bormsimage02.brd.borms.com bormsmanufact01.emea.

borms.com bormssan01.emea.borms.com

nsrlic: bormstest01.emea.borms.com

nsrlic: NetWorker Module for Microsoft SQL Server: Available=1, Remaining=1, Use

d=0

Available commands are:

summary - display a summary report of licenses

detail - display a detailed report of licenses

connect [server name] - connect to server

help - list command helps.

quit - quit out of nsrlic command.

nsrlic> detail

SERVER (UNIVERSAL) CLIENT LICENSES

Available: 50

Used: 8

Borrowed from Server: 0

Remaining: 42

Connected Clients: bormsapp04.emea.borms.com,

bormsback01.emea.borms.com,

bormsfs01.emea.borms.com,

bormsfs02.emea.borms.com,

bormsimage02.brd.borms.com,

bormsmanufact01.emea.borms.com,

bormssan01.emea.borms.com,

bormstest01.emea.borms.com;

WORKSTATION CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Borrowed from Cluster for NT: 0

Borrowed from Cluster for UNIX: 0

Borrowed from Cluster for LINUX: 0

Remaining: 0

Connected Clients: ;

NT CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

UNIX CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

LINUX CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

NDMP CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

SERVER/CLUSTER CLIENT TYPES

AIX: 0

Digital UNIX: 0

HP UX: 0

HP MPE: 0

Linux: 0

NetWare: 0

Network Appliance: 0

IBM DYNIX/ptx: 0

SGI: 0

Solaris: 0

SunOS: 0

UnixWare: 0

Windows NT Server: 8

WORKSTATION CLIENT TYPES

DOS: 0

Macintosh: 0

OS/2: 0

Windows 3.1x: 0

Windows 95: 0

Windows NT Workstation: 0

UX/4800: 0

Others: 0

Defined Clients: ;

PRE-5.0 CLIENT TYPES: ;

APPLICATION LICENSES

NetWorker Module for Microsoft SQL Server

Available: 1

Used: 0

Remaining: 1

Connected Clients: bormsmanufact01.emea.borms.com,

bormsmanufact01.emea.borms.com;

CLIENT PAKS: none;

CLIENT TYPES ALLOWED: Windows 3.1x client,

Windows 95 client,

Windows NT Server client,

Windows NT Workstation client;

nsrlic>

Lgtolmd

NAME

lgtolmd − Legato license daemon

SYNOPSIS

lgtolmd −p product −n version

Lgtolic

NAME

lgtolic − Legato license utility command

SYNOPSIS

lgtolic [ −s server ] −c enabler_code

lgtolic −i [ −m hostfile_dir ]

lgtolic [ −s server ] −l

lgtolic [ −s server ] −r [ −m hostfile_dir ] [ −f output_file ]

lgtolic [ −s server ] −u enabler_code −a authorization_code

lgtolic [ −s server ] −v enabler_code

DESCRIPTION

The lgtolic command is used to manipulate Legato licenses that are stored within a license resource

database.

clients

nsradmin> show name; NetWorker_version

nsradmin> print type: NSR client

Licences

SERVER (UNIVERSAL) CLIENT LICENSES

Available: 50

Used: 11

Borrowed from Server: 0

Remaining: 39

Connected Clients: ;

WORKSTATION CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Borrowed from Cluster for NT: 0

Borrowed from Cluster for UNIX: 0

Borrowed from Cluster for LINUX: 0

Remaining: 0

Connected Clients: ;

NT CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

UNIX CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

LINUX CLUSTER CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

NDMP CLIENT LICENSES

Available: 0

Used: 0

Remaining: 0

Connected Clients: ;

SERVER/CLUSTER CLIENT TYPES

AIX: 0

Digital UNIX: 0

HP UX: 0

HP MPE: 0

Linux: 0

NetWare: 0

Network Appliance: 0

IBM DYNIX/ptx: 0

SGI: 0

Solaris: 0

SunOS: 0

UnixWare: 0

Windows NT Server: 11

WORKSTATION CLIENT TYPES

DOS: 0

Macintosh: 0

OS/2: 0

Windows 3.1x: 0

Windows 95: 0

Windows NT Workstation: 0

UX/4800: 0

Others: 0

Defined Clients: ;

PRE-5.0 CLIENT TYPES: ;

APPLICATION LICENSES

NetWorker Module for Microsoft SQL Server

Available: 1

Used: 1

Remaining: 0

Query

Query Commands:

nsradmin> show name; NetWorker version

nsradmin> print type; NSR client

server clients=11

N	Fully Qualified Server Name	Version	HOMONYMS
1	bormsback01.emea.borms.com	NetWorker version: 7.2.Build.172	4
2	bormsapp01.emea.borms.com	NetWorker version: 7.2.Build.172	4
3	bormsapp02.emea.borms.com	NetWorker version: 7.2.Build.172	4
4	bormsapp04.emea.borms.com	NetWorker version: 7.2.Build.172	4
5	bormsback01.emea.borms.com	NetWorker version: 7.2.Build.172	4
6	bormsfs01.emea.borms.com	NetWorker version: 7.4.2.Build.431	4
7	bormsfs02.emea.borms.com	NetWorker version: 7.2.Build.172	4
8	bormsimage02.emea.borms.com	NetWorker version: 7.2.Build.172	4
9	bormsmanufact01.emea.borms.com	NetWorker version: 7.2.Build.172	5
10	bormssan01.emea.borms.com	NetWorker version: 7.2.Build.172	1
11	bormstest01.emea.borms.com	NetWorker version: 7.2.Build.172	2
12	rudmvapp01.emea.borms.com	NetWorker version: 7.2.Build.172	2

1. SERVER

a. Client Licences

server licenses=50, workstation licenses=0, cluster licenses=0, nt cluster licenses=0, unix cluster licenses=0, linux cluster licenses=0, NDMP licenses=0,

unix clientpak=false, linux clientpak=false, desktops clientpak=false, netapp clientpak=false, netware clientpak=false, nt clientpak=false, macintosh clientpak=false, hpmpe clientpak=false,

server type=23, storagenodes=0, dstoragenodes=0, sharednodes=0, diskbackup=0, lsm=false, single=false, server edition=false, enterprise edition=false, nt shared jb=true, unix shared jb=false, registration=true;

b. Modules Licences

"module 111 OFC: licenses=0, clients=0",

"module 6 BusinesSuite Module for Oracle: licenses=0, clients=0",

"module 8 BusinesSuite Module for Informix: licenses=0, clients=0",

"module 9 NetWorker Module for Microsoft SQL Server: licenses=1, clients=1",

"module 7 BusinesSuite Module for Sybase: licenses=0, clients=0",

"module 11 NetWorker Module for Microsoft Exchange Server: licenses=0, clie\nts=0",

"module 12 BusinesSuite Module for Lotus Notes: licenses=0, clients=0",

"module 13 NetWorker Module for Lotus cc:Mail: licenses=0, clients=0",

"module 15 BusinesSuite Module for SAP R/3 Oracle: licenses=0, clients=0",

"module 16 NetWorker Module for SAP R/3 Microsoft SQL Server: licenses=0, c\lients=0",

"module 14 NetWorker Module for Microsoft Mail: licenses=0, clients=0",

"module 18 NetWorker Module for Oracle: licenses=0, clients=0",

"module 19 Database Toolkit for Informix: licenses=0, clients=0",

"module 28 NetWorker Module for DB2: licenses=0, clients=0",

"module 31 Legato NetWorker for EMC Symmetrix for Oracle: licenses=0, clien\ts=0",

"module 32 Legato NetWorker Module for EMC Symmetrix for SAP/R3 on Oracle: licenses=0, clients=0",

"module 35 Legato NetWorker Module for Oracle: licenses=0, clients=0",

"module 42 Legato NetWorker Module for Oracle on Linux: licenses=0, clients\=0",

"module 45 SharePoint Portal Server for Windows: licenses=0, clients=0",

"module 47 Volume Shadowcopy Service for Windows: licenses=0, clients=0",

"module 85 Power Snap for Shadow Copy: licenses=0, clients=0",

"module 28 Legato Single Server Version for Oracle: licenses=0, clients=0",

Operations

nsr

nsr_ize(1m) The NetWorker installation script.

nsr_layout(5) Describes where NetWorker programs, files, and manual pages are installed.

NAME

nsr − NetWorker directive file format

DESCRIPTION

This man page describes the format of .nsr directive files. These files are interpreted by save(1m) and

Application Specific Module (ASM) programs, during NetWorker backup processes.

Directives appear in one of three distinct forms:

[+] ASM [args ...] : pattern ...

save environment

<< dir >>

The three forms are referred to as ASM specifications, save environment directives, and << dir >> directives,

respectively.

SYNOPSIS

type: NSR archive request

DESCRIPTION

Each NSR archive request is described by a single resource of type NSR archive request (see

nsr_resource(5)). To edit the NSR archive request resources for a NetWorker server type:

nsradmin -c "type:NSR archive request"

NAME

nsr_client − NetWorker resource type ‘‘NSR client’’

SYNOPSIS

type: NSR client

DESCRIPTION

Each NSR client is described by a single resource of type NSR client (see nsr_resource(5)). To edit the

NSR client resources for a NetWorker server type:

nsradmin -c "type:NSR client"

NAME

nsr_crash − How to recover from a disaster with NetWorker

For more information on using the recover command, see the recover(1m) manual page.

If the NetWorker server daemons or commands are lost, it may be necessary to re-install the server from the

NetWorker distribution media. Once the NetWorker server is installed and the daemons are running, other

NetWorker server files can be recovered using the recover command. When re-installing NetWorker you

must be sure to install the /nsr directory in exactly the same place as it was originally installed. The

machine used to recover files may be different that the one used to save the files, but it must have the same

hostname as the original machine.

To summarize, these are the steps you must do to recover your server after mmrecov completes.

1. Shut down your NetWorker server (nsr_shutdown -a). For Windows, you would stop the Net-

Worker services.

2. Changeto the /nsr directory (cd /nsr). For Windows, cd to the install location (default C:\Program

Files\nsr).

3. Save the temporary resource directory created when you reinstalled the NetWorker server (mv res

res.save). For Windows, use "My Computer" or "Windows Explorer" to rename the res directory

to res.save.

4. Move the recovered resource directory into place (mv res.R res). For Windows, use "My Computer"

or "Windows Explorer" to rename the res.R directory to res.

5. Restart the NetWorker daemons on the Server by running the platform dependent startup script.

Eg., on Solaris, this is "/etc/init.d/networker start". For Windows, you would start the NetWorker

services.

6. After verifying that the recovered resources are valid, remove the temporary resource directory

(rm -r /nsr/res.save). For Windows, use "My Computer" or "Windows Explorer" to send the

res.save directory to the recycle bin.

7. Recover your server and client indexes (nsrck -L7).

NOTE: The mmrecov command is only used to recover the NetWorker server’s media database and

resource files. Use nsrck to recover the server and client indexes.

NAME

nsr_data − Data formats for NetWorker Save and Recover

DESCRIPTION

All data in the NetWorker system is encoded using the eXternal Data Representation (XDR) standard.

When files are passed between client (see save(1m) and recover(1m)) and server (see nsrd(1m)) and media

(see nsrmmd(1m)), they are represented as a savestream, which is encoded as a linked list of savefiles.

There are currently 2 different savefile formats. A magic number at the start of each file indicates the particular

type of the following savefile thus allowing for self identifying savestreams containing more than

one savefile type. Logically each savefile consists of some header information followed by file data. The

original savefile1 format uses a doubly wrapped set of client attributes describing the file attributes and the

file data is encoded as a buck etlist. The newer savefile2 format uses an alternate singularly wrapped client

attributes with the file data encoded as a bucket-less succession of self describing sections each containing a

type, a length, and bytes of data. The file data section of a file is terminated by an ending section with a

type of 0 (NSR_ASDF_END).

NAME

nsr_device − NetWorker resource type "NSR device"

SYNOPSIS

type: NSR device

DESCRIPTION

Each storage device used by a NetWorker server is described by a single resource of type NSR device. See

nsr_resource(5) for information on NetWorker resources. To edit the NSR device resources run:

nsradmin -c "type:NSR device"

NAME

nsr_directive − NetWorker resource type ‘‘NSR directive’’

SYNOPSIS

type: NSR directive

DESCRIPTION

Each NSR directive is described by a single resource of type NSR directive (see nsr_resource(5)). To edit

the NSR directive resources for a NetWorker server, use nsradmin(1m) or nwadmin(1m).

NAME

nsr_getdate − convert time and date from ASCII

NAME

nsr_group − NetWorker resource type ‘‘NSR group’’

SYNOPSIS

type: NSR group

DESCRIPTION

Each NetWorker group is described by a single resource of type NSR group (see nsr_resource(5)). To

edit the NSR group resources for a NetWorker server type:

nsradmin −c "type:NSR group"

NAME

nsr_ize − NetWorker installation and removal

SYNOPSIS

nsr_ize [ −i | −r | −u ] [ −c | −t | −l | −s ] [ −kmnqxv ]

NAME

nsr_jukebox − NetWorker resource type ‘‘NSR jukebox’’

SYNOPSIS

type: NSR jukebox

DESCRIPTION

Each jukebox known to NetWorker is described by a single resource of type NSR jukebox. A jukebox

keeps track of the resources, volumes and devices that are being managed by an external media management

service and are available to this NetWorker server. An example of an external media management service

is OpenVault. This resource describes the physical characteristics of a jukebox. See nsr_resource(5).

To edit the NSR jukebox resources for a NetWorker server, type:

nsradmin -c "type:NSR jukebox"

NAME

nsr_label − NetWorker resource type ‘‘NSR label’’

SYNOPSIS

type: NSR label

DESCRIPTION

Each NSR label template is described by a single resource of type NSR label (see nsr_resource(5)). To

edit the NSR label resources for a NetWorker server, type:

nsradmin -c "type:NSR label"

Example:

next: aa.00;

Using the separator and field attributes shown above, the next attribute would show: next: aa.01;

NAME

nsr_layout - NetWorker file layout

SYNOPSIS

type: NSR layout

NAME

nsr_license − NetWorker resource type ‘‘NSR license’’

SYNOPSIS

type: NSR license

DESCRIPTION

A resource of type NSR license is used to describe each feature enabled in your NetWorker installation.

See nsr_resource(5) for more information on NetWorker resources. To inspect the NSR license resources

type:

nsradmin −c "type:NSR license"

NAME

nsr_migration − NetWorker resource type ‘‘NSR migration’’

SYNOPSIS

type: NSR migration

DESCRIPTION

Each NSR migration client is described by a single resource of type NSR migration (see nsr_resource(5)).

To edit the NSR migration resources for a NetWorker server type:

nsradmin -c "type:NSR migration"

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"

NAME

nsr_notification − NetWorker resource type ‘‘NSR notification’’

SYNOPSIS

type: NSR notification

DESCRIPTION

A resource of type NSR notification is used for each combination of an event, priority, and action handled

by the NetWorker notification system. A NetWorker notification consists of a single event type, a single

priority, and a message. The notification system posts each message to the action of each NSR notification

resource (by executing the command listed in the action, with the message on standard input) that includes

that event type and priority. See nsr_resource(5) for more information on NetWorker resources. To edit

the NSR notification resources type:

nsradmin −c "type:NSR notification"

NAME

nsr_policy − NetWorker resource type ‘‘NSR policy’’

SYNOPSIS

type: NSR policy

DESCRIPTION

Each NetWorker policy is described by a single resource of type NSR policy (see nsr_resource(5)). To

view the NSR policy resources for a NetWorker server, enter nsradmin at the command prompt to start the

nsradmin program. At the nsradmin prompt, enter:

nsradmin>print type:NSR policy

NAME

nsr_pool − NetWorker resource type ‘‘NSR pool’’

SYNOPSIS

type: NSR pool

DESCRIPTION

Each NSR pool is described by a single resource of type NSR pool (see nsr_resource(5)). To edit the NSR

pool resources for a NetWorker server type:

nsradmin −c "type:NSR pool"

NAME

nsr_regexp − regular expression syntax

NAME

nsr_resource − NetWorker resource format

SYNOPSIS

resource ::= attribute list <blank line>

attribute list ::= attribute [ ; attribute ]∗

attribute ::= name [ : value [ , value ]∗ ]

name, value ::= <printable string>

NAME

nsr_schedule − NetWorker resource type "NSR schedule"

SYNOPSIS

type: NSR schedule

DESCRIPTION

Each NetWorker schedule is described by a single resource of type NSR schedule (see nsr_resource(5)).

To edit the NSR schedule resources for a NetWorker server, type:

nsradmin −c "type:NSR schedule"

NAME

nsr_service − NetWorker server resource type ‘‘NSR’’

SYNOPSIS

type: NSR

DESCRIPTION

Each NetWorker server is described by a resource of type NSR. See nsr_resource(5) for general information

on NetWorker resources. To edit the NSR resource use the command:

nsradmin −c "type:NSR"

or use the nwadmin(1m) GUI.

NAME

nsr_shutdown − stop a NetWorker server’s processes

SYNOPSIS

nsr_shutdown [ −a ] [ −A ] [ −c ] [ −d ] [ −n ] [ −q ] [ −s ] [ −v ]

DESCRIPTION

nsr_shutdown terminates NetWorker processes on a NetWorker server. This command is simpler than the

procedure of using ps(1), grep(1), and kill(1).

OPTIONS

−a Terminates all daemons; this is the same as using the −A, −d, and −s options.

−A Terminates any nsralist(1m) processes.

−c Does not purge the savegrp(1m) worklist of non-completed savesets during a nsr_shutdown.

−d This is the default option; it terminates the server daemons. These may include nsrd(1m),

ansrd(1m), nsrindexd(1m), nsrexecd(1m), nsrib(1m), nsrmmd(1m), and nsrmmdbd(1m).

Since savegrp(1m), nsrexec(1m), and nsralist(1m) processes depend on the service daemons,

they are also terminated.

−n Echoes the kill(1) command without actually invoking it.

−q Perform the shutdown quietly; don’t prompt for confirmation.

−s Terminates any savegrp(1m) (and nsrexec(1m)) processes.

−v Verbose: Instruct the shell to print commands and their arguments as they are executed.

NAME

nsr_snappolicy − NetWorker resource type ‘NSR Snapshot Policy’

SYNOPSIS

type: NSR Snapshot Policy

NAME

nsr_stage − NetWorker resource type ‘‘NSR stage’’

SYNOPSIS

type: NSR stage

DESCRIPTION

Each staging policy used by a NetWorker server is described by a single resource of type NSR stage. See

nsr_resource(5) for information on NetWorker resources. To edit the NSR stage resources run:

nsradmin -c "type:NSR stage"

NAME

nsr_storage_node − description of the storage node feature

SYNOPSIS

The storage node feature provides central server control of distributed devices for saving and recovering

client data.

NAME

nsrsup - NetWorker command to gather system information

SYNOPSIS

nsr_support [ −ab:cdef:g:hi:jl:m:no:prst:uvwxz ]

nsrsup [ −ab:cdef:g:hi:jl:m:no:prst:uvwxz ]

DESCRIPTION

nsr_support gathers up information about a system to be used by Technical Support or Engineering for

analysis. Although there are a lot of flags, in most cases the default should suffice. The output is gathered

into /nsr/tmp/n_supp.pid.

a, --all Turn on all flags.

-A Turn off all flags.

-b cores,daemons

--dbg-cores

--dbg-daemons

Run debugger on core files and/or daemons. Default is −−dbg−cores. −−all turns on

−−dbg−cores −−dbg−daemons.

-B Turn off running debugger on cores and daemons.

-c, --clients

Examine clients. On by default.

-C Do not examine clients.

-d, --dmesg

dmesg(1m) info printed. On by default.

-D Do not run dmesg(1m)

-e, --env-path

Append the PATH from the environment to the default in script. The default is

/sbin:/usr/sbin:/bin:/usr/bin:/etc

If it exists, /usr/xpg4/bin is prepended. The following are appended, if they exist.

/usr/ucb

/usr/bsd

/usr/sadm/bin

/usr/ccs/bin

/usr/etc

/etc/LGTOuscsi

/usr/local/bin

/usr/libexec

/usr/libexec/sccs

/usr/sbin/nsr

/usr/bin/nsr

/usr/nsrsbin

/usr/nsrbin

/opt/SUNWspro/bin

/opt/networker/bin

/usr/opt/networker/bin

-f arg, --file-list=arg

Tail additional named files.

-F Do not tail additional files.

-g arg, --grep-list=arg

grep(1) logfiles specified with −l. Default is −−greplist=mbuf.

-G Turn off grepping of logfiles.

-h Print help on the single character flags and exit.

--help Print help on the long flags and exit.

--hw-conf

Attempt to gather some hardware and kernel configuration information. On by default.

--html-output, --html

Generate html output. Off by default. --all turns it on.

-i arg, --mminfo=arg

Run mminfo(1m) with the specified flags, do not use the − before arg. Default is

−−mminfo=mvV,avV.

-I Do not run mminfo(1m).

--ipcs-info

Run ipcs(1) -a. On by default.

-j, --jb-info

Display jukebox info, if available. On by default.

-J Do not display jukebox info.

-l nsr,nsrd,sysmess,nsrres,rapres,lines=nnn

--nsr-log

--daemon-log

--sysmess-log

--nsr-res

--rap-res

--log-lines=nnn

Display log files, the nsr res files and query RAP. Default is −−nsr−log −−daemon−log

−−sysmess−log −−nsr−res −−log−lines=3000. −−all turns on −−nsr−log −−daemon−log

−−sysmess−log −−nsr−res −−rap−res −−log−lines=all.

-L Do not display logfiles.

-m arg, --mail=arg

Set email address to arg. Output will be emailed to named person. The output is going to be

multiple files that are tar’red, compressed and then uuencoded. If output is in html mode, there

will be only one single file but the above still applies. To retrieve the files use:

uudecode -p < file_name | uncompress -c | tar xf -

You can replace the uncompress(1) command with gzip -dc.

-M Do not email output. On by default.

-n, --netstat

Run netstat(1m). On by default.

-N Do not run netstat(1m).

-o arg, --output-file=arg

Set output file name to arg.

-O Do not set output file name. On by default.

-p, --check-path

Check for presence of NetWorker executables. Runs cksum(1) and what(1) on binaries. On by

default.

-P Do not check for presence of NetWorker binaries.

--path=arg

Add arg to the PATH. See −−env−path as well.

-r, --rpcinfo

Run rpcinfo(1m) -b 390109 2 to find NetWorker servers. On by default.

-R Do not run rpcinfo(1m).

-s, --ps Run ps(1). On by default.

-S Do not run ps(1).

--savegrp

Run savegrp(1m) -p on every group

--show-pkgs

Attempt to show the packages installed. On by default.

--subject=arg

Set the email’s Subject: field.

-t arg, --trace-list=arg, --trace-time=nnn

Do a truss(1)/par(1)/strace(1) on specified processes. The default is

−−trace−list=’nsr rap save asm’ −−trace−time=20. These are grepped for, they do not need to

represent actual process names.

-T Do not trace processes.

--temp-dir=arg

Set temp directory for temporary output files.

-u, --user-info

Interactively obtain user info, incident #, etc. On by default.

-U Do not try to obtain user info interactively.

-v, --vmstat

Run vmstat(1m)/sar(8). On by default.

-V Do not run vmstat(1m)/sar(8).

--verbose

Set verbose output. Prints the values of the internal configuration parameters. Also prints some

info on the progress of the script.

-w, --swap-info

Get swap info. On by default.

-W Do not get swap info.

-x, --indexes

Print index data. On by default.

-X Do not print index data.

-z, --compress

Compress output using compress(1). Emails are always compressed.

-Z Do not compress(1) output. On by default.

REQUIREMENTS

nsr_support requires a temporary directory to store the data it is gathering. This directory is by default

/nsr/tmp or if that does not exist, it is /tmp.

NAME

nsr_usergroup − NetWorker resource type ‘‘NSR usergroup’’

SYNOPSIS

type: NSR usergroup

DESCRIPTION

Each NSR user group is described by a single resource of type NSR usergroup (see nsr_resource(5)). To

edit the NSR usergroup resources for a NetWorker server, type:

nsradmin -c "type:NSR usergroup"

NAME

nsradmin − NetWorker administrative program

SYNOPSIS

nsradmin [ −c ] [ −i file ] [ −s server ] [ −p prognum ] [ −v version ] [ query ]

nsradmin [ −c ] [ −i file ] [ −d resdir . . . ] [ −t typefile ] [ query ]

nsradmin [ −c ] [ −i file ] [ −f resfile . . . ] [ −t typefile ] [ query ]

DESCRIPTION

The nsradmin command is a command-line based administrative program for the NetWorker system. Normally

nsradmin monitors and modifies NetWorker resources over the network. Commands are entered on

standard input, and output is produced on standard output.

If nsradmin is started without a query it uses a default query that selects all resources involved in Net-

Worker products.

OPTIONS

−c Uses the termcap(5) and curses(3) packages to implement a full-screen display mode, just like

the visual command described below. (UNIX Only)

−d resdir

Uses the NetWorker resource database resdir instead of opening a network connection. The

database resdir must be in directory format. This should be used sparingly, and only when the

NetWorker server is not running. Multiple −d and resdir arguments can be used to start nsradmin

with access to more than one database at a time.

−f resfile

Similar to the −d resdir option except that it opens an existing resource file, rather than a resource

directory. Some configuration databases are stored in file format, others in directory format.

−i file Takes input commands from file instead of from standard input. In this mode, the interactive

prompt will not be printed.

−s server

Opens a connection to the named NetWorker server instead of allowing administration of all

servers. Useful to limit the number of resources if there are many servers, or to administer when

the RAP location service is not working.

−p program

Use the given RPC program number or name instead of the default program number of 390103 -

which refers to nsrd. Other suitable program arguments include:

NetWorker Remote Execution Daemon:

390113 or nsrexecd

Host Agent Daemon:

390427 or hagentd

−t typefile

Uses the alternate file typefile to define RAP types.

−v version

Binds to the NetWorker RAP service with the given version number. The default is 2. This option

is generally used only for debugging.

query If a query is specified (in the form of an attribute list), the edit operation is performed on the

results of the query. See COMMANDS for more information on how the edit command works.

savegrp

Note: The "savegrp" command is executed on a NetWorker server.

savegrp ARTLAB

Starts backups for every client in the "ARTLAB" group and uses the schedule defined for each client or the "ARTLAB"

group. If the group schedule exists it takes precedence.

savegrp -c monet ARTLAB

Starts a backup for the client "monet", and uses the schedule defined for "monet" or the schedule for the "ARTLAB" group. If the group schedule exists it takes precedence.

savegrp -l full -c monet ARTLAB

Starts an explicit full backup for the client "monet" regardless of the defined schedule for the client or the "ARTLAB" group.

save

Note: The "save" command is executed on a NetWorker client.

NAME

save − sav e files to long term storage with NetWorker

savepnpc − save files to long term storage with NetWorker and performs pre and post processing commands

on a NetWorker client.

SYNOPSIS

command [ −BEiKLnquSVvx ] [ −s server ] [ −c client-name ] [ −N name ] [ −e expiration ] [ −f dirfile ] [

−o save_operations ] [ −b pool ] [ −F file ] [ −I input_file ] [ −g group ] [ −l level ] [ −t date ] [ −m masquerade

] [ −w browse_time ] [ −y retention_time ] [ −W width ] [ path . . . ]

where command is either save or savepnpc.

savepnpc consists of the same command options as save but requires the -g group to run.

DESCRIPTION

save saves files, including directories or entire filesystems, to the NetWorker server

save /export/home/jeffd

Starts a backup of the "/export/home/jeffd" directory to the default NetWorker server.

Without any additional specifications, it cause a volume from the "default" pool to be used.

save -s bserver -p FULL -l full /export/home/jeffd

Starts an explicit full backup of the "/export/home/jeffd" directory to the backup server "bserver" and causes a volume

from the "FULL" pool be used. The "-s" option is only relevant if there are multiple backup servers available to this client.

Safefs

NAME

savefs − save filesystem to a NetWorker server

SYNOPSIS

savefs [ options ] filesystem

savefs −p [ options ] [ filesystem ... ] [ −M filesystem ... ]

options: [ −BEFnpqRv ] [ −s server ] [ −N name ] [ −g group ] [ −c client ] [ −l level | −C schedule ] [ −e

expiration ] [ −w browse ] [ −y retention ] [ −f filename ] [ −o save_operations ] [ −W width ] [ −t

date ]

DESCRIPTION

The savefs command saves a filesystem (using save(1m)) to a NetWorker server. Mount points are not

crossed, and symbolic links are not followed. NOTE: running savefs directly is not recommended; use

savegrp(1m) instead.

Savegrp

NAME

savegrp − start a group of NetWorker clients saving their filesystems

SYNOPSIS

savegrp [ options ] [ −R | −G ] [ groupname ]

options: [ −EIOFXmnpv ] [ −l level | −C schedule ] [ −N parallelism ] [ −e expiration ] [ −w browse ] [ −y

retention ] [ −t date ] [ −r retries ] [ −P printer ] [ −W width ] [ −b backup snapshot ] [ −c client [

−c client ... ] ]

DESCRIPTION

The savegrp command runs a group of NetWorker clients through the process of saving their filesystems

(using save(1m)).

recover

Note: The "recover" command is executed on a NetWorker client.

NAME

recover − browse and recover NetWorker files

SYNOPSIS

recover [-f] [-n] [-q] [-u] [-i {nNyYrR}] [-d destination] [-c client] [-x index-namespace] [-t date] [ -s

server] [ dir]

recover [-f] [-n] [-u] [-q] [-i {nNyYrR}] [-I input file] [-d destination] [-c client] [-x index-namespace] [-t

date] [ -s server] -a path. . .

recover [-f] [-n] [-u] [-q] [-i {nNyYrR}] [-d destination] -s server -S ssid[/cloneid] [-S ssid[/cloneid]]. . . [

path]. . .

recover [-f] [-q] -i {NYR} -R recover-target [-c client] [-d destination] [-x index-namespace] [-t date] [ -s

server] [ dir ]

recover [-f] [-n] [-q] [-i {nNyYrR}] [-t date] [-s server] [-N system save set]

DESCRIPTION

recover browses the saved file index and recovers selected files from the NetWorker system. The file index

is created in the backup index namespace when files are saved with save(1m). If files are saved into an

index-storing archive pool using nsrarchive(1m), the file index is created in the archive index namespace.

recover -s bserver

Enter the "recover" interactive interface to the backup server named "bserver".

recover -s bserver /export/home/jeffd/projects/OTS

Recover all the files in the "/export/home/jeffd/projects/OTS” directory from the backup server named "bserver". NetWorker, will automatically use the appropriate combination of full and incremental backup volumes to restore the directory.

recover -s bserver -S 14527786

Recover the saveset indicated by the SSID "14527786" from the backup server named "bserver". An SSID identifies a

chronologically and source specific backup. SSIDs can be determined using the "mminfo" command.

Relem

NAME

relem − read element status

SYNOPSIS

relem [ -a b.t.l ] [ -fvtb ] [ -m {0|1|2} ] [ -r eladdr.nel ] [ -l ]

DESCRIPTION

The relem program will send a READ ELEMENT STATUS command to all changers, or (with the -a

option) to the named device.

SIMPLE OPTIONS

−a b.t.l Selects a specific ordinal SCSI address, where b is the logical SCSI bus, t is the SCSI target, and l

is the SCSI logical unit number (LUN) on that target. See libscsi(1m).

−f generates full output (somewhat verbose).

−v generates very verbose output.

−t causes volume tags, if present, to be printed.

−b causes the returned element status data to be dumped as hexadecimal codes rather than interpreted.

−l Performs a complete LUN search for all SCSI adapters in the system when performing Autodetection.

This argument is accepted on all systems, but does not have any effect on HP-UX systems.

Due to the method used to scan for available devices on HP-UX systems, all accessible devices are

shown, and the −l option has no additional effect. On all other systems, checking starts at LUN 0

for SCSI devices. The first empty LUN found will end the search for a given target ID. With the

−l option, LUNS on all target IDs for all SCSI busses in the system are checked for jukeboxes.

This can take a very long time and should only be used when necessary. For example, a Fibre

Channel adapter can support 126 target IDs, each of which may have 80 or more LUNs. Checking

all LUNs on this single adapter may take over 10 minutes.

METHOD OPTIONS

-m 0 all element status data is fetched in one call

-m 1 element status data is fetched per element type (e.g., all drive elements are read at once, then all

slot elements, etc.)

-m 2 element data is fetched per element (which is the default method)

The SCSI specification allows each of the previous methods of fetching element data.

Note: some changers have defects with respect to fetching element data. For example, one changer may be

accurate when reporting all elements of a particular type (using method −m 1), but return only zeros if

asked for all elements at once (using method −m 2).

RANGE OPTIONS

−r eladdr.nel is used to read a range of addresses, where eladdr is the starting decimal address (in the

particular changer’s numbering scheme) of the element to start from, and nel is the number of

mmrecov

NAME

mmrecov − recover a NetWorker media index

SYNOPSIS

mmrecov [ −q | −v ]

DESCRIPTION

The mmrecov command is used in recovering from the loss of a NetWorker server’s critical files. mmrecov

restores the media index and the server’s resource files.

ASM APPLICATION SECIFIC VOLUMES

STOP NSR CLIENT P162

Note: The mmrecov command is performed on a NetWorker server.

mmrecov /dev/rmt/0cbn

Initiate the recovery of a NetWorker server's online index and media index from the volume loaded in /dev/rmt/0cbn.

The mmrecov utility will prompt for information regarding the SSID and record number of the appropriate bootstrap

image on the volume. This information must be known BEFORE initiating this process,

The SSID and record number can be determined by either of the "mminfo" or "scanner" commands described above. Of course, if the server is in a damaged state, the "mminfo" command won't work and the "scanner" method must be used. The "mminfo" method is only useful if it is employed before damage occurs and the information is recorded offline.

nsrmm

Note: The "nsrmm" command is performed on a NetWorker server.

SYNOPSIS

nsrmm

[ −C ] [ −v | −q ] [ −s server ] [ −f device ]

nsrmm

−m [ −v | −q ] [ −s server ] [ −f device ] [ −r ] [ volume ]

nsrmm

−l [ −v | −q ] [ −s server ] [ −f device ] [ −myB ] [ −e forever ] [ −c capacity ] [ −o mode ] [ −b pool

] [ −R | volume ]

nsrmm

{ −u | −j } [ −v | −q ] [ −s server ] [ −y ] [ −f device | volume.. ]

nsrmm −p [ −v | −q ] [ −s server ] [ −f device ]

nsrmm

{ −d | −o mode } [ −v | −q ] [ −s server ] [ −Py ] [ −S ssid[/cloneid] | −V volid | volume ... ]

nsrmm

−S ssid [ −w browse-time ] [ −e retention-time ]

Displaying the current volumes:

The −C option displays the configured devices and the mounted volumes. This is the default

option.

nsrmm −C

nsrmm -m -f /dev/rmt/0cbn FULL.20020103

Mounts the volume named "FULL.20020103" on the specified tand-alone tape drive

nsrmm -m -l -f /dev/rmt/0cbn -b FULL FULL.20020109

Writes a NetWorker label "FULL.20020109" on the tape in the specified stand-alone tape drive, adds the volume to

the "FULL" pool, and mounts it. This also adds the volume name to the media manager database.

nsrmm -u -f /dev/rmt/0

Unmount the volume in the specified device. This is a logical action - the volume remains in the device.

nsrmm -j -f /dev/rmt/0

Eject the volume from the specified device. This is a physical action.

nsrmm -o recyclable INCR.20011210

Set the volume "INCR.20011210" to recyclable mode.

nsrmm -d ENGR.OFFSITE.001

Delete the volume "ENGR.OFFSITE.001" from the media manager database.

Labelling new tapes

To introduce a new tape, named mars.001, to the NetWorker system, load the tape in an empty

drive, then use the command:

nsrmm −l mars.001

The tape is labeled with mars.001 and an entry is made in the appropriate NetWorker indexes

The mminfo(1m) command may be used to inspect the volume database and display information

about the volumes: mminfo −m

Mounting a tape

To mount a NetWorker volume, use the −m option. Note that the volume must have been labeled

previously and loaded in the drive:

nsrmm −m

When mounting, a volume name can also be specified:

nsrmm −m mars.001

Labeling and mounting a tape:

A volume may be labeled and mounted with a single nsrmm command by combining the −m and

−l options. The following example labels a volume as mars.003 and mounts it on device

/dev/nrst0:

nsrmm −m −l −f /dev/nrst0 mars.003

Unmounting or ejecting a volume:

When a volume needs to be unmounted, use either the −u or −j option, depending on whether or

not the device can physically eject a volume.

nsrmm −u

When more than one volume is mounted, you can specify either the volume name or device to

select the desired volume. The following example ejects the volume named mars.003.

nsrmm −j mars.003

Deleting a volume:

To remove references to a volume and the user files saved on it from the NetWorker indexes, use

the −d option This option does not modify the physical volume, and should only be used when

the physical volume is destroyed. By deleting a volume, you free up space in the NetWorker file

index and the NetWorker media index, but not much more than if you had purged it.

nsrmm −d mars.003

The scanner(1m) command can be used to rebuild the database entries.

It is also possible to preserve the media database entries of a volume while purging the file index by specifying the −P option when deleting. The following example purges all of the file index entries for volume mars.001:

nsrmm −d −P mars.001

nsrmmd

NAME

nsrmmd − NetWorker media multiplexor daemon

SYNOPSIS

nsrmmd [−v] [−s server] [−r system] number

nsrmmdbasm

NAME

nsrmmdbasm − NetWorker module for saving and recovering media databases

SYNOPSIS

nsrmmdbasm [ standard-asm-arguments ]

DESCRIPTION

The nsrmmdbasm is a standard, external ASM (Application Specific Module) that assists in the saving and

recovering of the NetWorker media multiplexor’s database files.

nsrmmdbd

NAME

nsrmmdbd − NetWorker media (volume) management database daemon

SYNOPSIS

Nsrmmdbd

Nsrmon

NAME

nsrmon − command to remotely control NetWorker commands and daemons

SYNOPSIS

Nsrmon

nsrndmp_clone

NAME

nsrndmp_clone − use NetWorker and Network Data Management Protocol(NDMP) to perform save set

cloning

SYNOPSIS

nsrndmp_clone

[ −v ] [ −s server ] [ −b pool ] { −f file | volname... }

nsrndmp_clone

[ −v ] [ −s server ] [ −b pool ] −S { −f file | ssid[/cloneid]... }

nsrndmp_clone

[ −v ] [ −s server ] [ −b pool ] −V { −f file | volid... }

The nsrndmp_clone program makes new copies of existing save sets

EXAMPLES

Copy all save sets that begin on the volume mars.001 to a volume in the Offsite Clone pool:

nsrndmp_clone −b ’Offsite Clone’ mars.001

Copy all complete save sets created during the previous weekend (recall that nsr_getdate(3) dates without

time-of-day match midnight at the beginning of that day). Only complete save sets can be copied by

nsrndmp_clone(1m):

nsrndmp_clone -S ‘mminfo −r ssid \

-q ’!incomplete,savetime>last saturday,savetime<last monday’‘

Copy a specific clone of a specific save set:

nsrndmp_clone -S 1538800517/770700786

nsmdmp_recover

NAME

nsrndmp_recover − use NetWorker and Network Data Management Protocol (NDMP) to recover data

SYNOPSIS

nsrndmp_recover [ −c client ] [ −s server ] [ −R recover-target ] { -r raw device -S ssid[/cloneid] -m

mount point [ -v { on|off } ] [ paths [ paths... ] ] | -F }

nsmdmp_save

NAME

nsrndmp_save − use NetWorker and Network Data Management Protocol (NDMP) to save data

SYNOPSIS

nsrndmp_save −T backup-type −c client-name [ −LL ] [ −M ] [ −P Proxy-host ] [ −I Index-host ] [ −g

group ] [ −l level ] [ −b pool ] [ −m masquerade ] [ −s server ] [ −t date ] [ −e expiration ] [ −w

browse_time ] [ −y retention_time ] [ −W width ] path

nsrpmig

NAME

nsrpmig − premigrate files for long-term storage with NetWorker HSM

SYNOPSIS

nsrpmig [ −BEiLnpqvx ] [ −LL ] [ −s server ] [ −N name ] [ −f dirfile ] [ −b pool ] [ −g group ] [ −m masquerade

] [ −W width ] [ −I input file ] path

nsrports

NAME

nsrports − port configuration tool

SYNOPSIS

nsrports [ −s server ] [ −S | −C ] [ range ... ]

nsrretrieve

NAME

nsrretrieve − retrieve NetWorker archive sav e sets

SYNOPSIS

nsrretrieve [ −fnqu ] [ −i {nNyYrR} ] [ −d destination ] [ −s server ] { [ −S ssid[/cloneid] ]. . . [ −A

annotation ]. . . } [ path . . . ]

DESCRIPTION

nsrretrieve is used to restore archive sav e sets from a NetWorker server. No browsing is available via nsrretrieve.

Nsrscc

NAME

nsrssc − NetWorker save set consolidation program

SYNOPSIS

nsrssc −c client −N saveset [ −p pool ] [ -r ] [ −vq ]

DESCRIPTION

nsrssc consolidates the most recent level 1 (partial) save set and its corresponding full-level sav e set into a

new full-level sav e set. This consolidation process effectively achieves the same outcome as a full-level

backup at the time partial backup was done.

Nsrstage

NAME

nsrstage − NetWorker save set staging command

SYNOPSIS

nsrstage

[ −v ] [ −d ] [ −s server ] [ −b pool ] −m −S { −f file | ssid[/cloneid]... }

nsrstage

[ −v ] [ −s server ] −C −V volume

DESCRIPTION

The nsrstage program is used to migrate existing save sets on a manual basis. Migration is the process of

moving one or more save sets between volumes. The process begins with a clone of the specific save sets

to the new volume specified, followed by the deletion of cloned save set entries from the media database

(see the -S description). Finally, the possible removal of the save sets from the original source volumes.

EXAMPLES

Migrate save sets 1234 and 4568 to a volume in the Offsite Clone pool:

nsrstage −b ’Offsite Clone’ -m -S 1234 4567

Migrate clone instance 12345678 of save set 1234 to a volume in the Default Clone pool:

nsrstage −m −S 1234/12345678

Migrate all save sets created since last Saturday to a volume in the Default Clone pool:

nsrstage −m −S ‘mminfo −r ssid \

-q ’savetime>last saturday’‘

Recover space from volume jupiter.013:

nsrstage −C −V jupiter.013

nsrtrap

NAME

nsrtrap − snmp notification scheme for NetWorker messages

SYNOPSIS

nsrtrap [ −c community ] [ −t trap-type ] [ −s specific-type ] [ −v ] network_management_station

DESCRIPTION

nsrtrap is a mechanism to send NetWorker notifications using the Simple Network Management Protocol

(SNMP) trap mechanism. A NetWorker administrator could create a custom NetWorker notification

scheme based on nsrtrap, by configuring the NetWorker events and priorities.

A NetWorker administrator could create notification schemes to receive messages on different network

management consoles by configuring the events and priorities and specifying the desired network management

station as the location to receive the trap messages.

To create a new SNMP notification, follow the steps below:

1. Open the Notifications window from the Customize menu.

2. Choose the Details option under the View menu.

3. Click on the Create button.

4. Enter the name of the new notification in the Name field.

5. In the Action field, enter the command nsrtrap along with the

network management station name to which the networker SNMP notification should be sent. For

example:

/usr/sbin/nsrtrap -c networker SNMPhost

where SNMPhost is the hostname of the SNMP network management station.

6. Set the events and priorities desired.

7. Click on the Apply button.

OPTIONS

−c community The SNMP community string. This option allows you to specify the SNMP community

that is authorized to receive traps from the NetWorker server. SNMP communities are

configured on the SNMP server. This option defaults to "public".

−s specific-type This option is a generic setting that can be used to identify the type of trap the Net-

Worker server is sending. This option can be set to any integer value and may be used in

conjunction with different SNMP notifications to distinguish different traps coming from

the NetWorker server. For example, you can create multiple SNMP notifications: one for

critical messages, another for warnings, and another for other events or priorities. You

can then use the -s option to differentiate the various notifications so that the SNMP

management software can determine which type of trap is being sent.

−t trap-type One of the SNMP trap types[0-6]. The default is 6, the "enterprise-specific" trap type.

−v Sets the Output mode to verbose. In verbose mode, nsrtrap echoes the community, trap

type, specific trap type, and the hostname or IP address to the command line.

Nsrwatch

NAME

nsrwatch − command for character-based display of NetWorker status

SYNOPSIS

nsrwatch [ −s server ] [ −p polltime ]

nsrwizreg

NAME

nsrwizreg − Command to register NetWorker Configuration Wizard plugins or clients.

SYNOPSIS

nsrwizreg −a | -r −f nsrwizcon.res | nsrwizclnt.res −t plugin_type [ −c client_name ] [ −n plugin_name ]

[ −p library_path ] [ −v library_version ]

nsrjb

Note: The nsrjb command is performed on a NetWorker server with a jukebox attached.

nsrjb

A plain "nsrjb" command shows the volumes present in the jukebox slots and in the jukebox drives.

nsrjb -d -P1 -S26

Deposit a tape cartridge from access port slot 1 (-P1) to jukebox slot 26 (-S26).

nsrjb -w -S236 -P5

Withdraw a tape cartridge from jukebox slot 236 to access port slot 5.

nsrjb -l -f /dev/rmt/0cbn B00341

Load volume B00341 into jukebox device /dev/rmt/0cbn.

nsrjb -l -f /dev/rmt/6cbn -S 26

Load a tape cartridge from jukebox slot 26 into jukebox device /dev/rmt/6cbn.

nsrjb -u -f /dev/rmt/6cbn

Unload the tape cartridge in jukebox device /dev/rmt/6cbn back to the jukebox slot it came from.

nsrjb -L -f /dev/rmt/2cbn -S 177 -b FULL

Load the tape cartridge in jukebox slot 177 into jukebox device /dev/rmt/2cbn and write a label on it indicating

that it is in the FULL pool. This example assumes that the jukebox has a barcode reader, that the tape cartridge

has a barcode attached, and NetWorker is configured to automatically use barcodes for logical labels. This also

updates the media index database.

nsrjb -HE

Unload all jukebox drives and reset them.

nsrjb -IE -S307 -f /dev/rmt/4cbn

Inventory the contents of slot 307 using jukebox device /dev/rmt/4cbn.

Microsoft Windows 2000 [Version 5.00.2195]

C:\Documents and Settings\user5>nsrjb

Jukebox Overland:

slot volume pool barcode volume id recyclable

1: PYR292 Full Clone PYR292 6083011 manually

2: PYR296 Full Clone PYR296 4284273312 manually

3: PYR307 Full Clone PYR307 4267496258 manually

4: PC37182 Full PC37182 5739057 no

5: PC36282 Full PC36282 4283929282 no

6: PC37102 Full PC37102 4267152186 no

7: PC37072 Full PC37072 4250375075 no

8: 000014 Full 000014 4233597948 no

9: PC37212 Full PC37212 4216820877 no

10: PYR338 Full Clone PYR338 4250719253 manually

11: PYR353 Full Clone PYR353 4233942169 manually

12:

13:

14: 000031 Differential 000031 2837784730 no

15: NKH133S3 Differential NKH133S3 2888115757 yes

16: NKH150S3 Differential NKH150S3 1498630233 no

17: PD46452 Differential PD46452 2871338670 no

18: PD46462 Differential PD46462 2354227477 no

19: PD47132 Differential PD47132 2854561666 no

20: PYR325 Differential PYR325 2489049919 no

21: PXV562 Differential PXV562 2991156680 no

22: 000054 Differential 000054 525596979 no

23: PD46882 Full Clone PD46882 4217165113 manually

24: PC36882 Full Clone PC36882 4200387991 manually

25: PD46372 Full Clone PD46372 4183610895 manually

26:

27: PXV574 Full Clone PXV574 4082948638 manually

28: PC36232 Full Clone PC36232 4166833890 manually

29: PC36592 Full Clone PC36592 4150056798 manually

30: PD47072 Full PD47072 2992156268 no

31: PD47202 Full PD47202 3106217579 yes

32: PD46932 Full PD46932 2925075860 no

33: 000035 Full 000035 2988778164 yes

34: PD46392 Full PD46392 2975388253 no

35: PD46732 Full PD46732 2941843531 no

36: PC36292 Full Clone PC36292 4133279762 manually

37:

38:

39:

40: PC36602 Full Clone PC36602 4116502735 manually

41: PC36832 Full Clone PC36832 4099725631 manually

42: PXV563 Full Clone PXV563 4066171557 manually

43: 000075 Full 000075 4200043789 no

44: PXV613 Full PXV613 4183266746 no

45: 000079 Full 000079 4166489667 no

46: PYR283 Full PYR283 4149712577 no

47: PXV549 Full PXV549 4132935470 no

48: PD46962 Full PD46962 4116158396 no

49: PXV540 Full Clone PXV540 4049394598 manually

50: Cleaning Tape (20 uses left) CLN033 -

*not registered in the NetWorker media data base

drive 1 (\\.\Tape0) slot :

drive 2 (\\.\Tape1) slot :

drive 3 (\\.\Tape2) slot :

drive 4 (\\.\Tape3) slot :

C:\Documents and Settings\user5>

nsrjb

nsrjb -I

nsrwatch

mmlocate

mminfo -m -t 'overlan'

mminfo -m -r 'volume, pool, stat, volfalgs, location, %used, written'

mminfo -a "PYR387" -t 'last week'

mminfo -av PYR387

nsrck

Note: The nsrck command is performed on a NetWorker server.

nsrck -c monet

Perform a consistency check and repair of the indexes for client "monet"

nsrck -F -c monet

Perform a consistency check and repair of the indexes for client "monet" and force all phases to be performed. The

-F option also forces compression on the client indexes.

NAME

nsrck − NetWorker index consistency check, repair, and recovery program

SYNOPSIS

nsrck [ −qMv ] | [ −R [ −Y ] ] [ −L check-level [ −t date ] | −X [ −x percent ] | −C | −F | −m | −n | −c ] [ −T

tempdir ] [ clientname . . . ]

DESCRIPTION

nsrck is used to check the consistency of the NetWorker online index of clients’ save records. Normally,

nsrck is started automatically and synchronously by the nsrindexd(1m) program when nsrindexd starts.

scanner

NAME

scanner − NetWorker media verifier and index rebuilder

SYNOPSIS

scanner [ options ] −B −S ssid [ −im ] device

scanner [ options ] −i [ -S ssid ] [ -c client ] [ -N name ] device

scanner [ options ] −m [ -S ssid ] device

scanner [ options ] [ −S ssid ] [ −c client ] [ −N name ] device [ command ]

options: [ −npqv ] [ −f file ] [ −r record ] [ −s server ] [ −t type ] [ −b pool ]

command: −x command [ arg ... ]

DESCRIPTION

The scanner command reads NetWorker media, such as backup tapes or disks, to confirm the contents of a

volume, to extract a save set from a volume, or to rebuild the NetWorker online indexes.

Note: The scanner command is performed on a NetWorker server.

scanner -i -S 3359806141 \\.\Tape2 where 33.. is the SSID of save set

scanner -i /dev/rmt/0cbn

Scan the volume in device /dev/rmt/0cbn and rebuild media and online indexes from the data found on the tape.

scanner -B /dev/rmt/0cbn

Scan the volume in device /dev/rmt/0cbn and identify bootstrap images on it. See "mmrecov"

C:\Program Files\nsr\bin>scanner -i '000030'

scanner: '000030': No such file or directory

C:\Program Files\nsr\bin>scanner -i \\.\Tape1

scanner: scanning sdlt600 tape 000030 on \\.\Tape1

scanner: sdlt600 tape 000030 already exists in the media index

scanner: ssid 4081409222: scan complete

scanner: ssid 4081409222: 19 MB, 15 file(s)

scanner: ssid 4031077590: scan complete

scanner: ssid 4031077590: 867 KB, 8 file(s)

scanner: ssid 3880082700: scan complete

scanner: ssid 3880082700: 32 MB, 11 file(s)

scanner: ssid 4064632011: scan complete

scanner: ssid 4064632011: 251 MB, 2060 file(s)

scanner: ssid 3930414340: scan complete

scanner: ssid 3930414340: 607 MB, 2951 file(s)

scanner: ssid 3779419474: scan complete

scanner: ssid 3779419474: 1019 MB, 1582 file(s)

scanner: ssid 4014300379: scan complete

scanner: ssid 4014300379: 8306 MB, 19679 file(s)

scanner: ssid 3812973884: scan complete

scanner: ssid 3812973884: 14 GB, 46555 file(s)

scanner: fn 209 rn 5176 read error unknown error 1104 (0x450)

scanner: ssid 3796196687: NOT complete

scanner: ssid 3796196687: 212 GB, 233721 file(s)

scanner: ssid 3527761434: NOT complete

scanner: ssid 3527761434: 196 GB, 999398 file(s)

scanner: done with sdlt600 tape 000030

scanner: the following save sets continue on NKH111S3:

client name save set save time level size files ssid S

bormsfs01.em K:\ 8/12/11 19:04 f 217737903044 233721 379619668

7 S

bormsfs01.em M:\ 8/12/11 19:08 f 201015385900 999398 352776143

4 S

scanner: when next volume is ready, enter device name (or `q' to quit) [\\.\Tape

1]?

nsrclone

Note: The "nsrclone" command is executed on a NetWorker server.

Source and destination do not have to be the same kind of device or the same size volumes. NetWorker will use as many of the destination volumes as necessary to complete the cloning.

nsrclone -b FULLCLONE 14527786

Clone the data in the saveset identified by SSID "14527786" onto a volume in the "FULLCLONE" pool.

nsrclone -b FULLCLONE B00341

Clone the savesets from volume B00341 onto a volume in the "FULLCLONE" pool.

Storage queries

mminfo Contents and mode of the storage volumes and/or the identification numbers and status of the stored save sets.

mmlocate User-defined location of storage volumes.

nsrinfo Contents of the client file index.

nsrmm Status of the storage devices known to the NetWorker software

SYNOPSIS

mminfo [ −avV ] [ −o order ] [ −s server ] [ −x exportspec ] [ report ] [ query ] [ volname... ]

< report >: [ −m | −p | −B | −S | −X | −r reportspec ]

< query >: [ −c client ] [ −N name ] [ −t time ] [ −q queryspec ]

XML Format

To generate a report in XML format with mminfo or nsrinfo, include the –x option, followed by m.

For example: mminfo -xm -s jupiter -c mars

Without any options, mminfo displays information about the save sets that completed properly since the

previous day’s midnight, and are still contained in an online file index (browsable save sets). The following

information is printed for each save set: the containing volume name, the client’s name, the creation date,

the size saved on that volume, the save set level, and the save set name.

mminfo

mminfo -xc, -s BORMSBACK01 -c BORMSMANUFACT01

mminfo -xc, -s BORMSBACK01 -c BORMSMANUFACT01 –t’one months ago’

mminfo -xc, -s BORMSBACK01 -c BORMSFS01 -t’four months ago’.

OPTIONS

−a Causes queries to apply to all complete, browsable save sets, not just those in the last 24 hours.

This option is implied by the −c, −N, −q, −m, and −o options, described below. When combined

with a media-only report (−m or a custom report showing only media information), −a applies to

all volumes, not just those with complete and browsable save sets.

−c client

Restricts the reported information to the media and/or save sets pertaining to the specified client

and its known aliases. This is similar to specifying a client name using the queryspec option

name. In both cases the names are matched using a case-insensitive string comparsion.

−m Displays a media report instead of the default save set report

−N name

Restricts the reported information to the media and/or save sets pertaining to the specified save set name.

−o order

Sorts the output in the specified order. Before displaying the save sets, they are sorted by various fields. Numeric fields are sorted least to greatest, other fields are sorted alphabetically. order may be any combination of the letters celmnotR, representing client, expiration date, length, media name, name of save set, offset on media (file and record number), time, and Rev erse, respectively. The default sorting order for save set reports is mocntl. The offset fields (file and record) are only considered when the −V option has been selected and for custom reports that show sav e set section (fragment) information. When applied to −m media-only reports, the length is the amount used on the volume, the time is the last time the media was accessed, and the other order flags are ignored.

−q queryspec

Adds the given query constraint to the list of constraints on the current query. Multiple −q options may be given. See the CUSTOM QUERIES AND REPORTS section below for the syntax of the queryspec.

−r reportspec

Appends the given report specification to the list of attributes to be displayed for the current query.

Multiple −r options may be given. See the CUSTOM QUERIES AND REPORTS section

below for the syntax of the reportspec.

−s server

Displays volume and save set information from the NetWorker system on server. See nsr(1m) for a description of server selection. The default is the current system.

−t time Restricts the reported information to the media and/or save sets pertaining to the save sets created

on or after time. See nsr_getdate(3) for a description of the recognized time formats. The default

is ‘yesterday’, except when using the following switches: -a, -B, -c, -N, -m, -o and -q. When

using those switches, there is no default value for time. If you wish to see only the backups since

yesterday, you will have to specify ‘-t yesterday’ explicitly.

−v Turns on the verbose display reports, described above.

−x exportspec

As an alternative to the default human-readable output format, exportspec provides for two styles

of program-readable output formats. The exportspec ‘m’ displays XML output, while exportspec

‘c<separator>’ displays values separated by any single character. For example, ‘mminfo −xc,’

will produce comma-separated values.

−B Runs the canned query to report bootstraps which have been generated in the past five weeks, as

described above. This option is used by savegrp(1m) when saving the server’s index and bootstrap.

−S Displays a long, multiline save set report, as described above.

−V Displays additional verbose report output, as described above.

−X Prepares a summary report, as described above.

Display all bootstraps generated in the previous five weeks, as reported by savegrp(1m):

mminfo −B

mminfo −N bootstrap −t ’5 weeks ago’ −ot

-r ’savetime(17),space,level(6),ssid’

-r ’mediafile(6),mediarec(1m),space(3),volume’

Display information about all of the volumes:

mminfo −m

mminfo −a −r ’state,volume,written,%used,read,space’

-r ’mounts(5),space(2),capacity’

Display media information from volumes mars.001 and mars.002:

mminfo −m mars.001 mars.002

mminfo −m -q ’volume=mars.001,volume=mars.002’

Display all save sets named /usr:

mminfo −N /usr

mminfo −q name=/usr

Display save sets named /usr, generated by client venus, in the past week:

mminfo −N /usr −c venus

mminfo −q ’name=/usr,client=venus’

Display save sets named /usr, generated by client venus, on volume mars.001:

mminfo −N /usr −c venus mars.001

mminfo −q ’name=/usr,client=venus,volume=mars.001’

Display a media report of all volumes written on in the past week:

mminfo −m -t ’last week’

mminfo −m -q ’savetime>=last week’

Display a media report of all non-full volumes, showing the percent-used, pool and location of each volume:

mminfo −a −r ’volume,%used,pool,location’ -q ’!full’

Display a media report similar to the −m report but showing the barcode instead of the volume label:

mminfo −a −r ’state,barcode,written,%used,read,space’

-r ’mounts(5),space(2),capacity’

Display a verbose list of the instances of all save sets with more than one copy, sorted by save time and

client name:

mminfo −otc −v −q ’copies>1’

Display all archive sav e sets with an annotation of "project data" for the past four months.

mminfo −q’annotation=project data’

-r"volume,client,savetime,sumsize,ssid,name,annotation"

-t’four months ago’

Display all snapshot save sets for the client cyborg.

mminfo −q’client=cyborg, snap’

-r"volume,client,savetime,sumsize,ssid,name,annotation"

-t’four months ago’

NOTE: This option is available with Legato’s PowerSnap Module only

Display all snapshot save sets with their snapshot handle, for the client cyborg. The snapshot handle is

stored in the attribute ´∗snapid´.

mminfo −a −S −q’client=cyborg, snap’

-t’four months ago’

NOTE: This option is available with Legato’s PowerSnap Module only

mminfo –m

mmlocate

mmpool

Infos from Tapes Catalog

mminfo -a -v 000001 or AZT518S = volume

Note: The "mminfo" command is typically performed on a NetWorker server.

mminfo -m -q "client=monet,savetime>=last week"

Display a media report of all volumes used for backups of client "monet" in the past week.

mminfo -a -r "volume,%used,pool"

Display a report of all volumes showing the volume name, % of space used on the volume, and the pool of the volume

mminfo -q "client=monet" -r "ssid,name,totalsize,savetime,volume"

Display a report of all savesets from client monet, showing

the SSID, saveset name (file system or directory), total

size of the saveset, the savetime of the saveset, and the

volume it was written to.

mminfo -B

Run a defined query to report bootstrap savesets which have been generated in the last five weeks.

mminfo -av -r "volume,%used,written,location,pool,volretent"

PYR340 full 401 GB Buch04_2OG_Year08_No_Exp_Date Full expired

PYR341 full 408 GB Buch04_Archiv_July11_Exp12 Full Clone expired

PYR342 full 358 GB Buch4a_2OG_Juni10_Exp11 Full expired

PYR343 full 384 GB Buch04_Archiv_Jahr_2006 Full Clone expired

PYR344 full 555 GB Buch04_Archiv_Jahr_2006 Full Clone expired

PYR345 full 442 GB Buch04_Archiv_Jahr_2006 Full Clone expired

PYR346 48% 142 GB Full Clone manual

PYR347 full 426 GB Buch4a_2OG_Mai11_Exp12 Full expired

PYR348 full 313 GB Buch4a_2OG_November10_Exp11 Full expired

PYR349 full 501 GB Buch04_2OG_Year08_No_Exp_Date Full expired

PYR350 full 416 GB Buch4a_2OG_KW45_11_ExpKW50_11 Full 21.12.2011

PYR351 full 332 GB Full 27.12.2011

PYR352 full 387 GB Full manual

PYR353 full 320 GB Buch04_Archiv_Aug11_Exp12 Full Clone manual

PYR355 full 481 GB Buch04_Archiv_Sept11_ExpSept12 Full expired

PYR356 full 416 GB Full Clone manual

PYR359 full 347 GB Buch4a_2OG_KW13_11_ExpKW18_11 Full expired

mminfo -s bormsback01 -q"client=bormsfs02,level=full,name="I:\\"" -r"client,name,sumsize,savetime,level" -t "last week"

mminfo -s bormsback01 -t "last week"

mmlocate

NAME

mmlocate − NetWorker media location reporting command

SYNOPSIS

mmlocate [ −s server ] [ −l

{ −n volname | −i volid | location }] [ −L ] [ −d location ]

[ −c { −n volname | −i volid }] [ −u { −n volname| −i volid| location }]

DESCRIPTION

The mmlocate command is used to access and manage the volume location information contained in the

media database. The information contained in a volume’s location field is meant to give the user an idea of

where the volume can physically be found.

List all volumes stored in the location ’Media Vault’

mmlocate ’Media Vault’

Microsoft Windows 2000 [Version 5.00.2195]

C:\Documents and Settings\user5>mmlocate Overland

Volume Location

PYR322 Overland

PC36372 Overland

PYR275 Overland

000095 Overland

PD47042 Overland

PYR332 Overland

000044 Overland

NKH122S3 Overland

000066 Overland

NKH123S3 Overland

PC36412 Overland

PD47032 Overland

000048 Overland

000030 Overland

PYR298 Overland

PYQ122 Overland

000080 Overland

PC36902 Overland

PYR308 Overland

PXV589 Overland

PYR334 Overland

PD46802 Overland

PXV532 Overland

PYR325 Overland

000054 Overland

000045 Overland

000038 Overland

mmpool

SYNOPSIS

mmpool [ −s server ] [ volume... ]

[ −d pool ] [ −l pool ] [ −L ]

C:\Documents and Settings\user5>mmpool -l full

DESCRIPTION

The mmpool command is used to access pool information stored in the NetWorker server’s media database.

This command can also be used to delete all the volumes in a particular pool. If you specify one or more

volume names with the mmpool command, the report shows the pool that each named volume belongs to.

By default, all volumes and their pools are displayed.

You cannot change the pool to which a volume belongs without relabeling the volume, which destroys all

data stored on the volume. Pools are configured through a NetWorker administration tool, such as nwadmin(

1m) or nsradmin(1m). These tools are used to create and modify unique pool (see nsr_pool(5))

resources.

OPTIONS

−d pool Deletes all volumes for the given pool. The user will be prompted for deletion of each volume.

−l pool Lists all volumes and the pools to which they belong. If a pool is specified, mmpool only lists the

volumes belonging to that pool.

−L Lists the names of all pool resources configured on the server.

−s server

Specifies the NetWorker server to act upon. See nsr(1m) for a description of server selection

mmpool –l full

nsrinfo

SYNOPSIS

nsrinfo [ −vV ] [ −s server | −L ] [ −n namespace ] [ −N filename ] [ −t time ] [ −X application ] [ −x

exportspec ] client

nsrib

NAME

nsrib − NetWorker index browser daemon

nsriba − NetWorker index browser agent daemon

SYNOPSIS

nsrib [ −s server ] [ −t timeout ] [ −v ] [ −M ] [ −i # ] [ −C # ] [ −D # ] [ −R # ] [ −T rdir ] [ dir ]

nsriba [ −s server ] [ −c client ] [ −p path ] [ −v ] [ −t browse_date ] [ −I index_type ] [ −N session_name ]

[ −i # ] [ −C # ] [ −D # ] [ −R # ] [ −T rdir ] [ dir ]

DESCRIPTION

The nsrib (index browser) and nsriba (index browser agent) daemons provide a convenient NFS interface

in which to view NetWorker indexes.

OPTIONS

Common nsrib and nsriba options:

−s server Indicates the NetWorker server to use.

−i # Specifies "in place" mode if the corresponding file in the system is a symlink whose target

string has the filename at the end.

0 - nev er do "in place" recovers

1 - do "in place" recovers only for exact matches with names of "file@date"

2 - do "in place" recovers on any matching symlink target

Default value is 1.

−v Runs in verbose mode. This should only be used for debugging purposes.

−C # Sets an upper limit on the number of concurrent file recovers. A value of 0 will disable all

recovers (independent of the −R value). Default value is 2.

−D # Specifies the debug level for messages. Using a number from 1 - 3 to get various (reasonable)

levels of output. When running in a debugging mode, nsrib will not automatically run

itself in the background. Default value is 0.

−R # Specifies recover mode on read.

0 - nev er recover the file on NFS read.

1 - recover the file on NFS read if "online".

2 - always attempt a recovery of a file on NFS read.

Default value is 2.

−T rdir Temporary directory to use to cache recovered files. Default value is

"/usr/tmp/nsrib/Rtmp.client".

The −i, −s, −v, −C, −D, −R, and −T options to nsrib are passed through to each nsriba program started.

The following options apply only to nsrib:

−t timeout Indicates the time in minutes to attempt umounts of nsriba browsing directories. Default is

30 minutes.

−M Indicates that nsrib is being monitored by another process (such as nsrexecd(1m)), and

should not run in the background.

The following options apply only to nsriba:

−c client Indicates the NetWorker client index name to browse.

−p path Indicates the NetWorker index path to browse.

−t browse_date

Indicates a nsr_getdate(3) string giving the "browse as of" time. Default value is now.

−I index_type Indicats the type of index that is being browsed. The default is a backup index.

−N session_name

Indicates the name to use to generate the NetWorker session name. Default value is the

mount directory dir.

Nsrim

NAME

nsrim − NetWorker index management program

SYNOPSIS

nsrim [ −c client ] [ −N saveset ] [ −V volume ]

[ −x percent ] [ −lnqvMX ]

DESCRIPTION

The nsrim program is used to manage the NetWorker online file and media indexes.

OPTIONS

−c client

Only process the online file index for the specified client. Normally, all client indexes are processed.

This option may be repeated to process multiple clients.

−l Removes the oldest full save and all save sets dependant on it from the online index. Browse and

retention policies are ignored. The save set header information will print the number of browsable

full cycles currently in the online index. Archive and migration save sets are ignored. With this

option, manual save sets are treated as normal incremental save sets. This option also sets the utilization

threshold to 30 percent.

−M Master mode (not advised for manual operation). Advises nsrim that it is being run by nsrd(1m)

or another NetWorker daemon and that it should log messages with timestamps, and perform any

other behavior expected by nsrd.

−N save set

Process only save sets named; all others are skipped. This option can be repeated to process multiple

save sets.

−n Do nothing. Instead, emulate the actions of this command without the index cross-check. Note

that trailer statistics reflect current (and not emulated) results.

−q Run quietly. This option will not generate header, trailer or save set messages.

−V volume

Specifies the name of the volume to be processed. This option can be repeated to process multiple

volumes. −c, −N and −l options are ignored when this option is specified.

−v Produce a more detailed report. This may produce a large amount of output. When both −v and

−q are issued, they cancel each other.

−X Check the consistency of the data structures of the save set with the data structures of the volume.

This is only required after a NetWorker crash. This option also sets the utilization threshold to 30

percent.

−x percent

Sets the utilization threshold. If, after removing entries, the utilization of an online file index is

less than the specified amount, the index is compressed automatically by passing this percentage to

nsrindexd when requesting a cross-check. The default value is 50 (percent). Note that specifying

−X or −l changes the default to 30 (percent).

Nsrindexasm

NAME

nsrindexasm − NetWorker module for recovering indexes

SYNOPSIS

nsrindexasm [standard-asm-arguments]

DESCRIPTION

The nsrindexasm is a standard, external ASM (Application Specific Module). It assists in the recovery of

NetWorker on-line save record index files that were saved with NetWorker versions earlier than version 6.

nsrindexd

NAME

nsrindexd − NetWorker file index daemon

SYNOPSIS

nsrindexd

DESCRIPTION

The nsrindexd daemon is started by the server nsrd(1m) daemon. It should not be started manually.

If you believe an index may be corrupt, you can manually run a higher level check on the index, for example:

nsrck -L 6

Running nsrck -L 7 will not overwrite existing files in the client file index. So, if online client file index

data already exists for a saveset for a particular save time, it must be removed before nsrck -L 7 can be

used to restore it from the backup media.

Since nsrindexd and nsrck are run at the same time, both programs use an advisory file-locking mechanism

on the file db.SCAVENGE to synchronize their access to an index.

FILES

/nsr/index/clientname/db This file is where the client’s index records are stored and accessed.

/nsr/index/clientname/db.SCAVENGE

When this file exists and nsrindexd is not running, the nsrck program must be

run before nsrindexd is restarted.

nsrinfo

NAME

nsrinfo − NetWorker file index reporting command

SYNOPSIS

nsrinfo [ −vV ] [ −s server | −L ] [ −n namespace ] [ −N filename ] [ −t time ] [ −X application ] [ −x

exportspec ] client

DESCRIPTION

The nsrinfo command generates reports about the contents of a client file index.

For example, to generate a report of all files backed up in the most recent backup of the /usr file system for

the client mars, use the following sequence of commands (assuming the % character is the shell prompt):

% mminfo −r nsavetime −v −N /usr −c pegasus −ot | tail −1

809753754

% nsrinfo −t 809753754 mars

Note: The time used in the query is obtained by running the mminfo(1m) command with a custom report to

print the save time for the most recent save set for /usr. The time printed is passed to nsrinfo along with the

name of the client (mars).

OPTIONS

−v Verbose mode. In addition to the filename, it prints the type of the file, the internal file index identifier

(if any), the size (if a UNIX file), and the savetime. This option may be combined with the

−V option.

−V Alternate verbose mode. In addition to the filename, it prints the offset within the save set containing

the file, the size within the save set, the application name space (see the −n option for a list of

values), and the save time. This option may be combined with the −v option.

−s server

Indicates the name of the NetWorker system to be queried. By default, the server on the local system

is queried.

−L Opens a file index directly without using the server. This option is used for debugging, or to query

the file index while NetWorker is not running.

−n namespace

Indicates the file index name space to query. By default the backup name space is used. The other

recognized values are: migrated, archive (reserved for future use), nsr (for internal use), informix

(for INFORMIX data), sybase (for Sybase data), msexch (for Exchange data), mssql (for SQL

Server data), notes (for Lotus Notes data), db2 (for DB/2 data), oracle (for Oracle data), and all.

The name space field is case sensitive.

−N filename

Indicates an exact filename to look for in the file index. Only index entries matching this name

exactly print. Note that for some clients, such as NetWare, the name stored in the file index is

often not made up of printable ASCII characters, giving this option limited use.

−t time Restricts the query to a single, exact save time. The time can be in any of the NetWorker nsr_getdate(

3) formats. Every save set created by NetWorker has a unique save time; these times can be

determined by using the mminfo(1m) command.

−X application

Restricts the query to list information for only a specific X/Open Backup Services (XBSA) application.

Valid application types are All, Informix, and None. The application type is not case sensitive.

See the APPLICATION TYPES section of this man page for more information.

−x exportspec

As an alternative to the default human-readable output format, exportspec provides for two styles

of program-readable output formats. The exportspec ‘m’ displays XML output, while exportspec

‘c<separator>’ displays values separated by any single character. For example, ‘nsrinfo −xc,’ will

produce comma-separated values.

nsrls

NAME

nsrls − list statistics of NetWorker index files

SYNOPSIS

nsrls [ { clientname . . . | −m } ]

C:\Documents and Settings\user5>nsrls -m

Database id 0: C:\Program Files\nsr\mm\mmvolume6

Fid | Size | Count | Name

------------------------------------------

0 | 344 KB | 529 | vol

1 | 11 MB | 6977 | ss

2 | 16 KB | 47 | clients

3 | 24 KB | 529 | vol_i0

4 | 24 KB | 528 | vol_i1

5 | 24 KB | 528 | vol_i2

6 | 16 KB | 528 | vol_i3

7 | 24 KB | 528 | vol_i4

8 | 192 KB | 6977 | ss_i0

9 | 160 KB | 6977 | ss_i1

10 | 16 KB | 0 | ss_i2

11 | 88 KB | 6977 | ss_i3

12 | 16 KB | 47 | clients_i0

13 | 16 KB | 47 | clients_i1

Pmode

NAME

pmode − print mode sense data

SYNOPSIS

pmode [ -f filename ]

DESCRIPTION

The pmode program will parse the data output by the msense(1m) program and print in technological

English. (C-style variables with hexadecimal numbers)

OPTIONS

−f filename Specifies input; otherwise standard input is assumed.

EXAMPLE

Sample output might look like:

viper# msense -a 0.0.0 -p 0x03 | pmode

Mode Header: mdl=35 mtype=0x0 dparm=0x10 bdlen=8

Block Desc[0]: dens=0x0 nblks=3933040 blklen=512

Fixed Page, code 0x03 (Format Device):

tracks_per_zone: 0xf

alt_sectors_per_zone: 0x22

alt_tracks_per_zone: 0x0

alt_tracks_per_vol: 0x0

sectors_per_track: 0x5e

data_bytes_per_sect: 0x200

interleave: 0x1

track_skew_factor: 0x8

cylinder_skew_factor: 0x11

SSEC: 0x0

HSEC: 0x1

RMB: 0x0

SURF: 0x0

SEE ALSO

msense(1m)

msense

MSENSE ( 1m )

NAME

msense − get mode sense data

SYNOPSIS

msense -a b.t.l [ -p pagecode ]

DESCRIPTION

The msense program will send a MODE SENSE command to the named device.

OPTIONS

The required -a argument must be used to select a specific ordinal SCSI address (see libscsi (1m)).

The optional -p pagecode argument may be used to select a specific mode page, else all pages are fetched

(code 0x3f). This argument must be specified in hexadecimal notation.

BUGS

The output is not readable. It is intended as input to pmode (1m).

SEE ALSO

libscsi(1m), pmode(1m)

NetWorker

hadump

EXAMPLES

Report all information submitted by all clients to Host Agent server on jupiter :

hadump −s jupiter

Report all information submitted by client trout.legato.com to Host Agent server on jupiter :

hadump −s jupiter −c trout.legato.com

Report information of type system information submitted by client trout.legato.com to Host Agent server

on jupiter :

hadump −s jupiter −c trout.legato.com −t ’system information’

Report the OS type and IP address information submitted by clients trout.legato.com and rx7 to Host

Agent server on jupiter :

hadump −s jupiter −c trout.legato.com −c rx7 −a ’IP address’ −a ’OS type’

List host-names for all clients with information submitted to Host Agent server on jupiter :

hadump −C −s jupiter

List types of information submitted by clients trout.legato.com and rx7 to Host Agent server on jupiter :

hadump −T −s jupiter −c trout.legato.com −c rx7

C:\Program Files\nsr\bin>hadump -s bormsback01.emea.borms.com

hadump: RPC error: Program not registered

hafs

Collect file system information and dump the result to the standard output, do not update the local RAP

data base:

hafs −n

Collect file system information and update the local RAP data base:

Hafs

Graphical Interfaces

Nwadmin

NAME

nwadmin, networker − graphical administration interface to NetWorker

SYNOPSIS

nwadmin [ −s server ]

networker [ −s server ]

nwarchive

NAME

nwarchive − NetWorker graphical archive interface

SYNOPSIS

nwarchive [ −s server ]

nwbackup

NAME

nwbackup − NetWorker graphical backup interface

SYNOPSIS

nwbackup [ −s server ] [ path ]

nwrecover

NAME

nwrecover − NetWorker graphical recover interface

SYNOPSIS

nwrecover [ −s server ] [ −c client ] [ −x index namespace ] [ −T browse time ] [ path ]

NAME

nwretrieve − NetWorker graphical retrieve interface

SYNOPSIS

nwretrieve [ −s server ]

pathownerignore

NAME

pathownerignore − ignore path-ownership rules during scheduled saves

SYNOPSIS

<nsr_bin>/pathownerignore

DESCRIPTION

In a clustered environment, the NetWorker software must distinguish between filesystems associated with

the physical client, and those that are managed by a resource group (a virtual client). These criteria are

referred to as the path-ownership rules.

Command Arguments

Time & Date formats

08/12/11 00:00:00 = 8 august 2011

4 months ago

yesterday

forever

undef

ASM arguments

Standard-ASM-Arguments.

ASM's may also have additional options.

A particular ASM's additional options must be capital letters.

Either -s (saving), -r (recovering) or -c (comparing) mode must be

specified and must precede any other options. When saving, at least one

path argument must be specified. Path may be either a directory or file

name.

The following options are valid for all modes:

-n Perform a dry run. When saving, walk the file system but don't

attempt to open files and produce the save stream. When recovering

or comparing, consume the input save stream and do basic sanity

checks, but do not actually create any directories or files when

recovering or do the work of comparing the actual file data.

-v Turn on verbose mode. The current ASM, its arguments, and the file

it is processing are displayed. When a filtering ASM operating in

filtering mode (that is, processing another ASM's save stream)

modifies the stream, its name, arguments and the current file are

displayed within square brackets.

When saving, the following options may also be used:

-b Produce a byte count. This option is like the -n option, but byte

count mode will estimate the amount of data that would be produced

instead of actually reading file data so it is faster but less

accurate than the -n option. Byte count mode produces three

numbers: the number of records, i.e., files and directories; the

number of bytes of header information; and the approximate number of

bytes of file data. Byte count mode does not produce a save stream

so its output cannot be used as input to another asm in recover

mode.

-o Produce an ``old style'' (see nsr_data(4)) save stream that can be

handled by older NetWorker servers.

-e Do not generate the final ``end of save stream'' boolean. This flag

should only be used when an ASM invokes an external ASM and as an

optimization chooses not to consume the generated save stream

itself.

-i Ignore all save directives from .nsr directive files found in the

directory tree.

-f proto

Specifies the location of a .nsr directive file to interpret before

processing any files, see nsr(4). Within the directive file

specified by proto, <<path>> directives must resolve to files within

the directory tree being processed, otherwise their subsequent

directives will be ignored.

-p ppath

This string is prepended to each file's name as it is output. This

argument is used internally when one ASM exec's another external

ASM. Ppath must be a properly formatted path which is either the

current working directory or a trailing component of the current

working directory.

-t date

The date (in nsr_getdate(3) format) after which files must have been

modified before they will be saved.

-x Cross filesystem boundaries. Normally, filesystem boundaries are

not crossed during walking. Symbolic links are never followed,

except in the case of rawasm.

When recovering, the following options may also be used:

-i {nNyYrR}

Specifies the initial default overwrite response. Only one letter

may be used. When the name of the file being recovered conflicts

with an existing file, the user is prompted for overwrite

permission. The default response, selected by just pressing Return,

is displayed within square brackets. Unless otherwise specified

with the -i option, `n' is the initial default overwrite response.

Each time a response other than the default is selected, the new

response becomes the default. When either N, R, or Y is specified,

no prompting is done (except when auto-renaming files that already

end with the rename suffix) and each subsequent conflict is resolved

as if the corresponding lower case letter had been selected.

The valid overwrite responses and their meanings are:

n Do not recover the current file.

N Do not recover any files with conflicting names.

y Overwrite the existing file with the recovered file.

Y Overwrite files with conflicting names.

r Rename the conflicting file. A dot, ".", and a suffix are

appended to the recovered file's name. If a conflict

still exists, the user will be prompted again.

R Automatically renames conflicting files by appending a

dot, ".", and a suffix. If a conflicting file name

already ends in a "." suffix, the user will be prompted to

avoid potential auto rename looping conditions.

-m src=dst

This option will map the file names that will be created. Any files

that start exactly with src will be mapped to have the path of dst

replacing the leading src component of the path name. This option

is useful if you wish to perform relocation of the recovered files

that were saved using absolute pathnames into an alternate directory

(e.g., -m /usr/etc=.).

-z suffix

Specifies the suffix to append when renaming conflicting files. The

default suffix is "R".

path Used to restrict the files being recovered. Only files with

prefixes matching path will be recovered. This checking is

performed before any potential name mapping is done with the -m

specification. When path is not specified, no checking is done.

CAVEATS

Raw partitions are often used to store active DBMS data. If your raw

partition contains data managed and updated by an active DBMS product,

rawasm alone will not give a consistent backup. The database must not be

updating the data in an uncontrolled fashion while rawasm saves or

recovers data on the partition. Either the partition must be offline,

the database manager shutdown, or the partition placed in an appropriate

state for backup. Legato has products to assist with online database

backup. Likewise, were one to use the rawasm to save a partition

containing a Unix filesystem, the filesystem must be unmounted or mounted

read-only to obtain a consistent backup.

Ideally, recovery of a raw partition should take place to a system

configured with the same disk environment and same size partitions as the

system which performed the backup. If the new partition is smaller than

the original partition, the recovery will not be complete successfully.

If the new partition is larger than the original partition, only the

amount of data originally saved will be recovered.

If the partition backed up includes the disk label - the label often

contains the disk geometry - recovering this partition to a new disk will

also recover the label, changing the new disks geometry to match the

original disk. Likewise, if a Unix filesystem partition is backed up

using rawasm, recovering the partition will reset all information on the

partition, including timestamps concerning mount times, if applicable.

Since rawasm does not discover the size of the partition it backs up

until the backup is completed, the estimated size reported on recovery is

not accurate.

EXAMPLES

Copying files

To copy all of the files in the current directory to target_dir,

use:

uasm -s . | (cd target_dir; uasm -rv)

This will preserve ownership, time, and the other Unix attributes.

Only the data in holey files will be copied, the holes will not be.

Copying a file tree to an archive directory

To copy the file tree under the directory here to archive and

overwrite any files with conflicting names, use:

cd here

uasm -s . | (cd archive; uasm -r -iY)

Note that we cd to here first and give the first uasm doing the save

a relative path so that the second uasm doing the recover will

recreate the file tree under archive.

Another way to get the same effect is to use the -m option on the

second uasm doing the recover to explicitly map the path names.

uasm -s here | uasm -r -iY -m here=archive

Pages

Monday, 10 February 2014

Legato Commands part 3

Command Arguments

Time & Date formats

ASM arguments

No comments:

Post a Comment