The CCP disk array, hosted on copper.cgd.ucar.edu, consists of a total of about 32TB (Terabytes) of usable disk space. The partition names, their intended uses, and the availability of automated backups is detailed in the following table.

The partitions that make up the disk array are not visible (via NFS-crossmounting) from any machine, in CGD or elsewhere, other than copper. Crossmounting these disks to other machines is subject to the CGD ISG as well as NCAR security policy. Users of the disk array cannot count on these disks being visible other than on copper.

All use of the disk array is subject to CCP staff review, and individual users and/or files may be moved, or removed, at CCP discretion. We will make all reasonable attempts to contact the owner(s) of any files located on the CCP disks before removal, but we cannot assure that removal will not take place even without affirmation from the owner(s) of the files.

The CCP group prefers (but does not require) that the use of the disk array is as follows:
ccpa:
Intended for "small" files, like source code, scripts, text files, and other similar types of files. Each user of the disk array will be given a subdirectory, using their CGD username, to store files. It is highly recommended that large data files not be placed on the ccpa partition.
If large files placed on ccpa interfere with the automated backup process (by filling up ccpa) they will be removed without notice.
ccpb, ccpc, ccpd, ccpe, ccpf, ccpg:
Intended for large data file storage. These disks are "permanent" online archives of model output data, and data derived from model data. Analysis scripts, codes, NCL scripts, IDL scripts and so on stored on these disks are not available for automated backups.

There are currently no quotas instituted on copper. The CCP group does monitor the use of the disk array on a daily basis, but we assume that all users will be "good neighbors" and not consume unreasonable amounts of disk space unless prior arrangements with the CCP group are made. If this becomes unworkable, quotas (on a per-user basis) will be instituted.

Since the CCP group controls the disk array, the policy for backups is as follows:

The ccpa disk will be subject to automated backups to the NCAR MSS, using scripts provided by the CCP group. It is highly recommended that these scripts be used, as opposed to writing your own backup scripts. copper is not a large CPU machine, and increasing its load via your own backup scripts is strongly discouraged.

These scripts will be run as "cron" jobs, from copper, and will be appropriately spaced to be run during the overnight (using Mountain Standard Time) hours.

To set up the creation of automated backups of your files on ccpa, or if you have support-type questions about these scripts, please contact Gary Strand (strandwg@ucar.edu).

The backup files themselves will be (temporarily) stored in the directory /datalocal/ccpa/BACKUPS/$user, before being written to the NCAR MSS.

Files located in these partitions will be the responsibility of their owner(s). If the file is very important, back it up to the NCAR MSS. Shell scripts, NCL scripts, FERRET .jnl files, source code and so on located on the 'b' through 'g' partitions will NOT be automatically backed up. Users of the disk array who would like a simple script to backup files on any of these data partitions need to contact Gary Strand (strandwg@ucar.edu).

An acknowledgment (form is here, in PDF format) must be signed and returned to Gary Strand, to ensure that all users of copper and the CCP disk array understand and accept all the policies outlined here.

Any further comments/questions/suggestions should be addressed to ccp@cgd.ucar.edu.