Backup Tools - Revision history

Root at 13:32, 28 January 2011

2011-01-28T13:32:21Z

← Older revision		Revision as of 13:32, 28 January 2011
Line 1:		Line 1:
	{{Box\|As of January 2011 I have moved to a different backup software. Read about the new solution [[Proud to be paranoid -- backup strategy for the lazy and forgetful\|here.}}		{{Box\|As of January 2011 I have moved to a different backup software. Read about the new solution [[Proud to be paranoid -- a backup strategy for the lazy and forgetful\|here]].}}
	[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]		[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]
	==Why?==		==Why?==

Root at 13:31, 28 January 2011

2011-01-28T13:31:57Z

← Older revision		Revision as of 13:31, 28 January 2011
Line 1:		Line 1:
	{{Box\|As of ~~13:29, 28~~ January 2011 ~~(GMT)~~}}		{{Box\|As of January 2011 I have moved to a different backup software. Read about the new solution [[Proud to be paranoid -- backup strategy for the lazy and forgetful\|here.}}
	[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]		[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]
	==Why?==		==Why?==

Root at 13:30, 28 January 2011

2011-01-28T13:30:23Z

← Older revision		Revision as of 13:30, 28 January 2011
Line 1:		Line 1:
	{{~~wbox:~~As of 13:29, 28 January 2011 (GMT)}}		{{Box\|As of 13:29, 28 January 2011 (GMT)}}
	[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]		[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]
	==Why?==		==Why?==

Root at 13:29, 28 January 2011

2011-01-28T13:29:22Z

← Older revision		Revision as of 13:29, 28 January 2011
Line 1:		Line 1:
			{{wbox:As of 13:29, 28 January 2011 (GMT)}}
	[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]		[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]
	==Why?==		==Why?==

Root at 08:24, 4 October 2009

2009-10-04T08:24:00Z

← Older revision		Revision as of 08:24, 4 October 2009
Line 1:		Line 1:
			[[File:2007-12-23_12.47.11_0000000424Tivoli-vialla_andriana_and_Este_048.jpg\|thumb\|400px\|right]]
	==Why?==		==Why?==
	Contrary to popular belief -- Computer failures do happen! They are rare in today's modern hardware, but when they do happen, they are devastating. Once I dropped notebook running from a room to room in the office -- the computer survived with some minor blemishes -- but the hard drive was gone -- with all the data in it! Another time my hard disk JUST failed! When these things happen, there is almost no way to recover the data from the failed hardware. Of course there are numerous specialized companies doing data recovery (try Googling), but they are not for us mortals! Data recovery from failed hardware will cost you an arm and a leg. Once one of my rich friends from a rich company faced this situation. First, we tried local services -- and we were surprised by the quotations. Then my friend started carrying the failed hardware with him during his numerous business trips to Asia hoping (quite desperately, for like most of us, he also did not backup his data!) he'd find a reasonable recovery service! To cut the long story short -- he had to live with the loss and recover slowly. Having witnessed the amount of time and effort that was wasted during this event, I almost preach to all I know on the virtues of a good backup system. Until recently there were no backup software I could outrightly recommend to a person who do not want to make major sacrifices to the advancement of the art of hacking. But, the times have changed. Therefore, it's a good time to make a summary of the options.		Contrary to popular belief -- Computer failures do happen! They are rare in today's modern hardware, but when they do happen, they are devastating. Once I dropped notebook running from a room to room in the office -- the computer survived with some minor blemishes -- but the hard drive was gone -- with all the data in it! Another time my hard disk JUST failed! When these things happen, there is almost no way to recover the data from the failed hardware. Of course there are numerous specialized companies doing data recovery (try Googling), but they are not for us mortals! Data recovery from failed hardware will cost you an arm and a leg. Once one of my rich friends from a rich company faced this situation. First, we tried local services -- and we were surprised by the quotations. Then my friend started carrying the failed hardware with him during his numerous business trips to Asia hoping (quite desperately, for like most of us, he also did not backup his data!) he'd find a reasonable recovery service! To cut the long story short -- he had to live with the loss and recover slowly. Having witnessed the amount of time and effort that was wasted during this event, I almost preach to all I know on the virtues of a good backup system. Until recently there were no backup software I could outrightly recommend to a person who do not want to make major sacrifices to the advancement of the art of hacking. But, the times have changed. Therefore, it's a good time to make a summary of the options.

Root: Text replace - '

' to '
'

2009-10-02T19:07:11Z

Text replace - '<pre>' to ' <pre>'

← Older revision		Revision as of 19:07, 2 October 2009
Line 37:		Line 37:
	* Apply time-limit patch.		* Apply time-limit patch.
	* compile and install		* compile and install

	<pre>		<pre>
	cd /tmp		cd /tmp
Line 55:		Line 56:

	I create the following script in the directory <tt>/home/tommy/backups</tt> as sitebackup.bash		I create the following script in the directory <tt>/home/tommy/backups</tt> as sitebackup.bash

	<pre>		<pre>
	#!/bin/bash		#!/bin/bash
Line 66:		Line 68:
	</pre>		</pre>
	Then add a [[wikipedia:crontab\|crontab]] entry:		Then add a [[wikipedia:crontab\|crontab]] entry:

	<pre>		<pre>
	03 1 * * * /home/tommy/backups/sitebackup.bash >& /home/tommy/backups/sitebackup.bash.log		03 1 * * * /home/tommy/backups/sitebackup.bash >& /home/tommy/backups/sitebackup.bash.log

Root: /* Scenario 1: Daily backup of a website */

2009-10-01T18:29:06Z

Scenario 1: Daily backup of a website

← Older revision		Revision as of 18:29, 1 October 2009
Line 77:		Line 77:
	What I have to do:		What I have to do:
	;Occasionally:		;Occasionally:
	:* Check the log files (<tt>sitebackup.bash.log</tt>, tt>sitebackup.bash.01.log</tt>, <tt>sitebackup.bash.02.log</tt>, ...) to see if things are running smoothly.		:* Check the log files (<tt>sitebackup.bash.log</tt>, <tt>sitebackup.bash.01.log</tt>, <tt>sitebackup.bash.02.log</tt>, ...) to see if things are running smoothly.
	:* Check the backup files at <tt>/backup/site</tt> to see if they are OK.		:* Check the backup files at <tt>/backup/site</tt> to see if they are OK.

	[[Category:Computing]][[Category:Unix]]		[[Category:Computing]][[Category:Unix]]

Root: /* Scenario 1: Daily backup of a website */

2009-10-01T18:28:28Z

Scenario 1: Daily backup of a website

← Older revision		Revision as of 18:28, 1 October 2009
Line 51:		Line 51:
	I have done this in Linux distributions and in [[Cygwin]] without issues. I do this in all machines that participate in my rsync activities.		I have done this in Linux distributions and in [[Cygwin]] without issues. I do this in all machines that participate in my rsync activities.

	==Scenario 1: Daily backup of a website==		===Scenario 1: Daily backup of a website===
	First I install my custom rsync in the local and remote machines. Then I make it possible to login from the local machine to the remote machine without a password. [[SSH login without passwords\|Here's how.]]		First I install my custom rsync in the local and remote machines. Then I make it possible to login from the local machine to the remote machine without a password. [[SSH login without passwords\|Here's how.]]

Root: /* Scenario 1: Daily backup of a website */

2009-10-01T18:28:06Z

Scenario 1: Daily backup of a website

← Older revision		Revision as of 18:28, 1 October 2009
Line 71:		Line 71:

	What this will do is:		What this will do is:
	* Every day at 0103HRs, an rsync session will start and backup (remote) the directory <tt>/home/tom/</tt> to the directory <tt>/backup/site/</tt> in the local machine. \		* Every day at 0103HRs, an rsync session will start and backup (remote) the directory <tt>/home/tom/</tt> to the directory <tt>/backup/site/</tt> in the local machine.
	* The rsync session will not last more than 1400 minutes (just short of a day). So that the possibility of two rysnc sessions running once is eliminated. If the first day's rsync session could not complete the job, the next day's session starts from where it left.		* The rsync session will not last more than 1400 minutes (just short of a day). So that the possibility of two rysnc sessions running once is eliminated. If the first day's rsync session could not complete the job, the next day's session starts from where it left.
	* If there is not much change in the remote machine, the rsync session will be short. If there's no change it will be very short (just ring and check for changes!).		* If there is not much change in the remote machine, the rsync session will be short. If there's no change it will be very short (just ring and check for changes!).

Root: /* Scenario 1: Daily backup of a website */

2009-10-01T18:27:47Z

Scenario 1: Daily backup of a website

← Older revision		Revision as of 18:27, 1 October 2009
Line 72:		Line 72:
	What this will do is:		What this will do is:
	* Every day at 0103HRs, an rsync session will start and backup (remote) the directory <tt>/home/tom/</tt> to the directory <tt>/backup/site/</tt> in the local machine. \		* Every day at 0103HRs, an rsync session will start and backup (remote) the directory <tt>/home/tom/</tt> to the directory <tt>/backup/site/</tt> in the local machine. \
	* The rsync session will not last more than 1400 minutes (just short of a day). So that the possibility of two rysnc sessions running once is eliminated. If the first day's rsync session could not complete the job, the next day's session ~~strts~~ from where it left.		* The rsync session will not last more than 1400 minutes (just short of a day). So that the possibility of two rysnc sessions running once is eliminated. If the first day's rsync session could not complete the job, the next day's session starts from where it left.
	* If there is not much change in the remote machine, the rsync session will be short. If there's no change it will be very short (just ring and check for changes!).		* If there is not much change in the remote machine, the rsync session will be short. If there's no change it will be very short (just ring and check for changes!).

	What I have to do:		What I have to do:
	;Occasionally:		;Occasionally:
	:* Check the log files (<tt>sitebackup.bash.log</tt>, tt>sitebackup.bash.01.log</tt>, tt>sitebackup.bash.02.log</tt>, ...) to see if things are running smoothly.		:* Check the log files (<tt>sitebackup.bash.log</tt>, tt>sitebackup.bash.01.log</tt>, <tt>sitebackup.bash.02.log</tt>, ...) to see if things are running smoothly.
	:* Check the backup files at <tt>/backup/site</tt> to see if they are OK.		:* Check the backup files at <tt>/backup/site</tt> to see if they are OK.

	[[Category:Computing]][[Category:Unix]]		[[Category:Computing]][[Category:Unix]]

Backup Tools - Revision history

Root at 13:32, 28 January 2011

Root at 13:31, 28 January 2011

Root at 13:30, 28 January 2011

Root at 13:29, 28 January 2011

Root at 08:24, 4 October 2009

Root: Text replace - '' to ' '

Root: /* Scenario 1: Daily backup of a website */

Root: /* Scenario 1: Daily backup of a website */

Root: /* Scenario 1: Daily backup of a website */

Root: /* Scenario 1: Daily backup of a website */

Root: Text replace - '
' to '
'