EMC Backup and Recovery for Oracle 11g OLTP Enabled by EMC ...

Chapter 3: Storage Design
EMC SnapView SnapView clones were used to create complete copies of the database. A clone
copy was used to offload the backup operations from the production nodes to the
proxy node. A second clone copy was used as a gold copy. The following graphic
shows an example of a clone LUN's relationship to the source LUN, in this example
the clone information for one of the LUNs is contained in the ASM datagroup.
SnapView clones create a full bit-for-bit copy of the respective source LUN. A clone
was created for each of the LUNs contained within the ASM diskgroups, and all
clones were then simultaneously split from their respective sources to provide a
point-in-time content consistent replica set.
The command naviseccli – h arrayIP snapview –listclonegroup –data1 was used
to display information on this clone group. Each of the ASM diskgroup LUNs was
added to a clone group becoming the clone source device. Target LUN clones were
then added to the clone group. Each clone group is assigned a unique ID and each
clone gets a unique clone ID within the group. The first clone added has a clone ID
of 010000000000000, and for each subsequent clone added the clone ID
increments. The clone ID is then used to specify which clone is selected each time a
cloning operation is performed.
As shown above there are two clones assigned to the clone group. Clone ID
01000000000000000 was used as the gold copy and clone ID 0200000000000000
was used for backups. (The Navisphere Manager GUI also shows this information.)
When the clones are synchronized they can be split (fractured) from the source LUN
to provide an independent point-in-time copy of the database.
EMC Backup and Recovery for Oracle 11g OLTP Enabled by EMC CLARiiON, EMC Data Domain, EMC NetWorker,
and Oracle Recovery Manager using NFS Proven Solution Guide
21