Hi Kumar,

We are CC users on NetApps. It works great!

Question 1. I would say yes, as it means you can set a no quotas style volume and not worry about your CC data swallowing up all your available resource.

Question 2. As per the info above I would say no. Keep the CC data separate. There seems to be no official reason for this, but it make managing it all easier.

Question 3. Locking the vobs is relatively easy. We use a Perl script that another message board regular and employ of our company devised for us. It simply runs a lock command on all vobs, runs a snapshot command on the filer volume then unlocks all the vobs. The snapshot can then be backed up at leisure. I will ask him if he thinks this is something he could publish.

This kind of adds weight to the argument for having a separate volume. You are not wise to do incremental backups of CC data. There is no real way to restore an incremental, so full backups are required, and this means nightly full backups of the whole CC data. If you are chucking other data in there as well this means full nightly backups of ALL your data! CC data grows fast, so will be a big lump on its own.

Hope this helps. There are great white papers on NOW that cover this too.

Simon

-----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: 27 June 2003 11:24 Cc: toasters@mathworks.com Subject: Clearcase and Netapp

Hi All,

Can somebody provide me a little help with Clearcase and Netapps a) Is is recommended to have a different volume dedicated for Clearcase Related Data. b) Can I have a single volume to accommodate the CC-Vobs & other data. c) As far as I understand we need to have "nvfail on" for the volume related to clearcase d) Backing up or taking snapshot for the CC data requires to have the "vobs locked" during that time. How does that come into picture if I have a different volume for clearcase vesrus having a mixture of all the data on one volume

Regards Rahul Kumar