ORACLE RMAN DATABASE DUPLICATION PDF
Protected Databases. Cloud @ Customer. File syste m. RMAN: Built-in backup & recovery engine for the Oracle database which provides performant, efficient. PDF · Mobi · ePub In active database duplication, RMAN connects as TARGET to the source database instance and as RMAN connects to the auxiliary instance of the duplicate database on the destination host. The DUPLICATE entry in Oracle Database Backup and Recovery Reference for a complete list of which. Database Cloning Procedure using Oracle RMAN and the Sun ZFS Storage. Appliance. . appliance are then used to duplicate or clone the Oracle RMAN backup. The cloning procedure explained in pdf. The solution described in.
|Language:||English, Spanish, Hindi|
|Genre:||Science & Research|
|ePub File Size:||20.58 MB|
|PDF File Size:||16.12 MB|
|Distribution:||Free* [*Regsitration Required]|
The focus of this book is database duplication using RMAN. main purpose is the backup and recovery of Oracle databases, there are other features that. Oracle 11g has introduced active database duplication, we can create a duplicate of the .. LOSS OF FULL DATABASE & RECOVERY - RMAN BACKUP. pdf. Oracle RMAN Database Duplication – PDF Books. Oracle Oracle Database Workspace Manager Developers Guide · Oracle Database JDBC Developers.
In Oracle Database 11g, you can directly duplicate a database over the network without having to back up and provide thesource database files. This direct database duplication is called active databaseduplication or network-aware database duplication. RMAN simply copies the target database files to the destination server it can be the same server over a network connection. Until the Oracle Database 11g release, duplicating a destination database with RMAN meantyou had to have all of the following:. When you use the network-enabled active database duplication, the process of duplicating is considerably simpler. The database files are directly copied over the networkconnection from the source database to the new destination database. RMAN automatically selects completed, so it can recover the datafiles to a consistent point in time.
That can be done by either copying them to the matching location on the destination server, or placing them on a shared drive. If you are copying the files, you may want to use the following type of commands. With the duplicate database started we can now connect to it from RMAN. We can then duplicate the database using one of the following commands.
Oracle RMAN Database Duplication
The time it takes to complete varies depending on the size of the database and the specification of the server. Once the process is finished RMAN produces a completion message and you have your duplicate instance. Oracle 11g introduced the ability to create duplicate databases directly without the need for a backup.
This is known as active database duplication. The process is similar to the backup-based duplication, with a few exceptions. The passwords in the password files must match for both servers, so remember to set the correct password when creating the password file on the destination server.
Both the source and destination database servers require a "tnsnames. In this case I added the following to each server. The destination server still requires the source entry shown in the previous section.
See "Step 5: Your business requirements and the database environment determine which duplication technique is best for your situation. Consider the following questions:.
Some prerequisites are common to all duplication techniques, such as the following:. The source and duplicate databases must be on the same platform. Other prerequisites are specific and depend on the duplication technique. For example, active duplication requires that the source and auxiliary instances use the same password as the source database, whereas backup-based duplication without connections to the target database and recovery catalog requires only that all backups and database copies reside in a single location.
The principal advantage of active database duplication is that it does not require source database backups. Active duplication copies mounted or online database files over a network to the auxiliary instance.
One disadvantage of this technique is the negative performance effect on the network. Another disadvantage is that the source database is running processes required to transfer the files to the auxiliary host, thereby affecting the source database and production workload. If the source database backups already exist, and if the effect on the network is unacceptable, then backup-based duplication may be a better option.
You can copy backups to temporary storage and transfer them manually to the destination host. If duplication is made with a connection to the target or the recovery catalog, then the backup files on the destination host must have the same file specification as they had on the source host. Otherwise, this is not a requirement. This technique is advantageous where network connections from the auxiliary host to the source database are restricted or prone to intermittent disruptions. The disk space on the destination host can be an issue when you perform duplication using disk backups.
For example, if the source database is 1 terabyte TB , and if you duplicate the database from disk backups without using shared disk or network file system NFS , then you must have at least 2 terabytes TB of space available on the destination host.
In some environments, manual transfer of backups is necessary because NFS performance is a bottleneck. Performance of active database duplication is probably slower on a wide area network WAN than a local area network LAN. If the performance degradation on a WAN is unacceptable, then backup-based duplication may be the only viable option. If you must duplicate the database during a period of high user activity, then the loss of network throughput caused by active duplication may be a problem, making backup-based duplication a better choice.
Also, in active database duplication the RMAN channels required for copying files to the auxiliary host can affect performance. When duplicating a database, RMAN generates names for the duplicate control files, data files, temp files, and online redo log files. Therefore, you must decide on a naming strategy for these files.
Oracle recommends the simplest duplication strategy, which is to configure the duplicate database to use the same names as the source database. Using the same names means that your environment meets the following requirements:.
If the source database uses ASM disk groups, then the duplicate database must use ASM disk groups with the same names. Although the directories are the same on the source and destination hosts, Oracle Database chooses the relative names for the duplicate files. If the names of the database files in the source database contain a path, then this path name must be the same in the duplicate database. When you configure your environment as suggested, no additional configuration is required to name the duplicate files.
When duplicating with a target and recovery catalog or just a target connection, RMAN uses metadata in the RMAN repository to locate backups and archived redo log files needed for duplication.
If RMAN is not connected to a catalog, as may be the case when performing backup-based duplication with a target connection, then RMAN obtains metadata from the control file.
Unless you are duplicating without a connection to the target and to the recovery catalog, the names of the backups must be available with the same names recorded in the RMAN repository. Ensure that auxiliary channels on the destination host can access all data file backups and archived redo log files required to restore and recover the duplicate database to the desired point in time. If not, duplication fails. The archived redo log files can be available either as image copies or backup sets. Make the tapes with the backups accessible to the destination host.
Typically, you do one of the following:. When you make disk backups accessible to the auxiliary instance, your strategy depends on whether or not you duplicate the database while connected to the target or recovery catalog.
In the latter case, you do not need to preserve the name or the original path of the backup or copy. It is not required that all of the backups be from the same point in time, or that they all be backup sets, or all image copies.
Data file backups can be supplied as either image copies or backup sets. Archived logs can be supplied either in their normal format or as backup sets of archived logs. When you use backups from different points in time, the backup location must contain archived logs covering the time from the start of the oldest backup until the desired recovery point. If the backup location contains backup files from multiple databases, then the DATABASE clause must specify the name of the database that is to be duplicated.
The source database's Fast Recovery Area is particularly well suited for use as a backup location because it almost always contains all of the files needed for the duplication. To use a Fast Recovery Area as a backup location, you can either remotely access it from the destination system, or copy its contents to the destination system.
This scenario is the simplest and Oracle recommends it. In this case, you can make disk backups accessible to the destination host in either of these ways:. Manually transfer backups from the source host to an identical path in the destination host. Use NFS or shared disks and ensure that the same path is accessible in the destination host. In this case you cannot use the same directory name on the destination host as you use on the source host.
You have the following options:. You can use shared disk to make backups available. This section explains the shared disk technique. You cannot use shared disk to make backups available. Assume that you have two hosts, srchost and dsthost , and access to NFS or shared disk. The database on srchost is called srcdb. Mount the directory created in the previous step on the other host, ensuring that the directory and the mount point names are the same.
Make the backups available in the new location on the destination host. You can use either of the following techniques:. In this case, RMAN automatically catalogs the backups in the new location. Use an operating system utility to transfer the backups to the new location. When a database must be accessed from another host, you must set up a password file and Oracle Net connectivity.
Be aware of the potential security consequences of this type of setup. Follow the instructions in Oracle Database Administrator's Guide to create a password file.
The types of file names allowed for password files and the location of the password file are both platform specific and operating system-specific. Oracle Data Guard Concepts and Administration to create a password file manually. Follow the instructions in Oracle Database Net Services Administrator's Guide to configure a client for connection to a database and add static service information for the listener. You have the following options for creating a password file for the auxiliary instance on the destination host:.
You may want to create the password file with a single password so that you can start the auxiliary instance and enable the source database to connect to it.
In this case, RMAN copies the source database password file to the destination host and overwrites any existing password file for the auxiliary instance. This technique is useful if the source database password file has multiple passwords that you want to make available on the duplicate database.
Duplicate a Database Using RMAN in Oracle Database 11g Release 2
The location and content of the initialization parameter file depend on your choice in "Step 2: Choosing a Strategy for Naming Duplicate Files".
This section makes the following assumptions:. You choose the recommended technique of using the same naming strategy for the source and destination hosts. You create a text-based initialization parameter file for the auxiliary instance. SPFILE technique is easiest because during duplication RMAN automatically copies the server parameter file from the source database to the auxiliary instance or restores it from backup. If a server parameter file exists on the auxiliary instance, then RMAN overwrites it.
To create an initialization parameter file and start the auxiliary instance: If you are performing active database duplication, then ensure that the following additional requirements are met:.
In this task, you must start the RMAN client and connect to the database instances required by the duplication technique chosen in "Step 1: Choosing a Duplication Technique".
The RMAN client can be located on any host so long as it can connect to the necessary databases over the network. A recovery catalog connection is optional. A recovery catalog is optional. In the following example of active database duplication, a connection is established to three database instances, all using net service names:.
The channel on the auxiliary instance, not the source database instance, restores RMAN backups in backup-based duplication. The channel configuration depends on your duplication technique. However, you may want to increase the parallelism setting of your source database disk channels so that RMAN copies files over the network in parallel. RMAN can use the same channel configurations on the source database for duplication on the destination host. The channel type DISK or sbt of the auxiliary channel must match the backup media.
In general, the more channels you allocate for disk backups, the faster the duplication. For tape backups, limit the number of channels to the number of devices available.
When you perform duplication without a target connection and without a recovery catalog, only disk channels can be used. If no user-allocated channels are used, then only one channel initially restores the control file.
After the control file is mounted, the number of allocated channels depends on the configuration in the restored control file. This section describes the most basic procedure to duplicate a database. You are duplicating the database to a remote host. The duplicate database files use the same names as the source database files. You are duplicating the entire database. RMAN automatically copies the server parameter file to the destination host, starts the auxiliary instance with the server parameter file, copies all necessary database files and archived redo logs over the network to the destination host, and recovers the database.
Example creates a duplicate of the source database prod as it appeared in in a previous database incarnation.
By not specifying this clause, you instruct RMAN to perform backup-based duplication. The DBID is specified because the source database name prod is not unique in the recovery catalog. Assume a variation in which you want to restore an archival backup , which is all-inclusive in the sense that every file needed to restore and recover the database is included. In this way, you avoid interfering with the source database.
Example recovers the duplicate database to 1 week ago to view the data in the source database as it appeared then. All backup and copies necessary for duplication until November 11 of at 2: The database name is not specified.
Omitting this clause instructs RMAN to perform backup-based duplication. This applies to all forms of duplication, whether they are backup-based with or without a target connection or active database duplication.
Displays a message similar to the following for each data file that it does not need to duplicate again:. Restores only the missing or incomplete data files, thereby avoiding re-copying and restoring all the data files.
ORACLE-BASE - Duplicate a Database Using RMAN in Oracle Database 11g Release 2
Skip Headers. This chapter contains the following topics: Purpose of Database Duplication A duplicate database is useful for a variety of purposes, most of which involve testing. You can perform the following tasks in a duplicate database: Test backup and recovery procedures Test an upgrade to a new release of Oracle Database Test the effect of applications on database performance Create a standby database Generate reports For example, you can duplicate the production database on host1 to host2 , and then use the duplicate database on host2 to practice restoring and recovering this database while the production database on host1 operates as usual.
See Also: Basic Concepts of Database Duplication The source host is the computer that hosts the source database. RMAN can perform backup-based duplication with or without either of the following connections: Target Recovery catalog A connection to both is required for active database duplication.
Figure shows the decision tree for the two duplication techniques. Figure Duplication Techniques. Figure Active Database Duplication. This technique of duplication uses one of the following mutually exclusive subtechniques:
- DESIGNING THE USER INTERFACE SHNEIDERMAN PDF
- FJALOR GJERMANISHT SHQIP PDF
- ORACLE 10G/11G DATA AND DATABASE MANAGEMENT UTILITIES PDF
- GERMAN LANGUAGE LESSONS PDF
- DEFINITIVE GUIDE TO SOA ORACLE SERVICE BUS PDF
- HIGH PERFORMANCE WEBSITES STEVE SOUDERS PDF
- MOBILE DATABASE SYSTEMS VIJAY KUMAR BOOK EBOOK
- BASIC GERMAN A GRAMMAR AND WORKBOOK PDF
- DOA TAHLIL LENGKAP PDF
- CALCULUS OF VARIATIONS GELFAND PDF
- SPOKEN ENGLISH BANGLA EBOOK
- CUTTING FOR STONE EBOOK
- RABBIT FARMING PDF
- COMPUTER AWARENESS FOR BANK PO PDF
- APOSTILA DETRAN PDF