Re: [Sks-devel] Copying DBs & Pruning Logs

[Dan Egli]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yaron M. Minsky wrote:

| On Mon, 2003-11-17 at 17:47, Daniel Johnson wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Possibly dumb question:
|>Instead of dumping my database, copying that to another system, and
|>merging it, can I just copy my KDB and PTree directories to save time?
|
|
| Yes, but stop sks_db and sks_recon before doing the copy.
|
|
This is critical. Doing some experimentation Yaron and I discovered that
if you cp your database while sks_recon and sks_db have it open, it has
about a 95% chance of being a corrupted copy. My backup script (that I
run by hand a few times a month) kills sks db and sks recon (I'm betaing
1.0.5, which replaces sks_db and sks_recon with a single sks binary that
takes the operation as a paramater, so your sks_db is my sks db [notice
the lack of an underscore]).

|>My home server took ~30 hours just to merge the dump.  Given that it
|>is ~10x faster than the office system, I'd like to avoid a merge op if
|>I can.  :)
|>
|>BTW, I've got a lot of 10mb log files (~5gb).  Is it safe to delete
|>some of them (say, all but the newest 3)?
|
|
| Use "db_archive" to figure out the list of outdated log files.  "rm
| `db_archive`" will get rid of them.  Don't just do it by hand.

Shutdown sks_db and sks_recon before doing this too. For some reason
db_archive does not like playing with an open database.

- --- Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/upxqtwT22Jak4/4RAgMgAKCjTj02FFA2NqjlDbsz2fTujP4BwACeJ+jL
QmZkYFsv/XWE6Ah0VD1pZFc=
=DviS
-----END PGP SIGNATURE-----