[p4] Revision limiting

[Slava Imeshev]

I think the root of the problem is that you use Perforce 
as a backup storage, and not as a revision control system.

This is legitimate use for many cases (think golden
master CD images). But in your case the rate of change
for that binary files may signal that the stored items 
are in fact intermediate or short-lived objects (such as 
nightly builds). 

The other signal is that you care about only a month worth 
of these objects and older objects are not required to be 
online all the time.

The ultimate solution could be a "normal" file storage for 
that objects with some sound backup policy.

Hope this helps.

Regards,

Slava Imeshev
www.viewtier.com

--- Jeff Desharnais <jdesharnais at maddocsoftware.com> wrote:

> This could work, only if there is a good solution for permanently
> backing up those older versions and storing them away.
> 
> Is this really possible, to remove old revisions but still have them
> backed up somewhere and retrievable/restorable? 
> 
> Thanks.
> 
> 
> 
> -----Original Message-----
> From: Russell C. Jackson [mailto:rusty at rcjacksonconsulting.com] 
> Sent: Thursday, September 28, 2006 11:27 AM
> To: Robert Cowham
> Cc: Jeff Desharnais; perforce-user at perforce.com
> Subject: Re: [p4] Revision limiting
> 
> If you don't need the old versions, it is pretty easy to create a script
> that will obliterate all the last X revisions. I did this for a team
> that said they only needed to keep the last 5 revisions of the binaries
> they were checking in available. It has been requested many times that
> Perforce support this behavior directly, but so far, they have not
> implemented it.
> 
> Thanks,
> Rusty
> 
> --------------------------------------------------
> RCJackson Consulting
> Perforce Consulting Partner and Certified Trainer
> --------------------------------------------------
> rusty at rcjacksonconsulting.com
> http://www.rcjacksonconsulting.com
> tel:      479-696-9710
> fax:      479-967-0963
> mobile:   479-747-3845
> --------------------------------------------------
> 
> 
> 
> 
> Robert Cowham wrote:
> > Look at Richard Baum's presentation:
> >
> > http://www.perforce.com/perforce/conf2005/index.html
> >
> > Note that ICManage do something similar for their customised version 
> > of Perforce.
> >
> > Regards
> > Robert
> >
> >   
> >> -----Original Message-----
> >> From: perforce-user-bounces at perforce.com
> >> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff 
> >> Desharnais
> >> Sent: 27 September 2006 22:50
> >> To: perforce-user at perforce.com
> >> Subject: [p4] Revision limiting
> >>
> >> Hello,
> >>
> >> We are experiencing an issue where we have large files
> >> (250mb) with 150 revisions. My concern is the amount of space this is
> 
> >> taking up, and it is starting to cause backup problems (time and 
> >> space).
> >>
> >> My question is in regards to the idea of limiting the amount of 
> >> revisions a certain file will retain.
> >>
> >> If a 250mb file only needs a month of revisions at a time, we could 
> >> save many gigs of space. Perhaps store the old revisions on one tape 
> >> and leave it locked away.
> >>
> >> Is there a good (and safe) practice for doing this that anyone could 
> >> suggest?
> >>
> >> Thanks,
> >>
> >> ---------------------
> >> Jeff Desharnais
> >> IT Specialist
> >> Mad Doc Software
> >> 100 Burtt Rd., Suite 220
> >> Andover, MA  01810
> >> (978) 409-6272 Ext. 132
> >>
> >> _______________________________________________
> >> perforce-user mailing list  -  perforce-user at perforce.com 
> >> http://maillist.perforce.com/mailman/listinfo/perforce-user
> >>
> >>
> >>     
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com 
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >
> >   
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
>