Re: tapeless backups doc
I almost have it, I can do amcheck -c, but amcheck -t will return ERROR: file:/home/software/amanda/backup: not an amanda tape (expecting a new tape) $amverify Daily No tape changer... Tape device is file:/home/software/amanda/backup... Verify summary to amanda Defects file is /tmp/amanda/amverify.30434/defects amverify Daily lun dic 30 12:50:39 CET 2002 Using device file:/home/software/amanda/backup Waiting for device to go ready... Rewinding... Processing label... ** Error reading label on tape When I try to do amdump *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: a new tape. FAILURE AND STRANGE DUMP SUMMARY: agisrv03.a /etc lev 0 FAILED [can't switch to incremental dump] That's my tape config. tapedev file:/home/software/amanda/backup tapetype DLT I mkdir /home/software/amanda/backup/data from the amanda user. And I made sure amanda could write there. Any hints ? Thank you for your time.
Script for maintaining on-disk backups
Hi all, I use amanda in a mostly on hard disk setup. Two machines are backing each other (and themselves) up every night; since chances of simultaneous hardware failure on two machines is probably not that high, this at least reduces the risk of on-disk backups somewhat. Some backups are also occasionally written to CD. In such a system, it is easy to fill up quite a lot of disk space quickly. And a lot of the data will be filled up by data that has been obsoleted by a later backup; finding and deleting that by hand could quickly turn into a nightmare, so I wrote a little Python script that will maintain the backup archive for me. The script first catalogues all files on disk, then looks for the obsolete ones (eg: a fresh level 1 dump makes all the preceding dumps with equal or higher levels obsolete) and deletes them. An additional variable can be used to determine the wanted duplicity, which is called keep. Example: If keep is set to 2 and the last dump was level 3, the program will delete all dumps with levels of 4 and higher, while keeping the last and second-last level 3 dump. Finally, the script will create an Index file in which a user can see the archive and quickly find out which files exist and where to go looking for the latest backups. Since there are probably others running on-disk backups, the script is appended below. It works quite well for me, maybe it will be useful to someone, maybe not. Regards, Georg maintenance.py Description: Binary data -- Georg C. F. Greve [EMAIL PROTECTED] Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World(http://brave-gnu-world.org) msg16662/pgp0.pgp Description: PGP signature
Re: Script for maintaining on-disk backups
On Mon, Dec 30, 2002 at 01:12:22PM +0100, Georg C. F. Greve wrote: Hi all, I use amanda in a mostly on hard disk setup. [[ snip ]] The script first catalogues all files on disk, then looks for the obsolete ones (eg: a fresh level 1 dump makes all the preceding dumps with equal or higher levels obsolete) and deletes them. An additional variable can be used to determine the wanted duplicity, which is called keep. Example: If keep is set to 2 and the last dump was level 3, the program will delete all dumps with levels of 4 and higher, while keeping the last and second-last level 3 dump. If I understand your algorithm, it would defeat one of the amanda capabilities I like and have used a number of times; the ability to recover files as of a particular date. For example, not too long ago I badly mangled a boot-time configuration file. Did not realize any problem until a reboot several weeks later. As I keep 4 dumpcycles worth of backups (tape, not hard disk, but the concept would be the same), I just recovered the config file by picking a date 3 weeks earlier, prior to my botch job. Just food for thought. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amandad busy
Hi all, I was just wondering why would amanda send a message amandad busy. Do I need to check before running amdump that would solve my problem?? Thanks Adnan Olia
Re: amandad busy
On Mon, 30 Dec 2002, Adnan Olia wrote: I was just wondering why would amanda send a message amandad busy. Do I need to check before running amdump that would solve my problem?? Typically this means that a previous run has not yet finished. Maybe something got hung? Does ps show any amanda processes running? Another possibility is that you listed multiple filesystems from the same client with different hostnames in disklist. This would cause amanda server to view them as different clients and attempt a separate connection to each. The second connection will find amandad already busy from the first connection. -Mitch
Problem with initial install of amanda on SCO openserver
I have installed amanda on SCO Openserver 5.0.6, and everything has
passed the checks. However, when I issue the command:
su amanda -c /usr/local/sbin/amdump Daily
I get the report at the bottom of this email.
I have checked the net and the faq-o-matic, and can't
seem to figure out what is causing this. The only note that
I saw related to symlinks, but there are none in /home.
Please help me by telling me where to look, or ask for
information I have not provided. I'm new at this, so I
don't even know what information is needed.
-Josh
[EMAIL PROTECTED]
--Start Report
These dumps were to tape DailySet101.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
backupmast /home RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk backupmaster:/home.
driver: WARNING: got empty schedule from planner
taper: tape DailySet101 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
backupmaster /home MISSING --
(brought to you by Amanda version 2.4.3)
--End Report--
amstatus doesn't work
[root@backup root]# su amanda -c amstatus DailySet1 bash: /root/.bashrc: Permission denied /var/lib/amanda/DailySet1/amdump: No such file or directory at /usr/sbin/amstatus line 103. [root@backup root]# ls -l /var/lib/amanda/DailySet1/ total 148 -rw---1 amanda disk27751 Dec 30 02:04 amdump.1 -rw---1 amanda disk29060 Dec 29 02:05 amdump.2 -rw---1 amanda disk26758 Dec 28 02:05 amdump.3 -rw---1 amanda disk 190 Dec 17 11:53 amflush.1 drwxr-sr-x 12 amanda disk 4096 Dec 27 14:13 curinfo drwxr-xr-x 12 amanda disk 4096 Dec 27 14:09 index -rw---1 amanda disk 511 Dec 12 16:37 log.20021212.0 -rw---1 amanda disk 297 Dec 12 16:42 log.20021212.1 -rw---1 amanda disk 297 Dec 17 11:52 log.20021217.0 -rw---1 amanda disk 222 Dec 17 11:53 log.20021217.1 -rw---1 amanda disk 2286 Dec 18 16:06 log.20021218.0 -rw---1 amanda disk 2404 Dec 19 17:31 log.20021219.0 -rw---1 amanda disk 2375 Dec 26 15:40 log.20021226.0 -rw---1 amanda disk 2585 Dec 27 14:13 log.20021227.0 -rw---1 amanda disk 2412 Dec 28 02:05 log.20021228.0 -rw---1 amanda disk 2296 Dec 29 02:05 log.20021229.0 -rw---1 amanda disk 2296 Dec 30 02:04 log.20021230.0 drwx--2 amanda disk 4096 Dec 12 16:37 oldlog Sur enough, there is no /var/lib/amanda/DailySet1/amdump But amanda is supposed to automagically create that stuff, right? -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Still get No index records...
On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 backup AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-12-30) 200 Working date set to 2002-12-30. 200 Config set to DailySet1. 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? I do have index yes in amanda.conf. Why is it still unhappy? Where specifically in amanda.conf? This is supposed to be a dumptype by dumptype configuration option. That leaves the posibility that someplace in the chain of defines, its turned back off by your choice of dumptypes. There may be a dim possibility that your particular tar is fubar, what version are you useing? Minimum generally speaking is 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is usually grounds enough to replace it with the newer release. Get 1.13-25 from alpha.gnu.org. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.21% setiathome rank, not too shabby for a WV hillbilly
Re: amstatus doesn't work
On Mon, Dec 30, 2002 at 09:19:02PM -0500, Gene Heskett wrote: On Monday 30 December 2002 19:25, John Oliver wrote: [root@backup root]# su amanda -c amstatus DailySet1 bash: /root/.bashrc: Permission denied ^^^ This is a bogus report and can be ignored. It seems to have no effect on the outcome, and no one could tell me why I used to get it, but don't anymore. It's because since we're su'ing to amanda, but not using amanda's environment, it's trying to source root's .bashrc, but can't becasue /root is unreadable to non-root users... :-) /var/lib/amanda/DailySet1/amdump: No such file or directory at /usr/sbin/amstatus line 103. Also, here its apparent that amanda has finished and can no longer be queried for its current sataus because its not running anymore. Ahhh... hence the -p option. I get it now... :-) Thanks... -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Still get No index records...
Gene Heskett wrote: On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover I had this problem but solvd it when launched amrecover with the name of your config. [root@backup root]# amrecover YourBackupConfig cheers. Hery Zo RAKOTONDRAMANANA AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 backup AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-12-30) 200 Working date set to 2002-12-30. 200 Config set to DailySet1. 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? I do have index yes in amanda.conf. Why is it still unhappy? Where specifically in amanda.conf? This is supposed to be a dumptype by dumptype configuration option. That leaves the posibility that someplace in the chain of defines, its turned back off by your choice of dumptypes. There may be a dim possibility that your particular tar is fubar, what version are you useing? Minimum generally speaking is 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is usually grounds enough to replace it with the newer release. Get 1.13-25 from alpha.gnu.org.
Re: Problem with initial install of amanda on SCO openserver
On Mon, 30 Dec 2002, Josh More wrote: FAILURE AND STRANGE DUMP SUMMARY: backupmast /home RESULTS MISSING Firstly, before running amdump did you run amcheck? If yes, what do you see in /tmp/amanda? -Mitch
Re: Still get No index records...
On Mon, 30 Dec 2002, John Oliver wrote: 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? What did you use for the hostname for this client in disklist? -Mitch
