Information on this document

On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.
This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the format …@ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument

Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.
Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009

Release Notes

NSR-AMON Archiving Monitor V2.0

Contents

1. General
   1. Ordering
   2. Delivery
   3. Documentation
2. Software Extensions
   1. New in V2.0
   2. Changes between V1.4 and V2.0
3. Technical Information
   1. Resource Requirements
   2. Software Configuration
      1. Software Dependencies
   3. Product Installation
      1. Accessing the Software Package 
      2. Initial Installation
         1. Solaris (SPARC)
         2.  Linux
         3. HP-UX (PA)
         4. Windows
      3. Product Removal
      4. Update Installation
      5. License String Installation
   4. Product Operation
      1. General Information
      2. Information for Linux/UNIX Systems
      3. Information for Windows Systems
   5. Obsolete and Discontinued Functions
   6. Incompatibilities
   7. Restrictions
      1. General Restrictions
      2. Linux/UNIX Systems Restrictions.

1.     General

1.1    Ordering

1.2    Delivery

1.3    Documentation

• Manuals
  The following manuals are available:
  NSR-AMON V2.0 Administrator's Guide (English)
  The manuals are contained on the Networker DVD in the directory /documentation/manuals. They are also available on the web at:
  http://manuals.fujitsu-siemens.com -> Software -> Storage Software
• Other Documentation
  This Release Note can be found on the NetWorker DVD in /documentation/releasenotes.

2    Software Extensions

2.1    New in V2.0

• Use of Oracle RMAN for backup
  The option of  backing up the archived redo logs using Oracle RMAN (Recovery Manager) is now supported. This new operating mode is referred to as RMAN mode. The term NetWorker Save and Recover (NWSR) mode has been introduced for the alternate operating mode, which is still available.
  NSR-AMON in RMAN mode creates the RMAN scripts necessary for the backups on its own. The user consequently only requires a minimum knowledge of Oracle.
  All functions supported by the NSR-AMON in NWSR mode are also supported in RMAN mode, but there are some differences.
• Automatic Storage Management (RMAN mode only)
  Archived redo logs from archive destinations located in the ASM (Automatic Storage Management) disk groups are now supported.
• Flash Recovery Area (RMAN mode only)
  Archived redo logs from an archive destination located in the flash recovery area of a database are now supported.
• Database connection authentication
  In addition to system authentication (connect /), service authentication (connect /@service) and database authentication (connect user/password) are now also supported for setting up connections to Oracle databases.
• Configuration tool conf_amon
  The command  now  connects the Oracle database to verify that connection data is correct and to detect and check database parameters that are needed.
  The new  -verify  option makes it possible to check syntax and (limited) semantics of the configuration files.
  With the -offline option the communication with the NetWorker services, remote systems and the database can be suppressed.
• Automating the configuration process
  Further on the conf_amon configuration tool is enhanced, so that a configuration can be changed or upgraded in non-interactive mode (-autoanswer). Moreover a parameter value either is predefined by means of  input files (-input, -input_ccms) or  the value from the current configuration file or the parameter's default value is used.
  
• conf_nsr_amon enhancements
  The new -query option of the command determines the NetWorker resources which currently exist for NSR-AMON.
  The -delete option now determines the existing resources before deleting them.
  
• NetWorker Resources
  The NetWorker resources used by the archiving monitor can now be specified in detail with the parameters AMON_POOL, AMON_LABEL, AMON_LABEL_FIELDS, AMON_MIRROR_POOL, AMON_MIRROR_LABEL and AMON_MIRROR_LABEL_FIELDS. Therefore, conf_nsr_amon creates customized resources. Manual interferences are no longer needed or at least reduced.
  
• Limitation of  log file size 
  The size of the major log files used by the archiving monitor is now monitored during runtime. If a file gets too large a new generation is created. This is done by renaming the current file and opening a new one. Therefore, stopping and restarting the archiving monitor only because the log files have got too large is no longer necessary.
  With the configuration parameter AMON_MAX_SAVED_LOGFILES_SIZE_MB the size of the saved_logfiles file can be adjusted. The AMON_MAX_PROT_SIZE_MB parameter is used for the files amon.prot and amon_<db_id>.dbg in NWSR mode as well as the files amon.prot, oracle.dbg, mml_<n>.dbg and exp_internal.dbg in RMAN mode. The CCMS_MAX_PROT_SIZE_MB parameter turns the scale for the ccms_debug.log file.
  
• Number of save processes for redo log backups (NWSR mode only)
  For each NetWorker server the maximum number of save processes backing up archived redo logs can now be specified with the AMON_MAX_SAVES parameter. The default value is 4. The processes for the backup of the log_hist files are not included. If mirroring is configured, the save processes to the AMON_MIRROR_SERVER are counted on their own. This is important, especially when the NSR_SERVER and the AMON_MIRROR_SERVER are the same computer.
• Backup of redo logs after database online backup (RMAN mode only)
  Oracle archives redo logs also during online backups of the database. A backup can be used for a database recovery only if the redo logs created during the backup are available, too. Therefore, the archiving monitor now automatically backs up these redo logs within the first AMON_INTERVAL after a  backup of the database was done with NSR-ORA. So, the database backup is short term usable.
  
• Solaris Zones
  Installation of the NSR-AMON package within a non-global zone (container) and the automatic installation of non-global zones out of a global zone is supported.
  
• Solaris 10 Live Upgrade
  The package is installable with the Solaris 10 "Live Upgrade" feature.

2.2    Changes between V1.4 and V2.0

• Generation suffixes of the amon.prot and saved_logfiles files
  The suffixes identifying older generations of the amon.prot and saved_logfiles files are changed:
  from: .old, .001, .002, .003
  to: .001, .002, .003, .004
  
• Logging of the save processes
  In NWSR mode the save processes now log into temporary files. After the process has finished the contents of its file is copied to the amon.prot file by the archiving monitor.
  
• Delayed Remove
  This feature formerly performed in an independent process nsrdelayedrm is now done by the archiving monitor (daemon or service nsramond) itself. Therefore, the corresponding status and operations are now logged into the <DB-workdir>/prot/amon.prot file.

3    Technical Information

3.1     Resource Requirements

3.2    Software Configuration

• The software versions shown in the following tables are supported on the database server:

• The following NetWorker versions are supported on the NetWorker server and the database server:
  1. FSC NetWorker Unix/Linux V7.2, V7.3
  2. EMC NetWorker Unix/Linux /Windows 7.2.x, 7.3.x 

3.2.1    Software Dependencies

3.3    Product Installation

3.3.1 Accessing the Software Package 

3.3.2    Initial Installation

3.3.2.1 Solaris (SPARC)

3.3.2.2 Linux

• SuSE Linux: /media/cdrecorder or /media/cdrom or /media/dvd
• RedHat Linux: /mnt/cdrom 

3.3.2.3 HP-UX (PA)

3.3.2.4 Windows

1. Login as local user, who has system administrator privileges.
2. If you use the DVD to install the software, double click the symbol of the file setup.exe in the directory products\Window_X86\NSR-AMON_V2.0A00
   If you use the downloaded file to install the software, double click the symbol of the file NSR-AMON_2.0A0005.zip.

1. Start the Windows Explorer and select the DVD drive.
2. Double click the symbol of the file setup.exe in the directory products\NSR-AMON_V2.0A00

• one for the program and library files
• one for the base work directory
  

3.3.3  Product Removal

3.3.4    Update Installation

3.3.5    License String Installation

3.4    Product Operation

3.4.1    General Information

• Behavior of SQL*Plus
  NSR-AMON expects the default behavior of SQL*Plus, such as SQL>  as SQLPROMPT and not more than the default output as the result of each statement (e.g. NOT something like the elapsed time printed at the end of each output). In Oracle 10g or newer the behavior can be modified by a site and a user profile setup script. NSR-AMON uses the file <DB-workdir>/config/login.sql as the user profile of SQL*Plus. If not already existing conf_amon creates this file with entries presently necessary for some customer configurations (as far as is known).
• Changing from NWSR to RMAN mode
  If you change the operating mode from NWSR to RMAN mode records for archived redo logs already backed up in NWSR mode and deleted from the archive destinations must be manually removed from the RMAN repository. For this purpose proceed as follows:
  
  1. Start the RMAN client and connect it to the target database and if necessary to the recovery catalog. You can find an example for the instructions in the manual, chapter Monitoring und Troubleshooting, section backup Maintenance.
  2. Enter the command
     RMAN> crosscheck archivelog all;
     All records for archived redo logs not found in the archive destinations are set to Expired. You can check it with the list archivelog all; command (column S is set to X)
  3. With the command
     RMAN> delete expired archivelog all;
     you can remove all records for archived redo logs showing the status Expired.
     
• If you change the operating mode from NWSR- to RMAN mode or vice versa the log files of the previous mode not used in the new mode are not removed automatically. If necessary these files can be removed manually from the <DB-workdir>/prot, <DB-workdir>/prot/dbg and <DB-workdir>/tmp directories.
  
• CCMS connection password
  When CCMS monitoring is used the password (CCMS_PASSWORD parameter) must be entered again because the encryption algorithm is changed.
• Archive Destination on NFS file system
  If the Archive Destination resides on a NFS file system, the user root must have unrestricted access. This has to be specifed with the appropriate option on the host where the file system is shared.
  Example Solaris:
  share -F nfs -o anon=0,rw=ibiza /home3
• MaxDB
  MAXDB_ADMIN_TOOL:
  Complete path to the Database Manager CLI dbmcli. On Mircosoft Windows systems you must specify the suffix .exe and slashes (/) instead of backslashes (\).
  MAXDB_LOGIN_DATA:
  
  1. The specified SYSDBA user must have at least the DBInfoRead or the Backup server authorization.
  2. An XUSER key is specific for an operating system user.
     Linux/Unix systems: The XUSER key must be created for a root user.
     Microsoft Windows systems: The login account under which the NSR-AMON service should run must be the one for which the XUSER key was created.
     

3.4.2    Information for Linux/UNIX Systems

• High Availibility Cluster
  If a database instance is switched to another cluster node, the high availibililty monitor (e.g. PRIMECLUSTER) must
  
  • stop the archiving monitor on the node active up to now.
  • delete the file <base-workdir>/etc/workdir_<db_id> on the node active up to now and create it at the new node (the file must exist on one node only, otherwise booting the systems would start the archiving monitor on multiple nodes).
  • start the archiving monitor at the new node.
• Renaming of  workdir_<db_id>
  If you rename the file workdir_<db_id> within the directory <base-workdir>/etc, use a name like <prefix>workdir_<db_id>. If you rename it using a suffix (e.g. workdir_DB1.sav) the nsramon command will attend a corresponding database (e.g. DB1.sav). Please note that the nsramon command is used during system startup.
  
• Shutdown of the database (RMAN mode)
  In RMAN mode the archiving monitor is connected to the database via SQL*Plus and RMAN permanently. On some systems the database could therefore only be shut down with shutdown immediate instead of shutdown normal. To avoid this problem, first stop the archiving monitor and then the database.
• Red Hat Enterprise Linux 5 for IA64
  Red Hat Enterprise Linux 5 for the 64-bit Intel Itanium2 architecture includes runtime support for 32-bit applications through the use of Intel's IA-32 Execution Layer. The IA-32 Execution Layer is provided on the Supplementary disc for the Intel Itanium2 architecture. In addition, a set of 32-bit libraries and applications are provided on a separate 32-bit Compatibility Layer disc. The IA-32 Execution Layer and 32-bit compatibility packages together provide a runtime environment for 32-bit applications on the 64-bit native distribution.
  After the installation of the Red Hat Enterprise Linux 5 for the Intel Itanium2 Architecture, install the ia32el package of the Red Hat Enterprise Linux 5 Supplementary CD
  # rpm -Uvh ia32el-<version>.ia64.rpm
  Replace <version> with the corresponding version of the ia32el package to be installed.
  Install afterwards compatibility libraries by inserting the 32-bit Compatibility Layer disc. 

3.4.3    Information for Windows Systems

• Configuration
  The NSR-AMON configuration file parameters should neither be defined as system nor as user variables in the Windows environment. This applies especially for ORACLE_SID and ORACLE_HOME.
  
• ORACLE_HOME and ORACLE_ADMIN_TOOL must be specified with slashes (/) instead of backslashes (\).
  
• Mail command
  A mail command is required for operating NSR-AMON. If there is no email program on the computer that is suitable for the MAIL_CMD parameter, one must be installed, e.g. Blat.
  
• High Availability Cluster
  If the database instance is switched to an other cluster node, the NSR-AMON service must be stopped on the old node and started on the new one. If on the old node the Startup type of the NSR-AMON service was Automatic you must then set it to Disabled or Manual.
  

3.5    Obsolete and Discontinued Functions

• Oracle 8 is no longer supported.
  
• Windows 2000 is no longer supported.
• The file <DB-workdir>/prot/delayed_rm.prot is no longer used. The file amon.prot is now used instead.

3.6     Incompatibilities

3.7    Restrictions

3.7.1    General Restrictions

• RMAN mode
  The RMAN mode is restricted to Oracle 10g.
  On Windows and Linux IA64 systems the RMAN mode is not supported.
• Oracle Cluster File System V1.0 (OCFS1)
  Only datafiles, control files and spfiles can be put on OCFS1 file systems. Archived redo log files on OCFS1 file systems are not supported by NSR-AMON.
  

3.7.2 Linux/UNIX Systems Restrictions

• The nosuid option is not allowed for file systems a database or the Oracle software is located on.
• Retention Policies (RMAN mode)
  NSR-AMON and NSR-ORA in RMAN mode can only be used with the Oracle retention policy deactivated (persistent RMAN configuration CONFIGURE RETENTION POLICY TO NONE;). This setting is automatically forced by  NSR-AMON. The retention period of the backups is always determined by the NetWorker Retention Policy. Please note that the backups are only accessible as long as they are listed in the RMAN repository. For more information see the manual NSR-AMON Administrator's Guide V2.0 , chapter Configuration, section Parameters to Apply the Browse and Retention Policies. 
• Autobackup of control file (RMAN mode)
  NSR-AMON and NSR-ORA in RMAN mode can only be used with the function autobackup of control file deactivated (persistent RMAN configuration CONFIGURE AUTOBACKUP OFF;). This setting is automatically forced by  NSR-AMON. Together with the archived redo logs NSR-AMON always backs up the control file and as the case may be the server parameter file (spfile).
  If you change the physical structure of the database and you do not use a recovery catalog, it is therefore recommended to subsequently archive some redo logs manually (ALTER SYSTEM SWITCH LOGFILE;) forcing NSR-AMON to back up the modified control files.
• RAC with HP-UX (PA) 
  RAC with HP-UX is not supported.
  
  

Microsoft®, Microsoft Windows®, and Microsoft Windows NT® are U.S. registered trademarks of Microsoft Corporation.
HP-UX® Release 10.20 uand later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX® 95 branded products.
AMD Opteron™ is the trademark owned by Advanced Micro Devices, Inc.
Intel®, Intel Itanium®, Intel Pentium®, and Intel Xeon™ are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
EMC and NetWorker are trademarks of EMC Corporation.
Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.
NetApp, Data ONTAP, SnapDrive, SnapManager, SnapMirror, SnapRestore, and WAFL are registered trademarks and Network Appliance Inc. in the U.S. and other countries.