Clone an Oracle database backup
You can use SnapCenter to clone an Oracle database using the backup of the database.
Before you begin
If you have installed the plug-in as a non-root user, you should manually assign the execute permissions to the prescript and postscript directories.
About this task
The cloning operation creates a copy of the database data files, and creates new online redo log files and control files. The database can be optionally recovered to a specified time, based on the specified recovery options.
|Cloning fails if you try to clone a backup that was created on a Linux host to an AIX host or vice-versa.|
SnapCenter creates a stand-alone database when cloned from an Oracle RAC database backup. SnapCenter supports creating clone from the backup of a Data Guard standby and Active Data Guard standby databases.
During cloning, SnapCenter mounts the optimal number of log backups based on SCN or dat and time for recovery operations. After recovery, the log backup is unmounted. All such clones are mounted under /var/opt/snapcenter/scu/clones/. If you are using ASM over NFS, you should add /var/opt/snapcenter/scu/clones/*/* to the existing path defined in the asm_diskstring parameter.
While cloning a backup of an ASM database in a SAN environment, udev rules for the cloned host devices are created at /etc/udev/rules.d/999-scu-netapp.rules. These udev rules associated with the cloned host devices are deleted when you delete the clone.
|In a Flex ASM setup, you cannot perform clone operation on Leaf nodes if the cardinality is less than the number nodes in the RAC cluster.|
In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.
In the Resources page, select either Database or Resource Group from the View list.
Select the database either from the database details view or from the resource group details view.
The database topology page is displayed.
From the Manage Copies view, select the backups either from Local copies (primary), Mirror copies (secondary), or Vault copies (secondary).
Select the Data backup from the table, and then click .
In the Name page, perform one of the following actions:
If you want to… Steps…
Clone a database (CDB or non CDB)
Specify the SID of the clone.
The clone SID is not available by default, and the maximum length of the SID is 8 characters.
You should ensure that no database with the same SID exists on the host where the clone will be created.
Clone a pluggable database (PDB)
Select PDB Clone.
Specify the PDB that you want to clone.
Specify the name of cloned PDB. For the detailed steps to clone a PDB, see Clone a pluggable database.
When you select a mirrored or vault data:
if there are no log backup at mirror or vault, nothing is selected and the locators are empty.
if log backups exist in mirror or vault, the latest log backup is selected and corresponding locator is displayed.
If the selected log backup exists in both mirror and vault location, both the locators are displayed.
In the Locations page, perform the following actions:
For this field… Do this…
By default, the source database host is populated.
If you want to create the clone on an alternate host, select the host having the same version of Oracle and OS as that of the source database host.
By default, the datafile location is populated.
The SnapCenter default naming convention for SAN or NFS file systems is FileSystemNameofsourcedatabase_CLONESID.
The SnapCenter default naming convention for ASM disk groups is SC_HASHCODEofDISKGROUP_CLONESID. The HASHCODEofDISKGROUP is an automatically generated number (2 to 10 digits) that is unique for each ASM disk group.
If you are customizing the ASM disk group name, ensure that the name length adheres to the maximum length supported by Oracle.
If you want to specify a different path, you must enter the datafile mount points or ASM disk group names for clone database. When you customize the datafile path, you must also change the control file and redo log file ASM disk group names or file system either to the same name used for data files or to an existing ASM disk groups or file system.
By default, the control file path is populated.
The control files are placed in the same ASM disk group or file system as that of the data files. If you want to override the control file path, you can provide a different control file path.
The file system or the ASM disk group should exist on the host.
By default, the number of control files will be same as that of the source database. You can modify the number of control files but a minimum of one control file is required to clone the database.
You can customize the control file path to a different file system (existing) than that of the source database.
By default, the redo log file group, path, and their sizes are populated.
The redo logs are placed in the same ASM disk group or file system as that of the data files of the cloned database. If you want to override the redo log file path, you can customize the redo log file path to a different file system than that of the source database..
The new file system or the ASM disk group should exist on the host.
By default, the number of redo log groups, redo log files, and their sizes will be same as that of the source database. You can modify the following parameters:
Number of redo log groups
A minimum of two redo log groups are required to clone the database.
Redo log files in each group and their path
You can customize the redo log file path to a different file system (existing) than that of the source database.
A minimum of one redo log file is required in the redo log group to clone the database.
Sizes of the redo log file
On the Credentials page, perform the following actions:
For this field… Do this…
Credential name for sys user
Select the Credential to be used for defining the sys user password of the clone database.
If SQLNET.AUTHENTICATION_SERVICES is set to NONE in sqlnet.ora file on the target host, you should not select None as the Credential in the SnapCenter GUI.
ASM Instance Credential name
Select None if OS authentication is enabled for connecting to the ASM instance on the clone host.
Otherwise, select the Oracle ASM credential configured with either “sys” user or an user having “sysasm” privilege applicable to the clone host.
The Oracle home, user name, and group details are automatically populated from the source database. You can change the values based on the Oracle environment of the host where the clone will be created.
In the PreOps page, perform the following steps:
Enter the path and the arguments of the prescript that you want to run before the clone operation.
You must store the prescript either in /var/opt/snapcenter/spl/scripts or in any folder inside this path. By default, the /var/opt/snapcenter/spl/scripts path is populated. If you have placed the script in any folder inside this path, you need to provide the complete path up to the folder where the script is placed.
SnapCenter allows you to use the predefined environment variables when you execute the prescript and postscript. Learn more
In the Database Parameter settings section, modify the values of prepopulated database parameters that are used to initialize the database.
You can add additional parameters by clicking .
If you are using Oracle Standard Edition and the database is running in Archive log mode or you want restore a database from archive redo log, add the parameters and specify the path.
Fast recovery area (FRA) is not defined in the prepopulated database parameters. You can configure FRA by adding the related parameters. The default value of log_archive_dest_1 is $ORACLE_HOME/clone_sid and the archive logs of the cloned database will be created in this location. If you have deleted the log_archive_dest_1 parameter, the archive log location is determined by Oracle. You can define a new location for archive log by editing log_archive_dest_1 but ensure that the file system or disk group should be existing and made available on the host.
Click Reset to get the default database parameter settings.
In the PostOps page, Recover database and Until Cancel are selected by default to perform recovery of the cloned database.
SnapCenter performs recovery by mounting the latest log backup that have the unbroken sequence of archive logs after the data backup that was selected for cloning. The log and data backup should be on primary storage to perform the clone on primary storage and log and data backup should be on secondary storage to perform the clone on secondary storage.
The Recover database and Until Cancel options are not selected if SnapCenter fails to find the appropriate log backups. You can provide the external archive log location if log backup is not available in Specify external archive log locations. You can specify multiple log locations.
If you want to clone a source database that is configured to support flash recovery area (FRA) and Oracle Managed Files (OMF), the log destination for recovery must also adhere to OMF directory structure.
The PostOps page is not displayed if the source database is a Data Guard standby or an Active Data Guard standby database. For Data Guard standby or an Active Data Guard standby database, SnapCenter does not provide an option to select the type of recovery in the SnapCenter GUI but the database is recovered using Until Cancel recovery type without applying any logs.
Field name Description
SnapCenter performs recovery by mounting the latest log backup having the unbroken sequence of archive logs after that data backup that was selected for cloning. The cloned database is recovered till the missing or corrupt log file.
Date and time
SnapCenter recovers the database up to a specified date and time. The accepted format is mm/dd/yyyy hh:mm:ss.
The time can be specified in 24 hour format.
Until SCN (System Change Number)
SnapCenter recovers the database up to a specified system change number (SCN).
Specify external archive log locations
If the database is running in ARCHIVELOG mode, SnapCenter identifies and mounts optimal number of log backups based on the specified SCN or the selected date and time.
You can also specify the external archive log location.
SnapCenter will not automatically identify and mount the log backups if you have selected Until Cancel.
Create new DBID
By default Create new DBID check box is selected to generate a unique number (DBID) for the cloned database differentiating it from the source database.
Clear the check box if you want to assign the DBID of the source database to the cloned database. In this scenario, if you want to register the cloned database with the external RMAN catalog where the source database is already registered, the operation fails.
Create tempfile for temporary tablespace
Select the check box if you want to create a tempfile for the default temporary tablespace of the cloned database.
If the check box is not selected, the database clone will be created without the tempfile.
Enter sql entries to apply when clone is created
Add the sql entries that you want to apply when the clone is created.
Enter scripts to run after clone operation
Specify the path and the arguments of the postscript that you want to run after the clone operation.
You should store the postscript either in /var/opt/snapcenter/spl/scripts or in any folder inside this path. By default, the /var/opt/snapcenter/spl/scripts path is populated.
If you have placed the script in any folder inside this path, you need to provide the complete path up to the folder where the script is placed.
If the clone operation fails, postscripts will not be executed and cleanup activities will be triggered directly.
In the Notification page, from the Email preference drop-down list, select the scenarios in which you want to send the emails.
You must also specify the sender and receiver email addresses, and the subject of the email. If you want to attach the report of the clone operation performed, select Attach Job Report.
For email notification, you must have specified the SMTP server details using the either the GUI or the PowerShell command Set-SmSmtpServer.
Review the summary, and then click Finish.
While performing recovery as part of clone create operation, even if recovery fails, the clone is created with a warning. You can perform manual recovery on this clone to bring the clone database to consistent state.
Monitor the operation progress by clicking Monitor > Jobs.
After cloning the database you can refresh the resources page to list the cloned database as one of the resource available for backup. The cloned database can be protected like any other database using the standard backup workflow or can be included in a resource group (either newly created or existing). The cloned database can be further cloned (clone of clones).
After cloning, you should never rename the cloned database.
|If you have not performed recovery while cloning, the backing up of the cloned database might fail due to improper recovery and you might have to perform manual recovery. The log backup can also fail if default location which was populated for archive logs is on a non-NetApp storage or if the storage system is not configured with SnapCenter.|
In AIX setup, you can use the lkdev command to lock and the rendev command to rename the disks on which the cloned database resided.
Locking or renaming of devices will not affect the clone deletion operation. For AIX LVM layouts built on SAN devices, renaming of devices will not be supported for the cloned SAN devices.
Find more information