2012/8/20 Arnold Krille arn...@arnoldarts.de:
From looking at the help, I couldn't whether this option is only to
specify the directory where the tars are written or if this is also
used to find the backuppc-data. And its very strange to write the tars
by default to the same directory where
Hi again Oliver,
=
If you want to check what smbclient can see as shares you can use the
following command line:
smbclient -L SERVERNAME -U USERNAME (-I instead of L if you are going by IP)
=
The following is the output of the commant smbclient -L -U;
Hi again Oliver,
=
If you want to check what smbclient can see as shares you can use the
following command line:
smbclient -L SERVERNAME -U USERNAME (-I instead of L if you are going by IP)
=
The following is the output of the commant smbclient -L -U;
Hi gshergill,
Can you check if you have in your samba.conf file the following line:
msdfs proxy = no
If so, can you try removing it and retesting the listing of the data on
the shares ?
Regards,
Olivier
--
Live
Hi Oliver,
Can you check if you have in your samba.conf file the following line:
msdfs proxy = no
If so, can you try removing it and retesting the listing of the data on
the shares ?
I don't have a samba.conf file, however, I assume you mean smb.conf?
In that file
My bad, did mean smb.conf.
The only thing I added to the global section of the smb.conf file is this:
#=== Share Definitions ===
workgroup = GAULTETFREMONT
netbios name = srvbkpp03
security = ADS
preferred master = no
disable spoolss =
Hi Oliver,
==
By the way, which version of samba are you using ?
Because with Samba 3.2, you'll have some trouble getting it to connect
to Windows Server 2008.
==
This is interesting...
root@backuppc:~# samba --version
The program 'samba' is currently not installed.
smbclient --version would be better :)
I am running Version 3.5.6
Regards,
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT
Hi Oliver,
=
smbclient --version would be better
=
root@backuppc:~# smbclient --version
Version 3.6.3
Newer version to yourself, that shouldn't be an issue I think?
Kind Regards,
gshergill
+--
|This
Hello,
Kinda out of idea now ^^ knowledge out, except for one last thing, but
since you are able to check the shares it shouldn't be it. Have you tried
deactivating the firewall on the windows 2008 server for all networks
?(Pro / Home / Public) ?
Regards,
Hi Oliver,
=
smbclient
Hi Oliver,
=
Kinda out of idea now ^^ knowledge out, except for one last thing, but
since you are able to check the shares it shouldn't be it. Have you tried
deactivating the firewall on the windows 2008 server for all networks
?(Pro / Home / Public) ?
=
I
One last thing though, could you try creating a user on the windows 2008
server. Give it admin rights and then try to connect to the share using
said account ?
Regards,
Hi Oliver,
=
Kinda out of idea now ^^ knowledge out, except for one last thing, but
since you are able to
Hi Oliver,
==
One last thing though, could you try creating a user on the windows 2008
server. Give it admin rights and then try to connect to the share using
said account ?
==
Unfortunately that didn't work. Here is the error in xfer log;
Running: /usr/bin/smbclient
Hi Oliver,
Just a random question, but do you back up linux machines?
It keeps failing for me at the point where it tries the file;
/proc/kcore
At this point it see's it's in use and aborts the backup... any way around that
which you know?
Thanks again.
Kind Regards,
gshergill
You need to exclude /proc from your backups. It's a virtual file
system maintained by the kernel, and does not need to be backed up.
Here's the excludes we use for Linux hosts:
$Conf{BackupFilesExclude} = {
'*' = [
'/dev',
'/proc',
'/tmp_mnt',
'/var/tmp',
'/tmp',
Hi Ray,
=
You need to exclude /proc from your backups. It's a virtual file system
maintained by the kernel, and does not need to be backed up.
Here's the excludes we use for Linux hosts:
...
=
This sounds to me like a stupid question, but I assume I add that
Try this:
$Conf{XferMethod} = 'rsync';
$Conf{BackupFilesExclude} = ['/proc', '/sys', '/tmp', '/dev'];
/proc, /sys and /dev will produce errors if you don't exclude them...
--
Johan Wilfer
2012-08-21 17:19, gshergill skrev:
Hi Oliver,
Just a random question, but do you back up linux
Gshergill-
Please refer to the abundant documentation on this topic. Here's a good
starting point, though the section on Linux excludes is just plain wrong.
The Windows excludes are quite good.
http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Common_backup_excludes
On Tue, Aug
Hi Ray,
=
You need to exclude /proc from your backups. It's a virtual file system
maintained by the kernel, and does not need to be backed up.
Here's the excludes we use for Linux hosts:
...
=
I am running that now on the Linux Machines, hopefully all is
Hi guys,
Johan,
===
Try this:
$Conf{XferMethod} = 'rsync';
$Conf{BackupFilesExclude} = ['/proc', '/sys', '/tmp', '/dev'];
===
From reading the config file it seems you need to add the '*' part that Ray
mentioned, to define it as being for rsync.
Thanks though.
Ray Frush ray.fr...@avagotech.com wrote on 08/21/2012 11:30:22 AM:
You need to exclude /proc from your backups. It's a virtual file
system maintained by the kernel, and does not need to be backed up.
Here's the excludes we use for Linux hosts:
$Conf{BackupFilesExclude} = {
'*' = [
Using '*' works also for the windows shares (at least when using samba).
So you don't have to specify C$, D$...
As for the syntax, personnally, had to actually tweak it a bit, for 2k3
and 2k8 servers:
* always use backward slashes
* don't double the first backward slashes
* Through the web
On Tue, Aug 21, 2012 at 11:51 AM, Olivier Ragain orag...@chryzo.net wrote:
However, as explained in the documentation, you can only create one
default config that will be applied to every hosts. If an host is an
exception, you have to manually edit its conf file. Usually, I use the
web
23 matches
Mail list logo
