RESEND UPDATE - RE: Amanda Solaris 10
Thanks for your input. I believe there is a big difference between pre 2.5.1 and 2.5.1. See the following: http://wiki.zmanda.com/index.php/Main_Page http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authenticatio n 2.5.1 starts using the secure API which means xinetd or inetd is different. The zmanda "Configuring bsd" above talks about his. It talks about how to do this with xinetd/inetd but Solaris 10 is different. The problem is I am not sure how this equates to Solaris 10 smf. Some parameters will need to be added to the smf service entry for amandad to get this to work, I believe. I have not done this yet and just wanted to know if someone else has 2.5.1 working with Solaris 10 and see if I am on the right path. In 2.5.1 when I rum the amrecover I get ##R##-zorn->[146] ##> ~amanda/sbin/amrecover AMRECOVER Version 2.5.1. Contacting server on zorn ... NAK: amindexd: invalid service This is my inetadm -l svc:/network/amanda/udp:default SCOPENAME=VALUE name="amanda" endpoint_type="dgram" proto="udp" isrpc=FALSE wait=TRUE exec="/local/Amanda/amanda/libexec/amandad" user="amanda" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE default tcp_trace=FALSE default tcp_wrappers=FALSE So my question is how do I get -auth=bsd amdump amindexd amidxtaped in the exec="/local/Amanda/amanda/libexec/amandad" Answer to your second question. We have a Sun C4 and I have moved to chg-zd-mtx to control my changer. I like how it handles searching for barcodes. Robert * UPDATE * * * I did the following and this resolved my amrecover problem ##R##-zorn->[233] ##> inetadm -m svc:/network/amanda/udp:default "exec=/local/Amanda/amanda/libexec/amandad -auth=bsd amdump amindexd amidxtaped" ##R##-zorn->[234] ##> inetadm -l svc:/network/amanda/udp:default SCOPENAME=VALUE name="amanda" endpoint_type="dgram" proto="udp" isrpc=FALSE wait=TRUE exec="/local/Amanda/amanda/libexec/amandad -auth=bsd amdump amindexd amidxtaped" user="amanda" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE default tcp_trace=FALSE default tcp_wrappers=FALSE and now my amrecover work just fine. I will need to look at adding this to the zmanda manual pages. Robert * * * > -Original Message- > From: Peter Kunst [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 23, 2006 5:08 AM > To: McGraw, Robert P. > Subject: Re: Amanda Solaris 10 > > > Hi Robert, > > McGraw, Robert P. wrote: > > Is anyone running Amanda 2.5.1 on Solaris 10 host? If so could you send > me > > the output from > > > > inetadm -l svc:/network/amanda/udp:default > > inetadm -l svc:/network/amandaidx/tcp:default > > inetadm -l svc:/network/amidxtape/tcp:default > > > > I would like to see how you have set things up. > > you can run inetconv(1M) after inserting your amanda services into > /etc/inetd.conf, which results in appropriate amanda smf services > manifests. > > If you change the path to binaries, you have to edit service manifests > in /var/svc/manifest/network/ and run "svccfg import .xml", > because another inetconv run doesn't change an existing manifest. > > But anyways, here we go: > > > [amanda] janus30(Solaris[5.10]):amanda/$ inetadm -l > svc:/network/amanda/udp:default > SCOPENAME=VALUE > name="amanda" > endpoint_type="dgram" > proto="udp" > isrpc=FALSE > wait=TRUE > exec="/home/amanda/2.5.0p2/Solaris/5.10/libexec/amandad" > user="amanda" > default bind_addr="" > default bind_fail_max=-1 > default bind_fail_interval=-1 > default max_con_rate=-1 > default max_copies=-1 > default con_rate_offline=-1 > default failrate_cnt=40 > default failrate_interval=60 > default inherit_env=TRUE > default tcp_trace=FALSE > default tcp_wrappers=FALSE > [amanda] janus30(Solaris[5.10]):amanda/$ inetadm -l > svc:/network/amandaidx/tcp:default > SCOPENAME=VALUE > name="amandaidx" > endpoint_type="stream" > proto="tcp" > isrpc=FALSE > wait=FALSE > exec="/home/amanda/2.5.0p2/Solaris/5.10/libexec/amindexd" > user="amanda" > default bind_addr="" > default bind_fail_max=-1 > default bind_fail_interval=-1 > default max_con_rate=-1 > default max_copies=-1 > default con_rate_offline=-1 > default failrate_cnt=40 > default failrate_interval=60 > default inherit_env=TRUE > default tcp_trace
RE: Amanda Solaris 10
Thanks for your input. I believe there is a big difference between pre 2.5.1 and 2.5.1. See the following: http://wiki.zmanda.com/index.php/Main_Page http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authenticatio n 2.5.1 starts using the secure API which means xinetd or inetd is different. The zmanda "Configuring bsd" above talks about his. It talks about how to do this with xinetd/inetd but Solaris 10 is different. The problem is I am not sure how this equates to Solaris 10 smf. Some parameters will need to be added to the smf service entry for amandad to get this to work, I believe. I have not done this yet and just wanted to know if someone else has 2.5.1 working with Solaris 10 and see if I am on the right path. In 2.5.1 when I rum the amrecover I get ##R##-zorn->[146] ##> ~amanda/sbin/amrecover AMRECOVER Version 2.5.1. Contacting server on zorn ... NAK: amindexd: invalid service This is my inetadm -l svc:/network/amanda/udp:default SCOPENAME=VALUE name="amanda" endpoint_type="dgram" proto="udp" isrpc=FALSE wait=TRUE exec="/local/Amanda/amanda/libexec/amandad" user="amanda" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE default tcp_trace=FALSE default tcp_wrappers=FALSE So my question is how do I get -auth=bsd amdump amindexd amidxtaped in the exec="/local/Amanda/amanda/libexec/amandad" Answer to your second question. We have a Sun C4 and I have moved to chg-zd-mtx to control my changer. I like how it handles searching for barcodes. Robert > -Original Message- > From: Peter Kunst [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 23, 2006 5:08 AM > To: McGraw, Robert P. > Subject: Re: Amanda Solaris 10 > > > Hi Robert, > > McGraw, Robert P. wrote: > > Is anyone running Amanda 2.5.1 on Solaris 10 host? If so could you send > me > > the output from > > > > inetadm -l svc:/network/amanda/udp:default > > inetadm -l svc:/network/amandaidx/tcp:default > > inetadm -l svc:/network/amidxtape/tcp:default > > > > I would like to see how you have set things up. > > you can run inetconv(1M) after inserting your amanda services into > /etc/inetd.conf, which results in appropriate amanda smf services > manifests. > > If you change the path to binaries, you have to edit service manifests > in /var/svc/manifest/network/ and run "svccfg import .xml", > because another inetconv run doesn't change an existing manifest. > > But anyways, here we go: > > > [amanda] janus30(Solaris[5.10]):amanda/$ inetadm -l > svc:/network/amanda/udp:default > SCOPENAME=VALUE > name="amanda" > endpoint_type="dgram" > proto="udp" > isrpc=FALSE > wait=TRUE > exec="/home/amanda/2.5.0p2/Solaris/5.10/libexec/amandad" > user="amanda" > default bind_addr="" > default bind_fail_max=-1 > default bind_fail_interval=-1 > default max_con_rate=-1 > default max_copies=-1 > default con_rate_offline=-1 > default failrate_cnt=40 > default failrate_interval=60 > default inherit_env=TRUE > default tcp_trace=FALSE > default tcp_wrappers=FALSE > [amanda] janus30(Solaris[5.10]):amanda/$ inetadm -l > svc:/network/amandaidx/tcp:default > SCOPENAME=VALUE > name="amandaidx" > endpoint_type="stream" > proto="tcp" > isrpc=FALSE > wait=FALSE > exec="/home/amanda/2.5.0p2/Solaris/5.10/libexec/amindexd" > user="amanda" > default bind_addr="" > default bind_fail_max=-1 > default bind_fail_interval=-1 > default max_con_rate=-1 > default max_copies=-1 > default con_rate_offline=-1 > default failrate_cnt=40 > default failrate_interval=60 > default inherit_env=TRUE > default tcp_trace=FALSE > default tcp_wrappers=FALSE > [amanda] janus30(Solaris[5.10]):amanda/$ inetadm -l > svc:/network/amidxtape/tcp:default > > SCOPENAME=VALUE > name="amidxtape" > endpoint_type="stream" > proto="tcp" > isrpc=FALSE > wait=FALSE > exec="/home/amanda/2.5.0p2/Solaris/5.10/libexec/amidxtaped" > user="amanda" > default bind_addr="" > default bind_fail_max=-1 > default bind_fail_interval=-1 > default max_con_rate=-1 > default max_copies=-1 > default con_rate_offline=-1 > default failrate_cnt=40 > default failrate_interval=60 > default inherit_env=TRUE > default tcp_trace=FALSE > default tcp_wrappers=FALSE > > By the way, do you have a changer connected ? Which changer utility do > you use ? We still use stctl. > > Cheers, Peter smime.p7s Description: S/MIME cryptographic signature
Re: Illegal density on dump command
Fabio, You installed amanda-2.5.1-20060922.tar.gz on the client? Could you send me the sendbackup..debug file? Jean-Louis Fabio Corazza wrote: Jean-Louis Martineau wrote: Fabio, It's a known bug, it is already fixed. Get the latest 2.5.1 snapshot from http://www.iro.umontreal.ca/~martinea/amanda I've got amanda-2.5.1-20060922.tar.gz but tonight I had the same exact problem: /-- mybbook-db01-mgmt /var lev 0 FAILED [/sbin/dump returned 1] sendbackup: start [mybbook-db01-mgmt:/var level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f - ... sendbackup: info end ? /sbin/dump: illegal density -- 0usf sendbackup: error [/sbin/dump returned 1] What can it be at this time? I was thinking to switch into GNUTAR but those servers are very quiet, just some logs are being written and during the night there's just a little of activity, so dump would have been the best way to go. Regards, Fabio
Re: Illegal density on dump command
Jean-Louis Martineau wrote:
> Fabio,
>
> It's a known bug, it is already fixed.
> Get the latest 2.5.1 snapshot from
> http://www.iro.umontreal.ca/~martinea/amanda
I've got amanda-2.5.1-20060922.tar.gz but tonight I had the same exact
problem:
/-- mybbook-db01-mgmt /var lev 0 FAILED [/sbin/dump returned 1]
sendbackup: start [mybbook-db01-mgmt:/var level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f - ...
sendbackup: info end
? /sbin/dump: illegal density -- 0usf
sendbackup: error [/sbin/dump returned 1]
What can it be at this time?
I was thinking to switch into GNUTAR but those servers are very quiet,
just some logs are being written and during the night there's just a
little of activity, so dump would have been the best way to go.
Regards,
Fabio
> Jean-Louis
>
> Fabio Corazza wrote:
>> Hi guys,
>> I'm getting all the dump failed with the following reason:
>>
>> ? /sbin/dump: illegal density -- 0usf
>> sendbackup: error [/sbin/dump returned 1]
>>
>> This is my dumptype definition:
>>
>> define dumptype nocomp-root-ssh {
>> comp-root
>> comment "Root partitions without compression through SSH"
>> auth "ssh"
>> ssh_keys "/var/lib/amanda/.ssh/id_rsa_amdump"
>> compress none
>> }
>>
>>
>> Using Amanda 2.5.1 on RHEL4.4
>>
>>
>>
>> Regards,
>>
>>
>
