amverify doesn't run
Hello again!, I had a successful backup run last night as shown in the log.20001128.0 file. 8-) When I run amverify It returns: Using device /dev/nst0 Waiting for device to go ready... which never happens. It sits there like that 'till I Ctrl-C it. What might be causing this? Is there an easier way to install the client piece than the whole configure/make/make install process? Randy __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Client install
Hey John, How is installing for the clients different than for the server? That is not evident in anything I've read (README, INSTALL and the entire chapter online at www.amanda.org). Do I need to do the whole ./configure, make, make install process for each client? IT seems that's massive overkill. Randy Cordell __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Re: missing result in amanda 2.4.2
--- "John R. Jackson" [EMAIL PROTECTED] wrote: I am running Linux. I have a dump 0.4b9-1 ... As I recall, that's **way** too old. ... Before I go to the work of installing it, are there good reasons to prefer dump to gnu-tar or vice versa? Oh, no. Here we go on this subject again :-). Yes, there are reasons. But for every one side A gives, side B has a counter, so it's mostly philosophical. Pick what you're comfortable with. I will throw in that GNU tar alters the last access time of every file backed up, and that's the main reason I don't use it. I typed a reply, hit a key stroke and landed back in my inbox, so if this comes across twice that's why. I made note for myself that didn't include enough data for me to be able to decipher: "Tar --atime-preserve" But I do remember this keeps tar from changing the last-access time of files as it backs them up. This doesn't look like a tar option so is it an option for the configure script of AMANDA? If so does this resolve your issue with tar? I read that the amverify is much more reliable with tar than dump. That's good enough for me. Randy Cordell Dylan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
amanda install
Hello all! I have numerous questions about amanda all leading hopefully towards making it work. The short story is that now 'amcheck' runs w/o errors but when I issue "amdump daily" it appears as if nothing happens and I get the prompt back immediately. 'daily' is the name of my config. amlabel is happy with my EXB-8500 as /dev/nst0. The progression of events was as follows: I installed amanda-2.4.2p1 as root on my TurboLinux 6.0 (WS) workstation (aka my server at home) and had a really difficult time getting anywhere with it failing at the amcheck step. I created, recreated, moved and chmod'd directories and files trying to make sense out of what appears to be a mixture of at least three standards for file locations in the README, INSTALL, /amanda-2.4.2/eamaple/amanda.conf file and the chapter from W. Curtis Preston's book "Unix Backup and Recovery" as posted at www.amanda.org. I recognize this as a common 'Linux' problem so I did the best that I could to resolve by couth and sleuth. At some point noticed that there is an amanda-2.4.2 version and it appeared as though it is no longer beta. So taking into concideration the comments about running './configure' and 'make' as user amanda and then running 'make install' as root (also found at www.amanda.org in the FAQ section), I did just that after cleaning out as much garbage from the previous install as I knew where it lived (read: the source directory and directories that I had created). Amcheck still failed and still showed brought to you by Amanda 2.4.1p1 - is this a key indicator of my problem? I fianlly was able to get amcheck to pass off my install as good. :) What follows is what I had to do to get amcheck to run successfully. I had to manually create and assign permissions for numerous files and directories including, and I hope limited to (asuming I was thorough in my note taking): /etc/amandates file, /etc/amanda/daily/amanda.conf and disklist (where amanda.conf was copied from /amanda-2.4.1p1/examples and edited, daily is the name of my configuration and disklist just includes my server's "/" dir at present), /var/amanda/curinfo and /index directories, /usr/local/var/amanda/gnutar-lists file, /home/amanda/.amandahosts, /etc/amanda/daily/tapelist file, added my user amanda to 'disks' group to access /dev/nst0 and /dev/hd*, ran /amanda-2.4.2/client-src/patch-system script to modify /etc/services and inted.conf files, added PATH=/usr/sbin:$PATH to /home/amanda/.bashrc, created /dumps/amanda, usr/lib/amanda and copied to it /usr/local/sbin/amgetconf as getconf to make amcheck happy. Now amcheck is happy. When I run "amdump daily" the prompt returns immediately and nothing further happens, including no messages or mail. Any ideas what is wrong here? And you are not allowed to select 'Randy' as the answer to that question. grin. Randy Cordell. ps: tar cvf /dev/st0 /* works fine. __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Re: Amanda reinstall issues
no /var/amanda/curinfo/ or /index/ As I said earlier, these should not exist. They should be Amanda config dependent, i.e. they should be /var/amanda/daily/curinfo and /var/amanda/daily/index. I also think that if you create the "daily" directory with permissions that allow the Amanda user (or a group it is a member of) to create entries (rwx), these two will be created for you by the first run. The location for these dirs is in amanda.conf and can be changed to anywhere I want them. Currently they are in /usr/local/var/amanda/. So I have that handled ok. I don't think Amanda should be responsible for creating /usr/local/var. What was it trying to put in there? Amanda is the only thing that uses it and it didn't exist prior to this isntall. These are the files and directories found there in /usr/local/var/amanda/: -rw--- 1 amanda backup 5141 Nov 27 21:54 amdump.1 drwxrwx--- 3 amanda backup 4096 Nov 27 21:54 curinfo/ drwxrwx--- 2 amanda backup 4096 Nov 27 21:35 gnutar-lists/ drwxrwx--- 3 amanda backup 4096 Nov 27 21:35 index/ -rw--- 1 amanda backup853 Nov 27 21:54 log.20001127.0 drwx-- 2 amanda backup 4096 Nov 27 21:54 oldlog/ I got real hung up on my first try at installing amanda because I was expecting things to go in presently existing directories and amanda is duplicating all those same directories (or expecting them) under /usr/local/ rather than off of the root (/etc/, /var/, /lib/, etc.) and so, I ended up with a mixture of locations. Now that's much clearer for me. I do see the reasoning for this from an ease of trouble shooting, upgrading and removal perspective - but I honestly don't understand the mechanics of program installs/removals enough yet to know if this is a real issue or not, throwing everything into the same locations. But one thing that has been a tad frustrating is the lack of standards, or more specifically the 'partial adherance' to standards as seen so far in my miniscule introduction to the *nix world. I plan on this being my career direction so I am interested in any changes for the better. I noted that you are making action items and you got my attention... grin. Also, I doubt most people do a "make install" on all their clients, which is where this exists. Most probably do it once on a prototypical system, then use rdist, NFS or the equivalent to the others. The next steps I have to tackle. Are you saying they just copy that /usr/local branch off to other machines? Is there nothing then that was put in /sbin or /bin etc? wow. That could be cool. Thanks again. Randy __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
