Log in

No account? Create an account
Brackup 1.03 - brad's life — LiveJournal [entries|archive|friends|userinfo]
Brad Fitzpatrick

[ website | bradfitz.com ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Brackup 1.03 [May. 23rd, 2007|02:32 pm]
Brad Fitzpatrick
[Tags|, ]

New Brackup...

1.03 (may 23, 2007)

  - brackup-restore's verbose flag is more verbose now, showing files
    as they're restored.

  - brackup-restore can restore from an encrypted *.brackup file now,
    firing up gpg for user to decrypt to a tempfile

  - brackup-target tool, to list/get brackup files from a target,
    and in the future do garbage collection on no-longer-referenced
    chunks (once a command exists to delete a brackup file from a target)

  - stop leaking temp files

  - doc fixes/additions

[User Picture]From: robflynn
2007-05-23 10:04 pm (UTC)
You are a release fiend!
(Reply) (Thread)
[User Picture]From: schernyshev
2007-05-24 02:29 am (UTC)
Why didn't you opensource ShipIt::Step::LJPost?
Release early, release often! ;)
(Reply) (Thread)
[User Picture]From: brad
2007-05-28 10:59 pm (UTC)
I haven't written it! But I totally should... I already have Net::LiveJournal written.
(Reply) (Parent) (Thread)
[User Picture]From: schernyshev
2007-05-29 12:09 am (UTC)
It's just that this post looks very ShipIt-ish ;)
(Reply) (Parent) (Thread)
[User Picture]From: youngoat
2007-05-24 06:24 am (UTC)

Out of curiosity...

You have checksums for everything you brackup, right? Do you validate it when you do a restore? It'd be kinda' neat to know if Amazon ever corrupts your data. :-)
(Reply) (Thread)
[User Picture]From: grahams
2007-05-24 02:47 pm (UTC)

Re: Out of curiosity...

Please let's not make "brackup" a verb. =)
(Reply) (Parent) (Thread)
[User Picture]From: brad
2007-05-28 11:00 pm (UTC)

Re: Out of curiosity...

I believe it already does, but I'm not looking at the source now.
(Reply) (Parent) (Thread)
From: (Anonymous)
2007-05-24 08:28 am (UTC)
Excellent work Brad!

Two questions:
1) does brackup-target work with Amazon targets? I get:
$ brackup-target amazon list_backups
ERROR: backups method not implemented in sub-class Brackup::Target::Amazon=HASH(0x1841440) at /Library/Perl/5.8.6/Brackup/Target.pm line 67.

2) if I do a backup-restore on an old .brackup file will I rollback my directory tree to that date even if later backups were done? This should be pretty obvious given that Brackup is "incremental", but there's no mention of such behaviour in docs so I ask...

Thank you again!
(Reply) (Thread)
[User Picture]From: brad
2007-05-28 11:02 pm (UTC)
1) whoops, I forgot the Amazon support!

2) brackup-restore should, yes, have an option to take an existing tree and just do an equivalent to "svn switch", bringing it to the older date, but currently it can only restore to an empty directory tree, bailing if files already exist. That's a TODO in the code to extend. It's just way too paranoid now and doesn't have any conflict resolution options/smarts.
(Reply) (Parent) (Thread)
[User Picture]From: grahams
2007-05-26 02:44 am (UTC)
Does Brackup handle HFS resource forks properly?
(Reply) (Thread)
[User Picture]From: brad
2007-05-28 11:01 pm (UTC)
I doubt it, since I know nothing about APIs to access resource forks. Likewise, it won't preserve POSIX ACLs/etc. Just mtime/atime/mode.

Shouldn't be hard to add, though, if you want to give me some hints (or a patch).
(Reply) (Parent) (Thread)
[User Picture]From: grahams
2007-05-29 03:52 pm (UTC)
Patch would take me awhile, as my perl is more than rusty and I've never worked with the forks in perl anyway... If you don't have a chance to swing at it for awhile, I'll take a look at at after I get settled into the new house..

A friend recommended taking a look at the source for psync and MacOSX::File:

(Reply) (Parent) (Thread)
[User Picture]From: idigital
2007-06-28 02:43 am (UTC)
Is there a mailing list or something that I should use to provide some feedback?
(Reply) (Thread)
[User Picture]From: brad
2007-06-28 05:14 am (UTC)
email me, brad@danga.com, with brackup in subject
(Reply) (Parent) (Thread)