Re: Trying to backup to disk, getting "dump to tape failed, will try again"
2007-11-27 13:35:47
Okay, I figured out what my silly little problem was. Apparently, you
need to turn on amanda on your server before anything will work. It's
interesting that there isn't a useful error to point out such a basic
lack. Amcheck was happy and the logs just had connection timeout
errors. The timeout errors are certainly logical, they just encompass a
lot more than, "Hey, you, start the software!"
Anyway, thanks for all the responses. I am going to go enjoy my working
amanda config and try to forget the last several hours. :-/
Jen
Jennifer Luisi wrote:
I think I'm getting closer to the problem. There seems to be a
connection issue between my server and client. If anyone has any
input, I'd appreciate it. I've got iptables on my client set up to
accept port 10080 connections from my server, and it's obviously
talking a bit since I have logs on my client. So...?
Taking a closer look at the amdump log on my backup server, I see:
<snip>
GENERATING SCHEDULE:
--------
ENDFLUSH
DUMP [client.host] fffffeff9ffe0f /etc 20071127 13847 0 1970:1:1:0:0:0
3035 101
--------
reserving 0 out of 0 for degraded-mode dumps
driver: flush size 0
driver: start time 0.099 inparallel 4 bandwidth 3100 diskspace 0 dir
OBSOLETE datestamp 20071127 driver: drain-ends tapeq FIRST big-dumpers
ttt
driver: result time 0.099 from taper: TAPER-OK driver: dumping
[client.host]:/etc directly to tape
driver: send-cmd time 0.099 to taper: PORT-WRITE 00-00001
[client.host] fffffeff9ffe0f /etc 0 20071127
taper: try_socksize: receive buffer size is 65536
taper: stream_server: waiting for connection: 0.0.0.0.33284
driver: result time 0.099 from taper: PORT 33284
driver: send-cmd time 0.099 to dumper0: PORT-DUMP 01-00002 33284
[client.host] fffffeff9ffe0f /etc NODEVICE 0 1970:1:1:0:0:0 GNUTAR
|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;
driver: state time 0.099 free kps: 3070 space: 0 taper: writing
idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400
driver-idle: not-idle
driver: interface-state time 0.099 if : free 300 if VBEB: free 770 if
ETH0: free 1000 if LOCAL: free 1000
driver: hdisk-state time 0.099
taper: stream_accept: connection from 127.0.0.1.3328dutaper:
try_socksize: receive buffer size is 327dumper: try_socksize: send
buffer size is 65536
dumper: stream_client: connect to 10.0.82.134.53380 failed: Connection
timed out
driver: result time 189.086 from dumper0: TRY-AGAIN 01-00002 could not
connect to data port: Connection timed out
On the client-side, I found the following in my sendbackup.*.debug file:
sendbackup: debug 1 pid 30171 ruid 33 euid 33: start at Tue Nov 27
11:49:37 2007/usr/lib/amanda/sendbackup: version 2.4.4p3
parsed request as: program `GNUTAR'
disk `/etc'
device `/etc'
level 0
since 1970:1:1:0:0:0
options
`|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.000: stream_server: waiting for connection:
0.0.0.0.54035
sendbackup: time 0.000: stream_server: waiting for connection:
0.0.0.0.54036
sendbackup: time 0.000: stream_server: waiting for connection:
0.0.0.0.54037
sendbackup: time 0.000: waiting for connect on 54035, then 54036, then
54037
sendbackup: time 29.992: stream_accept: timeout after 30 seconds
sendbackup: time 29.992: timeout on data port 54035
sendbackup: time 59.984: stream_accept: timeout after 30 seconds
sendbackup: time 59.985: timeout on mesg port 54036
sendbackup: time 89.976: stream_accept: timeout after 30 seconds
sendbackup: time 89.977: timeout on index port 54037
sendbackup: time 89.977: pid 30171 finish time Tue Nov 27 11:51:07 2007
The amandad.*.debug file says:
amandad: debug 1 pid 30170 ruid 33 euid 33: start at Tue Nov 27
11:49:37 2007
amandad: version 2.4.4p3
amandad: build: VERSION="Amanda-2.4.4p3"
<snip>
--------
Amanda 2.4 REQ HANDLE 000-F03E6008 SEQ 1196180673
SECURITY USER amanda
SERVICE sendbackup
OPTIONS features=fffffeff9ffe0f;hostname=client.host;
GNUTAR /etc 0 1970:1:1:0:0:0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;
--------
amandad: time 0.000: sending ack:
----
Amanda 2.4 ACK HANDLE 000-F03E6008 SEQ 1196180673
----
amandad: time 0.002: bsd security: remote host backup.server.com user
amanda local user amanda
amandad: time 0.002: amandahosts security check passed
amandad: time 0.002: running service "/usr/lib/amanda/sendbackup"
amandad: time 0.006: sending REP packet:
----
Amanda 2.4 REP HANDLE 000-F03E6008 SEQ 1196180673
CONNECT DATA 54035 MESG 54036 INDEX 54037
OPTIONS features=fffffeff9ffe0f;
----
amandad: time 0.006: got packet:
----
Amanda 2.4 ACK HANDLE 000-F03E6008 SEQ 1196180673
----
amandad: time 0.006: pid 30170 finish time Tue Nov 27 11:49:37 2007
Thanks!!!
Jen
Jennifer Luisi wrote:
Hi there,
I'm new to Amanda and am trying to get a disk-to-disk backup going.
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log
file shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will
try again]
I've googled and read docs and how-to's to get where I am now.
Unfortunately, all the docs and how-to's get me to running amcheck
without errors and then launch into how to start a recovery process.
I guess that means that most people have no problems with amdump.
;-) I've included config info below, amanda.conf, disklist, etc.
Please take a look and let me know what silly error I've made. I'd
really appreciate it. If I've left out some pertinent info, please
tell me and I'll include it.
Thanks!!
My amanda.conf file is
org "OrgName" # your organization name for reports
dumpuser "amanda" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel
dumpcycle 14 # the number of days in the normal dump cycle
runspercycle 10 # the number of amdump runs in dumpcycle days
etimeout 55 # number of seconds per filesystem for estimates.
runtapes 1 # number of tapes to be used in a single run of amdump
tapetype HARDDISK # what kind of tape it is (see tapetypes below)
labelstr "^OrgName-[0-9][0-9]*$" # label constraint regex: all tapes
must match
tapecycle 11
tpchanger "chg-disk"
changerfile "/export/amanda/status/chg-disk-status" # status files
prefix
tapedev "file:/export/amanda/vtapes/tape1/slots"
infofile "/export/amanda/adm/BlueFrog/curinfo" # database filename
logdir "/export/amanda/adm/BlueFrog" # log directory
indexdir "/export/amanda/adm/BlueFrog/index" # index directory
define tapetype HARDDISK {
comment "Dump onto hard disk"
length 40960 mbytes
}
define dumptype global {
index yes
program "GNUTAR"
exclude list "/var/lib/amanda/exclude.gtar"
# record no
}
define dumptype hard-disk-dump {
global
comment "Back up to hard disk instead of tape using dump"
holdingdisk no
index yes
priority high
kencrypt no
program "GNUTAR"
}
define interface vbeb {
comment "10 Mbps ethernet over the vbeb"
use 800 kbps
}
And my test disklist file looks like this:
client.host /etc hard-disk-dump -1 vbeb
client.host /export/backup hard-disk-dump -1 vbeb
client.host /export/subversion hard-disk-dump -1 vbeb
client.host /export/httpd/beta-webspaces hard-disk-dump -1 vbeb
client.host /export/httpd/swc.bluefrog hard-disk-dump -1 vbeb
I have my virtual tapes set up and labeled:
[root@backuphost ~]# ls -lR /export/amanda/vtapes/ | more
/export/amanda/vtapes/:
total 4
drwxr-x--- 4 amanda disk 4096 Nov 26 10:41 tape1
/export/amanda/vtapes/tape1:
total 12
drwxr-xr-x 2 amanda disk 4096 Nov 23 13:19 data
-rw------- 1 amanda disk 11 Nov 23 13:19 info
drwxr-xr-x 12 amanda disk 4096 Nov 26 13:53 slots
/export/amanda/vtapes/tape1/data:
total 0
/export/amanda/vtapes/tape1/slots:
total 44
lrwxrwxrwx 1 amanda disk 39 Nov 26 13:53 data ->
/export/amanda/vtapes/tape1/slots/slot4
-rw------- 1 amanda disk 11 Nov 26 13:53 info
drwxr-xr-x 2 amanda disk 4096 Nov 26 12:38 slot1
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot10
drwxr-xr-x 2 amanda disk 4096 Nov 26 13:29 slot2
drwxr-xr-x 2 amanda disk 4096 Nov 26 13:51 slot3
drwxr-xr-x 2 amanda disk 4096 Nov 26 15:12 slot4
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:49 slot5
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot6
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot7
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot8
drwxr-xr-x 2 amanda disk 4096 Nov 26 11:40 slot9
Jennifer Luisi
--
-------------------------------------------------------------------
Jennifer Luisi Systems Group
jenl AT bluefrog DOT com Blue Frog
-------------------------------------------------------------------
|
Previous by Date: |
Re: Trying to backup to disk, getting "dump to tape failed, will try again", Stefan G. Weichinger |
Next by Date: |
Re: IBM 3584 and mtx?, Jean-Francois Malouin |
Previous by Thread: |
Re: Trying to backup to disk, getting "dump to tape failed, will try again", Stefan G. Weichinger |
Next by Thread: |
Re: Trying to backup to disk, getting "dump to tape failed, will try again", Stefan G. Weichinger |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|