Clone Oracle database backups using UNIX commands
PDF of this doc site
- SnapCenter Server installation
Protect Microsoft SQL Server databases
- SnapCenter Plug-in for Microsoft SQL Server
- Prepare to install the SnapCenter Plug-in for Microsoft SQL Server
Protect SAP HANA databases
- SnapCenter Plug-in for SAP HANA Databases
- Prepare to install the SnapCenter Plug-in for SAP HANA Database
- Back up SAP HANA resources
- Protect Oracle databases
- Protect Windows file systems
- Protect Microsoft Exchange Server databases
Protect Custom applications
- Prepare to install SnapCenter Custom Plug-ins
The clone workflow includes planning, performing the clone operation, and monitoring the operation.
About this task
You should execute the following commands to create the Oracle database clone specification file and initiate the clone operation.
The information regarding the parameters that can be used with the command and their descriptions can be obtained by running Get-Help command_name. Alternatively, you can also refer to the SnapCenter Software Command Reference Guide.
Create an Oracle database clone specification from a specified backup: New-SmOracleCloneSpecification
If secondary data protection policy is unified mirror-vault, then specify only -IncludeSecondaryDetails. You do not have to specify -SecondaryStorageType.
This command automatically creates an Oracle database clone specification file for the specified source database and its backup. You must also provide a clone database SID so that the specification file created has the automatically generated values for the clone database which you will be creating.
The clone specification file is created at /var/opt/snapcenter/sco/clone_specs.
Initiate a clone operation from a clone resource group or an existing backup: New-SmClone
This command initiates a clone operation. You must also provide an Oracle clone specification file path for the clone operation. You can also specify the recovery options, host where the clone operation to be performed, prescripts, postscripts, and other details.
By default, the archive log destination file for the clone database is automatically populated at $ORACLE_HOME/CLONE_SIDs.