Rahul> Can somebody provide me a little help with Clearcase and Netapps Rahul> a) Is is recommended to have a different volume dedicated for Rahul> Clearcase Related Data.

It's better this way, since you can put the vobs/views into seperate qtrees, and then manage your snapshots by hand on this volume, since you need to lock the VOBs (as of CC 5.x, you can lock views too) while doing the snapshot.

Rahul> b) Can I have a single volume to accommodate the CC-Vobs & Rahul> other data.

Sure, but the other data will have it's snapshots done with the VOBs, so it might not fit your needs. We ended up dedicating a volume to VOBs/VIEW data, and putting other data into vol0.

Rahul> c) As far as I understand we need to have "nvfail on" for the Rahul> volume related to clearcase

Read the Rational release notes.

Rahul> d) Backing up or taking snapshot for the CC data requires to Rahul> have the "vobs locked" during that time. How does that come Rahul> into picture if I have a different volume for clearcase vesrus Rahul> having a mixture of all the data on one volume

It's simple, just do:

foreach v (list of vobs) cleartool lock $v end rsh filer "snap create $vol $snapname" foreach v (list of vobs) cleartool unlock $v end

Of course all the error checking and such adds alot to this, along with whether or not you have this script run on your VOB server(s), or your NetApp Admin server.

I've got scripts I'd be happy to share with people for doing this where we have:

- VOBs/VIEWs on a toaster - machine A is toaster admin hosts (rsh root access) - machines V1...Vn are the VOB servers (gotta run locks on the servers) - some perl scripts to setup the coordination between all the parts that need to run in various places.

John John Stoffel - Senior Unix Systems Administrator - Lucent Technologies stoffel@lucent.com - http://www.lucent.com - 978-399-0479