This is my current exclude list.. nothing seems to work:
\\System Volume Information
\\System Volume Information\\*
\System Volume Information\*
\System Volume Information
System Volume Information
\\System Volume Information
\\System Volume Information\\*
\System Volume Information\*
\System
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
On Mon, Mar 14, 2011 at 01:21:02PM -0700, Aaron Vinson wrote:
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\*
On 6/14/06, Jon LaBadie [EMAIL PROTECTED] wrote:
I only recently noticed the -N option to smbtar
(-TN for smbclient). This allows backups based
on a file's timestamp being newer than a control
file.
Using the archive bit, as is now done, has several
problems. For example, other apps might
On Thu, Jun 15, 2006 at 11:37:52AM -0700, Paddy Sreenivasan wrote:
On 6/14/06, Jon LaBadie [EMAIL PROTECTED] wrote:
I only recently noticed the -N option to smbtar
(-TN for smbclient). This allows backups based
on a file's timestamp being newer than a control
file.
Using the archive bit,
Paddy Sreenivasan schreef:
On 6/14/06, Jon LaBadie [EMAIL PROTECTED] wrote:
I only recently noticed the -N option to smbtar
(-TN for smbclient). This allows backups based
on a file's timestamp being newer than a control
file.
Using the archive bit, as is now done, has several
problems. For
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
Paul Bijnens wrote:
Paddy Sreenivasan schreef:
On 6/14/06, Jon LaBadie [EMAIL PROTECTED] wrote:
I only recently noticed the -N option to smbtar
(-TN for smbclient). This allows backups based
on a file's timestamp being newer than a control
file.
Using the archive bit, as is now done, has
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
On Thu, Sep 01, 2005 at 07:42:36AM +0200, Gregor Ibic wrote:
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
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 to
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
Just to provide some closure, I sent the relevant details about this bug
to samba-technical list, and it turned out to indeed be a Samba bug. A
developer sent me a patch last night that seems to have solved the
problem. Thanks for everyone's help here!
-Fran
Hi, Fran,
on Samstag, 17. Jänner 2004 at 19:53 you wrote to amanda-users:
FF Just to provide some closure, I sent the relevant details about this bug
FF to samba-technical list, and it turned out to indeed be a Samba bug. A
FF developer sent me a patch last night that seems to have solved the
On Saturday 17 January 2004 13:53, Fran Fabrizio wrote:
Just to provide some closure, I sent the relevant details about this
bug to samba-technical list, and it turned out to indeed be a Samba
bug. A developer sent me a patch last night that seems to have
solved the problem. Thanks for
Samba 3.0.1.
On Sat, 2004-01-17 at 15:51, Gene Heskett wrote:
On Saturday 17 January 2004 13:53, Fran Fabrizio wrote:
Just to provide some closure, I sent the relevant details about this
bug to samba-technical list, and it turned out to indeed be a Samba
bug. A developer sent me a patch
On Saturday 17 January 2004 17:01, Fran Fabrizio wrote:
Samba 3.0.1.
On Sat, 2004-01-17 at 15:51, Gene Heskett wrote:
On Saturday 17 January 2004 13:53, Fran Fabrizio wrote:
Just to provide some closure, I sent the relevant details about
this bug to samba-technical list, and it turned out to
Hi, Fran Fabrizio,
on Mittwoch, 14. Jänner 2004 at 22:51 you wrote to amanda-users:
FF To make a long story short, my attempts to backup a Samba share from a
FF W2k3 ADS server are failing in the range of 755698176 - 763534336 bytes
FF into the tar operation. I can even rename the files and
Hi, Fran Fabrizio,
on Mittwoch, 14. Jänner 2004 at 22:51 you wrote to amanda-users:
FF To make a long story short, my attempts to backup a Samba share from a
FF W2k3 ADS server are failing in the range of 755698176 - 763534336 bytes
FF into the tar operation. I can even rename the files and
Do you get any error messages? What does AMANDA tell you?
What´s in the logfiles for AMANDA and/or Samba?
Amanda reports STRANGE, and the logs show SMB signing errors (which I've
googled extensively for with no luck, and posted to the Samba list but no
luck there either). The process will be
Another fast-google:
http://lists.samba.org/archive/samba-technical/2003-October/032249.html
I know that signing is working between the server and client at least
initially, since I can successfully retrieve 750MB or so of data, and on
shares that are smaller than that, I can get the entire
Hi, Fran,
on Donnerstag, 15. Jänner 2004 at 14:41 you wrote to amanda-users:
You could also test if your backup works with security = share if
your setup allows.
FF Good idea, just tried it, failed at the same spot. This is seeming more
FF and more like a bug and less like a configuration
Wow...I see what you've pointed out in the man page. This is what I
read in the HOWTO:
From the Official Samba-3 HOWTO (Section 6.6.3, page 80):
Windows 2003 requires SMB signing. Client-side SMB signing has been
implemented in Samba 3.0. Set client use spnego = yes when
communicating with a
Hi, Fran,
on Donnerstag, 15. Jänner 2004 at 16:13 you wrote to amanda-users:
FF Wow...I see what you've pointed out in the man page. This is what I
FF read in the HOWTO:
From the Official Samba-3 HOWTO (Section 6.6.3, page 80):
FF Windows 2003 requires SMB signing. Client-side SMB signing
Sorry for not being clear, yes I did test with the configuration you
suggested...
Here's the [global] that I just tested on your suggestion:
-bash-2.05b$ more /usr/local/samba/lib/smb.conf
[global]
#realm = ciswinnet.cis.uab.edu
workgroup=CISWINNET
#security = ADS # have also tried DOMAIN and
On Thursday 15 January 2004 08:31, Fran Fabrizio wrote:
Do you get any error messages? What does AMANDA tell you?
What´s in the logfiles for AMANDA and/or Samba?
Amanda reports STRANGE, and the logs show SMB signing errors (which
I've googled extensively for with no luck, and posted to the Samba
Hi, Fran,
on Donnerstag, 15. Jänner 2004 at 16:46 you wrote to amanda-users:
FF -bash-2.05b$ smbclient snapper\\dfs password -U Administrator -W
FF CISWINNET -D home -d1 -Tqca /tmp/junkme.tar
FF [2004/01/15 09:45:18, 1] client/client.c:do_connect(2597)
FF Domain=[CISWINNET] OS=[Windows
On Thursday 15 January 2004 08:07, Stefan G. Weichinger wrote:
Hi, Fran Fabrizio,
on Mittwoch, 14. Jnner 2004 at 22:51 you wrote to amanda-users:
FF To make a long story short, my attempts to backup a Samba share
from a FF W2k3 ADS server are failing in the range of 755698176 -
763534336 bytes
The only question I would be able to come up with Fran, is:
Whats the posibility that the login thru the samba server has a
timeout that roughly corresponds to that amount of data transmitted?
Hrmm...excellent thought. Let's do some timings and see if it looks
suspicious. When I run it on
Bluhm/CLE/MS/PHILIPS)
Subject:Re: Samba backups failing after a specific amount of data
Classification:
The only question I would be able to come up with Fran, is:
Whats the posibility that the login thru the samba server has a
timeout that roughly corresponds
PROTECTED]
440-483-5323
[EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
01/15/2004 12:37 PM
To: Fran Fabrizio [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
(bcc: Tobias Bluhm/CLE/MS/PHILIPS)
Subject:Re: Samba backups failing after a specific amount of data
I've also asked about this on the Samba lists but I'm guessing that
since we here are in the backup business we're the most likely to have
encountered the particular Samba quick I seem to be hitting.
To make a long story short, my attempts to backup a Samba share from a
W2k3 ADS server are
I'm moving over to use SAMBA based AMANDA backups, and have to start
using gnutar.
If my amcheck tells me...
ERROR: edinburgh: [GNUTAR program not available]
ERROR: edinburgh: [can not read/write
/usr/local/var/amanda/gnutar-lists/.: No such file or directory]
Client check: 1 host checked in
Does /usr/local/bin/tar exist (and is it executable) on edinburgh ?
Frank
--On Friday, June 14, 2002 16:29:27 +0100 Kenny MacPherson
[EMAIL PROTECTED] wrote:
I'm moving over to use SAMBA based AMANDA backups, and have to start
using gnutar.
If my amcheck tells me...
ERROR: edinburgh:
MacPherson; [EMAIL PROTECTED]
Subject: Re: GNU tar and SAMBA backups
Does /usr/local/bin/tar exist (and is it executable) on edinburgh ?
Frank
--On Friday, June 14, 2002 16:29:27 +0100 Kenny MacPherson
[EMAIL PROTECTED] wrote:
I'm moving over to use SAMBA based AMANDA backups, and have
-
From: Frank Smith [mailto:[EMAIL PROTECTED]]
Sent: 14 June 2002 16:48
To: Kenny MacPherson; [EMAIL PROTECTED]
Subject: Re: GNU tar and SAMBA backups
Does /usr/local/bin/tar exist (and is it executable) on edinburgh ?
Frank
--On Friday, June 14, 2002 16:29:27 +0100 Kenny MacPherson
[EMAIL
Smith'; [EMAIL PROTECTED]
Subject: RE: GNU tar and SAMBA backups
Yes it does!!
edinburgh.root(7)= ls -al /usr/local/bin/tar
-rwxr-xr-x 1 root other 835584 Jun 14 13:08
/usr/local/bin/tar
--
Kenny MacPherson
IT Manager
DDI: +44 131 272 7091
-Original Message-
From: Frank
a new version, get a copy of tar from
ftp://alpha.gnu.org/gnu/tar/.
I started running samba backups a few days before I ran across the
first reference to a problem with gnutar 1.13. It turns out that's the
version that runs on my smbclient host, yet the indexes displayed by
amrecover and the two
About 2 weeks ago I asked the following:
I'm backing up a single W2K machine to my tape server.
There are 4 partitions on the windows box. Some nights
al 4 partitions are processed normally. Most nights
1 or more of the partitions fail with the query
host offline? which obviously it is
About 2 weeks ago I asked the following:
I'm backing up a single W2K machine to my tape server.
There are 4 partitions on the windows box. Some nights
al 4 partitions are processed normally. Most nights
1 or more of the partitions fail with the query
host offline? which obviously it is
I'm backing up a single W2K machine to my tape server.
There are 4 partitions on the windows box. Some nights
al 4 partitions are processed normally. Most nights
1 or more of the partitions fail with the query
host offline? which obviously it is not as the other
partitions are backing up.
I've
I have compiled Samba 2.4.2 with:
Do you mean Amanda 2.4.2? Why not 2.4.2p1?
./configure --with-libsmbclient (and the other options are the same as
the ones that worked before)
There is no --with-libsmbclient option to ./configure with Amanda.
What were you trying to accomplish?
[adlcds1 ]#
Hmmm!
I have compiled Samba 2.4.2 with:
./configure --with-libsmbclient (and the other options are the same as
the ones that worked before)
Added:
[adlcds1 ]# cat /etc/amandapass
//WEBAPP/Web asifiwouldtellapubliclist
Added:
[adlcds1 ]# cat disklist
adlcds1 //WEBAPP/Web comp-tar
BUT
Eric Wadsworth [EMAIL PROTECTED] wrote:
I'm just starting out, but I understood that excludes didn't work with
samba shares when using GNUTAR. I've been working around that limitation,
AFAIK exclude works with samba in 2.4.2 but didn't work in 2.4.1p1.
The results of my backups verify this.
On 5 Dec 2000, Roland E. Lipovits wrote:
Eric Wadsworth [EMAIL PROTECTED] wrote:
I'm just starting out, but I understood that excludes didn't work with
samba shares when using GNUTAR. I've been working around that limitation,
AFAIK exclude works with samba in 2.4.2 but didn't work in
to suggestions... if the excludes actually work on samba
shares, let me know!
--- Eric
On 5 Dec 2000, Roland E. Lipovits wrote:
I'm using samba-backups with an exclude-statement (specified in
the disklist-file). As far as I read from the files in /tmp/amanda
the exlusion is only used when
On Tue, Dec 05, 2000 at 04:08:03AM +0100, Roland E. Lipovits wrote:
I'm using samba-backups with an exclude-statement (specified in
the disklist-file). As far as I read from the files in /tmp/amanda
the exlusion is only used when backuping, not when estimating.
Bug or feature? (BTW: amanda
51 matches
Mail list logo
