nixCraft

Hello Group - Seems like wonderful community you have here!

I have 3 fedora core servers - One hosting email using Bynari Insight server(call it bynari) One hosting an internal wiki and Samba server for windows clients (call it wiki) and a third that at the moment does nothing (call it amanda) I would like to have Amanda be my central backup server for both bynari and wiki . I have installed the server and client, configured Amanda.conf and .amadnahost on server and clients. But I still get an error whe I run amcheck - here are the results .

[root@amanda ~]# su amanda
bash-3.2$ /usr/sbni/amcheck DailySet1
bash: /usr/sbni/amcheck: No such file or directory
bash-3.2$ /usr/sbin/amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps/amanda: 11364684 KB disk space available, using 11262284 KB
Changer problem: could not read result from "/usr/lib/amanda/chg-disk"
changer problem: could not read result from "/usr/lib/amanda/chg-disk" (ex pecting a new tape)
WARNING: tapecycle (2) <= runspercycle (20).
NOTE: conf info dir /etc/amanda/DailySet1/curinfo does not exist
NOTE: it will be created on the next run.
NOTE: index dir /etc/amanda/DailySet1/index does not exist
NOTE: it will be created on the next run.
Server check took 0.184 seconds

Amanda Backup Client Hosts Check
--------------------------------
WARNING: Usage of fully qualified hostname recommended for Client localhost.
WARNING: localhost: selfcheck request failed: timeout waiting for ACK
WARNING: amanda.adsnv.com: selfcheck request failed: timeout waiting for ACK
Client check: 2 hosts checked in 30.147 seconds, 2 problems found

(brought to you by Amanda 2.5.1p3)

I don't even know where to begin as I specialist in IBM software and hardware and am at best a novice linux admin.

Suggest comments are appreciated.

ps I will be putting more disk in Amanda to allow for larger backups once I get it working

Perhaps I should provide some more Info - Please feel free to ask me for what think I need to post.

A backup target can either be a physical tape or a directory on a filesystem that is defined as a virtual tape (vtapes is a method of using disk media to emulate tape device. Before either type of target can be accessed it must be labeled using AMANDA's amlabel command. Compression must be turned off, and the blocksize set to 0 before labelling a tape. The label must be a valid label as defined by the "labelstr" option in amanda.conf. The mt and amlabel commands must be executed as the amanda user.


Have you followed installation steps mentioned at following redhat location?
Server Config - redhat.com | Red Hat Support

Client config - redhat.com | Red Hat Support

How do I configure virtual tapes for an AMANDA backup server? : redhat.com | Red Hat Support

I always use above doc on CentOS / Fedora and RHEL server. Let me know the status.

__________________
Rocky Jr.
You may have my body & soul, but you will never touch my pride!

If you have knowledge, let others light their candles at it.

Certified to work on HP-UX / Sun Solaris / RedHat

Thanks for the Response I have taking a Glance at the sites you suggested and I originally used a different site that appears to have left out many important details - I will follow the configuration guidelines suggested from these site and let you know my results.

Thanks Again!

Fedora is beta version for Red Hat and CentOS. Fedora is good choice for Desktop and laptop. It has cutting edge software and technology. For production server use CentOS (free red hat clone) or RHEL 5.x itself. Some people also prefer Debian over rpm based distro.

Just my 2 cents

__________________
Friends - v-nessa - missyAdmin

Thanks for the advice I will take that into consideration.

Any updates on your problem?

__________________
Rocky Jr.
You may have my body & soul, but you will never touch my pride!

If you have knowledge, let others light their candles at it.

Certified to work on HP-UX / Sun Solaris / RedHat

It's going Well-

Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps/amanda: 11371200 KB disk space available, using 11268800 KB
Changer problem: could not read result from "/usr/lib/amanda/chg-disk"
changer problem: could not read result from "/usr/lib/amanda/chg-disk" (expecting a new tape)
NOTE: conf info dir /etc/amanda/Backup1/curinfo does not exist
NOTE: it will be created on the next run.
NOTE: index dir /etc/amanda/Backup1/index does not exist
NOTE: it will be created on the next run.
Server check took 0.043 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.100 seconds, 0 problems found

(brought to you by Amanda 2.5.1p3)


I haven't gotten all the bugs worked out yet

At the moment I only have it configured to backup the /home directory of one client and the amcheck is showing no problems but as you can see it is not error free

Changer problem: could not read result from "/usr/lib/amanda/chg-disk"

I also see this error when I try to use the amlabel command so I am going through the configuration again to see what I may have missed

could not load slot "current":could not read result from "/usr/lib/amanda/chg-disk"

Is the actaull error I get when using the amlabel command I think it is being caused by the way I have it dump to disk instead of tape ... I think... I am still working it but I feel confident that once I get this final error resolved I can start using amanda.

I also downloaded CentOS to evalute per Sweta advice. although I don't intend on replacing Fedora anytime soon.