+++ "John R. Jackson" <[EMAIL PROTECTED]>
+++ >==== WARNING: skipping tape test because amdump or amflush seem to be running;
+++ >==== WARNING: if they are not, you must run amcleanup.
+++
+++ This says there either an amdump/amflush is still running (you might
+++ check with "ps -fu <amanda-user>") or the previous run aborted and left
+++ stuff laying around (which is unusual, but can happen). As it says,
+++ if you don't find any evidence of things still active, run amcleanup to
+++ get it going (and run amcheck again to confirm).
John, Thanks..that helped...
The backups had some success last night....
Actually, the most important part, the production application data was backed up
+++ >==== WARNING: eprod: selfcheck request timed out. Host down?
+++
+++ This is, without doubt, the number 1 problem that comes up here, so
+++ you're in good company. The FAQ at www.amanda.org has a number of items
+++ to check, so rather than going through that yet again here, give them a
+++ try and if it still won't work, post back with what you tried and what
+++ the results were.
I went through the FAQ section on amcheck.
There are no error messages in /var/adm/messages on either host.
BTW, three of the "hostnames" are actually virtual IP addresses,
since this is an HA cluster.
I cleaned /tmp/amanda on the backup host.
I did not think to clean it on the other hosts. I don't know if it matters.
/tmp/amcheck is writable on all hosts.
I'll include files I think are relevant to my problem, with comments/questions.
==== _root@s20_[/var/backup]:> cat log.amcheck
==== Amanda Tape Server Host Check
==== -----------------------------
==== /var/dumps/amanda: 804746 KB disk space available, that's plenty.
==== ERROR: cannot overwrite active tape edgd129.
==== (expecting tape DailySet111 or a new tape)
==== NOTE: skipping tape-writable test.
==== Server check took 5.334 seconds.
====
==== Amanda Backup Client Hosts Check
==== --------------------------------
==== WARNING: eprod: selfcheck request timed out. Host down?
==== Client check: 6 hosts checked in 30.283 seconds, 1 problem found.
====
==== (brought to you by Amanda 2.4.1p1)
==== _root@s20_[/var/backup]:>
There are 6 hosts. 3 of them are IP aliases on one of the hosts,
so four addresses are really the same host. I don't know if that matters.
==== _root@s20_[/var/backup]:> cat disklist
==== ##### VCS DISKS ######
==== prod /dg/dghome nocomp-root
==== qa1 /dg1/qa1 nocomp-user
==== qa2 /dg1/qa2 nocomp-user
==== ##### ETEST ##########
==== etest /dev/vx/rdsk/rootvol nocomp-root
==== etest /var nocomp-root
==== etest /opt nocomp-root
==== etest /dg nocomp-root
==== etest /dg1 nocomp-root
==== ####### EPROD ##########
==== eprod /dev/vx/rdsk/rootvol nocomp-root
==== eprod /var nocomp-root
==== eprod /opt nocomp-root
==== eprod /dg nocomp-root
==== eprod /dg1 nocomp-root
==== #### S20 ###############
==== s20 /dev/rdsk/c0t3d0s0 nocomp-root -1
==== s20 /var nocomp-root -1
==== s20 /export/home nocomp-root -1
s20 is the backup host. prod, qa1, and qa2 are IP aliases on eprod
==== _root@s20_[/var/backup]:> cat amverify.29
==== Defects file is /tmp/amverify.5685/defects
==== amverify csd
==== Thu Mar 29 04:06:02 EST 2001
====
==== Using device /dev/rmt/0bn
==== Volume edgd0329, Date 20010329
==== Checked etest._var.20010329.0
==== Checked etest._dg.20010329.0
==== Checked s20._dev_rdsk_c0t3d0s0.20010329.0
==== Checked etest._opt.20010329.0
==== Checked etest._dev_vx_rdsk_rootvol.20010329.0
==== Checked etest._dg1.20010329.0
==== Skipped prod._dg_dghome.20010329.0 (** Cannot do /usr/sbin/vxdump dumps)
==== End-of-Tape detected.
I notice that s20 /var and and /export/home are not backed up,
and all eprod system disks were not backed up.
Is there a way to get more details on what is failing with eprod?
Is it trying to rsh, or some remote dump?
BTW, I do notice that some of the disks in the disk list are
specified wrong, but I don't want to make too many changes at once.
Thanks everyone
Seth
