3Com NSR-ORA V3.2 manual Configuring NSR-ORA

Page 30

Installation and Configuration

Configuration

lation directory). This file contains SQL commands, which are executed each time sqldba or svrmgrl is called. There should be no SQL commands here which could lead to error messages of the form (ORA-xxxx) when sqldba or svrmgrl is called: NSR-ORA would notice these error messages when sqldba or svrmgrl is called and might draw false conclusions from them about the state of the data- base.

Please note that with ORACLE Version 9.x the svrmgrl command is no longer supported. Instead of this NSR-ORA uses the sqldba command by default.

4.3.3Configuring NSR-ORA

The following steps refer to the NetWorker client on which the ORACLE database and NSR-ORA are installed. For the first-time configuration of NSR- ORA or when changing to a more recent version, you can use the interactive tool configure_nsrora, which is located in the directory $NSR_INST/oracle/config. If you have several databases (several ORACLE instances) on your computer, you will have to call configure_nsrora once for each database (for each ORACLE_SID).

If you call configure_nsrora after changing to a different version, it will adopt the settings from the corresponding old files dbo${ORACLE_SID}.init as defaults. The tablespaces recorded in the directories monday to sunday will also be taken over and displayed, and the parameters given in the file shell_variables_for_${ORACLE_SID} will be used for the new version.

The tool first asks you for the name of the ORACLE instance (ORACLE_SID), the owner of the ORACLE software (ORACLE_OWNER), the owner’s group (ORACLE_GROUP), the path to the ORACLE software (ORACLE_HOME). If these variables are already defined as shell variables and exported, they will be offered to the user as the default setting. Then configure_nsrora creates the configuration directory /nsr/oracle/${ORACLE_SID} as well as the directory /nsr/oracle/etc. If the directory /nsr does not exist on a NetWorker client (this directory always exists on NetWorker servers) it will be created during instal- lation. But you can also create /nsr yourself before the installation (e.g. if you want to use links).

The file all_ORACLE_SIDs is created in the directory /nsr/oracle/etc and the ORACLE_SID is saved there. This file will be accessed if the archiving monitor daemons are automatically started up again following a boot of your NetWorker client for all ORACLE instances (i.e. for all ORACLE_SIDs).

System Administrator’s Guide

U42252-J-Z915-1-76

Page 29 Page 31
Image 30
Page 29 Page 31
Contents NSR-ORA Edition OctoberCopyright and Trademarks Audience ConventionsBoldface What is New in Release Update from Previous ReleasesPreface Introduction Physical Database Structure Logical Database StructureIntroduction Database Backup Archive Mode of the DatabaseDatabase files Control file 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 requiredInvoke the following command Log in as root Set the Display variableRufen Sie folgendes Kommando auf 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 ParametersNo compression is used Amon ParametersNow the amon parameters are queried Mirror Recovery Parameters Parameters with Expert ModeOPS Parameters 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 Installation ConfigurationNSR-ORA in OPS clusters On HP-UX /opt/networker/oracle/bin/startamon.sh Troubleshooting Backing Up an Oracle Database Version 8.0 or higherNSR-ORA on Linux Selecting the Type of Recovery Recovery ComponentRecovery Until Time with Logical Errors RecoveryControl file Database files 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 fileRecovery with NSR-ORA Recover until time orarecutDebugging 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.
Top Page Image Contents