Re: tapetype recommendations
Brandon D. Valentine wrote: My quarrel seems to be with the fact that amanda is attempting to backup more data than will fit on a single tape. This might not be a tapetype problem, but it seems the logical place to start twiddling. It may be that planner is unable to get good estimates for some of this data so what it thought would compress to 35GB only became 46GB post dump. That's probably the case. Planner gets an estimate of the uncompressed sizes, and makes an educated guess to what ratio it will compress. For it's education it uses the history of the last three dumps and computes an average. If it has no history, it assumes by default 50% (but you can change that in your dumptype with the comprate parameter). If for some reason, the data does not compress as well as it did in the past (e.g. because someone replaced an almost empty database with the same amount of mp3 files -- it happened to me) dumper has to consume a lot more data than planner thought it would. Also when the default compression ratio is 50%, and you dump the first time a disk full of already compressed files, the estimates are way off. That's why I set the default compression ratio to 90% (comprate .90). I've set length in tapetype to 33000mb, a good 2GB below what the tape will theoretically hold. Worst case scenario is that Amanda uses powers of 2 to define tape size and Sony uses powers of 10. If this is the case then 33000*1024*1024/1000/1000 = 34603 so I should still be safe. Actually, amanda informs you about the exact place where it bumped into EOT: taper: tape Daily06 kb 34136032 fm 42 writing file: No space left on device That is 34136032 / 1024 = 5 Mb (Or should i count (34136032 + 42 * 500) / 1024 = 33356 Mb So you're indeed on the safe side with 33000 mb capacity in your tapetype. I would investigate the details, and see if you got any new disks, or if any disk changed it's contents and compression ratio suddenly. -- Paul Bijnens, Lant Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 http://www.lant.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 * ***
Verifying backups
Hello, How do people verify their backups? Are there some nifty scripts or tools available somewhere. Restoring 20GB+ of data just to find out that tar or dump has trashed some of the data is a tediuos task. Especially because you know you have to do it again when the problem is fixed to ensure that the data really is ok. Checking the history of both tar and dump reveals so many issues that one has to wonder if it is ever possible to guarantee a safe backup on a linux box. Some cron task that could do a file to file compare or md5 compare would really help me sleep at night. Regards, Ole Kaas
RE: Shit
If you know how to read...and I'm assuming you do since you can type...go to www.amanda.org and read the instructions. If that is too difficult I've pasted them below. (And in the future keep your profanity to yourself, it's unprofessional and uncalled for) pasted from amanda site Please note: To subscribe or unsubscribe to a mailing list, DO NOT, EVER, send mail to that list. Send mail to listname[EMAIL PROTECTED] with the following line in the body of the message: subscribe your-email-address and when you want to unsubscribe, use the following line in the body: unsubscribe your-email-address where listname is one of the following: amanda-announce The amanda-announce mailing list is for important announcements related to the Amanda Network Backup Manager package, including new versions, contributions, and fixes. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-users The amanda-users mailing list is for questions and general discussion about the Amanda Network Backup Manager. This package and related files are available via anonymous FTP from ftp.amanda.org in the pub/amanda directory. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-hackers The amanda-hackers mailing list is for discussion of the technical details of the Amanda package, including extensions, ports, bugs, fixes, and alpha testing of new versions. To subscribe, send a message to [EMAIL PROTECTED] -Original Message- From: Roy Andrè Tollefsen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Shit Hello amanda-users, Can someone please tell how we can unsubscribe from this list? For the last time ... I call this spam -- geworth
Re: amrestore open the tape RW
On Wed, Dec 05, 2001 at 05:20:19PM +0100, Nicolae Mihalache wrote: Jean-Louis Martineau wrote: On Tue, Dec 04, 2001 at 09:37:08PM +0100, Nicolae Mihalache wrote: Hello! I'm using amanda for tapeless operation (using file: types) and write the data created on DVD. When I try to resore directly from DVD using amrestore, it complains that the DVD is mounted read-only. I've seen that it tries to open the info file in read-write mode, is this really needed? What if the info file remains unchanged during restore? You should write only the 'data' directory to the DVD. The 'info' file need to be r/w. And how do I restore directly from DVD if the info file is not there? Amanda will still try to create it. Maybe by making a symbolic link to the data directory from a writable file system that will be set as restore tape. Or you can mount de DVD on the data directory. Anyway I found a tricky solution to this problem. I create the info file as a symbolic link to /tmp/info (or other file). Then amrestore, will open the /tmp/info, that is writeable. For symbolic links on iso9660, I guess that the Rockridge extension is needed. But that was needed anyway for the filenames that amanda creates in data directory. That's dangerous, anybody can create /tmp/info with a symbolic to any file other file. I hope you don't run amanda as root or bin? I'm preparing an amanda configuration for someone with little sys admin knowledge, and I want that restore be as simple as possible. For this, I use a multi-tape configuration with backup in multiple directories, and after amdump is run, a script takes the backup and put the data on DVD. It also update another file that contains the mapping between tapes and DVDs. For the restore, I've modified a little bit amrecover and amindexd to send together with the tape, the media on which that tape is. And also amrestore will run amtape to assure that the correct tape is in the drive. That means setting a symbolic link from the tapedev that is defined in amanda.conf to the right directory. So for restoring one only need to put the correct media inside and to mount it over the backup directory, and all the restore will be done automatically. If someone is interested in my setup, please tell me, I'd be glad to help. mache -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
RE: Problem with windows 2000 Professional
Hi, I have problem with Win2k Server SP2 also. My environment is: Amanda 2.4.2p2 server running on Solaris 8 Samba 2.2.2 running on same Solaris 8 box Win2k Server version SP2 (Japanese) GNU tar 1.3.23(?) I can see the amdump pulling file names from the Win2k machine by monitor the network packet. I think after it got all file list from the PC, it stops there. The CPU and network becomes idle. Using Ctrl-C can stop it. There is no any error message in the dump or log file. I can use the amanda to backup the Solaris local disk partition without any problem. And I can use smbclient to connect to the Win2K server and retrieve file. (I don't know how to combine smbclient with gnutar manually, so I didn't try it.) Does anyone have an idea that I can try ? Thank you very much in advance, Shu Liu On Mon, 3 Dec 2001, Amanda Admin wrote: Christophe, I use the samba package extensively (2.2.1a), though not for backup with amanda (yet) as you are trying. I tried a simple tar test using smbclient and had no problems. I connected to the client (my laptop, Win2k SP2, NTFS) from my amanda server (RH 7.1) as both myself and as my amanda user (member of the local Backup Operators group). Tarred up about 800K worth of files no problem. Then tested a bigger set of files (116 files, 46 directories, 550MB) also with no problems. Suspecting it might be disk space issue, I even tried this last test in a directory with not enough disk space to hold the resulting tar file. It failed as expected, but never froze. Try running your smbclient tests with a debug level of 3 and a log file (smbclient -l log -d 3) and see what the log says if/when the freeze occurs. Increasing the log level (up to 10) will give you incredible amounts of information (every function entry I believe). Also, check the Event Log on the client. Does the freezing only occur with one client or do other 2000 clients behave similarly? If not every client behaves the same, check permissions and/or service packs. I suspect the freeze occurs because the file may be in use. Or, if the tar is running for some time, perhaps a network problem. I searched the samba lists I'm a member of ([EMAIL PROTECTED], [EMAIL PROTECTED]) and didn't see any posts from yourself. You may try posting there also, check samba.org for the appropriate list (samba-users?). HTH, Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christophe Condomines Sent: Thursday, November 29, 2001 7:09 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Problem with windows 2000 Professional Hi, I am testing Amanda for my backup solution. I use Amanda 2.2.4p2 on a Linux Red Hat 7.1 and without any tape for the test. The backup works fine on linux. I use samba 2.2.2 for the windows clients : that works with NT and 98, but on windows 2000, the amdump starts and finally freeze. I have checked the use of smbclient and a command like tar c test.tar produces the same freeze : smbclient starts to retrieve some files and finally stop. It's not always on the same file, it's not always the same size, ... Any suggestion ? I also try the amanda win32 client, failed on win95, works on win2k but very slowly. Any comments ? = Christophe Condomines [EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Courrier : http://courrier.yahoo.fr
Re: [Amanda-users] Re: amverify failing alot.
On Wed, Dec 05, 2001 at 07:35:32PM -0800, Dan Wilder wrote: Maybe I missed your earlier post. What error messages are you seeing? What happens if you try just dding a big file to a tape then reading it back in the same way, and checking its integrity? I can dd a file say 200MB and read it back and the md5sums match. when using amverify I get: Loading current slot... Using device /dev/scsi/host1/bus0/target15/lun0/mtn Volume MonthlySet101, Date 20011205 Checked set.ext.tsa._etc.20011205.0 Checked sobek.tsa._etc.20011205.0 Checked imhotep.ext.tsa._etc.20011205.0 Checked bart.tsa._home.20011205.0 Checked sothis.tsa._sothis_projects1.20011205.0 Checked sothis.tsa._etc.20011205.0 Checked sobek.tsa._sobek.20011205.0 Checked sothis.tsa._sothis_projects3.20011205.0 Checked imhotep.ext.tsa._imhotep.20011205.0 Checked set.ext.tsa._mnt_hdc1.20011205.0 End-of-Tape detected. Loading next slot... Using device /dev/scsi/host1/bus0/target15/lun0/mtn Volume MonthlySet102, Date 20011203 Checked hathor.tsa._hathor_httpd.20011203.0 ** Error detected (apophos.tsa._apophos.20011203.0) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring apophos.tsa._apophos.20011203.0 /bin/tar: Skipping to next header /bin/tar: Error exit delayed from previous errors 64+0 records in 64+0 records out Checked sothis.tsa._sothis_projects1.20011203.0 Checked hathor.tsa._hathor_projects4.20011203.0 ** Error detected (hathor.tsa._hathor_projects1.20011203.0) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring hathor.tsa._hathor_projects1.20011203.0 amrestore: read error: Input/output error /bin/tar: Unexpected EOF in archive /bin/tar: Error is not recoverable: exiting now 64+0 records in 64+0 records out ** Error detected () amrestore: error reading file header: Input/output error ** No header 0+0 records in 0+0 records out ** Error detected () amrestore: error reading file header: Input/output error ** No header 0+0 records in 0+0 records out ** Error detected () amrestore: error reading file header: Input/output error ** No header 0+0 records in 0+0 records out ** Error detected () amrestore: error reading file header: Input/output error ** No header 0+0 records in 0+0 records out Too many errors. as you can see the first tape went alright but then the second screwed up, these are both reasonably new tapes. but I also get this on our Daily set as well. it will be okay for two or three and then screw up like this for the next couple. msg08735/pgp0.pgp Description: PGP signature
Re: Shit
On Wed, 2001-12-05 at 11:22, Roy Andrè Tollefsen wrote: For the last time ... I call this spam I call it incompetency. ;) http://www.amanda.org /dab -- david a. brooks * systems administrator * stayonline.net * voice: .. 770/933-0600 x217 * email: .. [EMAIL PROTECTED] * :wq!
Help needed, problems with amrecover: weird no index messages on the tape server and never connects from Linux client
Greetings, My backups are running now, but i'm having problems using amrecover; I added all the amanda services on the /etc/inetd.conf (/etc/xinetd.d/amanda on the linux client) and in the /etc/services. Here are the tests i performed: On the Solaris Tape Server (Solaris 7): # /home/amanda/checkPorts amanda udp amanda/udp: 10080 # /home/amanda/checkPorts amandaidx tcp amandaidx/tcp: 10082 # /home/amanda/checkPorts amidxtape tcp amidxtape/tcp: 10083 And i ran the amcheck program too (i'm using the last backup tape on purpouse i'll change it today): amcheck NEWBREAK Amanda Tape Server Host Check - Holding disk /export/data06/amanda-hold-disk-temp: 5270139 KB disk space available, that's plenty Holding disk /home/amanda/holding-disk: 2748691 KB disk space available, that's plenty ERROR: cannot overwrite active tape NEWBREAK_03 (expecting tape NEWBREAK_04 or a new tape) NOTE: skipping tape-writable test Server check took 5.574 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 0.206 seconds, 0 problems found (brought to you by Amanda 2.4.2) Error #1: I ran amrecover on the tape server: # /home/amanda/sbin/amrecover NEWBREAK AMRECOVER Version 2.4.2. Contacting server on lenbkx0001 ... 220 lenbkx0001 AMANDA index server (2.4.2) ready. 200 Access OK Setting restore date to today (2001-12-06) 200 Working date set to 2001-12-06. 200 Config set to NEWBREAK. 501 No index records for host: lenbkx0001. Invalid? Trying lenbkx0001 ... 501 No index records for host: lenbkx0001. Invalid? Trying lenbkx0001.newbreak.com ... 501 No index records for host: lenbkx0001.newbreak.com. Invalid? amrecover What are these No index records messages?. I'm using dump for the Solaris Servers and clients and GNU tar for the Linux clients. Error #2: Running amrecover on the Linux client [root@lnxsrv0001 /root]# amrecover NEWBREAK AMRECOVER Version 2.4.2. Contacting server on lenbkx0001 ... Stays running forever... I'm able to telnet the tape server port 10083 (amidxtape), 10082 (amandaidx) but not the 10080 (amanda) port (i got a connection refused error). Any ideas about what i'm doing wrong? Thankx in advance. Jose Vicente. = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
Re: skipping cruft file
On Thu, 6 Dec 2001 at 8:40am, Steve wrote Hi all. I've installed amanda from the latest source after removing the SuSE 7.3 rpm version. When I run amcheck it passes server test and dies on client: WARNING: localhost: selfcheck request timed out. Host down? Did you go through the steps in FAQ-O-Matic to solve this? Is there any firewall (external, or ipchains/iptables) in the way? Did you make the appropriate changes to (x)inetd? Did you then restart (x)inetd? etc, etc. I've gone through the amanda chapter in the book recommended, the same with INSTALL file and cannot see anything I've missed. So I ran amoverview and it reported: amoverview is not going to help you debug this. You need to get your setup to pass amcheck. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Verifying backups
On 6 Dec 2001 at 2:29pm, Ole Barnkob Kaas wrote How do people verify their backups? Are there some nifty scripts or tools available somewhere. Restoring 20GB+ of data just to find out that tar or dump has trashed some of the data is a tediuos task. Especially because you know you have to do it again when the problem is fixed to ensure that the data really is ok. Well, there's amverify, but all it does is generate a table of contents from the tape images -- if that succeeds, the tape is marked OK. Note that there is no comparison of the TOC to index files or file system contents, so this isn't exactly the best. Checking the history of both tar and dump reveals so many issues that one has to wonder if it is ever possible to guarantee a safe backup on a Dump has its issues, yes. But a lot of people depend upon tar. linux box. Some cron task that could do a file to file compare or md5 compare would really help me sleep at night. Patches welcome. ;) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Shit
Well the bright side to all of this is that he is unsubscribing. *grin* -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rebecca Pakish Sent: Wednesday, December 05, 2001 11:29 AM To: 'Roy Andrè Tollefsen' Cc: Amanda Users (E-mail) Subject: RE: Shit If you know how to read...and I'm assuming you do since you can type...go to www.amanda.org and read the instructions. If that is too difficult I've pasted them below. (And in the future keep your profanity to yourself, it's unprofessional and uncalled for) pasted from amanda site Please note: To subscribe or unsubscribe to a mailing list, DO NOT, EVER, send mail to that list. Send mail to listname[EMAIL PROTECTED] with the following line in the body of the message: subscribe your-email-address and when you want to unsubscribe, use the following line in the body: unsubscribe your-email-address where listname is one of the following: amanda-announce The amanda-announce mailing list is for important announcements related to the Amanda Network Backup Manager package, including new versions, contributions, and fixes. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-users The amanda-users mailing list is for questions and general discussion about the Amanda Network Backup Manager. This package and related files are available via anonymous FTP from ftp.amanda.org in the pub/amanda directory. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-hackers The amanda-hackers mailing list is for discussion of the technical details of the Amanda package, including extensions, ports, bugs, fixes, and alpha testing of new versions. To subscribe, send a message to [EMAIL PROTECTED] -Original Message- From: Roy Andrè Tollefsen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Shit Hello amanda-users, Can someone please tell how we can unsubscribe from this list? For the last time ... I call this spam -- geworth
amrecover help
Hi, I've been having quite a bit of difficulty getting amrecover to work properly. I've been getting the Unexpected server end of file error, and the logs in /tmp/amanda/ are not being updated, even though they exist. tapeserver is the server, and client is the client. Amanda runs as operator on the tapeserver. Here is the command I am using to attempt the recovery, as root, on client amrecover Daily -s tapeserver -t tapeserver -d /dev/nst0 And Daily is the correct (and only) configuration I'm using. Here is the ~operator/.amandahosts file from the tape server: tapeserver operator client root The permissions on that file are as follows: -rw-r-1 operator disk And the appropriate lines from /etc/inetd.conf: amandadgram udp waitoperator /usr/sbin/tcpd /usr/lib/amanda/amandad amandaidx stream tcp nowait operator /usr/sbin/tcpd /usr/lib/amanda/amindexd amidxtape stream tcp nowait operator /usr/sbin/tcpd /usr/lib/amanda/amidxtaped /etc/inetd.conf had the user listed as operator.disk, which I changed. After doing that, amrecover fails instantly, instead of hanging for a few seconds. I can ping / nslookup either machine by hostname, ip, or fqdn just fine. I get the same message even if I put localhost root in the .amandahosts file, and try running amrecover on the tapeserver as root. /etc/hosts has all the correct information in it too. I guess inetd cannot correctly start amandaidx... Any ideas? -Brian Ferguson.
changing the /tape/dev
hi, My question is quite simple... can we enable the hard-compression of the tape after using the soft compression in amanda for a while. soft compression = comp-user in the disklist and /dev/rmt/0bn hard compression = nocomp-user in the disklist and /dev/rmt/0cbn One of the problems that I see is : Imagine that the dump0 was happenning when we were doing a software compression and that the dump1 with a hard compression...So when we will recover the data, amrecover will use the amanda.conf which contain the hard-compression...so the system will be able to only read one of them... So I will be constrain to do the recover manually 1)any idea on how to do it 2)do you see any other problems thanks in advance briner
Re: Shit
I knew this would erupt into a flame war :) He deserved it. wab - Original Message - From: Christopher Adams [EMAIL PROTECTED] To: 'Rebecca Pakish' [EMAIL PROTECTED]; 'Roy Andrè Tollefsen' [EMAIL PROTECTED] Cc: 'Amanda Users (E-mail)' [EMAIL PROTECTED] Sent: Thursday, December 06, 2001 11:23 AM Subject: RE: Shit Well the bright side to all of this is that he is unsubscribing. *grin* -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rebecca Pakish Sent: Wednesday, December 05, 2001 11:29 AM To: 'Roy Andrè Tollefsen' Cc: Amanda Users (E-mail) Subject: RE: Shit If you know how to read...and I'm assuming you do since you can type...go to www.amanda.org and read the instructions. If that is too difficult I've pasted them below. (And in the future keep your profanity to yourself, it's unprofessional and uncalled for) pasted from amanda site Please note: To subscribe or unsubscribe to a mailing list, DO NOT, EVER, send mail to that list. Send mail to listname[EMAIL PROTECTED] with the following line in the body of the message: subscribe your-email-address and when you want to unsubscribe, use the following line in the body: unsubscribe your-email-address where listname is one of the following: amanda-announce The amanda-announce mailing list is for important announcements related to the Amanda Network Backup Manager package, including new versions, contributions, and fixes. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-users The amanda-users mailing list is for questions and general discussion about the Amanda Network Backup Manager. This package and related files are available via anonymous FTP from ftp.amanda.org in the pub/amanda directory. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-hackers The amanda-hackers mailing list is for discussion of the technical details of the Amanda package, including extensions, ports, bugs, fixes, and alpha testing of new versions. To subscribe, send a message to [EMAIL PROTECTED] -Original Message- From: Roy Andrè Tollefsen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Shit Hello amanda-users, Can someone please tell how we can unsubscribe from this list? For the last time ... I call this spam -- geworth
RE: Verifying backups
Right now we use a shell script to gather information about date, file size, uid, gid and permission. We run teh script on the server and on the restored replica. We filter both lists with a python script and parses the through diff to see how much they differ. This is very time consuming as you have to restore a complete server each time. I have another idea to a script which could be run from cron: There are a a number of IDS (intrusion detection systems) that gathers the same info, but at the inode level, already optimized for speed. I settled on 'integrit', after fiddling with 'aide' for a month or so. 'tripwire' isn't an option for this shop. integrit already has the ability to compare two logs, remember to filter out inode changes... Maybe an option for md5sum'ing each partition's tape stream to be stored in curinfo? -dan
Re: amrecover: No index records for host?
Hello,
--- Stavros Patiniotis [EMAIL PROTECTED] escribió:
Hello,
Hi!
What i did was to recompile the amanda server and
also
added the option index to the dumpiles type (for
example comp-user) in the amanda.conf file. I got
it
working for Tar, and i let you know if that fixes
my
dump errors too (i got that error with dump).
Ok, I have now recomplied the server and client
after installing tar
1.13.25, previously I had only link the old tar
location to the new
tar. I have the following in amanda.conf:
define dumptype incremental {
comment General Data Backup
priority medium
program GNUTAR
compress client fast
index yes
record yes
}
I don't have the record tag but seems ok to me :)
On the client when running ./configure I get
[cut]
checking for gtar... no
checking for gnutar... no
checking for tar... /usr/local/bin/tar
[cut]
But there is a parameter called with-gnu-tar or
something (do a ./configure --help). Then it should
work.
however,
www# which tar
/usr/local/bin/tar
www# tar --version
tar (GNU tar) 1.13.25
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent
permitted by law.
You may redistribute it under the terms of the GNU
General Public License;
see the file named COPYING for details.
Written by John Gilmore and Jay Fenlason.
Any more suggestions?
Hope this helps
JV.
--- Stavros Patiniotis [EMAIL PROTECTED]
escribió:
Hello,
I get the error, No index records for host?
I've
upgraded tar, linked the
old tar location to the new (ln -s
/usr/local/bin/tar /usr/bin/tar), and
still get the above error. In the /tmp/amanda
dir I
get no errors in the
amrecover files, however in the amandaindexd
files,
I get an error like:
OISD /
500 No dumps available on or before date
2001-12-07
OISD /
500 No dumps available on or before date
2001-12-07
The partition in question definately has a
backup as
the Amanda daily
report says its been backed up.
I do not record to tape, but leave my backups on
the
holding disk.
Any suggestion?
Kind Regards,
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
escape net
m a k i n g t h e n e t w o r k f o
r
y o u
465b South Road
ph 8293 2526
KESWICK SA 5035
fx 8293 2949
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
=
System Engineer, José Vicente Nuñez Zuleta
([EMAIL PROTECTED])
Newbreak System Administrator
(http://www.newbreak.com)
Phone: 203-355-1511, 203-355-1510
Java 2 Certified Programmer
Java 2 Certified Developer
_
Do You Yahoo!?
¿Quieres armar tu própia página Web pero no sabes
HTML?
Usa los asistentes de edición de Yahoo! Geocities
y tendrás un sitio en sólo unos minutos.
Visítanos en http://espanol.geocities.yahoo.com
=
System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
Newbreak System Administrator (http://www.newbreak.com)
Phone: 203-355-1511, 203-355-1510
Java 2 Certified Programmer
Java 2 Certified Developer
_
Do You Yahoo!?
¿Quieres armar tu própia página Web pero no sabes HTML?
Usa los asistentes de edición de Yahoo! Geocities
y tendrás un sitio en sólo unos minutos.
Visítanos en http://espanol.geocities.yahoo.com
Re: Problem with windows 2000 Professional
Problem fixed after I created one empty file /etc/amandates and one empty directory /usr/local/amanda/var/amanda/gnutar-lists/ .. Found this problem by using amcheck . Thanks, Shu Liu Shu Liu wrote: Hi, I have problem with Win2k Server SP2 also. My environment is: Amanda 2.4.2p2 server running on Solaris 8 Samba 2.2.2 running on same Solaris 8 box Win2k Server version SP2 (Japanese) GNU tar 1.3.23(?) I can see the amdump pulling file names from the Win2k machine by monitor the network packet. I think after it got all file list from the PC, it stops there. The CPU and network becomes idle. Using Ctrl-C can stop it. There is no any error message in the dump or log file. I can use the amanda to backup the Solaris local disk partition without any problem. And I can use smbclient to connect to the Win2K server and retrieve file. (I don't know how to combine smbclient with gnutar manually, so I didn't try it.) Does anyone have an idea that I can try ? Thank you very much in advance, Shu Liu On Mon, 3 Dec 2001, Amanda Admin wrote: Christophe, I use the samba package extensively (2.2.1a), though not for backup with amanda (yet) as you are trying. I tried a simple tar test using smbclient and had no problems. I connected to the client (my laptop, Win2k SP2, NTFS) from my amanda server (RH 7.1) as both myself and as my amanda user (member of the local Backup Operators group). Tarred up about 800K worth of files no problem. Then tested a bigger set of files (116 files, 46 directories, 550MB) also with no problems. Suspecting it might be disk space issue, I even tried this last test in a directory with not enough disk space to hold the resulting tar file. It failed as expected, but never froze. Try running your smbclient tests with a debug level of 3 and a log file (smbclient -l log -d 3) and see what the log says if/when the freeze occurs. Increasing the log level (up to 10) will give you incredible amounts of information (every function entry I believe). Also, check the Event Log on the client. Does the freezing only occur with one client or do other 2000 clients behave similarly? If not every client behaves the same, check permissions and/or service packs. I suspect the freeze occurs because the file may be in use. Or, if the tar is running for some time, perhaps a network problem. I searched the samba lists I'm a member of ([EMAIL PROTECTED], [EMAIL PROTECTED]) and didn't see any posts from yourself. You may try posting there also, check samba.org for the appropriate list (samba-users?). HTH, Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christophe Condomines Sent: Thursday, November 29, 2001 7:09 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Problem with windows 2000 Professional Hi, I am testing Amanda for my backup solution. I use Amanda 2.2.4p2 on a Linux Red Hat 7.1 and without any tape for the test. The backup works fine on linux. I use samba 2.2.2 for the windows clients : that works with NT and 98, but on windows 2000, the amdump starts and finally freeze. I have checked the use of smbclient and a command like tar c test.tar produces the same freeze : smbclient starts to retrieve some files and finally stop. It's not always on the same file, it's not always the same size, ... Any suggestion ? I also try the amanda win32 client, failed on win95, works on win2k but very slowly. Any comments ? = Christophe Condomines [EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Courrier : http://courrier.yahoo.fr
