We create a backup copy and restore the Oracle database. Backup and recovery of Oracle Database data

Oracle backup must be performed efficiently and quickly, since Oracle database servers are usually used in the most loaded operations in the commercial segment. Handy Backup organizes backup of Oracle backups through standard utility Oracle backup RMAN.

Benefits of Using Oracle RMAN Backup with Handy Backup

The specialized Oracle backup plugin in Handy Backup acts as a graphical add-in (GUI) over the standard Backup RMAN program, preserving all the functions and capabilities provided by the RMAN Backup Oracle utility.

Backup of an Oracle database in Handy Backup can be performed according to a schedule in specified time and at specified intervals (from one minute to several months inclusive), as well as upon the occurrence of a system event (user login, connection of USB storage).

Various techniques for backing up and restoring Oracle from a backup

With Handy Backup, you can perform a mixed, differential or incremental Oracle backup, save multiple versions of an Oracle database backup from one source data set, encrypt or compress the resulting RMAN backup, etc.

Storage for Oracle database backup

Using Handy Backup, you can configure the RMAN utility to back up backups to a variety of data storage facilities, including such modern storage media as:

• Local drives, USB storage devices, attached network drives;
• Network shares, NAS devices, FTP, SFTP, FTPS servers, private clouds;
• Cloud services Yandex Disk, Google Drive, Amazon S3, Dropbox, OneDrive and others;
• Specialized reliable storage HBDrive, suitable for Oracle database backups.

Note: server solutions Handy Backup Office Expert and Handy Backup Server Network contain out of the box all available information storage plugins, allowing you to organize an Oracle database backup into the most convenient and reliable data storage for a specific task.

Why is it convenient to use RMAN backup via Handy Backup?

The interface and set of functions of Handy Backup allow you to use the RMAN backup utility as one of the program plugins under the control of a single interface. You can not only easily create or modify Oracle database backup tasks, but also manage them:

• Run other applications before and after the task, effectively replacing the typical Oracle PL SQL backup script with a convenient visualized solution.

• Receive reports on backup tasks and view work logs in the program window or by email, with a customizable sending frequency.

• Use it network solutions Handy Backup for Oracle backup on remote machines from a central administrative panel.

How to make an Oracle backup using Handy Backup

Here you will find brief instructions on how to create a backup of an Oracle database using Handy Backup. The program takes care of all the work of interacting with the RMAN backup utility, allowing you to backup the Oracle database and restore the database from the backup automatically.

1. to work with backup functions.
2. Create a new task in Handy Backup using the "New task" menu or button.
3. In Step 1, select a backup task. Click Next.
4. In Step 2, select the Oracle plugin from the Database group in the left pane.

1. Double click on the plugin name or click ">>".
2. The data selection dialog will open. Check the boxes next to the databases for Oracle backup.

1. Click OK and return to Step 2. Continue with the DB:

• Select the appropriate storage in Step 3.
• Choose to create a full/incremental Oracle backup in Step 4.

• Configure compression and/or encryption in Step 5.
• Set the operation schedule by time or by event in Step 6.
• Run other programs, commands, or packages before and/or after the task in Step 7.
• In Step 8, name your task and complete the New Task Wizard.

Note: you can subsequently change any details of any task using the tab system in the task view window. Each tab corresponds to a specific step in the New Task Wizard.

Restoring Oracle from a backup

To restore a database from a backup for Oracle, you need to create an automatic data recovery task. Launch the New Task Wizard and use the following instructions:

1. Select a recovery task in Step 1. Go to Step 2.
2. Open the data warehouse, find the Oracle database backup directory, and in it the file backup.hbi.

1. Double-click the file name or click Next.
2. If you want to let Oracle restore the database from the backup to its original location, simply click the "Next" button until the end of the task wizard.
3. If you want to change the restore location, click on the "Change Location" button.

In the dialog for selecting a recovery location, specify the server to which you are going to restore Oracle from the backup. This way you can clone and replicate Oracle backups.

Try the Oracle RMAN backup plugin in action by downloading and installing Handy Backup right now with all available features and plugins for a 30-day free trial!

Hello, dear readers of the blog site! I present to your attention an article about backup and restoration of the Oracle database. I think this material will be useful for administrators performing backups and restores on an Oracle server using the Recovery Manager (RMAN).

Backup and Restore

To understand the article, it is advisable to have knowledge in the following areas:

• Relational database concepts and administration fundamentals.
• The OS environment under which the Oracle database is running.

In fact, this article is the introductory one in a series of articles devoted to the basic concepts of backup and recovery. I recommend this material for all users responsible for backup and recovery. In general, the article will be of interest to all users, not just those using RMAN. In the future, I plan to tell you more about backup and recovery technologies using the Recovery Manager. Users managing backup and recovery without RMAN will need to familiarize themselves with the concepts in this article and subsequent backup and recovery review posts.

Thus, the purpose of the proposed set of articles is to make general overview concepts of backup and recovery, review Oracle database files related to backup and recovery, and explore the tools available to backup and restore your database, protect against information loss and other errors.

So, what is backup and recovery? Backup and recovery implies various strategies and procedures related to protecting your database from information loss and restoring the database after any type of data loss.

Physical and Logical Backups

Backup is a copy of data from your database that can be used for recovery. Backups can be divided into physical backups And logical backups.

Physical backups are backups of physical files used to store and restore your database, such as data files, control files, log file archives. Ultimately, each physical backup is a copy of files that store database information in another location (on disk, on tape, etc.).

Logical backups contain logical data (for example, tables or stored procedures), exported from the database using the Oracle export utility and stored as a binary file - for subsequent import into the database using the Oracle import utility.

Physical backups are the foundation of any reliable backup and recovery strategy, while logical backups are useful addition to physical backups in many cases, but they are not sufficient to provide satisfactory protection against information loss without physical backups.

Further, the term “backup” in this article about backup and recovery will mean, first of all, physical backups (if it is not specified which backups we are talking about), and make a backup part or the entire database will mean making one of the types of physical backups. The emphasis in the article is mainly on physical backups.

Errors and Failures that require Restoring from Backup

While there are several types of problems that can interrupt the normal functioning of an Oracle database or I/O operations, typically only two of them require administrator (DBA) intervention and media recovery: media failures (media failures). hard drives etc.), and user errors.

Other failures may require DBA intervention to reload the database (after an instance crash) or allocate additional disk space(after a failure while executing sql sentences due, for example, to an overflowing data file), but these situations will not, generally speaking, lead to data loss and will not require restoration from a backup.

User errors

User errors occur either due to errors in the application logic, or when deviating from the operating instructions, the data in your database is changed or deleted incorrectly. Information loss due to user error includes mistakes such as deleting important tables or deleting or changing the contents of a table. While user training and careful privilege management can protect against most user errors, your backup strategy will determine how gracefully you recover lost data when user error causes information loss.

Failure of storage media

Media failure– this is a failure when reading or writing a file on the disk that is required for the database to work, due to physical problem with disk. For example, head failure. Any database file can be damaged due to media failure.

The appropriate method for recovering from a media failure depends on what files were affected by the failure, as well as the types of backups available.

Oracle Backup and Recovery Solutions: RMAN and Custom Backups

To perform backup and restore based on physical backups, you have two solutions at your disposal:

• Recovery Manager– tool (works from the command line or from GUI Enterprise Manager), which integrates with sessions running on the Oracle server to perform a number of actions related to backup and recovery, as well as maintaining a history of your backups
• Traditional custom backup and restore(i.e. user-managed and controlled) where you directly manage the files that make up your database using OS commands and SQL*Plus backup and restore capabilities

Both methods are supported by Oracle and are fully documented. Recovery Manager, however, is the preferred solution for database backup and recovery. It can perform the same types of backup and restore available with custom backup and restore, but in a much simpler manner, and RMAN also provides a common interface for backup tasks across different operating systems, and also offers a number of backup technologies not available with manual backup methods.

Most of the article will focus on backup and restore using RMAN. I plan to describe custom backup and recovery methods in future articles on backup and recovery.

Whichever method you use (RMAN or a custom method), you can supplement your physical backups with logical backups of schema objects, which are carried out through export utilities. Data saved in this way can be later imported to recreate these objects after restoring from a physical backup. However, I will not consider logical backups in this article (then I want to write a separate article about logical backups).

Thank you for your attention! Don't miss the continuation of the topic of backup and recovery in future articles, which I will try to write in the near future. Good luck!.

This document describes the policies and procedures that must be followed for enterprise-level Oracle backups using Bacula Enterprise Edition software. The document also includes various scenarios for restoring an Oracle backup.

Oracle Backup Overview

Bacula Enterprise Edition uses a unique Oracle backup plugin to simplify Oracle backup and recovery. The plugin allows you to use advanced methods for hot and cold Oracle backups and restore data and configurations stored on 10th and 11th generation servers. The Oracle database backup plugin allows you to restore Oracle to a specific point in time (to a checkpoint), filter objects during Oracle backup and restore them. It also allows you to create Oracle backups with configuration information such as parameters. The Oracle database backup plugin is supported by Linux 32/64 bit platforms supported by Oracle, as well as Oracle 10.x, 11.x databases.

Other benefits of Oracle backup with Bacula:

• When using RMAN mode, the plugin allows you to create incremental and differential Oracle backups at the block level.
• RMAN's change tracking feature, used for subsequent incremental backups, significantly improves backup creation by recording the changed blocks of each data file in a change tracking file.
• The database administrator does not have to have skills in working with the Oracle database or be able to create complex scripts for Oracle backups.
• This plugin for creating and restoring Oracle backups is also designed to create backup copies of configuration information, such as parameters.

This document presents various ways and Oracle backup strategies using Bacula Enterprise Edition software and related plugin.

Oracle Backup Glossary

The following terms are used in this document:

• ARC(Archival log)– standard method used to ensure data integrity. The basic idea behind ARC is that changes made to data files (which contain tables and indexes) will only be written after the changes have been logged, that is, after the log entries describing the changes have been migrated to permanent storage.
• PITR Oracle Predefined Point Recovery (PITR) restores a database to a specific point in time and then uses incremental backups and rollbacks to restore the database to that point. PITR recovery is sometimes called incomplete because PITR recovery restores the database to a specific point, and the procedure itself does not use all Oracle backup log files.
• RMAN Oracle Recovery Manager or RMAN, a command line and Oracle Enterprise Manager-based tool, is the Oracle-recommended method for database backup and recovery. The RMAN utility is designed to work directly with the server. The utility allows you to identify damaged data blocks during database backup and recovery. The RMAN utility optimizes performance and memory consumption during backup creation by compacting files and compressing the backup set.
  http://docs.oracle.com/cd/B28359_01/backup.111/b28270/toc.htm
• EXP/IMP Oracle export (exp) / import (imp) utilities are used to perform logical database backup/restore. When exporting, a dump of database objects is created in the form of a binary file, which can then be imported into another Oracle database.
• Data Pump Oracle Data Pump technology is a more modern, faster and more flexible alternative to the “exp” and “imp” utilities that were used in previous versions Oracle. Unfortunately, this new method does not support outputting data directly to a FIFO file. Therefore, the use of tools Data Pump requires you to first dump the data to disk and then read that data using the Bacula Enterprise File Daemon. Current version Oracle backup plugin does not support Data Pump technology.
• SBT By default, RMAN sends all Oracle backups to a special system directory on disk. You can also configure RMAN to create backups on other media, such as magnetic tape, using the SBT module. Bacula in this case will act as the Media Manager, and the data will be transferred directly from RMAN to Bacula.
• libobk The SBT interface is implemented based on the libobk library file.
• Tablespace The database is divided into logical storage areas called table spaces, which are grouped based on their logical structure. For example, table spaces typically group all application objects together to simplify administration.
• Scheme is a collection of database objects. The database user owns the schema. The schema has the same name as its user. Schema objects are logical structures that are directly related to database data. Schema objects include structures such as tables, views, and indexes. (There is no relationship between a tablespace and a schema. Objects from the same schema can be in different tablespaces, and tablespaces can contain objects from different schemas.)
• Instance An Oracle database server consists of an Oracle database and an Oracle database instance. Each time the database is started, a system global area (SGA) is allocated and Oracle background processes are launched. Combination background processes and memory buffers is called an Oracle instance.
• SID The Oracle System ID (SID) is used to identify the database in the system. For this reason, more than one database with a unique SID cannot exist on the same system. Typically, the SID is specified by the “ORACLE_SID” variable. Alternatively, you can find this identifier in the first field (before 🙂 of the /etc/oratab.
• Copy Each time you open a database using the ALTER DATABASE OPEN RESETLOGS command, such a copy is created.
• SCN System change number (SCN) is a number in Oracle that increases sequentially with each change made to the database: insertion, update, deletion. The SCN number also increases as a result of DB interaction.
• Oracle Recovery– an action leading to data extraction from a backup. After restoring the database, you may need to return it to original state, that is, roll forward to a certain control point.
• Return to original state– this is a procedure for updating a restored data file using archived logs of “redo” operations and current logs, that is, using changes made to the database after creating a backup.
• Function Proxy Copy is a feature of the RMAN utility that is not supported by the current implementation of the SBT interface in Bacula Enterprise software.

Legend

• Values ​​enclosed in parentheses< >entered by users, for example, must be replaced with the current ORACLE_SID number. If your ORACLE_SID number is a test TEST, the file written as init .ora will look like initTEST.ora.
• % means that the command must be run by a normal user.
• # means the command must be run as a root user account.
• RMAN> means that the command must be run inside an rman session.
• SQL> means that the command must be run inside a sqlplus session.

1. Oracle backupwith plugin

Selecting an Oracle backup method: Dump or RMAN utility

The table below shows the benefits of backup recovery methods supported by the Bacula Enterprise plugin for Oracle. To choose one or another method, be guided by such features as the ability to restore an Oracle backup to a specified checkpoint, the ability to filter objects during backup or restore. The user can also combine the methods of creating a dump and using the RMAN PITR utility for one cluster.

The RMAN utility also allows you to use modern methods, thanks to which you can send data through Bacula Enterprise's SBT interface, for example, to tape and disk simultaneously for faster recovery.

Table 1. Oracle Recovery Methods

*When using the RMAN SBT interface, the recovery speed will depend on various elements such as media type (tape or disk), network transfer speed, availability of the device with the guardian daemon, etc... In Bacula Enterprise software version 6.4 and higher a device with a guardian daemon can use the same disk volume for multiple parallel restores. Thus, it is possible to perform multiple Oracle restore and backup tasks simultaneously.

Configuring RMAN SBT

This section of the user manual describes correct installation and configuring the Bacula Enterprise SBT interface with using Oracle and RMAN.

When creating an Oracle backup or running a backup from RMAN, RMAN will need to contact the centralized Bacula Enterprise Director to obtain file and volume information or to run an Oracle backup or restore. To establish a connection, you will need general batch files FIFO and b-console.

When using the oracle-sbt-fd plugin, the director will not be able to run an Oracle backup from the b-console or from the schedule. Only the RMAN utility will be able to initiate a session and start the backup. Consider the fact that you are still running a standard Oracle system backup and then use RunScript to call RMAN automatically.

Configuring Bacula When using the SBT interface, you must install the b-console (Bacula console). The console must allow you to connect to a centralized director and access local client, Oracle backup task, and other pool characteristics.

To use the console with disabilities, you can use the following console definition:

Figure 1. Oracle backup when interacting between RMAN and Bacula

The “oracle” Unix user should be able to display the b-console and read the corresponding configuration file bconsole.conf, which is not default configuration. You can copy the binary and configuration file to a folder /opt/bacula/oracle using the following Unix commands:

Important: You may need a copy of the binary b-console after each Bacula Enterprise update.

Executing parallel tasks when backing up an Oracle database

To run an Oracle backup or restore using multiple channels, you need to ensure that all required Oracle DB backup plugin resources are correctly configured using the Maximum Concurrent Jobs command to allow parallel tasks to run.

• Director: Director (ex: 100)
• Director: Client (ex: 10)
• Director: Job (ex: 10)
• Director: Storage (ex: 10)
• Storage: Storage (ex: 100)
• Storage: Device (ex: 10 or 10 devices grouped into a Virtual Changer)
• Client: FileDaemon (ex: 10)

To enable backup and restore tasks to run concurrently on the same Director Storage resource, the configuration must use a Virtual Changer drive. For specific configuration information, see technical documentation Disk Backup.

Media restrictions

Oracle requires that Bacula Enterprise Media Manager not merge data streams from two parallel API sessions on the same serial device. This means that if you are using a tape drive to back up an Oracle database, you must use a different tape drive for each parallel backup task. This limitation does not apply to disk drives. This limitation requires a particularly long recovery.

Configuring Bacula SBT

libobk can be configured using a file /opt/bacula/oracle/sbt.conf or / opt/bacula/etc/sbt.conf or using the command RMAN SEND. Table 2 shows the descriptors used:

Table 2. SBT libobk configuration

The minimum parameters that must be specified in the configuration file are client, task and b-console. Please note that double quotes must be used if the element being configured contains spaces (eg b-console).

These settings can be overwritten using the RMAN SEND command.

The SEND command is limited to 512 bytes, so multiple SEND commands can be used to specify all the parameters. It would be better to avoid long paths when using the SBT interface.

FileSet Configuration

The Oracle SBT database backup plugin (oracle-sbt) accepts parameters in the Job FileSet, as described in Table 3.

Table 3. Oracle SBT plugin parameters

Testing the sbt.conf configuration

To test the Bacula Enterprise Oracle SBT plugin configuration, a root user can use the following commands:

If a connection error occurs, a message will appear. Until you configure your connection settings correctly, there is no point in running an Oracle RMAN backup.

Bacula SBT Internal Catalog

libobk file Bacula Enterprise software uses a local directory to store information about all files. This information may be out of date. Therefore, you can use the update=force parameter in the sbt.conf file or the SEND command to force a search for the Bacula directory.

The default directory is stored in / opt/bacula/oracle/bacula-sbt.cat and can be part of a regular system backup.

Ability to save Oracle RMAN backup

When using the RMAN SBT Bacula Enterprise plugin, the Oracle backup saving capability set by the RMAN utility must match the Bacula volume or in-memory job persistence. When RMAN sends commands to delete backup files, Bacula will not attempt to clean up or delete anything.

Examples of Oracle backups

The following example describes how to run 3 parallel Bacula backup jobs simultaneously. In this case, the RMAN utility will send data to them using the so-called round-robin algorithm. If the RMAN utility is unable to communicate with Bacula on one or more channels, RMAN will automatically send data to an available channel. This means that if your storage or centralized director is busy (limited by the number of devices or the settings for the maximum number of parallel tasks), RMAN will find a way out automatically.

In this example, RMAN uses 3 Bacula tasks to recover 3 files.

RMAN Mode Configuration

This section of the user manual describes the procedure for configuring the RMAN utility to work correctly with that part of the Oracle database backup plugin that does not use the SBT interface.

The current version of the Oracle database backup plugin only supports databases launched from active mode ARCHIVELOG.

ARCHIVELOG configuration in Oracle

To use the Oracle backup creation mode with RMAN, the database must be launched in ARCHIVELOG mode. To check how your database is configured, you can use the following SQL command.

To enable archiving mode for a database, you can use the ALTER DATABASE ARCHIVELOG command in the SYSDBA state.

• Stop the database using SHUTDOWN commands
• Create a database backup
• Edit the init file .ora to configure the archived log location
• Start the database without opening it using the STARTUP MOUNT command
• Change the archiving mode using the ALTER DATABASE ARCHIVELOG command; and open it using the ALTER DATABASE OPEN command;
• Stop the database using the SHUTDOWN IMMEDIATE command
• Create a database backup again, as changing ARCHIVELOG will update the control files and render old backups unusable. The Bacula Enterprise plugin for Oracle will create an RMAN backup placed in a subfolder in the location where the archived log file is located, specified in the init file .ora.

Optimizing Oracle Incremental Backup

RMAN's change tracking feature for creating incremental Oracle backups improves the efficiency of such backups by recording changed blocks in each data file to a change tracking file. When change tracking is enabled, RMAN uses the change tracking file to identify changed blocks to create incremental backups. This eliminates the need to scan every block in the data file.

After activating the change tracking feature, in the case of the first full backup, the system will still have to scan all data files, since the change tracking file does not yet reflect the states of all blocks. Any subsequent incremental backup using this full backup as the parent, will use the change tracking file.

The following SQL command, run as sysdba, enables the change tracking feature and uses the location “/path/to/file” as the archived log location. (Please note that the file must be in a valid folder that the Oracle user can write to).

RMAN backup ability

When using RMAN mode with the Bacula Enterprise plugin for Oracle, each Bacula task will run RMAN to create a set of backups. We recommend configuring RMAN to delete old files after a certain amount of time. Even though this operation can be performed immediately after the backup is completed, we recommend storing the data on disk longer so that there are no difficulties with the ability to restore Oracle to checkpoints. The following command will help you set the Oracle file retention period to 7 days. This should be enough time provided you back up Oracle at least once every 7 days.

For more information, see the RMAN manual.

docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#i1019318

Configuring the Oracle Plugin for RMAN

If you use RMAN's PITR recovery feature, the Bacula plugin for Oracle will require Accurate mode to be activated. You must enable Accurate mode on the task resource. Please note that in conjunction with the plugin, the Accurate function is used to ensure that all new files are saved by the Bacula plugin but are not marked as deleted as they are likely to be useful again.

In RMAN mode, the plugin for Oracle also allows the use of additional parameters, specified via command line plugin. See table below:

Table 4. Plugin parameters for Oracle in RMAN mode

Then, using where=/ or where= the plugin will load this SQL file into your database. If some roles already exist, an error message will appear in the job log. You can also restore the users.sql file to a local directory, edit it, and load it using sqlplus to restore any selected portion of the file.

Restoring one Oracle database. To restore a single schema using the Bacula Enterprise Plugin for Oracle, you need to select a directory schema during the restore command, the selection must contain a data file (data.dmp) and a schema creation script (user.sql).

Rice. 3 Database contents with dump in BWeb

Once the DB directory is selected, you can use the where parameter to restore the schema to new scheme with a different name. To create a new schema name, you need to equate the where parameter to a single word that contains the characters A..Z, 0-9, and _. The Bacula plugin will then create the specified schema and restore the data to it.

We recommend that you always use capital letters. The Bacula Enterprise plugin for Oracle will recreate the new schema using the name you specified in the where= parameter. If you use uppercase and lowercase letters in the name, there may be a situation where you have to enclose the schema name in quotation marks to access it.

After recovery, you may need to reset the password of the schema you just created using the same settings as the original schema. To do this, run:

If you set the parameter to never, the Bacula plugin will check the list of schemas and abort the task if the current schema being restored already exists.

If the where parameter is a directory (containing /), the Bacula plugin will restore all files to that directory. This way you can use the imp directory and restore only triggers, tables, indexes, etc.

Recovering a single Oracle table. To restore a single object, such as a table, from a dump you created, you must first restore the dump file to a local directory. Then use the imp tool to import the desired object. For more information, see the documentation on importing objects into Oracle.

Restoring Oracle dump files to a directory. To restore SQL dumps to a directory, you can assign the where parameter to any valid directory.

The Oracle restore process with Bacula plugin will create the following folders when restoring the SYS schema in Oracle SID XE, and will restore the selected files into it.

Restoring the entire Oracle database. To restore all databases and database configurations, simply restore all files located in /@ORACLE/ , use replace=always and where=/.

Limitations of Oracle Backup and Restore

Default plugins are not compatible with Copy/Migration/VirtualFull tasks.

Read, What tools can you use to create a backup or restore a lost Oracle Database?. Let's consider both tools built into the database and third-party applications. Oracle Database stores all files of the created database in data files. Often, to restore data from a specific database, it is enough to restore its data files and import them into Oracle Database.

Oracle Database Structure

During operation, an Oracle Database instance uses several groups of files that should be archived for later recovery. This:

So, to save, archive or backup an Oracle Database, copies of exactly the specified groups of files should be created, and this is:

• *.DBF– data files, table spaces and database control files. Located:
  C:\oraclexe\app\oracle\oradata\XE
• *.ora– database configuration files and password files.
  Configuration files:
  C:\oraclexe\app\oracle\product\11.2.0\server\dbs
  Password files (PW…ora):
  C:\oraclexe\app\oracle\product\11.2.0\server\database
• *.LOG– transaction log files:
  C:\oraclexe\app\oracle\fast_recovery_area\XE\ONLINELOG

where, XE is the name of the database in our case.

Oracle Database Backup

There are two ways to back up an Oracle Database:

• Archiving means operating system.
• Using the built-in tools of Oracle Application Express – Import / Export.

Archiving using the operating system

Archiving using the operating system means “manual” copying of all working database files, such as:

• Tablespace files.
• Control files.
• Transaction log files.
• Configuration files.

In this case, the archiving process consists of simply copying control files, tablespace files, configuration, archived transaction logs to a backup directory or to a backup server. Archiving is performed when the database instance is stopped, and users are unable to work with it.

To restore a database damaged during a crash, it must be stopped and the backup copies of working files and transaction logs must be rewritten to their original location.

Backup and recovery using Export / Import tools

Archiving and restoring an Oracle Database can be done using standard Export and Import mechanisms in Oracle. To increase the reliability of data safety, it is necessary to periodically, depending on the intensity of work with the database, perform a full export. If changes to data are made quite intensively, it is necessary to export once a week.

To do this:

Importing a file created earlier in the archive is carried out in the same way:

Open Oracle Application Express and select the Application Builder / Import menu

Select the file to import and specify its type



• Install the imported database

  
  

Recovering a Lost Oracle Database

If the Oracle Database is deleted or lost for some reason, it can be restored by restoring files using Hetman Partition Recovery and restore them using the method described in section "Archiving using the operating system".

To do this:




For example, restoring database files, the process of restoring *.DBF files is described. But keep in mind that to restore all data to a working database, you also need to restore the corresponding *.ORA and *.LOG files.

Backing up and restoring a database using Oracle Recovery Manager (RMAN)

Oracle Recovery Manager (RMAN) is another tool for creating a backup copy of the Oracle Database. It differs from other tools in that it creates full copy the entire database, not just the data from it. And also, importantly, Oracle Recovery Manager combines the functionality of the SQL Command Line while simultaneously freeing the user from complete dependence on its commands. This tool is installed on the computer simultaneously and together with Oracle installation Database.

To create a database backup using Oracle Recovery Manager (RMAN):




To restore a database from a database backup using Oracle Recovery Manager (RMAN):




By the way, in case of loss or deletion of the Oracle Database backup file, *.BKP The backup file can also be restored using Hetman Partition Recovery , then restore in the database using the method described above using Oracle Recovery Manager (RMAN).

Key Features:

Disk Image, Backup to NAS, Backup Open Files(VSS), Perpetual License
Starting from € 29

FREE BACKUP SOFTWARE FOR SERVER AND WORKSTATIONS

BACKUP FREE AND PROFESSIONAL SOLUTIONS

Iperius is a complete Windows utility for data backup. You can use the Freeware version (also for Windows Server) to back up files to NAS, external disks, RDX drives, etc. without any time limitation - or choose an enterprise version, with plenty of backup functions and advanced features: copy of open files (VSS), Drive Image for disaster recovery, backup of ESXi and Hyper-V virtual machines, SQL Server and MySQL database backup , Exchange Server backup, backup to LTO Tape, backup to Cloud (Google Drive, Amazon S3, etc.), backup to FTP/SFTP. Starting from Iperius Free, a trial of the Full version can be activated to test all the features of the software.

Iperius Console

KEEP UNDER CONTROL ALL THE BACKUPS IN A SHOT

Iperius Console is the advanced tool for centralized management and monitoring of your computers and backup. Using either the dedicated desktop application or just the web portal, you can view the results of your backup operations, examine the details of any errors, set and customize the backup schedulings and also run backup jobs remotely. The console integrates perfectly with all the products of Iperius Suite, allowing also to remotely update Iperius Backup to the latest version. The large amount of information provided keeps users updated about the status of every PC and Server where Iperius is installed, making Iperius Console an extremely useful IT Monitoring tool, both for your customers and your company.