Amanda-2.4.4p4 - RedHat 7.3 - Samba-3.0
Hi Using the above fine for ann Unix type hosts and of these tar and dump based backups work fine. Just tried to backup my first windows partition last night and it seems to have worked but the dump ran with 'strange' - Can anyone point me in the direction of what might be wrong? FAILED AND STRANGE DUMP DETAILS: /-- titan //printserver/hyperion lev 0 STRANGE sendbackup: start [titan://printserver/hyperion level 0] sendbackup: info BACKUP=/opt/samba/bin/smbclient sendbackup: info RECOVER_CMD=/opt/samba/bin/smbclient -f... - sendbackup: info end ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1433) ? tar: dumped 3546 files and directories ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1434) | Total bytes written: 3155058688 sendbackup: size 3081112 sendbackup: end \ thanks for any help! Tom
Re: Exabyte VXA-2 Packet-Loader and chg-zd-mtx nagging problem
Hi! /usr/sbin/amdump new /bin/mt -f /dev/nst1 offline /usr/sbin/amtape new slot next Amanda changes the tapes as needed, i. e. you don´t need to call amtape (and mt) for that. When testing this manually from the console, I receive the following error message when running the amtape command: amtape new slot next amtape: could not load slot 7: mtx: Request Sense: Long Report=yes However, after a long wait, it in fact DOES perform this command correctly and has the next tape loaded as it should. This is my only nagging bug. What is causing this and how can I fix it ? Hm, from one of your previous posts I´ve seen the SCSI-errors your getting in the syslog. Are there still such errors being reported? I would guess that there´s a problem with the SCSI controller leading to very long timeouts before responses to mtx commands. Thus, mtx times out and gives you the above message, but the command is finally performed after that long wait during which the SCSI controller is being reset and such by the driver. The command has been wating in the queue for the SCSI devices to become ready, and then gets executed. Unless you fix that, amanda might be unable to change tapes automatically because it might have likewise problems with unexpected delays in SCSI command-execution (especially when using mtx on the low level side to do the changes). --- There is sometimes combinations of computers/mainboards and (SCSI-)cards that just don´t work. BTW, the VXA-drive can be used in native mode. Afair, docs only say that the identification strings the drive will answer inquiry commands with can be changed by using different modes, and I don´t think that the modes will change anything else beyond that for the drive uses standard SCSI commands. Does anybody know if this is true? GH
Restore problem - tar backup
Hi Posted earlier about a 'strange' report to do with a windows partition. I'm trying to restore this partition to see what made it onto tape. The issue i'm having is that amanda is ignoring this partition and skipping it. eg amrestore -p /dev/nst0 titan \\printserver\hyperion | tar xvfp - -- snip amrestore: 9: skipping titan.__printserver_hyperion.20050224.0 I have tried escaping the \\ with a $ so had amrestore -p /dev/nst0 titan $\\printserver$\hyperion | tar xvfp - but that yielded the same - Any hints here? The OS of the amanda server where i'm doing this from is RH7.3 thanks!
Re: Restore problem - tar backup
On Thu, Feb 24, 2005 at 12:54:06PM +, Tom Brown enlightened us: Posted earlier about a 'strange' report to do with a windows partition. I'm trying to restore this partition to see what made it onto tape. The issue i'm having is that amanda is ignoring this partition and skipping it. eg amrestore -p /dev/nst0 titan \\printserver\hyperion | tar xvfp - -- snip amrestore: 9: skipping titan.__printserver_hyperion.20050224.0 I have tried escaping the \\ with a $ so had amrestore -p /dev/nst0 titan $\\printserver$\hyperion | tar xvfp - but that yielded the same - Any hints here? The OS of the amanda server where i'm doing this from is RH7.3 thanks! try titan //printserver/hyperion Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpau2luCIHha.pgp Description: PGP signature
Amanda - unable to create temporary directory
Hello, Amanda is successfully running on our Solaris Servers. But on Amanda's report (the E-mail it sends after amdump) I get the following STRANGE message: ? Unable to create temporary directory in any of the directories listed below: ? /tmp/ ? /var/tmp/ ? / But when I manually accessed the server as Amanda user - I had no problem creating a folder under /tmp as well as /var/tmp/ ! Any thoughts why am I getting this message? Additionally, can somebody tell me what files does Amada writes under /tmp folder? Many thanks, gil
Re: Amanda - unable to create temporary directory
Gil, I've managed a few strange things over the years, my errors or compounded bad choices specific to my site... Over tightened security on temp, normal protections are 1777. Configure amanda with one username but modify amanda.conf and choose a different runuser. List of errors goes on but that is all I can think of prior to my 2nd of coffee. You are sure that the user you think is running amanda actually is ? This is a server, client or client/server machine ? I'm pretty sure you can run amdump as one user but configure /etc/inetd.conf to run client as a different user. That is, I'm sure you could but equally certain you don't want to. How do you initiate amdump, crontab for amanda user ? We have at least one system that runs it as bin but does it via a root crontab entry that beings su - bin, this does not simplify debugging. On Thu, Feb 24, 2005 at 09:04:49AM -0500, Gil Naveh wrote: Hello, Amanda is successfully running on our Solaris Servers. But on Amanda's report (the E-mail it sends after amdump) I get the following STRANGE message: ? Unable to create temporary directory in any of the directories listed below: ? /tmp/ ? /var/tmp/ ? / But when I manually accessed the server as Amanda user - I had no problem creating a folder under /tmp as well as /var/tmp/ ! Any thoughts why am I getting this message? Additionally, can somebody tell me what files does Amada writes under /tmp folder? Many thanks, gil --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Restore problem - tar backup
try titan //printserver/hyperion Ah yes - its been a long week! Thanks!
How to reconfigure email notifications?
This sounds like an easy mod, but I can't for the life of me find out where to make the change. Our backup box sends its report emails to [EMAIL PROTECTED] whenever a backup job is completed. However, I just switched the box from sendmail to postfix so that I could do some internal email stuff on it unrelated to backups. The problem is, now I'm no longer receiving email notifications when backup jobs are completed. Can someone tell me where/ how the mail MTA is specified, and how to modify it? Again, I apologize if this is a basic question - I can't seem to find any info on it. Thanks, Matt Emmott
Re: How to reconfigure email notifications?
Matt so what happens if you email out as root to [EMAIL PROTECTED] do the emails arrive? have a look in the maillog for clues.. -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 Matt Emmott wrote: This sounds like an easy mod, but I can't for the life of me find out where to make the change. Our backup box sends its report emails to [EMAIL PROTECTED] whenever a backup job is completed. However, I just switched the box from sendmail to postfix so that I could do some internal email stuff on it unrelated to backups. The problem is, now I'm no longer receiving email notifications when backup jobs are completed. Can someone tell me where/ how the mail MTA is specified, and how to modify it? Again, I apologize if this is a basic question - I can't seem to find any info on it. Thanks, Matt Emmott ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **
Re: Amanda-2.4.4p4 - RedHat 7.3 - Samba-3.0
On Thu, Feb 24, 2005 at 09:19:31AM +, Tom Brown wrote: FAILED AND STRANGE DUMP DETAILS: I posted about this in the last week or two. Look for strange in the list archives. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, Foucault's Pendulum
Re: Amanda-2.4.4p4 - RedHat 7.3 - Samba-3.0
FAILED AND STRANGE DUMP DETAILS: /-- titan //printserver/hyperion lev 0 STRANGE sendbackup: start [titan://printserver/hyperion level 0] sendbackup: info BACKUP=/opt/samba/bin/smbclient sendbackup: info RECOVER_CMD=/opt/samba/bin/smbclient -f... - sendbackup: info end ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1433) ? tar: dumped 3546 files and directories ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1434) | Total bytes written: 3155058688 sendbackup: size 3081112 sendbackup: end \ responding to myself here but seems that this may be due to a samba error? We are using version 3.0.0 and perhaps this does not play nicely with amanda 2.4.4p4 - The backup restored fine though. Anyone know a 'good' 2.4.4p4 and Samba version combo? thanks
Re: Amanda - unable to create temporary directory
Gil Naveh wrote: Amanda is successfully running on our Solaris Servers. But on Amanda's report (the E-mail it sends after amdump) I get the following STRANGE message: ? Unable to create temporary directory in any of the directories listed below: ? /tmp/ ? /var/tmp/ ? / I think these messages are not from amanda but from the dump program, that is invoked by amanda. Are you sure the dump program you use compatible with the filesystem? e.g. ufsdump for ufs filesystems, etc. Try switching to gnutar if you don't mind the longer estimate time. But when I manually accessed the server as Amanda user - I had no problem creating a folder under /tmp as well as /var/tmp/ ! Any thoughts why am I getting this message? Additionally, can somebody tell me what files does Amada writes under /tmp folder? No files at all. Only in /tmp/amanda . -- 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: Amanda-2.4.4p4 - RedHat 7.3 - Samba-3.0
Tom Brown wrote: FAILED AND STRANGE DUMP DETAILS: /-- titan //printserver/hyperion lev 0 STRANGE sendbackup: start [titan://printserver/hyperion level 0] sendbackup: info BACKUP=/opt/samba/bin/smbclient sendbackup: info RECOVER_CMD=/opt/samba/bin/smbclient -f... - sendbackup: info end ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1433) ? tar: dumped 3546 files and directories ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1434) | Total bytes written: 3155058688 sendbackup: size 3081112 sendbackup: end \ responding to myself here but seems that this may be due to a samba error? We are using version 3.0.0 and perhaps this does not play nicely with amanda 2.4.4p4 - The backup restored fine though. Error is a bit a strong word. Samba seems be a gotten a little more verbose again. And amanda is not yet prepared to discard the more verbose messages. I have the same issue with logwatch which sends me tons of unexpected logentries on my machines with samba 3.0 installed. (Had not yet time/energy to filter them out again.) If the strange messages annoy you, you can dive into the source, edit client-src/sendbackup-gnutar.c, find in the beginning of the file a table with the regular expressions and their classificiation and add a pattern that classifies the 3 strange lines as normal. Anyone know a 'good' 2.4.4p4 and Samba version combo? In my experience samba 3 works good. At least the backups are fine. -- 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: Amanda - unable to create temporary directory
On Thu, Feb 24, 2005 at 09:04:49AM -0500, Gil Naveh wrote: Hello, Amanda is successfully running on our Solaris Servers. But on Amanda's report (the E-mail it sends after amdump) I get the following STRANGE message: ? Unable to create temporary directory in any of the directories listed below: ? /tmp/ ? /var/tmp/ ? / But when I manually accessed the server as Amanda user - I had no problem creating a folder under /tmp as well as /var/tmp/ ! Any thoughts why am I getting this message? Additionally, can somebody tell me what files does Amada writes under /tmp folder? I replied to your earlier post on this topic but I don't see my response in my archive of the list. That message is not coming from amanda directly, but coming from ufsdump. Now the question is why ufsdump, running for amanda, can't deal with those directories. I only had one possibility and have little confidence in it. On my system /usr/sbin/ufsdump is a symbolic link to /usr/lib/fs/ufs/ufsdump. The latter program is root-owned, set-uid. Perhaps yours has been altered. $ ls -l /usr/lib/fs/ufs/ufsdump -r-sr-xr-x 1 root bin 83820 Apr 12 2004 /usr/lib/fs/ufs/ufsdump -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda-2.4.4p4 - RedHat 7.3 - Samba-3.0
On Thu, Feb 24, 2005 at 09:19:31AM +, Tom Brown wrote: Hi Using the above fine for ann Unix type hosts and of these tar and dump based backups work fine. Just tried to backup my first windows partition last night and it seems to have worked but the dump ran with 'strange' - Can anyone point me in the direction of what might be wrong? FAILED AND STRANGE DUMP DETAILS: /-- titan //printserver/hyperion lev 0 STRANGE sendbackup: start [titan://printserver/hyperion level 0] sendbackup: info BACKUP=/opt/samba/bin/smbclient sendbackup: info RECOVER_CMD=/opt/samba/bin/smbclient -f... - sendbackup: info end ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1433) ? tar: dumped 3546 files and directories ? [2005/02/24 00:46:52, 0] client/clitar.c:process_tar(1434) | Total bytes written: 3155058688 sendbackup: size 3081112 sendbackup: end \ thanks for any help! Gee, based on my experience, that would be a very clean report of a samba dump. :((My reports always have lots of files and/or directories that could not be backed up because of Windows various permissions and restrictions. The two messages seem to be normal end of smbtar/smbclient reports. Amanda maintains list of messages it ignores and considers normal. Some other types of messages it doesn't recognize but feels the backup went to some form of normal completion and considers them strange, i.e. unrecognized by amanda so the operator must decide if they are of any consequence. If you can put up with reports like this, I'd consider them your norm for that DLE. Alternatively, amanda uses pattern matching (regular expression patterns) to recognize messages to ignore or report. Perhaps amanda was meant to ignore those particular messages, but in your version of samba, the message is subtly altered and the pattern no longer matches it. This has happened before. Things as simple as spacing or capitalization or punctuation could throw off the pattern match. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Backup image tape spanning, a look back and a look ahead...
Gene Heskett [EMAIL PROTECTED] sez: On Wednesday 23 February 2005 10:27, John Stange wrote: snipple Just a note, on the expectation that people will ask after the status of my span/split patch. The most recent release is a patch against 2.4.5, and works pretty well for me. I've had one report of amrecover troubles with it, but I've been unable to reproduce that so far (I use the amfetchdump util that comes with the patch, myself). So, it's not abandoned or anything, just idling for feedback. A url to the patch would have been nice, John. :-) Can I get a duh from the crowd? http://www.cs.umd.edu/~building/span_split_2.4.5-current.patch.gz That's against the 2.4.5b release available on the official AMANDA page, from October. I can whip one up that applies cleanly to the more recent 2.4.5b snapshots, if so desired. I haven't made any efforts to port it to the 2.5.0 tree, because in the grand scheme of things I don't really know what's up with 2.5.0, or for that matter whether the core team thinks my code is the work of a jabbering fool (and, ok, it is, but that may be immaterial to its utility :). -- John Stange, Systems Administrator National Academies Press 202-334-3514
Re: Amanda - unable to create temporary directory
Jon LaBadie said: On my system /usr/sbin/ufsdump is a symbolic link to /usr/lib/fs/ufs/ufsdump. The latter program is root-owned, set-uid. Perhaps yours has been altered. $ ls -l /usr/lib/fs/ufs/ufsdump -r-sr-xr-x 1 root bin 83820 Apr 12 2004 /usr/lib/fs/ufs/ufsdump We actually strip the setuid bit on ufsdump and this seems to work in most circumstances. We had this problem every night on one specific solaris 9 system, and no other sol9 or sol8 systems (and our amanda client is installed via a package, so it's the same across all machines). The solaris boxes are also installed from the same jumpstart images, so they should all behave the same. This error comes from ufsdump, and near as I've been able to tell, ufsdump is creating a directory named something like '.rlg.zyaaGR in each of /tmp and /var/tmp (and failing to be able to in / since it's not running as root, the jibberish after .rlg. changes with each run). This directory is called with mode 000 and then ufsdump attempts to create a file in it, which fails and generates that error message. I wasn't able to get ufsdump to behave better (nor did I look for a patch or try to reset ufsdump to being setuid again) but on that specific system we had amanda incorrectly configured to backup something other than the mountpoint of the filesystem, but something inside the filesystem (that is, instead of /export/home it was /export/home/foo/bar where the filesystem was mounted on /export/home). Switching this to the mountpoint made the error go away. There may be some limitations in ufsdump that cause you only be able to use ufsdump this way if you're root (though sounsd lke a bug). If you're doing this, and doing it on purpose, I'd suggest using gnutar instead of dump since incremental dumps don't work right except on filesystem boundaries. If you're not doing this and actually backing up a mountpoint, then maybe the above info will help track it down. (perhaps the setuid bit, as Jon suggests). -Todd
Re: Amanda's report
Jon and others are correct that this message is coming from ufsdump when it
is run as a user other than root. For instance when run as amanda:
$ /usr/sbin/ufsdump 0Ssf 1048576 - /dev/md/rdsk/d92
Unable to create temporary directory in any of the directories listed
below:
/tmp/
/var/tmp/
/
Please correct this problem and rerun the program.
43413422080
and when run as root:
/usr/sbin/ufsdump 0Ssf 1048576 - /dev/md/rdsk/d92
43413422080
When I do truss -o /var/tmp/truss.output /usr/sbin/ufsdump 0Ssf 1048576 -
/dev/md/rdsk/d92 the following results:
lstat64(.rlg.10aqFe, 0xFFBFE2B8) Err#2 ENOENT
mkdir(/tmp/.rlg.10aqFe, 0)= 0
mkdir(/tmp/.rlg.10aqFe/.rlg.10aqFe, 0)= 0
mount(/dev/md/dsk/d92, /tmp/.rlg.10aqFe/.rlg.10aqFe,
MS_RDONLY|MS_DATA|MS_OP
TIONSTR, ufs, 0xFFBFEBBC, 4) = 0
umount2(/dev/md/dsk/d92, 0x) = 0
rmdir(/tmp/.rlg.10aqFe/.rlg.10aqFe) = 0
rmdir(/tmp/.rlg.10aqFe) = 0
and when run as amanda:
Truss will not work on suid applications.
So, you can see that ufsdump is attempting to create directories with names
of the form .rlg.*
Now, my permissions on ufsdump are as follows:
# ls -lad /usr/sbin/ufsdump
lrwxrwxrwx 1 root root 21 Sep 22 12:51 /usr/sbin/ufsdump -
../lib/fs/ufs/ufsdump
and
# ls -lad /usr/lib/fs/ufs/ufsdump
-r-sr-xr-x 1 root bin87508 Apr 12 2004
/usr/lib/fs/ufs/ufsdump
On Wed, Feb 23, 2005 at 03:22:01PM -0600, Karl W. Burkett wrote:
I'm having the same problem. I'll provide what additional information
I have:
Operating system: Solaris 5.9 on amanda server and client
amanda version: 2.4.4p3
problem happens in both sendbackup and sendsize
There seems to be a problem with permissions being created on
some temporary directories ( in /tmp in this case ):
$ ls -la /tmp
total 178
drwxrwxrwt 12 root sys 867 Feb 23 08:30 .
drwxr-xr-x 24 root root1024 Feb 21 22:48 ..
d- 2 amanda backup 117 Feb 23 04:00 .rlg.iDa4R3
d- 2 amanda backup 117 Feb 23 04:00 .rlg.o3aiS3
d- 2 amanda backup 117 Feb 23 04:23 .rlg.uUaWT3
drwx-- 2 amanda backup 718 Feb 23 04:23 amanda
As you can see, amanda has no write permission in .rlg*, though I
am getting the debug files in /tmp/amanda. This could be the source
of the problem, though I've no idea how to fix this. Could it be a
umask issue when amandad is called from inetd?
Speaking of the debug files, here are a couple that provide a little
more information on the issue:
::
sendbackup.20050223042349.debug
::
sendbackup: debug 1 pid 28523 ruid 479 euid 479: start at Wed Feb 23
04:23:49 20
05
/usr/site/amanda-2.4.4p3/libexec/sendbackup: version 2.4.4p3
parsed request as: program `DUMP'
disk `/dev/md/rdsk/d92'
device `/dev/md/rdsk/d92'
level 0
since 1970:1:1:0:0:0
options `|;bsd-auth;no-record;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.000: stream_server: waiting for connection:
0.0.0.0.50045
sendbackup: time 0.000: stream_server: waiting for connection:
0.0.0.0.50046
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.50047
sendbackup: time 0.001: waiting for connect on 50045, then 50046, then
50047
sendbackup: time 0.004: stream_accept: connection from
172.23.247.34.50070
sendbackup: time 0.005: stream_accept: connection from
172.23.247.34.50071
sendbackup: time 0.007: stream_accept: connection from
172.23.247.34.50072
sendbackup: time 0.007: got all connections
sendbackup: time 0.010: dumping device '/dev/md/rdsk/d92' with ''
sendbackup: time 0.011: spawning /usr/sbin/ufsdump in pipeline
sendbackup: argument list: dump 0sf 1048576 - /dev/md/rdsk/d92
sendbackup: time 0.016: started index creator: /usr/sbin/ufsrestore
-tvf - 21
| sed -e '
s/^leaf[]*[0-9]*[ ]*\.//
t
/^dir[ ]/ {
s/^dir[ ]*[0-9]*[ ]*\.//
s%$%/%
t
}
d
'
sendbackup: time 0.024: 117: strange(?): Unable to create temporary
directory in
any of the directories listed below:
sendbackup: time 0.026: 117: strange(?):/tmp/
sendbackup: time 0.029: 117: strange(?):/var/tmp/
sendbackup: time 0.031: 117: strange(?):/
sendbackup: time 0.033: 117: strange(?): Please correct this problem
and rerun t
he program.
sendbackup: time 0.188: 93: normal(|): DUMP: Date of this level 0
dump: Wed
I don't have any idea. Just the comment that the message Unable ...
is coming from ufsdump, not from any of the amanda code.
On my x86 Solaris 9, ufsdump, in /usr/sbin, is a symbolic link to
/usr/lib/fs/ufs/ufsdump. That program is set uid, root owned.
Perhaps your's has been altered.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG
Switching to GNUTAR - RE: Amanda - unable to create temporary directory
Thanks for the help, At this point it seems that the best way for us is to switch from ufsdump to gnutar. But before doing so - what will happen with the backups that I did so far? (I backed our data on a tape drive). Does ufsdump and gnutar stores the data the same way? (Does ufsdump level 0,1... is identical to gnutar level 0,1...) Or does it store the data on a different format? Does Gnutar is going to store the data twice or is it going to overwrite the data that was stored by ufsdump? Any other concerns that I should keep in mind before switching from ufsdump to gnutar? Thanks, gil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Todd Kover Sent: Thursday, February 24, 2005 12:37 PM To: amanda-users@amanda.org Subject: Re: Amanda - unable to create temporary directory Jon LaBadie said: On my system /usr/sbin/ufsdump is a symbolic link to /usr/lib/fs/ufs/ufsdump. The latter program is root-owned, set-uid. Perhaps yours has been altered. $ ls -l /usr/lib/fs/ufs/ufsdump -r-sr-xr-x 1 root bin 83820 Apr 12 2004 /usr/lib/fs/ufs/ufsdump We actually strip the setuid bit on ufsdump and this seems to work in most circumstances. We had this problem every night on one specific solaris 9 system, and no other sol9 or sol8 systems (and our amanda client is installed via a package, so it's the same across all machines). The solaris boxes are also installed from the same jumpstart images, so they should all behave the same. This error comes from ufsdump, and near as I've been able to tell, ufsdump is creating a directory named something like '.rlg.zyaaGR in each of /tmp and /var/tmp (and failing to be able to in / since it's not running as root, the jibberish after .rlg. changes with each run). This directory is called with mode 000 and then ufsdump attempts to create a file in it, which fails and generates that error message. I wasn't able to get ufsdump to behave better (nor did I look for a patch or try to reset ufsdump to being setuid again) but on that specific system we had amanda incorrectly configured to backup something other than the mountpoint of the filesystem, but something inside the filesystem (that is, instead of /export/home it was /export/home/foo/bar where the filesystem was mounted on /export/home). Switching this to the mountpoint made the error go away. There may be some limitations in ufsdump that cause you only be able to use ufsdump this way if you're root (though sounsd lke a bug). If you're doing this, and doing it on purpose, I'd suggest using gnutar instead of dump since incremental dumps don't work right except on filesystem boundaries. If you're not doing this and actually backing up a mountpoint, then maybe the above info will help track it down. (perhaps the setuid bit, as Jon suggests). -Todd
Re: Amanda's report
On Thu, Feb 24, 2005 at 12:52:17PM -0600, Karl W. Burkett wrote: Jon and others are correct that this message is coming from ufsdump when it is run as a user other than root. For instance when run as amanda: $ /usr/sbin/ufsdump 0Ssf 1048576 - /dev/md/rdsk/d92 Unable to create temporary directory in any of the directories listed below: /tmp/ /var/tmp/ / Please correct this problem and rerun the program. 43413422080 and when run as root: /usr/sbin/ufsdump 0Ssf 1048576 - /dev/md/rdsk/d92 43413422080 When I do truss -o /var/tmp/truss.output /usr/sbin/ufsdump 0Ssf 1048576 - /dev/md/rdsk/d92 the following results: lstat64(.rlg.10aqFe, 0xFFBFE2B8) Err#2 ENOENT mkdir(/tmp/.rlg.10aqFe, 0)= 0 mkdir(/tmp/.rlg.10aqFe/.rlg.10aqFe, 0)= 0 mount(/dev/md/dsk/d92, /tmp/.rlg.10aqFe/.rlg.10aqFe, MS_RDONLY|MS_DATA|MS_OP TIONSTR, ufs, 0xFFBFEBBC, 4) = 0 umount2(/dev/md/dsk/d92, 0x) = 0 rmdir(/tmp/.rlg.10aqFe/.rlg.10aqFe) = 0 rmdir(/tmp/.rlg.10aqFe) = 0 and when run as amanda: Truss will not work on suid applications. For this situation, as root run something like: truss -f ... su -c amanda ufsdump ... You will be running truss as root and following (-f) any child processes created by the primary command (su) which will change its id and run the app you really want to trace. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Switching to GNUTAR - RE: Amanda - unable to create temporary directory
Gil, I'm confused, why would suid be needed on ufsdump - isn't it run beneith the amanda program (/usr/local/libexec/) rundump which is suid ? For recovery, personally I use amrestore and pipe it to the required utility so as long as I can figure that out (and its imbedded into the first block on of the archive) its not a big deal. On Thu, Feb 24, 2005 at 01:14:03PM -0500, Gil Naveh wrote: Thanks for the help, At this point it seems that the best way for us is to switch from ufsdump to gnutar. But before doing so - what will happen with the backups that I did so far? (I backed our data on a tape drive). Does ufsdump and gnutar stores the data the same way? (Does ufsdump level 0,1... is identical to gnutar level 0,1...) Or does it store the data on a different format? Does Gnutar is going to store the data twice or is it going to overwrite the data that was stored by ufsdump? Any other concerns that I should keep in mind before switching from ufsdump to gnutar? Thanks, gil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Todd Kover Sent: Thursday, February 24, 2005 12:37 PM To: amanda-users@amanda.org Subject: Re: Amanda - unable to create temporary directory Jon LaBadie said: On my system /usr/sbin/ufsdump is a symbolic link to /usr/lib/fs/ufs/ufsdump. The latter program is root-owned, set-uid. Perhaps yours has been altered. $ ls -l /usr/lib/fs/ufs/ufsdump -r-sr-xr-x 1 root bin 83820 Apr 12 2004 /usr/lib/fs/ufs/ufsdump We actually strip the setuid bit on ufsdump and this seems to work in most circumstances. We had this problem every night on one specific solaris 9 system, and no other sol9 or sol8 systems (and our amanda client is installed via a package, so it's the same across all machines). The solaris boxes are also installed from the same jumpstart images, so they should all behave the same. This error comes from ufsdump, and near as I've been able to tell, ufsdump is creating a directory named something like '.rlg.zyaaGR in each of /tmp and /var/tmp (and failing to be able to in / since it's not running as root, the jibberish after .rlg. changes with each run). This directory is called with mode 000 and then ufsdump attempts to create a file in it, which fails and generates that error message. I wasn't able to get ufsdump to behave better (nor did I look for a patch or try to reset ufsdump to being setuid again) but on that specific system we had amanda incorrectly configured to backup something other than the mountpoint of the filesystem, but something inside the filesystem (that is, instead of /export/home it was /export/home/foo/bar where the filesystem was mounted on /export/home). Switching this to the mountpoint made the error go away. There may be some limitations in ufsdump that cause you only be able to use ufsdump this way if you're root (though sounsd lke a bug). If you're doing this, and doing it on purpose, I'd suggest using gnutar instead of dump since incremental dumps don't work right except on filesystem boundaries. If you're not doing this and actually backing up a mountpoint, then maybe the above info will help track it down. (perhaps the setuid bit, as Jon suggests). -Todd --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
new problem with the Exabyte VXA-2 packet-loader system
The Exabyte lack of timely tech support may be hurting them. I get better help through this forum which may discourage people from purchasing from Exabyte. I have great success with the first round of 10 tapes with the autoloader. Each day, a new tape was loaded and the AMANDA backup performed correctly. Then I unloaded all 10 tapes (exported in Exabyte terminology) and proceeded to load a cleaning tape to clean the drive. I placed the cleaning tape into the slot using the import command from the autoloader console. The door closed and the system proceeded to lock up completed. It looks like the cartridge is stuck somehow. Nothing at all will work now. I cannot unload the cartridge. All I get is an error message at the console H/W Inoperable Servo Error Anyone else with this experience ? How do I remove the cartridge and try again ?
Re: new problem with the Exabyte VXA-2 packet-loader system
This request did not seem to go through. Try again. On Thu, 2005-02-24 at 09:17 -0500, James D. Freels wrote: The Exabyte lack of timely tech support may be hurting them. I get better help through this forum which may discourage people from purchasing from Exabyte. I have great success with the first round of 10 tapes with the autoloader. Each day, a new tape was loaded and the AMANDA backup performed correctly. Then I unloaded all 10 tapes (exported in Exabyte terminology) and proceeded to load a cleaning tape to clean the drive. I placed the cleaning tape into the slot using the import command from the autoloader console. The door closed and the system proceeded to lock up completed. It looks like the cartridge is stuck somehow. Nothing at all will work now. I cannot unload the cartridge. All I get is an error message at the console H/W Inoperable Servo Error Anyone else with this experience ? How do I remove the cartridge and try again ?
Re: Switching to GNUTAR - RE: Amanda - unable to create temporary directory
On Thu, Feb 24, 2005 at 02:16:36PM -0500, Brian Cuttler wrote: Gil, I'm confused, why would suid be needed on ufsdump - isn't it run beneith the amanda program (/usr/local/libexec/) rundump which is suid ? It is not an amanda requirement, it is the way the system supplies ufsdump. I suspect it is so that things like /etc/dumpdates can be updated. Though I'm not sure /etc/dumpdates gets updated when ufsdump is run by an ordinary user. I'm pretty sure that if run by an ordinary user ufsdump would switch id's to do the actual reading of files so that the ordinary user does not get to backup files they are not allowed to see under normal circumstances. But there may be a few tasks that require root privleges outside of the actual dumping. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Switching to GNUTAR - RE: Amanda - unable to create temporary directory
On Thu, Feb 24, 2005 at 01:14:03PM -0500, Gil Naveh wrote: At this point it seems that the best way for us is to switch from ufsdump to gnutar. But before doing so - what will happen with the backups that I did so far? (I backed our data on a tape drive). If you change the program in your dumptype from DUMP to GNUTAR, you will not be able to use amrecover to get your data back from the earlier backups. Newer backups yes, older ones no. You could use amrestore and the appropriate dump program or you could temporarily reset the program parameter while you do your amrecover. Does ufsdump and gnutar stores the data the same way? (Does ufsdump level 0,1... is identical to gnutar level 0,1...) Or does it store the data on a different format? Same way as far as dumplevels are concerned, but the storage format is totally different. Does Gnutar is going to store the data twice or is it going to overwrite the data that was stored by ufsdump? I don't get what you are asking by the twice question. But amanda does not overwrite things because you change a parameter. Only when a tape gets reused will the old dump data be overwritten. Any other concerns that I should keep in mind before switching from ufsdump to gnutar? Unix systems keep 3 timestamps for each file. Because a dump program avoids accessing the files via the normal filesystem calls, these time stamps are not altered by backing up a file. Tar does work with normal filesystem calls. At least one of the 3 timestames will be affected, either the last time the file was read (shows with ls -la) or the last time the file properties were changed (shows with ls -lc). If you do choose to make the switch, I suggest you do it a few DLE's at a time. Change their dumptypes and then uses amadmin to force a level 0 dump for that DLE the next run. A tar level 1 or 2 will not be much use with a ufsdump level 0. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Todd Kover Sent: Thursday, February 24, 2005 12:37 PM To: amanda-users@amanda.org Subject: Re: Amanda - unable to create temporary directory Jon LaBadie said: Still can't get you delete superfluous stuff and to bottom or inline post huh? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda's report
On Thu, Feb 24, 2005 at 12:52:17PM -0600, Karl W. Burkett wrote: mount(/dev/md/dsk/d92, /tmp/.rlg.10aqFe/.rlg.10aqFe, MS_RDONLY|MS_DATA|MS_OP TIONSTR, ufs, 0xFFBFEBBC, 4) = 0 That'd be the fundamental reason that ufsdump wants root. That it fails to create the temp directory otherwise, turns out to be pretty irrelevent, since what it does with the thing requires root in the first place :-/ One can only guess what it's doing, but from Jon(?)'s observation that the problem only arises on partial-filesystem dumps, my guess would be that it's figuring out which inodes to dump by traversing the file system via readdir() like any other process -- even though it does the actual backup directly, via the special file. Well, I've seen things done in even-weirder ways... -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, Foucault's Pendulum
Re: Backup image tape spanning, a look back and a look ahead...
On Thursday 24 February 2005 09:08, John Stange wrote: Gene Heskett [EMAIL PROTECTED] sez: On Wednesday 23 February 2005 10:27, John Stange wrote: snipple Just a note, on the expectation that people will ask after the status of my span/split patch. The most recent release is a patch against 2.4.5, and works pretty well for me. I've had one report of amrecover troubles with it, but I've been unable to reproduce that so far (I use the amfetchdump util that comes with the patch, myself). So, it's not abandoned or anything, just idling for feedback. A url to the patch would have been nice, John. :-) Can I get a duh from the crowd? Duh... http://www.cs.umd.edu/~building/span_split_2.4.5-current.patch.gz That's against the 2.4.5b release available on the official AMANDA page, from October. I can whip one up that applies cleanly to the more recent 2.4.5b snapshots, if so desired. If its not too much trouble John, I'd appreciate it. I haven't made any efforts to port it to the 2.5.0 tree, because in the grand scheme of things I don't really know what's up with 2.5.0, or for that matter whether the core team thinks my code is the work of a jabbering fool (and, ok, it is, but that may be immaterial to its utility :). -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Windows client to use?
Hello! We have our amanda server running on Linux, we use large disks as backup medium and it works great.. However, I am not sure which windows client to use for our Windows 2000 server machine.. Can anyone point me to which client I should use? Regards, -turgut -- Turgut Kalfaoglu Manager,EgeNet Internet Services http://www.egenet.com.tr
Amanda indexing and multiple backup rotations
Hello, A question about amanda's indexing and database Short version: Does a mechanism to share databases exist in amanda? Long version: (best with an example) I want 4 different configurations. All but one will be in offsite storage. I want different configurations because then I will be assured that each tapeset I have in the changer will be a complete set that I change out each week for a new set. example: five configurations: Daily1-5 dumpcycle = five weeks runspercycle = 7 days worth tapecyle = as many as needed to be complete... disklist, changer.conf, and common parts of amanda.conf files would be hardlink shared between all configurations. Each week cron would use a different configuration, and so long as the dumpdates don't overlap, they won't interfere with each other. The problem: to do a restore, I would need to remember or calculate What configuration was used during the targeted backup time. The solution (I think): make a parent configuration of all of the configurations that can be queried. the act of setting a restore date would tell the parent config what database to use. Has someone already done this, or is work proceeding along these lines? --jason ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 Email to: [EMAIL PROTECTED] Twiki: http://twiki.wrs.com/do/view/Main/JasonBrooks Senior Systems Administration Analyst Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
Re: Windows client to use?
If I understand your question correctly, you are looking for smbclient; which is being called by Amanda in case of backing up an smb server (your windowsserver) smbclient is part of the Samba suite. In your amanda disklist you would have sth. like this : localhost //WindowsServerName/WindowShareName server-compress in your /etc/amandapass there would be an entry like this : //WindowServerName/WindowsShareName domainuserwithaccess%passwordforthisuser HTH Bert turgut kalfaoglu [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 02/24/2005 11:07 AM To amanda-users@amanda.org cc Subject Windows client to use? Hello! We have our amanda server running on Linux, we use large disks as backup medium and it works great.. However, I am not sure which windows client to use for our Windows 2000 server machine.. Can anyone point me to which client I should use? Regards, -turgut -- Turgut Kalfaoglu Manager,EgeNet Internet Services http://www.egenet.com.tr
RE: Windows client to use?
If you don't want to back everything up on the samba share, an easy way of excluding files/directories are to just deny the backup user account access at all. I found this works a lot better than trying to get an exclude statement working w/ SMB, but the trick only works with NTFS. --Nick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: Thursday, February 24, 2005 10:26 PMTo: turgut kalfaogluCc: amanda-users@amanda.org; [EMAIL PROTECTED]Subject: Re: Windows client to use? If I understand your question correctly, you are looking for smbclient; which is being called by Amanda in case of backing up an smb server (your windowsserver) smbclient is part of the Samba suite. In your amanda disklist you would have sth. like this : localhost //WindowsServerName/WindowShareName server-compress in your /etc/amandapass there would be an entry like this : //WindowServerName/WindowsShareName domainuserwithaccess%passwordforthisuser HTH Bert turgut kalfaoglu [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 02/24/2005 11:07 AM To amanda-users@amanda.org cc Subject Windows client to use? Hello!We have our amanda server running on Linux, we use large disks as backup mediumand it works great.. However, I am not sure which windows client to use for ourWindows 2000 server machine.. Can anyone point me to which client I should use?Regards, -turgut-- Turgut KalfaogluManager,EgeNet Internet Serviceshttp://www.egenet.com.tr
Re: Amanda indexing and multiple backup rotations
On Thu, Feb 24, 2005 at 04:44:29PM -0800, Brooks, Jason wrote: Hello, A question about amanda's indexing and database Short version: Does a mechanism to share databases exist in amanda? Long version: (best with an example) I want 4 different configurations. All but one will be in offsite storage. I want different configurations because then I will be assured that each tapeset I have in the changer will be a complete set that I change out each week for a new set. Before even attempting an answer I have a question. What, for your needs, are the properties of a complete tapeset? It sounds like you are thinking of traditional backup systems where you do a monster dump of everything on day zero and then tiny incrementals til the next monster dump. In such a scheme you need the monster dump or none of the little dumps are valid. So they form nice discreet sets. Amanda spreads the level 0 dumps across then entire dumpcycle. So there is no discreet starting point to a set of tapes. If your dumpcycle is 7 days and you do a run every days (runspercycle) then the Monday - Sunday tapes are as valid a set as the Wednesday - Tuesday. Any 7 sequential tapes is a set. example: five configurations: Daily1-5 dumpcycle = five weeks runspercycle = 7 days worth dumpcycle is the 'maximum' time you want amanda to allow between level 0 dumps. Do you really only want a full dump every 35 days? I suspect what you want is a dumpcycle of 7 days and runspercycle 7 (note, no units). -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
