amanda on Mac OS X (10.5.4) Leopard
I just got a MacBook Pro (10.5.4) and I want to add it as a client on my Amanda server. I looked at http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X#Version-Specific_Notes and it doesn't mention leopard. Do I follow the same instructions? I noticed that on my Mac /etc./services already has amanda in it. amanda 10080/udp # Amanda amanda 10080/tcp # Amanda # John Jackson <[EMAIL PROTECTED]> # <[EMAIL PROTECTED]> The ports listed are different than the wiki instructions. Is there another page that I should be looking at? --myron ===== Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College [EMAIL PROTECTED]
Re: amanda on Mac OS X (10.5.4) Leopard
This may take a while. I went to the step on setting up the amanda user and the niutil command is no longer there. I guess I have to think more about this and learn more about my Mac. --myron = Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College [EMAIL PROTECTED] On Jul 22, 2008, at 2:46 PM, Dustin J. Mitchell wrote: On Tue, Jul 22, 2008 at 1:42 PM, myron <[EMAIL PROTECTED]> wrote: I looked at http://wiki.zmanda.com/index.php/Installation/OS_Specific_Notes/Installing_Amanda_on_Mac_OS_X#Version-Specific_Notes and it doesn't mention leopard. Do I follow the same instructions? As far as I know. My machines are still 10.4. I'm cheap :) I noticed that on my Mac /etc./services already has amanda in it. amanda 10080/udp # Amanda amanda 10080/tcp # Amanda # John Jackson <[EMAIL PROTECTED]> # <[EMAIL PROTECTED]> The ports listed are different than the wiki instructions. Is there another page that I should be looking at? And so are the names. The ports in the wiki are only useful if you're using kerberos. You don't need to add those. Please add any notes, or just a description of your success, to the wiki when you get things working. Dustin -- Storage Software Engineer http://www.zmanda.com
new client backup problems--zfs?
I added a new client to amanda and it won't back up. I don't add clients often, but I think I got everything right. I have a feeling this is because the filesystem is zfs--my first--everything else I back up is ufs. I'm going to put a ufs filesystem on the client today and see if that backs up tonight, just to make sure the client isn't really the problem. I included all the relevant information in the hope that someone can spot something. disklist entry - hogwarts / comp-root 0 make sure network services are running and listening on the right ports hogwarts# netstat -a | grep amanda *.amandaIdle *.amandaidx *.*0 0 49152 0 LISTEN run a check for client - bane:~% amcheck DAILY hogwarts Amanda Tape Server Host Check - amcheck-server: slot 16: date 20100219 label DAILY16 (exact label match) NOTE: skipping tape-writable test NOTE: info dir /var/amanda/DAILY/curinfo/hogwarts: does not exist NOTE: index dir /var/amanda/DAILY/index/hogwarts: does not exist Server check took 5.064 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.176 seconds, 0 problems found (brought to you by Amanda 2.4.3) Problem entries from the logs --- --> log.20100610.0 DISK planner hogwarts / INFO planner Adding new disk hogwarts:/. FAIL planner hogwarts / 20100610 0 [disk / offline on hogwarts?] --> amdump.1 hogwarts:/ overdue 14770 days for level 0 setup_estimate: hogwarts:/: command 0, options: last_level -1 next_level0 -14770 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) planner: time 0.447: setting up estimates took 0.365 secs . (This is strange that the estimate number is small and negative.) planner: time 2.188: got result for host hogwarts disk /: 0 -> -1K, -1 -> -1K, -1 -> -1K 0: hogwarts / planner: FAILED hogwarts / 20100610 0 [disk / offline on hogwarts?] (I know amanda is on the system because these tmp files were created.) hogwarts# ls -al /tmp/.rlg.p3aW4b/ total 32 d- 2 amanda sys 117 Jun 10 00:14 . drwxrwxrwt 7 root sys 465 Jun 10 03:30 .. --myron = Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College my...@cs.moravian.edu
Re: new client backup problems--zfs?
It's been a while since I set up amanda. I didn't make any changes in amanda.conf. The only relevant line that I see in that file references dumptypes.conf. I think what you're telling me is that I should have used comp-root- tar, which uses guntar, instead of comp-root. The .rig* file that I sent was the only thing in /tmp. There are no other log files on the client that I can see. I'll make the dumptype change to disklist and see what happens tonight. I don't know how to answer your last question. How would I be able to tell? --myron ===== Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College my...@cs.moravian.edu On Jun 11, 2010, at 9:21 AM, Brian Cuttler wrote: Myron, You made all necesary changes to amanda.conf to allow for a gtar based dumper ? (there being no such things and zfsdump as an analog to ufsdump). What do the /tmp/amanda logs on the client tell you, are you getting through the estimate phase and failing the actual sendfile phase ? On Fri, Jun 11, 2010 at 09:04:57AM -0400, myron wrote: I added a new client to amanda and it won't back up. I don't add clients often, but I think I got everything right. I have a feeling this is because the filesystem is zfs--my first--everything else I back up is ufs. I'm going to put a ufs filesystem on the client today and see if that backs up tonight, just to make sure the client isn't really the problem. I included all the relevant information in the hope that someone can spot something. disklist entry - hogwarts / comp-root 0 make sure network services are running and listening on the right ports hogwarts# netstat -a | grep amanda *.amandaIdle *.amandaidx *.*0 0 49152 0 LISTEN run a check for client - bane:~% amcheck DAILY hogwarts Amanda Tape Server Host Check - amcheck-server: slot 16: date 20100219 label DAILY16 (exact label match) NOTE: skipping tape-writable test NOTE: info dir /var/amanda/DAILY/curinfo/hogwarts: does not exist NOTE: index dir /var/amanda/DAILY/index/hogwarts: does not exist Server check took 5.064 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.176 seconds, 0 problems found (brought to you by Amanda 2.4.3) Problem entries from the logs --- --> log.20100610.0 DISK planner hogwarts / INFO planner Adding new disk hogwarts:/. FAIL planner hogwarts / 20100610 0 [disk / offline on hogwarts?] --> amdump.1 hogwarts:/ overdue 14770 days for level 0 setup_estimate: hogwarts:/: command 0, options: last_level -1 next_level0 -14770 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) planner: time 0.447: setting up estimates took 0.365 secs . (This is strange that the estimate number is small and negative.) planner: time 2.188: got result for host hogwarts disk /: 0 -> -1K, -1 -> -1K, -1 -> -1K 0: hogwarts / planner: FAILED hogwarts / 20100610 0 [disk / offline on hogwarts?] (I know amanda is on the system because these tmp files were created.) hogwarts# ls -al /tmp/.rlg.p3aW4b/ total 32 d- 2 amanda sys 117 Jun 10 00:14 . drwxrwxrwt 7 root sys 465 Jun 10 03:30 .. --myron = Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College my...@cs.moravian.edu --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
how to specify a linux disk
I put raid and lvm on the disk running ubuntu 10.04. Amcheck didn't report any error, but it didn't back up. I have other linux boxes w/o raid or lvm that back up fine. I assume that it's the way I specified the partition. /dev/md0 instead of /dev/sda[1-5], or should it be how lvm specifies the partition /dev/mapper/system-var. /var/amanda/DAILY/log/amdump.1 planner: time 0.155: setting up estimates for errol:/dev/md0 errol:/dev/md0 overdue 15177 days for level 0 setup_estimate: errol:/dev/md0: command 0, options: last_level -1 next_level0 -15177 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) planner: time 0.156: setting up estimates took 0.082 secs planner: time 1.394: got result for host errol disk /dev/md0: 0 -> -1K, -1 -> -1K, -1 -> -1K FAILED QUEUE: 0: errol /dev/md0 planner: FAILED errol /dev/md0 20110722 0 [disk /dev/md0 offline on errol?] /var/amanda/DAILY/log/log.20110722.0 DISK planner errol /dev/md0 INFO planner Adding new disk errol:/dev/md0. FAIL planner errol /dev/md0 20110722 0 [disk /dev/md0 offline on errol?] --myron ===== Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College my...@cs.moravian.edu
Re: how to specify a linux disk
On Jul 22, 2011, at 11:14 AM, Jean-Louis Martineau wrote:
Which amanda release are you using?
root@errol:~# dpkg -l | grep amanda
ii amanda-client 1:2.6.1p1-2
Advanced Maryland Automatic Network Disk Arc
ii amanda-common 1:2.6.1p1-2
Advanced Maryland Automatic Network Disk Arc
Which program/application are you using to do the backup.
I guess it's tar or dump. Whatever is on linux? How do I find out?
Post all the related client debug files.
I don't see any debug files. The only log entry I have from this
morning's backup is
/var/log/deamon.log
Jul 22 00:15:01 errol amandad[4927]: connect from 204.186.196.15
(204.186.196.15)
This is how apt-get set up amanda.
root@errol:~# cat /etc/services | grep aman
amanda 10080/tcp # amanda backup services
amanda 10080/udp
kamanda 10081/tcp # amanda backup services
(Kerberos)
kamanda 10081/udp
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
root@errol:~# netstat -a | grep -i amanda
udp0 0 *:amanda*:*
root@errol:~# cat /etc/inetd.conf
...
#:OTHER: Other services
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad -
auth=bsd amdump amindexd amidxtaped
root@errol:~# cat /etc/xinetd.d/amanda
# default: on
# description: The amanda service
service amanda
{
# only_from =
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
disable = no
}
root@errol:~# lsof | grep aman
inetd 4566 root4u IPv4 17722
0t0UDP *:amanda
Jean-Louis
On 07/22/2011 09:35 AM, myron wrote:
I put raid and lvm on the disk running ubuntu 10.04.
Amcheck didn't report any error, but it didn't back up.
I have other linux boxes w/o raid or lvm that back up fine.
I assume that it's the way I specified the partition. /dev/md0
instead
of /dev/sda[1-5], or should it be how lvm specifies the partition
/dev/mapper/system-var.
/var/amanda/DAILY/log/amdump.1
planner: time 0.155: setting up estimates for errol:/dev/md0
errol:/dev/md0 overdue 15177 days for level 0
setup_estimate: errol:/dev/md0: command 0, options:
last_level -1 next_level0 -15177 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
planner: time 0.156: setting up estimates took 0.082 secs
planner: time 1.394: got result for host errol disk /dev/md0: 0 ->
-1K, -1 -> -1K, -1 -> -1K
FAILED QUEUE:
0: errol /dev/md0
planner: FAILED errol /dev/md0 20110722 0 [disk /dev/md0 offline on
errol?]
/var/amanda/DAILY/log/log.20110722.0
DISK planner errol /dev/md0
INFO planner Adding new disk errol:/dev/md0.
FAIL planner errol /dev/md0 20110722 0 [disk /dev/md0 offline on
errol?]
--myron
=
Myron Kowalski
MoCoSIN Network/Systems Administrator
Moravian College
my...@cs.moravian.edu <mailto:my...@cs.moravian.edu>
Re: how to specify a linux disk
HAVE_GZIP
COMPRESS_SUFFIX=".gz"
1311308101.214929: amandad:COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best"
1311308101.214935: amandad:UNCOMPRESS_OPT="-dc"
1311308101.215011: amandad: dgram_recv(dgram=0x7f8d9d322188,
timeout=0, fromaddr=0x7f8d9d332180)
1311308101.215032: amandad: (sockaddr_in *)0x7f8d9d332180 = { 2, 1015,
204.186.196.15 }
1311308101.215054: amandad: security_handleinit(handle=0x98cd00,
driver=0x7f8d9d317900 (BSD))
1311308101.219255: amandad: accept recv REQ pkt:
<<<<<
SERVICE noop
OPTIONS features=feff9f00;
>>>>>
1311308101.219280: amandad: creating new service: noop
OPTIONS features=feff9f00;
1311308101.219715: amandad: sending ACK pkt:
<<<<<
>>>>>
1311308101.219762: amandad: dgram_send_addr(addr=0x98cd40,
dgram=0x7f8d9d322188)
1311308101.219771: amandad: (sockaddr_in *)0x98cd40 = { 2, 1015,
204.186.196.15 }
1311308101.219777: amandad: dgram_send_addr: 0x7f8d9d322188->socket = 0
1311308102.221730: amandad: sending REP pkt:
<<<<<
OPTIONS features=9ffe7f;
>>>>>
1311308102.221763: amandad: dgram_send_addr(addr=0x98cd40,
dgram=0x7f8d9d322188)
1311308102.221771: amandad: (sockaddr_in *)0x98cd40 = { 2, 1015,
204.186.196.15 }
1311308102.221779: amandad: dgram_send_addr: 0x7f8d9d322188->socket = 0
1311308102.222848: amandad: dgram_recv(dgram=0x7f8d9d322188,
timeout=0, fromaddr=0x7f8d9d332180)
1311308102.222879: amandad: (sockaddr_in *)0x7f8d9d332180 = { 2, 1015,
204.186.196.15 }
1311308102.222900: amandad: received ACK pkt:
<<<<<
>>>>>
1311308102.222927: amandad: security_close(handle=0x98cd00,
driver=0x7f8d9d317900 (BSD))
1311308102.223641: amandad: dgram_recv(dgram=0x7f8d9d322188,
timeout=0, fromaddr=0x7f8d9d332180)
1311308102.223652: amandad: (sockaddr_in *)0x7f8d9d332180 = { 2, 1015,
204.186.196.15 }
1311308102.223663: amandad: security_handleinit(handle=0x98cd00,
driver=0x7f8d9d317900 (BSD))
1311308102.226317: amandad: accept recv REQ pkt:
<<<<<
SERVICE sendsize
OPTIONS features=feff9f00;maxdumps=1;hostname=errol;
GNUTAR /dev/md0 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;index;
>>>>>
1311308102.226346: amandad: creating new service: sendsize
OPTIONS features=feff9f00;maxdumps=1;hostname=errol;
GNUTAR /dev/md0 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;index;
1311308102.226821: amandad: sending ACK pkt:
<<<<<
>>>>>
1311308102.226864: amandad: dgram_send_addr(addr=0x98cd40,
dgram=0x7f8d9d322188)
1311308102.226873: amandad: (sockaddr_in *)0x98cd40 = { 2, 1015,
204.186.196.15 }
1311308102.226880: amandad: dgram_send_addr: 0x7f8d9d322188->socket = 0
1311308102.239066: amandad: sending REP pkt:
<<<<<
OPTIONS features=9ffe7f;
/dev/md0 0 SIZE -1
>>>>>
1311308102.239084: amandad: dgram_send_addr(addr=0x98cd40,
dgram=0x7f8d9d322188)
1311308102.239093: amandad: (sockaddr_in *)0x98cd40 = { 2, 1015,
204.186.196.15 }
1311308102.239101: amandad: dgram_send_addr: 0x7f8d9d322188->socket = 0
1311308102.240228: amandad: dgram_recv(dgram=0x7f8d9d322188,
timeout=0, fromaddr=0x7f8d9d332180)
1311308102.240251: amandad: (sockaddr_in *)0x7f8d9d332180 = { 2, 1015,
204.186.196.15 }
1311308102.240268: amandad: received ACK pkt:
<<<<<
>>>>>
1311308102.240293: amandad: security_close(handle=0x98cd00,
driver=0x7f8d9d317900 (BSD))
1311308131.244341: amandad: pid 4927 finish time Fri Jul 22 00:15:31
2011
On 07/22/2011 09:35 AM, myron wrote:
I put raid and lvm on the disk running ubuntu 10.04.
Amcheck didn't report any error, but it didn't back up.
I have other linux boxes w/o raid or lvm that back up fine.
I assume that it's the way I specified the partition. /dev/md0
instead
of /dev/sda[1-5], or should it be how lvm specifies the partition
/dev/mapper/system-var.
/var/amanda/DAILY/log/amdump.1
planner: time 0.155: setting up estimates for errol:/dev/md0
errol:/dev/md0 overdue 15177 days for level 0
setup_estimate: errol:/dev/md0: command 0, options:
last_level -1 next_level0 -15177 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
planner: time 0.156: setting up estimates took 0.082 secs
planner: time 1.394: got result for host errol disk /dev/md0: 0 ->
-1K, -1 -> -1K, -1 -> -1K
FAILED QUEUE:
0: errol /dev/md0
planner: FAILED errol /dev/md0 20110722 0 [disk /dev/md0 offline on
errol?]
/var/amanda/DAILY/log/log.20110722.0
DISK planner errol /dev/md0
INFO planner Adding new disk errol:/dev/md0.
FAIL planner errol /dev/md0 20110722 0 [disk /dev/md0 offline on
errol?]
--myron
=
Myron Kowalski
MoCoSIN Network/Systems Administrator
Moravian College
my...@cs.moravian.edu <mailto:my...@cs.moravian.edu>
Re: how to specify a linux disk
On Jul 22, 2011, at 12:47 PM, Jean-Louis Martineau wrote: On 07/22/2011 11:37 AM, myron wrote: On Jul 22, 2011, at 11:14 AM, Jean-Louis Martineau wrote: Which amanda release are you using? root@errol:~# dpkg -l | grep amanda ii amanda-client 1:2.6.1p1-2 Advanced Maryland Automatic Network Disk Arc ii amanda-common 1:2.6.1p1-2 Advanced Maryland Automatic Network Disk Arc Which program/application are you using to do the backup. I guess it's tar or dump. Whatever is on linux? How do I find out? In the disklist file If you are using tar, it is better to specify the mount point. I guess it is tar. this is what have in the disklist errol /dev/md0 linux-tar Post all the related client debug files. I don't see any debug files. The only log entry I have from this morning's backup is Then search, amandad.*.debug, sendsize.*.debug amadmin version version | grep AMANDA_DBGDIR Jean-Louis
Re: how to specify a linux disk
On Jul 22, 2011, at 1:04 PM, Frank Smith wrote: On 07/22/2011 11:53 AM, myron wrote: On Jul 22, 2011, at 12:47 PM, Jean-Louis Martineau wrote: On 07/22/2011 11:37 AM, myron wrote: On Jul 22, 2011, at 11:14 AM, Jean-Louis Martineau wrote: Which amanda release are you using? root@errol:~# dpkg -l | grep amanda ii amanda-client 1:2.6.1p1-2 Advanced Maryland Automatic Network Disk Arc ii amanda-common 1:2.6.1p1-2 Advanced Maryland Automatic Network Disk Arc Which program/application are you using to do the backup. I guess it's tar or dump. Whatever is on linux? How do I find out? In the disklist file If you are using tar, it is better to specify the mount point. I guess it is tar. this is what have in the disklist errol /dev/md0 linux-tar Tar deals with filesystems, so you need to either change /dev/md0 to / (or whatever directory is mounted on it), or use dump, which deals with devices. Personally, I'd stick with tar, but others may prefer to use dump. Frank df -h reports these filesystems. So, I should have something like this in disklist. errol /dev/mapper/system-root linux-tar # / errol /dev/mapper/system-home linux-tar # /home errol /dev/mapper/system-var linux-tar # /var errol /dev/mapper/system-scratch linux-tar # /scratch Post all the related client debug files. I don't see any debug files. The only log entry I have from this morning's backup is Then search, amandad.*.debug, sendsize.*.debug amadmin version version | grep AMANDA_DBGDIR Jean-Louis -- Frank Smith fsm...@hoovers.com Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: how to specify a linux disk
On Jul 22, 2011, at 2:23 PM, Jon LaBadie wrote: On Fri, Jul 22, 2011 at 01:18:05PM -0400, myron wrote: On Jul 22, 2011, at 1:04 PM, Frank Smith wrote: Tar deals with filesystems, so you need to either change /dev/md0 to / (or whatever directory is mounted on it), or use dump, which deals with devices. Personally, I'd stick with tar, but others may prefer to use dump. Frank df -h reports these filesystems. So, I should have something like this in disklist. errol /dev/mapper/system-root linux-tar # / errol /dev/mapper/system-home linux-tar # /home errol /dev/mapper/system-var linux-tar # /var errol /dev/mapper/system-scratch linux-tar # /scratch No, as Frank said, tar needs to know what directory to start from; dump needs to know what device to back up. If you run "ls -lL /dev/mapper" you will see that each of your names above are either block or character devices (b or c as first char of line). What you want for tar is: errol / linux-tar errol /home linux-tar errol /var linux-tar errol /scratch linux-tar In this case the 2nd column is both what to back up and the DLE name used in reports. You could also do something like: errol Root / linux-tar errol Home /home linux-tar errol Var /var linux-tar errol Scratch /scratch linux-tar In this case Root, Home, etc., when combined with the host "errol" are the DLE name and /, /home, etc. are where tar is to start. The combined host:name must be unique in the disklist. Jon I think I understand now. We'll see how tonight's backups go. Thanks for your help. -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Volume is not in dump format
I've never had a problem restore files to solaris boxes; however, I'm trying to restore a linux backup, which I've never done. This is the message I got. amrestore: 79: restoring aimserver._dev_hda2.20051216.0 Volume is not in dump format amrestore: 80: reached end of information I see the tape has the image I want. I usually use this command: amrestore -p (drive) aimserver /dev/hda2 | ufsrestore ivf - Is the error telling me that linux has the compressed the image a different way. This is the line from disklist aimserver /dev/hda2linux-tar # /usr --myron
switching between drives
I've been running Amanda (VERSION="Amanda-2.4.3") on a tape server that has two drives, but I've been using only one of the drives. Anyway to configure Amanda to use a different drive each night? --myron
