Amanda

2003-03-06 Thread Stephen D. Lane
Check out 

   http://www.backupcentral.com/amanda.html

for a pretty good how-to on getting amanda up & running.


--Steve Lane   /"\
  Doudna Lab   \ /  ASCII Ribbon Campaign
  U. C. BerkeleyX Against HTML Email
   / \

- Forwarded message from Philip ganss <[EMAIL PROTECTED]> -

From: "Philip ganss" <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Amanda
Date: Thu, 6 Mar 2003 13:19:31 -0500


Hi, my name is Philip, and AMANDA is really new to me and perhaps a little
too complex for me to set-up properly.
Is there anyone who could possibly point out, or perhaps give me some tips
on how to get around a few problems that I am encountering.  Here is where I
am currently.
1. I have Perl 5 installed along with mkisofs and cdrecord on RedHat 8.0
2. I have a IDE CD-RW device. I was able to use SCSI emulation to get
cdrecord to work properly, and
a cdrecord -scanbus tested just fine.
3. On the Linux system I have the Amanda base system files installed with
the rpm Amanda 2.4.2p2-9
4. I also have installed the Amanda-client 2.4.2p2-9 along with the
Amanda-sever 2.4.2p2-9.
5. I have all the dependencies for the Base system, server and client
installed
6. I downloaded CDRW-Taper from www.tivano.de/software/amanda/index.shtml
7. I renamed the Taper binary that came with Amanda to taper.original, that
file was located in
/usr/lib/amanda
8. I moved the tivano "taper" binary and the "taperlib.pm" perl script to
/usr/lib/amanda/
9. I left the "amlabel-cdrw" in my root directory, which is /root/src
10. It's at this point everything seems to be falling apart for me, I am
just not sure how to deal with these
 configuration files. For example I don't even know what taper means, I
sort of feel like I am on life
 support.
11. I used the mkdir -p /usr/adm/amanda/normal.but I have
nothing in there
12. I believe rpm created a  /etc/amanda directory which holds
"crontab.sample", "Daily-Set"1, and "normal."
13. In Daily-Set1 there was a Amanda.conf, I moved it to the /etc directory
not knowing if I should or not.
14. I then went to my /etc/services files and this is what I saw
kamanda 10081/tcp   # amanda backup services
(Kerberos)
kamanda 10081/udp   # amanda backup services
(Kerberos)
amandaidx
15. I then enabled amanda.idx, amidxtape, and amanda them in /etc/xinetd.d
by issuing disable =no
16. Then I restarted my xinetd server by the issuing the "restart" parameter
to xinetd from /etc/init.d/
17  I am not sure how to make a "disk list" nor exactly where to put it.
18. I do not really know what I need to edit in "Amanda.conf". nor how to
execute the back-ups properly.
19. Nor do I really have a handle on how taperlib.pm and amlabel-cdrw come
into play

Any help would be greatly appreciated. I am  trying to fill in the Gaps, but
at the same time I am
a little overwhelmed...with it all but I think Amanda will pay off
though, if I can ever master it.
Thanks for your time


Philip

- End forwarded message -


Problems backing up Windows servers with SAMBA: got 'badlyformatted response'

2003-03-06 Thread Jose Vicente Nunez Z
Greetings,

I got a working Amanda configuration and now my company wants to backup
the data on their windows machines; I tested samba using the tool
'smbclient' and so far i managed to tar a shared drive:

smbclient //10.1.20.26/MyDocuments -WMYDOMAIN -A auth -N -TXc backup.tar
'My Music' 'My Pictures' 'Personal' 'Messenger Service Received Files'
'./downloads'

(this command works just fine)


Also amcheck looks good, here is the debug trace:

selfcheck: debug 1 pid 26920 ruid 31 euid 31 start time Thu Mar  6
18:11:23 2003
/home/amanda/libexec/selfcheck: version 2.4.3b3
selfcheck: checking disk //10.1.20.44/MyDocuments2
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.44\MyDocuments2 -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.44 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
selfcheck: checking disk //10.1.20.44/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.44\MyDocuments -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.44 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
selfcheck: checking disk //10.1.20.46/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.46\MyDocuments -U
administrator -E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.46 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
selfcheck: checking disk //10.1.20.43/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.43\MyDocuments -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.43 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN.COM] OS=[Windows 5.0] Server=[Windows 2000 LAN
Manager]
selfcheck: checking disk //10.1.20.40/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.40\MyDocuments -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.40 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
selfcheck: pid 26920 finish time Thu Mar  6 18:11:27 2003


But when i try to backup the server from amanda i got a weird message:


[EMAIL PROTECTED] NEWBREAK_TAPE]$ amstatus MY_CONFIG
Using /home/amanda/MY_CONFIG/logs/amdump from Thu Mar  6 20:00:29 EST
2003

arbitrage:/dev/dsk/c0t0d0s0 1 244k dumping0k (20:08:00)
arbitrage:/dev/dsk/c0t0d0s5 0  802352k wait for dumping 
linux0107://10.1.20.40/MyDocuments 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.43/MyDocuments 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.44/MyDocuments 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.44/MyDocuments2 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.46/MyDocuments 0 planner: [badly formatted response
from linux0107]
lnxdev0002:/apps  2   19839k wait for dumping 
lnxdev0002:/data  1  22k dump done (20:07:41), wait for writing
to tape
lnxdev0002:/etc   1  14k dump done (20:07:42), wait for writing
to tape
lnxdev0002:/export3  244765k wait for dumping 
lnxdev0002:/home/cvs/repository 1 219k dump done (20:07:44), wait
for writing to tape
lnxdev0002:/usr/java  1  49k dump done (20:07:47), wait for writing
to tape
lnxdev0002:/var   13362k dump done (20:08:00), wait for writing
to tape
lnxdev0003:/usr/local/tutos 1   5k dump done (20:07:52), wait for
writing to tape
lnxdev0003:/var/lib/pgsql/backups 1  36k dump done (20:07:49), wait
for writing to tape

SUMMARY  part real estimated
  size  size
partition   :  16
estimated   :  111073307k
flush   :   00k
failed  :   5  0k   (  0.00%)
wait for dumping:   31066956k   ( 99.41%)
dumping to tape :   0  0k   (  0.00%)
dumping :   10k  244k (  0.00%) (  0.00

Problems backing up Windows servers with SAMBA: got 'badlyformatted response'

2003-03-06 Thread Jose Vicente Nunez Z
Greetings,

I got a working Amanda configuration and now my company wants to backup
the data on their windows machines; I tested samba using the tool
'smbclient' and so far i managed to tar a shared drive:

smbclient //10.1.20.26/MyDocuments -WMYDOMAIN -A auth -N -TXc backup.tar
'My Music' 'My Pictures' 'Personal' 'Messenger Service Received Files'
'./downloads'

(this command works just fine)


Also amcheck looks good, here is the debug trace:

selfcheck: debug 1 pid 26920 ruid 31 euid 31 start time Thu Mar  6
18:11:23 2003
/home/amanda/libexec/selfcheck: version 2.4.3b3
selfcheck: checking disk //10.1.20.44/MyDocuments2
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.44\MyDocuments2 -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.44 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
selfcheck: checking disk //10.1.20.44/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.44\MyDocuments -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.44 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
selfcheck: checking disk //10.1.20.46/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.46\MyDocuments -U
administrator -E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.46 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
selfcheck: checking disk //10.1.20.43/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.43\MyDocuments -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.43 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN.COM] OS=[Windows 5.0] Server=[Windows 2000 LAN
Manager]
selfcheck: checking disk //10.1.20.40/MyDocuments
selfcheck: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\10.1.20.40\MyDocuments -U backup
-E -W MY_DOMAIN -c quit
selfcheck: OK
selfcheck: extra info: added interface ip=10.1.20.107 bcast=10.1.20.255
nmask=255.255.255.0: session request to 10.1.20.40 failed (Called name
not present): session request to 10 failed (Called name not present):
Domain=[MY_DOMAIN] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
selfcheck: pid 26920 finish time Thu Mar  6 18:11:27 2003


But when i try to backup the server from amanda i got a weird message:


[EMAIL PROTECTED] NEWBREAK_TAPE]$ amstatus MY_CONFIG
Using /home/amanda/MY_CONFIG/logs/amdump from Thu Mar  6 20:00:29 EST
2003

arbitrage:/dev/dsk/c0t0d0s0 1 244k dumping0k (20:08:00)
arbitrage:/dev/dsk/c0t0d0s5 0  802352k wait for dumping 
linux0107://10.1.20.40/MyDocuments 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.43/MyDocuments 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.44/MyDocuments 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.44/MyDocuments2 0 planner: [badly formatted response
from linux0107]
linux0107://10.1.20.46/MyDocuments 0 planner: [badly formatted response
from linux0107]
lnxdev0002:/apps  2   19839k wait for dumping 
lnxdev0002:/data  1  22k dump done (20:07:41), wait for writing
to tape
lnxdev0002:/etc   1  14k dump done (20:07:42), wait for writing
to tape
lnxdev0002:/export3  244765k wait for dumping 
lnxdev0002:/home/cvs/repository 1 219k dump done (20:07:44), wait
for writing to tape
lnxdev0002:/usr/java  1  49k dump done (20:07:47), wait for writing
to tape
lnxdev0002:/var   13362k dump done (20:08:00), wait for writing
to tape
lnxdev0003:/usr/local/tutos 1   5k dump done (20:07:52), wait for
writing to tape
lnxdev0003:/var/lib/pgsql/backups 1  36k dump done (20:07:49), wait
for writing to tape

SUMMARY  part real estimated
  size  size
partition   :  16
estimated   :  111073307k
flush   :   00k
failed  :   5  0k   (  0.00%)
wait for dumping:   31066956k   ( 99.41%)
dumping to tape :   0  0k   (  0.00%)
dumping :   10k  244k (  0.00%) (  0.00

amanda not backing up local machine sometimes.

2003-03-06 Thread Raymond Keckler








I have Amanda setup and it works. There is one problem.
After the first good run it starts not working on some directories in the disklist

This is the first dump.

 



Reports:



These dumps were to tape
Vol05.

The next tape Amanda expects
to use is: a new tape.

 

 

STATISTICS:

 
Total   Full 
Daily

   
      

Estimate Time (hrs:min)   
0:01

Run Time (hrs:min)
0:06

Dump Time (hrs:min)   
0:03   0:03  
0:00

Output Size (meg) 
57.3   57.3   
0.0

Original Size (meg)   
79.6   79.6   
0.0

Avg Compressed Size
(%)    72.0   72.0   
-- 

Filesystems
Dumped    6 
6  0

Avg Dump Rate
(k/s)   289.9  289.9   
-- 

 

Tape Time (hrs:min)   
0:01   0:01  
0:00

Tape Size (meg)   
57.6   57.6   
0.0

Tape Used
(%)  
0.3    0.3   
0.0

Filesystems
Taped
6  6 
0

Avg Tp Write Rate (k/s) 
1431.7 1431.7   
-- 

 




 

NOTES:

  planner: Adding new
disk emailbkup:/netshare/qmail.

  planner: Adding new
disk emailbkup:/netshare/apache.

  planner: Adding new
disk emailbkup:/netshare/courier-imap.

  planner: Adding new
disk emailbkup:/netshare/ezmlm.

  planner: Adding new
disk emailbkup:/netshare/incoming.

  planner: Adding new
disk emailbkup:/netshare/php.

  taper: tape Vol05 kb
58944 fm 6 [OK]

 




 

DUMP SUMMARY:


DUMPER STATS   
TAPER STATS 

HOSTNAME
DISK    L ORIG-KB OUT-KB COMP% MMM:SS 
KB/s MMM:SS  KB/s

--
- 

emailbkup    -are/apache
0   12930   4320  33.4   1:23 
51.5   0:06 713.3

emailbkup   
-urier-imap 0    2340    896 
38.3   0:05 153.7   0:02 410.5

emailbkup   
-hare/ezmlm 0 270    128 
47.4   0:02  37.7   0:03  41.6

emailbkup   
-e/incoming 0   47590  47072  98.9   1:00
779.5   0:202304.3

emailbkup   
-tshare/php 0    6510   2272  34.9  
0:19 115.0   0:06 397.2

emailbkup   
-hare/qmail 0   11900   4256  35.8   0:32
131.0   0:041146.4

 



(brought
to you by Amanda version 2.4.3)



Then I added to the disklist and this is the second dump
with errors

 

 

These dumps were to tape
Vol06.

The next tape Amanda expects
to use is: a new tape.

 

FAILURE AND STRANGE DUMP
SUMMARY:

  emailbkup  /netshare/courier-imap
lev 1 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/incoming
lev 1 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/ezmlm
lev 1 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /usr/local/etc
lev 0 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/vqadmin
lev 0 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/apache
lev 1 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/qmailadmin
lev 0 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/spamassassin
lev 0 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /etc lev
0 FAILED 20030306[could not connect to emailbkup]

  emailbkup  /netshare/src
lev 0 FAILED 20030306[could not connect to emailbkup]

 

 

STATISTICS:

 
Total   Full 
Daily

   
      

Estimate Time (hrs:min)   
0:05

Run Time (hrs:min)
0:20

Dump Time (hrs:min)   
0:00   0:00  
0:00

Output Size (meg)  
0.0    0.0   
0.0

Original Size (meg)
0.1   
0.0    0.1

Avg Compressed Size
(%) 6.2   
-- 6.2   (level:#disks
...)

Filesystems
Dumped   
2 
0  2   (1:2)

Avg Dump Rate
(k/s)
0.5   
-- 0.5

 

Tape Time (hrs:min)   
0:00   0:00  
0:00

Tape Size (meg)
0.1   
0.0    0.1

Tape Used
(%)  
0.0    0.0   
0.0   (level:#disks ...)

Filesystems
Taped     2 
0  2   (1:2)

Avg Tp Write Rate
(k/s)    13.9   
--    13.9

 




 

NOTES:

  planner: Adding new
disk emailbkup:/netshare/qmailadmin.

  planner: Adding new
disk emailbkup:/netshare/spamassassin.

  planner: Adding new
disk emailbkup:/netshare/src.

  planner: Adding new
disk emailbkup:/netshare/vqadmin.

  planner: Adding new
disk emailbkup:/etc.

  planner: Adding new
disk emailbkup:/usr/local/etc.

  taper: tape Vol06 kb
128 fm 2 [OK]

 




 

DUMP SUMMARY:


DUMPER STATS   
TAPER STATS 

HOSTNAME
DISK    L ORIG-KB OUT-KB COMP% MMM:SS 
KB/s MMM:SS  KB/s

--
- 

emailbkup   
/etc    0 FAILED ---

emailbkup   
-are/apache 1 FAILED ---

emailbkup   
-urier-imap 1 FAILED

backup plan needs comments

2003-03-06 Thread bao
Hi everyone,

I have this backup plan in mind as below, and would hope if anyone
can suggest what can be wrong, can be hard to set up, or any 
suggestions. Anything is appreciated.

  Second HD (Amanda)  Tapes
--
Full   |   IncrementalWeekly(20GB)  |  Daily(12GB)
--
Full - - - - - - - - - - copied to - -> Weekly 1
   Day 1 -|
   Day 2 -|
   Day 3 -|
   Day 4 -|
   Day 5 -|
   Day 6 -|
  |- - - copied to - - - - - - - - - -> Daily 1
/--We clean up the 2nd HD at the end of this---/

Full - - - - - - - - - - copied to - -> Weekly 2
   Day 1 -|
   Day 2 -|
   Day 3 -|
   Day 4 -|
   Day 5 -|
   Day 6 -|
  |- - - copied to - - - - - - - - - -> Daily 2
/--We clean up the 2nd HD at the end of this---/



We copy the Full on 2nd hard drive to Weekly tape after it's done.
At the end of Day 6, we can copy everything onto Daily tape.
After 8 weeks, we recycle the tapes.
Assumptions:
1. Tapeless backup onto a 2nd hard drive is done first, then is copied
to tapes.
2. Tapes have sufficient sizes, so only one tape is needed at a time.
3. And GNU-tar is used with Amanda.
Problems with restoring:
1. For restore from Weekly tapes, the whole tape has to be dumped to the 
hard drive, then amanda is used to select the correct files/folders.

2. For restore from Daily tapes, again, the tape contents have to be
dumped to hard drive, then amanda is used.
3. How should Amanda's database/index be handled???
   Should they be backed up to tapes along with its data??
4. If the database/index are to be backed up to tapes, Does it mean
   when restore, I need to put them back to their correct place, i.e.,
   /tmp/amanda , etc. ???
thank you for any comments.





Amanda

2003-03-06 Thread Philip ganss

Hi, my name is Philip, and AMANDA is really new to me and perhaps a little
too complex for me to set-up properly.
Is there anyone who could possibly point out, or perhaps give me some tips
on how to get around a few problems that I am encountering.  Here is where I
am currently.
1. I have Perl 5 installed along with mkisofs and cdrecord on RedHat 8.0
2. I have a IDE CD-RW device. I was able to use SCSI emulation to get
cdrecord to work properly, and
a cdrecord -scanbus tested just fine.
3. On the Linux system I have the Amanda base system files installed with
the rpm Amanda 2.4.2p2-9
4. I also have installed the Amanda-client 2.4.2p2-9 along with the
Amanda-sever 2.4.2p2-9.
5. I have all the dependencies for the Base system, server and client
installed
6. I downloaded CDRW-Taper from www.tivano.de/software/amanda/index.shtml
7. I renamed the Taper binary that came with Amanda to taper.original, that
file was located in
/usr/lib/amanda
8. I moved the tivano "taper" binary and the "taperlib.pm" perl script to
/usr/lib/amanda/
9. I left the "amlabel-cdrw" in my root directory, which is /root/src
10. It's at this point everything seems to be falling apart for me, I am
just not sure how to deal with these
 configuration files. For example I don't even know what taper means, I
sort of feel like I am on life
 support.
11. I used the mkdir -p /usr/adm/amanda/normal.but I have
nothing in there
12. I believe rpm created a  /etc/amanda directory which holds
"crontab.sample", "Daily-Set"1, and "normal."
13. In Daily-Set1 there was a Amanda.conf, I moved it to the /etc directory
not knowing if I should or not.
14. I then went to my /etc/services files and this is what I saw
kamanda 10081/tcp   # amanda backup services
(Kerberos)
kamanda 10081/udp   # amanda backup services
(Kerberos)
amandaidx
15. I then enabled amanda.idx, amidxtape, and amanda them in /etc/xinetd.d
by issuing disable =no
16. Then I restarted my xinetd server by the issuing the "restart" parameter
to xinetd from /etc/init.d/
17  I am not sure how to make a "disk list" nor exactly where to put it.
18. I do not really know what I need to edit in "Amanda.conf". nor how to
execute the back-ups properly.
19. Nor do I really have a handle on how taperlib.pm and amlabel-cdrw come
into play

Any help would be greatly appreciated. I am  trying to fill in the Gaps, but
at the same time I am
a little overwhelmed...with it all but I think Amanda will pay off
though, if I can ever master it.
Thanks for your time


Philip



Wrapping amandad.exe on Cygwin

2003-03-06 Thread Richard Morse
Hi!  I'd like to write a wrapper script for amandad.exe on Cygwin.  I 
want to make sure that all the log files are made readable by the group 
once amandad is finished.  My issue is that I don't quite know how to 
ensure that amandad gets passed all the proper parameters.

Would the following work if placed in inetd.conf in place of 
amandad.exe?

-
#!/bin/sh
# call amanda
/usr/local/amanda/libexec/amandad.exe $@
cd /tmp/amanda
chmod g+r *
--
Thanks,
Ricky


Dumpcycle advise

2003-03-06 Thread F.M. Taylor
I need some dumpcycle advise.

I have a 40 slot tape library.

I have 4 "sets" of backups.
(4 configs with different systems in each config, some going to drive 1
some going to drive 0) All the configs use the same tapelist files, so
they are kind of aware of each other.

Amanda runs every day.

Each set can use 1 or two tapes.
(I told it it could use two, but most the time it only uses one).

Monthly I remove all the tapes from the library, send them offsite, and
install fresh ones. (this could be changed in order to meet my goal)

I need dumpcycle settings that ensure that every time I pull the tapes,
that all the data from the entire month is there.

currently I have 

dumpcycle 20 days
runspercycle 20
tapecycle 40 tapes

Comments? Suggestions? 

-- 
Mike Taylor
Coordinator of Systems Administration and Network Security
Indiana State University.   Rankin Hall Rm 053
210 N 7th St.   Terre Haute, IN.
SANS GSEC  http://www.sans.org/



re:

2003-03-06 Thread Kemal Etikan
Title: New Page 6









  
  

  


  

  
  

  


  
Turk Erotik Serisi>> 100% 
Turk
  


  
? 
Manken.de.Vu
  
 
 
 
Bilgi:79min - 450 Mb - Avi Divx - 
Rating: Oyuncular:Zerrin Egeliler,Aydemir 
Akbas,Koylu Kizimiz ve Istanbul 
AbazalariAciklama:Koyunde cani sikilan ve 
hayattan tad almayan azgin kizimiz Istanbul hayaline kapilir. Cani 
sevismek, gezip tozmak, eglenmek ister. Bu hayallerle Istanbul'a 
kacar ve firsatcilarin kucagina 
  duser.
  


  

  

  


  

  

  

  


  
Sevda Demirel >> Hollandali 
Kiz
  


  
 ? 
Manken.De.vu
  
Bilgi:25 dak - 250 Mb - Avi DivX - 
Rating: Oyuncular:Sevda Demirel, 
Tecavuzcu CoskunAciklama:Hollanda'nin 
daglarindan kopup gelen masbut kizimiz Sevda Turkiyemizin sahil 
kentlerinde yasayan yakisikli delikanlailari gorunce azmis,cildirmis 
ve aska gelmistir. Onune gelene pas vermekte mahaleyi bir birine 
katmaktadir. Anliyacaginiz surtukluk yapmaktadir.Mahalenin namus 
bekcisi delikanlimiz buna izin vermez ve olay karmakarisik bir hal 
alir.
Sevda Demirel'in birbirinden tahrik edici 
goruntuleri ile dolu super bir video. 
  
  


  
 
  
 
  
 

  
 
  
 
  
 
  
  ? copyright Manken.De.vu 
- 2003 


  
  

  
  

  
  

  





Re: Q: NOTE by amcheck

2003-03-06 Thread Frank Smith
--On Thursday, March 06, 2003 10:21:05 +0100 Raúl Wild-Spain <[EMAIL PROTECTED]> wrote:

Hi! After my first succesfully try with amanda I've been changed my disklist to adjust them not for filesystems but for the important directories I want to backup. In this case amcheck says the following:

NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.notesini: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.notesini: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.recursosBD: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.recursosBD: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.namesBD: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.namesBD: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.mail: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.mail: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.aplicacionsFURV: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.aplicacionsFURV: does not exist
Should I suppose that amanda will create the necessary directories and files when needed although it not indicates " NOTE: it will be created on the next run"? or I must to do this "by hand"?

The man page of amcheck isn't clear about this ...
As many others have already answered, these will be created by Amanda.

- comment : -  /.x are softlinks to every directory or file I want to backup
If you are saying that all of the paths you tell Amanda to back up  are soft links,
you have a big problem.  All that will be backed up are the links themselves, not
the directories they point to.   Also, disklist entries are usually directories or
partitions and not files, but if you are using GNU tar I suppose passing it a filename
instead of a directory would work (anyone here know for sure?).
Frank

Best Regards,

Raúl
[EMAIL PROTECTED]



--
Frank Smith [EMAIL PROTECTED]
Systems Administrator  Voice: 512-374-4673
Hoover's Online  Fax: 512-374-4501


Re: Win32 Backup?

2003-03-06 Thread tobias . bluhm
"Steve Loughran" <[EMAIL PROTECTED]> wrote:
>> One way I have done it is to use MS's backup program to backup to a
>> samba share on a freebsd box. MS backup will happily backup to a samba
>> share.  Then I just backup all that stuff using amanda.
>
>beware of backing up via NT Backup to a samba share, always verify the
>contents of the file. I ran into a problem wher it appeared to be backing 
up
>just fine, and created a huge BKF file, but it was full of zeros and
>unusable...


I've been using ntbackup to files on samba share for a number of weeks 
now, haven't seen any problems. I do have the verify flag on. Perhaps it's 
the samba version or config, or maybe networking issues?

Just a thought.

I did have to alter my original schedule/dump type in ntbackup. I was 
getting tape overruns due to that fact that amanda has no control of the 
w2k boxes schedule/dump type. It would be very cool if some smart win 
programmer could write wrappers for ntbackup.exe so that amanda could 
control it directly. Also, I copy over the ntbackup log files at the end 
of the script. Seems it can only have 10 log files at a time. Ntbackup in 
w2k is pretty useful. Although Veritas did write it for them.


--
toby bluhm
philips medical systems, it support, mr development, cleveland ohio
[EMAIL PROTECTED]
440-483-5323



Re: Q: NOTE by amcheck

2003-03-06 Thread Gene Heskett
On Thu March 6 2003 04:21, Raúl Wild-Spain wrote:
>Hi! After my first succesfully try with amanda I've been changed
> my disklist to adjust them not for filesystems but for the
> important directories I want to backup. In this case amcheck says
> the following:
>
>NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.notesini: does
> not exist NOTE: index dir
> /var/lib/amanda/furv/index/xaloc/_.notesini: does not exist NOTE:
> info dir /var/lib/amanda/furv/curinfo/xaloc/_.recursosBD: does
> not exist NOTE: index dir
> /var/lib/amanda/furv/index/xaloc/_.recursosBD: does not exist
> NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.namesBD: does
> not exist NOTE: index dir
> /var/lib/amanda/furv/index/xaloc/_.namesBD: does not exist NOTE:
> info dir /var/lib/amanda/furv/curinfo/xaloc/_.mail: does not
> exist NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.mail:
> does not exist NOTE: info dir
> /var/lib/amanda/furv/curinfo/xaloc/_.aplicacionsFURV: does not
> exist NOTE: index dir
> /var/lib/amanda/furv/index/xaloc/_.aplicacionsFURV: does not
> exist
>
>
>Should I suppose that amanda will create the necessary directories
> and files when needed although it not indicates " NOTE: it will
> be created on the next run"? or I must to do this "by hand"?
>
>The man page of amcheck isn't clear about this ...

They will be created when amdump runs and needs them.

-- 
Cheers, gene
gheskett at wdtv dot com
99.24% setiathome rank, not too bad for a WV hillbilly


Re: Q: NOTE by amcheck

2003-03-06 Thread Dietmar Goldbeck
On Thu, Mar 06, 2003 at 10:21:05AM +0100, Raúl Wild-Spain wrote:

> NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.recursosBD: does not exist
> 
> Should I suppose that amanda will create the necessary directories and files 

Yes, You can safely ignore these messages.


  Ciao
Dietmar

-- 
Dietmar Goldbeck, Senior Consultant, <[EMAIL PROTECTED]>
Neteligent GmbH, http://www.neteligent.de/
Walter-Benjamin-Platz 6, 10629 Berlin, Germany 
fon: +49 (0)30/310182-73, fax: +49 (0)30/310182-79


Re: Win32 Backup?

2003-03-06 Thread Steve Loughran
> One way I have done it is to use MS's backup program to backup to a
> samba share on a freebsd box. MS backup will happily backup to a samba
> share.  Then I just backup all that stuff using amanda.

beware of backing up via NT Backup to a samba share, always verify the
contents of the file. I ran into a problem wher it appeared to be backing up
just fine, and created a huge BKF file, but it was full of zeros and
unusable...

Steve



Re: Q: NOTE by amcheck

2003-03-06 Thread Christoph Scheeder
Hi,
if amanda has write permision to the needed places, it will create them
on the fly in the next run.
Christoph
Raúl Wild-Spain schrieb:
Hi! After my first succesfully try with amanda I've been changed my disklist to adjust them not for filesystems but for the important directories I want to backup. In this case amcheck says the following:

NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.notesini: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.notesini: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.recursosBD: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.recursosBD: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.namesBD: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.namesBD: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.mail: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.mail: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.aplicacionsFURV: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.aplicacionsFURV: does not exist
Should I suppose that amanda will create the necessary directories and files when needed although it not indicates " NOTE: it will be created on the next run"? or I must to do this "by hand"?

The man page of amcheck isn't clear about this ...

- comment : -  /.x are softlinks to every directory or file I want to backup

Best Regards,

Raúl
[EMAIL PROTECTED]






Re: Q: finally!!! my first backup ... but :-)

2003-03-06 Thread Christoph Scheeder
Hm,
there are some solutions to suppress such a situation,
1.)take your server down into single user-mode before taking the backup ;-)
2.)tell your users not to log in while your backup is running
3.)ignore the failed files,It is very likely that the next night amanda will
   catch these files correct. In worst case your users will loose the
   modifications after the last backup of these files.
4.) create a script which scanns the amanda mail after the run,
collects all strange files in a single tar-archive and write it
to the end of the tape amanda used
Christoph
Raúl Wild-Spain schrieb:
Ok! thanks, Christoph (and Toomas again), but ... does it exist any solution in 
> these cases? or  must I have to be satisfied and try a "post-backup"
(manually or not) of these files ?

thanks again,



- Original Message - 
From: "Christoph Scheeder" <[EMAIL PROTECTED]>
To: "Raúl Wild-Spain" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 06, 2003 11:20 AM
Subject: Re: Q: finally!!! my first backup ... but :-)



Hi,
Your guess is correct,
this messages are the result of an active filesystem.
The backup itself is ok, but these specific files will
probably be bad, as they have been modifyd while tar was reading them.
Christoph
Raúl Wild-Spain schrieb:

Finally! yesterday I did my first backup and it seems ok, but I've some doubts about various messages:

FAILURE AND STRANGE DUMP SUMMARY:
 xaloc  /dev/sdc2 lev 0 STRANGE


FAILED AND STRANGE DUMP DETAILS:

/-- xaloc  /dev/sdc2 lev 0 STRANGE
sendbackup: start [xaloc:/dev/sdc2 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it
? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it
? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it
| Total bytes written: 4793784320 (4.5GB, 3.3MB/s)
sendbackup: size 4681430
sendbackup: end
\
I've looked at the index files of  _dev_sdc2 and the list seems to be ok. Then I suppose the mentioned users was connected ( from home) when amanda did the backup (0:45). It seems, true? 

No problem with the rest of filesystems ( or it seems ).

Best Regards,

Raúl
[EMAIL PROTECTED]










powervault 120T on redhat 8 bis

2003-03-06 Thread Said El Mamouni
For instance nothink works with my redhat8, so i 'l reinstall a redhat 7.3.
perhaps on the summer, dell gives us a new driver.

thanks
 

Saïd El Mamouni
Laboratoire Jean Leray 
CNRS - UMR 6629
2 Rue de la Houssiniére
44322 Nantes Cedex
02.51.12.59.45




Re: Q: finally!!! my first backup ... but :-)

2003-03-06 Thread Christoph Scheeder
Hi,
Your guess is correct,
this messages are the result of an active filesystem.
The backup itself is ok, but these specific files will
probably be bad, as they have been modifyd while tar was reading them.
Christoph
Raúl Wild-Spain schrieb:
Finally! yesterday I did my first backup and it seems ok, but I've some doubts about various messages:

FAILURE AND STRANGE DUMP SUMMARY:
  xaloc  /dev/sdc2 lev 0 STRANGE


FAILED AND STRANGE DUMP DETAILS:

/-- xaloc  /dev/sdc2 lev 0 STRANGE
sendbackup: start [xaloc:/dev/sdc2 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it
? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it
? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it
| Total bytes written: 4793784320 (4.5GB, 3.3MB/s)
sendbackup: size 4681430
sendbackup: end
\
I've looked at the index files of  _dev_sdc2 and the list seems to be ok. Then I suppose the mentioned users was connected ( from home) when amanda did the backup (0:45). It seems, true? 

No problem with the rest of filesystems ( or it seems ).

Best Regards,

Raúl
[EMAIL PROTECTED]







Re: Q: finally!!! my first backup ... but :-)

2003-03-06 Thread Raúl Wild-Spain
Ok! thanks, Christoph (and Toomas again), but ... does it exist any solution in these 
cases? or  must I have to be satisfied and try a "post-backup" (manually or not) of 
these files ?

thanks again,



- Original Message - 
From: "Christoph Scheeder" <[EMAIL PROTECTED]>
To: "Raúl Wild-Spain" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 06, 2003 11:20 AM
Subject: Re: Q: finally!!! my first backup ... but :-)


> Hi,
> Your guess is correct,
> this messages are the result of an active filesystem.
> The backup itself is ok, but these specific files will
> probably be bad, as they have been modifyd while tar was reading them.
> Christoph
> 
> Raúl Wild-Spain schrieb:
> > Finally! yesterday I did my first backup and it seems ok, but I've some doubts 
> > about various messages:
> > 
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   xaloc  /dev/sdc2 lev 0 STRANGE
> > 
> > 
> > 
> > FAILED AND STRANGE DUMP DETAILS:
> > 
> > /-- xaloc  /dev/sdc2 lev 0 STRANGE
> > sendbackup: start [xaloc:/dev/sdc2 level 0]
> > sendbackup: info BACKUP=/bin/tar
> > sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
> > sendbackup: info COMPRESS_SUFFIX=.gz
> > sendbackup: info end
> > ? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it
> > ? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it
> > ? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it
> > | Total bytes written: 4793784320 (4.5GB, 3.3MB/s)
> > sendbackup: size 4681430
> > sendbackup: end
> > \
> > 
> > I've looked at the index files of  _dev_sdc2 and the list seems to be ok. Then I 
> > suppose the mentioned users was connected ( from home) when amanda did the backup 
> > (0:45). It seems, true? 
> > 
> > No problem with the rest of filesystems ( or it seems ).
> > 
> > Best Regards,
> > 
> > Raúl
> > [EMAIL PROTECTED]
> > 
> > 
> > 
> 
> 




Re: Win32 Backup?

2003-03-06 Thread Anthony A. D. Talltree
I've had weird stuff happen to me when writing across 

samba mounts -- the files would quietly disappear under the Nethood
pseudo-directory, eating up disk space while being inaccessible.  Associating
the mounts with drive letters seems to avoid this.



Re: Q: finally!!! my first backup ... but :-)

2003-03-06 Thread Toomas Aas
Hi!

> Finally! yesterday I did my first backup and it seems ok, but I've
> some doubts about various messages:
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   xaloc  /dev/sdc2 lev 0 STRANGE

The STRANGE message is generally nothing harmful. It means that the 
backup program exited with non-standard but non-fatal error code. See 
below for details:

> ? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it
> ? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it
> ? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it

So the mail arrived to these mailboxes while they were being read by 
gtar. You can check with amrecover whether these files were backed up. 
I use dump for backup myself so I don't know about gtar, but I'd guess 
you're OK.

BTW, please accept my sincere sympathy for running Lotus Domino :-)
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* How can you tell when you've run out of invisible ink?



Amanda time-out

2003-03-06 Thread Jeroen Heijungs
Dear listmembers,

I have a little problem here which I cannot solve so far:
We have some 13 servers (all FreeBSD in various versions from 3.5 to 4.7)
which I backup using Amanda 2.4.2, there are servers "before" a firewall,
and servers "behind" a firewall. All servers are backed up fine, it really
is trouble free, except for one of the servers behind the firewall. That
one (mailrelay server) was backed-up fine untill it became a production
server, suddenly it had every night a time-out error: 

"mailrelay. /var lev 0 FAILED [Request to mailrelay..xx timed out.]"
for all filesystems.

At first I suspected the resolver or DNS, because this kind of problems
happened before by a wrong resolver, but that was not the case, also no
secondary IP adresses at the nic, after that I checked and increased the
timeout parameters: 

- etimeout is now at 2400 
- ctimeout is now at 120
amandad.debug started at 02:40:01, and ended at 02:41:25 at that server so
that should be enough, but the only effect so far is that the whole job is
taking an awfully long time to complete.

There are only two thing that seem to help:
- leave out the biggest file system (/dev/ad0s1f24G   738M21G
3%/usr), then everything runs smoothly
- back up the same server two times (1-time by name, 2-time by IP-adress),
the first (name or IP-adress) to appear in the "disklist" is going well,
the second gets the error (??? that I do not understand, I stumbled upon
this when I tried the resolver and DNS solutions)

The error is always the same in amandad.debug:
Amanda 2.4 REP HANDLE 009-80FD0708 SEQ 1046914809
OPTIONS maxdumps=1;
/etc 0 SIZE 1260
/etc 1 SIZE 30
/home 0 SIZE 15710
/home 1 SIZE 40
/usr/local 0 SIZE 63730
/usr/local 1 SIZE 11610
/var 0 SIZE 9270
/var 1 SIZE 5020


amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, retrying
amandad: waiting for ack: timeout, giving up!
amandad: pid 75481 finish time Thu Mar  6 02:41:25 2003



Perhaps someone has a bright idea??

tia
Jeroen Heijungs
Het Muziektheater
Amsterdam, The Netherlands



Q: NOTE by amcheck

2003-03-06 Thread Raúl Wild-Spain
Hi! After my first succesfully try with amanda I've been changed my disklist to adjust 
them not for filesystems but for the important directories I want to backup. In this 
case amcheck says the following:

NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.notesini: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.notesini: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.recursosBD: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.recursosBD: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.namesBD: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.namesBD: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.mail: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.mail: does not exist
NOTE: info dir /var/lib/amanda/furv/curinfo/xaloc/_.aplicacionsFURV: does not exist
NOTE: index dir /var/lib/amanda/furv/index/xaloc/_.aplicacionsFURV: does not exist


Should I suppose that amanda will create the necessary directories and files when 
needed although it not indicates " NOTE: it will be created on the next run"? or I 
must to do this "by hand"?

The man page of amcheck isn't clear about this ...

- comment : -  /.x are softlinks to every directory or file I want to backup

Best Regards,

Raúl
[EMAIL PROTECTED]





Q: finally!!! my first backup ... but :-)

2003-03-06 Thread Raúl Wild-Spain
Finally! yesterday I did my first backup and it seems ok, but I've some doubts about 
various messages:

FAILURE AND STRANGE DUMP SUMMARY:
  xaloc  /dev/sdc2 lev 0 STRANGE



FAILED AND STRANGE DUMP DETAILS:

/-- xaloc  /dev/sdc2 lev 0 STRANGE
sendbackup: start [xaloc:/dev/sdc2 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./notesdata/mail/sdelamoc.nsf: file changed as we read it
? gtar: ./notesdata/mail/spaxtonl.nsf: file changed as we read it
? gtar: ./notesdata/mail/xguardio.nsf: file changed as we read it
| Total bytes written: 4793784320 (4.5GB, 3.3MB/s)
sendbackup: size 4681430
sendbackup: end
\

I've looked at the index files of  _dev_sdc2 and the list seems to be ok. Then I 
suppose the mentioned users was connected ( from home) when amanda did the backup 
(0:45). It seems, true? 

No problem with the rest of filesystems ( or it seems ).

Best Regards,

Raúl
[EMAIL PROTECTED]






Re: Compiling on Slackware 8.1

2003-03-06 Thread Christoph Scheeder
Hi,
is it possible you have a mismatch between installed libraris and header-files?
on my linux-system __ctype_b is defined in /usr/include/ctype.h.
Christoph
John Williams schrieb:
At 10:47 PM 3/5/2003 +0100, Paul Bijnens wrote:

John Williams wrote:

I've been using Amanda-2.4.2 for several months and decided to upgrade.

I configured 2.4.4  without any obvious problems (to me) but it fails 
on the
make.  Any ideas about the errors?  Thanks!


I run Amanda 2.4.4 on slackware 8.1 too.  It's my tapeserver.
It compiled without a hitch.
You did make a "make distclean" before you did "./configure ...", did 
you?
Just in case...

Paul


Yep, tried that.  I even backed down to the original binutils, gcc, 
make, etc..
that came with Slackware 8.1.  I've also removed the old version of Amanda
but make still dies in the same place.  It must be something I've 
installed on my
Slackware tapeserver because it compiled fine on another Slackware 8.1 box.

Thanks!

John






Re: Win32 Backup?

2003-03-06 Thread Michael Perry
Anthony A. D. Talltree wrote:
I've never had to do this, but an approach that I'd probably persue
would be to use Symmantec/Norton Ghost to create occasional disk images
that would get xferred via Samba to a *ix filesystem.  I'd try real
hard to keep important data off of the M$ machine's local disks.
One way I have done it is to use MS's backup program to backup to a 
samba share on a freebsd box. MS backup will happily backup to a samba 
share.  Then I just backup all that stuff using amanda.

I've used MS backup on XP Pro and w2kpro this way and it works pretty 
well for my needs.

--
Michael Perry | Do or do not. There is no try. -Master Yoda
[EMAIL PROTECTED] | http://www.lnxpowered.org