Snaplock with OnDemand & TSM?

[Justin Derrick]

I've been approached about implementing OnDemand with NetApp's 'SnapLock' product, which provides WORM (Write-Once Read-Many) functionality to SAN disk...  My initial response was that DR550 and Centera are the preferred WORM Disk solutions...

Is anyone using SnapLock in Production with OnDemand?  I'd be curious to hear about your experiences.

Thanks in advance...

-JD.

[jkari]

Hi!
I might be a little late, but we did move from opticals to netapp last winter. Snaplock was not usable, because you can't move existing archive into it, only a new one can be configured to use snaplock.
We solved this by changing manually (yeah, actually with a script) the attributes of the fully files to readonly. Aftr this netapp takes care that this file can't be changed or removed.

Juha Kari
TietoEnator Helsinki Finland

[msreed]

Hi!
I might be a little late, but we did move from opticals to netapp last winter. Snaplock was not usable, because you can't move existing archive into it, only a new one can be configured to use snaplock.
We solved this by changing manually (yeah, actually with a script) the attributes of the fully files to readonly. Aftr this netapp takes care that this file can't be changed or removed.

Juha Kari
TietoEnator Helsinki Finland

I was reading your reply-post on OD/TSM and Snap lock about changing the full files to read only manually. Do you mean  you used TSM command (say. update vol libname volname acc=readonly) on every volume that reached the size limit?

The way I understood the snaplock is that it would allow to set a threshold(say for eg. 30 days), so each new file
that gets created would remain writable upto 30 days from the day of it's creation and once those 30 days are passed file would become readonly. The duration it remains readonly can also be pre-set.

Thank you in advance for any help.

[iwitt]

I am trying to move all my IBM content Manager images(v7.2) from optical (3995) to Netapp and elminate TSM once it is on NetAPP. What utility did you use to do this so that CM will know the new location of the images. Help!! I have been trying  to figure this out for awhile ...any help  will be appreciated. I Have AIX v5.2 but will  be moving to a new AIX server(v5.3) and TSM will not be installed  on the new AIX server for CM.

iwitter@saf.sc.gov

[Justin Derrick]

Wow...  I thought this thread was dead for sure...

Without getting too deep, I highly recommend keeping TSM as a component of your CMOD system because it allows for redundancy, flexibility, and near infinite capacity.  Even for new customers who say that their system "won't grow to be that big", I stress the importance of having TSM to allow for future growth that might not be obvious -- things like acquisitions, mergers, new lines of business, or new uses for CMOD.  Most of the concerns about running TSM can be dealt with with a couple days of training.

In terms of SnapLock and CMOD, the system that was eventually implemented connected SnapLock to TSM, and used in very much the same way that it was when they simply had TSM and optical libraries.

I'm not familiar enough with the inner workings of the SnapLock product to be able to suggest how it might be used without TSM, but feel free to post again with more details about how you were planning on using it for us to review and talk about.

Good luck!