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

Best practices: BACKUP?

From: Mayur Jobanputra \(V\) <MJobanputra_at_intrawest.com>
Date: 2006-06-09 03:15:47 CEST

I am sorry if this answer is already online but I have done quite a bit
of research on this topic already and haven't found a really clear
answer. In some cases it's recommended to do nightly complete dumps
while others say that an incremental backup is fine. To me, having
quick reliable DB restores is the most important function of our backup
(heavy development). Some of you are zipping the archives also which I
would like to learn more about. It would be nice if someone would share
their batch and python files. I know there is a script called
hot-backup.py but I have been warned that if I run it while someone is
committing changes, it could damage our db. Its also more/less
important depending on the type of DB one has. Which one do I have?

 

Must have: nightly backups of the complete db to a shared folder on the
network.

Nice to have: the backups are zipped before they are sent over the
network, and instructions for disaster recovery situations

 

Our environment: Tortoise SVN, Python 2.4, Windows 2003 server

 

Thanks in advance!

===========================
Mayur Jobanputra
AST Development - Buildmaster
Advanced Sales Technology group
phone: 604.647.0706
fax: 604.683.6778
cell: 604.787.9993
email: mjobanputra@intrawest.com <mailto:mjobanputra@intrawest.com>
http://www.intrawest.com <http://www.intrawest.com/>
==========================
Received on Fri Jun 9 03:20:43 2006

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

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