Oracle ZFS Storage Appliance: SMU Cloning of a Standby Database

Asset ID:	1-71-2216826.1
Update Date:	2018-05-11
Keywords:

Solution Type Technical Instruction Sure

Solution 2216826.1 : Oracle ZFS Storage Appliance: SMU Cloning of a Standby Database

Related Items


Sun ZFS Storage 7420
 Oracle ZFS Storage ZS5-2
 Integrated Software for ZFS 7xx0 Arrays
 Oracle ZFS Storage ZS3-2
 Oracle ZFS Storage ZS4-4
 Oracle ZFS Storage ZS5-4
 Sun ZFS Storage 7120
 Oracle ZFS Storage ZS3-4
 Sun ZFS Storage 7320
 Oracle ZFS Storage Appliance Racked System ZS4-4
 Oracle ZFS Storage ZS3-BA

Related Categories


PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS

In this Document

Goal

Solution

References

Applies to:

Sun ZFS Storage 7120 - Version All Versions and later
Sun ZFS Storage 7420 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
Integrated Software for ZFS 7xx0 Arrays - Version All Versions and later
Oracle ZFS Storage ZS5-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Goal

How to create a snap clone from a snap backup.

Solution

Here is what you need to be able to create a snap clone from a snap backup.

Clones are exact copies of the origin/source; use the same memory model and memory sizes.
Clone shares are placed in the same project as original shares.
Clone LUNs are placed in the same initiator and target groups as the origin shares.
The target database's host oracle user must have the same uid and gid as the source database's host Oracle user.
The clone will use the same memory model as the original database.
If dNFS is desired for the clone database, it must be configured in the target Oracle home before the clone operation is performed.

From page 111 (119 of 136) of the Snap Management Utility (SMU) manual: https://docs.oracle.com/cd/E39520_01/pdf/E39313.pdf

Check for relevancy - 11-May-2018

References

https://docs.oracle.com/cd/E39520_01/pdf/E39313.pdf

Attachments

This solution has no attachment