[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: subversion to back up SQL server

From: Ruslan Sivak <rsivak_at_istandfor.com>
Date: 2006-04-27 19:21:06 CEST

The whole point is that I would like to keep a history of possibly older
then 2 weeks, and not use a lot of space to do it.

I understand that if you reorg or something, I might end up with a complete
db backup again. But I did the backup a few mins apart... there shouldn't
have been that many changes... Why did it backup the complete file again?

-----Original Message-----
From: Andy Levy [mailto:andy.levy@gmail.com]
Sent: Thursday, April 27, 2006 1:12 PM
To: Ruslan Sivak
Cc: users@subversion.tigris.org
Subject: Re: subversion to back up SQL server

On 4/27/06, Ruslan Sivak <rsivak@istandfor.com> wrote:
> I might research the sql server built in facilities a little more, but the
> reason I want to use subversion is so that I can have an on-disk backup
with
> history. I would like to be able to pull up a backup from 2 weeks ago,
and
> not have to wait for tape to arrive...

You can do that with the built-in backup. Might need an extra script
to blast any backup older than 2 weeks, but that's not hard to write.

> With proper diffing, subversion should only be storing the changes in the
> file, as opposed to the whole file, so in the end, the repository should
> remain small.

Unless you do a reorg, make a table definition change, re-index the
table, shrink the database, etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 27 19:29:39 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.