Re: No tape
I think this is pretty good explanation of what needs to be done: http://amanda.sourceforge.net/cgi-bin/fom?auth=ckd2128107166efile=191 Laas Toom On Wed, 2 Apr 2003 [EMAIL PROTECTED] wrote: On Wed, 2 Apr 2003, Audrey Brochet wrote: Yes you must run a version posterior of amanda-2.4.3 and use the driver file: in amanda.conf instead of tape device Is it possible to use Amanda with only backup on hard disk but not on tape ?? How does this ?? Thank you - Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: backup plan
On Mon, 31 Mar 2003, Lucia Mazzoni wrote: Hi everyone, I need a little help to tune a backup plan with Amanda. In my company we were used, before Amanda, to have this plan for our main servers (each one with a dedicated tape device): - a full backup was made every day from monday to friday but 1) from monday to thursday tapes were always the same, that is, every week they were overwritten 2) on friday we had 4 tapes to save a full-backup per week for one month. After 4 weeks we selected the oldest tape, put it in a safe place (against fire) and took a new one for the backup job. We kept 1 tape per month for 6 months and then one every 3 or 6 months. Now I'd like to maintain the same plan with Amanda and my problem is with Friday tapes that I want to extract and put away. I put a tapecycle of 4 tapes on Friday configuration but: - How can I maintain the possibility of restore data from the extracted tapes? Changing labels every time? Did i get the plan correctly - after a month the oldest Friday dump of one tape goest to archive and a new one replaces it? if this is the case, i think, that you could have the Friday's name-regexp set to acomodate a lot of numbers (e.g. Friday[0-9][0-9][0-9] for 10-years of archive - 120 tapes total, i.e. Friday001, Friday076, etc), so that amanda has enough name-space. after a month when the archved tape is selected, run command: amadmin config no-reuse tapelabel which tell's amanda not to reuse this tape anymore and to expect a fresh tape when this tape's turn comes (i hope that amanda labels the new tape on the fly, but i wouln'd be sure). This should keep the data located on the tape still indexed in database and therefore restorable via amrecover. another way is to just replace the old tape with new one by simply amlabeling new one with -f option. Note that this way you no longer can amrecover from this tape, but have to amrestore instead (this means that you have to extract whole image from the tape and restore it and only then you can pick the files you want). Laas Toom
Re: Problem with amrecover
If i am not mistaken, then .amandahosts must contain all of the users machines that need access to that machine. So edit the .amandahosts file on the BACKUP server and add lines to allow you to access from the host recover-host with user root: recover-host root recover-host.domain root 192.168.0.xx root (added all of the possible ways just to be sure that you get what you want (it depends on amanda and machines conf, which of the lines gets to be used, so i have all of them in my .amandahosts file) Laas Toom On Fri, 28 Mar 2003, Bartho Saaiman wrote: Hi All :) I am trying to restore from a tape using amrecover. If I use amrecover DailyBackup it says: AMRECOVER Version 2.4.2p2. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused If I use the -s backup and/or -t backup I also get the same: AMRECOVER Version 2.4.2p2. Contacting server on backup ... amrecover: cannot connect to backup: Connection refused I previously had a similar problem and rectified this by editing the /var/lib/amanda/.amandahosts and added localhost root to the file. Tried this as I am running amrecover as root but still could not fix it. Any suggestions on what I am missing?? -- # Bartho Saaiman # Network Administrator # Stellenbosch Automotive Engineering # Tel :: 27 21 882 8820 x 215 # Email :: bartho @ cae.co.za
Re: 'not an Amanda tape' after FreeBSD upgrade
I have the same problem with my amanda 2.4.3 (FreeBSD 4.7) I upgraded my FreeBSD ports collection and to upgrade KDE 3.0 - 3.1 and didn't think of this as a major upgrade (that would affect my systems stability) and therefore have no numbers or anything to bring here for information. But come to think of it, exactly from the point when i upgraded, i'm getting these messages. At first i thought that my one of my tapes is buggy and erased it before relabeling and running amflush. Now second one failed. That made me curious... i was firightened that all of my tapes are ruined (by some magnetic smth or what ever) as they are all in one place. After flushing this tape i put in next one and ran amcheck (i didn't think of this as a sticky problem in the first place and hoped only one of my tapes was problematic therefore didn't precheck previous tapes). Amcheck ran fine and without any errors... i'll find out tomorrow, if amdump also has no errors. Also i can restore from the tape written before upgrade (at least when using dummy hostname amrestore lists all files, I did not try actual restore) If the problem persists, i dig further more into it, so far this is ment as information that this problem has occured elsewere too. Laas Toom Now i put a next tape in and run am On Thu, 27 Mar 2003, Toomas Aas wrote: Hello! My Amanda server is running 2.4.3b4. Three days ago I upgraded the operating system from FreeBSD 4.7-RELEASE-p6 to 4.7-RELEASE-p9. This is really just some security patches to sendmail, libc and openssl. Since the upgrade Amanda thinks that all the backup tapes that were written before the upgrade are not Amanda tapes. After I re-label the tape, Amanda agrees to write the backup to it and also I can successfully amrestore it later. But it seems that, should the need arise to restore from a pre-upgrade tape, I would be in trouble because those tapes are 'not Amanda tapes'. I suppose I could still read the dump images with dd, though? Over the last couple of years I've done many OS upgrades on this Amanda server and this is the first time I see such problem. Has anyone else seen it? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * It's always darkest right before you step on the cat.
Re: ccd and amanda
On Mon, 24 Mar 2003, Joshua Baker-LePain wrote: On Mon, 24 Mar 2003 at 12:19pm, Laas Toom wrote Sorry for excluding such a vital info.. Here it is: disklist: ohto/usr/database nocomp-high where 'ohto' is the name of the machine. There was no changes in this file. Amanda report: ohto /usr/database lev 0 FAILED [disk /usr/database offline on ohto?] Are the permissions on the new device (/dev/ccd3a) the same as on the the old one (/dev/ccd0a)? No, they weren't, but after i changed them to be the same, i still get the error. Laas Toom
Re: ccd and amanda
Sorry for excluding such a vital info.. Here it is: disklist: ohto/usr/database nocomp-high where 'ohto' is the name of the machine. There was no changes in this file. Amanda report: ohto /usr/database lev 0 FAILED [disk /usr/database offline on ohto?] And CCD is some kind of simple software RAID system (similar to Vinum, but with less features and simpler). Mine is configured to use 6 devices (SCSI partitions) as one big device. Laas Toom On Fri, 21 Mar 2003, Jon LaBadie wrote: On Fri, Mar 21, 2003 at 12:34:14PM +0200, Laas Toom wrote: Hi! I ran out of space on one of my ccd filesystems and therefore configured it to use other devices for free space... this seems to be correct (the system is up and running), but since the change amanda fails to back up the data on the ccd. afaik everything is the same, except the mountingpoint of the filesystem, as described in /etc/fstab: /dev/ccd0a /usr/database ufs rw 1 1 there used to be: /dev/ccd3a /usr/database ufs rw 1 1 Can anyone give me any pointers as of where to start looking for mistake? What is specified in the disklist? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
ccd and amanda
Hi! I ran out of space on one of my ccd filesystems and therefore configured it to use other devices for free space... this seems to be correct (the system is up and running), but since the change amanda fails to back up the data on the ccd. afaik everything is the same, except the mountingpoint of the filesystem, as described in /etc/fstab: /dev/ccd0a /usr/database ufs rw 1 1 there used to be: /dev/ccd3a /usr/database ufs rw 1 1 Can anyone give me any pointers as of where to start looking for mistake? Laas
re: results missing
Hello again. i accidently deleted the previous answer to my question and therefore did a little research myself, as i forgot what conf files you asked for. The conclusion is that i found out my inetd.conf was not configured correctly to run amanda client on the server itself. once i restored old inetd.conf also, all problems disappeared. So, another reason for RESULTS MISSING has popped up. Laas Toom
Re: recovery problme using amrestore
On Mon, 17 Mar 2003, Jon LaBadie wrote: On Mon, Mar 17, 2003 at 10:26:14AM +0530, T. Bhaskar Reddy wrote: Hi there, I am using amanda 2.4.4. Using amanda i have dumped a directory on localhost. While i am trying restore it displays the following message amrestore: 0: restoring localhost._home_amanda_QA.20030315.0 the commanda i executed is /usr/local/sbin/amrestore 1.localhost._home_amanda_QA.0 afaik this is all correct. Try: # file restored_filename (where restored_filename is the name of the file that is created during the first command.) this should tell you the type of the dump. and from that you can figure out the command, to complete the restore. (That is wether to use restore or tar). Amanda can dump filesystems with either 'dump' or 'tar' (dependig on your conf). the filename looks the same, because it reflects only the filesystem name, dumpdate and dumplevel. (My amanda.conf says it uses 'dump' for 'always-full' dumptype.) if 'file' says, it is tar archive, then use: # tar xvf restored_filename and if file says it is dump archive (or smth), use: # restore restored_filename NOTE: Both of these commands should extract the contents to the working directory (therefore it is wise to do it in an empty directory or at the root of the filesystem that is being restored). See also: amrecover - this is interactive util to recover single files from dumps (everithing is done automatically, you only have to load tapes - so in your case you only have to hit enter or smth) -- laaz
results missing
Hello, I use amanda to back up my whole site: freebsd workstations as well as windows samba shares. recently my backup server chrashed and i had to reinstall the operatingsystem (in the way upgrading it from freebsd 4.6 to 4.7). After what i copied amanda config files to the locations they were before crash (the index files survived). Now amanda backs up only the freebsd workstations, but for all samba shares amanda says: RESULTS MISSING. What is the problem? How can i eliminate it? The Amanda Faq-o-matic did not help, because i know the system worked before, so i do not need to make any alters to my filesystems or catalog tree. Another strange thing happened when i moved one of my freebsd servers filesystems from a ccd too small to a bigger ccd device (everything is the same, exept the /etc/fstab row that mounts the filesystem). Now amanda says the disk is offline. Thanks in advance, Laas Toom
