3Com NSR-ORA V3.2 manual Automatic Recovery for an Optional Point in Time, Start orarecut

Page 48

Recovery

Performing a recovery

5.2.1Automatic Recovery for an Optional Point in Time

This section documents the use of the ora_recut command with the aid of which you can automatically recover a specific database level (recovery until time).

In order to recover a specific database level you can use the following command:

ora_recut [<ORA-SID>][-t <time>] [-v]

The ORACLE ID <ORA-SID> only needs to be specified if there is more than one database. If the -t option is used to define a point in time (format yyyy-mm- dd:hh:mm:ss,i.e., for instance: 1997-11-27:22:00:00) the ora_recut command will attempt to roll back the database to precisely that moment. If you do not enter a time here, then ora_recut will prompt you for a time presently. The -v option enables the output of additional information.

The following prerequisites must be met so that ora_recut can be used:

The database must be physically sound (operable) because ora_recut needs to query the position of the control files.

All the servers and device servers used for the backups have to be active.

The last full recovery made before the required point in time using

${ORACLE_SID}_full_save has to have run under Version 3.0 of NSR-ORA or higher.

If OPS is being used, you must pay attention to some further prerequisites (see section “Recovery with ORACLE Parallel Server (OPS)” for further information).

! With the automatic recover until time you cannot use backups which are distributed on several days of the week.

In order to restore a specific database level with these prerequisites you must carry out the following steps:

1.Specify the time.

2.Start ora_recut:

# ora_recut [<ORA-ID>] [-t <time>]

If ora_recut requires further information, you will be prompted to enter it. Basically ora_recut runs fully automatically. Only if errors occur that ora_recut cannot solve on its own, does an error message appear and you are informed that you can attempt to solve the problem yourself, for instance:

The database hadn’t gone down in 5 minutes

System Administrator’s Guide

U42252-J-Z915-1-76

Image 48
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 MonitorIndividual Components ArchiveDatabase interface NSR-ORA Archiving 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 Installation and ConfigurationInstallation then continues interactively Licensing NSR-ORAInstalling NSR-ORA from CD Is to be installedKeylic command 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-UXConfiguration How to Proceed for an Update from an Earlier VersionInstallation is then with the command Unpack the NSR-ORA.tarfile from the CDExample Configuration tool is invoked with the command PreparationsFirst make sure of the following Establishing tablespace namesInstallation and Configuration Checking the Oracle Administration ProgramConfiguring NSR-ORA Parameters for configurensrora Oracle ParametersDirectory where Oracle is installed Oracle ownerOracle owner group 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 RecoveryPerforming a recovery Recover the remaining save sets againFor the recovery of an online backup only 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 1 Three Backups per Day Name Oraclesidndmp Two groups for pure snapshot backupsScenario 2 Two Backups per Day Name Oraclesidndmp One group for pure snapshot backupsScenario 3 Seven Backups per Day Defining the Ndmp ClientName Oraclesidsnapinterval 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 attributeBackup with NSR-ORA Backup methodsPools Amon ClientFor online backups the binary control file Information and log files of the current backup processSavegrp completion notification 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 Backup Shell parameterDatabase DefiningShell parameter Config.sh Output For NetApp ConfigurensroraIndex For NetApp NetWorkerShell parameter No space left on device error Message Shell parameter Nsrndmpsave commandBackup component Components Installation Installing from CDConfiguration Installation on Remarkable things Shell parameter Orarecut command For NetAppRestore Redolog files OPS 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.