> Is it possible not to follow simbolic link on client?
Since the smb protocol doesn't have the notion of symbolic links,
by default samba makes symbolic links look like the file or directory
they point at. So a symbolic link mh -> . looks like an infinitely
deep tree of directories.
Samba has an option for turning this off. From the smb.conf man page:
follow symlinks (S)
This parameter allows the Samba administrator to stop
smbd from following symbolic links in a particular
share. Setting this parameter to "No" prevents any file
or directory that is a symbolic link from being fol-
lowed (the user will get an error). This option is
very useful to stop users from adding a symbolic link
to /etc/passwd in their home directory for instance.
However it will slow filename lookups down slightly.
This option is enabled (i.e. smbd will follow symbolic
links) by default.
So you can avoid this problem by turning off symlinks on the share
you are backing up.
However, this raises a bigger issue. For backing up linux file
systems, doing it through samba isn't a great choice. For example,
with the above option turned off, all symlinks will be skipped.
I probably need to implement additional mechanisms (other than
smbclient) for extracting the backup data for linux/unix clients.
Examples could include nfs, something (eg: tar) over ssh, rsync etc.
My guess is tar over ssh would be easiest to implement. This will
also make all the file attributes (modes and ownership) available to
BackupPC when it eventually supports attribute saving. I'll add this
to the todo list.
Does anyone have a recommendation or preference?