Backups with AMANDA - Revision history

Lars: /* Enabling / Disabling a Backup */

2015-10-09T17:09:06Z

Enabling / Disabling a Backup

← Older revision		Revision as of 17:09, 9 October 2015
Line 315:		Line 315:
	# Type '''crontab -e -u amanda''' to edit the contents of the cron file.		# Type '''crontab -e -u amanda''' to edit the contents of the cron file.
	# To disable the line that contains the amanda backup job, place a pound character at the start of the line.		# To disable the line that contains the amanda backup job, place a pound character at the start of the line.
	# If you're using vi, type ''':x''' to save changes and exit. (If you want to cancel your changes, type ''':q!''') If you're using nano, type '''ctl-o''' and '''ctl-x''' to save changes and exit.		# If you're using vi, type '''i''' to go into insert edit mode. After you've inserted or deleted the pound sign, press '''esc''' to exit editing mode. Then type ''':x''' to save changes and exit. (If you want to cancel your changes, type ''':q!''') If you're using nano, type '''ctl-o''' and '''ctl-x''' to save changes and exit.
	# Confirm that the changes were retained by viewing the cron file again: '''crontab -l -u amanda'''		# Confirm that the changes were retained by viewing the cron file again: '''crontab -l -u amanda'''

Gordp: /* Enabling / Disabling a Backup */

2015-10-06T20:54:35Z

Enabling / Disabling a Backup

← Older revision		Revision as of 20:54, 6 October 2015
Line 311:		Line 311:
	To disable or re-enable a backup, you have to edit the cron file.		To disable or re-enable a backup, you have to edit the cron file.
	# Log onto the server that is associated with the amanda backup using your personal credentials. Be aware, though, that Spitfire's backup is handled by Hercules.		# Log onto the server that is associated with the amanda backup using your personal credentials. Be aware, though, that Spitfire's backup is handled by Hercules.
	# Switch to root user. (In the case of Hercules, skip the first step and log on as root right away.)		# Switch to '''root''' user. (In the case of Hercules, skip the first step and log on as root right away.)
	~~# Switch to amanda user.~~
	# Type '''crontab -l -u amanda''' to list the contents of the cron file.		# Type '''crontab -l -u amanda''' to list the contents of the cron file.
	# Type '''crontab -e -u amanda''' to edit the contents of the cron file.		# Type '''crontab -e -u amanda''' to edit the contents of the cron file.

Lars at 20:15, 6 October 2015

2015-10-06T20:15:26Z

← Older revision		Revision as of 20:15, 6 October 2015
Line 305:		Line 305:

	After that, the new tape completely replaces the old hurricane05 tape.		After that, the new tape completely replaces the old hurricane05 tape.



			== Enabling / Disabling a Backup ==
			To disable or re-enable a backup, you have to edit the cron file.
			# Log onto the server that is associated with the amanda backup using your personal credentials. Be aware, though, that Spitfire's backup is handled by Hercules.
			# Switch to root user. (In the case of Hercules, skip the first step and log on as root right away.)
			# Switch to amanda user.
			# Type '''crontab -l -u amanda''' to list the contents of the cron file.
			# Type '''crontab -e -u amanda''' to edit the contents of the cron file.
			# To disable the line that contains the amanda backup job, place a pound character at the start of the line.
			# If you're using vi, type ''':x''' to save changes and exit. (If you want to cancel your changes, type ''':q!''') If you're using nano, type '''ctl-o''' and '''ctl-x''' to save changes and exit.
			# Confirm that the changes were retained by viewing the cron file again: '''crontab -l -u amanda'''

Lars at 15:50, 11 July 2012

2012-07-11T15:50:12Z

← Older revision		Revision as of 15:50, 11 July 2012
Line 292:		Line 292:
	# Wait until Amanda finishes. When done, Amanda will send out a new backup report		# Wait until Amanda finishes. When done, Amanda will send out a new backup report
	# Eject the current tape (ServerName08, in the above example) and put the next tape (ServerName09, in the above example) into the tape drive, as Amanda instructed		# Eject the current tape (ServerName08, in the above example) and put the next tape (ServerName09, in the above example) into the tape drive, as Amanda instructed



			== Replacing a Defective Tape ==

			In the event that a tape cartridge needs to be replaced (eg: tape got eaten, tape backup unit keeps rejecting the tape, etc.), the problematic tape must be removed from Amanda's database. The new, replacement tape must be labelled with the same name as the defective tape that it is replacing.

			For example, let's say that hurricane05 was defective. We'd put a brand new tape into the tape backup unit and then run the following commands:

			amrmtape hurricane hurricane05
			amlabel hurricane hurricane05

			After that, the new tape completely replaces the old hurricane05 tape.

Wilsonl at 02:26, 17 June 2009

2009-06-17T02:26:09Z

← Older revision		Revision as of 02:26, 17 June 2009
Line 264:		Line 264:

	usermod -s /bin/false amanda		usermod -s /bin/false amanda


			== Amanda Tape Usage Overflow ==

			There are times when Amanda has too much data to dump and one tape is not enough. In this case, the Amanda backup report will look similar to this:

			Hostname: ServerName
			Org : OrgName
			Config : SomeConfigName
			Date : June 01, 2099

			These dumps were to tape ServerName07.
			There are 260210700k of dumps left in the holding disk.
			Run amflush to flush them to tape.

			The next tape Amanda expects to use is: ServerName08.

			To correctly deal with this, please follow these steps:
			# The current tape (ServerName07, in the above example) is full, so eject it from the tape drive and store it
			# Put the next tape (ServerName08, in the above example) into the tape drive, as Amanda instructed
			# Log on to the server (ServerName, in the above example) with your userID and password
			# While logged in as userID@ServerName, switch to the ROOT user
			# While logged in as ROOT@ServerName, switch to the Amanda user (by typing '''su - amanda''')
			# While logged in as Amanda@ServerName, run '''amflush SomeConfigName'''
			# Confirm the process. Amanda will now start dumping the remaining data to the new tape (ServerName08, in the above example)
			# Log off the server
			# Wait until Amanda finishes. When done, Amanda will send out a new backup report
			# Eject the current tape (ServerName08, in the above example) and put the next tape (ServerName09, in the above example) into the tape drive, as Amanda instructed

Gordp: /* Amanda Server Configuration */

2008-08-26T21:16:56Z

Amanda Server Configuration

← Older revision		Revision as of 21:16, 26 August 2008
Line 57:		Line 57:
	WARNING: Tape drive has hardware compression enabled		WARNING: Tape drive has hardware compression enabled
	Estimated time to write 2 * 409600 Mbyte: 15400 sec = 4 h 16 min		Estimated time to write 2 * 409600 Mbyte: 15400 sec = 4 h 16 min
			wrote 12320768 32Kb blocks in 94 files in 7558 seconds (short write)
			wrote 12386304 32Kb blocks in 189 files in 8121 seconds (short write)
			define tapetype unknown-tapetype {
			comment "just produced by tapetype prog (hardware compression on)"
			length 386048 mbytes
			filemark 0 kbytes
			speed 50486 kps
			}

Gordp: /* Amanda Server Configuration */

2008-08-26T16:52:24Z

Amanda Server Configuration

← Older revision		Revision as of 16:52, 26 August 2008
Line 53:		Line 53:
	'''Ultrium 960 (LTO3)'''		'''Ultrium 960 (LTO3)'''
	<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 400G -o'''		<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 400G -o'''
			Writing 4096 Mbyte compresseable data: 45 sec
			Writing 4096 Mbyte uncompresseable data: 77 sec
			WARNING: Tape drive has hardware compression enabled
			Estimated time to write 2 * 409600 Mbyte: 15400 sec = 4 h 16 min

Gordp: /* Amanda Server Configuration */

2008-08-26T16:51:45Z

Amanda Server Configuration

Jjaythomas: /* Values to Change in Amanda Client Configurations */

2007-10-24T23:36:22Z

Values to Change in Amanda Client Configurations

← Older revision		Revision as of 23:36, 24 October 2007
Line 157:		Line 157:


	=== Values to Change in ~~Amanda~~ Client Configurations ===		=== Values to Change in Client Configurations ===



			'''vi /etc/xinetd.d/amanda:'''

			yamato.iat.sfu.ca musashi.iat.sfu.ca



			'''vi /etc/services:'''

			amanda 10080/tcp # amanda backup services

			amanda 10080/udp

			kamanda 10081/tcp # amanda backup services (Kerberos)

			kamanda 10081/udp

			amandaidx 10082/tcp # amanda backup services

			amidxtape 10083/tcp



			'''vi /etc/amanda/amandahosts:'''

			sr-musashi.iat.sfu.ca amanda

			musashi.iat.sfu.ca amanda

			209.87.56.239 amanda

			#

			sr-yamato.iat.sfu.ca amanda

			yamato.iat.sfu.ca amanda

			209.87.56.240 amanda

			#

			localhost amanda



			'''vi /etc/amanda/inetd.amanda:'''

			amanda dgram udp wait amanda /usr/libexec/amanda/amandad amandad

			amandaidx stream tcp nowait amanda /usr/libexec/amanda/amindexd amindexd

			amidxtape stream tcp nowait amanda /usr/libexec/amanda/amidxtaped amidxtaped



			'''vi /var/spool/amanda/.amandahosts:'''

			sr-musashi.iat.sfu.ca amanda

			musashi.iat.sfu.ca amanda

			209.87.56.239 amanda

			#

			sr-yamato.iat.sfu.ca amanda

			yamato.iat.sfu.ca amanda

			209.87.56.240 amanda

			#

			localhost amanda



			'''vi /etc/hosts:'''

			209.87.56.240 yamato.iat.sfu.ca yamato

			209.87.56.239 musashi.iat.sfu.ca musashi



			'''Experimental Value (troubleshooting)'''

			usermod -s /bin/false amanda

Jjaythomas: /* what about this */

2007-10-24T23:21:15Z

what about this

← Older revision		Revision as of 23:21, 24 October 2007
Line 157:		Line 157:


	=== ~~what about this~~ ===		=== Values to Change in Amanda Client Configurations ===

← Older revision		Revision as of 16:51, 26 August 2008
Line 28:		Line 28:
	Determine the tapetype entry, in /etc/amanda/Dailyxxx/amanda.conf; here are the results from two different drives, on two separate systems for our LTO-1 tapes:		Determine the tapetype entry, in /etc/amanda/Dailyxxx/amanda.conf; here are the results from two different drives, on two separate systems for our LTO-1 tapes:

	'''Ultrium 230'''		'''Ultrium 230 (LTO1)'''
	define tapetype Ultrium230 {		define tapetype Ultrium230 {
	comment "HP Ultrium 230, produced by amtapetype"		comment "HP Ultrium 230, produced by amtapetype"
Line 36:		Line 36:
	}		}

	'''Ultrium 232'''		'''Ultrium 232 (LTO1)'''
	<font color=lime>amanda@~~trainwreck~~</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 100G -o'''		<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 100G -o'''
	Writing 1024 Mbyte compresseable data: 37 sec		Writing 1024 Mbyte compresseable data: 37 sec
	Writing 1024 Mbyte uncompresseable data: 72 sec		Writing 1024 Mbyte uncompresseable data: 72 sec
Line 50:		Line 50:
	speed 13611 kps		speed 13611 kps
	}		}

			'''Ultrium 960 (LTO3)'''
			<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 400G -o'''


	=== Tape Drive Compression ===		=== Tape Drive Compression ===
	<br>		<br>
	Compression can be turned on or off using the '''mt''' tool noted below, then initiating the tapetype check; kill the tapetype check with '''ctrl-C''' when you've got enough info (takes quite a few minutes)		Compression can be turned on or off using the '''mt''' tool noted below, then initiating the tapetype check; kill the tapetype check with '''ctrl-C''' when you've got enough info (takes quite a few minutes)
	<font color=red>~~trainwreck~~</font> <font color=blue>~ #</font> '''mt -f /dev/nst0 defcompression 1''' ''turns internal-hardware compression '''on'''''		<font color=red>hostname</font> <font color=blue>~ #</font> '''mt -f /dev/nst0 defcompression 1''' ''turns internal-hardware compression '''on'''''
	<font color=red>~~trainwreck~~</font> <font color=blue>~ #</font> '''su - amanda'''		<font color=red>hostname</font> <font color=blue>~ #</font> '''su - amanda'''
	<font color=lime>amanda@~~trainwreck~~</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 100G -o'''		<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 100G -o'''
	Writing 1024 Mbyte compresseable data: 42 sec		Writing 1024 Mbyte compresseable data: 42 sec
	Writing 1024 Mbyte uncompresseable data: 72 sec		Writing 1024 Mbyte uncompresseable data: 72 sec
Line 62:		Line 66:
	Estimated time to write 2 * 102400 Mbyte: 14400 sec = 4 h 0 min		Estimated time to write 2 * 102400 Mbyte: 14400 sec = 4 h 0 min

	<font color=lime>amanda@~~trainwreck~~</font> <font color=blue>~ $</font> '''logout'''		<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''logout'''
	<font color=red>~~trainwreck~~</font> <font color=blue>~ #</font> '''mt -f /dev/nst0 defcompression 0''' ''turns internal-hardware compression '''off'''''		<font color=red>hostname</font> <font color=blue>~ #</font> '''mt -f /dev/nst0 defcompression 0''' ''turns internal-hardware compression '''off'''''
	<font color=red>~~trainwreck~~</font> <font color=blue>~ #</font> ''' su - amanda'''		<font color=red>hostname</font> <font color=blue>~ #</font> ''' su - amanda'''
	<font color=lime>amanda@~~trainwreck~~</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 100G -o'''		<font color=lime>amanda@hostname</font> <font color=blue>~ $</font> '''amtapetype -f /dev/nst0 -e 100G -o'''
	Writing 512 Mbyte compresseable data: 38 sec		Writing 512 Mbyte compresseable data: 38 sec
	Writing 512 Mbyte uncompresseable data: 39 sec		Writing 512 Mbyte uncompresseable data: 39 sec