backup

With SVN, I had a single big repository I kept on a server, and checked-out on a few machines. This was a pretty good backup system, and allowed me easily work on any of the machines. I could checkout a specific project, commit and it updated the 'master' project, or I could checkout the entire thing. Now, I have a bunch of git repositories, for various projects, several of which are on github. I also have the SVN repository I mentioned, imported via the git-svn command.. Basically, I like having all my code (not just projects, but random snippets and scripts, some things like my CV, articles

I have a server that hosts my Subversion code base. That server is currently a Windows Server 2003 box, and my IT administrator wants to update it to Windows Server 2008 . This means that I'm going to need to move my Subversion repository while the server gets built up and was wondering what the best practices are for moving the repository to a new server. It seems like, looking online, the recommended way is to use: svnadmin dump /path/to/repository > repository-name.dmp And then use: svnadmin create repository-name svnadmin load repository-name< repository-name.dmp To import the repository.

My SQL Server 2005 doesn't restore a backup because of active connections. How can I force it? George Stocker SQL Server Management Studio 2005 When you right click on a database and click Tasks and then click Detach Database , it brings up a dialog with the active connections. By clicking on the hyperlink under "Messages" you can kill the active connections. You can then kill those connections without detaching the database. More information here . SQL Server Management Studio 2008 The interface has changed for SQL Server Management studio 2008, here are the steps (via: Tim Leung ) Right

I have a Plone installation in my home directory under Linux. ~/Plone . This was made from a default distribution of Plone from its website. So Plone compiled own python and is bundeled with Zope. Please tell me, which files are necessary to backup if I want to: 1) Backup the whole data ever stored in my Plone instance; 2a) Restore the backed-up data in a same version of Plone, but located elsewhere. 2b) Restore the backed-up data in a (slightly) newer version of Plone. I thought, maybe it's a good idea to just backup the whole ~/Plone/zinstance directory, but I found thousands of occurrences

I want to write a java client based on SolrJ which pulls the entire core data to a file from a remote Solr server. Later on I want to replay this file to another remote Solr server core. What is the best method to implement this functionality? It's now possible with latest Solr versions. To achieve backup on one Solr Server and restore on another one needs to do the following: For each Solr installation in solr.xml setup backup repository to point to some shared drive. For example, one can use HDFS (this config requires -Dsolr.hdfs.home=... to be added into start script): <solr> ... <backup>