Legato NetWorker ClientPakl and Storage Node Users Guide
Legato NetWorker ClientPakl and Storage Node Users Guide
Legato NetWorker ClientPakl and Storage Node Users Guide
Preface....................................................................................................................... 7
About This Guide............................................................................................................................. 7
Audience ................................................................................................................................... 7
Legato Product Manuals and Documentation ................................................................................. 7
How to Navigate Through This Guide ............................................................................................. 8
Information and Services ................................................................................................................. 8
Technical Support............................................................................................................................ 9
Customer Service ............................................................................................................................ 9
Customer Feedback ........................................................................................................................ 9
Conventions...................................................................................................................................10
MPE Versus MPE/iX POSIX Filepath Naming Conventions ...................................................10
iii
Contents
iv
Contents
Glossary .................................................................................................................. 61
Index ........................................................................................................................ 67
v
Preface
Audience
Users and system administrators who perform client-initiated backups, recovers, and
archives from an HP 3000 MPE NetWorker client will benefit from this guide. This
guide assumes that you are an experienced MPE/iX user.
7
How to Navigate Through This Guide
Company
Technical Binary & Product Training
Legato Service or Resource Bulletins Patches Information Programs
8
Preface
Technical Support
If you purchased technical support from HP, please refer to your HP Support Contract.
You must register Legato NetWorker for MPE/iX with Legato Systems, Inc. before you
can purchase Legato technical support. Please complete the registration form found on
the last page of this guide.
Legato also provides several sources to fulfill your technical support needs.
E-mail [email protected]
Customer Service
Contact Legato Customer Service if you have questions about licensing, registering, or
authorizing your Legato products. Customer Service also supplies instructions for
transferring licenses to a different server (rehosting) and provides status on product
orders.
E-mail [email protected]
Customer Feedback
The Legato NetWorker for MPE/iX team welcomes your comments and suggestions
about software features, the installation procedure, and documentation. Please send
any suggestions and comments to [email protected]. You will receive a notice
confirming receipt of your e-mail. Although we cannot respond personally to every
request, we consider all your comments and suggestions during product design.
9
Conventions
Conventions
This guide uses the following typographic conventions and symbols to make
information easier to access and understand.
• boldface, lowercase or UPPERCASE – Indicates references to NetWorker
programs or commands within paragraphs as in the following example:
You can start the NetWorker NSRSAVE program either from the MPE/iX
Command Interpreter (CI) or from the POSIX shell if you prefer.
• italic – Indicates directory pathnames, files, computer names, new terms defined
in the Glossary or within the chapter, and emphasizing words or ideas as in the
following example:
With the NetWorker ClientPak for MPE/iX, you can manually perform client-
initiated backups.
• fixed-width – Used for examples and information displayed on the screen as
in the following example:
NSRSAVE: /reports/ 389 KB 00:00:30 5 files.
• fixed-width, boldface lowercase or UPPERCASE – Used for commands
and text you type exactly as shown as the recover command or the RUN
NSRRECOV;INFO= command as in the following examples:
recover> recover
: RUN NSRRECOV;INFO="-s server -c client"
• fixed-width, boldface italic lowercase – Used for commands and text
you type for which you need to substitute a variable, as used for reports,
server, and client in the following examples:
recover> add reports
: RUN NSRRECOV;INFO="-s server -c client"
•
FILENAME.GROUP.ACCOUNT /ACCOUNT/GROUP/filename
(Must be uppercase.) (The filename is case-sensitive.)
10
Chapter 1: Introduction to NetWorker
Overview
Legato NetWorker for MPE/iX is tightly integrated with HP’s TurboSTORE software
to provide enterprise storage management capability. HP’s TurboSTORE/iX products
provide high-performance backup solutions.
NetWorker ClientPak for MPE/iX
If you have used NetWorker software on a UNIX or NT server, then you know that
NetWorker normally has a graphical user interface (GUI).
The NetWorker ClientPak for MPE/iX does not have a GUI. Instead, you must enter
commands from either an MPE/iX Command Interpreter (CI) shell or from a POSIX
shell.
MPE Client
From the MPE client, you can enter commands to perform client-initiated backups,
recovers, and archives of your data.
To configure your MPE client to be included in the automatic server-initiated backups,
use the nwadmin GUI on the NetWorker server for your HP 3000 MPE client.
11
About Legato NetWorker for MPE/iX
Archiving involves long-term storage of data on media called archive volumes. Archive
1 volumes are similar to backup volumes, but are stored for long periods of time and are
not automatically recycled. They are also not browsable if you want to recover them.
To conserve space, you can groom files from your system after archiving. Mission-
critical data remains safely preserved for as long as you need it.
The optional Legato NetWorker Archive Application provides the ability to take a
snapshot of finished project files, directories, or MPE volume sets residing on primary
media. To conserve media space, you can choose to have archived data automatically
removed from the media after NetWorker verifies that the snapshot is safely stored on
removable media.
Unlike backed-up data, the media used for storing archived data is never recycled.
Archived data is preserved for as long as you need it. Archiving data associated with
a finished project frees up space for current projects, while assuring future access to
mission-critical data.
To use the Archive Application, your system administrator simply enables the
software on the NetWorker server. No additional installation procedures are required.
12
Chapter 2: Backing Up Files
You can perform two types of backups with Legato NetWorker for MPE/iX: server-
initiated backups and client-initiated backups. This chapter describes how to perform
client-initiated backups and briefly discusses server-initiated backups of an MPE
client. However, for comprehensive information on how to configure your MPE client
to perform server-initiated backups, refer to the Legato NetWorker Administrator’s Guide,
UNIX Version that is distributed with the NetWorker server software.
Server-Initiated Backups
Once your system administrator installs NetWorker on your HP 3000 and configures a
NetWorker server to recognize your HP 3000 as a NetWorker client, then NetWorker
performs server-initiated backups of your HP 3000.
Ideally, the system administrator should configure your HP 3000 as two MPE clients
on the NetWorker server: one for performing server-initiated backups of specific files
and directories, and one for performing server-initiated backups of MPE volume sets.
Refer to “Configuring the MPE Client on the NetWorker Server” in the Legato NetWorker
Installation Guide, MPE/iX Version, Release 5.5 for more information on configuring a
NetWorker MPE client on a NetWorker server. The process for configuring an MPE client to
receive server-initiated backups of MPE files and directories is standard. Refer to the Legato
NetWorker Administrator’s Guide, UNIX Version for information on the default
configuration for a client on a NetWorker server.
For server-initiated backups, NetWorker creates index entries and a media database that
track the media location of each client file. NetWorker maintains two types of indexes on the
server: a file index and a media index. The file index stores information about the files backed
up by NetWorker. The media index stores information about NetWorker media and the save
sets stored on the media.
Backing up files is short-term insurance against data loss. The NetWorker server to
which your HP 3000 is a client automatically backs up your files according to a backup
schedule determined by your system administrator.
For an overview of how to perform manual backups of directories, files, or volume sets
on an as-needed basis from your HP 3000, see “Client-Initiated Backups” on page 14.
13
Client-Initiated Backups
NetWorker saves directories, files, or MPE volume sets in groups called save sets. The save
sets are saved to backup volumes on a NetWorker backup device. A NetWorker backup
volume is a unit of media used for backup, such as a magnetic tape, a disk, or an optical
disk. NetWorker stores and tracks your data on backup volumes on a regular basis.
MPE volumes are disks on an MPE client; MPE volume sets are sets of disks.
A NetWorker volume pool contains a collection of backup volumes to which specific
data has been backed up. Volume pools allow you to sort backup data to selected
2 volumes. For more information on managing media and backup devices, refer to the
Legato NetWorker Administrator’s Guide, UNIX Version.
Client-Initiated Backups
You can back up directories, files, groups of files, or MPE volume sets on an MPE client
from the MPE Command Interpreter (CI) or from the POSIX shell.
You enter the NSRSAVE command to start the NetWorker NSRSAVE program. The
NSRSAVE program is a client-side program that runs manual backups. Manual
backups are intended for quick backups of a few files or directories. They do not
generate bootstrap files or back up indexes, so they do not serve as replacements for
server-initiated backups.
For details on entering the NSRSAVE command to back up directories, files, groups of
files, or volume sets, see the following sections:
• “Backing Up a Directory” on page 17
• “Backing Up a File” on page 19
• “Backing Up a Group of Files” on page 19
• “Backing Up MPE Volume Sets” on page 20
Once you have backed up your data using either a server-initiated backup or a client-
initiated backup, you can recover any lost or damaged data by using the NetWorker
NSRRECOV program. See “Chapter 3: Recovering Files” on page 23 for information.
14
Chapter 2: Backing Up Files
Important: You should always have the TZ variable set when performing server-
initiated or client-initiated backups, or recovering files and directories with
2
NetWorker. For example, when you are recovering your files, you need to set the time
zone variable; otherwise the backup times in the recover browser could be Greenwich
Mean Time.
To set the time zone for client-initiated backups, add the following system variable
when you start a CI session:
: SETVAR TZ "EST5daylight"
Note that the value EST5daylight is only an example; it might not be appropriate for
your time zone.
For information about the value to use to set the TZ variable, display the timezone man
page from the POSIX prompt only:
$ man timezone
15
Setting System Variables for Client-Initiated Backups
16
Chapter 2: Backing Up Files
Backing Up a Directory
You can back up directories or files from the MPE Command Interpreter (CI) or from
the POSIX shell.
The NSRSAVE command to back up a directory includes the following parameters:
• -s, the parameter for the server
• The name of the server to which you are backing up your directory
• The pathname of the directory that you are backing up
17
Backing Up a Directory
Backing up your files can take a fair amount of time. NetWorker displays the following
message while the backup is in progress:
>> TURBO-STORE/RESTORE VERSION C.55.29 B5152AA <<
(C) 1986 HEWLETT-PACKARD CO.
STORE /projects/project1/reports;;ONLINE=START;TREE;SHOW;NW3K
WED, DEC 17, 1997, 4:49 PM
2 VOLUME RESTRICTIONS SECTORS CODE MEDIA FILENAME
DISC :C 32 HFSDIR 1
/projects/project1/reports/
DISC :C 0 1
/projects/project1/reports*
/rep1
DISC :C 0 1
/projects/project1/reports*
/rep2
DISC :C 0 1
/projects/project1/reports*
/rep3
DISC :C 0 1
/projects/project1/reports*
/rep4
DISC :C 0 1
/projects/project1/reports*
/rep5
ONLINE BACKUP UTILIZED DISC SPACE FOR LOG ON THE FOLLOWING
VOLSETS:
MPEXL_SYSTEM_VOLUME_SET : 0 KB
HFS DIRECTORIES STORED : 1
FILES STORED : 5
TOTAL MEDIA WRITTEN : 0
NSRSAVE: /projects/project1/reports 15 KB 00:00:04 9 files
The last four items in the message are TurboSTORE information items that are not
interpreted by NetWorker.
18
Chapter 2: Backing Up Files
Backing Up a File
Backing up files is very similar to backing up directories. You can back up files from
the CI or from the POSIX shell.
The NSRSAVE command to back up a file includes the following parameters:
• -s, the parameter for the server
• The name of the server to which you are backing up your directory
• The pathname of the file that you are backing up 2
Using the Command Interpreter
From the CI, enter the following command to back up a file:
: RUN NSRSAVE;INFO="-s server /file_pathname"
For example:
: RUN NSRSAVE;INFO="-s jupiter /projects/project1/reports/rep1"
19
Backing Up MPE Volume Sets
20
Chapter 2: Backing Up Files
ONLINE BACKUP UTILIZED DISK SPACE FOR LOG ON THE FOLLOWING VOLSETS
SRSAVE: /PUCK_VOLUME_SET 27 KB 00:00:03 11 files
MPEXL_SYSTEM_VOLUME_SET : 0 KB
PROJECTS: 0 KB
MPE DIRECTORIES STORED: 1
HFS DIRECTORIES STORED : 9
HFS DIRECTORIES NOT STORED : 1
FILES STORED : 1
TOTAL MEDIA WRITTEN : 0
21
Backing Up MPE Volume Sets
Note that in the sample display, the line entry "PROJECTS VOLUMESET MPE
DIRECTORY ACCOUNTING FILE" corresponds to the directory accounting
information file, which is identified in the NSRRECOV program as
/PROJECTS_VOLUME_SET_DAF. In the previous version of NetWorker, the file was
displayed as /PROJECTS_VOLUME_SET.
22
Chapter 3: Recovering Files
23
Setting System Variables for a Recovery Session
Important: You should always have the TZ variable set when performing server-
initiated or client-initiated backups, or recovering files and directories with
NetWorker. For example, when you are recovering your files, you need to set the time
zone variable; otherwise the recover browse time will be in Greenwich Mean Time.
To set the time zone for recovery sessions, add the following system variable when you
start a CI session:
: SETVAR TZ "EST5daylight"
Note that the value EST5daylight is only an example; it might not be appropriate for
your time zone.
You can also set the TZ variable from the POSIX shell:
$ export T=EST5daylight
24
Chapter 3: Recovering Files
For information about the value used to set the TZ variable, display the timezone man
page from the POSIX prompt only:
$ man timezone
25
The NSRRECOV Program
To relocate files from one group to another, enter the following system variable during
the current CI session:
: SETVAR NSR_MPE_RECOV_GROUP "<new group>"
You can also set this system variable from the POSIX shell:
$ export NSR_MPE_RECOV_GROUP="<new group>"
To relocate files from one account to another, enter the following system variable
during the current CI session:
: SETVAR NSR_MPE_RECOV_ACCOUNT "<new account>"
You can also set this system variable from the POSIX shell:
$ export NSR_MPE_RECOV_ACCOUNT="<new account>"
3
Recovering Files to Local Groups or Accounts
You can recover files to your logon group or account with the
NSR_MPE_RECOV_LOCAL_ON system variable. This system variable is mutually
exclusive; it overrides the NSR_MPE_RECOV_CREATOR,
NSR_MPE_RECOV_GROUP, and NSR_MPE_RECOV_ACCOUNT system variables.
This system variable overrides the relocate command in the NSRRECOV program.
The default for the NSR_MPE_RECOV_LOCAL_ON system variable is off.
To change the destination of recovered files, enter the following system variable during
the current CI session:
: SETVAR NSR_MPE_RECOV_LOCAL_ON ""
You can also set this system variable from the POSIX shell:
$ export NSR_MPE_RECOV_LOCAL_ON=""
26
Chapter 3: Recovering Files
• If you enter -iY, the i turns on parallelism and the Y overwrites any existing files.
• If you enter -iN, the i turns on the parallelism and the N instructs the
NSRRECOV program not to overwrite any existing files or directories.
• If you turn on parallelism, you can set a system variable to turn it off again. See
“Turning Off Parallel Backups” on page 25.
The NSRRECOV command includes the following parameters:
• -s, the server parameter
The name of the server from which you are recovering the files
• -c, the client parameter
The name of the client to which you are locating the recovered files
• -iY, turns overwrite prompt off; overwrites existing files, directories and turns
parallelism on
• -iN, turns overwrite prompt off; does not overwrite existing files, directories and 3
turns parallelism on
• -a, the automatic parameter for non-interactive recoveries
The file path of the file, directory, or MPE volume set that you want to recover
Entering the client parameter and client name are optional; for example, if you are
recovering files from the client where the files were originally backed up, then you do
not have to enter the client name.
Important: The naming convention for recovering MPE volume sets differs from the
naming convention for saving MPE volume sets. See “Naming Conventions for
Recovering MPE Volume Sets” on page 41.
Non-interactive Recovery
With non-interactive recoveries you do not browse the save sets or mark the files for
recovery. Enter the NSRRECOV command and the parameters for the file path of the
file, directory, or MPE volume set that you want to recover. Perform non-interactive
recoveries when you want to recover files, directories, or MPE volume sets quickly.
To perform a non-interactive recovery file rep1, enter the NSRRECOV command and
all the parameters from the CI, as in the following example:
: RUN NSRRECOV;INFO="-s jupiter -iN -a
/projects/project1/reports/rep1"
27
Browsing Save Sets that are Available for Recovery
Important: You must have write permissions for the save sets that you want to browse.
28
Chapter 3: Recovering Files
Command Description
add filename Add a filename to the recovery list
cd dir Change to a specified directory (dir)
changetime Change the browse time of the online index
delete filename Delete a filename from the recovery list
dest Verify the destination directory for recovered files
force Overwrite existing files 3
help or ‘?’ Display this list of NSRRECOV commands
list List the files in the recovery list
ls -f (or lf) filename List filenames with file type information
ls - l (or ll) filename List filenames using long format
ls filename List filenames
noforce Do not overwrite existing files
pwd Display the name of the current directory
quit Exit from the NSRRECOV program
recover Start the recovery process from the recover prompt
relocate dir Specify a new directory location for recovered files
verbose Toggle verbose or quiet mode for recovery status messages
versions filename Display the backup history of a filename
(filename can be either a file or a directory)
volumes filename List the volumes needed to recover marked files
(filename can be either a file or a directory)
Refer to the man pages for more information on NetWorker commands. See
“Displaying the Man Pages” on page 60.
29
Recovering a Directory
Recovering a Directory
Once you have started the NSRRECOV program, you can recover an entire directory.
This section assumes that you have started the NSRRECOV program and have
changed to the save set where the recovery directory resides.
To recover an entire directory, follow these steps:
1. Mark the directory that you want to recover by entering the NetWorker add
command and the name of the directory:
recover> add reports
The following message is displayed:
6 file(s) marked for recovery
3 2. (Optional) Verify the marked files in the recovery list as follows:
recover> list
/projects/project1/reports/ @ Fri Nov 21 19:00:00 1997
/projects/project1/reports/rep1 @ Fri Nov 21 19:00:00 1997
/projects/project1/reports/rep2 @ Fri Nov 21 19:00:00 1997
/projects/project1/reports/rep3 @ Fri Nov 21 19:00:006 1997
/projects/project1/reports/rep4 @ Fri Nov 21 19:00:00 1997
/projects/project1/reports/rep5 @ Fri Nov 21 19:00:00 1997
6 file(s) marked for recovery
3. Start the recovery process by entering the recover command at the NetWorker
recover prompt:
recover> recover
NetWorker displays the following message:
Recovering 6 files into their original locations
FILES RESTORED : 5
Volumes needed (all on-line):
jupiter.012 at /source/rmt/data
Requesting 6 file(s), this may take a while...
>> TURBO-STORE/RESTORE VERSION C.55.29 B5152AA
(C) 1986 HEWLETT-PACKARD CO.
RESTORE ; ;SHOW;NW3K;CREATE
WED, DEC 17, 1997, 4:58 PM
’CREATE’ OPTION DEFAULTING TO
’CREATE=ACCOUNT,GROUP,CREATOR,PATH’
BASED ON YOUR CAPABILITIES (S/R 502)
WARNING: YOUR DEFAULT FILESET BECOMES ’@.@.@’ SINCE YOU HAVE OP
OR SM CAPABILITY (S/R 1911)
30
Chapter 3: Recovering Files
/projects/project1/reports*
/rep1
/projects/project1/reports*
/rep2
DISC :C 0 1
/projects/project1/reports*
/rep3
DISC :C 0 1
/projects/project1/reports*
/rep4
3
DISC :C 0 1
/projects/project1/reports*
/rep5
DISC :C 0 HFSDIR 1
/projects/project1/reports*
//
Received 6 file(s) from NSR server ‘jupiter’
Recover completion time: Wed Dec 17 16:58:31 1997
recover>
Recovering a File
If more than one version of a backed-up file exists, NetWorker automatically recovers
the file with the most recent backup date. This section describes how to recover a file
or files with the most recent backup date.
This section assumes that you have started the NSRRECOV program.
To recover files with the most recent backup date, follow these steps:
1. Change to the save set where the file resides, for example:
recover> cd reports
2. (Optional) List the files in the current save set as follows:
recover> ls
The following message is displayed:
rep1 rep2 rep3 rep4 rep5
31
Recovering a File
/projects/project1/reports*
/rep1
Received 1 file(s) from NSR server ‘jupiter’
Recover completion time: Wed Dec 17 17:00:48 1997
32
Chapter 3: Recovering Files
This section assumes that you have started the NSRRECOV program, changed to the
save set where the saved files reside, and listed the files.
To recover a group of files, follow these steps:
1. Mark the files that you want to recover by entering the NetWorker add command,
then enter the characters that create a common pattern in the filename and
substitute an asterisk for the different characters in the filename, as in the following
example:
recover> add r*
The following message is displayed:
5 file(s) marked for recovery
2. Start the recovery process as follows:
recover> recover
NetWorker displays the following message:
Recovering 5 files into their original locations
Volumes needed (all on-line):
jupiter.012 at /source/rmt/data
Requesting 5 file(s), this may take a while...
>> TURBO-STORE/RESTORE VERSION C.55.29 B5152AA <<
(C) 1986 HEWLETT-PACKARD CO.
RESTORE ; ;SHOW;NW3K;CREATE
WED, DEC 17, 1997, 5:02 PM
’CREATE’ OPTION DEFAULTING TO
’CREATE=ACCOUNT,GROUP,CREATOR,PATH’
BASED ON YOUR CAPABILITIES (S/R 502)
WARNING: YOUR DEFAULT FILESET BECOMES ’@.@.@’ SINCE YOU HAVE OP
OR SM CAPABILITY (S/R 1911)
33
Viewing the Backup History
3 DISC
/projects/project1/reports*
:C 0 1
/rep4
DISC :C 0 1
/projects/project1/reports*
/rep5
Received 5 file(s) from NSR server ‘jupiter’
Recover completion time: Wed Dec 17 17:02:39 1997
34
Chapter 3: Recovering Files
Information Example
35
Recovering a File That Already Exists
36
Chapter 3: Recovering Files
37
Recovering a File That Already Exists
The second time that you recover an existing file in the same recovery session,
NetWorker automatically overwrites the existing file without displaying a
warning prompt. When the recovery is complete, NetWorker displays the
following message:
Recovering 1 file into its original location
Volumes needed (all on-line):
jupiter.012 at /source/rmt/data
Requesting 1 file(s), this may take a while...
/projects/project1/reports/rep2
/projects/project1/reports/rep2: file exists, overwriting
3 DISC :C 16 1
/projects/project1/reports/rep2
Received 1 file(s) from NSR server ‘jupiter’
• R – NetWorker recovers and renames the file with a .R extension and displays the
following message:
Recovering 1 file into its original location
renaming /projects/project1/reports/rep3 to
/projects/project1/reports/rep3.R
VOLUME RESTRICTIONS SECTORS CODE MEDIA FILENAME
DISC :C 16 1
/projects/project1/reports/rep*
3.R
Received 1 file(s) from NSR server ‘jupiter’
The second time that you recover an existing file in the same recovery session,
NetWorker automatically renames the recovered file without displaying a warning
prompt. When the recovery is complete, NetWorker displays the following
message:
/projects/project1/reports/rep4
/projects/project1/reports/rep4: file exists, renaming to
/projects/project1/reports/rep4.R
DISC :C 16 1
/projects/project1/reports/rep*
4.R
Received 1 file(s) from NSR server ‘jupiter’
38
Chapter 3: Recovering Files
39
Recovering and Relocating Files
40
Chapter 3: Recovering Files
Important: Performing a full restoration of a system volume save set is not advised
because you could overwrite crucial files.
The NSRRECOV program for recovering MPE volume sets includes the special
directory accounting information file that allows you to rebuild the accounts and
groups of the volume set.
For information on recovering an entire MPE volume set in case of a disaster, see
“Disaster Recovery: Restoring an Entire MPE Volume Set” on page 43.
Important: Purged MPE/iX accounts and groups will be restored with only the default
attributes, which includes permissions.
41
Recovering Volume Sets
Important: Do not append _VOLUME_SET to the end of an MPE system volume set.
When an HP system is installed, it automatically creates the MPE system volume,
MPEXL_SYSTEM_VOLUME_SET.
The name of the directory accounting information file for an MPE volume set is the
same as the name of the MPE volume set for previously saved data. The new name has
an extra tag, _DAF. Therefore, if you enter the name of or mark an MPE volume set
during the recovery process, you recover the directory accounting information file only.
You can recover an entire MPE volume set by using the save set-based recovery
method, which uses the save set recovery identification (ssid) for the MPE volume set.
3 When NetWorker saves an MPE volume set, it saves the file directory accounting
information in the file /PROJECTS_VOLUME_SET_DAF. Using the example above,
when you recover this specific file, it will contain only the file directory accounting
information. To recover all the files and directories on an MPE volume set, you use the
save set identification (ssid) for the volume set.
Important: You can only restore one directory accounting information file at a time.
42
Chapter 3: Recovering Files
To recover MPE volume sets with the most recent backup date, follow these steps:
1. Change to the save set where the MPE volume set resides, for example:
recover> cd /
2. (Optional) List the files in the current save set as follows:
recover> ls /PROJECTS_VOLUME_SET_DAF
NetWorker displays the following information:
PROJECTS_VOLUME_SET_DAF SYS PROJGRP1
3. Mark the directory accounting information file that you want to recover as follows:
recover> add PROJECTS_VOLUME_SET_DAF
The following message is displayed:
1 file(s) marked for recovery
3
To add other files to the recovery list, repeat the add command.
4. Start the recovery process as follows:
recover> recover
Important: Performing a full restoration of the system volume save set is not advised
because you could overwrite crucial files.
43
Recovering Volume Sets
5. Once you have recreated and mounted a non-system volume set, perform a save
set recovery.
To perform a save set-based recovery from the CI prompt, enter the NSRRECOV
command:
: RUN NSRRECOV;INFO="-s jupiter -S ssid_for_volume_set"
To perform a save set-based recovery from the POSIX shell, enter the following
command:
$ NSRRECOV -s jupiter -S ssid_for_volume_set
44
Chapter 4: Archiving and Retrieving Files
This chapter describes how to archive and retrieve files using the optional NetWorker
Archive Application.
Archiving Data
The backup and archive processes serve very different purposes. Backup is short-term
insurance against data loss. NetWorker keeps track of backups in the online file index
to enable you to recover lost or corrupted files quickly. This online file index requires
considerable disk space. Because archives are kept forever theoretically, NetWorker
does not track them in the online file index; NetWorker only tracks archives in the
online media index.
Archiving is the process by which NetWorker backs up data to an archive volume.
Archive volumes are similar to backup volumes, except they do not have an expiration
date, which means that NetWorker will keep track of them indefinitely. Archiving is a
long-term strategy for preserving data.
Once files are safely stored on archive volumes, the archived files can be removed from
the local disk, freeing up space on your system. If you ever need to restore archived
files to your system, you can do so at any time.
If you have system administrator permissions, you can also archive MPE volume sets.
Although you can groom volume sets, be warned that you cannot remove the accounts,
groups, or pseudo files.
The best way to remember what an archive contains is to create a meaningful
annotation. An annotation is a comment that you associate with your archive to help
you identify data should you want to retrieve it. Annotations are stored in the media
index to make searching for archives easier. Annotations are limited to 1024 characters.
You can archive directories or individual files. You can start the NSRARCH program
during an MPE/iX CI session or from the POSIX shell.
When you archive, you have the options of verifying the archive, cloning the archive,
and grooming directories once the archive is complete. Cloning and grooming are
discussed under separate sections (see “Cloning an Archive” on page 47 and
“Grooming Your Directories” on page 48).
45
Archiving Data
You can archive a directory and verify the archive in one step. NetWorker verifies the
archive by comparing the data on the archive volume with the data on the local disk,
byte for byte, attribute for attribute. If there are any discrepancies, NetWorker lets you
know.
The NSRARCH command for archiving and verifying the archive includes the
following parameters:
• -s, the parameter for the server.
The name of the server to which you are archiving the directory.
• (Optional) -b, the parameter for the volume pool.
(Optional) The name of the volume pool, which must be enclosed in quotes if the
name is more than one word. Archive is the name of the default volume pool.
• -V, the verify parameter.
• -T, the parameter for the annotation text.
The annotation text, which must be enclosed in quotes if the text is more than one
word. Annotation text must be alphanumeric; avoid using characters. Keep the
annotation text simple. When NetWorker searches for an annotation, the search is
case-sensitive.
46
Chapter 4: Archiving and Retrieving Files
Annotation:
-----------
Project1
Cloning an Archive
NetWorker clones an archive by making a duplicate copy of the archive. Usually
system administrators clone archives. Before making a clone of your archive, you
might want to check with your system administrator.
Two backup devices are required to make a clone: one for the original archive volume
and the other for the archive clone volume. Each backup device must have a valid,
writable archive volume mounted.
The NSRARCH command for cloning an archive includes the following parameters:
• -s, the parameter for the server.
The name of the server to which you are cloning the files.
• -b, the parameter for the volume pool.
(Optional) The name of the archive volume pool, which must be enclosed in
quotes if the name is more than one word. Archive is the name of the default
archive volume pool.
• -V, the verify parameter.
• - C, the clone parameter.
The name of the volume pool to which you are cloning, which must be enclosed
in quotes if the text is more than one word. Archive clone is the name of the default
clone volume pool.
• -T, the parameter for the annotation text.
The annotation text, which must be enclosed in quotes if the text is more than one
word. Annotation text must be alphanumeric.
• The pathname of the directory that you are cloning.
47
Grooming Your Directories
48
Chapter 4: Archiving and Retrieving Files
Groomed: Yes
Volume(s): projects.archive.001
Annotation:
project1
49
Retrieving Archived Files
50
Appendix A: Error Messages
NetWorker provides error messages to help you solve backup, recovery, and archive
problems that you might encounter. This section contains a list of error messages for
the NSRSAVE, NSRARCH, NSRRECOV, NSRRETRV, and SAVEFS programs for
the NetWorker ClientPak for MPE/iX.
Error Messages
The error messages, listed in Table 4, are listed in alphabetical order. The tables also
provides the cause of each error message and a solution.
Error Message
‘09/30/12:00’ not valid, time not changed
Cause
You asked NetWorker to change the browse time to a browse time that was earlier
than the save time for the file.
Solution
Enter the time using one of the following valid time formats:
• hh:mm:ss (24 hour clock) or hh:mm:ss am/pm
• mm/dd(/yy) or monthname dd (yy) (/yy is optional)
• Last Friday, next Friday, or third Friday
• + or -x seconds, minutes, hours, weeks, months, or years
• Now (the current date and time)
51
Appendix A: Error Messages
Error Message
‘12:20:14:00’ not valid, time not changed
Cause
The change time you entered while trying to recover was an invalid time format.
Solution
Enter the time using a valid time format.
Error Message:
Annotation must contain only alphanumeric characters on MPE/iX
systems.
Cause:
You entered one or more non-alphanumeric characters, such as ! # * ? & ~, in your -T
annotation text or in response to the annotation prompt.
A Solution:
Reenter your annotation text using only alphanumeric characters from a-z, A-Z, and
0-9.
52
Appendix A: Error Messages
Error Message:
Cannot build recover list - volume set violation
Cause:
You tried to recover a directory accounting information file for a volume set along
with a version of some other file or directory from another save set or save time.
NetWorker does not allow you to mix save times to ensure data integrity.
For a related issue see the next error message, Conflict: at most one dir
info file can be marked/recovered at a time.
Solution:
• For interactive recovery, use the ls -l (list), delete, and versions commands, and
unmark the files or directories so all remaining marked objects have the same save
time.
• Or better, recover the directory accounting information file by itself, for example:
"-S ssid /XXX_VOLUME_SET" or "-S ssid".
Error Message: A
Conflict: at most one dir info file can be marked/recovered at
a time
Cause:
You marked more than one directory accounting information file for volume sets for
recovery in a single recovery session.
Solution:
• For an interactive recovery, mark and recover the directory accounting
information file one at a time. See “Non-interactive Recovery of a Directory
Accounting Information File” page 42.
• For saveset-based recovery of part or all of a volume set, or only the directory
accounting information file itself, use exactly one -S ssid_for_volume set
option or argument at a time. See “Disaster Recovery: Restoring an Entire MPE
Volume Set” page 43.
53
Appendix A: Error Messages
Error Message:
filter_mpe_volsets failed
Cause:
NetWorker found a temporary memory problem.
Solution:
Try one of the following solutions:
• Retry the command.
• Reboot the host system.
Error Message:
/<invalid_mpe_volset_id>_VOLUME_SET: invalid NetWorker volume
set identifier or /<invalid_system_volume_set_id>
Cause:
You specified an invalid MPE/iX volume set name after the required leading slash
(/) and, in the case of nonsystem volume sets, before the required suffix tag
A (_VOLUME_SET).
Solution:
Insert the valid MPE/iX volume set name in the expected NetWorker format:
/MPEXL_SYSTEM_VOLUME_SET
or
/<valid_mpe_volset_id>_VOLUME_SET
for example, /PROD_VOLUME_SET for an MPE/ix volume set named "PROD".
Error Message:
mpevs_init failed
Cause:
NetWorker found a memory or volume set management problem.
Solution:
Try the following in descending order of preference:
• Retry the command.
• Remount the non-system volume sets, ensure they are usable, and reboot the host
system.
• If all volume sets seem to be usable using test MPE/iX commands and the
problem persists, contact Legato Technical Support.
54
Appendix A: Error Messages
Error Message
Nothing marked for backup
Cause
You started a backup or archive without marking files.
Solution
Start the backup or archive again; mark at least one file.
Error Message
NSRSAVE: invalid time specification: ‘20d1978’
Cause
You entered the time with an invalid time format.
Solution
Enter the time using one of the following valid time formats:
• hh:mm:ss (24 hour clock) or hh:mm:ss am/pm
• mm/dd(/yy) or monthname dd (yy) (/yy is optional)
• Last Friday, next Friday, or third Friday A
• + or -x seconds, minutes, hours, weeks, months, or years
• Now (the current date and time)
Error Message:
TurboSTORE fails with error code n
Cause:
A request from NetWorker to start TurboSTORE failed for a backup or recovery
session.
Solution:
Ensure that your TurboSTORE product is operational. Test it by saving a small test
file to disk or to tape at the MPE prompt outside of NetWorker.
55
Appendix A: Error Messages
Error Message
Unable to relocate to /directory
Cause
NetWorker was unable to relocate the recovered file to the path you specified.
Solution
Start the recovery again and enter a valid pathname. Note that you must have write
permissions for the directory you specify.
Error Message
Unable to start backup
Cause
NetWorker was unable to execute the NSRSAVE program.
Solution
A Contact the system administrator. There could be a problem with the NetWorker
software or MPE client configuration.
Error Message:
usage: NSRARCH [<options>] [path ...]
options: [-BiLqvxVy] [-b pool] [-f directive file] [-N name]
[-s server] [-W width] [-T annotation] [-C clone pool
[-I input file] [-G remove] [-R name]
Cause:
An invalid option was entered. Note that the -E and -n NSRSAVE options have
been temporarily disabled for the NSRARCH program in NetWorker ClientPak for
MPE/iX.
Solution:
Reenter the option using only the valid options as shown in the error message.
56
Appendix A: Error Messages
Error Message:
Volume set save path argument must be by itself
Cause:
An extra save path argument was used with a volume set save path, as in the
following example:
: RUN NSRSAVE;INFO="-s nwrksrvr /PROD_VOLUME_SET /SYS/PUB"
Solution:
Specify the volume set path name by itself in a separate NSRSAVE or NSRARCH
command, as in the following example:
: RUN NSRSAVE;INFO="-s nwrksrvr /PROD_VOLUME_SET”
Error Message
Your system is not a registered client.
Cause
The server you selected does not have your system listed as a NetWorker client.
A
Solution
Contact the system administrator. Your MPE client needs to be added to the list of
recognized clients for the selected server.
57
Appendix B: Common NetWorker Commands
59
Appendix B: Common NetWorker Commands
60
Glossary
This glossary contains terms and definitions found in this manual. Most of the terms
are specific to NetWorker products.
61
Glossary
browse policy The policy that determines how long entries for
your files remain in the online file index.
62
Glossary
full (f) A backup level in which all files are backed up,
regardless of when they last changed.
Glossary
recovery services from a NetWorker server.
63
Glossary
64
Glossary
shell prompt A cue for input in a shell window where you enter
a command.
skip (s) A backup level in which files are skipped and not
backed up.
Glossary
each disk belongs to exactly one volume set.
“Volume set” is an MPE operating system term
used to denote one or more volumes that are
logically grouped together for system or business
reasons. For example, all disks that are used by the
accounting department may be put on an
exclusive volume set.
65
Index
67
Index
table of commands 29
man pages NSRRECOV program
commands for displaying 59 overview 23
descriptions in table 59 starting 26
displaying 60 NSRRETRV
manually backing up MPE volume sets 21 retrieving files from CI 50
MPE volume sets 42 retrieving files from POSIX 50
backing up 20 NSRSAVE
68
Index
69
Index
table
commands for displaying man pages 59
common NetWorker commands 59
information in the backup history of a file
35
recover commands 29
search patterns for recovering groups of
files 33
time formats, valid 36
time zone, setting NetWorker time zone to match
HP STORE process 15
True Online Backup, controlling 17
TurboSTORE online backups, storing temporary
shadow logs 16
70