4 messages in com.perforce.perforce-user[p4] Near-line storage for Perforce| From | Sent On | Attachments |
|---|---|---|
| Robert Duff | 15 Oct 2003 08:13 | |
| Jeff Bowles | 15 Oct 2003 09:41 | |
| Dave Lewis | 15 Oct 2003 10:23 | |
| Arnt Gulbrandsen | 15 Oct 2003 10:33 |
| Subject: | [p4] Near-line storage for Perforce |
|---|---|
| From: | Jeff Bowles (ja...@pobox.com) |
| Date: | 10/15/2003 09:41:16 AM |
| List: | com.perforce.perforce-user |
I suspect that symlink-ing the ",d" directory will be less error-prone, in that additional revisions added to the binary file (and thereby stored in the directory) will automatically end up in the same place as the earlier revisions. It allows you to symlink higher up in the tree, pulling over more files and in a more consistent way: 'the 1.0 release is stored on a slower disk' is the effective result.
I haven't tried this (did it for a while with a depot/... tree for space reasons), so take the above with a block of salt.
Otherwise, umm, it sounds quite reasonable. (I'd bounce it past Perforce Technical Support to see if they have any suggestions/concerns, since they are the ones who'll be supporting you anyhow.)
Jeff Bowles Perforce Consulting Partner
-------
From: "Robert Duff" <rduff at rim.net> We're running into a situation here at RIM where we want to make use of some sort of near-line (correct terminology?) storage solution in regards to Perforce. We have the Perforce metadata and data stored on an extremely fast disk array (XP512) but the price point is awfully high for some of the data that is rarely ever accessed any more.
So my question is this: Does anyone have anything in place where you automatically move the files in the ,d directories from one mount point to another, and then reference them with symbolic links, based on access (or perhaps modify) date? And, a far more important question -- is this possible and safe?