in several ways. We have seen
various versions of samba behave differently. I cannot say I saw
this below, though.
@Chris, could you pls share the updated amsamba-script asap?
My tests suggest that the issue with "[missing size line from
sendbackup]" seems to come from amsamba
and corrected in several ways. We have seen various versions
of samba behave differently. I cannot say I saw this below, though.
Chris, where is that amsamba app to test?
changed. We were
hoping to get a community build out ... but that keeps getting delayed.
It's been refined and corrected in several ways. We have seen various
versions of samba behave differently. I cannot say I saw this below,
though.
I run 4.14.6 on a few servers with amanda-3.5.1 (Debian
Hi @Chris,
that sounds great.
We use 4.13.5 on the backup server
backup@chronos:~$ apt-cache show smbclient|less
Package: smbclient
Source: samba
Version: 2:4.13.5+dfsg-2
so I don't know about 4.14 yet but I just posted an smill diff fix which
seemed to work at the moment for us. Maybe
versions
of samba behave differently. I cannot say I saw this below, though.
-- CH
> -Original Message-
> From: owner-amanda-us...@amanda.org us...@amanda.org> On Behalf Of Tobias Koeck
> Sent: Friday, August 20, 2021 7:54 AM
> To: li...@xunil.at; amanda-users@amand
imate server" configured
a long time ago
The system is Debian 11 (stable) with the installed amanda-server and
amanda-client packages and the samba version the distribution uses
---
root@chronos:/var/log/amanda/client/a2g-3# apt-cache show smbclient
Package: smbclient
Source: samba
Version
Well,
it looked like the same problem but I have "estimate server" configured
a long time ago
The system is Debian 11 (stable) with the installed amanda-server and
amanda-client packages and the samba version the distribution uses
---
root@chronos:/var/log/amanda/client/a2g-3#
Am 18.08.21 um 16:48 schrieb Tobias Koeck:
Yes I have the same problem.
Ah, someone still alive here ;-)
"estimate server" seems to work, can you test and confirm?
Yes I have the same problem.
On 8/14/21 9:51 AM, Stefan G. Weichinger wrote:
I see failing estimates (and dumps) since upgrading from Samba-4.13 to
4.14 (current stable).
sendsize debug file tells me:
Fri Aug 13 23:15:41.022302356 2021: pid 5952: thd-0x557d939ade00:
sendsize: ERROR
Am 14.08.21 um 09:51 schrieb Stefan G. Weichinger:
I see failing estimates (and dumps) since upgrading from Samba-4.13 to
4.14 (current stable).
sendsize debug file tells me:
Fri Aug 13 23:15:41.022302356 2021: pid 5952: thd-0x557d939ade00:
sendsize: ERROR "Application 'amsamba':
I see failing estimates (and dumps) since upgrading from Samba-4.13 to
4.14 (current stable).
sendsize debug file tells me:
Fri Aug 13 23:15:41.022302356 2021: pid 5952: thd-0x557d939ade00:
sendsize: ERROR "Application 'amsamba': ERROR smbclient:
NT_STATUS_OBJECT_NAME_INVALID li
Olivier,
Do not use the 'GNUTAR' program.
Use the amsamaba application.
Jean-Louis
2018-07-04 5:51 GMT-04:00 Olivier :
> Hi,
>
> I noticed that the command
>smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca -
> does not behave the same with Samb
Olivier writes:
> Hi,
>
> I noticed that the command
>smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca -
> does not behave the same with Samba 3 and Samba 4. The smbclient tar
> ends with giving the size of the data transfered, but the message is
&g
Hi,
I noticed that the command
smbclient olivier\\drivec -U on\%password -E -W samba -d0 -Tqca -
does not behave the same with Samba 3 and Samba 4. The smbclient tar
ends with giving the size of the data transfered, but the message is
slightly different and Amanda cannot parse the size
I agree, but in both cases, I use the same smbclient command and version
(the one on Amanda server). The only difference being I once specify the
share as "olivier\\drivec" and the other time I use
"\\olivier\drivec".
The first form is not working, this is the form cut and pas
Am 2018-07-02 um 09:22 schrieb Olivier:
> "Stefan G. Weichinger" writes:
>> Try the command yourself on the shell and use "-d3" or higher to see the
>> debug details.
See the difference ->
> resolve_lmhosts: Attempting lmhosts lookup for name <0x20>
> resolve_wins: WINS server resolution
"Stefan G. Weichinger" writes:
> Am 2018-07-02 um 08:28 schrieb Olivier:
>> Hi,
>>
>> Since I upgraded to Samba 4, I cannot backyp my Windows machine.
>>
>> Poking around, the command used by Amanda sendsize is:
>>
>> Mon Jul 2 00:14:39
Am 2018-07-02 um 08:28 schrieb Olivier:
> Hi,
>
> Since I upgraded to Samba 4, I cannot backyp my Windows machine.
>
> Poking around, the command used by Amanda sendsize is:
>
> Mon Jul 2 00:14:39 2018: thd-0x805422c00: sendsize: Spawning
> "/usr/bin/smb
Hi,
Since I upgraded to Samba 4, I cannot backyp my Windows machine.
Poking around, the command used by Amanda sendsize is:
Mon Jul 2 00:14:39 2018: thd-0x805422c00: sendsize: Spawning
"/usr/bin/smbclient smbclient "olivier\\drivec" -d 0 -U backup -E -W
olivie
Hello!
I finally found time to upgrade samba from 4.1.23 to 4.4.14 and try this out
myself. I'm running amanda 3.3.9 on Slackware 14.2 and had no problems with
samba 4.1.23.
I have applied both patches mentioned. Result: I still get 'Can't translate
pathname [...] to UTF-8' errors
Auftrag von Stefan G. Weichinger [s...@amanda.org]
Gesendet: Mittwoch, 4. Januar 2017 18:40
An: amanda-users@amanda.org; Jean-Louis Martineau
Betreff: need to have samba-4.2.11 on amanda server
I have to upgrade to samba-4.2.11 (gentoo linux) on an amanda server
running amanda-3.4.1
Does anyone know
Jan 18 21:26:31 2017: thd-0x55727b096000: sendbackup: 118:
strange(?): Error reading password from file descriptor 7: empty password
Wed Jan 18 21:26:31 2017: thd-0x55727b096000: sendbackup: 118: strange(?):
Wed Jan 18 21:26:31 2017: thd-0x55727b096000: sendbackup: 114:
normal(|): Domain=[SOMES
21:26:31 2017: thd-0x55727b096000: sendbackup: 118: strange(?):
Error reading password from file descriptor 7: empty password
Wed Jan 18 21:26:31 2017: thd-0x55727b096000: sendbackup: 118: strange(?):
Wed Jan 18 21:26:31 2017: thd-0x55727b096000: sendbackup: 114: normal(|):
Domain=[SOMESOFT] OS
Höhn; 'amanda-users@amanda.org'
Betreff: Re: need to have samba-4.2.11 on amanda server
Hi All,
The attached patch fix amsamba in 3.4.1 to works with newer version of samba.
In 3.3.9 you also need the patch from
https://github.com/zmanda/amanda/commit/585b2139153f8d4a93ccc796983eedfa5a38e6ce
Jean
Hi All,
The attached patch fix amsamba in 3.4.1 to works with newer version of
samba.
In 3.3.9 you also need the patch from
https://github.com/zmanda/amanda/commit/585b2139153f8d4a93ccc796983eedfa5a38e6ce
Jean-Louis
On 06/01/17 09:08 AM, Jean-Louis Martineau wrote:
On 06/01/17 07:18 AM
Am 2017-01-06 um 20:16 schrieb Stefan G. Weichinger:
> -> the amsamba-DLEs were dumped correctly now, no more bad news in the
> report etc
Unfortunately it's not fixed yet, I was too early with my posting.
I will provide logs off-list.
Am 2017-01-06 um 19:56 schrieb Jean-Louis Martineau:
On 06/01/17 01:47 PM, Stefan G. Weichinger wrote:
You point me at commit 585b213 ?
3.4.1 should already have that, as far as I understand.
Post the amsamba debug file and the complete sendbackup debug files so I
can see which argument is
On 06/01/17 01:47 PM, Stefan G. Weichinger wrote:
Am 2017-01-06 um 19:42 schrieb Jean-Louis Martineau:
3.3.9 will not work with newer samba, you must use 3.4.1
The amsamba patch is in the 3_3 branch, you can get it from svn or git.
This server runs
amanda-3.4.1
samba-3.4.5
You point me
Am 2017-01-06 um 19:42 schrieb Jean-Louis Martineau:
3.3.9 will not work with newer samba, you must use 3.4.1
The amsamba patch is in the 3_3 branch, you can get it from svn or git.
This server runs
amanda-3.4.1
samba-3.4.5
You point me at commit 585b213 ?
3.4.1 should already have
:712 Total bytes received: 6034735616
Fri Jan 06 18:18:36.298046851 2017: pid 30627: thd-0x8060200:
sendbackup: Index created successfully
Fri Jan 06 18:18:36.479196763 2017: pid 30625: thd-0x8060200:
sendbackup: critical (fatal): error [no backup size line]
3.3.9 will not work with newer samba
Am 2017-01-06 um 18:43 schrieb Jean-Louis Martineau:
Stefan,
Are you using amsamba? or you are using the old hack that allowed the
program "GNUTAR" to backup samba share?
Your dumptype must have the following lines to use amsamba:
program "APPLICATION"
applicat
Stefan,
Are you using amsamba? or you are using the old hack that allowed the
program "GNUTAR" to backup samba share?
Your dumptype must have the following lines to use amsamba:
program "APPLICATION"
application {
plugin "amsamba"
}
Jean-Louis
Am 2017-01-06 um 15:08 schrieb Jean-Louis Martineau:
If setting an environment variable is required, try setting it in the
amsamba script before all exec call
$ENV{'LANG'} = 'en_US.UTF-8'
I edited amsamba accordingly, test failed again.
To me it seems that the output of smbclient has
On 06/01/17 07:18 AM, Mike Höhn wrote:
> Am Freitag, 6. Januar 2017, 11:40:44 schrieb Stefan G. Weichinger:
>> Anyone using smbclient for backups with late amanda?
>> If yes, which version of samba?
> Stefan,
>
> I've had the same problems with samba 4.4.5 and amanda 3.3
Am Freitag, 6. Januar 2017, 11:40:44 schrieb Stefan G. Weichinger:
> Anyone using smbclient for backups with late amanda?
> If yes, which version of samba?
Stefan,
I've had the same problems with samba 4.4.5 and amanda 3.3.9 on Slackware.
I had found this:
http://www.backupcentral.com/fo
Am 2017-01-05 um 22:47 schrieb Stefan G. Weichinger:
Am 2017-01-04 um 23:08 schrieb Stefan G. Weichinger:
Still problems with samba-4.2.14 and amanda-3.4.1:
? smbclient: tar:943 Fatal: Can't translate pathname
'./Sanit„r/' to UTF-8
? smbclient: NT_STATUS_UNSUCCESSFUL listing
Am 2017-01-04 um 23:08 schrieb Stefan G. Weichinger:
> Still problems with samba-4.2.14 and amanda-3.4.1:
>
> ? smbclient: tar:943 Fatal: Can't translate pathname
> './Sanit„r/' to UTF-8
> ? smbclient: NT_STATUS_UNSUCCESSFUL listing \\*
> ? smbclient: tar
Am 2017-01-04 um 22:24 schrieb Stefan G. Weichinger:
> fyi: samba-4.2.11 : same problems
> rebuilding 4.2.14 now
>
> if problems persist, I contact samba-devs
did so already, see samba-ml.
Still problems with samba-4.2.14 and amanda-3.4.1:
? smbclient: tar:943 Fatal: Can't transl
Am 2017-01-04 um 18:43 schrieb Stefan G. Weichinger:
Am 2017-01-04 um 18:40 schrieb Stefan G. Weichinger:
I have to upgrade to samba-4.2.11 (gentoo linux) on an amanda server
running amanda-3.4.1
Does anyone know if this:
http://www.backupcentral.com/forum/16/263253
... is still an issue
Am 2017-01-04 um 18:40 schrieb Stefan G. Weichinger:
I have to upgrade to samba-4.2.11 (gentoo linux) on an amanda server
running amanda-3.4.1
Does anyone know if this:
http://www.backupcentral.com/forum/16/263253
... is still an issue?
seems more a samba-bug, right?
maybe I should contact
I have to upgrade to samba-4.2.11 (gentoo linux) on an amanda server
running amanda-3.4.1
Does anyone know if this:
http://www.backupcentral.com/forum/16/263253
... is still an issue?
If yes:
JL, could you have a look, please?
Thanks, Stefan
Sounds great. Keep me informed.
-Ursprüngliche Nachricht-
Von: Stefan G. Weichinger [mailto:s...@amanda.org]
Gesendet: Montag, 18. Januar 2016 18:18
An: Tobias Köck; amanda-users@amanda.org
Betreff: Re: smbclient 4.33 - samba 4 problem
Am 2016-01-12 um 10:06 schrieb Tobias Köck
Am 2016-01-12 um 10:06 schrieb Tobias Köck:
> There seem to be a similar problem with smbclient 4.33.
>
>
>
> It works with
>
>
>
> smbclient --version
>
> Version 4.1.17-Debian
>
>
>
> Either the smbclient 4.33 has a problem and/or AMANDA cannot handle the
> new smbclient version.
There seem to be a similar problem with smbclient 4.33.
It works with
smbclient --version
Version 4.1.17-Debian
Either the smbclient 4.33 has a problem and/or AMANDA cannot handle the new
smbclient version.
Greetings
Tobias
Are there any known issues with using samba-4.x as smbclient within
amanda-DLEs ?
I face failing backups since upgrading one server to fedora 23 which
brings Samba 4.3.3 (in this case as an ADS domain member server if that
matters).
$ amcheck -c daily samba01 carplan_sr
Amanda Backup Client
using PKZip to archive the files.
If, instead, I backup the files on my Windows server via Samba (and not
use the ZWC at all), will I be able to recover individual files using
amrestore?
What sort of performance difference might i expect to see in backing up
using the ZWC as opposed to over
on my Windows server via Samba (and not
use the ZWC at all), will I be able to recover individual files using
amrestore?
What sort of performance difference might i expect to see in backing up
using the ZWC as opposed to over Samba? I know I would lose the ability
to backup files that are in-use
. The resulting error message looks
like this:
? NT_STATUS_ACCESS_DENIED listing \System Volume Information\*
My dump definition looks like this:
define dumptype samba-serv-high {
program GNUTAR
comment Shares backed up via SAMBA
compress server fast
index
Amanda Users --
I'm having some difficulty excluding the System Volume Information
directory from a full disk backup. The resulting error message looks
like this:
? NT_STATUS_ACCESS_DENIED listing \System Volume Information\*
My dump definition looks like this:
define dumptype samba-serv-high
\*
My dump definition looks like this:
define dumptype samba-serv-high {
program GNUTAR
comment Shares backed up via SAMBA
compress server fast
index
priority high
exclude /etc/amanda/template.d/samba-exclude
}
In the exclude file I've tried both \\System Volume
Hello All,
I'm trying to backup two Barracuda Message Archiver 450 via CIFS/Samba
and I was wondering if anyone have or know of any resource/examples of
this type of setup. The main problem is (I think) the /etc/amandapass
file is read from the amanda client only. I need to add
For doing the backup with samba, three machine are involved:
- the amanda server, who contacts the amanda client
- the amanda client, who runs smbclient, which contacts the SMB share
- the machine that needs the backup, running
CIFS/samba/native-Windows-share-stuff
Many people configure
On Mon, Feb 1, 2010 at 9:51 AM, Corey Jones co...@sixfeetup.com wrote:
I'm trying to backup two Barracuda Message Archiver 450 via CIFS/Samba and I
was wondering if anyone have or know of any resource/examples of this type
of setup. The main problem is (I think) the /etc/amandapass file
server?
* Can you connect to the destination host using smbclient directly?
* Any entries in the destination hosts logfile (if it's samba)?
--
Marc Muehlfeld (Leitung Systemadministration)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152
I'm pretty sure this is a samba/smbclient error, but, in case you guys
are familiar with a quick fix:
? Call timed out: server did not respond after 2 milliseconds opening
remote file \dhinchcliff\H (\dhinchcliff\)
? Call timed out: server did not respond after 2 milliseconds listing
Marc Muehlfeld wrote:
Dan Brown schrieb:
# disklist
# Design Resources Mac
coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne
coralie //coralie/design_resources/ tar-comp-srvbest-ne
The first column is the name of the machine who connect to the samba
share
I've been through the docs a bunch of times to try to figure out what
exactly I'm doing wrong but either I'm not doing anything wrong
(unlikely) or there's something I keep thinking is right but isn't (more
likely). When I run a check on the Amanda setup, it queries the samba
client (a Mac OS X
Dan Brown schrieb:
# disklist
# Design Resources Mac
coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne
coralie //coralie/design_resources/ tar-comp-srvbest-ne
The first column is the name of the machine who connect to the samba share,
not the client. Here's one
Stefan G. Weichinger schrieb:
The machine must not be the backupserver itself.
You mean:
The machine does not have to be the backupserver itself
Right?
Oh hell. Better I go back home. Getting up at 6am doesn't seem to be good for
me. :-)
Marc
--
Marc Muehlfeld (Leitung
Marc Muehlfeld schrieb:
Stefan G. Weichinger schrieb:
The machine must not be the backupserver itself.
You mean:
The machine does not have to be the backupserver itself
Right?
Oh hell. Better I go back home. Getting up at 6am doesn't seem to be
good for me. :-)
Same here, same here.
Hello!
I just tried to add our Windows server to our Amanda backup.
Basically everything is working, the nightly dump fails
because of dumps way to big.
I want to backup this disklist entry:
hugo10.ka.punkt.de //hugo11/c$ samba-tar
The samba-tar definition looks like this:
define
change the
archive bit and using it as the control only allows
a single level of incremental.
Has the use of the -N option for samba-based backups
been considered? And maybe found wanting?
We have considered using -N option in testing. One drawback is that we need
to touch a file (one file
, as is now done, has several
problems. For example, other apps might change the
archive bit and using it as the control only allows
a single level of incremental.
Has the use of the -N option for samba-based backups
been considered? And maybe found wanting?
We have considered using -N
. For example, other apps might change the
archive bit and using it as the control only allows
a single level of incremental.
Has the use of the -N option for samba-based backups
been considered? And maybe found wanting?
We have considered using -N option in testing. One drawback is that we
need
In my testing it seemed the file could be on the direct client,
not the indirect PC. But I must admit I was only doing it from
the command line. For that I was creating (touch -t ...) the
control file on the linux box then smbtar'ing from a windows host.
This would mean the samba user
several
problems. For example, other apps might change the
archive bit and using it as the control only allows
a single level of incremental.
Has the use of the -N option for samba-based backups
been considered? And maybe found wanting?
We have considered using -N option in testing. One
Hi
Amanda 2.4.5p1 on CentOS 4
Samba 3.0.21b
Windows 2003 SP1
The above setup worked fine 'out of the box' and has been running for
about 6 months or so. Came in to find that one of the backups was taking
ages and when it did finish the samba shares were failing. Looking in
the debug i can
On 2006-04-24 11:11, Tom Brown wrote:
The above setup worked fine 'out of the box' and has been running for
about 6 months or so. Came in to find that one of the backups was taking
ages and when it did finish the samba shares were failing. Looking in
the debug i can see this so not sure
Note the time betwen the first message (0.477) and the next and final
messages (24570.113).
This seems like the problem (solution) described here:
http://wiki.zmanda.com/index.php/Amdump:_mesg_read:_Connection_reset_by_peer
thanks - will see if that helps - There is no firewall between
to be that the one and only Samba mount that I
backup threw 10 megabytes worth of errors like those below into the log
file...
? NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\grads\xu
xi\Hw3\Ch\ifa\draw\images\Diamond1.gif (\home\grads\xuxi\Hw3\Ch\ifa\dr
aw\images\)
... one
I think that if you google on 'NT_STATUS_OBJECT_PATH_NOT_FOUND' you will find
that it is a samba problem, not an amanda one. I used to get lines similar
in reports unrelated to amanda, but unfortunately I can't remember the cure.
I do agree, but it appears to be with the specific manner
I did eventually find the smbclient command Amanda was using (it was in
/var/log/amanda, not /var/log/amanda/mycyclename where I was looking :-)
Running that command from the command line produces the same problem, so
I have forwarded that to the Samba list and we'll see what comes back.
So
that to the Samba list and we'll see what comes back.
So, I think we can close this thread out as far as Amanda is concerned. :-)
All the same, I doubt if you are the only amanda user to come across this, so
if you get a resolution, would you please post it here?
Anne
pgploKgsQdMCP.pgp
Description
the need to migrate from chg-scsi to chg-zd-mtx as
documented in my earlier thread).
This new setup ran for the first time last night, with disastrous
results. More than half of my backup targets had estimate timeouts, and
the root problem seems to be that the one and only Samba mount that I
Wayne Johnson schrieb:
I've added a W2k server to my backup. I'm getting a strange dump
warning. I believe this is just a false alarm, but it would be nice to
get this out of the way. Anyone have suggestions on how to ignore
this? One web page says that there are regular expressions that
I've added a W2k server to my backup. I'm getting a strange dump warning. I believe this is just a false alarm, but it would be nice to get this out of the way. Anyone have suggestions on how to ignore this? One web page says that there are regular expressions that check for errors, and that
I am having troubles excluding files with amanda and samba.
Here is my dumptype:
define dumptype workstation-millerlu {
program GNUTAR
comment worksation
compress server fast
priority high
index yes
exclude ./Local Settings/Application Data/Google
}
And here
Luke Miller schreef:
I am having troubles excluding files with amanda and samba.
Here is my dumptype:
define dumptype workstation-millerlu {
program GNUTAR
comment worksation
compress server fast
priority high
index yes
exclude ./Local Settings/Application Data/Google
I don't understand what's happening when I try to specify Samba shares on the
command line:
[EMAIL PROTECTED]:~$ amadmin DBackup find centernet
Scanning /dumps/amanda2...
Scanning /dumps/amanda...
Scanning /dumps/amanda2...
Scanning /dumps/amanda...
date host
On Wed, Sep 28, 2005 at 10:22:58AM -0700, Kevin Dalley wrote:
Do the files do not get to amanda, even if they are not open on the
next run?
Jon LaBadie [EMAIL PROTECTED] writes:
IIRC you can't do a second open for read of a file already opened.
I'm guessing that it depends on how the
When I mount samba partitions using smbmount and run something like this:
find /mnt/linnet_g/ -type f|xargs wc
I get a number of errors which look like this:
wc: /mnt/linnet_g/analysis.lesion/b19o61/b61o19.9/b61o18.9-042303.332.cbin:
Input/output error
While I don't see exactly this output
As I wrote about issues with samba backup, I can now say that backup
doesnt stall if I enable compression on server (amanda server), and
regulary stalls without compression.
Has to be something wrong with pipeing to tar.
regards,
Gregor
Hi,
I checked and there is plenty of space on all drives, and samba does not
log anything on smbclient behalf.
And I dont run samba server.
Strange that the other amada config dumps fine, and this stalls
everytime on same spot!
regards,
Gregor Ibic
Hm, hm, strange.
I created a new amanda conf with only that share in disklist and it
finishes ok. Could be a problem of indexing? I saw that once a while
sendbackup sends index info, for file indexing purpose.
Could this be a problem? Where can I trace this out.
It seems that is not a
opening ..., 134 unfinished ...
Process 26744 detached
Slightly different interpretation of this trace:
smbclient on the samba server seems to have asked to access some resource
on the pc client, possibly a file or a share, and has already received
a denial. What is happening in the above trace
Here is a process list and strace to smbclient and tar. You can see that
is stalled at some opening of the file.
I modified share name and file name for security reasons.
regards,
gregor
19432 ?S 0:00 /bin/sh /usr/sbin/amdump tape
19442 ?S 0:20
Gregor Ibic wrote:
I have a problem with backuping one samba share. Backup / smbclient
stalls after backuping some data. Files on the server dont have
permission to access them, but it should skip them with errors and
backup other data, but sendbackup stalls and I have to kill smbclient
Ok, I wait for 10 hours (ethernity for me), and I see that it backuped
about 300MB of a 30GB job. Other shares that work are on the same
server, just on the other partition.
Then I kill smbclient and amdump resumes till the end of disklist.
I will try with . (dot) and report, but I notice that
I have a problem with backuping one samba share. Backup / smbclient
stalls after backuping some data. Files on the server dont have
permission to access them, but it should skip them with errors and
backup other data, but sendbackup stalls and I have to kill smbclient to
finish amdump. I dont
: the /etc/amandapass is createdon the right
computer, i.e. the server executing smbclient, that does not
necessarily is the amandaserver itself.
yes, it is setup on the right machine.
Maybe set debugging level on samba very high somehow (e.g.
by replacing smblient with a wrapper like:
exec
boztr0n wrote:
selfcheck: time 0.000: checking disk //rockwell/docs
selfcheck: time 0.000: spawning /usr/bin/smbclient in pipeline
selfcheck: argument list: smbclient \\rockwell\docs -U backup -E -W
NETSETGOODS -c quit
selfcheck: time 0.311: samba access error: //rockwell/docs: Error
connecting
On Fri, Jun 24, 2005 at 03:51:13PM +0200, Paul Bijnens enlightened us:
What is also strange is your statement just before the above
paragraph:
When I take a look at the Amanda logs in /var here is what I see:
because the logs that contain the above lines is in /tmp/amanda/
unless you make
On Fri, Jun 24, 2005 at 10:04:49AM -0400, Matt Hyclak wrote:
On Fri, Jun 24, 2005 at 03:51:13PM +0200, Paul Bijnens enlightened us:
What is also strange is your statement just before the above
paragraph:
When I take a look at the Amanda logs in /var here is what I see:
because the
hey list,
It's my first time playing with Amanda and I've been working for the
past few days to setup one central amanda server on a linux box
(generic fedora 4, using stock Amanda + Samba rpms) to backup a single
directory on 30 or so wintel boxes. Basically where I'm at now is that
amcheck
On Thu, May 19, 2005 at 09:04:46PM +0200, [EMAIL PROTECTED] wrote:
Hello, Filip,
on 19.05.2005, 19:05 you wrote to amanda-users@amanda.org:
FR At 05/18/05 19:35, Bryan K. Walton wrote:
FR (...)
FR Same here, with Amanda 2.4.5 / Samba 3.0.13, running slackware-current
with
FR 2.4.30 kernel
Hello, Filip,
on 19.05.2005, 19:05 you wrote to amanda-users@amanda.org:
FR At 05/18/05 19:35, Bryan K. Walton wrote:
FR (...)
FR Same here, with Amanda 2.4.5 / Samba 3.0.13, running slackware-current with
FR 2.4.30 kernel.
In client-src/sendbackup-gnutar.c there are regular expressions
I tried this:
--- client-src/sendbackup-gnutar.c.orig 2005-05-20 12:46:49.0 +0200
+++ client-src/sendbackup-gnutar.c 2005-05-20 12:31:03.0 +0200
@@ -73,6 +73,7 @@
AM_NORMAL_RE(^[Aa]dded interface),
AM_NORMAL_RE(^session request to ),
AM_NORMAL_RE(^tar: dumped
Dnia 05/24/05 18:05, Tom Brown napisa:
I tried this:
--- client-src/sendbackup-gnutar.c.orig 2005-05-20 12:46:49.0
+0200
+++ client-src/sendbackup-gnutar.c 2005-05-20 12:31:03.0
+0200
@@ -73,6 +73,7 @@
AM_NORMAL_RE(^[Aa]dded interface),
AM_NORMAL_RE(^session
Jon LaBadie wrote:
On Thu, May 19, 2005 at 07:05:15PM +0200, Filip Rembia³kowski wrote:
At 05/18/05 19:35, Bryan K. Walton wrote:
(...)
Same here, with Amanda 2.4.5 / Samba 3.0.13, running slackware-current with
2.4.30 kernel.
If I'm not mistaken, samba version changes in the past have resulted
Dnia 05/20/05 09:18, Paul Bijnens napisa:
Jon LaBadie wrote:
And the irony is that that when amanda believes you have samba
version 2, then the line will be recognized and categorized as
normal instead of strange: see amanda source:
client-src/sendbackup-gnutar.c, line 83 (for amanda-2.4.5
1 - 100 of 466 matches
Mail list logo
