Dell® EMC® NetWorker® OpenVMS Version
Release 18.1
Administration Guide
P/N 302-005-437 REV 01 Dell Copyright © 2005- 2019 Dell Inc. or its subsidiaries. All rights reserved. Published January, 2019 Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA.
Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com
2 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide CONTENTS
Preface
Chapter 1 Overview of OpenVMS Features The Dell EMC NetWorker environment and features ...... 12 NetWorker components for OpenVMS ...... 12 NetWorker user interfaces ...... 12 NetWorker command line interface...... 12 NetWorker legacy client interfaces...... 13 NetWorker character-based interface ...... 14 Understanding the NetWorker directory structure on OpenVMS ...... 14 Extended file specifications and ODS-5 volumes ...... 16 NetWorker commands and extended file specifications...... 17 Restrictions associated with extended file specifications and ODS-5..... 17 Starting and Stopping the NetWorker software ...... 18 The NetWorker startup procedure...... 18 The NetWorker shutdown procedure...... 19 Determining the NetWorker software version...... 19
Chapter 2 NetWorker Client Operations Using NetWorker commands on OpenVMS ...... 22 NetWorker commands are foreign ...... 22 NetWorker commands require privileges ...... 22 Command options are case-sensitive...... 22 Valid date/time formats for NetWorker commands ...... 22 NetWorker commands...... 24 The nsrexecd command ...... 24 The nsrinfo command...... 25 The nsrwatch command ...... 26 Identifying client data to be backed up...... 26 Pre- and postprocessing operations ...... 27
Chapter 3 Directives Directives overview ...... 32 Format of directive statements ...... 32 Precedence of directives ...... 34 Directives and ASMs supported for use on OpenVMS ...... 35 aes directive ...... 35 always directive ...... 36 asm directive ...... 36 The compressasm directive...... 37 The copy_alias directive (OpenVMS-specific) ...... 37 The ignobackup directive (OpenVMS-specific)...... 38 The logasm directive ...... 38 The nolock directive (OpenVMS-specific)...... 38 The null directive...... 39 The rawasm directive ...... 39 The record directive (OpenVMS-specific) ...... 42
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 3 Contents
The norecord directive (OpenVMS-specific) ...... 42 The skip directive...... 43 The skip_alias directive (OpenVMS-specific) ...... 43 The skip_shelved directive (OpenVMS-specific) ...... 43 The swapasm directive...... 44 The unshelve directive (OpenVMS-specific)...... 44 The xlateasm directive ...... 45 Creating directive files on the OpenVMS client ...... 45 Recommended directives for the system disk...... 46
Chapter 4 Backup and Recovery Manual backups ...... 48 Performing a manual backup on OpenVMS...... 48 Recovering data ...... 54 The recover command ...... 55 Recovering files with the nwrecover program...... 64 Relocating recovered data...... 65 Saving and recovering an OpenVMS system disk...... 66 Backing up an OpenVMS system disk...... 66 Recovering an OpenVMS system disk...... 68 Performing a physical disk backup and recovery...... 69 Performing an ad hoc physical disk backup...... 69 Recovering a physical disk backup...... 70
Chapter 5 Archiving Overview of archiving...... 74 Archive requirements ...... 74 How the NetWorker server archives data ...... 74 Manual archive operations...... 75 Performing a manual archive on OpenVMS...... 75 Retrieving archived data...... 80 The nsrretrieve command...... 81 Retrieving data using the nwretrieve program...... 83
Appendix A Logical Names NetWorker Logical Names...... 86
Appendix B NetWorker Module for Oracle Overview of the NetWorker Module for Oracle...... 98 Installing the Oracle module ...... 98 Configuring the Oracle module...... 98 Manual Oracle backups...... 99 Creating RMAN scripts for manual backups ...... 100 Server-initiated Oracle backups ...... 103 Creating RMAN and DCL scripts for server-initiated backups...... 104 Configuring the NetWorker Client resource for Oracle backups ...... 107 Restoring and recovering Oracle data ...... 108 Preparing to restore Oracle data ...... 108 Creating the RMAN restore script ...... 108 Restoring an Oracle database...... 109 Completing the Oracle data recovery ...... 109 Oracle database recovery...... 110
4 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Contents
Appendix C NetWorker Module for Oracle Rdb Overview of the NetWorker Module for Oracle Rdb...... 112 Installing the Oracle Rdb module...... 112 Configuring the Oracle Rdb module ...... 112 Manual Oracle Rdb backups...... 112 Defining logical names to set NetWorker environment variables...... 113 Server-initiated Oracle Rdb backups...... 113 Task 1: Create the Rdb backup script...... 114 Task 2: Configure the Client resource for Oracle Rdb backups...... 115 Task 3: Test the script ...... 115 Task 4: (Optional) Back up the sample Oracle Rdb database ...... 116 Restoring Oracle Rdb data...... 118 Restoring the sample Oracle Rdb database ...... 118 Known restrictions ...... 119
Glossary
Index
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 5 Contents
6 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide PREFACE
As part of an effort to improve its product lines, Dell EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your Dell EMC technical support professional if a product does not function properly or does not function as described in this document.
Note: This document was accurate at publication time. Go to Dell EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.
Purpose This document provides planning, practices, and configuration information for the use of the Dell EMC NetWorker OpenVMS features within a NetWorker backup and storage management environment. Audience This document is intended for system administrators.
Related documentation The following Dell EMC publications provide additional information:
◆ Dell EMC NetWorker Release 18.1 OpenVMS Version Release Notes ◆ Dell EMC NetWorker Release 18.1 OpenVMS Version Installation Guide ◆ Dell EMC NetWorker Administration Guide ◆ Dell EMC NetWorker Error Message Guide ◆ Dell EMC NetWorker Command Reference Guide Conventions used in this document Dell EMC uses the following conventions for special notices:
NOTICE is used to address practices not related to personal injury.
Note: A note presents information that is important, but not hazard-related.
Preface 7 Preface
Typographical conventions Dell EMC uses the following type style conventions in this document: Bold Use for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks) Italic Use for full titles of publications referenced in text
Monospace Use for: • System output, such as an error message or script •System code • Pathnames, filenames, prompts, and syntax • Commands and options
Monospace italic Use for variables. Monospace bold Use for user input. [ ] Square brackets enclose optional values | Vertical bar indicates alternate selections — the bar means “or” { } Braces enclose content that the user must specify, such as x or y or z ... Ellipses indicate nonessential information omitted from the example
Where to get help Dell EMC support, product, and licensing information can be obtained as follows: Where to find product documentation
◆ https://www.dell.com/support
◆ https://community.emc.com Where to get support The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories, downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Support. To access a product-specific page: 1. Go to https://www.dell.com/support. 2. In the search box, type a product name, and then from the list that appears, select the product. Knowledgebase The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword. To search the Knowledgebase: 1. Go to https://www.dell.com/support.
2. On the Support tab, click Knowledge Base. 3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by typing a product name in the search box, and then selecting the product from the list that appears.
8 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Preface
Live chat To participate in a live interactive chat with a support agent: 1. Go to https://www.dell.com/support.
2. On the Support tab, click Contact Support. 3. On the Contact Information page, click the relevant support, and then proceed. Service requests To obtain in-depth help from Licensing, submit a service request. To submit a service request: 1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests.
Note: To create a service request, you must have a valid support agreement. For details about either an account or obtaining a valid support agreement, contact a sales representative. To get the details of a service request, in the Service Request Number field, type the service request number, and then click the right arrow.
To review an open service request: 1. Go to https://www.dell.com/support.
2. On the Support tab, click Service Requests. 3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests. Online communities For peer contacts, conversations, and content on product support and solutions, go to the Community Network https://community.emc.com. Interactively engage with customers, partners, and certified professionals online. How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to [email protected].
9 Preface
10 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide CHAPTER 1 Overview of OpenVMS Features le Body Tag
This chapter covers these topics:
◆ The Dell EMC NetWorker environment and features ...... 12 ◆ NetWorker user interfaces ...... 12 ◆ Understanding the NetWorker directory structure on OpenVMS ...... 14 ◆ Extended file specifications and ODS-5 volumes ...... 16 ◆ Starting and Stopping the NetWorker software ...... 18 ◆ Determining the NetWorker software version...... 19
Overview of OpenVMS Features 11 Overview of OpenVMS Features
The Dell EMC NetWorker environment and features
The Dell EMC® NetWorker® environment provides backup and restore capabilities to protect against data loss. You can use the NetWorker Management Console to remotely manage all NetWorker clients and servers within a NetWorker datazone. The Dell EMC NetWorker Administration Guide provides details on the Console and all of the NetWorker components.
NetWorker components for OpenVMS
The NetWorker components that are available specifically for use on the OpenVMS platform are as follows:
NetWorker client A NetWorker client computer is any computer whose data must be backed up.
NetWorker storage node A NetWorker storage node can be used to improve performance by off-loading from the NetWorker server much of the data movement involved in a backup or recovery operation. NetWorker storage nodes are also NetWorker clients.
NetWorker Module for Oracle The NetWorker Module for Oracle software enables you to back up Oracle databases that are running on the OpenVMS operating system. Appendix B, “NetWorker Module for Oracle,”provides more information on this component.
NetWorker Module for Oracle Rdb The NetWorker Module for Oracle Rdb software enables you to back up Oracle Rdb databases that are running on the OpenVMS operating system. Appendix C, “NetWorker Module for Oracle Rdb,” provides more information on this component. NetWorker user interfaces
The NetWorker for OpenVMS client uses the interfaces described in this section.
NetWorker command line interface
NetWorker client tasks can be performed by entering commands at the DIGITAL Command Line (DCL) prompt. Chapter 2, “NetWorker Client Operations,” describes the NetWorker commands available for use on the OpenVMS operating system and explains how to use them. For more information on NetWorker commands:
◆ Refer to the Dell EMC NetWorker Command Reference Guide.
◆ Use the NetWorker command line help (also referred to as DCL Help) by entering the following at the DCL prompt:
help networker command_name
12 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Overview of OpenVMS Features
where command_name is the name assigned by command procedure NSR$SYSTEM:NSR$LOGIN.COM (nsrsave rather than save, for example).
NetWorker legacy client interfaces
Along with the command line interfaces for save, recover, archive, and retrieve, the NetWorker OpenVMS software package includes legacy Motif-based UIs for each function. These programs are nwbackup, nwrecover, nwarchive, and nwretrieve. They reside in the NSR$SYSTEM directory. These program are provided as-is. The command line variants are preferred and will demonstrate superior performance and capability.
The nwbackup program The nwbackup program provides a graphical representation of the client’s file system where you can browse to files and execute manual backups from the client machine. To start the nwbackup program, type the nwbackup command at the DCL prompt. Include the -s option and the name of the target NetWorker server. For example:
nwbackup -s myserver
The nwrecover program
The nwrecover program provides a graphical interface where you can browse backed-up files and file systems and select items for recovery. The versions of files and file systems available in nwrecover are determined by the time period specified in the browse policy, which is defined on the NetWorker server. To start the nwrecover program, type the nwrecover command at the DCL prompt. Include the -s option and the name of the target NetWorker server. To specify a particular NetWorker client, include the -c option and the name of the client. For example:
nwrecover -s myserver -c oreo If the -c option is not present, the local computer is used by default.
The nwarchive program The nwarchive program provides a graphical interface from which you can manually archive client data. To start the nwarchive program, type the nwarchive command at the DCL prompt. Include the -s option and the name of the target NetWorker server. For example:
nwarchive -s myserver
The nwretrieve program
The nwretrieve program provides a graphical interface from which you can retrieve archived client data. Before starting this program, you must mount the archive volume in the appropriate storage device. To start the nwretrieve program, type the nwretrieve command at the DCL prompt. Include the -s option and the name of the target NetWorker server. For example:
nwretrieve -s myserver
NetWorker user interfaces 13 Overview of OpenVMS Features
NetWorker character-based interface
The nsradmin program provides a character-based interface that can be used to perform configuration and management tasks for a NetWorker server. To start the nsradmin interface, type the nsradmin command at the DCL prompt. Include the -s option and the name of the target NetWorker server. For example:
nsradmin -s myserver Refer to the Dell EMC NetWorker Command Reference Guide for more information on this command. Understanding the NetWorker directory structure on OpenVMS
The NetWorker software for OpenVMS can be installed in any directory. By default, it is installed on the system disk in the [VMS$COMMON] directory. Regardless of where you install the NetWorker software, it creates the directory structure shown in the following illustration.
14 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Overview of OpenVMS Features
Figure 1 NetWorker Directory Structure on OpenVMS
Note: The subdirectories shown here are subject to change. The actual NetWorker installation may create more or different subdirectories, although the directory structure remains the same.
The following logical names are defined by the NetWorker startup procedure. Their definitions are based on the /DESTINATION qualifier value that was specified during the NetWorker installation.
◆ NSR$COMMON — Specifies the location of the NetWorker common directory tree. However, it is usually defined by using the [.NSR$
◆ NSR$SPECIFIC — Specifies the location of the NetWorker node-specific ([NSR$
Understanding the NetWorker directory structure on OpenVMS 15 Overview of OpenVMS Features
In general, files that are common to all nodes in a NetWorker for OpenVMS installation are found in the [NSR$COMMON] directory tree. Examples include product executable programs and common command procedures. Files that are created by the NetWorker software, such as the log for the nsrexecd process, are normally found in the node-specific directory tree. Additional logical names are defined in a search list so that the node-specific directory is searched first, followed by the common directory. For example, the logical name NSR$LOGS points to the log file directories. Because of the way it is defined, it points to the [.NSR$
◆ NSR$BITMAPS — Used to access the [.BITMAPS] subdirectories
◆ NSR$COMMON — Used to access the common NetWorker directory structure
◆ NSR$LOGS — Used to access the [.LOGS] subdirectories
◆ NSR$RES — Used to access the [.RES] subdirectories
◆ NSR$SPECIFIC — Used to access the node-specific directory structure
◆ NSR$SYSROOT —A search list logical used to access the node-specific directories followed by the common directories
◆ NSR$SYSTEM — Used to access the [.NSR] subdirectories
◆ NSR$TMP — Used to access the [.TMP] subdirectories This arrangement allows you to configure the NetWorker software for OpenVMS for general use in a cluster environment, while maintaining individual directories for log files and other node-specific activities. The Dell EMC NetWorker HP OpenVMS Version Installation Guide provides instructions for configuring the NetWorker software in a cluster environment. Appendix A, “Logical Names” provides a complete list of logical names used by the NetWorker software for OpenVMS. Extended file specifications and ODS-5 volumes
On volumes that use On-Disk Structure Level 5 (ODS-5), users can create longer filenames that contain a wider range of legal characters than those on the more traditional ODS-2 volumes. Filenames on ODS-5 volumes can be up to 236 8-bit characters or 118 16-bit characters in length, excluding the version number. These filenames can also contain characters from the 8-bit ISO-LATIN1 and 16-bit Unicode (UCS-2) character sets, in addition to the ODS-2-compliant character set. The ODS-2-compliant character set includes alphanumeric characters (A-Z, a-z, 0-9), the dollar sign ($), underscore (_), and hyphen (-). Filename length is limited to the 39.39 format. Filename case is recognized and supported on ODS-5 volumes. Filenames can contain lowercase, uppercase, or mixed-case characters. The case is preserved as created. On ODS-2, all characters are converted to uppercase.
16 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Overview of OpenVMS Features
The NetWorker software for OpenVMS supports these extended file specification and ODS-5 features as described in the sections that follow. The OpenVMS documentation provides more information on extended file specifications, ODS-5 volume structure, and case-sensitive file system operations.
NetWorker commands and extended file specifications
When any of the following NetWorker commands are used and an ODS-5 volume is being accessed, the NetWorker software automatically enables extended file specifications and case sensitivity: nsrinfo nsrrecover nwrecover nsrretrieve
When specifying an ODS-5 filename in any of these commands, you must enter the filename exactly as it was originally saved or archived, in uppercase, lowercase, or mixed-case, and enclose it in quotation marks. For example:
nwrecover -a -s cider "DISK$USER2:[JONES]MyFile.txt;3"
To prevent the NetWorker software from automatically enabling extended file names and case sensitivity on ODS-5 volumes, define the logical name NSR$NO_CASE_SENSITIVE to any value. For example:
define nsr$no_case_sensitive true
In this case, NetWorker will use the default parsing style (TRADITIONAL) and case lookup method (BLIND).
After defining the NSR$NO_CASE_SENSITIVE logical name, you can manually set the process to enable extended file specifications and case sensitivity by entering the following command at the DCL prompt before starting the NetWorker process:
SET PROCESS /PARSE_STYLE=EXTENDED /CASE_LOOKUP=SENSITIVE
To reset DCL to its default parsing style and case lookup method after the process completes, enter the next command:
SET PROCESS /PARSE_STYLE=TRADITIONAL /CASE_LOOKUP=BLIND
The NetWorker software for OpenVMS ignores the parse and case lookup settings when recovering files on an ODS-2 volume.
Restrictions associated with extended file specifications and ODS-5
The following restrictions are associated with the ODS-5 environment:
◆ When you issue commands in a case-sensitive process environment, only those filenames that match the specified name and case are returned.
◆ Because some ODS-5 filenames can use characters not found in the ODS-2 character set, these filenames may be changed when you restore ODS-5 files to an ODS-2 volume. This is necessary to permit creation of these files on the ODS-2 device.
Extended file specifications and ODS-5 volumes 17 Overview of OpenVMS Features
◆ Directories that do not have the file extension .DIR;1 (all uppercase) are not supported on ODS-5 volumes. These invalid directories can get created accidentally with a RENAME or SET FILE /ENTRY command. You can determine whether any of your directories are invalid by using a variation of the following command:
pipe directory disk$i64v821:[000000...]*.*;* | - search sys$input ".dir;1",".Dir;1",".dIr;1",".diR;1"/exact Rename any invalid directories that are found to use a DIR;1 extension. Although the ODS-5 file system does not support these invalid directories, the NetWorker software will save them and their contents during a scheduled group save. You can recover them by using normal recovery procedures. The recovered directory will have a corrected file extension of .DIR;1.
◆ File attributes specific to ODS-5 and not available on ODS-2 will not be restored. Starting and Stopping the NetWorker software
The NetWorker software for OpenVMS provides the following command procedures for starting up and shutting down the NetWorker software:
◆ SYS$STARTUP:NSR$STARTUP.COM
◆ SYS$MANAGER:NSR$SHUTDOWN The Dell EMC NetWorker HP OpenVMS Version Installation Guide instructs the NetWorker installer to add entries to the system startup and shutdown command procedures that cause them to run these NetWorker command procedures. This ensures automatic startup and efficient shutdown of the NetWorker client software on an OpenVMS client computer. If necessary, you can run the NetWorker shutdown and startup procedures manually from a privileged account. For example:
@sys$manager:nsr$shutdown
The NetWorker startup procedure
The startup procedure for the NetWorker software for OpenVMS is named SYS$STARTUP:NSR$STARTUP.COM. It performs the following operations:
◆ Ensures sufficient privileges for starting NetWorker.
◆ Defines the convenience logical names described in “Understanding the NetWorker directory structure on OpenVMS” on page 14.
◆ Executes SYS$MANAGER:NSR$LOGICAL_NAMES.COM to define the root logical names (unique to each cluster node) that locate the NetWorker software on this machine.
◆ If a NetWorker Module for Oracle or Oracle Rdb is installed, defines the RMU$LIBRARIAN_PATH or LIBNWORA_SHR logical name to identify the appropriate NetWorker Oracle Module.
◆ Defines the NSR$CLUSTER_ALIAS_NAME logical name if the NetWorker software was configured for a cluster environment.
◆ Starts the nsrexecd daemon.
18 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Overview of OpenVMS Features
The NetWorker shutdown procedure
The shutdown procedure for the NetWorker software for OpenVMS is named SYS$MANAGER:NSR$SHUTDOWN.COM. It performs the following operations:
◆ Stops the nsrexecd daemon and other associated programs, such as nsrmmd and nsrlcpd.
◆ Removes foreign commands defined by the NSR$SYSTEM:NSR$LOGIN.COM procedure.
◆ Disassociates the NetWorker Oracle Rdb library from RMU. The shutdown procedure does not disassociate the NetWorker Oracle library from RMAN, nor does it deassign the NetWorker logical names. Determining the NetWorker software version
When requesting assistance with NetWorker software, you need to know which release you are running. To obtain release and version information for the NetWorker software for OpenVMS, type the following command at the DCL prompt:
@nsr$system:nsr$version This command prints out the name of the program, the PCSI release number (Alpha only), and the version and link date/time of the image identification portion of all images in the NetWorker system directory. Unless you have hot fix updates or patches installed for the NetWorker software, the image identification values should be identical for all images in the NetWorker distribution, except for nwsave, nwarchive, nwrecover, and nwretrieve, which are legacy GUI programs from V7.3, ECO 14.
Note: OpenVMS shows the NetWorker release number with a hyphen rather than a second period due to PCSI restrictions associated with version numbering. For example, NetWorker release 9.2.1 is identified as V9.2-1 on OpenVMS.
Determining the NetWorker software version 19 Overview of OpenVMS Features
20 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide CHAPTER 2 NetWorker Client Operations Invisible Body Tag
This chapter covers these topics:
◆ Using NetWorker commands on OpenVMS ...... 22 ◆ Identifying client data to be backed up...... 26 ◆ Pre- and postprocessing operations ...... 27
NetWorker Client Operations 21 NetWorker Client Operations
Using NetWorker commands on OpenVMS
This section explains how to use NetWorker commands on the OpenVMS operating system and provides a complete list of available commands.
NetWorker commands are foreign
Because foreign commands are used to invoke the NetWorker software for OpenVMS, you must define the NetWorker commands for use in the OpenVMS environment. The Dell EMC NetWorker HP OpenVMS Version Installation Guide describes three methods for defining NetWorker commands:
◆ Use automatic foreign commands by adding NSR$SYSTEM to the DCL$PATH logical name.
◆ Execute the NSR$SYSTEM:NSR$LOGIN.COM command procedure to define foreign commands for all NetWorker programs found in NSR$SYSTEM.
◆ Use the mcr command interpreter to execute the commands directly.
Note: Except where the mcr command syntax is explicitly shown, examples in this document show commands as they would be entered on an OpenVMS client system where the NSR$LOGIN.COM command procedure has been executed. Because this command procedure adds an nsr prefix to each command (as required by OpenVMS conventions), the command names shown in examples include the command prefix. For example, nsrsave is shown in examples rather than save.
NetWorker commands require privileges
Most NetWorker commands require nondefault privileges. To allow nonprivileged use of NetWorker commands, specifically those related to save and recover functions, you must install the commands with privileges. Refer to the Dell EMC NetWorker HP OpenVMS Version Installation Guide for instructions.
Command options are case-sensitive
The command line syntax is case-sensitive. However, unlike DCL commands, which normally default to uppercase characters, the NetWorker commands default to all lowercase characters. Therefore, to retain their case, all uppercase options must be enclosed within quotation marks (" "). For example:
nsrexecd "-D" 3 Any argument that contains uppercase characters, embedded spaces, or punctuation must also be enclosed within quotation marks.
Valid date/time formats for NetWorker commands
The NetWorker software uses a routine named nsr_getdate to convert ASCII date and time specifications to a format recognizable to the NetWorker software. All date/time arguments supplied to the NetWorker software must be entered in a format that is acceptable to the nsr_getdate program.
22 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Client Operations
The nsr_getdate routine accepts most common abbreviations for days, months, and so on. In particular, nsr_getdate recognizes them with an uppercase or a lowercase first letter, and will recognize three-letter abbreviations for any of them, with or without a trailing period. Units such as weeks can be specified as singular or plural. Time zone and meridian values can be in upper- or lowercase, with or without periods. The nsr_getdate routine accepts a standard OpenVMS date-time specification for absolute time provided it is enclosed within quotation marks. For example, "21-SEP-2006 13:43" is acceptable. Relative times, however, must comply with the format guidelines presented in Table 1, which lists valid date and time formats for use on a NetWorker client.
Table 1 Valid date formats for nsr_getdate
Format Description
TOD Time of day, which is of the form hh[:mm[:ss]] (or hhmm) [meridian] [zone]. If no meridian (am or pm) is specified, a 24-hour clock is used. A TOD may be specified as just hh, followed by a meridian. If no zone (for example, GMT) is specified, the local time zone is assumed.
Date A specific month and day, and (optional) year. Valid date formats are mm/dd[/yy] and monthname dd[, yy]. If omitted, the year defaults to the current year. If a year is specified as a number within the range of 70 to 99, then 1900 is added. If a year is in the range of 00 to 30, then 2000 is added. If a number is followed by a day or relative time unit, it will be interpreted as a year provided a TOD, monthname, and dd have already been specified. Otherwise, it will be treated as a TOD.
Day Day of the week. The current day will be used if appropriate. To indicate a specific instance of that day, you may precede the day with a number. The default is 1. Negative numbers indicate times past. Some symbolic numbers are accepted: last, next, and the ordinals first through twelfth (second is ambiguous and is not accepted as an ordinal number). The symbolic number next is equivalent to 2; thus, next Monday refers not to the immediately upcoming Monday, but to the one a week later.
Relative time Specifications relative to the current time are also accepted. The format is [number] unit. Acceptable units are year, month, fortnight, week, day, hour, minute, and second.
The actual date is formed as follows: 1. Any absolute date and/or time is processed and converted. 2. Day-of-week specifications are added to the base date/time. 3. Relative specifications are used. If a date or day is specified and no absolute or relative time is given, midnight is used. 4. A correction is applied for daylight savings time differences. nsr_getdate restrictions The nsr_getdate routine has the following known restrictions:
◆ Some desirable and unambiguous constructions are not accepted.
◆ The meaning of some legal phrases is not what is expected. For example, next is equivalent to 2; thus, next Monday equates to the Monday that occurs 1 week after the upcoming Monday. Next week is interpreted as 2 weeks from now.
Using NetWorker commands on OpenVMS 23 NetWorker Client Operations
◆ The daylight savings time correction can become incorrect if the provided times are between midnight and 2:00 A.M. on the days that daylight savings time changes.
◆ Passing nsr_getdate a current time containing a different zone may fail. NetWorker commands
This section provides additional information on the nsrexecd, nsrinfo, and nsrwatch commands. For more information on the save and recover commands, see Chapter 4, “Backup and Recovery.” For more information on the nsrarchive and nsrretrieve commands, see Chapter 5, “Archiving.” To access command syntax and descriptions for all NetWorker commands that are valid on the OpenVMS operating system, type the following command at the DCL prompt:
help networker
Note: The DCL help for NetWorker uses the command names assigned by the NSR$SYSTEM:NSR$LOGIN.COM procedure. Therefore, help on the NetWorker save command can be found under nsrsave; help on recover can be found under nsrrecover; and so on. “NetWorker commands are foreign” on page 22 provides details.
The NetWorker man pages and the Dell EMC NetWorker Command Reference Guide provide a complete description of all NetWorker commands.
The nsrexecd command
The nsrexecd daemon is used by NetWorker servers to perform automatic operations on NetWorker clients. Under normal circumstances, the nsrexecd daemon is started by the command procedure SYS$STARTUP:NSR$STARTUP.COM. The NSR$STARTUP.COM procedure and the NSR$EXECD account under which the daemon runs ensure that the required quotas and privileges are in effect to allow the daemon to function properly. (The Dell EMC NetWorker HP OpenVMS Version Installation Guide lists the minimum account quotas required by the NSR$EXECD account.) Do not run the nsrexecd daemon interactively unless you are specifically instructed to do so for troubleshooting purposes. The format for the nsrexecd command is as follows:
nsrexecd [-s server [-s server ...]][-f serverfile] [-p savepath][-i]["-D" debug_level]
24 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Client Operations
Table 2 describes the valid options for the nsrexecd command.
Table 2 nsrexecd command options
Option Argument Description
-s server name (Server) Specifies the name of the NetWorker server that will be allowed to initiate save requests. Multiple -s options can be used to allow access by several NetWorker servers. If a NetWorker server has multiple network interfaces, list the hostname corresponding to each network interface to avoid failed saves.
-f server Specifies the name of a file that contains a list of NetWorker filename servers (one on each line) that can initiate saves. If no -f or -s option is specified, nsrexecd uses the default servers file, which is created by the NetWorker installation procedure in the NSR$SYSROOT:[NSR.RES] directory.
-p save path Directs nsrexecd to look for save commands in the savepath directory (the directory in which nsrexecd exists) rather than the default directory.
-i none As part of the NetWorker server authentication, the server's network address is mapped to a name. The name is then reverse-mapped to a network address. The server is authenticated if and only if the original network address matches the reverse-mapped address. The -i flag directs the nsrexecd to skip this authentication step. Important: Use this option with caution because it may allow the NetWorker client to send its data to an unauthorized computer.
-D level of Specifies the level of debugging information that will be output debugging by the nsrexecd daemon. The debug option accepts numeric (1-15) arguments of 1 to 15, with 15 producing the greatest amount of information.
The nsrinfo command
The nsrinfo command generates reports about the contents of a client file index. On other NetWorker platforms, the default behavior of this command is to list filenames as they are stored in the NetWorker file index. However, on OpenVMS clients, this command lists filenames as they would appear if they were restored (in mixed case, for example), rather than how they are actually stored (all uppercase). To make the nsrinfo command list filenames as they are actually stored, you must include the -r option in the nsrinfo command. The following sample command displays all filenames for a specific client as they are stored in the NetWorker file index:
nsrinfo -r -s cider oreo where:
◆ cider is the name of the NetWorker server being queried.
◆ oreo identifies the NetWorker client computer whose file index is being queried.
Using NetWorker commands on OpenVMS 25 NetWorker Client Operations
The nsrwatch command
The nsrwatch command runs the nsrwatch command line program, which displays the status of a NetWorker server in character-based format. If no server is specified, the program defaults to the server that would be used by a NetWorker command issued from the current directory. The nsrwatch program runs continuously until you quit the program (by typing q) or interrupt it (by pressing Ctrl-c, for example). The format for the nsrwatch command is as follows:
nsrwatch [-s server][-p polltime] Table 3 describes the valid options for the nsrwatch command.
Table 3 nsrwatch command options
Option Argument Description
-s server name (Server) Specifies the name of the NetWorker server that will be monitored.
-p number of (Polling interval) Defines the polling interval in seconds. The seconds default polling interval is 2 seconds.
For more information on the nsrwatch command, refer to the Dell EMC NetWorker Command Reference Guide. Identifying client data to be backed up
The collection of all data items that are backed up during a backup session between the server and client is called a save set. A save set can consist of a group of files or entire file systems, as well as application-generated data, such as a database or operating system information. When the NetWorker administrator creates the Client resource for an OpenVMS client on the NetWorker server, the NetWorker software is configured to back up all online, locally mounted disk devices on the client computer by default during server-initiated backups. You can restrict the devices that are eligible for backup services by changing the Save Set attribute of the Client resource. Multiple disk and directory specifications can be defined in the Save Set attribute. For example, to back up only two devices on the OpenVMS client—DISK$USER12 and DISK$USER—you would define the Save Set attribute as follows:
DISK$USER12:[000000] DISK$USER:[000000] While this example shows top-level directories, you can specify any directory found on the associated device. The save program will begin scanning for candidates at the specified directory and work its way down through the directory structure. A way to limit the files that will be backed up by a server-initiated save is to create directive files and place them in the top-level directory of the devices that you do not want backed up. The directive file would contain a directive similar to the following:
<<"disk:[000000]">>
26 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Client Operations
+null: *.*;* If the Save Set attribute of the Client resource contains the All save set, a save program will be started for each device on the client. On devices that use the sample directive file shown here, only connecting directory information will be saved. For more information on using directives, see Chapter 3, “Directives.” After you have specified which files are to be backed up by server-initiated saves, you are ready to create the schedules, policies, and pools as appropriate for your environment. The Dell EMC NetWorker Administration Guide provides details. For information on specifying the save set name during a user-initiated save, see the description of the -N option in Table 4, “save command options,” on page 50. Pre- and postprocessing operations
The NetWorker software for OpenVMS supports saveset based pre- and post processing. To use save set-based pre- and postprocessing on an OpenVMS client, you create the appropriate DCL command files and then define the following logical names on the client computer, where saveset_name represents the name of the save set that the save program will process:
◆ NSR$PRE_saveset_name, which identifies the name of the preprocessing command file.
◆ NSR$PST_saveset_name, which identifies the name of the postprocessing command file. You may define either or both of these logical names.
Define these logical names with the /SYSTEM and /EXECUTIVE qualifiers. Otherwise, the save program will ignore them.
Because the logical names are tied to the save set name, the save program must be invoked with the "-N" option, which specifies the name of the save set. This is the default behavior when save is invoked by the nsrexecd through the NetWorker server.
Note: When you create your DCL command files for pre- and postprocessing, ensure that your command scripts exit with the appropriate DCL status values. If a preprocessing script exits with an OpenVMS status code other than success (W, E, or F, for example), then the save program will halt and will not execute the save or the postprocessing commands.
You must also verify that pre- and postprocessing command files exist in the locations specified by the defined logical names. If these files are not present when save attempts to execute them, the process fails with RMS$_FNF (no such file) and the save program halts and does not execute the save. The following is an example of a command script that could be used for both pre- and postprocessing:
tmp = f$environment("procedure") fname = f$parse(tmp,,,"name") write sys$output "''fname' Starting at ''f$time()'"
Pre- and postprocessing operations 27 NetWorker Client Operations
wait 00:00:02 write sys$output "''fname' Ending at ''f$time()'" exit 1 This command script simply prints out a starting and ending message. The wait statement allows the pre- and postprocessing processes to exist long enough to be seen with the DCL SHOW SYSTEM command. To use this command script for both pre- and postprocessing of a save set named DISK$TEST:[000000], you would include this script in two command files (test_pre.com and test_pst.com in the next example) and then define the pre- and postprocessing logical names as follows:
define/system/executive nsr$pre_disk$test:[000000] - nsr$system:test_pre.com
define/system/executive nsr$pst_disk$test:[000000] - nsr$system:test_pst.com
SYS$OUTPUT for save set-based pre- and postprocessing The SYS$OUTPUT device for the save set-based pre- and postprocessing files is the same as the SYS$OUTPUT for the save program, and appears on the NetWorker server. Because save is active during both the pre- and postprocessing phases, the output of these command files is available in the Group Backup Details dialog box of the NetWorker Management Console. The Dell EMC NetWorker Administration Guide explains how to view group backup details. Limit the amount of data that your program writes to SYS$OUTPUT because it affects both the nsrexecd and the NetWorker server. You can include commands in the pre- and/or postprocessing command files to direct large amounts of output to a log file, for example.
Privileges for save set-based pre- and postprocessing When the save program is initiated by the nsrexecd daemon, in response to a request from the NetWorker server, it assumes the privileges of the daemon. The nsrexecd daemon has the following authorized and default privileges:
◆ Authorized privileges: BYPASS, CMKRNL, DIAGNOSE, EXQUOTA, DETACH, LOG_IO, NETMBX, PHY_IO, PRMMBX, PSWAPM, SHARE, SYSGBL, SYSLCK, SYSNAM, SYSPRV, TMPMBX, WORLD
◆ Default privileges: NETMBX and TMPMBX Any subprocess that is started by save has the same privileges. If commands in your pre- or postprocessing command files require additional privileges, you must install the save program with the required additional privileges. Use the following command to accomplish this:
install add nsr$system:save/open/header/priv=(priv-list)
This command authorizes but does not enable the privileges listed in the priv-list. Your pre- or postprocessing command file must explicitly enable the appropriate privileges with a SET PROCESS/PRIVILEGE command prior to the execution of any commands that
28 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Client Operations require those privileges. You can then disable the privileges from the command file by including another SET PROCESS/PRIVILEGE command similar to the one shown in the next example, which reduces privileges to default privileges only:
SET PROCESS/PRIV=(NOALL,TMPMBX,NETMBX)
Pre- and postprocessing operations 29 NetWorker Client Operations
30 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide CHAPTER 3 Directives Invisible Body Tag
This chapter covers these topics:
◆ Directives overview ...... 32 ◆ Directives and ASMs supported for use on OpenVMS ...... 35 ◆ Creating directive files on the OpenVMS client ...... 45 ◆ Recommended directives for the system disk...... 46
Directives 31 Directives
Directives overview
Directives are special instructions that control how the NetWorker server processes files and directories during backup. Directives can be used to customize NetWorker processes to meet specific needs, maximize the efficiency of backups, and apply special handling to individual files or directories. Directives for use with an OpenVMS client can be specified in any of the following places (unless otherwise noted in the individual directive descriptions):
◆ On the save command line by using the -f option.
◆ In a local directive file named .NSR that users can create on the NetWorker client machine.
◆ On the NetWorker server as a resource that can be applied to individual clients as needed. (These are referred to as global directives.) NetWorker directives use the same format, regardless of where they are specified.
Format of directive statements
Both local and global directives use a format that contains three primary types of statements:
◆ Directory specification
◆ Directive name and an optional filename argument (except when the rawasm directive is used, which requires a device name argument)
◆ Save environment keywords The syntax for NetWorker directives is as follows:
[<<"directory-specification">>] [+]directive-name[:filename] [<<"directory-specification">>] [save-environment-keyword] [more-directives...] Directory specifications and filenames are not case-sensitive in directives that apply to OpenVMS clients. You can include several directives in a single directive.
Note: Do not leave blank lines in directive scripts.
Directory specifications Directory specifications in directives specify the highest-level directory to which the directives following that entry apply. A directory specification is required with all directives and must be a valid OpenVMS disk and directory specification, such as DISK$USER1:[SMITH]. If you omit the disk portion of the directory specification, the NetWorker software uses the current disk being processed. You can use a common directive for multiple disks by omitting the disk from a directive. You can also specify the root directory, which is defined for NetWorker software as the forward slash (/), as the directory specification. The directory specification must use the following syntax:
32 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
<<"directory-specification">> It must be enclosed within double quotes (" ") and double angle brackets (<< >>) as shown. Wildcards of any kind are not supported within the directory specification. Rooted directories are also not supported. Directives can contain multiple directory specifications as shown in the syntax diagram in “Format of directive statements” on page 32.
Directive name and filename This statement specifies which directive or application-specific module (ASM) to run and the name of the file or device to be backed up. The filename argument is optional, as described here. However, a device name argument is required when the specified directive is rawasm. “The rawasm directive” on page 39 describes the specific syntax required by that directive. The directive name and filename syntax is as follows:
[+]directive-name[:file-name] where:
◆ [+] — The optional plus sign (+) that precedes the directive name indicates that this directive applies to all files that match the given filename in the current or previously specified directory and all of its subdirectories. If the plus sign is omitted, the directive is not applied to subdirectories.
◆ directive-name[:file-name] — A directive or ASM name is required. “Directives and ASMs supported for use on OpenVMS” on page 35 lists the directives that are valid with the OpenVMS client. If an optional filename is specified, it must be separated from the directive name by a colon (:). You can specify multiple filenames separated by spaces. The filenames that you specify must include the OpenVMS filename, file extension, and version. Do not include directory information. Wildcards are allowed in filenames. A percent sign (%) can be used as a single-character wildcard. An asterisk (*) can be used to match one or more characters within the filename or the entire filename (filename.extension;version). Both * and *.* default to *.*;*. For example, all of these filenames are valid: • * (represents all versions of all files) • *.LOG;* (represents all versions of any file with a .LOG extension) • sys* (represents all versions of all files whose names begin with "sys")
When the NSR$NO_DEFAULT_WILDCARD logical name is defined, the wildcards * and *.* no longer default to *.*;*. Standard DCL wildcard usage rules apply. The asterisk (*) wildcard character can be used to match one or more characters only within a single portion of the filename. Missing portions of the filename do not default to a wildcard.
Directives overview 33 Directives
Save environment keywords Save environment keywords determine whether previously specified save directives are in force for a particular directory or directory tree. There are three save environment keywords:
◆ allow ◆ forget ◆ ignore The allow and ignore keywords operate similarly and cause directive files found in the online file system to be allowed or ignored, respectively. The ignore keyword instructs the NetWorker server to ignore all directives specified in directive files above the current directory, while the allow keyword is used to override the ignore. The forget keyword causes all directives currently in effect (from the save command line, directive files, or server-based directive resources) to be forgotten. You can use the forget directive to eliminate any possible directives from higher up in the directory tree and establish the set of directives to use from the current directory downward. The scope of the forget directive extends from the directory where it is specified in a directive file to all lower subdirectories. An example of using save environment keywords is as follows: Assume that the recommended skip_alias and nolock directives are specified in SYS$SYSDEVICE:[000000].NSR;1 on an OpenVMS system disk. You can turn these directives off in a subdirectory by including a directive file that includes the ignore keyword. After that subdirectory and all of its subdirectories have been processed, the effect of the ignore keyword no longer applies and the save command once again skips alias files and saves open files. If you wanted the save command to resume the use of the skip_alias and nolock directives before reaching the bottom of the directory tree in which the ignore keyword was used, you could create another directive file in a subdirectory that uses the allow keyword. The effect of the allow keyword encompasses the directory in which the directive is found and all subdirectories of that directory.
Precedence of directives
If there is a conflict between global directives (created on the NetWorker server) and local directives (created on an OpenVMS client), global directives take precedence. If more than one directive is associated with a directory specification, the precedence of directives is based on the order in which they are specified. The first directive takes precedence over the second, the second takes precedence over the third, and so on. This order-based precedence does not apply to OpenVMS-specific directives, such as nolock, copy_alias, and norecord, however. OpenVMS-specific directives act as attributes associated with the save of the particular file that they target. The following example shows a save command that uses multiple directives to save one file—DISK:[TEST]MYFILE.TXT;1—that exists in a directory of many files. You could also accomplish this by specifying the full file specification in the save command line.
34 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
nsrsave -s server -f - DISK:[TEST] <<"disk:[test]">> always: myfile.txt;1 skip: *.*;* Ctrl-z In the preceding example:
◆ The -f option indicates that the next parameter is the name of a file containing directives.
◆ The hyphen (-) following the -f option indicates that directives will follow on the command line, one record at a time.
◆ The always directive instructs the save program to save MYFILE.TXT;1.
◆ The skip directive indicates that all other files in the directory can be skipped.
Note: The file specified by the preceding always directive has precedence over those specified by the skip directive.
The next example expands upon the previous one and uses the OpenVMS-specific directive nolock, causing the save program to save MYFILE.TXT;1 even if that file is open by another process:
nsrsave -s server -f - DISK:[TEST] <<"disk:[test]">> always: myfile.txt;1 skip: *.*;* nolock: *.*;* Directives and ASMs supported for use on OpenVMS
This section describes directives and ASMs, listed in alphabetical order, which are supported for use with the NetWorker software for OpenVMS: These directives can be used on the save command line, in local directive files on the client, or in directive resources on the NetWorker server unless the individual directive descriptions state otherwise. aes directive
When included in a global directive that is associated with a Client resource, the aes directive causes the save program to apply 256-bit data encryption to the associated backup data.
The syntax for the aes directive is as follows:
[+]aes: file-name
This example causes save to encrypt all associated backup data:
<<"SYS$SYSDEVICE:">> +AES: *.*;*
Directives and ASMs supported for use on OpenVMS 35 Directives
You can define the NSR$AES_NOTICE logical name to have a message added to the daemon log file when data is being encrypted (during a save) or decrypted (during a recover). The respective messages are as follows:
save: Encrypting data on this save recover: Decrypting data on this recover
The Dell EMC NetWorker Administration Guide provides more information on implementing encryption with the aes ASM. always directive
The always directive causes the save program to back up a file regardless of its backup status. For example, if the change time of the file indicates that it does not need to be saved during an incremental backup, the always directive causes it to be saved anyway. This directive can be used to ensure that important client files that change constantly are always backed up. The syntax for the always directive is as follows:
[+]always: file-name An example of an always directive is:
<<"sys$sysdevice:[db]">> always: my_database.dat;* The always directive can be combined with the null directive to save only specific files. See “The null directive” on page 39 for an example. asm directive
The save program for NetWorker OpenVMS clients uses the asm directive by default. It does not need to be specified. This default directive causes the NetWorker save program to behave as follows:
◆ Honor all OpenVMS file header characteristics.
◆ Save the headers of any shelved file without causing that file to become unshelved.
◆ Save all OpenVMS ACL information associated with a file.
◆ Save alias files by associating an index entry with the primary file without duplicating the saved data.
◆ Provide proper file locking during the save to prevent inconsistent backup copies of saved files.
◆ Create directory structures stored in the client index on the server, which can be displayed by the recover or nwrecover browser at a later time.
◆ Consider any specified time parameter for performing incremental saves or the various level saves. Only unique circumstances would require the use of the asm directive. For an example, see “The null directive” on page 39.
36 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
The syntax for the asm directive is as follows:
[+]asm: file-name An example of an asm directive is as follows:
<<"/">> +ASM: *.EXE;* +NULL: *.*;* The root directory (/) is specified as the directory specification to indicate that this directive is a client-wide directive and applies equally to all devices. This directive saves all executable files (.EXE) and does not save any other type of file. The default asm save is applied to all executable files.
The compressasm directive
The compressasm directive causes the save program to perform LZ compression on file contents while saving files to the server system. Use of this directive on systems where there is limited network bandwidth or limited NetWorker media but relatively large client CPU processing power can improve save efficiency. The syntax for the compressasm directive is as follows:
[+]compressasm: file-name An example of a compressasm directive is as follows:
<<"SYS$SYSDEVICE:[000000]">> +COMPRESSASM: *.*;* This directive causes save to compress all files on the system disk. Use of this directive with the rawasm directive is not supported. “Using rawasm with compression” on page 41 explains how to apply compression during a physical disk backup.
The copy_alias directive (OpenVMS-specific)
The copy_alias directive causes the save program to make a copy of any alias files. Instead of saving the file as an alias directory entry in the NetWorker index, save converts the alias attributes of the file to those of a regular file with the alias name. Further, upon recovery, an alias file saved with this directive loses its alias characteristics and is recovered as a regular file. Like all OpenVMS-specific directives, copy_alias has no precedence. It must be preceded by a directory specification and takes a file specification as an argument. The syntax for the copy_alias directive is as follows:
[+] copy_alias: file-name The following example shows how to save all files on the system disk without regard to their alias characteristic. This behavior is similar to what OpenVMS backup does by default for file-by-file backup operations:
<<"sys$sysdevice:[000000]">> +copy_alias: *.*;*
Directives and ASMs supported for use on OpenVMS 37 Directives
For additional information on the copy_alias directive, see “Saving and recovering an OpenVMS system disk” on page 66.
The ignobackup directive (OpenVMS-specific)
The ignobackup directive causes the save program to ignore the /NOBACKUP OpenVMS file attribute and back up the contents of these files. Files such as PAGEFILE.SYS are marked /NOBACKUP. Like all the OpenVMS-specific directives, ignobackup has no precedence. It must be preceded by a directory specification and takes a file specification as an argument. The syntax for the ignobackup directive is as follows:
[+]ignobackup: file.ext;ver The following example shows how to save and compress all of the files on the system disk, including those marked /NOBACKUP:
<<"sys$sysdevice:[000000]">> +ignobackup: *.*;* +compressasm: *.*;*
The logasm directive
The logasm directive prevents the save program from issuing a warning message if a file changes size during a save operation. Under normal circumstances, you would not need to specify this ASM because files cannot change size during a normal backup. However, when the nolock directive is in effect, a file being saved could be extended by another process. Use of the logasm directive prevents the warning message from occurring during these circumstances. The syntax of the logasm directive is as follows:
[+]logasm: file-name An example of the use of the logasm directive follows:
<<"DISK$USER1:[SMITH.LOG_FILES]">> LOGASM: *.LOG;* This example uses the logasm directive to save all of the files in DISK$USER1:[SMITH.LOG_FILES] and suppress warning messages for any .LOG files that change size during the save operation.
The nolock directive (OpenVMS-specific)
The nolock directive allows the save program to save open files by bypassing file locks during the save. By default, the NetWorker client on OpenVMS does not back up files that are open (and therefore "locked") by another process when read sharing is not enabled. Like all OpenVMS-specific directives, the nolock directive has no precedence. It must be preceded by a directory specification and takes a file specification as an argument. The following shows the syntax for the nolock directive:
[+]nolock: file.ext;ver
38 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
The following example shows how to save all open files and ignore file size changes for .LOG files:
<<"sys$sysdevice:[000000]">> +logasm: *.log;* +nolock: *.*;*
The null directive
The null directive causes save to perform no function with regard to the specified file. Because the null directive performs some operations related to internal directory structure consistency that are not performed by the skip directive, the null directive is the recommended method for instructing the save program to skip or ignore files during a save. The syntax for the null directive is as follows:
[+]null: file-name An example of a null directive is as follows:
<<"DISK$USER1:[SMITH.JUNK]">> +null: *.*;* This directive causes all files within the [SMITH.JUNK] directory and its subdirectories to be ignored during a save operation. The null directive can be combined with the always directive to save only a specific type of file. However, if the null directive specifies a file specification that matches the normal directory specifications, a problem can occur in that the save program may not scan the necessary directories to locate files matching subsequent directives. Under these circumstances, it is necessary to specify the asm directive to ensure that save scans all subdirectories. For example, to save all .DAT files in a specified directory but skip all other types of files, use a directive similar to the following:
<<"DISK:[DIRECTORY]">> +ASM: *.DIR;1 +ALWAYS: *.DAT;* +NULL: *.*;* In this example, the asm directive allows save to scan all subdirectories of [DIRECTORY]. Every file that matches the file specification, *.DAT;*, is saved; all other files are not processed.
The rawasm directive
The rawasm directive causes save to perform a physical disk backup: all physical blocks on the device are copied to a NetWorker save set. Any file structure that is present on the device is ignored. The save set is named with the physical device name and resides in the NetWorker index under root (/). The syntax for the rawasm directive on OpenVMS is as follows:
<<"/">> [+]rawasm: "device-name:"
Directives and ASMs supported for use on OpenVMS 39 Directives
where "device-name:" is the name of the device being backed up.
A device-name is required and must be a valid OpenVMS physical device name. It must also be enclosed in quotation marks (" ") and terminated with a colon (:). For example:
<<"/">> rawasm: "FLYER$DKB200:"
Note: Specify the same device name as the one specified in the save command line to avoid confusion.
While other NetWorker client platforms may allow you to specify an optional size argument (-L) with the rawasm directive to back up a portion of a specified device, this argument is ignored on OpenVMS. You cannot back up less than the entire disk device. To force save to use the rawasm directive, do all of the following:
◆ Specify a device name as the backup target (or path) in the save command.
◆ Specify the same device name in the rawasm directive.
◆ Specify the use of the rawasm directive by using the -f option in the save command line. You can use a filename argument to identify the name of the file that contains the rawasm directive or use the optional - (hyphen) argument to indicate that the directive will be supplied by the SYS$INPUT device rather than a separate file. The examples that follow use the latter method (-f -) because it allows you to view the entire save command and rawasm directive.
Note: Do not include the rawasm directive in a local .NSR file. This method is not supported for physical backups on OpenVMS. If you use a separate file for the rawasm directive, you must specify the name of the file with the -f option in the save command line.
If you specify a device as the backup target in your save command and fail to specify the rawasm directive, the save program will attempt to perform a normal, file-system-oriented backup. The save program interprets the specified device as a partial directory specification, appends the user's current default directory, and attempts to back up the resulting directory path. In the following example, the rawasm algorithm is used to back up device ITAN$LDA6: to the NetWorker server:
nsrsave -s nw_server -f - lda6: <<"/">> rawasm: "itan$lda6:" Ctrl-z ITAN$LDA6: /
save: ITAN$LDA6: 257 KB 00:00:03 2 files The save program attempts to match the device specified on the command line as the backup target with the device specified in the rawasm directive. In this example, itan$lda6: and lda6: resolve to the same physical device name, ITAN$LDA6:, which is then used for the save set name. The save program lists two files as being saved: ITAN$LDA6:, which is the new save set, and /, which is the root of the NetWorker index structure.
40 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
Using rawasm with volume sets When the rawasm directive is used to back up an OpenVMS bound volume set, the save program processes the volume set as a very large single volume. The resulting save set can only be restored to a volume set of identical configuration. For example, if you save a volume set composed of four relative volumes (RVNs), you must provide four devices of equal or greater size when recovering the volume set. The save program records the resulting save set as a single file by using the physical device of the first volume in the set, which is RVN 1. During recovery, the recover program requires that you provide the same number of devices as originally saved, and that each device be the same size or larger than the original. To recover a volume set to its original locations, you can omit the recover destination. The recover program recovers to the original location by default. The next example shows the use of rawasm to save a volume set:
nsrsave -s cider -f - itan$lda4: <<"/">> rawasm: "itan$lda4:" Ctrl-z ITAN$LDA4: ITAN$LDA5: ITAN$LDA6: / save: ITAN$LDA4: 6514 KB 00:00:03 2 files This example is very similar to the previous one in which a single volume was saved. A notable difference is that the save program prints out the additional RVNs as they are saved. This is purely informational to indicate that they are part of the save set. These RVNs cannot be restored individually.
Using rawasm with compression To instruct the save program to compress the data that is being backed up during a physical disk backup, define the following logical name to any value: NSR$RAWASM_COMPRESS For a manual (client-initiated) backup, define this logical name prior to executing the save command with the rawasm directive, and then deassign it afterwards. For server-initiated backups, predefine NSR$RAWASM_COMPRESS as a systemwide logical name (/SYSTEM). You can use pre- and postprocessing to define and deassign this logical name. The logical name definition is needed only during the save. The recover program will use the appropriate decompression method when recovering the save set.
Important considerations for physical backups By default, the save program will attempt to flush all device caches and lock the mounted volume against new allocations during a physical disk backup to produce the most consistent physical backup possible. (This behavior can be modified with the NSR$RAWASM_NOFLUSH and NSR$RAWASM_NOLOCK logical names, as described in Appendix A, “Logical Names.”) The save program cannot guarantee consistent backup copies when the rawasm directive is used.
Directives and ASMs supported for use on OpenVMS 41 Directives
To ensure a consistent backup, you must ensure that the device being backed up is not being accessed and that device caching is disabled. You can accomplish this by:
◆ Mounting the device /FOREIGN ◆ Mounting the device /NOWRITE ◆ Ensuring that the device will not be written to by any process during the backup To ensure consistent backup copies when doing a physical backup of a volume set, the recommended method is to dismount the volume set and then mount each RVN /FOREIGN. Use the rawasm directive to back up each volume separately. Keep track of which backups are associated with your volume set. To recover the volume set, recover each RVN in the set, and then mount and bind them into their original volume set.
Note: When recovering a physical backup, the target output volume must be mounted /FOREIGN.
For more information on using the rawasm directive, see “Performing a physical disk backup and recovery” on page 69.
The record directive (OpenVMS-specific)
The record directive has been deprecated in NetWorker V6.0.1-D and later. Specifying it has no effect, but will not generate an error. In this way, existing directive statements that use the record directive do not need to be modified immediately.
The norecord directive (OpenVMS-specific)
The norecord directive prevents the save program from writing the backup time of the file into the file’s header. By default, save updates the file header with the backup time, thus allowing you to view the most recent backup time for files when listing files with the OpenVMS DIRECTORY command. Like all of the OpenVMS-specific directives, the norecord directive has no precedence. It must be preceded by a directory specification and takes a file specification as an argument. The following shows the syntax for the norecord directive:
[+]norecord: file.ext;ver The example that follows shows how to compress all files on the entire client and avoid recording the backup dates on all .DAT files that are saved (and compressed):
<<"[000000]">> +norecord: *.dat;* +compressasm: *.*;* Because this directive does not specify a disk, the NetWorker software uses the disk that is currently being processed. You can use a common directive for multiple disks by omitting the disk from the directive. You could also use the root specification, <"/"> in place of <<"[000000]">> in the preceding example to achieve the same results. Because the OpenVMS-specific directives have no precedence, the compressasm directive in this example affects all files.
42 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
The skip directive
The skip directive directs the save program to skip any file that matches the directory and filename portion of the directive. The skip directive is implemented within the directory-walking function of the save program. When a file that matches the skip directive is found, it is discarded and save moves on to the next file in the directory. This behavior is unlike that of the null directive, which allows the save program to process the filename for internal directory structure consistency. For this reason, the null directive is the recommended method for skipping files during a save of client data. The syntax for the skip directive is as follows:
[+]skip: file-name Note that the skip directive follows a disk and directory specification. It also allows recursive application if you precede the directive with a plus sign (+). The following example specifies the root directory and indicates that all files on all volumes of the client are to be skipped:
<<"/">> +skip: *.*;* You may want to use this directive when troubleshooting client nsrexecd problems that occur only during server-initiated saves. While all of the save programs are started and all communications between the client nsrexecd and the NetWorker server occur, this skip directive causes no data to be saved. This allows you to verify the client installation by performing a real, server-initiated save without actually backing up data.
The skip_alias directive (OpenVMS-specific)
The skip_alias directive causes the save program to skip all alias files and directories as if they do not exist. Because the save program’s default behavior saves an alias only as a reference to its primary file, there is no penalty in allowing save to back up alias files. Therefore, you may use the skip_alias directive only when you need to prevent all alias information for a particular file system from being saved. The syntax for the skip_alias directive is as follows:
[+]skip_alias: file.ext;ver The following example shows how to skip all aliases, back up open files, and compress all files on the entire client:
<<"/">> +skip_alias: *.*;* +nolock: *.*;* +compressasm: *.*;*
The skip_shelved directive (OpenVMS-specific)
The skip_shelved directive causes the save program to bypass any file shelved with the OpenVMS HSM software or with any shelving software that uses the same file header semantics as OpenVMS HSM. By default, the save program saves only the file header of a shelved file and does not cause the file to become unshelved.
Directives and ASMs supported for use on OpenVMS 43 Directives
Note: In general, use of this directive is not recommended because the file header of a shelved file should be protected with a backup regimen.
The syntax of the skip_shelved directive is as follows:
[+] skip_shelved: file.ext;ver The following example shows how to skip all shelved flies on the client and always save files in the [IMPORTANT] directory:
<<"[000000]">> +skip_shelved: *.*;* <<"DISK:[IMPORTANT]">> always: *.*;* Because the skip_shelved directive has no precedence, it does not prevent the always directive from ensuring that DISK:[IMPORTANT]*.*;* is always backed up.
The swapasm directive
When the swapasm directive is used, save copies only the headers of the specified files but saves no file data. Files such as system paging and swapping files are candidates for swapasm because the contents of these files is meaningless during a restore, but their presence and their file attributes (size, and so forth) are important. Normally, use of the swapasm directive is not required on OpenVMS systems. The /NOBACKUP file attribute is normally set for OpenVMS page and swap files. When this attribute is present, the save program automatically saves only the file header. No special directives or action is required. However, if there are other files of this type on the system and you do not want to change their backup attributes, you can use the swapasm directive to save them as though they were marked /NOBACKUP. The syntax of the swapasm directive is as follows:
[+]swapasm: file-name The following shows an example of a swapasm directive:
<<"DISK$SWAPFILES:[000000...]">> +SWAPASM: *.*;* In this example, the file header information for all files in DISK$SWAPFILES is saved but no file data is saved. During recovery, the files are restored with all their file attributes, such as file size, type, and so forth. However, they contain no valid file data after the restore.
The unshelve directive (OpenVMS-specific)
The unshelve directive modifies the default behavior of the save program so that any shelved file is unshelved before being saved. This directive is useful if you want to ensure that all file data from a device that has shelved files resides on the NetWorker server. Another way to accomplish this would be to use HSM software to manually unshelve the files before initiating the save program. In either case, you must verify that the device has sufficient space to accommodate the unshelved files.
44 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Directives
Like all OpenVMS-specific directives, unshelve has no precedence. It must be preceded by a directory specification, and takes a file specification as an argument. The following shows the syntax for the unshelve directive:
[+]unshelve: file.ext;ver The example that follows shows how to unshelve all files on the entire client before backing them up with compression:
<<"/">> + unshelve: *.*;* + compressasm: *.*;*
The xlateasm directive
The xlateasm directive provides file data encryption. Data transferred from the client to the server is encrypted using a rudimentary algorithm. The data stream from client to server (and from server to client during a restore) is not human readable.
The algorithm used does not provide protection against any skilled attempt at decrypting. Do not rely on it to provide data security for sensitive data that is being transported across public networks.
The syntax for the xlateasm directive is as follows:
[+]xlateasm: file-name The following example shows the use of the xlateasm directive:
<<"DISK$USER1:[SMITH.PRIVATE]">> +XLATEASM: *.*;* This directive causes save to encrypt the file data for all files in the [SMITH.PRIVATE] directory and all of its subdirectories. Creating directive files on the OpenVMS client
Directive files are simply containers for directives. They contain directives that use the syntax described previously in this chapter. The save program processes the directive file when scanning a volume during a normal backup. (When a physical back is done with the rawasm directive, volumes are not scanned.) Nonprivileged users can create client-specific directives within their own directories, which allows them to affect the behavior of the save program. No access to the NetWorker server is required. Directive files are normal text files that can be created with a text editor. Use the following guidelines when creating a directive file on an OpenVMS client:
◆ The directive file must have no filename—only a file extension of NSR. For example: DISK$TEST:[000000].NSR;1
◆ The directive file can reside in any directory on the target volume. Its placement depends upon when, during the directory scan, the directive should become active. The save program discovers directive files as it enters a directory from the directory
Creating directive files on the OpenVMS client 45 Directives
level above. Therefore, a directive file can supersede, add to, or abolish directives from above the current directory in the directory hierarchy. The new settings remain in effect until the save scan returns to the directory above the one containing the directive file.
◆ To avoid ambiguity, only one version of a directive file (.NSR) should exist in any single directory.
◆ Comments can be included in directive files. Any text following a pound sign (#) is treated as a comment. The following is an example of a directive file that selectively turns on file compression for a particular directory:
create disk$user1:[smith.realbigfiles].nsr;1 <<"disk$user1:[smith.realbigfiles]">> compressasm: *.*;* Ctrl-z When the save file scan gets to the specified directory, the compressasm directive is invoked for all files matching the given filename (*.*;*). Recommended directives for the system disk
Use the nolock directive on system disks to enable the backup of files that were opened without read share but do not change, such as some OpenVMS-installed files. An example of a nolock directive for use on the system disk is as follows:
<<"SYS$SYSDEVICE:[000000]">> +NOLOCK: *.*;* Define a server-based directive like the one shown in the next example to back up open files on the system disk, skip all .LOG files on all client volumes, and compress files during a save on all client volumes:
<<"/">> +NULL: *.LOG;* +COMPRESSASM: *.*;* <<"SYS$SYSDEVICE:[000000]">> NOLOCK: *.*;* Directives shown in the preceding example cause the following behavior:
◆ The client will not save any files with the .LOG extension that are found on any client device.
◆ The client compresses all files on all client devices before sending them to the NetWorker server.
◆ The client saves open files found on the system device without regard to file locking. Note that files opened without read share on other volumes are not saved. The nolock directive used in this example applies only to the SYS$SYSDEVICE: volume (which is always the system disk). For more information on saving an OpenVMS system disk, see “Saving and recovering an OpenVMS system disk” on page 66.
46 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide CHAPTER 4 Backup and Recovery Invisible Body Tag
This chapter covers these topics:
◆ Manual backups ...... 48 ◆ Recovering data ...... 54 ◆ Saving and recovering an OpenVMS system disk...... 66 ◆ Performing a physical disk backup and recovery...... 69
Backup and Recovery 47 Backup and Recovery
Manual backups
The NetWorker server backs up client data regularly using scheduled backups. Scheduled backups are the preferred backup method because the backup occurs automatically, and data can be recovered more easily. You can start a scheduled group backup at any time by starting the associated policy immediately, as described in the Dell EMC NetWorker Administration Guide. By comparison, manual backups can be used to quickly back up a few files, specific directories, or a file system to the NetWorker server. This data is more difficult to recover, however, because manual backups do not generate bootstrap files.
Performing a manual backup on OpenVMS
To start a manual backup from an OpenVMS client machine, you can use either of the following methods:
Note: When running NetWorker in a cluster environment, higher performance is achieved when you start save and recover processes from a storage node as opposed to a client node. This is due to the way in which shared memory sections are used across cluster nodes.
◆ Enter the save command at the DCL prompt with the appropriate options, arguments, and optional directives. See “The save command” on page 49 for more information and examples.
◆ Run the nwbackup program and make the appropriate selections in the graphical user interface. See “Performing a manual backup with the nwbackup program” on page 54 for instructions. To perform a manual physical disk backup, you must use the save command, as described in “Performing a physical disk backup and recovery” on page 69. You may also want to use the save command when backing up an OpenVMS system disk, as described in “Saving and recovering an OpenVMS system disk” on page 66. During a backup, you can monitor messages using the nsrwatch program as described in “The nsrwatch command” on page 26. You can also monitor backups from the NetWorker Management Console. The Dell EMC NetWorker Administration Guide explains how to use this interface.
Saving and recovering directories
To be saved as a directory, a file must meet both of the following conditions:
◆ It must have a .DIR;1 type and version.
◆ The directory bit must be set.
If either condition is not met, the NetWorker software saves the file as a regular file that can be recovered.
Note: None of the files that reside in that directory are saved.
48 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
When saving or recovering a file that meets only one of the required conditions for directories, the NetWorker software issues a "size grew during save" warning. This applies to the following:
◆ A file that has the directory bit set but does not have the required .DIR;1 extension.
◆ A directory that has a version other than 1 (for example, TEST.DIR;2).
Directories with the proper file type and version but no file name (.DIR;1 for example) are saved as regular files that cannot be recovered.
The save command The save command can be used to back up entire file systems, directories, or individual files to the NetWorker server. Format
nsrsave ["-BEiKLnquSVv"][-s server][-c client]["-N" name] [-e expiration][-f dirfile][-b pool]["-F" file] ["-I" inputfile][-g group][-l level][-t date] [-m masquerade][-w browse_time] [-y retention_time] ["-W" width]["-D" debug_level][path...]
Note: All uppercase options must be enclosed in quotation marks (" ") to retain their case. Arguments that contain uppercase letters, embedded spaces, or punctuation must also be enclosed in quotation marks.
Arguments The save command takes one or more optional path arguments, separated by spaces. This argument specifies the path to the directory in which save should start its scan for backup candidates. If no path is specified in the save command, all files in the issuing process’s current default directory, its subdirectories, and the directories themselves are saved. Directives You can use directives to instruct NetWorker to process files in a special way (compressed or skipped, for example) during the save. The save program reads and applies local directive files (named .NSR) as they are encountered in each directory. You can also enter directives in the save command line or specify a particular directive file in the save command line. Chapter 3, “Directives” describes the directives available for use with the NetWorker software for OpenVMS. To specify a single file or selected files from within a directory as the target of a save operation, use a directive in your save command as shown in Example 5 on page 54. To perform a physical disk backup, use the rawasm directive as described in “Performing a physical disk backup and recovery” on page 69.
Manual backups 49 Backup and Recovery
Options Table 4 on page 50 lists the valid options (in alphabetical order) for the save command.
Table 4 save command options (page 1 of 3)
Option Argument Description
-b backup pool (Backup pool) Specifies the name of the destination pool for the name save sets.
-c client name (Client) Specifies the name of the client computer on which to start the save session. This option is useful on clients with multiple network interfaces and multiple hostnames. It can also be used on a cluster when performing manual backups or in specifying a nondefault backup command for scheduled saves.
-e date (Expiration date) Sets the date when this save set expires and becomes recyclable on the NetWorker server. See “Valid date/time formats for NetWorker commands” on page 22 for a list of valid date formats.
-f directive Specifies the name of the directive file to process before save filename begins scanning the specified file system. or Specify a hyphen (-) rather than a filename to instruct save to - (hyphen) read the directives from the command line (SYS$INPUT). The save program interprets each subsequent record (that is, each line, terminated by a carriage return) as a line in the directive until Ctrl-z is pressed, which terminates the directive.
Note: Do not allow the hyphen argument to be the last character on the command line. Otherwise, the OpenVMS operating system will interpret it as a command continuation character.
-g group name (Group) Denotes the group of the save. The NetWorker server uses this value to select the specific media pool.
-i none (Ignore) Instructs the save program to ignore any directive files found on the client’s online file system.
-l full, 1-9, incr (Level of save) The level option is ignored for manual saves. If specified, the save is performed at level adhoc.
Tip: to perform a manual incremental command, specify the -t option instead, which will backup files created since the specified time.
-m text string (Masquerade) Specifies an alternate string to use on the save summary line instead of save. For example: store: SYS$SYSDEVICE:[SMITH.TMP] 5 KB 00:00:10 4 files instead of: save: SYS$SYSDEVICE:[SMITH.TMP] 5 KB 00:00:18 4 files -n none (No save) Prevents the save program from sending any data to the server but instructs it to generate an estimate of the amount of data that would be sent during this save if an actual save was performed.
-q none (Quiet mode) Turns off verbose mode and prevents save from displaying the list of files being saved.
50 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
Table 4 save command options (page 2 of 3)
Option Argument Description
-s server name (Server) Specifies the name of the NetWorker server to use for the save. Include this option in all save commands.
-t date Specifies the date to be used by the save program when determining which files need to be backed up. See “Valid date/time formats for NetWorker commands” on page 22 for a list of valid date formats.
-u none Causes save to exit when an error occurs. By default, the save program treats errors as warnings and continues to save the rest of the files in the backup. This option is not recommended for general use, although it can be useful when a group of files needs to be backed up as a set.
-v none (Verbose mode) Causes the save program to display additional information about the save operation. Use of this option is helpful when troubleshooting directives because the directive parser outputs information in verbose mode.
-w browse time Sets the date or time after which this save set will no longer be browsable. By default, the server determines the browse date for the save set based on the browse policies in effect. This option allows you to override the existing policies on a save-by-save basis. See “Valid date/time formats for NetWorker commands” on page 22 for a list of valid formats.
-y date Sets the date (in nsr_getdate format) when the saved data will become recyclable. See “Valid date/time formats for NetWorker commands” on page 22 for a list of valid date formats. The special value forever is used to indicate that a volume that never expires (that is, an archive volume) must be used. By default, the server determines this date for the save set based on the retention policies in effect. This option allows overriding the existing policies on a save-by-save basis.
-B none Forces a save of all connecting directory information. This option causes the save program to walk up the directory tree and refresh all browser structures from the point of the save to the OpenVMS root directory (/).
-D level of (Debug level) Specifies the level of debugging information that debugging will be output by the save program. The debug option accepts (1-15) numeric arguments of 1 to 15, with 15 producing the greatest amount of information.
-E none (Estimate) Causes the save program to estimate the amount of data that will be saved before actually performing the save.
-F file Instructs the save program to save only those files whose modification time is later than the modification time of the specified file.
-I input filename (Input file) Specifies the name of a file that contains a list of the paths to save. Each line in the file must contain only a single directory path. These directories will be saved in addition to those specified by the path argument on the save command line. If no path is specified on the command line, then only the paths specified in this file will be saved.
-K none Causes the save program to not build any connecting directory index entries.
Manual backups 51 Backup and Recovery
Table 4 save command options (page 3 of 3)
Option Argument Description
-L[L] none (Local) Prevents remote file system saves by forcing saves to be performed from the local NetWorker client. The -L option is irrelevant on OpenVMS clients because remote saves are not supported. However, the -LL option may be useful. It causes save to display a final status line indicating the time at which the save command completed.
-N save set name (Name of save set) Specifies an arbitrary name for the save set. By default, the highest level disk:[directory] path that is common to all files being saved is used as the save set name. The -N option allows you to override the default save set name. IMPORTANT: If you assign a save set name that does not represent the most common path (MCP) to the files within the save set and then subsequently attempt to recover files from this save set by using save set recover mode, the recover program may exhibit unexpected behavior. To ensure that only expected files are recovered, you must first define the NSR$RECOVER_MCP logical name to identify the MCP to the files in the save set being recovered. For more information, see “Save set recover mode” on page 62 and the definition of the NSR$RECOVER_MCP logical name in Appendix A, “Logical Names.”
-S none Specifies that this data can only be recovered with the save set recover method. No index entries are created; therefore, the save set will not be browsable.
-V none Prevents the OFC mechanism from creating a point-in-time copy of the source volume. This option is included for compatibility with NetWorker servers running on Microsoft Windows NT.
-W number of (Width) Specifies the width, in characters, of the summary characters output.
Examples Examples of the save command follow.
Example 1 Backing up the current default directory
The save command in this example backs up the current default directory and all subdirectories. Because the optional path argument is not supplied, all of user James’s files are saved.
show default SYS$SYSDEVICE:[JAMES] nsrsave -s server DISK$ALPHASYS:[JAMES]CD.EXE;1 DISK$ALPHASYS:[JAMES.LOGFILES]FIRST.LOG;1 DISK$ALPHASYS:[JAMES.LOGFILES]FOURTH.LOG;1 DISK$ALPHASYS:[JAMES.LOGFILES]SECOND.LOG;1 DISK$ALPHASYS:[JAMES.LOGFILES]THIRD.LOG;1 DISK$ALPHASYS:[JAMES]LOGFILES.DIR;1 DISK$ALPHASYS:[JAMES]LOGIN.COM;2 DISK$ALPHASYS:[JAMES]LOGIN.COM;1 DISK$ALPHASYS:[JAMES]LSEINI.LSE;3 DISK$ALPHASYS:[000000]000000.DIR;1 / save: SYS$SYSDEVICE:[JAMES] 19 KB 00:00:11 11 files
52 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
Example 2 Omitting directories from a save
The save command in this example includes an explicit path argument (SYS$SYSDEVICE:[JAMES]) and a null directive to omit all files in the [.LOGFILES] subdirectory. nsrsave -s server -f - SYS$SYSDEVICE:[JAMES] <<"SYS$SYSDEVICE:[JAMES.LOGFILES]">> null: *.*;* Ctrl-z DISK$ALPHASYS:[JAMES]CD.EXE;1 DISK$ALPHASYS:[JAMES]LOGFILES.DIR;1 DISK$ALPHASYS:[JAMES]LOGIN.COM;2 DISK$ALPHASYS:[JAMES]LOGIN.COM;1 DISK$ALPHASYS:[JAMES]LSEINI.LSE;3 DISK$ALPHASYS:[000000]000000.DIR;1 / save: SYS$SYSDEVICE:[JAMES] 18 KB 00:00:03 7 files
Example 3 Doing a trial backup in which no data is saved
This save command in this example uses the –n option, which causes the save program to estimate the size of the data to be saved but not save any actual data. nsrsave -s server -f - -n SYS$SYSDEVICE:[JAMES] <<"SYS$SYSDEVICE:[JAMES.LOGFILES]">> null: *.*;* Ctrl-z DISK$ALPHASYS:[JAMES]CD.EXE;1 DISK$ALPHASYS:[JAMES]LOGFILES.DIR;1 DISK$ALPHASYS:[JAMES]LOGIN.COM;2 DISK$ALPHASYS:[JAMES]LOGIN.COM;1 DISK$ALPHASYS:[JAMES]LSEINI.LSE;3 save: SYS$SYSDEVICE:[JAMES] 5 records 2 KB header 14 KB data save: SYS$SYSDEVICE:[JAMES] 16 KB estimated Notice that the estimate does not include the connecting directory phase of the save, which adds another 2 KB to the estimate in this case.
Example 4 Backing up specific file types only
This example shows how to back up only certain types of files across an entire disk. In this case, all files that match the file specification *.dat;* are saved. nsrsave -s server -f - DISK$TEST:[000000] <<"disk$test:[000000]">> asm: *.dir;1 always: *.dat;* null: *.*;* Ctrl-z
Manual backups 53 Backup and Recovery
The asm: *.dir;1 portion of the directive must be specified to ensure that save scans all directories. Otherwise, the directory name matches the null specification and the save program does not scan that directory. This feature allows you to skip entire directories completely without scanning them. However, you must include the asm: *.dir;1 statement when you want the save program to scan all directories.
Example 5 Backing up a single file
This example shows how to back up a single file from the top-level [JAMES] directory.
nsrsave -s cider -f - SYS$SYSDEVICE:[JAMES] <<"sys$sysdevice:[james]">> always: cd.exe;* asm:*.dir;1 +null: *.*;* Ctrl-z DISK$ALPHASYS:[JAMES]CD.EXE;1 DISK$ALPHASYS:[000000]000000.DIR;1 /
save: SYS$SYSDEVICE:[JAMES] 10 KB 00:00:03 3 files In this case, all files were ignored except the specified file, CD.EXE;1. The additional files shown in the example are listed because of the connecting directories phase of the save, which saved two additional files, DISK$ALPHASYS:[000000]000000.DIR;1 and the root (/).
Performing a manual backup with the nwbackup program The nwbackup program provides a graphical representation of the client’s file system. Physical backups, which use the rawasm directive, are not supported. You must use the save command to perform this type of backup on OpenVMS, as described in “Performing an ad hoc physical disk backup” on page 69. To perform a manual backup with the nwbackup program: 5. Start the nwbackup program by typing the nwbackup command at the DCL prompt. To specify a particular NetWorker server, include the -s option. For example:
nwbackup -s server 6. In the nwbackup window, select the directories and/or files to be backed up and then select Mark from the Mark menu. To clear an item, select Unmark from the Mark menu. 7. Click Start to begin the manual backup. When the backup is completed, the nwbackup program displays a message similar to the following:
Backup completion time: 2-15-06 3:27p. For more information, refer to the nwbackup program’s online help Recovering data
To retrieve a backed up file from the NetWorker server and restore it to its original or a specified destination, use either of the following methods:
54 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
◆ Type the recover command at the DCL prompt with the appropriate options and arguments. See “The recover command” on page 55 for details.
◆ Run the nwrecover program and select the appropriate file or data items in the graphical user interface. See “Recovering files with the nwrecover program” on page 64 for instructions. You can designate individual files, specific directories, or an entire file system for recovery.
Note: When specifying an extended file specification in a NetWorker command at the DCL prompt, type it in the appropriate case and enclose it in quotation marks. “Extended file specifications and ODS-5 volumes” on page 16 provides details.
When no destination is specified, the NetWorker server attempts to recover data to its original location and uses the original file and directory names. You can alternately recover data to a different disk, directory, or both as explained in “Relocating recovered data” on page 65. If another file or directory with the same name is present in the recover destination, a file recovery conflict occurs. You can instruct the NetWorker software to respond to these conflicts automatically or on a file-by-file basis by using the -i option in the recover command. Additional information pertaining to specific recovery types is provided in the following sections:
◆ “Recovering an OpenVMS system disk” on page 68
◆ “Recovering a physical disk backup” on page 70 The recover command
The recover command retrieves backed-up files from the NetWorker server and restores them to their original or a specified destination. This command has four modes of operation:
◆ Browser mode — The recover program queries the client file index on the NetWorker server for files from the current (default) or directory or one that you specify and allows you to browse backed-up files on the specified NetWorker server. This is an interactive command line interface. “Browser mode” on page 58 provides more details and examples.
◆ Automatic mode — You supply all the information required to execute the recover. No browsing utility is provided. “Automatic mode” on page 61 describes restrictions and shows an example of this mode.
◆ Save set recover mode — The recover program retrieves all of the files within a specified save set that match the specified file specification. “Save set recover mode” on page 62 provides more details and an example.
◆ Directed recover mode — The recover program queries the client file index on the NetWorker server for files from the current (default) directory or one that you specify, and allows you to browse backed-up files on the specified NetWorker server. The files
Recovering data 55 Backup and Recovery
are recovered to a remote machine that you specify. This is an interactive command line interface. See “Directed recover mode” on page 63 for more details and examples. Format The format for each mode of the recover command is as follows:
◆ Browser mode:
nsrrecover [-fnqv][-c client][-d destination]["-D" debug_level] [-i {nNyYrR}][-t date][-s server] [directory-specification]
◆ Automatic mode:
nsrrecover -a [-fnqv][-c client][-d destination]["-D" debug_level] [-i {nNyYrR}][-t date][-s server] file-specification
◆ Save set recover mode:
nsrrecover [-fnqv][-d destination]["-D" debug_level][-i {nNyYrR}] [-t date] -s server "-S" ssid[/cloneid] ["-S" ssid[/cloneid]]... file-specification
◆ Directed recover mode:
nsrrecover [-qv] -f | -i {NYR} -R recover-target [-c client] [-d destination][-x index-namespace][-t date] [-s server][directory-specification]
Note: All uppercase options must be enclosed in quotation marks (" ") to retain their case. Arguments that contain uppercase letters, embedded spaces, punctuation, or extended file specifications must also be enclosed in quotation marks.
If you do not include the -a (automatic), "-S" (save set ID), or "-R" (redirect) option in the recover command, browser mode is used by default. Arguments The recover command takes the following arguments depending upon the mode being used:
◆ [directory-specification] — (Optional) Used in interactive mode (browser and directed recover modes) to determine the directory from which to begin browsing. Use of this argument prevents the browser from first attempting to look up the current default directory in the client file index on the NetWorker server. You can specify an explicit directory specification or a relative one ([.LOGFILES], for example)
◆ file-specification — (Required) Used by automatic and save set recover modes to identify the files or save sets to recover. Note the following guidelines when specifying the file-specification argument: • In automatic mode, specify an explicit file-specification. Enter the filename or filenames exactly as they would appear if you were to browse the file system. The use of wildcards is not supported in this mode.
56 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
• In save set recover mode, the file-specification identifies the save set to recover, and may include wildcards. Even the disk name portion of the file specification can be a wildcard. For example, *:[000000...]*.*;* is a valid file specification for save set recover mode and represents all files within the save set, regardless of their associated device.
Note: When using save set recover mode to recover files from a save set whose name does not represent the highest level disk:[directory] path common to all files within that save set, you must define the NSR$RECOVER_MCP logical before attempting to recover the files. See “Save set recover mode” on page 62 for more details.
Options Table 5 lists the valid options (in alphabetical order) for the recover command.
Table 5 recover command options (page 1 of 2)
Option Argument Description
-a none (Automatic) Instructs the recover program to use automatic mode when processing the recover command. No interactive browsing is supported in this mode.
-c client name (Client) Specifies the name of the client computer from which the save sets were originally saved. When you browse a directory that was saved by a different client, the browser shows files and directories that reflect the client that saved the files. You cannot use the –c option in conjunction with the "–S" option.
-d disk, (Destination) Specifies the destination disk and/or directory for directory, or recovered files. “Relocating recovered data” on page 65 explains how both the NetWorker software determines which disk or directory to use when (disk:[directo either of these values is omitted. ry]) When used to recover a save set that was created with the rawasm directive, this option accepts a device name as a valid argument.
-f none (Force overwrite) Causes recover to unconditionally overwrite any files that exist on the online volume with recovered files of the same name.
-i action to take (Initial overwrite response) Allows you to predefine the initial default when overwrite response when a filename conflict occurs. You can specify filename only one argument to this option. Valid arguments are: conflict • n = Do not overwrite the file. occurs • N = Do not overwrite any files. • y = Overwrite the file. • Y = Overwrite all files. • r = Rename the file. The OpenVMS client renames the file by creating a new version of it. • R = Rename all files. Only N, Y, and R are valid values for directed recovers. Remember to enclose uppercase arguments in quotation marks.
-n none (No recover) Prevents the recover program from creating any files or directories on the client. An estimate of required disk space for the data to be recovered is given in cases where the destination directory exists. However, if you instruct the recover program to relocate the data to a directory that does not yet exist, the directory is not created and no estimated disk space requirement is given.
Recovering data 57 Backup and Recovery
Table 5 recover command options (page 2 of 2)
Option Argument Description
-q none (Quiet mode) Turns off verbose mode, which recover uses by default, and prevents the recover program from displaying the names of files as they are recovered.
-s server name (Server) Specifies the name of the NetWorker server from which you are retrieving backed up files. This option is required for save set recover mode.
-t date Causes the recover program to display or recover files as of the specified date. This option cannot be used in conjunction with the "-S" option.
-v none (Verbose mode) Causes the recover program to display additional information about the recover operation.
-x index Instructs the recover program to browse/recover files in the specified namespace file index namespace. By default the backup namespace is used. The other recognized index namespace is archive. This argument is case-sensitive.
-D level of (Debug level) Specifies the level of debugging information that will be debugging output by the recover program. The debug option accepts numeric (1-15) arguments of 1 to 15, with 15 producing the greatest amount of information.
-I input (Input file) Specifies the name of a file that contains a list of file filename specifications to recover.
-R recover target Specifies the name of the remote machine to direct the recovery. This is used in conjunction with the -c option to specify browsing of another client's index. When the -R option is used, either the -f or the -i option must also be specified in order to instruct the recover target what to do when it is recovering existing files. Note that for directed recoveries, only the N, Y, and R values are valid with the -i option. Also note that the -a option is not supported with the -R option.
-S save set ID (Save set ID) Specifies the save set ID for the save set that is being (ssid) recovered. This value can be obtained from the NetWorker server. This option is required for save set recover mode.
Browser mode When you invoke the recover command in browser mode, the browser starts by querying the client file index on the NetWorker server for files from the default directory. If no matching files are found in the client file index, recover responds with a message similar to the one shown in the following example:
nsrrecover -s cider DISK$ALPHASYS:[SYS0.SYSMGR] not in index
58 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
Start browsing at the root (/) if you are unsure as to what has been backed up. You can change directory (cd) from there. To list the files in the current directory, use the dir command or the ls command, which presents output similar to that of the OpenVMS DIRECTORY command. Table 6 describes the valid commands for the recover browser mode.
Table 6 Recover browser commands (page 1 of 2)
Command Description
add [-q] [filename] Adds the current directory or the names of files or directories to the list of files to be recovered. Include the optional –q (quiet mode) option to suppress the display of intervening directories when adding a large number of files.
cd [directory] Changes the current default directory to the specified directory.
changetime [date] Displays the file system as it existed at the specified time. See “Valid date/time formats for NetWorker commands” on page 22 for a list of valid date/time formats.
delete [filename] Removes the specified directory or named files from the list of files to be recovered. If a directory is specified, that directory and all of its descendents are deleted from the list. The most expedient way to recover a majority of files from a directory is to add the directory to the recover list and then delete the unwanted files.
destination Displays the destination location for recovered files.
dir [/w] [filename...] Lists the files in the current directory or those that match the specified filename or directory. Files that are marked for recovery are not obvious in the output produced by this command. (They are marked with a plus sign (+) when listed in response to an ls command.) When the /w option is included, only directory names are listed.
exit and quit The exit and quit commands are synonymous. Both immediately terminate the recover program.
force Forces existing files to be overwritten if a filename conflict occurs during the recover.
help and ? Displays a summary of available commands for the recover browser.
list [-c|-l] Displays the list of files marked for recovery. If no arguments are specified, the recover list is displayed as a list of full path names, one per line, followed by a total count of the files to be recovered. The -c argument displays only the total count of files to be recovered. The -l argument generates a long format listing.
ls [filename...] Lists the files in the current directory or those that match the specified directory or filename. A plus sign (+) appears next to files that are marked for recovery. The browser ls command accepts many of the same arguments as the UNIX ls command. See the Dell EMC NetWorker Command Reference Guide for more information.
noforce Cancels the force command, which causes the recover program to prompt you each time a naming conflict arises.
pwd Prints the full pathname of the current directory.
recover Recovers the files in the recover list.
Recovering data 59 Backup and Recovery
Table 6 Recover browser commands (page 2 of 2)
Command Description
relocate {disk: | Changes the recover destination to the specified disk and/or directory. [directory] | “Relocating recovered data” on page 65 explains how the NetWorker disk:[directory]} software determines which disk or directory to use when either of these values is omitted.
spawn [command] Spawns a subprocess.
verbose Toggles the verbose setting, which provides more or less feedback during the recover process.
versions [filename] Instructs the browser to report on each version of the specified file.
volumes [filename] Prints a list of the volumes needed to recover the current set of files on the recover list.
Example 6 Using the recover command in browser mode
User Smith needs to recover selected files from various directories. A browser session is used to accomplish that task. Explanations for the numbered callouts that appear in parentheses throughout this example are provided in Table 7 on page 61.
nsrrecover -s cider recover_usr: No index was found for CATS$DKA100:[SYS0.SYSMGR]. The current working directory is /. (1) recover> dir 05/10/05 03:02 PM
60 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
2 file(s) marked for recovery recover> list DISK$USER12:[SMITH]LOGIN.COM;41 @ Wed Mar 7 08:12:10 2007 DISK$USER12:[SMITH.COMMAND_FILES]ADJUST_TIME.COM;16 @ Wed Mar 7 08:12:10 2007 2 file(s) marked for recovery recover> destination recover files into their original location recover> recover (5) recover_usr: Total estimated disk space needed for recover is 4 KB. Recovering 2 files into their original locations Volumes needed (all near-line): H15917 at rd=cats:CATS$MKA100: Requesting 2 file(s), this may take a while... DISK$USER12:[SMITH]LOGIN.COM;41 DISK$USER12:[SMITH.COMMAND_FILES]ADJUST_TIME.COM;16 Received 2 file(s) from NSR server `cider' Recover completion time: Fri Mar 9 08:25:14 2007 recover> exit
Table 7 Browsing example callouts
Callout Description
1 The nsrrecover command is used to start the recover program in browser mode. The recover program queries the specified NetWorker server for files in the user's current directory because no directory was specified in the command line. No files from this directory have been saved so recover sets the current directory to root (/). A dir command entered at the root directory reveals that there are five disks from this client that have files saved on the NetWorker server. CATS$DKC200: is a physical disk backup saved with the rawasm directive.
2 After changing directory (cd) to DISK$USER12:[000000] and locating the [SMITH] directory, the user changes directory (cd) again to DISK$USER12:[SMITH]. (Note that if this were an ODS-5 disk, any directory or file specifications would have to be typed in the appropriate case.) The ls command is used to list the files in the current directory. The list is similar to that of an OpenVMS DIRECTORY command.
3 The add command is used to select LOGIN.COM;41 for recovery. The version number of the file being marked for recovery is required unless it is version 1, which is the default version. Next, the user changes directory (cd) to DISK$USER12:[SMITH.COMMAND_FILES] and enters the dir command to list the files in that directory that are available for recovery.
4 Another add command selects a second file for recovery: ADJUST_TIME.COM;16. A list command displays a list of the files that are currently marked for recovery. In this example, there are two. The destination command shows where these files will be recovered. This destination can be changed with the relocate command.
5 The recover command starts the recover process. The recover program responds with an estimate of the total amount of disk space required, the number of files being recovered, and a list of the volumes where these files reside. After a brief wait for the NetWorker server to respond, the recover program logs each file as it is recovered, summarizing the recover before returning to the recover> prompt. At this point, the recovery is complete and the user exits the recover browser.
Automatic mode In automatic mode, you supply all the needed information for a recover on the command line and the recover program executes the specified recovery. No interactive browser is provided.
Recovering data 61 Backup and Recovery
The use of wildcards in file specifications is not supported in automatic mode. All file specifications must be explicit.
Example 7 Using the recover command in automatic mode
The following command recovers the same files that were recovered in the preceding recover browser example:
nsrrecover -a -s cider disk$user12:[smith]login.com;41 - disk$user12:[smith.command_files]adjust_time.com;16 Recovering 2 files into their original locations Total estimated disk space needed for recover is 9 KB. Requesting 2 files, this may take a while... DISK$USER12:[SMITH.COMMAND_FILES]ADJUST_TIME.COM;16 DISK$USER12:[SMITH]LOGIN.COM;41 Received 2 files from NSR server 'cider' $ The next example shows how to recover all files in a directory by specifying the explicit directory name:
nsrrecover -a -s cider disk$user12:[smith.command_files] Recovering 7 files into their original locations Total estimated disk space needed for recover is 33 KB. Requesting 7 files, this may take a while... DISK$USER12:[SMITH.COMMAND_FILES]ADJUST_TIME.COM;16 DISK$USER12:[SMITH.COMMAND_FILES]CHANGE_PRIVILEGE.COM;1 DISK$USER12:[SMITH.COMMAND_FILES]COMPARE_DISKS.COM;1 DISK$USER12:[SMITH.COMMAND_FILES]DUMP_FID.COM;1 DISK$USER12:[SMITH.COMMAND_FILES]FILL_FILE.COM;6 DISK$USER12:[SMITH.COMMAND_FILES]REPEAT.COM;7 DISK$USER12:[SMITH]COMMAND_FILES.DIR;1 Received 7 files from NSR server 'cider'
Save set recover mode In save set recover mode, the recover program recovers all of the files within a particular save set that match the output file specification. To use save set recover mode, you must specify the save set ID (SSID), which is a number that the NetWorker server associates with the save set. You can locate this number from the NetWorker Management Console interface. Refer to the Dell EMC NetWorker Administration Guide for more information if needed.
To recover files from a save set whose name does not represent the highest level disk:[directory] path to the files contained within that save set, you must define the NSR$RECOVER_MCP logical name before you begin the recover operation.
During a server-initiated save, the NetWorker software assigns a default save set name that represents the most common path (MCP) to all files being saved. Users can override this during a user-initiated save and assign an arbitrary name to the save set by using the -N option in the save command. If the user-assigned save set name does not represent the MCP to the files within the save set, the recover program may exhibit unexpected behavior. For example, additional files from higher-level directories, which are typically ignored during a recover, may be recovered.
62 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
Defining the NSR$RECOVER_MCP logical name ensures that the recover program knows the MCP for the specified save set. When defining the logical name, be sure to specify the disk:[directory] value exactly as it appears in the filename prefix stored in the NetWorker index for files in that save set.
Example 8 Using the recover command in save set recover mode
This example uses save set recover mode to recover the same directory that was recovered in the previous example (DISK$USER12:[SMITH.COMMAND_FILES].
nsrrecover -s cider "-S" 13621 - DISK$USER12:[SMITH.COMMAND_FILES]*.*;* Recovering files into their original locations within / DISK$USER12:[SMITH.COMMAND_FILES]ADJUST_TIME.COM;16 DISK$USER12:[SMITH.COMMAND_FILES]CHANGE_PRIVILEGE.COM;1 DISK$USER12:[SMITH.COMMAND_FILES]COMPARE_DISKS.COM;1 DISK$USER12:[SMITH.COMMAND_FILES]DUMP_FID.COM;1 DISK$USER12:[SMITH.COMMAND_FILES]FILL_FILE.COM;6 DISK$USER12:[SMITH.COMMAND_FILES]REPEAT.COM;7 DISK$USER12:[SMITH]COMMAND_FILES.DIR;1 Received 7 files from NSR server `cider'
Directed recover mode Direct recover mode uses the same interactive command line interface as the browser mode (see “Browser mode” on page 58). However, this mode allows you to instruct recover to send the recovered file to a NetWorker client other than the source client. You specify the recover target in the recover command line with the -R (redirect) option. Directed recoveries have the following restrictions:
◆ Both the source and destination clients must be running the same operating system—in this case, OpenVMS.
◆ Directed recoveries are supported for file selection recoveries only. They are not supported for save set recoveries.
◆ The nwrecover program does not support directed recoveries. You must use the recover command to perform a directed recovery. For more information on directing recovered files to another NetWorker client, refer to the Dell EMC NetWorker Administration Guide.
Example 9 Using the recover command in directed recover mode
In this example, user Smith recovers a selected file from the NetWorker server CIDER for OpenVMS client BUGS and restores the file to OpenVMS client ANTS using directed recover mode. A browser session is used to locate the file.
nsrrecover -s cider "-R" ants -c bugs -f -d - ants$dka0:[smith.reg.ret] DISK$ALPHASYS: recover_usr: Current working directory is DISK$ALPHASYS:[000000] recover> ls SMITH.DIR;1 recover> cd [smith.reg.ret] recover> ls ACCVIO.TXT;3 NSR.HELP;1 ACCVIO.TXT;4 NWARCHIVE.EXE_DBG;1 HOWTO_LD.COM;12 NWBACKUP.EXE;1
Recovering data 63 Backup and Recovery
recover> add ACCVIO.TXT;3 1 file(s) marked for recovery recover> recover Initiating remote recover to ants from server cider, this may take a while... Resource acquired: NSR$SMF_BG15151 recover_usr: recover: Recovering 1 file from DISK$ALPHASYS:[SMITH.REG.RET] into ants$dka0:[smith.reg.ret] Requesting 1 file(s), this may take a while... recover_usr: ants$dka0:[smith.reg.ret]ACCVIO.TXT;3 ants$dka0:[smith.reg.ret]ACCVIO.TXT;3: file exists, overwriting Received 1 file(s) from NSR server `cider' Recover completion time: Wed Nov 15 14:53:39 2006 recover> exit
Recovering files with the nwrecover program
The nwrecover program provides a graphical interface where you can browse backed-up files and file systems and select items for recovery. This interface does not support the following:
◆ Directed recoveries. You must use the recover command in directed recover mode to perform a directed recovery.
◆ The recovery of individual files or directories during a Save Set Recover.
Note: To recover data from a scheduled backup other than the most recent one, you must change the browse time. The Dell EMC NetWorker Administration Guide explains how to use the nwrecover program to recover an earlier version of a file.
To recover files with the nwrecover program: 1. Start the nwrecover program by entering this command at the DCL prompt:
nwrecover •Use the -s server option to specify a particular NetWorker server on the network. •Use the -c client option to specify a particular NetWorker client on the network. If the -c option is not used, the current client is assumed. The nwrecover program displays a representation of the client’s file system. 2. Mark each directory and/or file to be recovered by selecting the checkbox next to each directory or file listed. 3. Click Start to begin the recovery. The time it takes to recover the files depends on file size, network traffic, server load, and tape positioning. During this time, messages appear so that you can monitor the recovery. If there is a naming conflict during recovery, you are prompted to choose a workaround. If the recovery is successful, a message similar to this appears:
Received 1 file(s) from NSR server ’cider’ Recover completion time: Tue Jan 21 08:33:04 2006 For more information, refer to the nwrecover program’s online Help.
64 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
Relocating recovered data
By default the NetWorker server attempts to copy a recovered file to its original location. You can instruct the NetWorker server to relocate these files to a different disk, directory, or both by using one of the following methods:
◆ Include the -d option and specified destination in the recover command.
◆ In browser mode, type the relocate command and a specified destination.
◆ In the nwrecover program, select Relocate from the Options menu and enter a specified destination in the Relocate To field. Use the following syntax when specifying a destination for OpenVMS client data:
{disk:|[directory]|disk:[directory]} To specify the current working disk, enter the logical name SYS$DISK. To specify the current working directory, enter []. Relative paths are interpreted relative to the current working directory. Note the following when relocating recovered data: If no disk is specified — Files are recovered to the original source disk in the specified directory, which is created if necessary. For example, if you recover the file DISK$ODS2:[A.B.C]FILE.TXT to destination [RECOVER], the recovered file will reside at: DISK$ODS2:[RECOVER]FILE.TXT. If no directory is specified — Files are recovered to the original source directory tree on the specified disk. The directory is created if necessary. For example, if you recover the same file (DISK$ODS2:[A.B.C]FILE.TXT) to destination DISK$REC2:, the recovered file will reside at: DISK$REC2:[A.B.C]FILE.TXT. If neither a disk nor a directory is specified — The NetWorker software will prompt you to enter a destination. If files from multiple directories are being recovered to a specified directory — The recovered files are placed under a parent directory that represents the lowest directory in the hierarchy that is common to all files. For example, when the following files are recovered to destination [REC.TEMP]:
[A.B.C]FILE_A.COM;1 [A.B]FILE_B.COM;1 The recovered files are placed in the following locations:
[REC.TEMP.C]FILE_A.COM;1 [REC.TEMP]FILE_B;1 If an entire disk is being recovered — When recovering an entire disk to another disk, specify either disk: or disk:[000000] as the destination.
Note: When recovering a whole directory tree but not the entire disk, specify only the name of the target disk (disk:) as the destination. Do not include [000000]. Otherwise, the directory tree will be restored to the top level on the specified disk, which may not be the intended result.
Recovering data 65 Backup and Recovery
If a physical disk backup is being recovered — When recovering a save set that was created with the rawasm directive to an alternate location, use the -d option with the recover command. Specify one or more device names for the recovery destination. To specify multiple names, use a comma-separated list that is enclosed in quotation marks. See “Recovering a physical disk backup” on page 70 for more information. If aliases are being recovered — When NetWorker recovers alias files, it also recovers the associated primary files. If they reside within the recover path, they are recovered to the specified location. However, if the primary files reside outside the recover path, the NetWorker software places them in a new subdirectory named [.NSR_RECOVER], which is created under the designated recover destination. For example, you instruct the NetWorker software to recover [NSRQA.TEST06] to destination DISK$ODS2:[RECOVER]. This recovery path contains an alias file named [NSRQA.TEST06.A.B.C]ALIAS.TXT. The primary file for this alias resides at [NSRQA.ADMIN.W.X.Y]ORIGINAL.TXT. The alias and primary files are recovered as follows:
DISK$ODS2:[RECOVER]ALIAS.TXT DISK$ODS2:[RECOVER.NSR_RECOVER]ORIGINAL.TXT Saving and recovering an OpenVMS system disk
To correctly save and recover an OpenVMS system disk requires some up-front planning and an understanding of the capabilities of the NetWorker client software. The NetWorker client software provides a network-based save and recover program. It cannot perform a "bare metal restore" because it has no facility similar to the OpenVMS standalone backup program. Therefore, in the event of a complete system disk failure, you must first restore the OpenVMS system to the point where the NetWorker software can be loaded and a connection can be established with the NetWorker server. The NetWorker software can then perform all remaining recover operations.
Backing up an OpenVMS system disk
This section describes the directives to use when backing up an OpenVMS system disk and the commands for performing a client-initiated, manual backup of system disk directories and the entire system disk. Examples in this section show the use of the save command. You can alternately use the nwbackup program and put the recommended directives in a .NSR file in SYS$SYSDEVICE:[000000].
Recommended directives When backing up a system disk, use the nolock directive to allow NetWorker to back up files that are open. “The nolock directive (OpenVMS-specific)” on page 38 provides more information. The NetWorker software can save and recover the alias directory structure found on an OpenVMS system disk. By default, if an alias file is encountered during save processing, the save program creates an entry in the file index that includes the name of the primary file associated with the alias. However, the save program saves no file data. If the alias is a directory file, an entry is made in the index that refers to the primary file, but the alias directory is not scanned for files. This prevents multiple copies of the same file from being sent to the NetWorker server.
66 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
You can override the default settings by using OpenVMS-specific alias directives skip_alias and copy_alias. See the following sections for more information:
◆ “The skip_alias directive (OpenVMS-specific)” on page 43
◆ “The copy_alias directive (OpenVMS-specific)” on page 37 Server-initiated saves To do a server-initiated save of an OpenVMS system disk: 1. Specify the recommended nolock directive. 2. Ensure that the save set is defined as one of the following: • All, which creates the correct save set name • DISK:[000000], where DISK is the LOGVOLNAM of the system disk. For example, DISK$ALPHASYS. To determine the LOGVOLNAM of a volume:
WRITE SYS$OUTPUT F$GETDVI("SYS$SYSDEVICE","LOGVOLNAM")
Commands for backing up system disk directories Use the following commands when performing manual (client-initiated) backups of the SYS$SYSTEM and SYS$MANAGER directories on the OpenVMS system disk.
Do not back up files using system logical names, such as SYS$SYSTEM, SYS$MANAGER, or SYS$STARTUP.
◆ To back up all files in SYS$SYSTEM:
nsrsave sys$sysdevice:[vms$common.sysexe] nsrsave sys$sysdevice:[sysn.sysexe] where sysn is the system root for your computer.
◆ To back up all files in SYS$MANAGER:
nsrsave sys$sysdevice:[vms$common.sysmgr] nsrsave sys$sysdevice:[sysn.symgr]
Example 10 Saving an OpenVMS system disk
The following commands cause a client-initiated save of an entire system disk, name the save set DISK$ALPHASYS:[000000], and specify the nolock directive to ensure that open files are saved:
nsrsave -s server -f - "-N" "DISK$ALPHASYS:[000000]" - disk$alphasys:[000000] <<"DISK$ALPHASYS:[000000]">> +NOLOCK: *.*;* Ctrl-z
Saving and recovering an OpenVMS system disk 67 Backup and Recovery
Recovering an OpenVMS system disk
To recover an OpenVMS system disk: 1. Initialize an alternate disk that will become the system disk:
initialize/system disk: label 2. Mount the initialized alternate disk. 3. Use recover (in browser mode) to recover files from the saved system disk to the newly initialized one:
nsrrecover -s cider sys$sysdevice:[000000] nsr$recover: Current working directory is DISK$ALPHASYS71:[000000] recover> add DISK$ALPHASYS71:[000000] ... DISK$ALPHASYS71:[VMS$COMMON.VUE$LIBRARY.USER] DISK$ALPHASYS71:[VMS$COMMON.XDPS$INCLUDE] 8677 file(s) marked for recovery recover> relocate
• On Alpha: Run the WRITEBOOT utility on the newly restored system disk. For example:
run sys$system:writeboot Update VAX portion of boot block (default is Y) : n Update AXP portion of boot block (default is Y) : y Enter AXP boot file : disk:[vms$common.sysexe]apb.exe
• On Integrity: Use the SET BOOTBLOCK command to initialize the boot block on the newly restored system disk. For example:
set bootblock dka100: 5. Shut down the system and reboot on the newly restored system disk.
68 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
Performing a physical disk backup and recovery
You can instruct the save program to perform a physical disk backup by using the rawasm directive. This causes save to back up the specified device block by block, similar to that of an OpenVMS physical backup (BACKUP/PHYSICAL). You can subsequently recover the entire device but not individual files.
To obtain a consistent backup of a disk with rawasm, you must ensure that the device that is being backed up is not being actively written to by other processes and that disk caching has been disabled. Otherwise, the save program cannot guarantee a completely consistent backup. For more information, see “Important considerations for physical backups” on page 41.
Performing an ad hoc physical disk backup
To perform a physical disk backup from the NetWorker client: 1. (Recommended) To achieve a consistent backup, mount the input device (the device that is being backed up) as /FOREIGN or /NOWRITE. If you are backing up a volume set, dismount the volume set and then mount each relative volume (RVN) /FOREIGN and back up the RVNs one at a time using the instructions that follow. Keep track of which backups are associated with the volume set because you will need this information for recovery. 2. In the save command line, specify the physical device name as the target directory or backup target. 3. Use the -f option to specify the name of the file that contains the rawasm directive or include the optional argument - (hyphen) instead of a file name, press Enter, and type the rawasm directive, which uses this syntax:
<<"/">> [+]rawasm: "device-name:" where "device-name:" is the same device name you specified in the save command line as the backup target. The examples that follow show how to perform a physical backup of a disk and a bound volume set, respectively. “The rawasm directive” on page 39 provides more information on the use of this directive.
Example 11 Manual physical backup of a disk
The command in this example uses the rawasm directive to back up the device ITAN$LDA6: to the NetWorker server CIDER. The new save set is named ITAN$LDA6:.
nsrsave -s cider -f - itan$lda6: <<"/">> rawasm: "lda6:" Ctrl-z ITAN$LDA6: /
save: ITAN$LDA6: 257 KB 00:00:03 2 files
Performing a physical disk backup and recovery 69 Backup and Recovery
Because itan$lda6: and "lda6:" both resolved to the same physical device name, ITAN$LDA6:, the save program uses that name as the save set name. In this example, save lists two files as being saved: ITAN$LDA6:, which is the new save set, and /, which is the root of the NetWorker index structure.
Example 12 Manual physical backup of a volume set
The command in this example uses the rawasm directive to back up volume set ITAN$LDA4: to the NetWorker server (CIDER).
nsrsave -s cider -f - itan$lda4: <<"/">> rawasm: "itan$lda4:" Ctrl-z ITAN$LDA4: ITAN$LDA5: ITAN$LDA6: / save: ITAN$LDA4: 6514 KB 00:00:03 2 files The save program displays the name of each RVN as it is saved, to indicate that it is part of the save set. These RVNs cannot be restored individually.
Recovering a physical disk backup
To recover a physical disk backup from a NetWorker client: 1. Mount the destination disk for the recovery as /FOREIGN. If you are recovering a volume set, provide the same number of disks that were backed up when the volume set was saved. These disks must be the same size or larger than the original disks. 2. Use save set recover mode or browser mode as you would for a regular, single-file recovery. You can specify an alternate location for the recovered save set by including the -d (destination) option in the recover command and specifying the target device name as an argument. Note that the -d option accepts device names only when used during recovery of a save set created with rawasm. You may specify multiple device names in a comma-separated list enclosed in quotation marks.
Depending on how the original save was done, you may see the following informational message when you mount a device that contains a recovered physical backup (that is, a save performed with the rawasm directive):
MOUNT-I_REBUILD, volume was improperly dismounted; rebuild in progress
This message can be ignored.
Example 13 Recovery of a physical backup of a volume set
In this example, a volume set that was backed up with the rawasm directive is recovered. The browser is used to locate the save set containing the volume set. See Table 8 on page 71 for explanations of the numbered callouts that appear in parentheses throughout this example.
70 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Backup and Recovery
mount/foreign lda4 (1) %MOUNT-I-MOUNTED, RVN1 mounted on _ITAN$LDA4: mount/foreign lda5 %MOUNT-I-MOUNTED, RVN2 mounted on _ITAN$LDA5: mount/foreign lda6 %MOUNT-I-MOUNTED, RVN3 mounted on _ITAN$LDA6: nsrrecover -vvs cider / (2) recover: Current working directory is / recover> dir 03/08/06 11:16 AM
Table 8 Volume set recovery example callouts (page 1 of 2)
Callout Description
1 The mount/foreign command is used to mount three volumes, which will be the target devices for the recovery. These volumes are the same size or larger than the relative volumes (RVNs) that make up the volume set being recovered.
2 A browser session is started with the recover command. The -vv options instruct the recover program to display additional information during the session. The -s option identifies the NetWorker server as CIDER. The / (forward slash) instructs recover to start browsing at the root of the NetWorker index structure. (All save sets created with the rawasm directive reside in the root directory.) The browser sets the current working directory to root. The user enters the directory command to obtain a list of files that are available for recovery. Two filenames are listed, one of which is the save set that the user is seeking (ITAN$LDA4:).
3 The add command is used to select ITAN$LDA4: for recovery.
Performing a physical disk backup and recovery 71 Backup and Recovery
Table 8 Volume set recovery example callouts (page 2 of 2)
Callout Description
4 The recover command instructs the recover program to begin recovery of the selected save set, ITAN$LDA4:. The recover program responds with the number of files being recovered, an estimate of the total amount of disk space required, and the identify of the volumes where the requested save set resides. After waiting for a response from the NetWorker server, the recover program displays the name of each relative volume as it is recovered, and summarizes the recovery before returning to the recover> prompt. The user exits the recover browser.
5 The dismount command is used to dismount each of the three volumes containing the three RVNs that make up the volume set being recovered.
6 The three volumes are remounted without the /FOREIGN qualifier. The /BIND qualifier is used to recreate the volume set and assign the name "vset." OpenVMS assigns the logical volume name of DISK$VSET to the recovered volume set.
Example 14 Another example of a physical backup recovery of a volume set
This example uses save set recover mode (-S) and recovers the same three-volume volume set that was recovered in the preceding example. To illustrate the use of the -d option, the command in this example changes the output devices so that data from ITAN$LDA5 and ITAN$LDA6 is written to output devices ITAN$LDA6 and ITAN$LDA5. The data of these two volumes is swapped. Because ITAN$LDA4 is larger than either ITAN$LDA5 or ITAN$LDA6, its data cannot be written to one of the other devices.
mount/foreign lda4 %MOUNT-I-MOUNTED, RVN1 mounted on _ITAN$LDA4: mount/foreign lda5 %MOUNT-I-MOUNTED, RVN2 mounted on _ITAN$LDA5: mount/foreign lda6 %MOUNT-I-MOUNTED, RVN3 mounted on _ITAN$LDA6: nsrrecover -vvs cider "-S" 4015405014 -d "ITAN$LDA4:,ITAN$LDA6:,ITAN$LDA5:" Recovering files into their original locations within / recover: recovering 1 save set(s) on rsid 1295020486 rawasm -r ITAN$LDA4: rawasm recovering volume set volumes: ITAN$LDA4: to ITAN$LDA4:, 12000 OpenVMS disk blocks ITAN$LDA5: to ITAN$LDA6:, 512 OpenVMS disk blocks ITAN$LDA6: to ITAN$LDA5:, 512 OpenVMS disk blocks Received 1 matching file(s) from NSR server `cider' Recover completion time: Sat Nov 11 15:49:27 2006 dismount lda4 dismount lda5 dismount lda6 mount/system lda4,lda6,lda5 rvn1,rvn2,rvn3 /bind=vset %MOUNT-I-MOUNTED, RVN1 mounted on _ITAN$LDA4: %MOUNT-I-MOUNTED, RVN2 mounted on _ITAN$LDA6: %MOUNT-I-MOUNTED, RVN3 mounted on _ITAN$LDA5: $
72 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide CHAPTER 5 Archiving Invisible Body Tag
This chapter covers these topics:
◆ Overview of archiving...... 74 ◆ Manual archive operations...... 75 ◆ Retrieving archived data...... 80 Note: The archive feature must be purchased and licensed separately from other NetWorker software components. See the Dell EMC NetWorker Licensing Guide for more information on licensing procedures.
Archiving 73 Archiving
Overview of archiving
The archive process captures files or directories as they exist at a specific time, and writes the data to archive storage volumes, which are not automatically recycled. After the archive process completes, you can delete the original files from the disk to conserve space. This process is referred to as grooming. Archive save sets are similar to backup save sets. The main difference is that archive save sets have no expiration date. By default, the archive backup level is always set to full. Because the NetWorker server treats archive data differently than backup save set data, archive data must be written to separate pools. Browse and retention policies do not apply to archive data. Benefits of using the NetWorker archive feature include:
◆ Files that have been archived can be: • Deleted from primary disk storage to make space for newer files. • Retained in archive volumes for quick retrieval in the future.
◆ Archived data is never subject to automatic recycling so it cannot be overwritten accidentally.
Archive requirements
For a complete description of the requirements for using the NetWorker archive feature, including both licensing and permissions, refer to the Dell EMC NetWorker Administration Guide.
How the NetWorker server archives data
The NetWorker software provides three preconfigured pools to receive archived data: the Archive pool (for nonindexed archiving) and the Indexed Archive and PC Archive pools (for indexed archiving). Client data for OpenVMS clients is written to the Archive pool by default. You can also create custom archive pools. Information about archive data is tracked in the NetWorker server’s media database. If you create a custom archive pool for OpenVMS client data, you must set the Store Index Entries attribute in the custom archive pool’s resource to No.
If you use the preconfigured Indexed Archive pool or PC Archive pool, or if you create a custom archive pool that has the Store Index Entries attribute in the Pool resource set to Yes, information about individual files in the archive save set are tracked in the client file index. The client file index entries that are generated during an archive are backed up to volumes from the Default pool during the next scheduled backup.
Note: Index entries are not generated when the Store Index Entries attribute in the Pool resource is set to No.
Data that is archived with the nonindexed archiving method is archived as a single save set, regardless of the combination of directories and files specified for the archive. When you retrieve this data, the NetWorker software must read the entire save set before a specified file or files can be retrieved.
74 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Archiving
When you manually archive data or create an archive request for scheduled archiving of OpenVMS client data, you will be prompted for an annotation that describes the save set. An annotation is a comment that you associate with an archive to help you identify data later for retrieval. Manual archive operations
You can manually archive data at any time. Manually archiving data is similar to performing a manual backup.
Performing a manual archive on OpenVMS
You can manually archive data from an OpenVMS NetWorker client by using either of the following methods:
◆ Enter the nsrarchive command at the DCL prompt with the appropriate options and arguments. See “The nsrarchive command” on page 75 for details.
◆ Run the nwarchive program and select the appropriate file or data items in the graphical user interface. See “Archiving data with the nwarchive program” on page 79 for more information. During an archive operation, you can monitor messages with the nsrwatch program as described in “The nsrwatch command” on page 26. You can also monitor the progress of the archive operation from the NetWorker Management Console. The Dell EMC NetWorker Administration Guide explains how to use this interface.
The nsrarchive command The nsrarchive command allows you to archive entire file systems, directories, or individual files to the NetWorker server. Depending upon the options you include, this command can also be used to:
◆ Verify the archive, as described in “Archiving data and verifying the archive” on page 77.
◆ Make a duplicate copy (clone) of the archive, as described in “Archiving data and cloning the archive” on page 78.
◆ Remove original files from the client computer (groom directories) after the files have been archived, as described in “Archiving data and grooming directories” on page 78. To use the NetWorker archive services from a client computer, the Archive Services attribute must be enabled in the Client resource on the NetWorker server. The Dell EMC NetWorker Administration Guide provides more information on enabling archive services for clients. Format The format for the nsrarchive command is as follows:
nsrarchive ["-BinpqvVy"][-b pool]["-C" clone_pool] [-f directive_filename]["-G" remove path_specification] ["-I" input_file] ["-N" name] ["-R" name][-s server] ["-T" annotation_text] ["-W" width][path...]
Manual archive operations 75 Archiving
Note: All uppercase options must be enclosed in quotation marks (" ") to retain their case. Arguments that contain uppercase letters, embedded spaces, or punctuation must also be enclosed in quotation marks.
When using the nsrarchive command, note the following:
◆ If you have a multiserver network and do not specify a server name, the NetWorker software chooses an archive server for you.
◆ If you do not specify a volume pool for the archive, the volume pool becomes Archive by default.
◆ If you do not specify an annotation for the archive, you will be prompted for one. Arguments Like the save command, the nsrarchive command takes one or more optional path arguments, separated by spaces. This argument specifies the path to the directory or file to be archived. Wildcards are permitted. For example:
nsrarchive -s cider DISK$ALPHASYS:[SWENG]TCPIP$FTP_SERVER.LOG;* - DISK$ALPHASYS:[ACCTG.2006] If no path is specified in the nsrarchive command, all files in the issuing process’s current default directory, its subdirectories, and the directories themselves are archived. Options Table 9 lists the valid options for the nsrarchive command. The sections that follow show examples of the appropriate nsrarchive command and options to use when archiving with verification, cloning, and grooming, respectively.
Table 9 nsrarchive command options (page 1 of 2)
Option Argument Description
-b archive volume Specifies the name destination pool for the archive save set. pool name If no pool is specified, the Archive pool is used by default for OpenVMS clients.
-f directive filename Specifies the name of the directive file to process before nsrarchive begins scanning the specified file system. You can also specify a hyphen (-) as an argument to this option. This instructs nsrarchive to read the directives from the command line (SYS$INPUT). When you specify –f – on the command line and then press Enter, nsrarchive expects the directives to follow. Each record that you type thereafter is interpreted as a line in the directive file until Ctrl-z is pressed, which terminates the directive.
-i none (Ignore) Instructs the nsrarchive program to ignore any directive files found on the client’s online file system.
-s server name (Server) Specifies the name of the NetWorker server to use for archiving the directory.
-y none (Yes) Instructs NetWorker to respond affirmatively to any questions.
76 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Archiving
Table 9 nsrarchive command options (page 2 of 2)
Option Argument Description
-C clone pool name (Clone) Causes the nsrarchive program to generate a clone (a duplicate copy) of this archive save set to the specified clone pool. If no pool is specified, the default clone pool Archive Clone is used. “Archiving data and cloning the archive” on page 78 provides more information.
-G remove path specification (Groom) Causes the nsrarchive program to groom files from the specified directory tree after they have been archived. You must include the remove keyword and the directory path for the directory being groomed. If the -y option is not supplied, you will be prompted for the removal of top-level directories. See “Archiving data and grooming directories” on page 78 for more details.
-I input_file Specifies the name of the file that contains the names of the files to be archived. This option is unique to OpenVMS. It allows you to specify multiple filenames and paths without the character restriction imposed by the DCL command line. When creating the input file, enter each filename on a separate line.
-N archive name Specifies the name for this archive save set. By default, the first path argument is used as the name.
-T annotation text Associates the specified, descriptive text with the archive save set. If you do not specify an annotation, the nsrarchive program prompts for it. Annotation text must be alphanumeric and cannot exceed 1024 characters. Avoid the use of special characters. If the annotation contains more than one word or mixed case or punctuation, the entire string must be enclosed in quotation marks (" ").
Note: When NetWorker searches for an annotation, the search is case-sensitive.
-V none (Verify) Verifies the archive by comparing data on the archive volume against data on the local disk and reporting any discrepancies found. See “Archiving data and verifying the archive” on page 77 for more information.
Archiving data and verifying the archive You can archive a directory and verify the archive in one step by including the -V (verify) option in your nsrarchive command as shown in Example 15. After the archive completes, the NetWorker software verifies the archive save set by comparing the data on the archive volume with the data on the local disk, byte for byte and attribute for attribute. You are notified of any discrepancies.
Example 15 Archive with verify
The command in this example directs the nsrarchive program to archive the user directory tree [SMITH]. All files and subdirectories for the [SMITH] directory tree are saved. The nsrarchive program prompts for an annotation because the annotation option (-T) is not specified in the command line. The -V option instructs nsrarchive to verify all files in the archive after the archive completes.
Manual archive operations 77 Archiving
nsrarchive "-V" -s cider disk$test:[smith] Please enter annotation for this archive (type
Finished reading annotation; beginning archive. . . . (all of the files from the [SMITH] directory tree are listed here)
nsrarchive: DISK$TEST:[SMITH] 276 KB 00:00:03 80 files
Start verifying. Recover completion time: Wed Jan 31 21:20:19 2007 Done verifying.
Archive Completion Information
Completed: Wed Jan 31 21:20:19 2007 Save set(s): disk$test:[smith] Verified: Yes Groomed: No Volume(s): server.archive.002
Annotation: ------Mr. Smith's Archive 31-Jan-2007
Archiving data and cloning the archive The NetWorker software clones an archive by making a duplicate copy of it. Two backup devices are required to make a clone:
◆ One for the original archive volume
◆ One for the archive clone volume Both devices must have a valid, writable archive volume mounted. To clone an archive, include the -C (clone pool) option and a pathname for the directory that you are cloning in the nsrarchive command. The format for an nsrarchive command that archives data, verifies the archive, and clones the archive is as follows:
nsrarchive -s server -b "pool" "-V" "-C" clone_pool - "-T" annotation_text disk:[dir]
Note: Archiving with cloning can take a significant amount of time. The NetWorker software displays the list of directories and files as archiving and cloning tasks are performed.
Archiving data and grooming directories To conserve disk space, you can instruct the NetWorker software to groom files after archiving. This causes nsrarchive to remove all archived files from the specified directory tree after the archive operation has finished. If verification or cloning is requested, grooming will occur after these functions have successfully completed.
78 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Archiving
To instruct the NetWorker software to groom directories after archiving, include the -G option in your nsrarchive command and specify the remove keyword and the path to the directory to be groomed.
Example 16 Archive with grooming
The command shown in this example directs nsrarchive to delete all of the files in the [SMITH] directory tree after they have been archived and verified.
nsrarchive "-V" -s cider "-G" remove disk$test:[smith] Please enter annotation for this archive (type
Finished reading annotation; beginning archive. . . . (all the files from the [SMITH] directory tree are listed here)
nsrarchive: DISK$TEST:[SMITH] 276 KB 00:00:03 80 files
Start verifying. Recover completion time: Wed Jan 31 21:20:19 2007 Done verifying.
remove all files and directories archived (y/n)? [n] y Archive Completion Information
Completed: Wed Jan 31 21:20:19 2007 Save set(s): disk$test:[smith] Verified: Yes Groomed: Yes Volume(s): cider.archive.002
Annotation: ------Mr. Smith's Archive 31-Jan-2007
Archiving data with the nwarchive program The nwarchive program provides a graphical interface from which you can request a manual archive of client data. You can select options to indicate whether verification, cloning, grooming, and compression should also be performed.
Note: Manual archives performed with the nwarchive command do not support the use of directives. However, scheduled archives do enforce global and local file (.NSR) directives. For more information about scheduled archives, see the Dell EMC NetWorker Administration Guide.
To perform a manual archive by using the nwarchive program:
3. Start the nwarchive program by typing the nwarchive command at the DCL prompt. To archive to a NetWorker server other than the default server, include the -s option and the server name. For example:
nwarchive -s cider 4. Select Mark from the Mark menu to select each file or directory for archiving. 5. On the File menu, select Start Archive.
Manual archive operations 79 Archiving
6. Enter a comment in the Annotation attribute to uniquely identify this archive save set. 7. Select the appropriate archive pool from the Archive Pool attribute. Only pools with the Pool Type attribute set to Archive are listed. 8. Select the appropriate responses for these data archiving attributes: • Compress: To compress the data as it is archived, select Yes. Be aware that compression and decompression use more server resources and may slow data archiving and retrieval. • Clone: To write a copy of each archive save set to a volume from an archive clone pool, select Yes. If you enable cloning, enter or select an archive clone pool in the Clone Pool attribute. • Verify: To check the integrity of the data on the storage volume, select Yes. • Grooming: To remove the archived files from the disk, select Yes. 9. Click Archive. The Archive Status window appears. When the archive is complete, a message similar to the following appears in the Archive Status window:
Archive completion time: 1-31-07 5:18p 10. If Groom was selected in step 6, you are prompted to confirm before archived files are deleted from the local disk. For more information, refer to the online help for the nwarchive program. Retrieving archived data
You can retrieve nonindexed archived data from an OpenVMS client by using either of the following methods:
◆ Type the nsrretrieve command at the DCL prompt with the appropriate options and arguments. “The nsrretrieve command” on page 81 provides details.
◆ Run the nwretrieve program and select the appropriate save sets in the graphical user interface. (You cannot retrieve individual files using this method.) “Retrieving data using the nwretrieve program” on page 83 provides details.
To browse indexed archives (archives saved to the Indexed Archive pool, PC Archive pool, or a custom archive pool with the Store Index Entries attribute enabled) and select files for retrieval use either of the following methods:
◆ Use the nsrrecover command to start the recover program in browser mode. Include the -x option and specify the archive index namespace to access indexed archives. Select the files to retrieve using the same procedure that you would use to recover backed up files. “Browser mode” on page 58 provides details.
◆ Run the nwrecover program as described in “The nwrecover program” on page 1-3 and select Index Namespace>Archive from the Change menu. Mark the files to be recovered and click Start on the toolbar. Refer to the nwrecover program’s online Help for more information if needed.
80 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Archiving
The following restrictions apply when retrieving archived data:
◆ You must have read permissions to the archived data.
◆ If the Server resource’s Public Archives attribute is enabled, all users listed in the Client resource’s Archive Users attribute can retrieve data (as long as they have read permissions to the data).
◆ If the Server resource’s Public Archives attribute is disabled, only the NetWorker administrator or the owner of the file can retrieve the data.
Note: If, during retrieval, the operating system allows you to change the ownership of archived data to that of the original owners, then the retrieved files display the original ownership. Otherwise, the user who retrieves the files becomes the owner of the files.
The Dell EMC NetWorker Administration Guide provides more information on permissions for archiving.
The nsrretrieve command
The nsrretrieve command allows you to restore archive save sets from a NetWorker server. Unlike the recover command, the nsrretrieve command does not have a browser mode. When retrieving archived files, you must specify the save set ID number or the annotation text for that save set and the name of the archive pool. This information is available from the NetWorker server. Format The format for the nsrretrieve command is as follows:
nsrretrieve [-fnqu][-i {nNyYrR}][-d destination][-s server] {["-S" ssid[/cloneid]]["-A" annotation_text]}[path...]
Note: All uppercase options must be enclosed in quotation marks (" ") to retain their case. Arguments that contain uppercase letters, embedded spaces, or punctuation must also be enclosed in quotation marks.
Arguments The nsrretrieve command takes one or more optional path arguments, separated by spaces. This allows you to restrict the retrieval to particular directories or files (as opposed to the entire save set). Wild cards are permitted. For example:
nsrretrieve -s elmer "-A" "20070306_eng3" - DISK$ALPHASYS:[SWENG]TCPIP$FTP_SERVER.LOG;22 - DISK$ALPHASYS:[SWENG]TCPIP$FTP_SERVER.LOG;21 Only those files that match the specified path are retrieved. If you omit the path argument or specify one that contains all wildcards (for example: *.*;*), then the contents of the entire save set are retrieved.
Retrieving archived data 81 Archiving
Options Table 10 lists the valid options for the nsrretrieve command. An example of the nsrretrieve command is shown in Example 17 on page 82.
Table 10 nsrretrieve command options
Option Argument Description
-d disk, directory, or (Destination) Specifies the destination disk and/or directory for both retrieved files. “Relocating recovered data” on page 65 (disk:[directory]) explains how the NetWorker software determines which disk or directory to use when either of these values is omitted.
-f none Indicates that retrieved files will overwrite existing files whenever a filename conflict occurs.
-i action to take Allows you to predefine the initial default overwrite response when filename when a filename conflict occurs. You can specify only one letter. conflict occurs Valid arguments are: n = Do not overwrite the file N = Do not overwrite any files y = Overwrite the file Y = Overwrite all files r = Rename the file (OpenVMS creates a new version) R = Rename all files Enclose any uppercase arguments in quotation marks.
-n none (No retrieve) Prevents nsrretrieve from creating any directories or files.
-q none (Quiet mode) Turns off verbose mode, which nsrretrieve uses by default.
-s server name (Server) Specifies the name of the NetWorker server from which you are retrieving archived files.
-u none Instructs nsrretrieve to stop retrieving files after the first error is encountered. If this option is not set, nsrretrieve will attempt to continue to retrieve the rest of the files requested.
-A annotation text Specifies the annotation text for the archive save set from which you are retrieving data. At least one annotation or save set ID (ssid) must be specified.
-S save set ID (ssid) (Save set ID) Specifies the save set ID for the save set being retrieved. When there are multiple clone instances for an archive save set, you can specify the save set ID for the clone save set (cloneid) to select the particular clone instance to be retrieved. At least one ssid or annotation must be specified.
Example 17 Retrieving archived data
The following nsrretrieve command retrieves the files that were archived previously in Example 16 on page 79. Because the file specification at the end of this nsrretrieve command uses wildcards, all files are returned.
nsrretrieve -s cider "-A" "Mr. Smith's Archive - 31-Jan-2007" disk$test:[smith...]*.*;* Recovering files into their original locations within DISK$TEST:[SMITH]
... (files are listed here) ...
82 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Archiving
Received 80 matching file(s) from NSR server 'cider' Recover completion time: Thu Feb 01 20:32:19 2007
Retrieving data using the nwretrieve program
The nwretrieve program provides a graphical interface from which you can retrieve archived save sets. To retrieve archived save sets with the nwretrieve program: 1. Mount the archive volume in the appropriate storage device. 2. Start the nwretrieve program by entering the nwretrieve command at the DCL prompt. To use a NetWorker server other than the default server, include the -s option and the server name. For example:
nwretrieve -s cider 3. To limit the archived save sets found during the query, specify one or more of these attributes: • Client: The client with the archived data to retrieve. • Save Set Name: The name of the archived save set to retrieve. • Search Annotation For: All or part of the annotation assigned when the save set was archived. To aid the search, use wildcard symbols. 4. Click Query to search for the save sets. Matching archived save sets appear in the Archives window. To view the details of an archived save set, such as its size, save set ID, and archive date, select the archived save set and click Details. 5. To begin the retrieval, select the archived save set to retrieve and select Start Retrieve from the File menu. The Retrieve Status window appears. To relocate the files, enter the new location in the Relocate To attribute. To overwrite existing files, enable the Overwrite Existing Files attribute. 6. Click OK. For more information, refer to the online help for the nwretrieve program.
Retrieving archived data 83 Archiving
84 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide APPENDIX A Logical Names Invisible Body Tag
This appendix describes the logical names used by the NetWorker software for OpenVMS.
Logical Names 85 Logical Names
NetWorker Logical Names
The NetWorker software for OpenVMS relies on several logical names for proper operation. Other logical names can be defined to modify the default behavior of various commands and utilities and for diagnostic purposes. Most NetWorker logical names are intended for use by the software itself or at the direction of software support personnel and are not defined for general operation.
Some of the logical names described in this appendix can adversely affect NetWorker performance and/or operation. Therefore, indiscriminate use of these logical names is discouraged.
Table 11 on page 86 lists the logical names (in alphabetical order) that are used by the NetWorker software.
Table 11 NetWorker logical names (page 1 of 10)
Logical name Description
NSR$AES_NOTICE Causes one of the following messages to be written to the daemon log when encryption or decryption is being performed: save: Encrypting data on this save recover: Decrypting data on this recover NSR$ARCHIVE_TMPDIR Specifies the directory where the nsrarchive command places the list of files to groom if grooming has been selected. By default, this list of files is placed in a temporary file in SYS$SCRATCH.
NSR$AUTH_THREADS Minimum size of the thread pool for the main authentication methods within nsrexecd. If the default size is insufficient for a given workload, the nsrexecd logs a message to the DAEMON.RAW file suggesting a value for this logical name and providing the recommended syntax for defining it.
NSR$AUTHRESPONDER_THREADS Minimum size of the thread pool for the authresponder within nsrexecd. If the default size is insufficient for a given workload, the nsrexecd logs a message to the DAEMON.RAW file suggesting a value for this logical name and providing the recommended syntax for defining it.
NSR$BITMAPS Specifies the location of the [.BITMAPS] subdirectory in the NetWorker directory tree.
86 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Logical Names
Table 11 NetWorker logical names (page 2 of 10)
Logical name Description
NSR$BLOCK_SIZE_devnam Defines the block size (in kilobytes) to use for the specified tape unit. The devnam portion of the logical name must match the local tape device portion of the Tape resource name, minus the leading node name and trailing colon. For example, if the Tape resource name is: rd=axpvms:AXPVMS$MKC400: then define this logical name: NSR$BLOCK_SIZE_AXPVMS$MKC400 Include the /SYSTEM qualifier when defining this logical name. Its value equates to an integer value between 32 (NetWorker storage node minimum) and 64 (OpenVMS maximum). The actual value used by the NetWorker software depends upon the value you specify and buffer size alignment considerations. The maximum size supported by OpenVMS is 65,535 (64 KB-1) bytes.
NSR$CHECK_SERVER_LIST When defined to any value as a system-wide logical name, causes a NetWorker storage node to honor requests from multiple servers by instructing it to validate server requests against a list of servers. The server list is defined at installation and resides at NSR$COMMON:[NSR.RES]SERVERS. You can modify this file as necessary, but must restart the NetWorker software to put your changes into effect. When this logical is defined, the NetWorker storage node accepts requests from the first NetWorker server to establish contact after startup. Requests from subsequent servers are denied.
NSR$CLUSTER_ALIAS_NAME Specifies one or more names that NetWorker software associates with the OpenVMS cluster. All names must be associated with the same TCP/IP address, which must be available in DNS. For example: vmscluster.mycorp.com,vmscluster This logical name is defined during installation of the NetWorker client software, and is based on the response to the cluster alias name prompt. The logical name definition is stored in the following file: SYS$COMMON:[SYS$STARTUP] NSR$DEFINE_CLUSTER_ALIAS.COM The NSR$STARTUP.COM procedure executes this file.
NetWorker Logical Names 87 Logical Names
Table 11 NetWorker logical names (page 3 of 10)
Logical name Description
NSR$CONNECTION_STATE Specifies how nsrexecd connects a detached process’s stdout and stderr streams to the NetWorker server’s error and output sockets. The following integer values are supported: • Less than zero: The detached process’s stdout and stderr streams are connected to the NetWorker server’s stdin/stdout socket. • Zero (default): The detached process’s stdout and stderr streams are connected to the NetWorker server’s stdin/stdout and stderr sockets, respectively. • Greater than zero: The detached process’s stdout and stderr streams are connected to the NetWorker server’s stderr socket.
Note: Define this logical name only at the request of software support personnel.
NSR$COMMON Specifies the location of the NetWorker common directory tree. All files shared among nodes in a cluster are located in the common tree. The location of this directory tree depends on the /DESTINATION qualifier value provided to the PCSI utility during the NetWorker installation.
NSR$DEBUG_FLAG Specifies the level of debugging to be used by all NetWorker programs. Define this logical to an integer value prior to invoking a NetWorker program. (The integer controls the debug level.) The effect of this logical is similar to that of the debug option ("-D"), which is valid with many NetWorker commands.
Note: Define this logical name only at the request of software support personnel. Its use may interfere with the normal operation of the NetWorker software.
NSR$DAEMON_AUTH_THREADS Minimum size of the thread pool for the daemon authentication methods within nsrexecd. If the default size is insufficient for a given workload, the nsrexecd logs a message to the DAEMON.RAW file suggesting a value for this logical name and providing the recommended syntax for defining it.
NSR$DISABLE_DRIVE_ALLOC Forces the nsrmmd command to not allocate a tape drive while it is being used.
Note: Define this logical name only at the request of software support personnel.
NSR$DISABLE_FIDCACHE As part of its normal operation, the save program converts file IDs to filenames. Many times, this operation occurs against the same set of a few files. The save program contains an internal cache of FIDs and filenames that is used to improve performance of these lookups. Defining this logical name disables the cache and causes all such conversion requests to issue I/Os to the disk.
88 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Logical Names
Table 11 NetWorker logical names (page 4 of 10)
Logical name Description
NSR$DISABLE_SMART_SELECT One of several system-wide logical names used by daemon processes to allow the NetWorker software to accommodate the different ways in which TCP/IP software products handle the select function. (See also NSR$INTERRUPT_SELECT.) This particular logical disables the special processing associated with the NSR$INTERRUPT_SELECT logical names.
Note: This logical name is for internal software use only and is not intended for use by end users.
NSR$FILE_BUFFER_COUNT Specifies the number of file buffers to allocate initially. File buffers are areas of memory sufficient for holding an entire OpenVMS file specification. Rather than allocating these memory blocks from heap storage, the NetWorker software uses its own file buffer pool. This helps control memory usage in the software. By default, the software allocates 100 file buffers during program initialization.
NSR$FILE_BUFFER_SIZE Specifies the size, in bytes, of the buffers allocated for filenames. This value must not be less than 256 bytes or the NetWorker software may not operate properly because the maximum ODS-2 file specification is 255 bytes. The default value for this logical name is 4,096. You can safely use smaller values (minimum of 256 bytes) on ODS-2 disk volumes. Doing so reduces the memory requirements of the NetWorker software.
NSR$FILE_BUFFER_TRACE When defined, enables tracing of the file buffer pool operations.
NSR$FILE_DEVICE_SIZE Defines the default value for the initial allocation of a file device on the OpenVMS storage node. The default value is 4 times the block size of the file device. For file devices implemented on OpenVMS disks mounted with high-water marking enabled, it improves performance to allocate the entire file device initially rather than allowing the operating system to extend the file as needed. The value specified is the number of OpenVMS disk blocks (512 bytes) to allocate.
NSR$IGNORE_BACKUP_TIME By default, the save program considers a file’s last modification time and its last backup time when determining whether to backup the file during an incremental backup. Defining this logical name to any value causes save to ignore the backup time stamp.
NSR$INCLUDE_ALL_DEVICES When defined, causes the SCSI b.t.l emulation, which runs beneath nsrmmd to include SCSI disks as well as tapes and changer devices
Note: Define this logical name only at the request of software support personnel.
NetWorker Logical Names 89 Logical Names
Table 11 NetWorker logical names (page 5 of 10)
Logical name Description
NSR$INCLUDE_NONSCSI_DEVICES When defined, causes the SCSI b.t.l emulation, which runs underneath nsrmmd, to include non-SCSI devices in the device database.
Note: Define this logical only at the request of software support personnel.
NSR$INDEX_KEEPALIVE Defines the number of hours that the index socket will stay active before it times out. This will keep the index socket from timing out if you are saving very large files. The default is 2 hours.
NSR$INTERRUPT_SELECT, Used by daemon processes to allow the NetWorker NSR$INTERRUPT_SELECT_ERRNO, software to accommodate the different ways in which NSR$INTERRUPT_SELECT_RETVAL, TCP/IP software products handle the select function. NSR$INTERRUPT_SELECT_STATUS, (See also NSR$DISABLE_SMART_SELECT.) NSR$INTERRUPT_RDMSK_ZERO Under normal circumstances, none of these logical names are defined. The NetWorker software defines them when needed, after probing the capabilities of the TCP/IP software in use.
Note: These logical names are for internal software use only and are not intended for use by end users.
NSR$LOGS Defines the location for log files generated by the NetWorker utilities. The NSR$STARTUP command procedure defines this logical name.
NSR$LOG_AIO When defined, causes the nsrmmd command to log all asynchronous I/O operations.
NSR$LOG_START_STOP_OF_PROCESSES When defined as TRUE, nsrexecd logs the start and stop of processses. The default is undefined.
NSR$LUS_DEBUG When defined, causes the SCSI b.t.l emulation to print out additional debugging information.
NSR$MAX_SESSIONS Determines the value returned by the savefs program for maximum concurrent sessions on the save device. By default, this value is 4.
NSR$MAX_TAPE_BLOCK_SIZE Causes nsrmmd to use the specified value (in KB) as the maximum device block size. This value may not be used for the block size of a given tape drive because internal nsrmmd values can override the value you specify. Do not define this logical name except at the direction of software support personnel. (See the NSR$BLOCK_SIZE_devnam logical name for a supported method of increasing the block size beyond the default of 32 KB.)
NSR$MKDRIVER_64K Allows you to specify block sizes greater than 63 KB. Note, however, that the OpenVMS MKDRIVER does not support values greater than 65,535 bytes. Therefore, defining this logical name can cause nsrmmd to fail to properly initialize, write, and read tape media.
Note: Define this logical name only at the request of software support personnel.
90 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Logical Names
Table 11 NetWorker logical names (page 6 of 10)
Logical name Description
NSR$MAX_WRITESZ, Specifies the maximum size of TCP/IP writes during a NSR_CHUNK_SIZE save operation. For the TCPware TCP/IP software, this value should be less than or equal to 65,440 bytes. The recommended value for the TCPware software is 65,024 bytes. The NSR_CHUNK_SIZE logical name has the same effect as the NSR$MAX_WRITESZ logical name.
NSR$NO_AIO Disables asynchronous I/O in nsrmmd.
NSR$NO_CASE_SENSITIVE When defined to any value, prevents the NetWorker software from automatically setting the process parse style to EXTENDED and the case lookup method to SENSITIVE, which it does when restoring or retrieving data from an ODS-5 disk or viewing data from an ODS-5 disk with nsrinfo.
NSR$NO_HW_COMPRESS When defined, forces nsrmmd to disable compression for all tape units.
Note: Define this logical name only at the request of software support personnel.
NSR$NO_DEFAULT_WILDCARD Changes how wildcards can be used in a directive filename ([+]directive-name[:file-name]). The default behavior allows the use of an asterisk (*) wildcard character to match one or more characters within a portion of a filename or the entire filename. Both * and *.* default to *.*;*. When this logical is defined to any value, an asterisk can be used to match one or more characters only within a single portion of the filename (filename, extension, or version), but not the entire filename. Missing portions do not default to a wildcard.
NSR$PA_ORDER Controls the order in which primary files and aliases are saved. Setting this logical name ensures that primary files are saved first in the save process.
Note: Define this logical name only at the request of software support personnel.
NSR$PACKACK_TIMEOUT When defined, specifies the time, in seconds, that nsrmmd should wait after issuing an IO$_PACKACK function. By default, the timeout value is 5 seconds.
NSR$PATH_TRACE When defined, causes the NetWorker software to trace the entry and exit of functions used to convert between OpenVMS file specifications and UNIX-style file specifications.
NSR$PIPE_SIZE Specifies the size, in bytes, of the internal buffers used for pipe (mailbox) structures.
NetWorker Logical Names 91 Logical Names
Table 11 NetWorker logical names (page 7 of 10)
Logical name Description
NSR$PRE_saveset_name Used to implement save set-based preprocessing. The saveset_name is the name of the save set associated with the preprocessing function. This logical name should be defined as the name of a DCL command file that the save program executes when the specified save set is started. For additional details, see “Pre- and postprocessing operations” on page 27.
NSR$PRINT_FIDTREE When defined, causes the save program to print out a list of files processed during the save.
Note: Define this logical name only at the request of software support personnel.
NSR$PST_saveset_name Used to implement save set-based post-processing. The saveset_name is the name of the save set associated with the post-processing function. This logical name should be defined as the name of a DCL command file that the save program executes after it has completed its normal backup operations. For additional details, see “Pre- and postprocessing operations” on page 27.
NSR$QUIT_FLAG In general, causes all NetWorker programs that check for user-initiated stop signals to shut down.
Note: Define this logical name only at the request of software support personnel.
NSR$RAWASM_COMPRESS When defined to any value (1, for example), causes the save program to compress the data that is being backed up during a physical disk backup with the rawasm directive. For a single disk backup define this logical name prior to starting the save process and then deassign it afterwards. When backing up all disks, define this logical as a systemwide logical (/SYSTEM). You can also use pre- and postprocessing to define and deassign this logical name.
NSR$RAWASM_NOFLUSH Prevents the save program from flushing device caches for devices that are mounted with ODS-2 or ODS-5 file systems during a physical disk backup. By default, the save program attempts to flush all device caches to produce the most consistent physical backup possible. This logical name has no effect on devices that are mounted /FOREIGN.
NSR$RAWASM_NOLOCK Prevents the save program from locking a specified ODS-2 or ODS-5 mounted volume against new allocations during a physical disk backup. By default, save locks the device against new allocations to produce the most consistent physical backup possible. This logical name has no effect on devices that are mounted /FOREIGN.
92 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Logical Names
Table 11 NetWorker logical names (page 8 of 10)
Logical name Description
NSR$RECOVER_MCP Specifies the disk:[directory] that represents the "most common path" (MCP) to the files within the save set that is being recovered. Define this logical before using the save set recover mode to recover files from a save set that was assigned an arbitrary name (as opposed to a name that represents the MCP) during a user-initiated save operation. Otherwise, the recover program may exhibit unexpected behavior.
Note: The disk and directory name that you specify must be identical to the filename prefix stored in the NetWorker index for the files being recovered.
You do not need to define this logical when using browser or automatic recover modes.
NSR$RES Defines a location for the NetWorker resource files and the SERVERS file, which holds the names of NetWorker servers that can back up this client computer. The NSR$STARTUP command procedure defines this logical.
NSR$RPC_TIMEOUT_VALUE Defines the number of minutes of idle time before an application-level keepalive timestamp message is sent from the nsrexecd process, indicating (to the network software) that it is not idle.
NSR$SCAN_PIPE_SIZE Sets the buffer size used for the scanner program when piping data from tape to the output device. By default, this value is 8,192 bytes.
Note: Define this logical name only at the request of software support personnel.
NSR$SCSI_DISCTMO Changes the value used by the NetWorker SCSI subsystem for SCSI disconnect timeouts.
Note: Define this logical name only at the request of software support personnel.
NSR$SCSI_PHASETMO Changes the value used by the NetWorker SCSI subsystem for SCSI phase transition timeouts.
Note: Define this logical name only at the request of software support personnel.
NSR$SPECIFIC Specifies the location of the NetWorker node-specific directory tree. All files unique to a single node in a cluster are located in that cluster node's NSR$SPECIFIC directory. The location of this directory tree depends on the /DESTINATION qualifier value provided to the PCSI utility during the installation of NetWorker and on the name of the associated node.
NetWorker Logical Names 93 Logical Names
Table 11 NetWorker logical names (page 9 of 10)
Logical name Description
NSR$STATIC_EVENT_FLAGS When defined to any value, disables dynamic event flag allocation, the default method used by the nsrexecd daemon to manage event flags. Dynamic allocation supports the use of more AFTDs and nsrmmd processes than static allocation. However, in environments with few or no AFTDs and slow performance, disabling dynamic event flag allocation may improve performance.
NSR$STORE_ACL_INDEX Causes the save program to store file access control lists (ACLs) in the NetWorker index. By default, all ACLs are stored on tape media, along with file data.
Note: Define this logical name only at the request of software support personnel.
NSR$SYSROOT A search list logical name that is predefined to include NSR$SPECIFIC and NSR$COMMON, listed in the order shown here.
NSR$SYSTEM Defines the top-level directory of the NetWorker directory tree. The NSR$STARTUP command procedure defines this logical.
NSR$TCP_KEEPALIVE_DEFAULT Defines whether the following logicals are recognized: NSR$TCP_KEEPIDLE NSR$TCP_KEEPINTVL NSR$TCP_KEEPCNT The value is either 1 for on or 0 (default) for off
NSR$TCP_KEEPIDLE Defines the initial idle interval (in seconds) before any keepalive action occurs. The default value is 72000 seconds.
NSR$TCP_KEEPINIT Specifies the number of seconds to wait before the TCP connection attempt times out. The default value is 75 seconds.
NSR$TCP_KEEPINTVL Defines the number of seconds between keepalive messages. The default value is 75 seconds.
NSR$TCP_KEEPCNT Defines the number of keepalive messages that will be sent before timeout occurs. The default value is 8.
NSR$TCP_RECOVERBUF_SIZ Causes the recover program to use a socket with buffering of the specified size in bytes. If you define this logical name to the string "DEFAULT", the recover program uses the system default setting for TCP sockets. When this logical is undefined, a 30 KB buffer is used.
NSR$TCP_SAVEBUF_SIZ Causes the save program to use a socket with buffering of the specified size in bytes. If you define this logical name to the string "DEFAULT", the save program uses the stem default setting for TCP sockets. When this logical is undefined, a 30 KB buffer is used.
NSR$TMP Defines a location for temporary work files created by the NetWorker utilities. This logical is defined by the NSR$STARTUP command procedure.
94 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Logical Names
Table 11 NetWorker logical names (page 10 of 10)
Logical name Description
NSR$USE_BUFSIZ_ONLY When defined, forces the nsrmmd to use whatever values are currently set for the device density and compression, ignoring more optimum values that could be used.
Note: Define this logical name only at the request of software support personnel.
NSR$USE_DEFAULT_TAPE_INFO When defined, forces nsrmmd to use the default values associated with a tape unit for such things as density, compression, and buffer size. Use the SHOW DEVICE/FULL.command to determine these default values.
Note: Define this logical name only at the request of software support personnel.
NSR$VERBOSE_FLAG Specifies the level of verbosity for all NetWorker programs. Define this logical to an integer value—the larger the value, the more verbose the program output becomes. The effect of this logical is similar to specifying the -v option, which is available for use with several NetWorker commands.
Note: Define this logical name only at the request of support personnel. Its use may interfere with the normal operation of the NetWorker software.
NetWorker Logical Names 95 Logical Names
96 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide APPENDIX B NetWorker Module for Oracle Invisible Body Tag
This appendix covers these topics:
◆ Overview of the NetWorker Module for Oracle...... 98 ◆ Installing the Oracle module ...... 98 ◆ Configuring the Oracle module ...... 98 ◆ Manual Oracle backups...... 99 ◆ Server-initiated Oracle backups ...... 103 ◆ Restoring and recovering Oracle data ...... 108
NetWorker Module for Oracle 97 NetWorker Module for Oracle
Overview of the NetWorker Module for Oracle
The NetWorker Module for Oracle is an add-on module that enables the NetWorker software to back up an online Oracle database, in tandem with the Oracle Media Management API (SBT interface) and Oracle’s Recovery Manager (RMAN). This module runs on the OpenVMS operating system and is included in the NetWorker software for OpenVMS distribution. It is not distributed separately. The NetWorker Module for Oracle supports both scheduled (server-initiated) and manual (client-initiated) backups of Oracle data. Installing the Oracle module
You must install both the NetWorker client software and the NetWorker Module for Oracle on your Oracle Server host in order to use this module to back up your Oracle database. You can install both components as a new installation by using the PRODUCT INSTALL command, or add the Oracle module to an existing NetWorker client by using the PRODUCT RECONFIGURATION command.
Note: If you use the PRODUCT RECONFIGURE command to add the Oracle module, be sure to re-apply the latest ECO for the NetWorker software. The PRODUCT RECONFIGURE command rolls back any ECOs that have been added since the base product kit was installed.
When prompted whether to use defaults for all options, answer n[o]. You will then be prompted to install optional components, including the NetWorker for Oracle module. Answer y[es] to install Oracle database backup capability. For example:
Do you want the defaults for all options? [YES] n Add Storage Node Capability [YES] y Add Oracle/Rdb Database Backup Capability [NO] n Add Oracle Database Backup Capability [NO] y
Note: If you accept the default installation options, you will not be prompted to install the NetWorker Module for Oracle.
Refer to the Dell EMC NetWorker Administration Guide for complete installation and product reconfiguration instructions. Postinstallation tasks related to the NetWorker Module for Oracle are described in the next section. Configuring the Oracle module
When you choose to install the Oracle module, the installation procedure provides the following files to the NSR$SYSTEM directory: LIBNWORA_SHR.EXE NSR$ORA_BACKUP_TEMPLATE.COM NSR$ORA_BACKUP_TEMPLATE.RCV NSRORABCK.EXE NSRORASTART.EXE
98 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle
The first file (LIBNWORA_SHR.EXE) is the library file. Instruct the Oracle software to use NetWorker as its Media Management Library (MML) by explicitly overriding the specified MML as follows:
◆ Oracle 9i Release 2 — In the RMAN script, use the parms option of the allocate channel command to define the SBT_LIBRARY parameter to logical name LIBNWORA_SHR. The NetWorker startup procedure defines this logical name, which provides the complete path to the NetWorker library. For example, use RMAN to connect to the target database and then:
rman> run 2> { 3> allocate channel c1 device type 'SBT_TAPE' 3> parms='SBT_LIBRARY=LIBNWORA_SHR'; 3> }
Note: The Oracle 9i Release 2 release notes state that you can define the LIBOBK logical name as an alternative method for overriding the specified MML. This method does not work. To ensure that Oracle uses the NetWorker library as its MML, use the parms option of the allocate channel command as shown here
◆ Oracle 10g — In the RMAN script, use the parms option of the allocate channel command to define the SBT_LIBRARY parameter to specify the complete path to the NetWorker library. Do not use a logical name. For example:
rman> run 2> { 3> allocate channel c1 device type 'SBT_TAPE' 3> parms='SBT_LIBRARY=NSR$SYSTEM:LIBNWORA_SHR.EXE'; 3> } Other files provided by the installation include NSRORASTART.EXE and NSRORABCK.EXE, which are used by the NetWorker software to manage server-initiated backups as described in “Server-initiated Oracle backups” on page 103, and two template files that you can use when creating scripts as described in “Creating RMAN and DCL scripts for server-initiated backups” on page 104. Manual Oracle backups
To perform a manual (client-initiated) backup of an Oracle database, you execute an RMAN script on the Oracle Server host (the OpenVMS NetWorker client) that:
◆ Contains the appropriate RMAN backup commands for the type of backup that you want to perform.
◆ Specifies the NetWorker Module for Oracle as the Media Management device.
◆ Sets required and optional environment variables for the backup. You can create a new script for manual Oracle backups, as described in the next section, or modify your existing scripts accordingly.
Manual Oracle backups 99 NetWorker Module for Oracle
Creating RMAN scripts for manual backups
Create the RMAN script for the preferred type of manual Oracle backup on the Oracle Server host. RMAN backup scripts can be stored as flat ASCII files. Alternatively, if a Recovery Catalog is used, backup scripts can be stored in the Recovery Catalog database. For more information on storing the backup scripts in the Recovery Catalog database, refer to the appropriate Oracle backup and recovery documentation. Use the following guidelines when creating your RMAN script for manual Oracle backups that will use the NetWorker Module for Oracle:
◆ To specify the NetWorker Module for Oracle as the Media Management device, set the type option in the RMAN allocate channel command to 'SBT_TAPE'. For example:
allocate channel t1 device type 'SBT_TAPE';
◆ To set required (NSR_SERVER and NSR_GROUP) and optional NetWorker environment variables, use one or more RMAN send commands in your script. For example:
send "NSR_ENV=(NSR_SERVER=nwsvr,NSR_GROUP=Oracle)"; The next section provides more information on using the RMAN send command to set NetWorker environment variables.
Note: The typical method of defining process or job-wide logical names for these environmental variables is not supported.
For more information on how to write RMAN scripts, refer to the appropriate Oracle backup and recovery documentation.
Using the send command to set NetWorker environment variables You can use the send command in the run job of an RMAN script for manual Oracle backups or specify it as an option in an RMAN command line. To run the send command from the RMAN script, enter the command in the following format, at the required point within the run command brackets:
send [device_type 'device_specifier' | channel channel_id] "NSR_ENV=(var_name1=value1[, var_name2=value2, ...])" The device_type and channel options shown in the syntax diagram are optional. You may include one of these options in your send command, but not both. The device_type option sets the environment variables for all channels of the specified backup tape device (in this case 'SBT_TAPE'). The channel option sets the environment variables for specified channels only. Refer to the appropriate Oracle backup and recovery documentation for more information on channels and the use of these options. Typically, you will use the send command with no option, only the quoted NSR_ENV string. This sets the environment variables for all allocated channels. Follow these syntax rules when entering the quoted NSR_ENV command string in the send command:
◆ The maximum length of the command string is restricted by Oracle to 512 bytes, including the terminating NULL.
◆ The NSR_ENV keyword and the variable names must be entered in all uppercase. (See Table 12 on page 102 for a list of variable names and their descriptions.)
100 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle
◆ Between the NSR_ENV keyword and the left parenthesis, an equal sign and spaces are optional. For example, all of these commands are correct:
send "NSR_ENV = (NSR_SERVER=server1)" send "NSR_ENV=(NSR_SERVER=server1)" send "NSR_ENV (NSR_SERVER=server1)" send "NSR_ENV(NSR_SERVER=server1)"
◆ The parentheses in the command string are mandatory.
◆ Inside the parentheses, there must be one or more NetWorker environment variable names and the corresponding variable values.
◆ Spaces are not allowed around the equal signs. A space before an equal sign is interpreted as part of the variable name; a space after an equal sign becomes part of the variable’s value.
◆ Commas separating the var_name=value entries are required.
◆ Comments are not allowed inside the quotes. In the example that follows, "# NSR_SERVER" is interpreted as the name of the first variable:
run { allocate channel t1 type 'SBT_TAPE'; send "NSR_ENV=( # NSR_SERVER=server1, NSR_CLIENT=oracle)";
◆ A send command in an RMAN script can span multiple lines. For example:
send "NSR_ENV=( NSR_SERVER=server1, NSR_CLIENT=oracle)";
◆ You may specify multiple send commands in your script. The NetWorker software appends the information in subsequent send commands to the current list of environment variables. If a duplicate environment variable is encountered, the last specified value for that variable is used. To run the send command as an option of the rman command on the operating system command line, enter the command in the following format: rman send "'NSR_ENV=(var_name1=value1[, var_name2=value2, ...])'" Note that the device_type and channel options are not valid in send commands entered at the operating system command line. For more information on using send in an RMAN command line, refer to the appropriate Oracle backup and recovery documentation.
Manual Oracle backups 101 NetWorker Module for Oracle
Table 12 lists the environment variables (in alphabetical order) that can be set with the send command in an RMAN script or command line:
Table 12 NetWorker environment variables
Variable Description
NSR_CHECKSUM Specifies whether the NetWorker software uses a checksum to verify the backup data.
NSR_CLIENT Specifies the NetWorker Client resource to use for a backup or restore session.
NSR_COMPRESSION Specifies whether the NetWorker software performs compression on the backup data.
NSR_DEBUG_FILE Enables debugging by specifying the complete pathname of the log file on the OpenVMS client.
NSR_ENCRYPTION Specifies whether the NetWorker software performs encryption on the backup data.
NSR_GROUP Specifies the NetWorker group to use for the backup.
NSR_SAVESET_ Specifies the date when the entry for the backup is to be removed from BROWSE the NetWorker client index. (See “Valid date/time formats for NetWorker commands” on page 22 for information on specifying dates and times.)
NSR_SAVESET_ Specifies the date when the save set becomes recyclable. (See “Valid EXPIRATION date/time formats for NetWorker commands” on page 22 for information on specifying dates and times.)
NSR_SERVER Specifies the name of the NetWorker server to use for the backup.
Example 18 Basic RMAN script for a manual database backup
This example shows a sample RMAN script designed for a manual (client-initiated) backup of an Oracle database. This script backs up tablespace TBS1 from the dbname database. Note that the device type is 'SBT_TAPE' and the send command sets the required environment variables (NSR_SERVER and NSR_GROUP) to identify the name of the NetWorker server (NWSRV) and group (Oracle).
rman target sys/admin@dbname catalog rman_usr/rman_pwd@recmgr run { allocate channel t1 device type 'SBT_TAPE'; send "NSR_ENV=(NSR_SERVER=nwsvr,NSR_GROUP=Oracle)"; backup tablespace TBS1; release channel t1; } exit exit
Example 19 RMAN script with multiple send commands and an optional variable
The next sample RMAN script, which was also designed for a manual backup, backs up the payroll database. It specifies device type 'SBT_TAPE' and uses multiple send commands to specify the name of the NetWorker server (NWSRV) and the name of the group to use (Oracle Backup). It also sets the optional NSR_DEBUG_FILE variable to specify the name of a file to receive debugging output, which is useful if the script does not work as expected.
102 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle
rman target sys/admin@payroll catalog rman_db1/rman_db1@recmgr run { allocate channel t1 type 'SBT_TAPE'; send "NSR_ENV=(NSR_DEBUG_FILE=NSR$LOGS:DMOBCK.LOG)"; send "NSR_ENV=(NSR_SERVER=nwsrv); send "NSR_EVN=(NSR_GROUP=Oracle Backup)"; backup full filesperset database; backup filesperset 20 archivelog all; release channel t1; } exit Server-initiated Oracle backups
Server-initiated backups of an Oracle database can be scheduled by using the Group and Schedule resources of the NetWorker server in the same manner in which they are used for other NetWorker client backups. For more information on scheduling backups with NetWorker, refer to the Dell EMC NetWorker Administration Guide. To set up your Oracle Server host for NetWorker-server-initiated backups, you must create an RMAN script and a special DCL (.COM) script. You must also configure Client resources on the NetWorker server. The following sections provide more detail:
◆ “Creating RMAN and DCL scripts for server-initiated backups” on page 104
◆ “Configuring the NetWorker Client resource for Oracle backups” on page 107 A server-initiated backup of an Oracle database starts when the NetWorker server contacts the nsrexecd daemon on the client node. In response, the nsrexecd starts the savefs program to validate the requested backup. When the savefs procedure completes, the NetWorker server requests that the nsrexecd start one or more saves (depending on the Parallelism attribute setting and the number of save sets defined in the Client resource). For typical (non-Oracle) backups, the nsrexecd starts the save program located in the NSR$SYSTEM directory. However, for Oracle backups, the nsrexecd starts an alternate save program named nsrorastart. The nsrorastart program initializes the save environment and then starts another fully detached process named nsrorabck, which is responsible for reading your DCL script and executing the RMAN commands to do the actual backup. The nsrorabck program initializes itself and scans your Oracle backup DCL script for any environment variables. From the DCL script, nsrorabck determines the name of the RMAN script to execute as well as other operating variables. Once these variables are established, the nsrorabck program executes any preprocessing script you have specified, and based on the results of that command, executes the RMAN backup, and finally executes any postprocessing script you have specified. When the nsrorabck program completes, the nsrorastart program regains control and informs the NetWorker server of the results of the database backup. Settings on the NetWorker server, including those defined in Client resources that are associated with your OpenVMS client system and associated Group, Pool, and Device resource settings, are used during the database backup. To change these settings, you need to modify the appropriate resources on the NetWorker server.
Server-initiated Oracle backups 103 NetWorker Module for Oracle
Creating RMAN and DCL scripts for server-initiated backups
For server-initiated backups, create two scripts on the Oracle Server host: an RMAN script (.RCV) and a DCL (.COM) script. The NetWorker installation procedure provides the following script templates to help simplify this task:
◆ NSR$SYSTEM:NSR$ORACLE_BACKUP_TEMPLATE.COM
◆ NSR$SYSTEM:NSR$ORACLE_BACKUP_TEMPLATE.RCV The following sections provide more details on each script type:
◆ “The DCL script” on page 104
◆ “The RMAN script for server-initiated backups” on page 106 The DCL script The template DCL script provided by the NetWorker Module for Oracle installation (NSR$SYSTEM:NSR$ORACLE_BACKUP_TEMPLATE.COM) includes sample definitions for a series of symbols that can be used during server-initiated backups. All symbol definitions are commented out by default. You must define the ORACLE_HOME and NSR_RMAN_SCRIPT symbols. All other symbol definitions are optional.
Do not change local symbol definitions to global symbol definitions. This will cause the backup process to fail because the NetWorker software cannot properly interpret a global symbol definition.
104 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle
Table 13 describes the symbols you can define in the DCL script to control server-initiated backups of Oracle data. Refer to the comments in the DCL script itself for more information about these symbols and the proper syntax for setting them.
Table 13 Local Symbols in DCL Script for Server-Initiated Backups (page 1 of 2)
Symbol Description
ORACLE_HOME Specifies the location of the Oracle Server installation. The NetWorker Module for Oracle uses this value to determine the location of the RMAN program, which is expected to be located in either the [.BIN] or [.RDBMS] subdirectory of ORACLE_HOME. This symbol definition is required if NSR_ORACLE_BKUP_CMD is not defined.
NSR_ORACLE_BKUP_CMD Specifies the full file specification for the RMAN program. By default, the nsrorabck program will look in the [.RDBMS] and [.BIN] subdirectories of ORACLE_HOME. If the location of RMAN.EXE is different on your system, define this symbol to notify NetWorker of its location.
NSR_ORACLE_INIT Provides the name of the file that initializes a process for Oracle operations. By default, the NetWorker Module for Oracle searches in ORACLE_HOME and the [.UTIL] subdirectory of ORACLE_HOME for the file ORAUSER.COM. If found, this initialization file is executed prior to the backup. If the file is not found, no initialization occurs within the backup process. This can result in failure because the various Oracle logical names may not be available to the backup process. If your Oracle initialization file is not located in either default location, specify the full file specification of the initialization file that the backup process should use.
NSR_RMAN_SCRIPT Specifies the name and location of the RMAN script that should be executed as part of this backup. This symbol definition is required.
NSR_ORA_USER Specifies the username of the OpenVMS account that will be used to run the nsrorabck command. By default, the NetWorker Oracle backup is run under the NSR$EXECD account. Because the backup uses Oracle services, you must either grant the NSR$EXECD account appropriate Oracle rights to back up the target databases or direct NetWorker to run the backup under another username by defining this symbol.
Note: If the username you specify does not have the same or greater privileges than the NSR$EXECD account, you may have to install the nsrorabck program (nsrorabck.exe) with privileges, as described in the Dell EMC NetWorker HP OpenVMS Version Installation Guide.
NSR_RMAN_ARGUMENTS Specifies additional RMAN parameters. Enclose this value in quotation marks to ensure that is correctly passed to RMAN.
NSR_ORA_SCRIPT_OUTPUT Specifies the full file specification to use as the SYS$OUTPUT device for the nsrorabck program that is invoked by this DCL procedure.
Server-initiated Oracle backups 105 NetWorker Module for Oracle
Table 13 Local Symbols in DCL Script for Server-Initiated Backups (page 2 of 2)
Symbol Description
NSR_RMAN_OUTPUT Provides the option to capture the RMAN standard output if the RMAN "msglog" or "log" command line option is not set. The connect strings will be hidden in this file.
NSR_PRECMD Specifies a command or command procedure that nsrorabck will run before the Oracle backup. The specified command or command script will be run once for every save set specified in the Client resource.
NSR_POSTCMD Specifies a command procedure that will be run after the RMAN backup script completes. The specified command procedure will be run once for every save set specified in the Client resource.
NSR_DEBUG_FILE Specifies the full file specification of the file into which NetWorker will write debug and trace messages.
The RMAN script for server-initiated backups The RMAN script that you create on the Oracle Server host for use during server-initiated backups differs from the one intended for manual backups.
For scheduled backups, do not include send as part of the allocate channel command. The send command must be separate.
For example, NMO does not support the following for scheduled backups:
allocate channel t1 type ‘SBT_TAPE’ send ‘NSR_ENV=(NSR_SERVER=mars.emc.com)’; The following is the correct form of the commands:
allocate channel t1 type ‘SBT_TAPE’; send channel t1 ‘NSR_ENV=(NSR_SERVER=mars.emc.com)’; With automatic channel allocation, specifying the send command before the backup or restore command causes the following error:
RMAN-06422: no channels found for SEND command The installation procedure for the NetWorker Module for Oracle provides the following template RMAN script for server-initiated backups:
NSR$SYSTEM:NSR$ORACLE_BACKUP_TEMPLATE.RCV This template includes a sample script that looks similar to the following:
connect target target_user/target_passwd@target_Netservicename; connect rcvcat rcvcat_user/rcvcat_passwd@rcvcat_Netservicename; run { allocate channel t1 type 'SBT_TAPE' ; allocate channel t2 type 'SBT_TAPE' ; set command id to 'xxx' ; backup full filesperset 4 format /FULL_%d_%u/ database; release channel t1;
106 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle
release channel t2; } exit Note the following guidelines when modifying this script:
◆ Do not enter the rman command in the script. The nsrorabck command will start an RMAN session and execute this script on your behalf.
◆ The connect target and connect rcvcat statements are required syntax for a server-initiated backup.
◆ To specify the NetWorker Module for Oracle as the Media Management device, the type option of the allocate channel statements must specify 'SBT_TAPE', as shown.
◆ Other RMAN statements are optional and depend on the type of backup. Refer to the appropriate Oracle backup and recovery documentation for additional information on these commands.
Configuring the NetWorker Client resource for Oracle backups
A separate Client resource is required for Oracle database backups. This allows definition of the required backup command for server-initiated Oracle database backups and allows you to associate Oracle backups with different backup groups and storage pools. When you create the Client resource for Oracle database backups, define the following attributes (in addition to default values assigned to a Client resource):
◆ Save Set — The Save Set attribute identifies the Oracle backup script that will be used to back up your database. (In a more typical Client resource, the Save Set attribute identifies the highest level directory of the data to be backed up to the NetWorker server.) Identify the full file specification of the DCL (.COM) script that you created on the OpenVMS client. If you created multiple DCL scripts (to run more than one Oracle backup using the same Client resource, for example), enter the file specification for each script as a separate line in the Save Set attribute.
◆ Backup Command — The Backup Command attribute of a Client resource enables you to specify the execution of a custom save program for backing up client data. In Client resources for Oracle backups, this attribute must specify the backup command nsrorastart. During a regular (non-Oracle) client backup, the nsrexecd starts the save program located in the NSR$SYSTEM directory. When you define the Backup Command to be nsrorastart, the nsrexecd starts the nsrorastart program (also located in the NSR$SYSTEM directory) instead. (See “Server-initiated Oracle backups” on page 103 for more information.)
◆ Group — If you have created a special backup group and associated pool for Oracle database backups, be sure to select the appropriate group when defining the Group attribute of the Client resource. The Dell EMC NetWorker Administration Guide includes step-by-step instructions for creating a Client resource on the server.
Server-initiated Oracle backups 107 NetWorker Module for Oracle
Restoring and recovering Oracle data
This section provides information related to Oracle data restore operations and Oracle database recovery.
Preparing to restore Oracle data
During an Oracle backup, the NetWorker server adds an entry for each backup piece in the online client file index and records the location of the data in the media database. These entries provide information required to restore every Oracle data object that is backed up. They are maintained as follows:
◆ The client file index entry is maintained until the browse policy specified for the client’s save set expires.
◆ The media database entry is maintained until the retention policy specified for the client’s save set expires. When the retention policies for all the save sets on a backup volume expire, the volume becomes recyclable and eligible for automatic relabeling by the NetWorker server. The save set entries, however, remain in the media database until the volume is actually relabeled. When the volume is relabeled, the data on it becomes inaccessible and can no longer be restored. The NetWorker Module for Oracle uses the client file index entries to restore Oracle backup pieces. Set the browse policy to a period long enough to retain the client index entries for restoring the Oracle backup pieces.
Note: After a browse policy expires, the NetWorker scanner program can be used to rebuild the online indexes. However, index entries regenerated by the scanner might cause the NetWorker indexes to become unsynchronized with the RMAN catalog and lead to problems. To avoid this, ensure that the backup pieces have unique names.
For more information on browse and retention policies, refer to the Dell EMC NetWorker Administration Guide.
Creating the RMAN restore script
The process for restoring and recovering an Oracle database is similar to that used for a manual backup. You run an RMAN script that contains the appropriate restore command, allocate channel command type ('SBT_TAPE'), and send commands that specify nondefault NetWorker servers or a particular group or client. For example, the following RMAN script performs a restore of an Oracle tablespace using the (remote) NetWorker server mars.emc.com. The Oracle data is restored to the NetWorker client jupiter.emc.com.
run { allocate channel t1 type 'SBT_TAPE'; allocate channel t2 type 'SBT_TAPE'; send "NSR_ENV=(NSR_SERVER=mars.emc.com, NSR_CLIENT=jupiter.emc.com)"; sql ’alter tablespace users offline immediate’; restore (tablespace users); sql ’alter tablespace users online’; release channel t1;
108 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle
release channel t2; } For more information on setting environment variables in an RMAN script, see “Using the send command to set NetWorker environment variables” on page 100.
Restoring an Oracle database
Before starting a restore of an Oracle database, ensure that the volume required for the restore operation is mounted in a configured backup device. If auto media management is enabled for a tape device or autochanger, ensure that the tape is loaded in the tape device or autochanger for the NetWorker server to use automatically. To start the restore operation, run the RMAN restore script that you created (as described in “Creating the RMAN restore script” on page 108) from the Oracle Server host. For example, if the RMAN restore script shown on page 108 is stored in the file DISK1:[SCRIPTS]RESTORE.RCV and the Net service has been configured to connect to the databases payroll and rcvcatdb, you can start the Oracle restore by typing the following command:
rman target internal/oracle@payroll rcvcat - rman/rman@rcvcatdb cmdfile ’disk1:[scripts]restore.rcv’
Restoring an Oracle database to a different host In some cases, an Oracle database must be restored to a system other than the one that was originally backed up. To restore an Oracle database to different system: 1. On the NetWorker server that contains the backup to be restored, specify the hostname of the different system for the Remote Access attribute in the Client resource of the original system. (Refer to the Dell EMC NetWorker Administration Guide for instructions on editing Client resource attributes.) 2. On the system where the Oracle data is to be restored, install and configure the NetWorker Module for Oracle. 3. Ensure that RMAN is installed and configured on that system. 4. Create an appropriate RMAN restore script. 5. In the RMAN script, set the NSR_SERVER environment variable to the name of the NetWorker server that contains the backup. 6. Set the NSR_CLIENT environment variable to either the name of the NetWorker client (Oracle Server host) that was backed up or the value of NSR_CLIENT used during the backup. 7. Use the appropriate RMAN command to run the script to restore the Oracle database files.
Completing the Oracle data recovery
After restoring the NetWorker Module for Oracle backups of the Oracle data by using the RMAN utility, complete the data recovery if required. To recover the Oracle data, use the appropriate Oracle commands to apply the archived redo logs and online redo logs. There are two ways to run the Oracle recovery commands:
Restoring and recovering Oracle data 109 NetWorker Module for Oracle
◆ Include the Oracle commands in the RMAN restore script.
◆ Run the commands after the RMAN restore script has completed successfully. For more information on Oracle data recovery procedures, refer to the appropriate Oracle backup and recovery documentation.
Oracle database recovery
Refer to the Oracle backup and recovery documentation for information on how to prepare for recovery of an Oracle database after a disaster.
110 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide APPENDIX C NetWorker Module for Oracle Rdb Invisible Body Tag
This appendix covers the following topics:
◆ Overview of the NetWorker Module for Oracle Rdb...... 112 ◆ Installing the Oracle Rdb module...... 112 ◆ Configuring the Oracle Rdb module ...... 112 ◆ Manual Oracle Rdb backups...... 112 ◆ Server-initiated Oracle Rdb backups...... 113 ◆ Restoring Oracle Rdb data...... 118 ◆ Known restrictions ...... 119
NetWorker Module for Oracle Rdb 111 NetWorker Module for Oracle Rdb
Overview of the NetWorker Module for Oracle Rdb
The NetWorker Module for Oracle Rdb is an add-on module that enables the NetWorker software to back up an online Oracle Rdb database, in tandem with the Oracle Media Management API (SBT interface) and RMU, the Oracle Rdb management utility. This module runs on the OpenVMS operating system and is included in the NetWorker software for OpenVMS distribution. It is not distributed separately. The NetWorker Module for Oracle Rdb supports both scheduled (server-initiated) and manual (client-initiated) backups of Oracle Rdb data. Installing the Oracle Rdb module
You must install both the NetWorker client software and the NetWorker Module for Oracle Rdb on your Oracle Rdb system in order to use this module to back up your Oracle Rdb database. You can install both components as a new installation by using the PRODUCT INSTALL command, or add the Oracle Rdb module to an existing NetWorker client by using the PRODUCT RECONFIGURATION command. When prompted whether to use defaults for all options, answer n[o]. You will then be prompted to install optional components, including the NetWorker for Oracle Rdb module. Answer y[es] to install Oracle Rdb database backup capability. For example:
Do you want the defaults for all options? [YES] n Add Storage Node Capability [YES] y Add Oracle/Rdb Database Backup Capability [NO] y Add Oracle Database Backup Capability [NO] n
Note: If you accept the default installation options, you will not be prompted to install the NetWorker Module for Oracle Rdb.
Refer to the Dell EMC NetWorker HP OpenVMS Version Installation Guide for complete installation and product reconfiguration instructions. Configuring the Oracle Rdb module
To instruct Oracle RMU to use NetWorker as its media librarian, the RMU$LIBRARIAN_PATH logical name must be defined to identify the location of the NetWorker Module for Oracle Rdb, which resides at: NSR$SYSTEM:LIBNWRDB_SHR.EXE This logical name definition is automatically added to your NetWorker startup command procedure. Therefore, no manual post-installation tasks are required. Manual Oracle Rdb backups
To perform a manual (client-initiated) backup of an Oracle Rdb database, you do the following on the Oracle Rdb system (the OpenVMS NetWorker client):
◆ At the DCL prompt, define logical names to set required (NSR_SERVER and NSR_GROUP) and optional NetWorker environment variables for the backup. The next section provides more information on setting NetWorker environment variables.
112 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle Rdb
◆ Type the appropriate RMU/BACKUP/LIBRARY command or one of its variants to perform the type of backup that you want to perform. (Refer to the Oracle Rdb documentation for a list of valid RMU/BACKUP commands.)
◆ When the backup completes, deassign the logical names to ensure they do not affect subsequent NetWorker functions.
Defining logical names to set NetWorker environment variables
Before executing a manual backup from an Oracle Rdb system, you must set the NetWorker environment variables on the client system. You can do this by defining logical names for these values. At a minimum, you must define the following logical names:
◆ NSR_SERVER — Specifies the name of the NetWorker server to use for this backup.
◆ NSR_GROUP — Specifies the NetWorker group to use for this backup. For example:
DEFINE NSR_SERVER "nwsvr" DEFINE NSR_GROUP "Oracle_Rdb" For a list of other NetWorker environment variables that can be set for a manual backup, see Table 12 on page 102.
Note: When the backup completes, deassign the backup-specific logical names to ensure that they do not interfere with subsequent NetWorker operations. For example: DEASSIGN NSR_SERVER DEASSIGN NSR_GROUP
Server-initiated Oracle Rdb backups
Server-initiated backups of an Oracle Rdb database can be scheduled by using the Group and Schedule resources of the NetWorker server in the same manner in which they are used for other NetWorker client backups. For more information on scheduling backups with NetWorker, refer to the Dell EMC NetWorker Administration Guide. To set up your Oracle Rdb system for NetWorker server-initiated backups, you must create an Rdb backup script and configure Client resources on the NetWorker server, as described further in the sections that follow. You may also want to test the backup script to ensure that it is working properly. A server-initiated backup of an Oracle Rdb database starts when the NetWorker server contacts the nsrexecd daemon on the client node. In response, the nsrexecd starts the savefs program to validate the requested backup. When the savefs procedure completes, the NetWorker server requests that the nsrexecd start one or more saves (depending on the Parallelism attribute setting and the number of save sets defined in the Client resource). For typical (non-Oracle Rdb) backups, the nsrexecd starts the save program located in the NSR$SYSTEM directory. However, for Oracle Rdb backups, the nsrexecd starts an alternate save program named nsrrdbstart, which is also located in the NSR$SYSTEM directory. The nsrrdbstart program initializes the save environment and then executes the Rdb backup script.
Server-initiated Oracle Rdb backups 113 NetWorker Module for Oracle Rdb
Settings on the NetWorker server, including those defined in Client resources that are associated with your OpenVMS client system, and associated Group, Pool, and Device resource settings, are used during the database backup. To change these settings, you must modify the appropriate resources on the NetWorker server.
Task 1: Create the Rdb backup script
To configure your Oracle Rdb system for server-initiated backups using the NetWorker Module for Oracle Rdb, you must create an Rdb backup script on the OpenVMS client. This script specifies the RMU commands that will be used to back up your Oracle Rdb database. The NetWorker Module for Oracle Rdb provides a template Rdb backup script that you can modify for use at your site. The instructions that follow explain how to use the template script to create a basic script that specifies the name of the database to back up and the RMU command to back it up. Comments included in the template script itself provide additional information. For a complete list of RMU commands, refer to the Oracle RMU documentation and the Oracle RDB release notes.
One difference between Oracle Rdb and Oracle backups is that the Oracle Rdb software does not provide a method of generating unique backup save set names. Therefore, the script you use for Rdb backups must create unique save set names for each backup attempt.
The template script uses a date and time scheme to ensure that each backup has a unique save set name. If you write your own backup script, ensure that it generates unique save set names. To create an Rdb backup script on your Oracle Rdb system from the template Rdb backup script provided by the NetWorker Module for Oracle Rdb: 1. Copy the template script from its current location to another location. You can choose any destination because you will be identifying the full file specification in the Save Set attribute of the Client resource on the server. By default, the NetWorker Module for Oracle Rdb installation creates the template script in the following location:
NSR$SYSTEM:NSR$RDB_BACKUP_TEMPLATE.COM
Note: Retain the original template file for future reference.
2. Rename the copied script to a name that is meaningful to you. 3. Edit the values of the following symbols in your copy of the template script: • DATABASE_NAME — Specify the disk, directory, and name of the Rdb database that is being backed up. For example: DATABASE_NAME = "DISK$DB:[RDB_FILES]PERSONNEL" • BACKUP_NAME — Specify the base portion of the name of the save sets for database backups. For example:
BACKUP_NAME = "RDB_DB"
114 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle Rdb
The backup procedure appends the date and time to the name you specify, making it unique for each backup. RMU appends the file extension, .RBF. For example: RDB_DB_2003-12-25_091311.RBF
Note: RMU requires the backup name to comply with ODS-2 conventions.
• BACKUP_COMMAND — Specify the RMU command that will be used to back up the database. For example:
BACKUP_COMMAND = "RMU/BACKUP/LIBRARY" Repeat this procedure to create additional Rdb backup scripts if necessary. Once you have created and modified your Rdb backup scripts, you are ready to configure Client resources for Oracle Rdb backups on the NetWorker server.
Task 2: Configure the Client resource for Oracle Rdb backups
You need to create a separate Client resource on the NetWorker server for Oracle Rdb database backups. This is necessary to allow definition of the required backup command for server-initiated Oracle Rdb database backups. It also allows you to associate Rdb backups with different backup groups and storage pools. When creating the Client resource for Oracle Rdb database backups, define the following attributes:
◆ Save Set — The Save Set attribute identifies the Rdb backup script that will be used to back up the database. (In a more typical Client resource, this attribute identifies the highest level directory of the data to be backed up to the NetWorker server.) Identify the full file specification for all Oracle Rdb backup scripts that you have configured on the OpenVMS client.
◆ Backup Command — To instruct NetWorker to execute an alternate save program for these backups, Client resources for Oracle Rdb backups must specify the backup command nsrrdbstart. During a regular (non-Oracle Rdb) client backup, the nsrexecd starts the save program located in the NSR$SYSTEM directory. When you define the Backup Command to be nsrrdbstart, the nsrexecd starts the nsrrdbstart program (also located in the NSR$SYSTEM directory) instead. (See “Server-initiated Oracle Rdb backups” on page 113 for more information.)
◆ Group — If you have created a special backup group and associated pool for Oracle Rdb database backups, be sure to select the appropriate group when defining the Group attribute of the Client resource. The Dell EMC NetWorker Administration Guide includes step-by-step instructions for creating a Client resource on the server.
Task 3: Test the script
After creating your Rdb backup script from the template script (NSR$SYSTEM:NSR$RDB_BACKUP_TEMPLATE.COM), you can test your script by executing it interactively as follows:
Server-initiated Oracle Rdb backups 115 NetWorker Module for Oracle Rdb
1. Before running the script, verify that the following required symbols are defined within the script: •DATABASE_NAME •BACKUP_NAME •BACKUP_COMMAND 2. Define the following logical names at the DCL prompt to set NetWorker environment variables for this test: • NSR_SERVER — Identifies the NetWorker server that will receive the backup data. • NSR_GROUP — Specifies the backup group that this client is associated with. Define this logical to match the Group attribute definition in the Client resource you created. • NSR_DEBUG_FILE — Specifies the full file specification of the file into which the NetWorker software will write debug and trace messages. • NSR_DEBUG_LEVEL — Specifies the level of debug and trace messages that the NetWorker software will write to the file specified by the NSR_DEBUG_FILE logical name. Valid values are 1 to 5, where 5 provides the most detail. For example:
DEFINE NSR_GROUP "db_backups" DEFINE NSR_SERVER "nw_server" DEFINE NSR_DEBUG_FILE "nsr$logs:test_dbbackup.log" DEFINE NSR_DEBUG_LEVEL "3" 3. Execute the Rdb backup script. The following sample command specifies the default name of the template script. If you renamed your copy of the script, substitute the appropriate name.
@NSR$RDB_BACKUP_TEMPLATE 4. Monitor the progress of the database backup from the NetWorker Management Console. When the backup completes, check either or both of the following files to determine if any errors occurred: • The debug file specified by the NSR_DEBUG_FILE logical name • The daemon.log file on the NetWorker server 5. Deassign the logical names that you defined in step 2. For example:
DEASSIGN NSR_GROUP DEASSIGN NSR_SERVER DEASSIGN NSR_DEBUG_FILE DEASSIGN NSR_DEBUG_LEVEL
Task 4: (Optional) Back up the sample Oracle Rdb database
The following procedure explains how to create an Rdb backup script, configure a Client resource, and perform a server-initiated backup of the sample corporate data database, which is provided by the Oracle Rdb product. You can use this procedure at your site as a test. When you can successfully back up the sample database, you can then use a similar process to configure and back up your Oracle Rdb database.
116 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle Rdb
Note: The sample database requires approximately 3,800 blocks of disk space.
1. Enter the following commands to create the directory that will contain the sample database and backup script and set default to that directory:
create/directory sys$sysdevice:[rdb] set default sys$sysdevice:[rdb] 2. Enter the next command to create the CORPORATE_DATA sample database in the SYS$SYSDEVICE:[RDB] directory:
@SYS$COMMON:[SYSHLP.EXAMPLES.RDB71]PERSONNEL - SQL S NOCDD MSDB SYS$SYSDEVICE:[RDB] where: • @SYS$COMMON:[SYSHLP.EXAMPLES.RDB71]PERSONNEL runs the (Oracle-supplied) PERSONNEL command procedure. • SQL specifies the language interface to use. • S specifies a single file database. • NOCDD (No Common Data Dictionary) specifies that the data dictionary not be used. • MSDB creates a multi-schema database. • SYS$SYSDEVICE:[RDB] is the location where the database will be created. For more information on the parameters that can be used with the PERSONNEL command procedure, refer to the comments in the procedure itself or to the appropriate Oracle Rdb documentation. 3. Use the DIRECTORY command to verify that the appropriate files now exist in this directory:
directory
Directory SYS$SYSDEVICE:[RDB]
CORPORATE_DATA$2.LOG;1 CORPORATE_DATA.LOG;1 CORPORATE_DATA.RDB;1 CORPORATE_DATA.SNP;1
Total of 4 files. 4. Copy NSR$SYSTEM:NSR$RDB_BACKUP_TEMPLATE.COM (the template backup script) to the SYS$SYSDEVICE:[RDB] directory. Rename the copy to NSR$RDB_BACKUP.COM. 5. Edit NSR$RDB_BACKUP.COM as follows:
a. Define the DATABASE_NAME symbol to specify the file specification of the CORPORATE_DATA Rdb database as shown in the following example: DATABASE_NAME = "SYS$SYSDEVICE:[RDB]CORPORATE_DATA" b. Change the default value of the BACKUP_NAME symbol from "RDB_DB" to "CORPORATE_DATA". (This step is optional.) For example:
BACKUP_NAME = "CORPORATE_DATA"
Server-initiated Oracle Rdb backups 117 NetWorker Module for Oracle Rdb
6. On the NetWorker server, create a Client resource that defines the following attributes as shown: • Save Set: SYS$SYSDEVICE:[RDB]NSR$RDB_BACKUP.COM • Backup Command: nsrrdbstart 7. Start the backup on the NetWorker server. You can verify completion of the backup by checking the savegrp completion messages on the server. For more information on the savegrp command and its output, refer to the Dell EMC Command Reference Guide. Restoring Oracle Rdb data
Before starting an Oracle Rdb restore, ensure that the volume required for the restore operation is mounted in a configured backup device. If auto media management is enabled for a tape device or autochanger, ensure that the tape is loaded in the tape device or autochanger for the NetWorker server to use automatically. You will need to know the name of the save set that is stored on the NetWorker server. You can use the mminfo command to obtain a list of save set names for a specified backup. If you created a special backup group for Oracle Rdb backups, you can specify the group name in your mminfo command to filter the response. The example in the next section shows how to use the mminfo command in this manner. For more information on the mminfo command, refer to the Dell EMC NetWorker Command Reference Guide. To start the restore operation, enter the appropriate RMU/RESTORE/LIBRARY command at the DCL prompt on the OpenVMS client system.
Restoring the sample Oracle Rdb database
This example shows how to restore the sample Oracle Rdb database that was configured and backed up in “Task 4: (Optional) Back up the sample Oracle Rdb database” on page 116. 1. The following command lists the save sets for the CORPORATE_DATA backup and filters the response by specifying the group name, rdb_backup:
pipe mcr nsr$system:mminfo -s
DEFINE NSR_SERVER "nsrsrv1" 3. The command that follows restores the database specifying the save set name obtained in step 1:
rmu/restore/library/new/nocdd - corporate_data_2003-10-30_091311.RBF 4. The next command deassigns the NSR_SERVER logical name because this environment variable definition can affect subsequent NetWorker commands:
118 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide NetWorker Module for Oracle Rdb
DEASSIGN NSR_SERVER Known restrictions
The NetWorker Module for Oracle Rdb has the following known restrictions:
◆ Parallel recover operations are not supported.
◆ A parallel backup operation is not supported when the LIBRARIAN qualifier is used and more than one writer thread is specified. For example, the following command is not supported:
rmu/backup/librarian=(writer_threads=3) disk$oracle[rdb72db] mfp However, the next command is supported because the value of WRITER_THREADS is 1, which is the default value:
rmu/backup/librarian=(writer_threads=1) disk$oracle[rdb72db] mfp
◆ The TRACE and LEVEL switches are not supported for use in an RMU/LIBRARIAN command. For example:
rmu/librarian=(trace=filespec,level=level) To configure the NetWorker software to write debug and trace messages to a specified file, define the following logical names before beginning the database backup: • NSR_DEBUG_FILE • NSR_DEBUG_LEVEL Deassign these logical names after the backup operation completes.
◆ Wildcards are not supported with RMU/LIBRARY/LIST command. The RMU program supports a function that queries the librarian catalog. When the RMU program invokes the NetWorker software, this function queries the media and file indexes. The format for the RMU LIST command is:
rmu/library/list
rmu/library/list corporate_data_2003-10-30_091311.RBF LIBRARIAN BACKUP FILES BACKUP NAME: CORPORATE_DATA_2003-10-30_091311.RBF CREATION METHOD: stream CREATION DATE/TIME: Thu Oct 30 09:13:23 2003 EXPIRATION DATE/TIME: Fri Oct 29 10:14:34 2004 VOLUME LABEL: wumpus.tz87.008 SHARING MODE: single user ORDERING MODE: sequential access
Known restrictions 119 NetWorker Module for Oracle Rdb
120 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide GLOSSARY
This glossary contains terms related to disk storage subsystems. Many of these terms are used in this manual.
A
alternate track A track designated to contain data in place of a defective primary track. See also ”primary track.”
actuator A set of access arms and their attached read/write heads, which move as an independent component within a head and disk assembly (HDA).
adapter Card that provides the physical interface between the director and disk devices (SCSI adapter), director and parallel channels (Bus & Tag adapter), director and serial channels (Serial adapter).
C
cache Random access electronic storage used to retain frequently used data for faster access by the channel.
cache slot Unit of cache equivalent to one track.
channel director The component in the Symmetrix subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.
controller ID Controller identification number of the director the disks are channeled to for EREP usage. There is only one controller ID for Symmetrix.
CKD Count Key Data, a data recording format employing self-defining record formats in which each record is represented by a count area that identifies the record and specifies its format, an optional key area that may be used to identify the data area contents, and a data area that contains the user data for the record. CKD can also refer to a set of channel commands that are accepted by a device that employs the CKD recording format.
D
DASD Direct access storage device., a device that provides nonvolatile storage of computer data and random access to that data.
data availability Access to any and all user data by the application.
delayed fast write There is no room in cache for the data presented by the write operation.
device address The hexadecimal value that uniquely defines a physical I/O device on a channel path in an MVS environment. See also ”unit address.”
device number The value that logically identifies a disk device in a string.
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 121 Glossary
diagnostics System level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking.
director The component in the Symmetrix subsystem that allows Symmetrix to transfer data between the host channels and disk devices. See also ”channel director.”
disk director The component in the Symmetrix subsystem that interfaces between cache and the disk devices.
dual-initiator A Symmetrix feature that automatically creates a backup data path to the disk devices serviced directly by a disk director, if that disk director or the disk management hardware for those devices fails.
dynamic path reconnect A function that allows disconnected I/O operations with Symmetrix to reconnect over any (dpr) available channel path rather than be limited to the one on which the I/O operation was started. This function is available only on System 370/XA, System 370/ESA, and System 390/ESA systems.
dynamic sparing A Symmetrix feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all non-mirrored devices in the Symmetrix subsystem.
E
ESCON Enterprise Systems Connection, a set of IBM and vendor products that connect mainframe computers with each other and with attached storage, locally attached workstations, and other devices using optical fiber technology and dynamically modifiable switches called ESCON directors. See also ”ESCON director.”
ESCON director Device that provides a dynamic switching function and extended link path lengths (with XDF capability) when attaching an ESCON channel to a Symmetrix serial channel interface.
F
fast write In Symmetrix, a write operation at cache speed that does not require immediate transfer of data to disk. The data is written directly to cache and is available for later destaging.
FBA Fixed Block Architecture, disk device data storage format using fixed-size data blocks.
field replaceable unit A component that is replaced or added by service personnel as a single entity. (FRU)
frame Data packet format in an ESCON environment.
G
gatekeeper A small logical volume on a Symmetrix storage subsystem used to pass commands from a host to the Symmetrix storage subsystem. Gatekeeper devices are configured on standard Symmetrix disks.
gigabyte (GB) 109 bytes.
122 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Glossary
H head and disk assembly A field replaceable unit in the Symmetrix subsystem containing the disk and actuator. (HDA)
home address (HA) The first field on a CKD track that identifies the track and defines its operational status. The home address is written after the index point on each track. hyper-volume extension The ability to define more than one logical volume on a single physical disk device making use of its full formatted capacity. These logical volumes are user-selectable in size. The minimum volume size is one cylinder and the maximum size depends on the disk device capacity and the emulation mode selected.
I
ID Identifier, a sequence of bits or characters that identifies a program, device, controller, or system.
IML Initial microcode program loading.
index marker Indicates the physical beginning and end of a track.
index point The reference point on a disk surface that determines the start of a track.
INLINES A Dell EMC-provided host-based Cache Reporter utility for viewing short and long term cache statistics at the system console.
I/O device An addressable input/output unit, such as a disk device.
K
K Kilobyte, 1024 bytes. L
least recently used The algorithm used to identify and make available the cache space by removing the least algorithm (LRU) recently used data.
logical volume A user-defined storage device. In the Model 5200, the user can define a physical disk device as one or two logical volumes.
long miss Requested data is not in cache and is not in the process of being fetched.
longitude redundancy Exclusive OR (XOR) of the accumulated bytes in the data record. code (LRC)
M
6 MB Megabyte, 10 bytes. mirroring The Symmetrix maintains two identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, Symmetrix automatically uses the other disk device.
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 123 Glossary
mirrored pair A logical volume with all data recorded twice, once on each of two different physical devices.
P
PDS Partitioned Dataset, a composite mainframe dataset that is much like a directory in UNIX containing files, for example, source files. The members in a PDS are usually of the same type of data, for example, C language source files or header files.
physical ID Physical identification number of the Symmetrix director for EREP usage. This value automatically increments by one for each director installed in Symmetrix. This number must be unique in the mainframe system. It should be an even number. This number is referred to as the SCU_ID.
primary track The original track on which data is stored. See also ”alternate track.”
promotion The process of moving data from a track on the disk device to cache slot.
R
read hit Data requested by the read operation is in cache.
read miss Data requested by the read operation is not in cache.
record zero The first record after the home address.
S
scrubbing The process of reading, checking the error correction bits, and writing corrected data back to the source.
SCSI adapter Card in the Symmetrix subsystem that provides the physical interface between the disk director and the disk devices.
short miss Requested data is not in cache, but is in the process of being fetched.
SSID For 3990 storage control emulations, this value identifies the physical components of a logical DASD subsystem. The SSID must be a unique number in the host system. It should be an even number and start on a zero boundary.
stage The process of writing data from a disk device to cache.
storage control unit The component in the Symmetrix subsystem that connects Symmetrix to the host channels. It performs channel commands and communicates with the disk directors and cache. See also ”channel director.”
string A series of connected disk devices sharing the same disk director.
U
unit address The hexadecimal value that uniquely defines a physical I/O device on a channel path in an MVS environment. See also ”device address.”
124 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide Glossary
V
volume A general term referring to a storage device. In the Symmetrix subsystem, a volume corresponds to single disk device.
W
write hit There is room in cache for the data presented by the write operation. write miss There is no room in cache for the data presented by the write operation.
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 125 Glossary
126 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide INDEX
A always directive 36 alias files 66 asm directive 36 archive compressasm directive 37 archiving and verifying data 77 copy_alias directive 37 cloning an archive 78 creating on client 45 grooming directories after archiving 78 format of 32 nsrarchive command 75 ignobackup directive 38 overview 74 list of 35 pools 74 logasm directive 38 retrieving archived data 80 nolock directive 38 norecord directive 42 null directive 39 B overview 32 backup precedence of 34 of a physical disk 69 rawasm directive 39 of a single file 54 recommended for system disk 46, 66 of a system disk 66 record directive 42 of an Oracle database 99, 103 save environment keywords 34 of an Oracle Rdb database 112 skip directive 43 of client data 26, 48 skip_alias directive 43 See also save skip_shelved directive 43 single or selected files 49 swapasm directive 44 unshelve directive 44 C xlateasm directive 45 Client resource directories configuring for Oracle backups 107 for recovered primary files 66 configuring for Oracle Rdb backups 115 grooming after archive 78 command line help 24 command procedures E for pre- and postprocessing 27 environment variables NSR$LOGIN.COM 22 defining for manual Oracle Rdb backups 113 NSR$SHUTDOWN.COM 19 specifying for manual Oracle backups 100 NSR$STARTUP.COM 18 extended file specifications 16 PERSONNEL 117 commands G case sensitivity 22 date formats for 22 graphical user interfaces defining foreign 22 nwarchive 13 list of 24 nwbackup 13 nsrarchive 75 nwrecover 13 nsrexecd 24 nwretrieve 13 nsrinfo 25 nsrretrieve 81 L nsrwatch 26 logical names 86 privileges required 22 convenience 16 recover 55 LIBOBK 99 save 49 NSR_CHUNK_SIZE 91 See also specific command names NSR$ARCHIVE_TMPDIR 86 convenience logical names 16 NSR$BITMAPS 86 NSR$BLOCK_SIZE_devname 87 D NSR$COMMON 88 date formats 22 NSR$CONNECTION_STATE 88 DCL script for Oracle backups 104 NSR$DEBUG_FLAG 88 directives NSR$DISABLE_DRIVE_ALLOC 88
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 127 Index
NSR$DISABLE_FIDCACHE 88 N NSR$DISABLE_SMART_SELECT 89 NetWorker NSR$FILE_BUFFER_COUNT 89 determining version number 19 NSR$FILE_BUFFER_SIZE 89 NSR_CHUNK_SIZE logical name 91 NSR$FILE_BUFFER_TRACE 89 nsr_getdate routine 22 NSR$FILE_DEVICE_SIZE 89 NSR$ARCHIVE_TMPDIR logical name 86 NSR$IGNORE_BACKUP_TIME 89 NSR$BITMAPS logical name 86 NSR$INCLUDE_ALL_DEVICES 89 NSR$BLOCK_SIZE_devname logical name 87 NSR$INCLUDE_NONSCSI_DEVICES 90 NSR$COMMON logical name 88 NSR$INO_AIO 91 NSR$CONNECTION_STATE logical name 88 NSR$INTERRUPT_RDMSK_ZERO 90 NSR$DEBUG_FLAT logical name 88 NSR$INTERRUPT_SELECT 90 NSR$DISABLE_DRIVE_ALLOC logical name 88 NSR$INTERRUPT_SELECT_ERRNO 90 NSR$DISABLE_FIDCACHE logical name 88 NSR$INTERRUPT_SELECT_RETVAL 90 NSR$DISABLE_SMART_SELECT logical name 89 NSR$INTERRUPT_SELECT_STATUS 90 NSR$FILE_BUFFER_COUNT logical name 89 NSR$LOG_AIO 90 NSR$FILE_BUFFER_SIZE logical name 89 NSR$LOGS 90 NSR$FILE_BUFFER_TRACE logical name 89 NSR$LUS_BUG 90 NSR$FILE_DEVICE_SIZE logical name 89 NSR$MAX_SESSIONS 90 NSR$IGNORE_BACKUP_TIME logical name 89 NSR$MAX_TAPE_BLOCK_SIZE 90 NSR$INCLUDE_ALL_DEVICES logical name 89 NSR$MAX_WRITESZ 91 NSR$INCLUDE_NONSCSI_DEVICES logical name 90 NSR$MKDRIVER_64K 90 NSR$INTERRUPT_RDMSK_ZERO logical name 90 NSR$NO_CASE_SENSITIVE 91 NSR$INTERRUPT_SELECT logical names 90 NSR$NO_HW_COMPRESS 91 NSR$LOG_AIO logical name 90 NSR$PA_ORDER 91 NSR$LOGIN.COM command procedure 22 NSR$PACKACK_TIMEOUT 91 NSR$LOGS logical name 90 NSR$PATH_TRACE 91 NSR$LUS_BUG logical name 90 NSR$PIPE_SIZE 91 NSR$MAX_SESSIONS logical name 90 NSR$PRE_saveset_name 92 NSR$MAX_TAPE_BLOCK_SIZE logical name 90 NSR$PRINT_FIDTREE 92 NSR$MAX_WRITESZ logical name 91 NSR$PST_saveset_name 92 NSR$MKDRIVER_64K logical name 90 NSR$QUIT_FLAG 92 NSR$NO_AIO logical name 91 NSR$RAWASM_COMPRESS 92 NSR$NO_CASE_SENSITIVE logical name 91 NSR$RAWASM_NOFLUSH 92 NSR$NO_HW_COMPRESS logical name 91 NSR$RAWASM_NOLOCK 92 NSR$PA_ORDER logical name 91 NSR$RECOVER_MCP 93 NSR$PACKAK_TIMEOUT logical name 91 NSR$RES 93 NSR$PATH_TRACE logical name 91 NSR$SCAN_PIPE_SIZE 93 NSR$PIPE_SIZE logical name 91 NSR$SCSI_DISCTMO 93 NSR$PRE_saveset_name logical name 92 NSR$SCSI_PHASETMO 93 NSR$PRINT_FIDTREE logical name 92 NSR$SPECIFIC 93 NSR$PST_saveset_name logical name 92 NSR$STORE_ACL_INDEX 94 NSR$QUIT_FLAG logical name 92 NSR$SYSROOT 94 NSR$RAWASM_COMPRESS logical name 92 NSR$SYSTEM 94 NSR$RAWASM_NOFLUSH logical name 92 NSR$TCP_RECOVERBUF_SIZ 94 NSR$RAWASM_NOLOCK logical name 92 NSR$TCP_SAVEBUF_SIZ 94 NSR$RECOVER_MCP logical name 93 NSR$TMP 94 NSR$RES logical name 93 NSR$USE_BUFSIZ_ONLY 95 NSR$SCAN_PIPE_SIZE logical name 93 NSR$USE_DEFAULT_TAPE_INFO 95 NSR$SCSI_DISCTMO logical name 93 NSR$VERBOSE_FLAG 95 NSR$SCSI_PHASETMO logical name 93 See also specific logical name NSR$SHUTDOWN procedure 19 system logical names 67 NSR$SPECIFIC logical name 93 NSR$STARTUP.COM procedure 18 M NSR$STORE_ACL_INDEX logical name 94 modules NSR$SYSROOT logical name 94 for Oracle 98 NSR$TCP_RECOVERBUF_SIZ logical name 94 for Oracle Rdb 112 NSR$TCP_SAVEBUF_SIZ logical name 94 NSR$TMP logical name 94 NSR$USE_BUFSIZ_ONLY logical name 95 NSR$USE_DEFAULT_TAPE_INFO logical name 95
128 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide IndexIndex
NSR$VERBOSE_FLAG logical name 95 S NSR$YSTEM logical name 94 save nsrarchive command 75 command description 49 nsrexecd command 24 of a single file 54 nsrexecd daemon omitting directories from 26, 53 authorized and default privileges 28 performing without saving data 53 nsrretrieve command 81 restricting to a specific file type 53 nwarchive program 13, 79 starting process from within a cluster 48 nwbackup program 13, 54 Save Set attribute 26 nwrecover program 13, 64 save set name 52 nwretrieve program 13, 83 save sets defining for server-initiated client backups 26 O for Oracle Rdb backups 114 ODS-5 volumes 16 scripts Oracle module 98 for Oracle backups configuring 98 server-initiated 104 installing 98 for Oracle data restore 108 restoring Oracle data 108 for Oracle Rdb backups 114 scripts for server-initiated backups 104 send command in RMAN scripts 100 Oracle Rdb module 112 shutdown procedure for NetWorker 19 configuring 112 startup procedure for NetWorker 18 creating script for 114 symbols installing 112 defining for server-initiated Oracle backups 105 restoring Oracle Rdb data 118 SYS$OUTPUT restrictions 119 for save set-based pre- and postprocesses 28 testing backup script 115 system disk backing up 66 individual directories 67 P open files 46, 66 PERSONNEL command procedure 117 recovering 68 physical disk backup 69 system logical names 67 performing 69 recovering 70 V privileges for NetWorker commands 22 version identification 19 for nsrexecd 28 volume sets for save set-based pre- and post-processes 28 doing a physical backup of 41, 69 recovering physical backup 42, 70 R rawasm directive 39, 69 recover command description 55 command modes automatic 61 browser 58 directed recover 63 save set recover 62 of a physical disk backup 70 of an OpenVMS system disk 68 of an Oracle database 110 performing from a client 54 starting process from within a cluster 48 restore of Oracle data 108 of Oracle Rdb data 118 retrieve command. See nsrretrieve command RMAN scripts for restoring Oracle data 108 for server-initiated Oracle backups 106 RMU$LIBRARIAN_PATH logical name 112
Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide 129 Index
130 Dell EMC NetWorker OpenVMS Version Release 18.1 Administration Guide