Hello Matthew,
Monday, December 17, 2007, 5:45:12 PM, you wrote:
MCA> We are currently running sun cluster 3.2 on solaris 10u3. We are
MCA> using ufs/vxvm 4.1 as our shared file systems. However, I would
MCA> like to migrate to HA-NFS on ZFS. Since there is no conversion
MCA> process from UFS to ZFS other than copy, I would like to migrate
MCA> on my own time. To do this I am planning to add a new zpool
MCA> HAStoragePlus resource to my existing HA-NFS resource group. This
MCA> way I can migrate data from my existing UFS to ZFS on my own time
MCA> and the clients will not know the difference.
MCA> I made sure that the zpool was available on both nodes of the
MCA> cluster. I then created a new HAStoragePlus resource for the
MCA> zpool. I updated my NFS resource to depend on both HAStoragePlus
MCA> resources. I added the two test file systems to the current
dfstab.nfs-rs file.
MCA> I manually ran the shares and I was able to mount the new zfs
MCA> file system. However, once the monitor ran it re-shared I guess
MCA> and now the ZFS based filesystems are not available.
MCA> I read that you are not to add the ZFS based file systems to the
MCA> FileSystemMountPoints property. Any ideas?
You just use Zpool property and not FileSystemMountPoints with ZFS.
Check
http://milek.blogspot.com/2006/09/zfs-in-high-availability-environments.html
for step-by-step example.
btw: for testing, if you really have to test it on production cluster,
I would first create a new test resource group with only two resources
- IP (logicalhostname) and hastorageplus with zfs pool. Then check if
you can failover, failback, etc. once you prove it you know how it
workse, move the resource to production rg.
--
Best regards,
Robert Milkowski mailto:rmilkowski at task.gda.pl
http://milek.blogspot.com