Search

Top 60 Oracle Blogs

Recent comments

cloning

EM 12c Snap Clone



Oracle OEM 12c introduces a new feature that enables the creation of Oracle database thin clones by leveraging file system snapshot technologies from either Oracle ZFS Storage Appliance or Netapp.  The OEM adds a graphic interface to the process of making database thin clones. The feature that enables database thin cloning in OEM is called Snap Clone and is part of OEM’s Cloud Control Self Service for data cloning. Snap Clone is available via the feature Database as a Service (DBaaS). Snap clone leverages the copy on write technologies available in some storage systems for database cloning.  Support is initially available for NAS storage and specifically on Oralce ZFS Storage Appliacen and NetApp Storage.

VirtualBox Cloning: A minor warning…

The cloning feature in VirtualBox was a welcome addition, but there are a couple of fringe issues to be aware of:

  • If you use the cloning feature to clone a VM that has shared disks (like in a VM RAC setup), the shared disks are also cloned, so you end up with a new VM that is not accessing the original shared disks, but has a new set. I’ve put a note about this in my VirtualBox RAC articles and suggested you still use the old method of cloning the virtual hard disk manually. I guess for most people this is not a big deal.
  • The virtual disks of a clone get placed in the default location. Once again, not a big deal unless you try to spread your virtual disks onto different spindles to get better performance.

Like I said, these are very edge-case issues and not a reason for most people to avoid the cloning feature.

Cheers

Tim…




In Praise of Clones

I’m all alone, so are we all We’re all clones All are one and one are all ~ Alice Cooper Two separate discussions, one at work and one around the virtual OakTable , have made me aware that maybe not as many Oracle professionals as I imagined are aware that Oracle provides a facility to [...]