Backing store with NetApp

Hi,
We are trying to have TeamSite backing store(iw-store) on NetApp(which is on another machine). The Environment: Solaris 8, TS 5.5.2 SP3. The problem we are facing is when teamsite is installed theres an error in the iwtrace.log that says "Store Manager Failed.". So I rename iw-store to iw-store.old and then restart iwserver which results in a new backing store(iw-store) on the local machine instead of the one on NetApp.... Can anyone help us out?
Thanks a lot in advance.......

Find more posts tagged with

Comments

13adam13

Harold,

The relevant parts of your iw.cfg would help determining what your problem is.
Also, for this to work, I believe that you would need to mount the NetApp machine first, as iw-store, and then start up TS. Then, you would need to make sure that when the box is bounced (which, granted should be about never), the mount points are created before TS is started.

There are probably other considerations when trying to mount a remote backing store, but I have never tried it, so I am not sure what they are. If you have success with this, please share your experience.

--Adam Wilson
Senior Programmer

Migrateduser

It's been a while (>2yrs) since I did this. But IIRC, all I did was mount the NetApp volume at /local/iw-store and tell TS during install that that was where to write backing stores. The location of the default backing store is saved in /etc/defaultiwstore.

Of course you need to configure the NetApp to allow writes to the exported filesystem. I seem to recall needing to make the NetApp treat TS host root as root on the NetApp. But that might have been to implement the snapshot-based backup capability. So the first thing to do is make sure you can write to the NetApp f/s through the mount point on the TS host and that the mount point matches what's in /etc/defaultiwstore. The start you TS server.

Though my recollection of how I did this is fuzzy, I can look at stuff on the TS host filesystem for more hints if needed. I'm not sure I have much access to the NetApp anymore. Our IS dept. has taken over maintenance in the intervening time.

herald10

Hi,
Thanks for all your responses. I am still stuck with the following error while restarting iw-server.... "Failed to start event manager" or "workflow directory not empty". any help plz...

TIA.

Migrateduser

Hey! that's good; it appears you've solved the store issue. It sounds like you should get in touch with tech. supt. and have them help you through getting your server running. The cycletime will be much smaller than asking people here.

herald10

Yeah We did open a case with support they are saying that the problem is with NetApp permission settings. In your first reply you said that you had to do some kind of mapping between root on teamsite and admin on netapp. could you please recall how you did that?
Thanks a lot!!

Migrateduser

Sure, I'll try. But all I did was look up how to do it in the NetApp System Administrator's Guide. Though I think it turned out that once I got to a command prompt I just used the NFS config file to do the job. Based on that recollection, it ought to look like adding this line to <NetApp>:/etc/exports:

volume -root=TS host:any other hosts:...,(anon=65535)

Where:

volume is the volume you're exporting for backingstore use

TS host is the name your NetApp uses for the TeamSite server host machine

You might need to set the anon option. If so set it to all 1s: 65535.

I'm not sure I have access to the NetApp any more. I haven't needed access for >2yrs. I'll check, meantime run this by whoever does NetApp configuration for you so they can confirm that it makes sense. Especially the 'anon' option.

Bill Klish

I was given an Interwoven / Network Appliance whitepaper that was given to me by support. I can't post it as it is quite large (~ 1MB). Let me know if you need it and I can forward it to you.

herald10

That would be very helpful. Could you please forward that attachment file to my email address: sy62k@yahoo.com.

Migrateduser

The exports file, /net/<netapp>/vol/vol0/etc/exports, was accessible. Here is the entry which may be relevent to your situation:

/vol/<backing store vol> -access=<TS host>:<other host>,root=<other host>:<TS host>

herald10

Thanks for all your responses. The problem is fixed now. It was due to some permission setting on NAS(we are using Dell Powervault and its on windows).