hm... where can I find Zoomax's notes? Those were useful stuffs. :]

angeek: because the reservation in most cases (to avoid multiple access to the same storage)

1) dont know about checking the size of a vpath.

2) you can convert to Big on the fly.

regards,
Michael

Definitely going to need to study more about MPIO next week.

However, in terms of HACMP I dont think vpath is a monitored resource by HACMP. If it is, then it would be assignable in the extended resource smit menus. However, probably it is just getting it assigned to the disks in the volume group.

re: cascading, rotating, etc..

Those terms were "retired" starting with HACMP 5.1. From the sounds of it, your resource group policy follow what would have been called a cascading resource group.

Basically, a resource group now has three policies that govern it's behavior: startup, fallover (i call this failover frequently, but fallover is the correct documented term), and fallback.

The default policies are, respecitvely: start on Home node, takeover on next node, fallback to higher priority node (old cascading behavior). Your policy of never fallback means it is "modified cascading". However, if your startup policy is "Start on Any node", then your policies more close resemble "rotating".

Basically, this new arrangement makes it much simplier to specify what is going on, or expected to happen, rather than a "name" followed by a list of exceptions.

Hope this answers most of your immediate questions.