hello,
I encounter a trouble when trying to configure
my Amanda server to backup NT hosts through
the Samba suite:
* Amanda index/tape server: Linux RH7.1
(the server is also an Amanda client)
* Amanda version : 2.4.2p2,
compiled with --with-smb-client=/full/path/...
* Samba version : 2.2
answering my own question:
* Amanda version : 2.4.2p2,
compiled with --with-smb-client=/full/path/...
I tried to recompile again, and checked the
configure output:
$ ./configure ... --with-smblient=/usr/local/samba/bin/smbclient ...
(...)
checking for smbclient... no
(...)
but,
$
[root@tapeserver /root]# amrecover -C Normal
AMRECOVER Version 2.4.2p1. Contacting server on name_server ...
220 tapeserver AMANDA index server (2.4.2p1) ready.
500 Access not allowed: [access as amanda not allowed from root@tapeserver]
amandahostsauth failed
[root@tapeserver /root]#
In
John R. Jackson wrote:
here is a sample of the gnutar list for 1.13 (looks bad) :
2555905 43008 ./kretzsch/mail/communication_OBS
2555905 40960 ./kretzsch/mail/SOHO-news
That's the wrong file. I'm talking about the index files. Those look
like the incremental list file. Look up the
John R. Jackson wrote:
Scanning /the/holdingdisk ...
20010328: found Amanda directory. (*)
20010416: found Amanda directory.
...
(*) these directories are empty.
Just for my own curiosity, why are they still there if they are empty?
I don't know why exactly, sorry. According
On May 3, 2001, Pierre Volcke [EMAIL PROTECTED] wrote:
amrestore: 4: restoring planeto._home_zone10.20010502.0
amrestore: write error: File too large
Alexandre Oliva wrote:
You seem to be bumping into file size limits of the host filesystem.
You may want to pipe the output
hello,
I'm configuring my tape server to run different configurations
(e.g., daily backups and periodic archival runs on the same
filesystems, plus different configurations on separate filesystems)
The FAQ says to set the record no option for archival runs :
I guess it has no effect on
hello again,
I'm trying to am-recover some datas, and I
get the following problem when I run amrecover :
[tape-server]$ amrecover -C conf -s tape-server
amrecover sethost backup-client
amrecover setdisk /the/disk
Scanning /the/holdingdisk ...
20010328: found Amanda directory. (*)
hello,
I get the following message when restoring one of my
full dumps with amrestore:
[tape-serveur]# /usr/local/amanda/sbin/amrestore /dev/nst0 planeto
amrestore: 0: skipping start of tape: date 20010502 label TAPE4
amrestore: 1: skipping jupiter._home_zone1.20010502.2
amrestore: 2:
hello,
I've just installed an Amanda backup client on an AIX 4.3 box.
amanda version : 2.4.2
# client side #
gnu-tar has been installed on this client in
/usr/local/bin/gtar
and to be quite sure, I've also made a link as
/bin/gtar - /usr/local/bin/gtar
On this client,
Mitch Collinsworth wrote:
On Tue, 1 May 2001, Pierre Volcke wrote:
checking for gnutar... (cached) tar
...
(what does this mean?)
This means you didn't rm config.cache before running configure, so
configure used info saved in config.cache from the last time you
ran it. You
CHAN Sing Leung Cyril wrote:
Hi, I want to install the Amanda 2.4.2 in my new Mandrake 7.2 Linux
server. But, I don't know how to start. When I reading the
installation notes. sorry~ I don't understand the procedure. Can you
recommand another document or web site for me to solve this
hello,
my Amanda backup server mounts some NFS filesystems
exported from machines that are in fact
Amanda backup clients.
Should I better install the Amanda client software
on the backup machines, or may I directly
make a reference to the NFS filesystems into the
disklist as if it
hello,
this question was already posted yesterday, but I
got no answer! ;)
1/
When I try to run 'amrecover' to check file index
recovery, here's what it says:
bash$ /usr/local/amanda/sbin/amrecover -C daily1
AMRECOVER Version 2.4.2. Contacting server on *
amrecover: Unexpected
did you check /tmp/amanda/amrecover.*.debug ?
amrecover.debug shows only 1 line:
amrecover: debug 1 pid 16190 ruid 0 euid 0 start time Wed Feb 28
12:13:55 2001
And are you running this on the server ?
if not, you have to specify the server
amrecover -C daily1 -s mytapeserver
hi there,
I'm currently testing my Amanda conf.
This night, a first 'amdump' built a first full dump
of 1 filesystem.
When I try to run 'amrecover' to check file index
recovery, here's what it says:
bash$ /usr/local/amanda/sbin/amrecover -C daily1
AMRECOVER Version 2.4.2. Contacting
Matt McManus wrote:
I have now got amanda running very happily on my network. I have a query
about how to turn hardware compression 'off' on my Quantum DLT4000 drive.
At the moment I use the 'density select' button on the front of the drive,
but I understand that I am able to do this with
hello Isaac,
this is an example, but if your auto-rewind device is /dev/st0,
the non-rewind device is /dev/nst0.
If you want to crontol hardware compression on/off , you may
use the "mt" command (have a look at the man page)
for example:
mt -f /dev/st0 datcompression off
.. but
Can Amanda be used to backup up a Windows Machine, if so when the file is
restored will you have to install Windows first?
yes, Amanda can do that but you have to setup the Samba package first.
See Samba docs about this.
I guess that the files may be restored anywhere if the Windows
I need to back up a Windows pc with Amanda.
I didn't find appropriate documentation about "how configure amanda to
backup Windows client".
Could someone help me?
Tank you very much.
Alessandro Chiauzzi
System Engineer
Dialogos3 s.r.l.
You may use both Samba Amanda to backup your
hello there,
I'm backing up (full incremental) my windows PCs
using Amanda Samba's "smbclient".
Smbclient unset the archive bit on all the backed up
files onto the PC hardisk, so as to make incremental
backups possible.
Does someone have heard about any conflicts with
some
21 matches
Mail list logo
