Re: Amrecover Issue in 3.4

2016-10-31 Thread Steven Backus 
Debra S Baddorf  wrote to me:

> When somebody in charge finally reads your notes, I'm sure
> they'll agree.

Not sure if that's what's slowing down amrecover but the 3.4
version is much slower than the 3.3.9 one I was using.  Maybe that
problem will go away when all my backups are done with 3.4.

> I've never seen those numbers. (I'm only at 3.3.8)   

There seems to be no auth = bsd (only auth = bsdtcp) in 3.4 so be
prepared to change that if you decide to upgrade.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: Amrecover Issue in 3.4

2016-10-29 Thread Steven Backus 
These numbers slow things down and don't provide information I
need.  An option to turn them off seems appropriate.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: Amrecover Issue in 3.4

2016-10-28 Thread Steven Backus 
The amrecover prompt returned at 595007296 kb, after 3 hours.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: Amrecover Issue in 3.4

2016-10-28 Thread Steven Backus 
On a test restore the numbers got to 67971072 kb before the file
restored, it took 20 minutes.  My concern is after the file
restored the numbers continued to grow without ending.  Prior
versions eventually gave me the amrecover prompt back.  Having to
^C out each time would be a pain.  This is an LTO6 drive with
e/sata interface.

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Amrecover Issue in 3.4

2016-10-28 Thread Steven Backus 
I upgraded to 3.4 and found amrecover to be quite a bit slower.
Perhaps someone thinks we need to watch it read the tapes.  Is
there some way to turn off these numbers?

Extracting files using tape drive /dev/changer on host serendipity.med.utah.edu.
Load tape gen2011 now
Continue [?/Y/n/s/d]? 
Restoring files into directory /tmp
All existing files in /tmp can be deleted
Continue [?/Y/n]? 

411840 kb 
435424 kb
880064 kb 
901248 kb
 (30 minutes or more of this)
./users/backus/.cshrc  <--file I asked to be restored
69142720 kb 
69251904 kb
70801632 kb 
 (an hour or so of this)
385915232 kb
38632 kb
(still going...)

Steve
-- 
Steven J. BackusComputer Systems Manager
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: Amrecover issue...

2009-01-05 Thread Dustin J. Mitchell 
On Fri, Jan 2, 2009 at 4:59 AM, Christiaan de Vries ch...@baxter-fx.com wrote:
 Hello again,

 Please find all the requested info, I am lost!

The amanda-auth(7) manpage may help to straighten all of this out.  See
  http://wiki.zmanda.com/man/amanda-auth.7.html

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com

Re: Amrecover issue...

2009-01-02 Thread Christiaan de Vries 

Hello again,

Please find all the requested info, I am lost!

r...@dub-amanda1:~# cat /etc/xinetd.d/amanda
=
# default: on
#
# description: Amanda services for Amanda server
#
service amanda
{
   only_from   = 10.100.100.0/24
   disable = no
   socket_type = dgram
   protocol= udp
   wait= yes
   user= backup
   group   = backup
   groups  = yes
   server  = /usr/lib/amanda/amandad
   server_args = -auth=bsd amdump amindexd amidxtaped
}
service amandaidx
{
   socket_type = stream
   protocol= tcp
   wait= no
   user= backup
   group   = backup
   groups  = yes
   server  = /usr/lib/amanda/amindexd
   disable = no
}
service amidxtape
{
   socket_type = stream
   protocol= tcp
   wait= no
   user= backup
   group   = backup
   groups  = yes
   server  = /usr/lib/amanda/amidxtaped
   disable = no
}
r...@dub-amanda1:~#

r...@dub-amanda1:~# cat 
/var/log/amanda/amandad/amandad.20081229174344.debug

=
amandad: debug 1 pid 1414 ruid 34 euid 34: start at Mon Dec 29 17:43:44 2008
Could not open conf file /etc/amanda/amanda-client.conf: No such file 
or directory

amandad: time 0.000: security_getdriver(name=bsd) returns 0xb7f092e0
amandad: version 2.5.2p1
amandad: time 0.000: build: VERSION=Amanda-2.5.2p1
amandad: time 0.000:BUILT_DATE=Fri Nov 9 01:06:28 GMT 2007
amandad: time 0.000:BUILT_MACH=Linux palmer 2.6.15.7 #1 SMP Thu 
Sep 7 19:42:20 UTC 2006 i686 GNU/Linux

amandad: time 0.000:CC=gcc
amandad: time 0.000:CONFIGURE_COMMAND='./configure' 
'--prefix=/usr' '--bindir=/usr/sbin' '--mandir=/usr/share/man' 
'--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' 
'--localstatedir=/var/lib' 
'--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' 
'--with-index-server=localhost' '--with-user=backup' 
'--with-group=backup' '--with-bsd-security' '--with-amandahosts' 
'--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/log/amanda' 
'--with-dumperdir=/usr/lib/amanda/dumper.d' 
'--with-tcpportrange=5,50100' '--with-udpportrange=840,860' 
'--with-maxtapeblocksize=256' '--with-ssh-security'

amandad: time 0.000: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad: time 0.000:libexecdir=/usr/lib/amanda 
mandir=/usr/share/man

amandad: time 0.000:AMANDA_TMPDIR=/tmp/amanda
amandad: time 0.000:AMANDA_DBGDIR=/var/log/amanda 
CONFIG_DIR=/etc/amanda
amandad: time 0.000:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ 
DUMP=/sbin/dump
amandad: time 0.000:RESTORE=/sbin/restore VDUMP=UNDEF 
VRESTORE=UNDEF
amandad: time 0.000:XFSDUMP=/sbin/xfsdump 
XFSRESTORE=/sbin/xfsrestore

amandad: time 0.000:VXDUMP=UNDEF VXRESTORE=UNDEF
amandad: time 0.000:SAMBA_CLIENT=/usr/bin/smbclient 
GNUTAR=/bin/tar
amandad: time 0.000:COMPRESS_PATH=/bin/gzip 
UNCOMPRESS_PATH=/bin/gzip

amandad: time 0.000:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
amandad: time 0.000:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: time 0.000: defs:  DEFAULT_SERVER=localhost 
DEFAULT_CONFIG=DailySet1
amandad: time 0.000:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP 
NEED_STRSTR
amandad: time 0.000:HAVE_SYSVSHM LOCKING=POSIX_FCNTL 
SETPGRP_VOID DEBUG_CODE
amandad: time 0.000:AMANDA_DEBUG_DAYS=4 BSD_SECURITY 
RSH_SECURITY USE_AMANDAHOSTS

amandad: time 0.000:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad: time 0.000:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad: time 0.000:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: dgram_recv(dgram=0xb7f0b284, timeout=0, 
fromaddr=0xb7f1b270)

amandad: time 0.000: (sockaddr_in *)0xb7f1b270 = { 2, 858, 10.100.100.160 }
amandad: time 0.000: security_handleinit(handle=0x80529a0, 
driver=0xb7f092e0 (BSD))

amandad: time 0.001: accept recv REQ pkt:

SERVICE amindexd
OPTIONS features=9ffe00;auth=bsd;

amandad: time 0.001: creating new service: amindexd
OPTIONS features=9ffe00;auth=bsd;

amandad: time 0.002: sending ACK pkt:


amandad: time 0.002: dgram_send_addr(addr=0x80529c0, dgram=0xb7f0b284)
amandad: time 0.002: (sockaddr_in *)0x80529c0 = { 2, 858, 10.100.100.160 }
amandad: time 0.002: dgram_send_addr: 0xb7f0b284-socket = 0
amandad: time 0.004: security_streaminit(stream=0x8063010, 
driver=0xb7f092e0 (BSD))

amandad: time 0.004: try_socksize: send buffer size is 65536
amandad: time 0.004: try_socksize: receive buffer size is 65536
amandad: time 0.005: bind_portrange2: Try  port 50037: Available   - Success
amandad: time 0.005: stream_server:

Re: Amrecover issue...

2008-12-30 Thread Christiaan de Vries 

Hello Jean-Louis,

File Permissions:
==
bac...@dub-amanda1:~$ ls -al /usr/lib/amanda/amidxtaped
-rwxr-xr-x 1 root root 16248 2007-11-09 01:08 /usr/lib/amanda/amidxtaped

Xinetd.d conf:

r...@dub-amanda1:/etc/xinetd.d# cat /etc/xinetd.d/amidxtape
#default: on
# description: The amanda tape service
service amidxtape
{
#only_from= Amanda client list
   socket_type= stream
   protocol= tcp
   wait= no
   user= backup
   group= backup
   groups= yes
   server= /usr/lib/amanda/amidxtaped
   server_args= -auth=bsd amdump amindexd amidxtaped
   disable= no
}

Socket:

r...@dub-amanda1:/etc/xinetd.d# netstat -an | grep 10083
tcp0  0 0.0.0.0:10083   0.0.0.0:*   
LISTEN



FYI: I have tried changing the file ownership to the backup user, but to 
no avail... I also tried to start the amixdtaped deamon with root, also 
no change, still the same error:


amrecover - can't talk to tape server: NAK: execute access to 
/usr/lib/amanda/amidxtaped denied


Kind regards again,
Christiaan de Vries

(Btw, where would I set the 'sethost' and 'settape' variables on the 
client machine permanently?)


Jean-Louis Martineau wrote:

Christiaan de Vries wrote:

Thanks for that Jean-Louis! That helped... !

Getting a bit closer to completion again. FYI: I am running the 
client now, and after some configuration issues (such as setting 
setdisk and sethost) I can finally list the back upped files on the 
server from a client connection


Unfortunately, when I try to extract the files, I receive the 
following error:

=
amrecover add SweetSweetKisses_Final.mov
Added file /Documents/SweetSweetKisses_Final.mov
amrecover extract

Extracting files using tape drive changer on host localhost.
The following tapes are needed: DailySet1-13

Restoring files into directory /var/log/amanda/client/DailySet1
Continue [?/Y/n]? y

Extracting files using tape drive changer on host localhost.
Load tape DailySet1-13 now
Continue [?/Y/n/s/t]? y
amrecover - can't talk to tape server: NAK: execute access to 
/usr/lib/amanda/amidxtaped denied

amrecover

Why amandad can't execute? What is your xinetd config? What is the user?
What is the permission on /usr/lib/amanda/amidxtaped?








Jean-Louis

Re: Amrecover issue...

2008-12-30 Thread Jean-Louis Martineau 

Christiaan de Vries wrote:

Hello Jean-Louis,

File Permissions:
==
bac...@dub-amanda1:~$ ls -al /usr/lib/amanda/amidxtaped
-rwxr-xr-x 1 root root 16248 2007-11-09 01:08 /usr/lib/amanda/amidxtaped

Xinetd.d conf:

r...@dub-amanda1:/etc/xinetd.d# cat /etc/xinetd.d/amidxtape
#default: on
# description: The amanda tape service
service amidxtape
{
#only_from= Amanda client list
   socket_type= stream
   protocol= tcp
   wait= no
   user= backup
   group= backup
   groups= yes
   server= /usr/lib/amanda/amidxtaped
   server_args= -auth=bsd amdump amindexd amidxtaped
   disable= no
}

xinetd amindexd and amidxtaped are not use, you should disable them if 
you don't have older client.

Post /etc/xinetd.d/amanda
Post the amandad.*.debug file
Do /usr/lib/amanda/amidxtaped have the same permission as 
/usr/lib/amanda/amindexd?

Socket:

r...@dub-amanda1:/etc/xinetd.d# netstat -an | grep 10083
tcp0  0 0.0.0.0:10083   0.0.0.0:*   
LISTEN   

FYI: I have tried changing the file ownership to the backup user, but 
to no avail... I also tried to start the amixdtaped deamon with root, 
also no change, still the same error:


amrecover - can't talk to tape server: NAK: execute access to 
/usr/lib/amanda/amidxtaped denied


Kind regards again,
Christiaan de Vries

(Btw, where would I set the 'sethost' and 'settape' variables on the 
client machine permanently?)

Either when you configure amanda or in the amanda-client.conf file.

Jean-Louis

Re: Amrecover issue...

2008-12-29 Thread Jean-Louis Martineau 

Christiaan de Vries wrote:

Hello all,

(After quite some time spent on initial configuration issues...)

It seems the dump works successfully, but when I try an amrecover from 
the client, I get the following error:

=
r...@chris-desktop:~# amrecover -s 10.100.100.150
AMRECOVER Version 2.5.2p1. Contacting server on 10.100.100.150 ...
NAK: user root from chris-desktop is not allowed to execute the 
service amindexd: Please add amindexd amidxtaped to the line in 
/var/backups/.amandahosts on the client
The message is not 100% correct, for amrecover, the line must be added 
to the .amandahosts on the server.

Add the following to the .amandahosts on the server:
 chris-desktop backup amindexd amidxtaped
The message is fixed in 2.6.1

Jean-Louis


My .amandahosts file contains:
=
r...@chris-desktop:~# cat /var/backups/.amandahosts
localhost root amindexd amidxtaped
localhost backup amdump
chris-desktop root amindexd amidxtaped
chris-desktop backup imindexd amidxtaped

The amrecover debug output:
=
amrecover: debug 1 pid 11618 ruid 0 euid 0: start at Mon Dec 29 
13:37:01 2008
Could not open conf file /etc/amanda/amanda-client.conf: No such 
file or directory
Could not open conf file /etc/amanda/DailySet1/amanda-client.conf: 
No such file or directory
amrecover: debug 1 pid 11618 ruid 0 euid 0: rename at Mon Dec 29 
13:37:01 2008

amrecover: time 0.000: security_getdriver(name=bsd) returns 0xb8033c00
amrecover: time 0.000: security_handleinit(handle=0x8c7ced0, 
driver=0xb8033c00 (BSD))
amrecover: time 0.001: bind_portrange2: Try  port 855: Available   - 
Success

amrecover: time 0.001: dgram_bind: socket 3 bound to ::.855
amrecover: time 0.001: dgram_send_addr(addr=0x8c7cef0, dgram=0xb8045a84)
amrecover: time 0.001: (sockaddr_in6 *)0x8c7cef0 = { 10, 10080, 
:::10.100.100.150 }

amrecover: time 0.001: dgram_send_addr: 0xb8045a84-socket = 3
amrecover: time 0.006: dgram_recv(dgram=0xb8045a84, timeout=0, 
fromaddr=0xb8055a70)
amrecover: time 0.007: (sockaddr_in6 *)0xb8055a70 = { 10, 10080, 
:::10.100.100.150 }
amrecover: time 0.007: security_close(handle=0x8c7ced0, 
driver=0xb8033c00 (BSD))


FYI: When I run a amcheck -c DailySet1 on the server, I receive the 
following output:

=
Amanda Backup Client Hosts Check

ERROR: NAK 10.100.100.160: user backup from 
dub-amanda1.dublinoffice.bfx is not allowed to execute the service 
noop: Please add amdump to the line in /var/backups/.amandahosts on 
the client

Client check: 1 host checked in 10.003 seconds, 1 problem found

(brought to you by Amanda 2.5.2p1)

Anybody have a clue/tips?

After the server gave me that pointer (add amdump to the .amandahosts 
file), the contents now look as follows:

=
r...@chris-desktop:~# cat  /var/backups/.amandahosts localhost root 
amindexd amidxtaped amdump

localhost backup amdump
chris-desktop root amindexd amidxtaped amdump
chris-desktop backup imindexd amidxtaped


The message clearly state that it is the host 
'dub-amanda1.dublinoffice.bfx' that try to connect, .amandahosts must be:

 dub-amanda1.dublinoffice.bfx backup amdump

Re: amrecover issue

2007-05-03 Thread anthonyh 

Hi Guys,settape x:/backup/amanda/dumps/tape01 

Thank You for replying this mail. Well actually i'm a bit confused with the
way the amanda recovers the data.

Is it true that the host in the command settape
host:file:/backup/amanda/dumps/tape01 refers to the amanda tape server? 

Newbie here guys.

Regards,
Anthony


Olivier Nicole wrote:
 
 Hi,
 
 Currently i'm having some issue with the amrecover. Whenever i tried
 to execute the amrecover it executed properly but till i started to
 extract the data it stated there Can't Talk to Tape Server
 
 I would try in two directions:
 
 1) try to amrecover on the server itself, to some temporary directory
 
 2) check the firewall on your server
 
 
 best regards,
 
 Olivier
 
 

-- 
View this message in context: 
http://www.nabble.com/amrecover-issue-tf3669327.html#a10309363
Sent from the Amanda - Users mailing list archive at Nabble.com.

Re: amrecover issue

2007-05-03 Thread anthonyh 
:  [EMAIL PROTECTED]
 ***
 * I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
 * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
 * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
 * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
 * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
 * ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
 ***
 
 
 

-- 
View this message in context: 
http://www.nabble.com/amrecover-issue-tf3669327.html#a10309489
Sent from the Amanda - Users mailing list archive at Nabble.com.

Re: amrecover issue

2007-05-03 Thread dustin 
On Thu, May 03, 2007 at 10:18:34AM -0700, anthonyh wrote:
 
 Hi Guys,settape x:/backup/amanda/dumps/tape01 
 
 Thank You for replying this mail. Well actually i'm a bit confused with the
 way the amanda recovers the data.
 
 Is it true that the host in the command settape
 host:file:/backup/amanda/dumps/tape01 refers to the amanda tape server? 
 
 Newbie here guys.

Yes -- that's correct.  If you're on the tape server itself, you should
use e.g.,

  localhost:file:/backup/amanda/dumps/tape01

Dustin

-- 
Dustin J. Mitchell
Storage Software Engineer, Zmanda, Inc.
http://www.zmanda.com/

Re: amrecover issue

2007-05-03 Thread anthonyh 

Hi,

I'm abit confused in this part because as far as i know the amanda service
is using udp packet and the amindexd/amidxtaped are using tcp. can
everything be fitted into one context that primarily stating that its using
udp protocol?


/etc/xinit.d/amanda
 service amanda
 {
only_from   = x.com y.com
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group   = disk
groups  = yes
server  = /usr/local/libexec/amandad
server_args = -auth=bsd amdump amindexd amidxtaped 
disable = no
} 
 

Thank you guys. Newbie here ...


Regards,
Anthony



Jean-Louis Martineau-2 wrote:
 
 Check amrecover and amandad debug files.
 
 anthonyh wrote:
 The following are some of my config files
 /etc/xinit.d/amanda
 service amanda
 {
only_from   = x.com y.com
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group   = disk
groups  = yes
server  = /usr/local/libexec/amandad
server_args = -auth=bsd amdump amindexd
disable = no 
 }
   
 You forgot amidxtaped
 server_args = -auth=bsd amdump amindexd amidxtaped
 You must also add an entry in .amandahosts
 
 The following 2 services are not needed if all your client are 2.5.1.
 /etc/xinit.d/amandaidx
 service amandaidx
 {   
 only_from   = x.com y.com
 socket_type = stream
 protocol= tcp
 wait= no
 user= amanda
 group   = disk
 groups  = yes
 server  = /usr/local/libexec/amindexd 
 server_args = -auth=bsd amdump amindexd
 disable = no
 }

 service amidxtape
 {   
 only_from   = x.com y.com
 socket_type = stream
 protocol= tcp
 wait= no
 user= amanda
 group   = disk
 groups  = yes
 server  = /usr/local/libexec/amidxtaped 
 server_args = -auth=bsd amdump amidxtaped
 disable = no
 }


 Any good Solution Guys? Thanks!
   
 
 Also you tape device /backup/amanda/dumps/tape01 is not correct,
 it should be file:/backup/amanda/dumps/tape01
 
 use: setape x.com:file:/backup/amanda/dumps/tape0
 
 Jean-Louis
 
 

-- 
View this message in context: 
http://www.nabble.com/amrecover-issue-tf3669327.html#a10309749
Sent from the Amanda - Users mailing list archive at Nabble.com.

amrecover issue

2007-05-02 Thread anthonyh 
 ditem-path=/.bash_history
add_file: (Successful) Added /.bash_history
add_file: Pondering ditem-path=/.
append_to_tapelist(tapelist=(nil), label='DailySet1-001', , file=-1,
isafile=0)
dump_tapelist(0x9b02948):
  0x9b02948-next = (nil)
  0x9b02948-label= DailySet1-001
  0x9b02948-isafile  = 0
  0x9b02948-numfiles = 0
  0x9b02948 count = 1
append_to_tapelist(tapelist=0x9b02948, label='DailySet1-001', , file=1,
isafile=0)
dump_tapelist(0x9b02948):
  0x9b02948-next = (nil)
  0x9b02948-label= DailySet1-001
  0x9b02948-isafile  = 0
  0x9b02948-numfiles = 1
  0x9b02948-files[0] = 1
  0x9b02948 count = 1
append_to_tapelist(tapelist=(nil), label='DailySet1-001', , file=-1,
isafile=0)
dump_tapelist(0x9b0a708):
  0x9b0a708-next = (nil)
  0x9b0a708-label= DailySet1-001
  0x9b0a708-isafile  = 0
  0x9b0a708-numfiles = 0
  0x9b0a708 count = 1
append_to_tapelist(tapelist=0x9b0a708, label='DailySet1-001', , file=1,
isafile=0)
dump_tapelist(0x9b0a708):
  0x9b0a708-next = (nil)
  0x9b0a708-label= DailySet1-001
  0x9b0a708-isafile  = 0
  0x9b0a708-numfiles = 1
  0x9b0a708-files[0] = 1
  0x9b0a708 count = 1
security_getdriver(name=bsd) returns 0xa380e0
security_handleinit(handle=0x9b0a738, driver=0xa380e0 (BSD))
amrecover: dgram_send_addr(addr=0xbff84250, dgram=0xa39024)
amrecover: (sockaddr_in *)0xbff84250 = { 2, 10080, 69.20.122.33 }
amrecover: dgram_send_addr: 0xa39024-socket = 3
amrecover: dgram_recv(dgram=0xa39024, timeout=0, fromaddr=0xa49010)
amrecover: (sockaddr_in *)0xa49010 = { 2, 10080, 69.20.122.33 }
security_close(handle=0x9b0a738, driver=0xa380e0 (BSD)

The following are some of my config files
/etc/xinit.d/amanda
service amanda
{
   only_from   = x.com y.com
   socket_type = dgram
   protocol= udp
   wait= yes
   user= amanda
   group   = disk
   groups  = yes
   server  = /usr/local/libexec/amandad
   server_args = -auth=bsd amdump amindexd
   disable = no 
}

/etc/xinit.d/amandaidx
service amandaidx
{   
only_from   = x.com y.com
socket_type = stream
protocol= tcp
wait= no
user= amanda
group   = disk
groups  = yes
server  = /usr/local/libexec/amindexd 
server_args = -auth=bsd amdump amindexd
disable = no
}

service amidxtape
{   
only_from   = x.com y.com
socket_type = stream
protocol= tcp
wait= no
user= amanda
group   = disk
groups  = yes
server  = /usr/local/libexec/amidxtaped 
server_args = -auth=bsd amdump amidxtaped
disable = no
}


Any good Solution Guys? Thanks!
-- 
View this message in context: 
http://www.nabble.com/amrecover-issue-tf3669327.html#a10252427
Sent from the Amanda - Users mailing list archive at Nabble.com.

Re: amrecover issue

2007-05-02 Thread Olivier Nicole 
Hi,

 Currently i'm having some issue with the amrecover. Whenever i tried
 to execute the amrecover it executed properly but till i started to
 extract the data it stated there Can't Talk to Tape Server

I would try in two directions:

1) try to amrecover on the server itself, to some temporary directory

2) check the firewall on your server


best regards,

Olivier

Re: amrecover issue

2007-05-02 Thread Paul Bijnens 
On 2007-04-30 14:05, anthonyh wrote:
 Hi Guys. This is my first post in this Forum. Currently i'm having some issue
 with the amrecover. Whenever i tried to execute the amrecover it executed
 properly but till i started to extract the data it stated there Can't Talk
 to Tape Server

Well you edited the log to obfuscate the hostnames.
Hoping you know what you did:


 
 # amrecover DailySet1
 AMRECOVER Version 2.5.1p3. Contacting server on y.com ...
 220 y.com AMANDA index server (2.5.1p3) ready.

So, y.com is the amanda index-server

 Setting restore date to today (2007-04-30)
 200 Working date set to 2007-04-30.
 200 Config set to DailySet1.
 501 Host y is not in your disklist.
 Trying host y.com ...

And you are executing this command from y.com itself
So client == server?

 501 Host y.com is not in your disklist.
 Trying host y.com ...
 501 Host y.com is not in your disklist.
 Use the sethost command to choose a host to recover
 amrecover sethost x.com

And you want to restore something from a different host x.xom ?


 200 Dump host set to x.com
 amrecover setdisk /home/abamon
 200 Disk set to /home/abamon.
 amrecover list
 amrecover add *
 Added file /libexec.tar.gz
 Added file /.zshrc
 Added file /.viminfo
 Added dir /.ssh/ at date 2007-04-30-18-32-42
 Added file /.mysql_history
 Added file /.bashrc
 Added file /.bash_profile
 Added file /.bash_logout
 Added file /.bash_history
 amrecover list
 TAPE DailySet1-001:1 LEVEL 0 DATE 2007-04-30-18-32-42
/.bash_history
/.bash_logout
/.bash_profile
/.bashrc
/.mysql_history
/.ssh
/.viminfo
/.zshrc
/libexec.tar.gz
 amrecover settape x:/backup/amanda/dumps/tape01
 Using tape /backup/amanda/dumps/tape01 from server x.com

And here Amanda somehow believes that x.com is the tapeserver?
I would expect y.com instead here.  Unless x.com is some
tapeserver running amanda-server software too?


 amrecover extract
 
 Extracting files using tape drive /backup/amanda/dumps/tape01 on host x.com
 The following tapes are needed: DailySet1-001
 
 Restoring files into directory /tmp/amanda/client/DailySet1
 Continue [?/Y/n]? y
 
 Extracting files using tape drive /backup/amanda/dumps/tape01 on host x.com
 Load tape DailySet1-001 now
 Continue [?/Y/n/s/t]? y
 amrecover - can't talk to tape server

That's what I expect, yes.
But I'm not 100% sure because you obfuscated the hostnames



-- 
Paul Bijnens, xplanation Technology ServicesTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***

Re: amrecover issue

2007-05-02 Thread Jean-Louis Martineau 

Check amrecover and amandad debug files.

anthonyh wrote:

The following are some of my config files
/etc/xinit.d/amanda
service amanda
{
   only_from   = x.com y.com
   socket_type = dgram
   protocol= udp
   wait= yes
   user= amanda
   group   = disk
   groups  = yes
   server  = /usr/local/libexec/amandad
   server_args = -auth=bsd amdump amindexd
   disable = no 
}
  

You forgot amidxtaped
server_args = -auth=bsd amdump amindexd amidxtaped
You must also add an entry in .amandahosts

The following 2 services are not needed if all your client are 2.5.1.

/etc/xinit.d/amandaidx
service amandaidx
{   
only_from   = x.com y.com

socket_type = stream
protocol= tcp
wait= no
user= amanda
group   = disk
groups  = yes
server  = /usr/local/libexec/amindexd 
server_args = -auth=bsd amdump amindexd

disable = no
}

service amidxtape
{   
only_from   = x.com y.com

socket_type = stream
protocol= tcp
wait= no
user= amanda
group   = disk
groups  = yes
server  = /usr/local/libexec/amidxtaped 
server_args = -auth=bsd amdump amidxtaped

disable = no
}


Any good Solution Guys? Thanks!
  


Also you tape device /backup/amanda/dumps/tape01 is not correct,
it should be file:/backup/amanda/dumps/tape01

use: setape x.com:file:/backup/amanda/dumps/tape0

Jean-Louis

amrecover issue with tar and spaces

2006-12-06 Thread Steffan Vigano 

Hello,
Seems to be an issue with amrecover within a DLE that contain spaces.
This particular incident came to light on a volume that is being backed 
up via TAR.  I have not tried to reproduce with Dump.  As you can see 
from the snippets below, the output is being mangled a bit.  Dropping 
off leading characters.  If you know what the file structure is suppose 
to be, you can cd down into the dir by specifying it's real name.  
Extraction and recovery seems to work as well.  I ended up just 
extracting the whole directory above where the issue starts.  All files 
were recovered successfully.  Just thought I'd throw it out for the 
developers to see.


I'm a revision behind on 2.5.1p1, so please forgive me if this has been 
addressed.   I'm using GNUtar 1.13.25, on FreeBSD 4.7

-Steffan



amrecover cd Operating Plans
/nfs/snap/NS_Novell/VOL1/RestOfVOL1/NS_Business_Plan/Operating Plans
amrecover ls
2006-11-12-09-12-51 06 Operating Plans/
2006-11-12-09-12-51 06 Manager Scorecard/
amrecover cd 0506 Operating Plans
/nfs/snap/NS_Novell/VOL1/RestOfVOL1/NS_Business_Plan/Operating 
Plans/0506 Operating Plans

amrecover ls
2006-11-12-09-12-51 4 Dept Ops Plan.xls
2006-11-12-09-12-51 3 Dept Ops Plan.xls
2006-11-12-09-12-51 1 Dept Ops Plan.xls


A snippet of the Index file shows everything is fine within the file.

/NS_Business_Plan/Operating Plans/0506 Operating Plans/61141 Dept Ops 
Plan.xls
/NS_Business_Plan/Operating Plans/0506 Operating Plans/61151 Dept Ops 
Plan.xls
/NS_Business_Plan/Operating Plans/0506 Operating Plans/61161 Dept Ops 
Plan.xls
/NS_Business_Plan/Operating Plans/0506 Operating Plans/61171 Dept Ops 
Plan.xls
/NS_Business_Plan/Operating Plans/0506 Operating Plans/61212 Dept Ops 
Plan.xls

amrecover issue when I run ./configure that I believe causeing another issue down the line

2005-05-18 Thread Chuck Amadi Systems Administrator 
Hi I installed Using Yast2 readline and readline-devel

# locate readline as below

/usr/include/guile-readline
/usr/include/guile-readline/readline.h
/usr/include/readline
/usr/include/readline/chardefs.h
/usr/include/readline/history.h
/usr/include/readline/keymaps.h
/usr/include/readline/readline.h
/usr/include/readline/rlconf.h
/usr/include/readline/rlstdc.h
/usr/include/readline/rltypedefs.h
/usr/include/readline/tilde.h

But when I run ./configure I still get a warning about amrecover

configure: WARNING: *** No terminal library, no history and command line
editing in amrecover!
configure: WARNING: *** vtblc headers not found - no QIC volume table
support!

Any ideas

Cheers

Chuck

Re: amrecover issue when I run ./configure that I believe causeing another issue down the line

2005-05-18 Thread Paul Bijnens 
Chuck Amadi Systems Administrator wrote:
But when I run ./configure I still get a warning about amrecover
Because configure still uses the old settings.
Get rid of them by
   make distclean
And then followed by a new
  ./config --with-user=... ...
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***

Re: amrecover issue when I run ./configure that I believe causeing another issue down the line

2005-05-18 Thread Chuck Amadi Systems Administrator 
Hi Paul

I have done make distclean every time I re run ./configure I am going to
pursue using the rpm's as I assume I want have an issue with readline
and readline-devel.

Cheers


On Wed, 2005-05-18 at 11:05 +0200, Paul Bijnens wrote:
 Chuck Amadi Systems Administrator wrote:
  But when I run ./configure I still get a warning about amrecover
 
 Because configure still uses the old settings.
 Get rid of them by
 make distclean
 And then followed by a new
./config --with-user=... ...

Re: amrecover issue when I run ./configure that I believe causeing another issue down the line

2005-05-18 Thread Paul Bijnens 
Chuck Amadi Systems Administrator wrote:
I have done make distclean every time I re run ./configure I am going to
pursue using the rpm's as I assume I want have an issue with readline
and readline-devel.
Fine with me.
But is there a file /usr/lib/libreadline.so.* installed?
If yes, in the file config.status (the result of ./configure) is
there a line saying:
s,@READLINE_LIBS@,-lreadline,;t t
(a sed command used to change the needed files)
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***

Re: amrecover issue when I run ./configure that I believe causeing another issue down the line

2005-05-18 Thread Alexander Jolk 
Chuck Amadi Systems Administrator wrote:
configure: WARNING: *** No terminal library, no history and command line
editing in amrecover!
A look into config.log is normally most appropriate in a case like this. 
 It gives you a precise indication of what it checked for, and why it 
failed.

Alex

--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

amrecover issue

2001-08-07 Thread Matt Galer 

Greetings.

I just got amanda up and backing things up fine.  The next step is obviously
to test restores, and I've come up with some questions/concerns in this
area.

first, I have NO tape drive yet - I'm trying to pry some dollars out of
managements' hands for this, but no luck so far - so all backups are being
done to holding disks only (RAID 0+1).

anyway, I wanted to restore a file from yesterdays backup as a test.

from log.20010805.0:

SUCCESS dumper utl-atl-06 /export/home 20010805 0 [sec 59.666 kb 393280 kps
6591.3 orig-kb 393260]

so a full backup was done successfully.  I went ahead and verified the file
in question was in the index file:

[siteops@utl-atl-06 _export_home]$ zgrep sysedge.cf *
20010731_0.gz:07330357423/./siteops/sysedge.cf
20010805_0.gz:07331665340/./siteops/sysedge.cf

ok, looks good to me!  I su over to root and go into amrecover inside the
/export/home directory

[root@utl-atl-06 home]# amrecover Daily
AMRECOVER Version 2.4.2p2. Contacting server on utl-atl-06 ...
220 utl-atl-06 AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2001-08-06)
200 Working date set to 2001-08-06.
200 Config set to Daily.
200 Dump host set to utl-atl-06.
$CWD '/export/home' is on disk '/export/home' mounted at '/export/home'.
200 Disk set to /export/home.
/export/home
amrecover history
200- Dump history for config Daily host utl-atl-06 disk /export/home
201- 2001-08-05 0 /backup/hd2/20010805/utl-atl-06._export_home.0 0
201- 2001-08-04 1 /backup/hd2/20010804/utl-atl-06._export_home.1 0
201- 2001-08-03 1 /backup/hd1/20010803/utl-atl-06._export_home.1 0
201- 2001-08-02 1 /backup/hd3/20010802/utl-atl-06._export_home.1 0
201- 2001-08-01 1 /backup/hd2/20010801/utl-atl-06._export_home.1 0
201- 2001-07-31 0 /backup/hd2/20010731/utl-atl-06._export_home.0 0
200 Dump history for config Daily host utl-atl-06 disk /export/home
amrecover setdate ---05
200 Working date set to 2001-08-05.
amrecover ls
2001-08-05 app/
amrecover

hmm.. not good - here is a directory listing for /export/home:

[root@utl-atl-06 home]# ls -la
total 26
drwxr-xr-x   6 root root 512 Dec 13  2000 .
drwxrwxr-x   3 root sys  512 Dec 11  2000 ..
drwxr-xr-x   5 root other512 Dec 15  2000 app
drwxr-xr-x   8 aribaariba512 Dec 27  2000 ariba
drwx--   2 root root8192 Dec 11  2000 lost+found
drwxr-xr-x   6 siteops  siteops  512 Aug  6 12:19 siteops

so we are missing a couple of directories in the interactive part of
amrecover.  Being semi-concerned at the integrity of the backups, I decided
to try a manual restore, and so extracted the gzip-tar image from the
holding disk with dd.  Then unzipped it, and verified that the file was
there:

[root@utl-atl-06 20010805]# dd if=utl-atl-06._export_home.0 bs=32k skip=1
of=/tmp/out
12290+0 records in
12290+0 records out
[siteops@utl-atl-06 /tmp]$ tar tvf out | grep sysedge.cf
-rw--- siteops/siteops 2678 2001-04-20 16:41
07331665340/./siteops/sysedge.cf


extracting the file and diff'ing the original confirms that it is ok.

any suggestions?

is this a by-product of only using holding disks, or something else?  (note
that I got similar results for all the filesystems I backed-up - some
directories would appear in amrecover, some would not.

Thanks in advance!

Matt

+-
Matthew Galer
[EMAIL PROTECTED]
770-453-9001 x149

Re: Amrecover issue

2001-01-13 Thread Alexandre Oliva 

On Jan 10, 2001, Eric Helms [EMAIL PROTECTED] wrote:

 [EMAIL PROTECTED]

Wrong format.  This should be:

hostname username

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Amrecover issue

2001-01-10 Thread Eric Helms 

Hello.  I need to recover a single file that is archived, so I was
attempting to use amrecover because of it's convenient interactive
mode.  However, when I run the command
/usr/local/amanda/sbin/amrecover -s amandaserver.mydomain.com
I get
AMRECOVER Version 2.4.1p1. Contacting server on
amandaserver.mydomain.com ...
amrecover: Unexpected server end of file.

I have already read the Amanda FAQ-O-Matic with regards to this error,
and I am pretty certain that it is not a DNS issue.

Here is  the output of the .amandahosts file from the amanda server.

[EMAIL PROTECTED]
root@myhost
myhost.mydomain.com
myhost
10.1.1.17
[EMAIL PROTECTED]

I have made sure to run amrecover as root on my box (the client).

Since I have read quite a few of the archives on this list, I will also
include the contents of the /tmp/amanda/amrecover.debug file.

amrecover: debug 1 pid 7675 ruid 0 euid 0 start time Wed Jan 10 15:38:30
2001

Also, here is my entry in inetd.conf that is pertinent.

amandaidx stream tcp nowait amanda /usr/local/amanda/libexec amindexd
amidxtape stream tcp nowait amanda /usr/local/amanda/libexec amidxtaped

And, just for good measure,  some content of /var/log/messages which
corresponds to the time and attempts  to connect to the server.

Jan 10 14:47:28 amandaserver inetd[24130]: pid 26849: exit status 1
Jan 10 14:48:35 amandaserver inetd[24130]: pid 26856: exit status 1
Jan 10 14:51:11 amandaserver inetd[24130]: pid 26872: exit status 1
Jan 10 14:51:34 amandaserver inetd[24130]: pid 26873: exit status 1

This is obviously showing some type of inetd issue, but I am at a loss
to determine what it is.  I also ran tcpdump while attempting to
connect, analyzed the output,  and found it to be most unhelpful.

I sincerely appreciate any help that can be offered.

Eric Helms

Re: Amrecover issue

2001-01-10 Thread John R. Jackson 

/usr/local/amanda/sbin/amrecover -s amandaserver.mydomain.com

Are you certain the default configuration built into amrecover is the
config you wanted to use?  Put a different way, try this:

  /usr/local/amanda/sbin/amrecover config -s amandaserver.mydomain.com

I get
AMRECOVER Version 2.4.1p1. Contacting server on
amandaserver.mydomain.com ...
amrecover: Unexpected server end of file.

This says amindexd quit early.  What's in /tmp/amanda/amindexd*debug
on amandaserver.mydomain.com?

Eric Helms

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: Amrecover issue

2001-01-10 Thread David Lloyd 


John et al:

 /usr/local/amanda/sbin/amrecover -s amandaserver.mydomain.com
 
 Are you certain the default configuration built into amrecover is the
 config you wanted to use?  Put a different way, try this:

I gave up using the "default" configuration because it would always
"default" to something that didn't exist and wouldn't change. And some
of the utilities pick it up and some of them don't. Furthermore, I don't
like to use it because in an emergency backup situation where you manage
to get AMANDA back onto the system, if you're used to typing "amdump
MYCONFIG" or wotever then you've got one less headache in the heat of
battle...

DL
-- 
The hate stands ready...
 Send forth your terror into HELL!

Re: Amrecover issue

2001-01-10 Thread John R. Jackson 

I gave up using the "default" configuration because it would always
"default" to something that didn't exist and wouldn't change.  ...

Agreed.  I set mine during ./configure to one I know I'll never use so
I always have to explicitly enter it on commands.  Not that big a deal
since most commands require it anyway.

DL

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]