Red Hat NETSCAPE MANAGEMENT SYSTEM 6.01 - CUSTOMIZATION Datasheet

Red Hat NETSCAPE MANAGEMENT SYSTEM 6.01 - CUSTOMIZATION Datasheet
February 2006
NetWorker
®
Release 6.0.1-x
HP OpenVMS Version
Release Supplement
Copyright © 2003-2006 by EMC Corporation. All rights reserved. This software (including documentation) is subject to the terms and
conditions set forth in the end user license agreement or other applicable agreement, and you may use this software only if you accept all
the terms and conditions of the license agreement. This software comprises proprietary and confidential information of EMC.
Unauthorized use, disclosure, and distribution are strictly prohibited. Use, duplication, or disclosure of the software and documentation
by the U.S. Government are subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48 CFR
52.227-19, as applicable. Manufacturer is LEGATO Software, a division of EMC, 2350 West El Camino Real, Mountain View, CA 94040.
Legato NetWorker Release Supplement, Release 6.0.1-x, HP OpenVMS Version
February 2006
e4-1828-01
LEGATO and the LEGATO logo are registered trademarks, and LEGATO NetWorker, NetWorker, AAM, Co-StandbyServer, RepliStor,
SnapShotServer, QuikStartz, AlphaStor, ClientPak, Xtender, XtenderSolutions, DiskXtender, ApplicationXtender, ArchiveXtender,
EmailXtender, and EmailXaminer are trademarks or registered trademarks of LEGATO Software, a division of EMC. This is a
nonexhaustive list of LEGATO trademarks, and other trademarks may be the property of their respective owners.
The following may be trademarks or registered trademarks of the companies identified next to them, and may be used in this document
for identification purposes only.
Acrobat, Adobe / Adobe Systems, Inc.
Apple, Macintosh / Apple Computer, Inc.
Caldera Systems, SCO, SCO OpenServer, UnixWare / Caldera, Inc.
TELEform / Cardiff
Check Point, FireWall-1 / Check Point Software Technologies, Ltd.
Unicenter / Computer Associates International, Inc.
Access Logix, Celerra, Centera, CLARiiON, EMC, EMC2 , MirrorView, Navisphere, SnapView, SRDF, Symmetrix, Symmetrix DMX,
TimeFinder / EMC Corporation
Fujitsu / Fujitsu, Ltd.
Hewlett-Packard, HP, HP-UX, HP Tru64, HP TruCluster, OpenVMS, ProLiant / Hewlett-Packard Company
AIX, DB2, DB2 Universal Database, Domino, DYNIX, DYNIXptx, IBM, Informix, Lotus, Lotus Notes, OS/2, PTX, ptx/ADMIN, Raid Plus,
ServeRAID, Sequent, Symmetry, Tivoli, / IBM Corporation
InstallShield / InstallShield Software Corporation
Intel, Itanium / Intel Corporation
Linux / Linus Torvalds
Active Directory, Microsoft, MS-DOS, Outlook, SQL Server, Windows, Windows NT / Microsoft Corporation
Netscape, Netscape Navigator / Netscape Communications Corporation
Data ONTAP, NetApp, NetCache, Network Appliance, SnapMirror, SnapRestore / Network Appliance, Inc.
IntraNetWare, NetWare, Novell / Novell, Inc.
Oracle, Oracle8i, Oracle9i / Oracle Corporation
NetFORCE / Procom Technology, Inc.
DLTtape / Quantum Corporation
Red Hat / Red Hat, Inc.
R/3, SAP / SAP AG
IRIX, OpenVault, SGI / Silicon Graphics, Inc.
SPARC / SPARC International, Inc.a
ACSLS, REELbackup, StorageTek / Storage Technology Corporation
Solaris, Solstice Backup, Sun, SunOS, Sun StorEdge, Ultra / Sun Microsystems, Inc.
SuSE / SuSE, Inc.
Sybase / Sybase, Inc.
Turbolinux / Turbolinux, Inc.
Unicode / Unicode, Inc.
VERITAS, VERITAS File System/ VERITAS Software Corporation
WumpusWare / WumpusWare, LLC
UNIX / X/Open Company Ltdb
Notes:
a. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc.
b. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.
All other brand or product names may be trademarks or registered trademarks of their respective owners.
LEGATO Software
A Division of EMC Corporation
End-User License Agreement
THIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER PROPRIETARY MATERIAL, THE USE OF WHICH IS SUBJECT TO THIS
END-USER LICENSE AGREEMENT (THE "EULA"). DO NOT PROCEED WITH THE INSTALLATION OF THIS PRODUCT UNTIL YOU (LATER DEFINED
AS LICENSEE) HAVE READ THIS EULA AND AGREE TO BE BOUND BY AND BECOME A PARTY TO THIS EULA. BY PROCEEDING WITH THE
INSTALLATION OF THIS PRODUCT (OR AUTHORIZING ANY OTHER PERSON TO DO SO), YOU AND YOUR COMPANY ACCEPT THIS EULA AND
YOU REPRESENT THAT YOU ARE AUTHORIZED TO DO SO. IF YOU ARE ACCESSING THE PRODUCT ELECTRONICALLY INDICATE YOUR
ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THE EULA. IF YOU DO NOT AGREE TO THE TERMS OF
THIS EULA, YOU MAY RETURN THIS PRODUCT, ALL MEDIA AND DOCUMENTATION, AND PROOF OF PAYMENT, TO THE PLACE YOU OBTAINED
THEM FOR A FULL REFUND WITHIN THIRTY (30) DAYS OF FIRST ACQUIRING THIS PRODUCT OR, IF THE PRODUCT IS ACCESSED
ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS EULA AND RETURN PROOF OF PAYMENT IN ACCORDANCE WITH
THE ABOVE REFERENCED RETURN/REFUND PROCESS. WRITTEN APPROVAL IS NOT A PREREQUISITE TO THE VALIDITY OR ENFORCEABILITY
OF THIS EULA AND NO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON BEHALF OF LEGATO SHALL BE CONSTRUED AS AN
INFERENCE TO THE CONTRARY. IF YOU HAVE ORDERED THIS PRODUCT, LEGATO'S ACCEPTANCE IS EXPRESSLY CONDITIONAL ON YOUR
ASSENT TO THESE TERMS TO THE EXCLUSION OF ALL OTHER TERMS; IF THESE TERMS ARE CONSIDERED AN OFFER BY LEGATO, ACCEPTANCE
IS EXPRESSLY LIMITED TO THESE TERMS.
1. DEFINITIONS
1.1 Authorization Code: means the unique code provided to Licensee by
LEGATO for permanent activation of the Software. The Authorization Code
is provided to Licensee once the Enabler Code is registered with LEGATO.
The Authorization Code may be tied to a unique machine ID code supplied
by Licensee.
1.2 Documentation: Documentation: means the user reference materials on
any media, provided by LEGATO for use with the Software.
1.3 Enabler Code: means the code provided by LEGATO for activation of the
Software.
1.4 Licensee: means the person or entity acquiring this License or for whom
this License was acquired.
1.5 Software: means the object code copy of the software program provided
to You in association with this EULA, together with the associated original
media and all accompanying Documentation, and together with all Updates
that may be provided by LEGATO to You from time to time.
2. OWNERSHIP AND ADMINISTRATION OF SOFTWARE
2.1 Ownership and Title. As between the parties, LEGATO, and its licensors,
own and shall retain all right, title, and interest in and to: (i) the Software
including all intellectual property rights embodied therein; (ii) all of the
service marks, trademarks, trade names, or any other designations associated
with the Software; and (iii) all copyrights, patent rights, trade secret rights,
and other proprietary rights relating to the Software.
2.2 Software Activation. LEGATO employs Enabler Codes and
Authorization Codes that enable the use of the Software. The Software is
shipped in a ”Media Kit” which consists of object code software on CD-ROM
and an Enabler Code for initial activation of the Software or the Software and
Enabler Code may be delivered electronically. Once LEGATO receives
confirmation from Licensee that the Software is installed with the correct
Enabler Code, and is provided with the host ID information, LEGATO will
provide the Authorization Code to Licensee. LEGATO administers the
generation and distribution of Enabler and Authorization Codes, which
administration may be modified by LEGATO from time to time.
2.3 Administration of Software. LEGATO may include on the media with
the Software additional computer programs which are not currently licensed
for use by Licensee and to which the Enabler Code or Authorization code will
not permit access. Inclusion of such additional computer programs in no way
implies a license from LEGATO and access or use of such programs is strictly
prohibited unless Licensee procures the right to use any such program and
the applicable Enabler Code is provided thereto.
3. LICENSE GRANT
3.1 Grant. LEGATO grants to Licensee a non-exclusive, nontransferable,
non-sublicensable, perpetual (unless terminated in accordance with the
provisions of this EULA), license (the “License”) to (i) use the Software
installed in accordance with the Documentation and only on the licensed
computer(s) solely for its own internal operations; and (ii) move the Software
temporarily in case of computer system malfunction. The Software may be
licensed: (a) on a per copy or per seat basis, on a physical or virtual machine,
(b) based upon the number of mailboxes or the number of non-concurrent
users for which it may be used, or (c) based upon data volumes it supports.
The License granted under this EULA does not constitute a sale of the
Software or any portion or copy of it. Licensee may not use the Software on
more than one computer system unless otherwise specifically authorized by
an explicit Software product, or additional licenses for additional computers
are purchased. Rights not expressly granted are reserved by LEGATO.
3.2 Copies. Licensee may make copies of the Software provided that any such
copy is: (i) created as an essential step in utilization of the Software as
licensed and is used in no other manner; or (ii) used for archival purposes.
All trademark and copyright notices must be reproduced and included on
such copies. Licensee may not make any other copies of the Software.
3.3 Restrictions on use. Licensee shall not, and shall not aid, abet, or permit
any third party to: (i) decompile, disassemble, or otherwise reverse engineer
or attempt to reconstruct or discover any source code or underlying ideas or
algorithms of the Software by any means whatsoever; (ii) remove any
identification, copyright, or other notices from the Software; (iii) provide,
lease, lend, use for timesharing or service bureau purposes; (iv) create a
derivative work of any part of the Software; or (v) develop methods to enable
unauthorized parties to use the Software. If EC law is applicable, the
restrictions in Section 3.3 (i) are limited so that they prohibit such activity only
to the maximum extent such activity may be prohibited without violating the
EC Directive on the legal protection of computer programs. Notwithstanding
the foregoing, prior to decompiling, disassembling, or otherwise reverse
engineering any of the Software, Licensee shall request LEGATO in writing,
to provide Licensee with such information or assistance and Licensee shall
refrain from decompiling, disassembling, or otherwise reverse engineering
any of the Software unless LEGATO cannot or has not complied with such
request in a commercially reasonable amount of time.
3.4 Purchase Orders. Nothing contained in any purchase order,
acknowledgment, or invoice shall in any way modify the terms or add any
additional terms or conditions to this EULA.
3.5 Updates. This section applies if the Software acquired is an update to the
original Software (the “Update”). An Update does not constitute a legally
licensed copy of the Software unless purchased as an Update to a previously
licensed version of the same Software. The Update may only be used in
accordance with the provisions of this EULA. The Update, together with the
original Software, constitutes one (1) legally licensed copy of the Software.
3.6 Evaluation License. This Section applies if the Software is being used for
an initial thirty (30) day evaluation period. The license is valid only for a
period of thirty (30) days from the delivery of the Software, and is designed
to allow Licensee the right to evaluate the Software during such period. In
the event that Licensee desires to continue to license the Software, Licensee
must purchase a license to the Software. Upon such purchase, Licensee will
be provided with an Enabler Code in accordance with Section 2.2 above. In
the event Licensee determines not to purchase a license for the Software at the
end of such thirty (30) day evaluation period, then Licensee’s rights under
this EULA shall terminate automatically and Licensee shall promptly return
to LEGATO or destroy all copies of the Software and so certify to LEGATO.
3.7 General Public License ("GPL"). The Software may include one or more
components which are derived from software subject to a General Public
License. Any such components are licensed exclusively under the applicable
GPL and not under this EULA.
4. MAINTENANCE AND SUPPORT
4.1 LEGATO has no obligation to provide support, maintenance, upgrades,
modifications, or new releases under this EULA. LEGATO may provide such
services under separate EULA.
5. LIMITED WARRANTY
5.1 Media and Documentation. LEGATO warrants that if the media or
documentation are damaged or physically defective at the time of delivery of
the first copy of the Software to Licensee and if defective or damaged product
is returned to LEGATO (postage prepaid) within thirty (30) days thereafter,
then LEGATO will provide Licensee with replacements at no cost.
5.2 Limited Software Warranty. Subject to the conditions and limitations of
liability stated herein, LEGATO warrants for a period of thirty (30) days from
the delivery of the first copy of the Software to Licensee that the Software, as
delivered, will materially conform to LEGATO’s then current published
Documentation for the Software. This warranty covers only problems
reported to LEGATO during the warranty period. For customers outside of
the United States, this Limited Software Warranty shall be construed to limit
the warranty to the minimum warranty required by law.
5.3 Remedies. The remedies available to Licensee hereunder for any such
Software which does not perform as set out herein shall be either repair or
replacement, or, if such remedy is not practicable in LEGATO’s opinion,
refund of the license fees paid by Licensee upon a return of all copies of the
Software to LEGATO. In the event of a refund this EULA shall terminate
immediately without notice with respect to such Software.
6. WARRANTY DISCLAIMER
6.1 Warranty Disclaimer. EXCEPT FOR THE LIMITED WARRANTY
PROVIDED IN SECTION 5 ABOVE, ALL SOFTWARE IS PROVIDED "AS
IS". LEGATO AND ITS LICENSORS MAKE NO WARRANTIES WITH
RESPECT TO ANY SOFTWARE AND DISCLAIMS ALL STATUTORY OR
IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR ARISING FROM A COURSE OF DEALING OR USAGE OF
TRADE AND ANY WARRANTIES OF NONINFRINGEMENT. LEGATO
DOES NOT WARRANT THAT THE SOFTWARE WILL MEET ANY
REQUIREMENTS OR THAT THE OPERATION OF SOFTWARE WILL BE
UNINTERRUPTED OR ERROR FREE. ANY LIABILITY OF LEGATO WITH
RESPECT TO THE SOFTWARE OR THE PERFORMANCE THEREOF
UNDER ANY WARRANTY, NEGLIGENCE, STRICT LIABILITY OR
OTHER THEORY WILL BE LIMITED EXCLUSIVELY TO THE REMEDIES
SPECIFIED IN SECTION 5.3 ABOVE. Some jurisdictions do not allow the
exclusion of implied warranties or limitations on how long an implied
warranty may last, so the above limitations may not be applicable.
7. LIMITATION OF LIABILITY
7.1 Limitation of Liability. EXCEPT FOR BODILY INJURY, LEGATO (AND
ITS LICENSORS) WILL NOT BE LIABLE OR RESPONSIBLE WITH
RESPECT TO THE SUBJECT MATTER OF THIS EULA UNDER ANY
CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER LEGAL OR
EQUITABLE THEORY FOR: (I) ANY INDIRECT, SPECIAL, INCIDENTAL
OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND
WHETHER OR NOT ADVISED IN ADVANCE OF THE POSSIBILITY OF
SUCH DAMAGES; OR (II) DAMAGES FOR LOST PROFITS OR LOST
DATA; OR (III) COST OF PROCUREMENT OF SUBSTITUTE GOODS,
TECHNOLOGY, SERVICES, OR RIGHTS; OR (IV) FOR AMOUNTS IN
EXCESS OF THOSE RECEIVED BY LEGATO FOR THE PARTICULAR
LEGATO SOFTWARE THAT CAUSED THE LIABILITY . Because some
jurisdictions do not allow the exclusion or limitation of incidental or
consequential damages, LEGATO's liability in such jurisdictions shall be
limited to the extent permitted by law.
8. TERM AND TERMINATION
8.1 Term. The term of this EULA is perpetual unless terminated in
accordance with its provisions.
8.2 Termination. LEGATO may terminate this EULA, without notice, upon
Licensee's breach of any of the provisions hereof.
8.3 Effect of Termination. Upon termination of this EULA, Licensee agrees
to cease all use of the Software and to return to LEGATO or destroy the
Software and all Documentation and related materials in Licensee's
possession, and so certify to LEGATO. Except for the License granted herein
and as expressly provided herein, the terms of this EULA shall survive
termination.
9. MISCELLANEOUS
9.1 Governing Law. This EULA shall be governed by the laws of the
Commonwealth of Massachusetts, without regard to the principles of conflict
of laws or the United Nations Convention on Contracts for the International
Sale of Goods.
9.2 Government Restricted Rights. Any Software which is acquired directly
or indirectly for or on behalf of the United States of America, its agencies
and/or instrumentalities ("U.S. Government"), is provided with Restricted
Rights. Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical
Data and Computer Software clause at DFARS 252.227-7013 or
subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is
LEGATO Software, a division of EMC Corporation, 2350 W. El Camino Real,
Mountain View, CA 94040. The Software is a commercial software product,
licensed on the open market at market prices, and was developed entirely at
private expense and without the use of any government funds.
9.3 Export and Import Controls. Regardless of any disclosure made by
Licensee to LEGATO of an ultimate destination of the Products, Licensee may
not directly or indirectly export or transfer any portion of the Software, or any
system containing a portion of the Software, to anyone outside the United
States (including further export if Licensee took delivery outside the U.S.)
without first complying with any export or import controls that may be
imposed on the Software by the U.S. Government or any country or
organization of nations within whose jurisdiction Licensee operates or does
business. Licensee shall at all times strictly comply with all such laws,
regulations, and orders, and agrees to commit no act which, directly or
indirectly, would violate any such law, regulation or order.
9.4 Assignment. This EULA may not be assigned or transferred by Licensee
without the prior written consent of LEGATO, which shall not be
unreasonably withheld. LEGATO may assign or otherwise transfer any or all
of its rights and obligations under this EULA upon notice to Licensee.
9.5 Sole Remedy and Allocation of Risk. Licensee's sole and exclusive
remedies are set forth in this EULA. This EULA defines a mutually
agreed-upon allocation of risk, and the License price reflects such allocation
of risk.
9.6 Equitable Relief. The parties agree that a breach of this EULA adversely
affecting LEGATO's intellectual property rights in the Software may cause
irreparable injury to LEGATO for which monetary damages may not be an
adequate remedy and LEGATO shall be entitled to equitable relief in addition
to any remedies it may have hereunder or at law.
9.7 No Waiver. Failure by either party to enforce any provision of this EULA
will not be deemed a waiver of future enforcement of that or any other
provision, nor will any single or partial exercise of any right or power
hereunder preclude further exercise of any other right hereunder.
9.8 Severability. If for any reason a court of competent jurisdiction finds any
provision of this EULA, or portion thereof, to be unenforceable, that
provision of the EULA will be enforced to the maximum extent permissible
so as to effect the intent of the parties, and the remainder of this EULA will
continue in full force and effect.
10. ENTIRE EULA
10.1 This EULA sets forth the entire understanding and EULA between the
parties and may be amended only in a writing signed by authorized
representatives of both parties. No vendor, distributor, reseller, dealer,
retailer, sales person, or other person is authorized by LEGATO to modify
this EULA or to make any warranty, representation, or promise which is
different than, or in addition to, the warranties, representations, or promises
made in this EULA. No pre-printed purchase order terms shall in any way
modify, replace or supersede the terms of this EULA.
Contents
Preface....................................................................................................................... 7
.
About This Release Supplement .................................................................................................... 7.
Information and Services ................................................................................................................ 7.
Related Documents ........................................................................................................................ 8.
Revision History of this Document.................................................................................................. 8.
Chapter 1: NetWorker Software Release 6.0.1-D ................................................... 9
.
Operating System Requirements ................................................................................................... 9.
New or Enhanced Features .......................................................................................................... 10.
Daemon Log File No Longer Created .................................................................................... 10.
Directory Structure Has Changed .......................................................................................... 10.
Extended File Specifications Now Supported ........................................................................ 11.
About Longer Filenames and Additional Character Sets................................................. 12.
About Case Sensitivity..................................................................................................... 12.
About Deeper Directory Structures.................................................................................. 13.
How NetWorker Implements/Supports These New Features .......................................... 13.
nsrinfo Command Displays Filenames as Stored (New -r Option)......................................... 13.
Save Behavior Has Changed - New Directive: norecord ....................................................... 13.
Oracle and Oracle Rdb Database Backup and Recovery Support Added............................. 14.
About the NetWorker Module for Oracle Rdb .................................................................. 14.
About the NetWorker Module for Oracle.......................................................................... 15.
Installation and Update Notes ...................................................................................................... 15.
Installation Destination Can be Specified By User ................................................................. 15.
Installation Options Have Changed........................................................................................ 17.
NSR$EXECD Account Issues Corrected ............................................................................... 17.
Old Directories Remain After Installation ............................................................................... 17.
Extracting the PCSI File on an ODS-5 Volume ...................................................................... 18.
Creating Node-Specific Root Directories ............................................................................... 18.
Known Limitations ........................................................................................................................ 19.
nsrexecd ACCVIO on Multiprocessor Clients During Concurrent Saves ............................... 19.
Oracle and/or Oracle Rdb Limitations .................................................................................... 19.
Parallel Recover Operations Not Supported (Oracle Rdb Module) ................................. 19.
Parallel Backup Operation Restricted (Oracle Rdb Module) ........................................... 20.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
5
Contents
RMU Tracing Feature Not Supported (Oracle Rdb Module)............................................ 20.
RMU/LIBRARY/LIST Does Not Support Wildcards (Oracle Rdb Module)....................... 20.
RMU/RECOVER/LIBRARY Fails When Specified Save Set Does Not Exist (Oracle Rdb
Module)............................................................................................................................ 21.
Problem With Rdb V7.2 Using A Plan (Oracle Rdb Module) ........................................... 21.
Save Fails With RPC Error When Using TCPware ................................................................ 21.
Directories That Do Not Have the Directory Bit Set ............................................................... 22.
Files That Have the Directory Bit Set ..................................................................................... 22.
Directories that have no Name............................................................................................... 22.
ODS-5 Volume Restrictions ................................................................................................... 22.
Directories That Do Not Have a Type of “.DIR;1“ ............................................................ 23.
Directories With the Same Name But Different Case ...................................................... 23.
Size Of A File Device Saveset ............................................................................................... 24.
Chapter 2: OpenVMS I64 Supplement .................................................................. 25
.
Operating System Requirements ................................................................................................. 25.
Installation .................................................................................................................................... 25.
Installation In A Mixed Cluster ...................................................................................................... 25.
Recovering an OpenVMS V8.2 System Disk ............................................................................... 26.
Known Limitations ........................................................................................................................ 26.
Oracle Module Limitations...................................................................................................... 26.
Oracle Rdb Module Limitations .............................................................................................. 26.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
6
Preface
Read the information contained in this Release Supplement before installing the
LEGATO NetWorker® software on your OpenVMS Alpha™ or I64 operating system.
About This Release Supplement
This Release Supplement briefly describes new features, known limitations,
configuration tips, and workarounds for this release of the NetWorker software. For a
complete list of documentation related to this product, see "Related Documents" on
page 8.
Late-breaking information obtained following the release of the CD-ROM is included
in an electronic version of this document that is available in the Support section of the
LEGATO web site (www.legato.com). Refer to the web site periodically to view the latest
release of this document.
Information and Services
LEGATO offers a variety of methods, including electronic, telephone, and fax support
to obtain company, product, and technical information.
The LEGATO web site provides most of the information that customers might need.
Technical bulletins and binary patches are also accessible on the LEGATO FTP site. For
specific sales or training needs, e-mail or call LEGATO.
LEGATO Service or Resource
Company &
Technical Binary
Product
Training
Bulletins Patches Information Programs
www.legato.com
Yes
Yes
ftp.legato.com (log in as anonymous) Yes
Yes
LEGATO Sales
(650) 210-7000 (option 1)
[email protected]
LEGATO Education Services
(650) 842-9357
[email protected]
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
Yes
Yes
Yes
Yes
7
Preface
Related Documents
The following documents, available on the LEGATO web site at www.legato.com,
provide further information about this release of the NetWorker software for
OpenVMS Alpha:
•
LEGATO NetWorker Fixed Bugs List, Release 6.0.1-x, HP OpenVMS Alpha Version
•
LEGATO NetWorker Installation Guide, Release 6.0.1-D, HP OpenVMS Alpha Version
•
LEGATO NetWorker Administrator’s Guide, Release 6.0.1-D, HP OpenVMS Alpha
Version
•
LEGATO Command Reference Guide, Release 6.0.1
•
Technical Bulletins
Revision History of this Document
The LEGATO NetWorker Release Supplement, Release 6.0.1-x, HP OpenVMS Alpha Version,
was originally published on February 5, 2004.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
8
Chapter 1: NetWorker Software Release 6.0.1-D
This Release Supplement describes the new and enhanced features of the NetWorker
release 6.0.1-D software for use on the OpenVMS operating system. NetWorker is
supported on OpenVMS Alpha and I64 operating systems. This chapter describe this
release in general and any thing special for topics:
•
"Operating System Requirements" on page 9
•
"New or Enhanced Features" on page 10
•
"Installation and Update Notes" on page 15
•
"Known Limitations" on page 19
"OpenVMS I64 Supplement" on page 25describes topics that are particular to
OpenVMS on I64.
Operating System Requirements
NetWorker release 6.0.1-D requires OpenVMS Alpha Version 7.0 at a minimum.
However, be aware that some of the new features of this release of NetWorker are not
supported by OpenVMS versions prior to Version 7.2.
As described in "New or Enhanced Features" on page 10, NetWorker now supports
several features related to extended file specifications. These were introduced in
OpenVMS Version 7.2. A major component of extended file specifications is the new
ODS-5 volume structure, which allows applications to store and display long
filenames containing both lowercase and uppercase characters. Filesystem operations
remained case insensitive until the release of OpenVMS Version 7.3-1, which added the
abilities to distinguish between matching filenames with differing case and to control
whether processes ignore or honor the case sensitivity of filenames.
Important: Depending on which version of OpenVMS you are using, some or all of the
NetWorker features associated with extended file specifications and the ODS-5 volume
structure may be unavailable to you. Refer to
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
9
Chapter 1: NetWorker Software Release 6.0.1-D
New or Enhanced Features
This section describes the following new or enhanced features (listed alphabetically by
title), which are included in NetWorker release 6.0.1-D:
•
"Daemon Log File No Longer Created" on page 10
•
"Directory Structure Has Changed" on page 10
•
"Extended File Specifications Now Supported" on page 11
•
"nsrinfo Command Displays Filenames as Stored (New -r Option)" on page 13
•
"Save Behavior Has Changed - New Directive: norecord" on page 13
•
"Oracle and Oracle Rdb Database Backup and Recovery Support Added" on
page 14
New or enhanced features that are directly related to the NetWorker installation are
described in "Installation and Update Notes" on page 15.
Daemon Log File No Longer Created
This release of NetWorker software for OpenVMS Alpha no longer creates the log file
daemon.log. The nsrexecd daemon writes all entries to nsrexecd.log.
Directory Structure Has Changed
To support the new arbitrary installation destination (described further in "Installation
Destination Can be Specified By User" on page 15), the directory structure created by
NetWorker has changed with release 6.0.1-D. Previously, the NetWorker software was
installed on the system disk and used the following directory trees:
SYS$COMMON:[NSR]
SYS$COMMON:[NSR.LOGS]
SYS$COMMON:[NSR.RES]
.
.
.
SYS$SPECIFIC:[NSR]
SYS$SPECIFIC:[NSR.LOGS]
SYS$SPECIFIC:[NSR.RES]
You could use the system logical names SYS$COMMON, SYS$SPECIFIC, and
SYS$SYSROOT when accessing files in the NetWorker directory tree.
To support alternate directory installations, NetWorker release 6.0.1-D uses a new
directory level called NSR$COMMON as a prefix for the old ([.NSR]) directory
structure, which otherwise remains unchanged. For example:
NSR$COMMON:[NSR]
NSR$COMMON:[NSR.LOGS]
NSR$COMMON:[NSR.RES]
.
.
.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
10
Chapter 1: NetWorker Software Release 6.0.1-D
NetWorker release 6.0.1-D defines its own root directories (NSR$node) based on the
name of the node on which it is running. The cluster root directories ([SYS0.], [SYS1.],
and so on) are no longer used.
Because the system logical names SYS$COMMON, SYS$SPECIFIC, and
SYS$SYSROOT can no longer be used as a reliable method of specifying the location of
the NetWorker directory tree, three new logical names are defined by the startup
procedure in this release of NetWorker:
NSR$COMMON
NSR$SPECIFIC
NSR$SYSROOT
These new logical names can be used in place of the aforementioned system logical
names to identify the current location of the NetWorker directories, regardless of the
destination specified for the installation. The logical names defined in previous
releases of NetWorker that provided shortcuts to the NetWorker directories continue
to function as they did before. These include the following:
NSR$BITMAPS
NSR$LOGS
NSR$RES
NSR$SYSTEM
NSR$TMP
Extended File Specifications Now Supported
OpenVMS Alpha Version 7.2 introduced a new feature called extended file specifications.
This feature, which was enhanced in OpenVMS Version 7.3-1, includes the following:
•
A new, optional volume structure called On-Disk Structure Level 5 (ODS-5),
which extends the features of the existing ODS-2 disk structure adding support
for longer filenames and a wider range of legal characters for use within
filenames
•
Filename case preservation and recognition
•
Support for deeper directory structures
These new features and enhancements allow the OpenVMS operating system to store,
manage, serve, and access files with names that are more traditionally used in a
Microsoft Windows operating system environment.
To create a process environment where commands are examined using the ODS-5 file
specification syntax, you must set the DCL parse style to "extended" using the
following command:
$ SET PROCESS /PARSE_STYLE=EXTENDED
The default parse style is TRADITIONAL.
The sections that follow provide more detail on these new OpenVMS features and
explain how this release of NetWorker supports them. For more information on
extended file specifications, ODS-5 volume structure, and case-sensitive filesystem
operations, refer to the following OpenVMS documentation:
•
OpenVMS Alpha Version 7.3–1 New Features and Documentation Overview
•
OpenVMS User’s Manual (for OpenVMS Alpha Version 7.3-1)
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
11
Chapter 1: NetWorker Software Release 6.0.1-D
•
OpenVMS Guide to Extended File Specifications (for OpenVMS Alpha Version 7.2)
These documents are accessible from the following web site (as of the date of
publication of this manual):
http://h71000.www7.hp.com/doc/os731_index.html
Note: While some of the features described here were released with OpenVMS Version
7.2, some enhancements to these features were not added until OpenVMS Version
7.3-1. For the most part, the information in this section assumes the use of OpenVMS
Version 7.3-1. To determine which features and/or enhancements are available only in
Version 7.2, refer to the OpenVMS documentation.
About Longer Filenames and Additional Character Sets
On ODS-5 volumes, filenames (excluding the version number) can be up to 236 8-bit
characters or 118 16-bit characters in length. Filenames on ODS-5 volumes 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.
Filenames on ODS-2 volumes continue to use traditional filename syntax, where
filename length is limited to the 39.39 format and valid filename characters are
restricted to the ODS-2-compliant character set: A-Z, a-z, 0-9, $, _, and - (dollar sign,
underscore, and hyphen).
Note: Because some ODS-5 file names 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.
Additionally, file attributes specific to ODS-5 and not available on ODS-2 will not be
restored.
About Case Sensitivity
Traditionally, the OpenVMS operating system has stored all filenames in all uppercase
and ignored filename case during filesystem operations. The introduction of extended
file specifications in OpenVMS Version 7.2 enabled applications to store and display
file specifications in mixed case on ODS-5 volumes. (Note that ODS-2 continues to
support uppercase characters only.)
Until the release of OpenVMS Version 7.3-1, filesystem operations remained case
insensitive. OpenVMS Version 7.3-1 enhanced the case sensitivity features on ODS-5
volumes to enable applications and system tools to distinguish among filename
specifications that differ in case only.
You can set the DCL process to ignore or recognize case sensitivity with the following
command:
$ SET PROCESS /CASE_LOOKUP={BLIND|SENSITIVE}
/PARSE_STYLE=EXTENDED
The default case lookup type is BLIND.
Note: When issuing commands in a case-sensitive process environment, be aware that
only those filenames matching the specified name and case are returned.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
12
Chapter 1: NetWorker Software Release 6.0.1-D
About Deeper Directory Structures
Both ODS-2 and ODS-5 volume structures now support the creation and access of up
to 255 directory levels. On ODS-5 volumes, the directory names can be up to 236 8-bit
or 118 16-bit characters in length. (Directory names on ODS-2 volumes are still limited
to 39 characters.)
How NetWorker Implements/Supports These New Features
This release of NetWorker supports the new OpenVMS features related to extended
file specifications and the ODS-5 volume structure as follows:
•
When backing up or recovering files on an ODS-5 volume, NetWorker honors
both parse style and case sensitivity process settings.
•
When backing up or recovering files on an ODS-2 volume, NetWorker ignores
both settings.
nsrinfo Command Displays Filenames as Stored (New -r Option)
The nsrinfo command has a new option (-r) that allows you to view filenames as they
are actually stored in the NetWorker index. (This is the default behavior of the nsrinfo
command on other, non-OpenVMS platforms.)
The NetWorker client for OpenVMS stores filenames in all uppercase in the
NetWorker file index. This is done to help support the various case sensitivity options
available on OpenVMS. However, by default, the nsrinfo command displays
filenames on OpenVMS as they would appear if the files were restored (in mixed case,
for example). If you include the -r option in your nsrinfo command line, all filenames
are shown as stored (that is, in all uppercase).
The following sample command displays all filenames for a specific client as they are
stored in the NetWorker file index:
$ mcr nsr$system:nsrinfo -r -s <server> <client>
where <server> is the name of the NetWorker server being queried and <client>
identifies the NetWorker client computer whose file index is being queried.
Save Behavior Has Changed - New Directive: norecord
In previous versions of NetWorker, the save program did not record the backup time
on files it saved unless the record directive was specified. In V6.0.1-D and newer, the
save program records the backup time in the file header unless the norecord directive
is specified. This represents a change in the default behavior of save.
It is no longer necessary to specify the record directive when saving files. However, if
you do not want save to record the backup time on files it saves, you should specify
the norecord directive.
The default behavior was changed to prevent a problem whereby files that have been
recovered are not backed up during the next incremental save operation. The new
behavior uses the backup time stamp to avoid this situation.
If you install this version of NetWorker and perform an incremental save, the save
program will save all files that do not have backup timestamps associated with them.
If you have not used the record directive for past saves, the save program will save
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
13
Chapter 1: NetWorker Software Release 6.0.1-D
more files than is strictly necessary. After this initial occurrence, incremental saves will
behave normally. You can override this behavior by defining the logical name
NSR$IGNORE_BACKUP_TIME to any value. In this case, save will not consider the
backup timestamp when selecting candidates for incremental backup.
For more information about the record and norecord directives, refer to the LEGATO
NetWorker Administrator’s Guide, Release 6.0.1-D, HP OpenVMS Alpha Version
Oracle and Oracle Rdb Database Backup and Recovery Support Added
This release of NetWorker software for OpenVMS Alpha includes support for backup
and recovery of Oracle and Oracle Rdb databases. The following modules are included
in the NetWorker release 6.0.1-D kit:
•
NetWorker Module for Oracle
•
NetWorker Module for Oracle Rdb
They are listed as separate installation options by the NetWorker PCSI installation
procedure. You may install one, both, or neither of these options during a NetWorker
client installation. Both options support the use of the PRODUCT RECONFIGURE
command, which permits the addition of these modules to existing NetWorker client
systems at a later date if desired.
These database modules are described further in the sections that follow. For more
details, refer to related appendixes in the LEGATO NetWorker Administrator’s Guide,
Release 6.0.1-D, HP OpenVMS Alpha Version.
About the NetWorker Module for Oracle Rdb
The NetWorker module for Oracle Rdb allows you to back up your online Oracle Rdb
databases using NetWorker in tandem with the Oracle Media Management API (SBT
interface) and RMU, the Oracle Rdb management utility. Both client-initiated and
server-initiated backups are supported
During installation, the NetWorker module for Rdb supplies the following shareable
image, which Rdb uses to activate the NetWorker library:
NSR$SYSTEM:LIBNWRDB_SHR.EXE
The NetWorker installation also provides a command procedure template called
NSR$RDB_BACKUP_TEMPLATE.COM that can be customized for use during
server-initiated backups. You can create your own scripts if desired. Refer to the
LEGATO NetWorker Administrator’s Guide, Release 6.0.1-D, HP OpenVMS Alpha Version
for more details.
The NetWorker module on Alpha for Oracle Rdb requires a minimum version of
Oracle Rdb with the appropriate patch set as follows:
•
Oracle Rdb Release 7.1.2.1.0 (AMV), ID:5029367, Patchset::3261866
•
Oracle Rdb Release 7.1.2.1.1 (AMV Performance Kit), ID:5029333,
Patchset::3261862
•
Oracle Rdb Release 7.2.0.0.1
These Rdb releases are available for downloading from the Oracle Technology
Network (OTN) web site at:
http://otn.oracle.com/software/products/rdb7/index.html
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
14
Chapter 1: NetWorker Software Release 6.0.1-D
About the NetWorker Module for Oracle
The NetWorker module for Oracle allows you to back up your online Oracle databases
using NetWorker in tandem with the Oracle Media Management API (SBT interface)
and Oracle’s Recovery Manager (RMAN). Oracle 9i or newer is required for use with
this NetWorker module.
During installation, the NetWorker module for Oracle creates the following library,
and shareable image which you must link with your Oracle server after installation:
NSR$SYSTEM:LIBNWORA64.OLB
NSR$SYSTEM:LIBNWORA_SHR.EXE
Like the module for Oracle Rdb, the NetWorker module for Oracle also provides a
command procedure template that can be customized for use during server-initiated
backups. Instructions for customizing the template and relinking the library can be
found in the LEGATO NetWorker Administrator’s Guide, Release 6.0.1-D, HP OpenVMS
Alpha Version.
Installation and Update Notes
This section contains release notes related to NetWorker software installations. The
following sections are included:
•
"Installation Destination Can be Specified By User" on page 15
•
"Installation Options Have Changed" on page 17
•
"NSR$EXECD Account Issues Corrected" on page 17
•
"Old Directories Remain After Installation" on page 17
•
"Extracting the PCSI File on an ODS-5 Volume" on page 18
•
"Creating Node-Specific Root Directories" on page 18
For more detailed information on installing this release of NetWorker, refer to the
LEGATO NetWorker Installation Guide, Release 6.0.1-D, HP OpenVMS Alpha Version.
Installation Destination Can be Specified By User
Previous versions of NetWorker software for OpenVMS Alpha did not support the use
of the /DESTINATION qualifier with the PRODUCT INSTALL command.
NetWorker was installed on the system disk by default.
That restriction has been lifted in this release of NetWorker. You can now specify any
destination for the NetWorker installation provided you are installing on a system that
does not have a previous version of NetWorker. Otherwise, the existing installation
location is used and a new destination is not allowed.
The syntax for this new qualifier is as follows:
/DESTINATION=device-name:[directory-name]
To support this new feature, the old directory structure used by NetWorker has
changed and new logical names have been introduced to accommodate the new
directory structure. See "Directory Structure Has Changed" on page 10 for more
details.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
15
Chapter 1: NetWorker Software Release 6.0.1-D
For more information on using the /DESTINATION qualifier with the PRODUCT
INSTALL command, refer to DCL help on the PRODUCT INSTALL command.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
16
Chapter 1: NetWorker Software Release 6.0.1-D
Installation Options Have Changed
The installation procedure for NetWorker release 6.0.1-D has additional installation
options for the new Oracle and Oracle Rdb modules. See "Oracle and Oracle Rdb
Database Backup and Recovery Support Added" on page 14 for more information.
These options appear when you indicate that you do not accept the default options. For
example:
Do you want the defaults for all options? [YES] N
Add Storage Node Capability [YES]
Add Oracle/Rdb Database Backup Capability [NO]
Add Oracle Database Backup Capability [NO]
You can elect to install any combination of these options. (The storage node option is
installed by default, as was the case with previous versions of NetWorker for
OpenVMS Alpha.)
You can also add any of the three optional components to an existing client using the
PRODUCT RECONFIGURE command as described in the LEGATO NetWorker
Installation Guide, Release 6.0.1-D, HP OpenVMS Alpha Version.
NSR$EXECD Account Issues Corrected
If you installed earlier versions of the NetWorker software for OpenVMS Alpha, you
may recall that the NSR$EXECD account created by the installation procedure had a
blank account name and insufficient privileges for pre- and post-processing activities.
Those problems have been corrected in this release of NetWorker.
The installation procedure for release 6.0.1-D of NetWorker correctly assigns an
account name of "NetWorkr" (which fits within the allotted space of eight characters).
The privileges assigned to the NetWorkr account now include the IMPERSONATE
privilege (required to create a fully detached process for post-processing) and the
PRMMBX privilege (required by the preprocessing function, which uses a set of
permanent mailboxes for communication with the NSR$EXECD).
Old Directories Remain After Installation
When you install NetWorker release 6.0.1-D on an existing NetWorker client system,
old directories remain on the system after the update. The PCSI utility does not remove
directories containing files that were not supplied by the original installation
(customer-created files and files created or updated by the NetWorker software such
as log files). In particular, it does not remove the root directories, [SYS0.NSR...],
because they contain files such as nsrexecd.log and servers.;.
You may want to remove these obsolete directories and their contents after updating
to NetWorker release 6.0.1-D. Refer to LEGATO NetWorker Installation Guide, Release
6.0.1-D, HP OpenVMS Alpha Version for more information on cleaning up obsolete
directories.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
17
Chapter 1: NetWorker Software Release 6.0.1-D
Extracting the PCSI File on an ODS-5 Volume
If you extract the PCSI to an ODS-5 volume, you must rename the PCSI file after
extracting it from the self-extracting archive file. The OpenVMS PRODUCT utility is
not able to find a lowercase PCSI filename. When you extract the PCSI file from the
self-extracting archive the PCSI filename will be in lowercase. You must rename the
lowercase filename to uppercase. For example:
lgto-axpvms-snclnt-v0600-1d-1.pcsi must be renamed to
LGTO-AXPVMS-SNCLNT-V0600-1D-1.PCSI.
Creating Node-Specific Root Directories
The procedure for creating node-specific root directories in the installation guide
shows the wrong location of the NSR$CONFIGURE_NODE.COM file. ECO11
installed NSR$CONFIGURE_NODE.COM in SYS$STARTUP. The following is the
correct procedure:
To complete the installation of the NetWorker software in a cluster environment, you
must create system-specific root directories for the NetWorker directory tree. (The
PRODUCT INSTALL command does this only for the node on which you install the
software.)
The NetWorker software distribution provides a command procedure that creates the
necessary directories for you on each node. This command procedure is named
NSR$CONFIGURE_NODE.COM and resides in SYS$STARTUP.
The NSR$CONFIGURE_NODE.COM command procedure accepts one of the
following arguments:
• "ADD"—Adds the root directories for the NetWorker directory tree
• "REMOVE"—Removes the root directories for the NetWorker directory tree
If no argument is specified, a default value of "ADD" is used.
To use the NSR$CONFIGURE_NODE.COM command procedure to add NetWorker
root directories to each node in a cluster, do the following:
1. Log onto the node you want to configure.
2. Execute the command procedure as follows:
$ @SYS$STARTUP:NSR$CONFIGURE_NODE "ADD"
This command adds the necessary root directories to the current node. Repeat this
procedure for each node in the cluster.
Note: As an alternative to logging on to each node you want to configure, you can use
the SYSMAN utility to execute the command ON selected set of nodes.
For example:
$ MCR SYSMAN
SET ENVIRONMENT/NODE=(TOWN,CITY)
SET PROFILE/PRIV=(BYPASS)
DO @SYS$STARTUP:NSR$CONFIGURE_NODE "ADD"
EXIT
See the OpenVMS System Manager’s Manual for additional information on using the
SYSMAN utility.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
18
Chapter 1: NetWorker Software Release 6.0.1-D
To use the NSR$CONFIGURE_NODE.COM command procedure to remove
node-specific root directories, use the following command:
$ @SYS$STARTUP:NSR$CONFIGURE_NODE "REMOVE"
Known Limitations
This section describes problems or restrictions that are known to exist in this release of
the NetWorker software for OpenVMS Alpha. The following limitations (arranged
alphabetically by title) are described:
•
"nsrexecd ACCVIO on Multiprocessor Clients During Concurrent Saves" on
page 19
•
"Oracle and/or Oracle Rdb Limitations" on page 19
•
"Save Fails With RPC Error When Using TCPware" on page 21
•
"Directories That Do Not Have the Directory Bit Set" on page 22
•
"Files That Have the Directory Bit Set" on page 22
•
"Directories that have no Name" on page 22
•
"ODS-5 Volume Restrictions" on page 22
•
"Size Of A File Device Saveset" on page 24
nsrexecd ACCVIO on Multiprocessor Clients During Concurrent Saves
Under certain circumstances, the nsrexecd client daemon fails with an ACCVIO
during backup of OpenVMS Alpha clients. This situation occurs on OpenVMS Alpha
client computers with multiple CPUs when the Parallelism attribute on the NetWorker
server is set to a value greater than 8 and multiple, concurrent saves are occurring.
Significantly increasing the page file quota on the OpenVMS Alpha client has no
impact.
Oracle and/or Oracle Rdb Limitations
The following sections describe known limitations or problems with the NetWorker
modules for Oracle and/or Oracle Rdb:
•
"Parallel Recover Operations Not Supported (Oracle Rdb Module)" on page 19
•
"Parallel Backup Operation Restricted (Oracle Rdb Module)" on page 20
•
"RMU Tracing Feature Not Supported (Oracle Rdb Module)" on page 20
•
"RMU/LIBRARY/LIST Does Not Support Wildcards (Oracle Rdb Module)" on
page 20
•
"RMU/RECOVER/LIBRARY Fails When Specified Save Set Does Not Exist
(Oracle Rdb Module)" on page 21
•
"Problem With Rdb V7.2 Using A Plan (Oracle Rdb Module)" on page 21
Parallel Recover Operations Not Supported (Oracle Rdb Module)
The NetWorker module for Oracle Rdb does not support parallel recover operations.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
19
Chapter 1: NetWorker Software Release 6.0.1-D
Parallel Backup Operation Restricted (Oracle Rdb Module)
The NetWorker module for Oracle Rdb does not support both types of Rdb parallel
backups. There are two types of parallel backups. One type is a parallel backup using
threads. Rdb uses threads to do the backup when you use more than one writer in the
/LIBRARIAN=(WRITER= qualifier. The following shows an example of the
unsupported parallel backup using three writers:
$ RMU/BACKUP/LIBRARIAN=(WRITER=3) DISK$ORACLE[RDB72DB] MFP
However, the following command is supported:
$ RMU/BACKUP/LIBRARIAN=(WRITER=1) DISK$ORACLE[RDB72DB] MFP
The other type of parallel backup is initiated using the RMU/PLAN qualifier.
NetWorker does support this type of parallel backup. However there is a problem with
RMU that restrictes the number of parallel processes to 4 or less.
RMU Tracing Feature Not Supported (Oracle Rdb Module)
The NetWorker module for Oracle Rdb does not support the use of the TRACE and
LEVEL switches in an RMU/LIBRARIAN command. For example:
RMU/LIBRARIAN=(TRACE=filespec,LEVEL=level)
To cause the NetWorker software to write debug and trace messages to a specified file,
you must define the following NetWorker logical names before beginning the database
backup:
•
NSR_DEBUG_FILE
•
NSR_DEBUG_LEVEL
It is recommended that you deassign these logical names after the backup operation
completes. Refer to the LEGATO NetWorker Administrator’s Guide, Release 6.0.1-D, HP
OpenVMS Alpha Version for more information.
RMU/LIBRARY/LIST Does Not Support Wildcards (Oracle Rdb Module)
The RMU program supports a function that queries the librarian catalog. In the case of
NetWorker, this function queries the media and file indexes. The format for the RMU
list command is:
RMU/LIBRARY/LIST <saveset-name>
In general, RMU appends the string .RBF to any name supplied by the NetWorker Rdb
backup template file. Thus, if you use the template file, the resulting save set names are
of the form: <BACKUP_NAME><DATE-TIME>.RBF, where <BACKUP_NAME> is the
string assigned to the BACKUP_NAME symbol within the backup procedure, and
<DATE-TIME> is the date and time of the backup. The RMU/LIBRARY/LIST
command works correctly only when the fully specified save set name is provided as
shown in the following example:
$ 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
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
20
Chapter 1: NetWorker Software Release 6.0.1-D
EXPIRATION DATE/TIME:
VOLUME LABEL:
SHARING MODE:
ORDERING MODE:
Fri Oct 29 10:14:34 2004
wumpus.tz87.008
single user
sequential access
RMU/RECOVER/LIBRARY Fails When Specified Save Set Does Not Exist (Oracle
Rdb Module)
RMU generates a bugcheck if you specify a save set name that does not exist.
Problem With Rdb V7.2 Using A Plan (Oracle Rdb Module)
There is a problem with Rdb V7.2 when using a plan file. You will get an ACCVIO
when you try to use a plan file. The following shows an example of the ACCVIO:
$ RMU/BACKUP/PLAN backup.plan
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual
address=000000007FFA4F38, PC=0000000000706014, PS=00000000
%RMU-F-FATALOSI, Fatal error from the Operating System
Interface.
%RMU-I-BUGCHKDMP, generating bugcheck dump file
SYS$SYSDEVICE:[ORACLE_RDB]RMUBUGCHK.DMP;
%RMU-F-FTL_BCK, Fatal error for BACKUP operation at 23-FEB-2006
17:23:59.68
Save Fails With RPC Error When Using TCPware
The TCPware TCP/IP software for OpenVMS supports a maximum write size of 65440
bytes, which is lower than the default write size of the NetWorker save program.
Therefore, if you are using TCPware TCP/IP software and attempting to save large
files that exceed TCPware’s maximum write size limitation, the save program may fail
with the following error:
RPC error -- unable to send
If this problem occurs, define the logical name NSR$MAX_WRITESZ in NetWorker’s
startup command procedure (SYS$STARTUP:NSR$STARTUP.COM) to a value that is
equal to or less than the TCPware size limit. The recommended value for the
NSR$MAX_WRITESZ logical is 65024 bytes. (Note that the value assigned to this
logical name should be a multiple of 512 bytes.)
The NetWorker startup command procedure already contains the following,
commented-out definition:
$!
define/system/executive nsr$max_writesz 65024
To define the NSR$MAX_WRITESZ logical name, simply remove the comment
character (the exclamation point (!)) from this definition and re-execute the
SYS$STARTUP:NSR$STARTUP.COM command procedure.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
21
Chapter 1: NetWorker Software Release 6.0.1-D
Directories That Do Not Have the Directory Bit Set
Directories that do not have the directory bit set are saved as a regular file. In order for
a file to be directory, it must meet two conditions: have a ".DIR;1" type and version and
the directory bit must be set. If either of these two conditions are not met NetWorker
saves the file as a regular file. NetWorker does not save any files that might be in the
directory. You reset the directory bit by use the SET FILE/NODIRECTORY command.
In the NWRECOVER and NWARCHIVE GUI, a file with the directory bit reset is
displayed as a regular file. However, the ".DIR;1" is not displayed even though it is
displayed as a regular file.
Files That Have the Directory Bit Set
Files that have the directory bit set are saved and can be recovered. However,
NetWorker issues a warning: “size grew during save”. The file did not grow and is
recovered exactly as it was saved. The warning is there because of the logic that
calculates the size of the file thinks it is a directory and it is not.
A variation of a file with a directory bit set is a directory that has a version other than
“;1”. For example: FRED.DIR;2. The file system does not recognize this as a directory.
NetWorker treats it as a file with the directory bit set. You can create this file by editing
a directory.
Directories that have no Name
Directories that have no name are saved as a regular file by NetWorker, but cannot be
recovered. A directory that has no name would be displayed as ".DIR;1" when doing a
directory of a directory.
ODS-5 Volume Restrictions
There are certain restrictions with ODS-5 volumes. Different versions of OpenVMS
may behave differently. Also, how you have the process parse_style and case_lookup
affects what files will be saved and which ones will be recovered. You may want to
revaluate whether you want or need an ODS-5 volume.
Important: All of the restriction listed below have the process parse_style set to
extended. If you have the process parse_style set to traditional, you cannot ever access
files that are not all upper case characters.
The following sections describes these restrictions:
•
"Directories That Do Not Have a Type of “.DIR;1“" on page 23
•
"Directories With the Same Name But Different Case" on page 23
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
22
Chapter 1: NetWorker Software Release 6.0.1-D
Directories That Do Not Have a Type of “.DIR;1“
Directories that do not have a type of “.DIR;1” are not supported by NetWorker or by
the file system. For example: all_lower_case.dir;1 is NOT supported. However,
all_lower_case.DIR;1 is supported. For ease of explanation in this section I will call any
directory with type of “.dir;1” or any permeation of dir as an invalid directory. You can
create an invalid directory that has a type other than “.DIR;1” by using the RENAME
or SET FILE/ENTRY OpenVMS utilities. You can check to see if any of your directories
have been renamed using some variation of the following command:
$ pipe directory disk$i64v821:[000000...]*.*;* | _$ search sys$input ".dir;1",".Dir;1",".dIr;1"/exact
Even though the file system does not support invalid directories, NetWorker saves
these invalid directories and contents. However, there are certain restrictions that you
must follow:
•
By default when you schedule a group save from the server, you will save any
invalid directories and their contents.
•
If you do a NSRSAVE or NSRARCHIVE command from the DCL prompt, you
must have your process case_lookup set to blind to backup invalid directories.
•
If you are using NWBACKUP or NWARCHIVE, you must start them from a
process that case_lookup is set to blind to save invalid directories.
Even though the file system does not support invalid directories, NetWorker can
recover invalid directories and their contents. The recovered directory will have a
“.DIR;1” type which is supported by NetWorker and the file system.
Directories With the Same Name But Different Case
Having directories with the same name but different case will not be recovered
correctly unless you have your process setting for case_lookup set to sensitive. Setting
your process case_lookup to sensitive pertains to: NSRRECOVER, NSRRETRIEVE,
NWRECOVER, and NWRETRIEVE. This is not a restriction of NetWorker, but of the
file system. For example: you have Mixed_Case.DIR;1 and mIXED_cASE.DIR;1 in the
same directory. If the case_lookup is set to blind, on a recover the first directory is
created and when it tries to create the second one, the recover will receive a directory
already exists from the file system. To restore these directories, you must have the
process case_lookup set to sensitive.
Important: Do not create two directories with the same name but with “.dir;1“ and
“DIR;1“ types. For example: DISK$TMP:[TEST]fred.dir;1 and
DISK$TMP:[TEST]fred.DIR;1. When you do the following command your process will
loop:
$ set process/case_lookup=blind
$ directory DISK$TMP:[TEST...]*.*;*
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
23
Chapter 1: NetWorker Software Release 6.0.1-D
Size Of A File Device Saveset
There is a limit to the size of a file device saveset if you are going to recover an
individual file from the saveset. The following table show the saveset size limit for
versions of OpenVMS.
Table 1. Size of File Device Saveset
OpenVMS Version
Size of Saveset Limit
Below V7.3
2.1 Gigabytes
V7.3 and above
9.2 Exabytes
The above limites are only for recovering an individual file in a saveset on a file device.
If you recover the complete saveset these limits do not apply.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
24
Chapter 2: OpenVMS I64 Supplement
This release of NetWorker supports the OpenVMS I64 operating system. There are
very few differences between NetWorker for OpenVMS Alpha and I64. This chapter
describes the differences for the OpenVMS I64 operating system. The following topics
are included in this chapter:
•
"Operating System Requirements" on page 25
•
"Installation" on page 25
•
"Installation In A Mixed Cluster" on page 25
•
"Recovering an OpenVMS V8.2 System Disk" on page 26
•
"Known Limitations" on page 26
Operating System Requirements
NetWorker release 6.0.1-D requires OpenVMS I64 Version 8.2 as a minimum.
Installation
The installation of NetWorker on the OpenVMS I64 operating system is the same as
installing it on OpenVMS Alpha except that the filenames of the self-extracting archive
and PCSI file are different. The self-extracting archive filename is:
LGTO-I64VMS-SNCLNT-V0600-1D-1.EXE. The PCSI filename is
LGTO-I64VMS-SNCLNT-V0600-1D-1.PCSI.
Installation In A Mixed Cluster
When installing NetWorker in a mixed cluster of OpenVMS Alpha and OpenVMS I64
operating systems, you must install the appropriate kit on the appropriate operating
system. Also, you cannot have a common NSR$SYSTEM. If you install NetWorker on
the system disk, there should be no problem because you must have a separate system
disk for each architecture. If you specify the destination with the /DESTINATION
qualifier when installing the SNCLNT, be sure to specify a different destination for
each architecture. See the installation manual on installation using the
/DESTINATION qualifier.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
25
Chapter 2: OpenVMS I64 Supplement
Recovering an OpenVMS V8.2 System Disk
When recovering an OpenVMS V8.2 system disk, you must initialize the boot block on
the target disk after recovering the data. On previous OpenVMS versions you used
SYS$SYSTEM:WRITEBOOT.EXE to write the boot block after a recover. On OpenVMS
I64 you must use the SET BOOTBLOCK command. Use the procedure for recovering
a system disk in the LEGATO NetWorker Administrator’s Guide, Release 6.0.1-D, HP
OpenVMS Alpha Version and then use the SET BOOTBLOCK command instead of RUN
SYS$SYSTEM:WRITEBOOT.EXE. For example:
$ set bootblock dka100:
Known Limitations
This section describes problems or restrictions that are known to exist in this release of
the NetWorker software for OpenVMS I64. The following limitations (arranged
alphabetically by title) are described:
•
"Oracle Module Limitations" on page 26
•
"Oracle Rdb Module Limitations" on page 26
Oracle Module Limitations
Oracle has not been released for the OpenVMS I64 operating system at the time of this
release. Therefore the Oracle module is not supported with this release. To allow it to
be installed at a later date when it has been tested, the Oracle module option has been
left in the installation script. However, if you install the option, you will get the
following error when you try to execute RMAN scripts.
If you install the Oracle option and run an RMAN script, you will get the following
error:
RMAN-00571: =====================================================
RMAN-00569: ========= ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: =====================================================
RMAN-03009: failure of allocate command on t1 channel at
12/12/2005 09:35:06
ORA-19554: error allocating device, device type: SBT_TAPE, device
name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT)
layer
%SYSTEM-?-NOMSG, Message number 00001BC6
ORA-19511: Error received from media manager layer, error text:
SBT error = 7110, errno = 0, sbtinit: internal error - invalid
argument(s)
Oracle Rdb Module Limitations
Oracle Rdb module is enabled with the latest ECO. If you did not install the Oracle Rdb
Data Protection Module during the initial installation, you must reinstall
LGTO-I64VMS-SNCLNT-V0600-1D-1.PCSI and select the appropriate options along
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
26
Chapter 2: OpenVMS I64 Supplement
with the Oracle Rdb Data Protection Module. Once you install the Oracle Rdb Data
Protection Module, you can install the latest ECO and enable RMU backups and
recovers
The following sections describe known limitations or problems with the NetWorker
modules for Oracle and/or Oracle Rdb:
•
"Parallel Recover Operations Not Supported (Oracle Rdb Module)" on page 27
•
"Parallel Backup Operation Restricted (Oracle Rdb Module)" on page 27
•
"RMU Tracing Feature Not Supported (Oracle Rdb Module)" on page 27
•
"RMU/LIBRARY/LIST Does Not Support Wildcards (Oracle Rdb Module)" on
page 28
•
"RMU/RECOVER/LIBRARY Fails When Specified Save Set Does Not Exist
(Oracle Rdb Module)" on page 28
•
"Problem With Rdb V7.2 Using A Plan (Oracle Rdb Module)" on page 28
Parallel Recover Operations Not Supported (Oracle Rdb Module)
The NetWorker module for Oracle Rdb does not support parallel recover operations.
Parallel Backup Operation Restricted (Oracle Rdb Module)
The NetWorker module for Oracle Rdb does not support both types of Rdb parallel
backups. There are two types of parallel backups. One type is a parallel backup using
threads. Rdb uses threads to do the backup when you use more than one writer in the
/LIBRARIAN=(WRITER= qualifier. The following shows an example of the
unsupported parallel backup using three writers:
$ RMU/BACKUP/LIBRARIAN=(WRITER=3) DISK$ORACLE[RDB72DB] MFP
However, the following command is supported:
$ RMU/BACKUP/LIBRARIAN=(WRITER=1) DISK$ORACLE[RDB72DB] MFP
The other type of parallel backup is initiated using the RMU/PLAN qualifier.
NetWorker does support this type of parallel backup. However there is a problem with
RMU that causes and ACCVIO. See "Problem With Rdb V7.2 Using A Plan (Oracle Rdb
Module)" on page 28
RMU Tracing Feature Not Supported (Oracle Rdb Module)
The NetWorker module for Oracle Rdb does not support the use of the TRACE and
LEVEL switches in an RMU/LIBRARIAN command. For example:
RMU/LIBRARIAN=(TRACE=filespec,LEVEL=level)
To cause the NetWorker software to write debug and trace messages to a specified file,
you must define the following NetWorker logical names before beginning the database
backup:
•
NSR_DEBUG_FILE
•
NSR_DEBUG_LEVEL
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
27
Chapter 2: OpenVMS I64 Supplement
It is recommended that you deassign these logical names after the backup operation
completes. Refer to the LEGATO NetWorker Administrator’s Guide, Release 6.0.1-D, HP
OpenVMS Alpha Version for more information.
RMU/LIBRARY/LIST Does Not Support Wildcards (Oracle Rdb Module)
The RMU program supports a function that queries the librarian catalog. In the case of
NetWorker, this function queries the media and file indexes. The format for the RMU
list command is:
RMU/LIBRARY/LIST <saveset-name>
In general, RMU appends the string .RBF to any name supplied by the NetWorker Rdb
backup template file. Thus, if you use the template file, the resulting save set names are
of the form: <BACKUP_NAME><DATE-TIME>.RBF, where <BACKUP_NAME> is the
string assigned to the BACKUP_NAME symbol within the backup procedure, and
<DATE-TIME> is the date and time of the backup. The RMU/LIBRARY/LIST
command works correctly only when the fully specified save set name is provided as
shown in the following example:
$ 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
RMU/RECOVER/LIBRARY Fails When Specified Save Set Does Not Exist (Oracle
Rdb Module)
RMU generates a bugcheck if you specify a save set name that does not exist.
Problem With Rdb V7.2 Using A Plan (Oracle Rdb Module)
There is a problem with Rdb V7.2 when using a plan file. You will get an ACCVIO
when you try to use a plan file. The following shows an example of the ACCVIO:
$ rmu/backup/plan reg_backup_db_w3FP.plan
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual
address=000000007FF43F8C, PC=0000000000E59521,
PS=00000000
%RMU-F-FATALOSI, Fatal error from the Operating System
Interface.
%RMU-I-BUGCHKDMP, generating bugcheck dump file
DKA0:[ORACLE_REG]RMUBUGCHK.DMP;
%RMU-F-FTL_BCK, Fatal error for BACKUP operation at 23-FEB-2006
17:36:11.12.
LEGATO NetWorker, Release 6.0.1-x, HP OpenVMS Version
Release Supplement
28
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement