zfs storage pools with EMC Snapview clones
We're currently using Veritas VM and Snapview clones to present multiple copies of our database data to the same host. I've found that Veritas doesn't like multiple copies of the same disk group being imported on a host and found a way around this. My question is: does zfs have this problem? If I switch to zfs for our new system and create a storage pool for each group of data files, (we put the data files with our tables on one filesystem, indexes on another, redo logs another, etc.) can I mount a clone of the indexes storage pool (for example) on the same host as the original?
[595 byte] By [
ifinzena] at [2007-11-27 2:40:03]
# 1
> We're currently using Veritas VM and Snapview clones
> to present multiple copies of our database data to
> the same host. I've found that Veritas doesn't like
> multiple copies of the same disk group being imported
> on a host and found a way around this.
VxVM 5.0 has some tools to redo the ID on the copy. That might make it easier to deal with. Of course that brings up other issues if you ever want to use that copy and roll it back as primary.
(If you don't have 5.0, you can still do it, but it's a lot more fiddley)
> My question
> is: does zfs have this problem? If I switch to zfs
> for our new system and create a storage pool for each
> group of data files, (we put the data files with our
> tables on one filesystem, indexes on another, redo
> logs another, etc.) can I mount a clone of the
> indexes storage pool (for example) on the same host
> as the original?
No. Same issue. The pool/volume group has a (hopefully) unique identifier to find the pieces of the storage. When the identified piece starts showing up in multiple locations, it knows things are wrong. You'd have to have some method of modifying that data on the copied disks. Today, I don't think there's any support in ZFS for doing that.
--
Darren
