Make the snapshot read/write by copying it into a LUN and attach it to the same host.
Take the snapshot of the disks that belong to the source database either through Pure GUI or CLI/Rest based APIs.If you are performing this cloning on a regular basis, check the next section. These steps are done the very first time when a source database on ASM is cloned and mounted on the same server. Select the 'DATA' disk group, then clicking the 'Next' button. Enter the ASM password if prompted, then click the 'OK' button. The following cloning process assumes the DM devices are named using the alias clause in /etc/nf file.įollowing are the high-level steps to clone an Oracle database on ASM using Pure FlashArray snapshot functionality onto the same server. Go back to the DBCA and create a custom database in the normal way, selecting the 'Automatic Storage Management (ASM)' storage option.As a precautionary measure, take the snapshots of the source volumes. Get acclimated to the cloning process by testing them in a non-production environment before attempting them in production. This can be accomplished by using the renamedg command that allows changing the diskgroup information at the header level on the cloned lun.ĭisclaimer: This post is purely for educational purposes. Similar to duplicate UUID error we would encounter in a cloned LVM volumes on the same host.įYI, Oracle generally doesn’t support mounting the copy of the ASM lun on to the same server as it is error-prone and admins might accidentally rename or destroy the wrong diskgroup. The problem is, cloning an ASM lun and mounting it onto the same host would result in two luns with same ASM header information that points to the same disk group name and the disk name.
0 kommentar(er)
