List of Legato Networker commands and tips. Copyright Avisit Solutions Limited. www.avisit.co.

nz Complete listing of legato Bullitins: http://web1.legato.com/lefaq/bulls/ Frequently asked questions http://www.backupcentral.com/networker-faq.html The Networker Journal http://www.drenpress.com/ Setup: Schedule, Directives, retention, Browse Policy Setup cron to check /usr/tmp savepnpc Check lck files in savepnpc groups (/nsr/res) Save files to long term storage with NetWorker and performs pre and post processing commands on a NetWorker client. savepnpc performs pre/post-processing commands if any exists in the /nsr/res/<grpname>.res file. inquire ldunld device. jb_config mminfo -m Database "name,level,ssid,pssid" BPK678 pssid series, zero for the daemon.log nsr_shutdown -a or -q nsrck -m nsrck -F |<client_name> networker nsrck -C <client_name> nsrck -c nsrinfo nsrls nsrim nsrim -l size of the indexes. nsrd nsrexecd savegrp -pvvv <group_name> not do anything) savegrp <group_name> nsrindexd first or only save set in a series. Most usefull log Shutsdown networker Checks media Fix client indexes. Clientname is optional Indexes can be corrupted when stopping Compress index Rebuilds Client Indexes NetWorker file index reporting command List statistics of NetWorker index files NetWorker index management program Remove the oldest save set to decrease the Server daemon. Coordinates server operations. Client/server communications daemon Run the probe step to backup a group (does Backup the specified group File-index database management When part of a save set series, the previous save set identifier in the Lists SCSI devices available. Sends and load or unload command to the tape Configure an autochanger Get Media information from the Networker Example : mminfo -av -c chocbar -r

nsrmmd nsrmmdbd nsrmm interface to manage the media

Media Management (tape drives) daemon Medai Database Management The nsrmm program provides a command line

and backup devices used by NetWorker servers and storage nodes. nsrjb Manipulate the jukeboxs nsrjb -I To read the new tapes that are in the jukebox volumes (Inventory) nsrjb -j DLT891 -O81 -Y -L -g -bDefault -f /dev/nrmt0h -S 1-1 To label tape in slot 1 nsrjb -j DLT891 -O84 -p -n -f /dev/nrmt0h -S 3-3 Verify volume in slot 3 nsrjb -j DLT891 -O85 -Y -L -g -bDefault -f /dev/nrmt0h -S 3-3 Label volume in slot 3 nsrjb -j DLT891 -O86 -p -n -f /dev/nrmt0h -S 4-4 Verify volume in slot 4 nsrjb -j DLT891 -O87 -Y -L -g -bDefault -f /dev/nrmt0h -S 4-4 Label tape in slot 4 nsrjb -L -S 5-19 To label the volumes in slots 5 through 19, use the -S option This is what the manual provides. nsrjb -u Unload volume from DLT nsrjb -o recyclable BPK687 Set volume BPK87 to recyclable. NOTE You will never be able to recover these files again. Not even with the scanner command. nsrmm -d <Volume> Delete a volume in the media database (when getting message duplicate name) nsrmmdbd Media Management db daemon nsrwatch Watch the progress of networker in a terminal mode. nsrls list statistics of NetWorker index files The nsrls program, when invoked without any options, prints the number of files in client file index, the number of kilobytes that the client file index currently requires, and the utilization of the client file index with respect to the number of kilobytes allocated to its UNIX file. nsrjb mmlocate nsradmin -s <servername> savegrp -pvvv <Group_name> several clients has to be backed up once a week. Deactivate the group in Legato. scanner media (such as backup tapes, The scanner program directly reads NetWorker Juke Box manipulation and information Show location of media Terminal mode for nwadmin Run Group Group_name. If this group has then you can also specify the client name. Run this command in cron if the group only

optical disks, or files) to confirm the contents of a volume, to extract a save set

from a volume, or to rebuild the NetWorker online indexes. You can only run this command as root. You must specify a device, which is usually one of the device names used by the NetWorker server. If the device is a tape drive, it must be a nonrewinding type. Any script in the backup command must begin with nsr or save Do not use remote user except with rman skips in directives Index management -------------------nsrls nsrck -F nsrim No more than 35 lines

List statistics of NetWorker index files Compress Indexes NetWorker index management program

Problem Solving. ---------------If the savegrp -pvvv Group_name does not come back with a list of filesystems then there could be TCP/IP problem. Use the following commands and files to identify the problem. 1) Is default route correct? Use netstat -rn 2) Is the DNS correct. You might have to use resolf.conf to use the /etc/host file first. This is done in svc.conf in Tru64 and /etc/nsswitch in Solaris. 3) Use nsrlookup 4) Use rcpinfo Reports ------something like mminfo -m -r 'volume, pool, state, volflags, location, %used, written'

will give you a E in state when the volume is recyclable(expired), an r in volflags when its read only. You can write querys using -q and just get tapes in the location of "libraryname" or use grep like i do. mminfo -m -t Will mminfo -m -t Will 'yesterday' give all the backups yesterday 'last week' give all the backups last week

-----------------savepnpc Client has savepnpc specified in the "Backup command:" field on server /nsr/res/TEST.res file on client contains:

type: savepnpc; precmd: /nsr/bin/precmd.sh; pstcmd: /nsr/bin/pstcmd.sh; timeout: "11:00pm"; When a savegroup starts the following happens (example using the group TEST): The server starts the group. The server sees the client has savepnpc specified as the backup command. The server contacts the client and checks for a /nsr/res/TEST.res file. (If there is not one, a dummy res file will be created.) The client executes the pre command/script specified in the file (precmd: /nsr/bin/precmd.sh;). It creates a tmp file indicating that savepnpc is running, /nsr/tmp/TEST.tmp It also executes a process that monitors the status of the saves waiting for completion and/or the timeout value specified in /nsr/res/TEST.res. (timeout: "11:00pm";) After the pre script successfully completes, the server then initiates the filesystem saves. During this time the client is constantly checking the server to see if the saves are completed. As soon as they have completed (or the timeout value has been reached), the client executes the post script specified in the /nsr/res/TEST.res file. (pstcmd: /nsr/bin/pstcmd.sh) It then removes the /nsr/tmp/TEST.tmp file. NOTES: The pre/post scripts need to have the necessary environment setup in them, as savepnpc does not pass any kind of environment to the scripts. The start/stop of the pre and post commands are recorded in /nsr/logs/savepnpc.log If the pre command fails (exit status non-zero), the saves for that client will abort and not be run. It will also not start the post command process, so the post script will never run and the /nsr/tmp/TEST.tmp file will be left. You will need to remove this by hand. If a savegroup session is manually aborted or stopped on the server, the /nsr/tmp/TEST.tmp file is left. (This is because the server allows you to restart it later.) Also, because an abort does not clear up the work list for the client,the client still thinks there are saves to be completed and the post script will not run. If a new savegroup session is started and there is an existing /nsr/tmp/TEST.tmp file, it will skip the pre/post commands; however it will run the filesystem save sessions.