git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Repository backups

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 19, 2007, 15:27 UTC
Message-ID
<Pine.LNX.4.64.0709191627040.28395@racer.site>
In-Reply-To
<31e9dd080709190814t6ef8b725w8a8320685e70578b@mail.gmail.com>
Hi,
On Wed, 19 Sep 2007, Jason Sewall wrote:
Show 16 quoted lines
> I'd like to build a modest safety net for my various git repositories
> in case of catastrophic failure. Currently, everything is backed up on
> machines in the same building. I'm not expecting the Computer Science
> building to get hit by terrorists and we're in a seismically stable
> place, but there *is* construction nearby...
> 
> Anyway, my university offers a "mass storage" tape-based service that
> is supposedly very safe. We are encouraged to give them single big
> files for backups.
> 
> The temptation to just make bundles of all branch heads is great but
> probably not what I really want - things like reflogs don't get handed
> off with those, if I understand correctly.
> 
> Is there any argument against just making a tar of a bare clone of the
> repo?
If you make a bare clone, you lose reflogs, too.
So I would backup the complete .git/ directory instead.

Hth, Dscho

Previous: Jason Sewall
Message 2 of 2 in “Repository backups”
  1. Jason SewallSep 19, 2007
  2. Johannes SchindelinSep 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.