Problem with stopped backup
I seem to have a backup that is stopped, but I don't know how to read the status report on it. I have included it below. This backup started last night after midnight and seems to be still going. However, the 40.96% dumped number has stayed the same for over an hour now. Can someone help me decipher this status report. Also, if it is indeed stopped, why did it stop and how do I kill it? Thanks for any assistance. Using /usr/adm/amanda/DailySet1/amdump from Thu Oct 18 00:45:00 EDT 2001 coltrane.krjda.com:/home 1 7380096k finished (1:29:28) travis.krjda.com:/home 010647688k dumping to tape (1:29:28) SUMMARY part real estimated size size partition : 2 estimated : 2 18017165k failed : 0 0k ( 0.00%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 1 10647688k ( 59.10%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 1 7380096k 7369477k (100.14%) ( 40.96%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 1 7380096k 7369477k (100.14%) ( 40.96%) 3 dumpers idle : not-idle taper writing, tapeq: 0 network free kps: 970 holding space : 719800k (100.00%) dumper0 busy : 0:41:30 (100.00%) taper busy : 0:41:30 (100.00%) 0 dumpers busy : 0:00:00 ( 0.00%) 1 dumper busy : 0:41:30 (100.00%)not-idle: 0:41:30 (100.00%)
Re: Exclude question
Jon,
I edited my dumptypes to be the following;
# dumptypes
define dumptype root-tar {
program "GNUTAR"
comment "user partitions dumped with tar"
compress none
index yes
exclude "./var"
exclude "./dev"
record yes
priority medium
}
however, this morning I got the same message. It is still looking for
/var/log/syslog.
Anything obvious I did wrong?
Thanks.
Bill
Jon LaBadie wrote:
>On Wed, Sep 12, 2001 at 09:45:35AM -0400, Bill Delphenich wrote:
>
>>I have the following in my "disklist" file:
>>
>>exclude "./var"
>>
>>for my server. The backups usually run just fine.
>>
>>This morning, I got the following message in my mail concerning last
>>night's backup:
>>
>>?gtar: ./var/log/syslog: file changed as we read it: No such file or
>>directory
>>
>>It looks to me like amanda is trying to backup something in the /var
>>directory even though I excluded it. Am I missing something here? Why is
>>it bothering with anything under the /var directory? Ordinarily this
>>backup runs just fine.
>>
>>
>>>>End of included message <<<
>>>>
>
>Exclude's don't go into the disklist That is file systems and/or
>directories that are to be backed up. Exclude lines like you
>show go into the dumptype definition.
>
>jl
>
Exclude question
I have the following in my "disklist" file: exclude "./var" for my server. The backups usually run just fine. This morning, I got the following message in my mail concerning last night's backup: ?gtar: ./var/log/syslog: file changed as we read it: No such file or directory It looks to me like amanda is trying to backup something in the /var directory even though I excluded it. Am I missing something here? Why is it bothering with anything under the /var directory? Ordinarily this backup runs just fine. Thanks for any help.
The Endless Estimate
I have been having some problems with Amanda lately. After doing some tweaking with it yesterday, I ran it from the command prompt, using the same command I have in the cron file for the user amanda. I have it backing up itself and another server. All servers are running RH Linux, and Amanda had been working in the past. After kicking it off yesterday, it got estimates for itself right away. It then went to the other server and tried to get an estimate. When I left yesterday, it was still getting the estimate. I got in this morning and it is still getting the estimate. What's going on here? The logs don't tell me anything about a problem. Thanks for any assistance.
Lots of BUSY messages
I have been trying to get Amanda v2.4.2p2 running on RH 7.1 for some time now. It seems to be set up correctly. It was compiled from source. I have it backing itself up and another Linux server. I have 10 tapes in the cycle. Occasionally it backs everything up just right and mails me a message. However, I seem to get an awful lot of "NAK amandad busy" errors in my reports. It happens so often, I don't really have much confidence in the backups. It goes for several days without getting anything backed up at all. Sometimes it fails to back up the remote server, sometimes it fails to back itself up and sometimes they both fail. I have run through all the FAQ's etc regarding this problem and still have no joy. Are there known problems with Linux kernel 2.4.2-2 or something? I'm getting exasperated! Thank you for any assistance.
Re: Tapetype question
1.) DMEG on my Dell 4400 server gives me: Vendor: BNCHMARKModel: DLT1Rev: 3213 Type: Sequential Access 2.) I have been using a tapetype I modified from the samples, i.e: DLT length 4 mbytes filemark 2000 kbytes speed 1536 kbytes Being a DYI-kind-of-guy, I wanted to get it exactly matching my hardware, so I know its right. 3.) The command I used was: "./tapetype -f /dev/nst0 -t DELL_DLT" and variations of it. All I get is the help screen. Do I need to run amlabel and name it "DELL_DLT" first? Thanks. Bill
Tapetype question
I want to create the tapetype for the 40/80gb DLT drive that came in my Dell 4400 server. I am not sure what exactly it is, so I was just going to create my own tapetype. However, when I do "./tapetype -f /dev/nst0 -t DELL_DLT" I get errors on usage and it quits. I have tried every variation of I can think of to get it to go, but still no joy. What obvious thing am I missing here? Thanks.
Confused about multiple configurations
I am running a "DailySet" configuration five days a week as is common with AMANDA. Now I want to set up periodic manual full backups for archiving purposes. I don't want these to be scheduled. I just want to throw a tape in once a month or so and get a full-backup to store off-site. The FAQ says to set up multiple configurations to do this, but I'm not clear on how to do this. Does this mean having multiple amanda.conf files; one for my "DailySet" backups and another for my "ArchiveSet" backups, along with duplicate directory structures for each? It doesn't look like you can define more than one configuration per "amanda.conf" file. Is this documented somewhere that I haven't found yet? Is this a relatively easy thing to do, or a difficult thing to do? Thanks for any assistance.
Applying patches
I am running amanda v2.4.2 on Red Hat Linux box. It was downloaded as a tar file and compiled from there (no RPM's). Recently I got the notice about the availability of patch level 2 for this product, but I don't find any information on how to upgrade a working copy. What is the standard way to upgrade? I don't see any patches on the Patches Page to bring v2.4.2 up to v2.4.2p2. Should I download the new tar file and recompile? Will that work without breaking my running copy? Thanks for any assistance.
Remove and start over
I compiled amanda on a new RH7 server, and did the "make" and "make install" thing, but now I want to compile it again but with different options compiled in. How do I completely remove amanda and start over again with a clean slate? Thanks for any assistance.
Re: Problem with amverify
"John R. Jackson" wrote: > >However, the AMANDA VERIFY REPORT says it skipped the verificiation on > >this server because; > > > >(** Cannot do /usr/bin/gtar dumps) > > This says that GNU tar is installed in /usr/bin/gtar on the client, > but since amverify runs on the server, it is apparantly not in that same > location, so it could not run it. > > Version 2.4.2 tries to handle this better by looking for a basename match > as well as a complete match, i.e. if the basename of the version of GNU > tar on your server is "gtar", amverify would have used it. OK, that makes sense. My RH7 amanda server is running amanda v2.4.1 from the rpm's and the client server is running amanda 2.4.2 which I compiled from source. If I bring all my amandas up to v2.4.2, this should go away, right? Thanks. Bill
Problem with amverify
I am setting up a SAMBA client server to be backed by amanda, which is running on RH7. The first night I ran the backup, it seems to have gone well. The AMANDA MAIL REPORT says it backed up 1.9 GB on the /home/samba directory on the client machine in 143:02 minutes. However, the AMANDA VERIFY REPORT says it skipped the verificiation on this server because; (** Cannot do /usr/bin/gtar dumps) I don't really understand what it's having trouble with, and I don't see anything in the archives relevant to this problem. Verification of the other clients work fine. Any idea what is amiss here? Thanks for any assistance.
Backing up SAMBA
I have amanda running on a RedHat 7 server and it is now backing up several Linux client servers to a DLT drive very nicely. The next thing I need to get going is backing up my SAMBA stuff. I have SAMBA running on a Linux server, serving applications and files to our LAN of about 70 NT workstations. What is the best way to back up SAMBA stuff? Is it enough to just point my amanda server to the appropriate directories on the SAMBA server, or is there a better way? I have never been able to get the smbclient to work, so I can't get my SAMBA directories to mount into the local filesystem of the amanda server, so I hope that's not the way to do it. Thanks for any assistance.
A couple more RedHat 7 questions
OK, I got amanda running on RedHat 7; at least amcheck doesn't barf anymore . . . Question 1.) There is no "tapelist" file or "curinfo" file anywhere. Do I also need to create these by hand? I have labeled one tape so far that I will be using as a tester. Question 2.) Should I su to the "operator" user before editing crontab? I ran crontab -e yesterday as root and added an entry for a dump to be done by user "operator". It saved it, of course, under /var/spool/cron/root. Does it matter? Thanks for any assistance.
Got RH7 working!
With a lot of help from this list, especially Casile and Siavosh, I finally got Amanda working on Red Hat 7, just as it was installed with the rpm's! After much futzing around with the .amandahosts file, it turned out Red Hat's default one had been right all along. The last little gotcha I ran into was the "operator" user that had been created had not been made a member of the "disk" group, although most file ownerships were correct. . Once I took care of that little detail, everything is golden. Thanks for your help.
permission denied on amcheck
I am waging an heroic battle here trying to get amanda to run on Red Hat v7, with little success. The application was installed using the RPM's off of the CDROM. The current problem is I can't run "amcheck" as the "operator" user. I get permission denied. I can run amcheck as the root user, but then I get the dreaded "access as operator not allowed from [EMAIL PROTECTED]" I have my .amandahosts file set up in /home/operator correctly, I think. The permissions on /usr/sbin/amcheck are: -rwsr-x---1rootdisk18520Aug 22 01:34amcheck Is this right? I haven't changed any of this. All of the other am* files in /usr/sbin are owned by "operator" and group "disk". Thanks for any assistance.
