3Com NSR-ORA V3.2 manual Logging, Following is a representative sample from the log file

Page 14

The individual Components

The Archiving Monitor

3.1.2Logging

While the archiving monitor is active, the occupancy level of the archive direc- tory and other important events are logged at regular intervals (AMON_INTERVALL) in the protocol file ${DBO_CONFIG_DIRECTORY}/prot/redologs/amon.prot.

Protocol file

There are four generations of the protocol file. The current protocol file is appended to the file amon<sid>.old with each restart. If this file exceeds a size of 5 Mbytes, it is renamed from amon<sid>.002 to amon<sid>.003 and amon<sid>.old is changed to amon<sid>.002.

Archiving log file

All of the files backed up by the archiving monitor are logged in the /nsr/ora- cle/<ORACLE_SID>/prot/save_logfiles file. There are four generations of this file. With each restart, the file is appended to save_logfiles.old, if it does not exceed 1 Mbyte as a result. Were this size to be exceeded, save_logfiles.old is renamed save_logfiles.002 and the current file is renamed save_logfiles.old.

The following is a representative sample from the log file:

00-05-08:16:51:59: Amon Instanz /opt/networker/oracle/bin/amon

(26293) startet ============================

00-05-08:16:51:59: INFO: NSR_SERVER <psi>

00-05-08:16:51:59: INFO: Variable CONTR_SERVER set to <psi>

00-05-08:16:51:59: INFO: Amon Group name set to <amonorapsi>

00-05-08:16:51:59: INFO: AMON_MAX_LOGS <5>

00-05-08:16:51:59: INFO: AMON_MIN_LOGS <1>

00-05-08:16:51:59: INFO: AMON_INTERVAL <1800>

00-05-08:16:51:59: INFO: mail user <root>

00-05-08:16:51:59: INFO: amon_watch_dog_cmd </usr/bin/mailx -s ’Redologs not saved in 900 seconds’ root>

00-05-08:16:51:59: INFO: AMON_WATCH_DELAY <900>

00-05-08:16:51:59: INFO: AMON_SAVE_ARG_NR <50>

00-05-08:16:51:59: INFO: AMON_PS_FILE </nsr/oracle/ora/tmp/amon.ps>

00-05-08:16:51:59: INFO: AMON_RM_WITHOUT_MIRROR_DELAY <0>

00-05-08:16:52:00: INFO: forked expect proc <26301>

00-05-08:16:52:00: ARCHIVE_DIR=/oradb/db734/ora/saparch

00-05-08:16:52:01: ARCHIVE_FORMAT=oraarch%t_%s.dbf

00-05-08:16:52:01: AMON_EXP_TIME=

00-05-08:16:52:01: forked got process nr 26309

00-05-08:16:52:01: INFO: PS_FILE </nsr/oracle/ora/tmp/amon.ps>

00-05-08:16:52:01: INFO: checking Nr of Redologs

00-05-08:16:52:01: /oradb/db734/ora/saparch

00-05-08:16:52:01: DEBUG:oraarch1_42.dbf 01/11/00 14:55:59 s: 0 m: 0

System Administrator’s Guide

U42252-J-Z915-1-76

Image 14
Contents NSR-ORA Edition OctoberCopyright and Trademarks Boldface AudienceConventions Preface What is New in ReleaseUpdate from Previous Releases Introduction Introduction Physical Database StructureLogical Database Structure Database files Control file Database BackupArchive Mode of the Database System Administrator’s Guide U42252-J-Z915-1-76 ArchivingFunction Scope Function ScopeIndividual Components Archiving MonitorDatabase interface NSR-ORA Archiving Individual ComponentsArchive Tape libraryStarting and Ending the Archiving Monitor ExampleSubsequent status enquiry generates the following output # startamon.sh status ora ORACLESIDs oraLogging Following is a representative sample from the log fileBackup Component Individual ComponentsThe Backup ComponentOffline Backup of the Database Database interface NSR-ORA Backup Archiving ComponentIndividual Components Online Backup of the Database Configuration and managementChecking backups troubleshooting Log files from local backups not for NAS filersAmon Recordings Individual Components Installation and Configuration Quick StartInstallation then continues interactively InstallationInstallation and Configuration Licensing NSR-ORAKeylic command Installing NSR-ORA from CDIs to be installed Unix Client is requiredRufen Sie folgendes Kommando auf Invoke the following commandLog in as root Set the Display variable Use the following command to uninstall NSR-ORA under Linux HP-UXInstallation is then with the command ConfigurationHow to Proceed for an Update from an Earlier Version Unpack the NSR-ORA.tarfile from the CDFirst make sure of the following Example Configuration tool is invoked with the commandPreparations Establishing tablespace namesInstallation and Configuration Checking the Oracle Administration ProgramConfiguring NSR-ORA Parameters for configurensrora Oracle ParametersOracle owner group Directory where Oracle is installedOracle owner NetWorker ParametersNow the amon parameters are queried No compression is usedAmon Parameters Mirror OPS Parameters Recovery ParametersParameters with Expert Mode Amonmirrorgroup Defining backup sets save sets It is also recommended generally to carry out a full backup Configuring NetWorker # configurenetworker createdelete OraclesidRoot 68 # configurenetworker create ORA2 NSR-ORA in OPS clusters InstallationConfiguration On HP-UX /opt/networker/oracle/bin/startamon.sh NSR-ORA on Linux TroubleshootingBacking Up an Oracle Database Version 8.0 or higher Selecting the Type of Recovery Recovery ComponentControl file Database files Recovery Until Time with Logical ErrorsRecovery Automatic Recovery Crash Recovery Performing a recovery Manual recoveryAutomatic Recovery for an Optional Point in Time Start orarecutFully-automatic Recovery New recovery attempt with orarecut can be madeRecovery Offline recovery of an offline or full backup For the recovery of an online backup only RecoveryPerforming a recoveryRecover the remaining save sets again Open the database usingRecovery with Oracle Parallel Server OPS Oracle No space left on deviceRecovery Using NSR-ORA with NetApp Filers Running NSR-ORA with NAS devicesPrerequisites NSR-ORA and NetAppConfiguring NSR-ORA with NetApp Filers RecommendationsNSR-ORA and NetApp NETAPPSNAPNR=255 Nfssave RSH Scenario 2 Two Backups per Day Scenario 1 Three Backups per DayName Oraclesidndmp Two groups for pure snapshot backups Name Oraclesidndmp One group for pure snapshot backupsName Oraclesidsnapinterval Scenario 3 Seven Backups per DayDefining the Ndmp Client You should use /vol/vol0 as the save setNetWorker Resources GroupsInterval attribute For Ndmp backups NSR-ORA provides two new save sets ClientsNdmpoffline client has to be assigned to Ndmp attributePools Backup with NSR-ORABackup methods Amon ClientSavegrp completion notification For online backups the binary control fileInformation and log files of the current backup process Control file as an Ascii trace fileDebugging Recovery with NSR-ORARecover until time orarecut NSR-ORA and NetApp Crash Recovery nsrorarec Example 1 Recovery based on the last snapshotExample 2 Recovery based on a specified snapshot Database BackupShell parameter DefiningIndex Shell parameter Config.sh OutputFor NetApp Configurensrora For NetApp NetWorkerBackup component Components Shell parameter No space left on device error MessageShell parameter Nsrndmpsave command Installation Installing from CDRestore Redolog files OPS Configuration Installation on Remarkable thingsShell parameter Orarecut command For NetApp Nfssave System Administrator’s Guide U42252-J-Z915-1-76Update OPS

NSR-ORA V3.2 specifications

The 3Com NSR-ORA V3.2 is a versatile networking solution designed to enhance connectivity and streamline data management across various enterprise environments. With the rapid evolution of digital communication, 3Com recognized the need for a robust system that caters to the demanding requirements of today's businesses. The NSR-ORA V3.2 is specifically engineered to provide optimal performance, scalability, and reliability.

One of the standout features of the NSR-ORA V3.2 is its integrated network processing capabilities. This device employs advanced multi-layer switching technology that significantly boosts data throughput while maintaining low latency. This is particularly advantageous for organizations that rely on real-time data transmission for critical applications, such as VoIP and video conferencing. The ability to process large volumes of data efficiently ensures that businesses can operate seamlessly without disruptions.

Another key characteristic of the NSR-ORA V3.2 is its support for a wide range of networking protocols. The device is compatible with both IPv4 and IPv6, allowing businesses to transition smoothly to newer network architectures without the need for significant reconfiguration. This dual-stack capability not only enhances network flexibility but also future-proofs investments as organizations look to scale and adapt their digital infrastructure.

Security is at the forefront of the NSR-ORA V3.2's design. The device incorporates advanced security features such as firewall protection, intrusion detection, and secure VPN capabilities. These components work together to safeguard sensitive information and ensure that data integrity is maintained across the network. In addition to these features, the device offers comprehensive management tools, allowing network administrators to monitor performance and manage access controls more effectively.

The NSR-ORA V3.2 also excels in its interoperability with various devices and platforms, making it an ideal choice for enterprises that utilize a mix of legacy systems and modern technologies. Its compatibility with both wired and wireless networks provides businesses with the flexibility to design an infrastructure that meets their specific operational needs.

In summary, the 3Com NSR-ORA V3.2 is a powerful networking solution that combines advanced processing capabilities, robust security features, and a high degree of compatibility with diverse systems. Its emphasis on performance and scalability makes it a compelling choice for organizations seeking to enhance their network infrastructure in an ever-evolving digital landscape.