5 messages in com.perforce.perforce-user[p4] Hot/Warm Spare for Perforce reco...| From | Sent On | Attachments |
|---|---|---|
| Johnson, Ron | 04 Feb 2004 06:19 | |
| Paul Goffin | 04 Feb 2004 06:32 | |
| Johnson, Ron | 04 Feb 2004 07:42 | |
| Jeff Bowles | 04 Feb 2004 08:22 | |
| Jeff Bowles | 04 Feb 2004 08:37 |
| Subject: | [p4] Hot/Warm Spare for Perforce recommendations |
|---|---|
| From: | Paul Goffin (Paul...@aepsystems.com) |
| Date: | 02/04/2004 06:32:31 AM |
| List: | com.perforce.perforce-user |
I've looked at p4p and remote depots, and they don't really seem to do the trick.
They're not intended to.
I could just run offline checkpoints of the databases, then rsync the depot files to another machine, but with 900k+ > files, the process would take quite a long time.
Why not have a demon process copy the database to the backup every hour (set the "don't copy unchanged files" flag on you copy utility)?
(Checkpoints & journals too.)
What solutions have other Perforce shops out there implemented?
We have a RAIDed server and daily tapes. In the event the main server went down we'd live with the half-day it'd take to recover the tapes.
Paul.
.
******************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the postmaster at the address below. ITS-Support at aepsystems.com Unless the contrary is specifically indicated above nothing in this message is intended to constitute an electronic signature within the meaning of the Electronic Commerce Act 2000 or similar legislation enacted elsewhere in the world. This footnote also confirms that this email message has been checked for the presence of computer viruses. **********************************************************************