> The source is an internal hdd on another machine mounted using smb > The destination is an external harddrive. > > I have "Ignore ownership" unselected on the destination extenral hard drive. > > I appreciate any help. Thanks. > > I am getting the following output: > > /usr/local/sbin/lbackup backup.conf > Loading Backup Script Configuration Data... > Checking for Pre Action Scripts... > First Run Full Copy... > Using custom rsync : v3... > Synchronizing... > rsync: failed to set file flags on > "/Volumes/extData5/BackupOfCommonOnData/Section.inprogress/common/..DS_Store.0ZVPGH": > Operation not permitted (1) > rsync: failed to set file flags on > "/Volumes/extData5/BackupOfCommonOnData/Section.inprogress/common/.10_procedureForNewDatasets_README.txt.1fJWPC": > Operation not permitted (1) > rsync: failed to set file flags on
<SNIP>
> "/Volumes/extData5/BackupOfCommonOnData/Section.inprogress/common/references/phiX/squashed/.phi.fa.2bpb.V9dK06":
> Operation not permitted (1)
> rsync: failed to set file flags on
> "/Volumes/extData5/BackupOfCommonOnData/Section.inprogress/common/references/phiX/squashed/.phi.fa.vld.VrxJ4J":
> Operation not permitted (1)
>
> Number of files: 160
> Number of files transferred: 111
> Total file size: 30158288908 bytes
> Total transferred file size: 30158288880 bytes
> Literal data: 30158288880 bytes
> Matched data: 0 bytes
> File list size: 6025
> File list generation time: 0.020 seconds
> File list transfer time: 0.000 seconds
> Total bytes sent: 30161981189
> Total bytes received: 2315
>
> sent 30161981189 bytes received 2315 bytes 20455736.52 bytes/sec
> total size is 30158288908 speedup is 1.00
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1039) [sender=3.0.6]
>
> real 24m33.937s
> user 4m55.953s
> sys 5m5.245s
>
> WARNING! : Data Transfer Interrupted
> Loading Mail Script Configuration Data...
> mail config file path :
> /Users/tim/home/backup/lbackup_commonOnData_to_extData5/example_mail.conf
> logFile :
> /Users/tim/home/backup/lbackup_commonOnData_to_extData5/DailyBackup1.log
> logFileArchive :
> /Users/tim/home/backup/lbackup_commonOnData_to_extData5/log_archive
>
> ERROR! : Email recipient address has yet to be configured.
> Log archiving and email reporting and have been automatically
> disabled.
> In order to enable email reporting and log archiving, specify a
> valid email recipient by editing
> the mail configuration file for this backup :
> /Users/tim/home/backup/lbackup_commonOnData_to_extData5/example_mail.conf
>
The upshot is that the issue is most likely due to configuring your backup
destination directly to an SMB mount point. LBackup has no official support for
backing up directly to network mounted file system (even AFP is unsupported).
LBackup has support for push backups to network mounted volumes via virtual
file systems. This is outlined in further detail below for Mac OS X.
First I have some questions :
(1) Which file system is your destination partition using? Assuming you are
running Mac OS X the following command quoted below will provide this
information :
> diskutil info /Volumes/data | grep "File System" | awk -F "File System:"
> '{print $2}' | sed -e 's/^[ \t]*//'
(2) Would you also please run the command quoted below and provide the output
from this command :
> ls -la /Volumes/data/common/.10_procedureForNewDatasets_README.txt
(3) Has this backup been setup and running for a sometime without issues or are
you just now configuring this backup?
(4) If you are running Mac OS X, which version are you using?
(5) One more question, which user is the backup running being executed as and
is it running from cron or directly from the terminal? If you have not yet
scheduled the backup then you could run the command quoted below prior to
running lbackup to find out which user you are logged into the system as :
> whoami
Answers to the questions listed above is a good place to start working out what
is happening.
> The source is an internal hdd on another machine mounted using smb
> The destination is an external harddrive.
As previously mentioned above, this is probably the root cause of the error
message you have been receiving. LBackup is designed for pull network backups
(from a backup client to a backup server). LBackup will support network push
backups as well. Details regarding the pull and push approaches are explained
in further detail at the following URL :
http://www.lbackup.org/network_backup_strategies
I think the errors you are having are relating to SMB not supporting various
meta data such as (some?) file flags. Below I will outline some options
regarding pushing backups to a remote SMB mount. I suggest as a first step try
changing your backup location to a DAS (directly attached storage) just to see
if this resolves the issue. This could even be a locally mounted USB memory
stick formatted HFS+.
Approach #1 - Backup to a disk image located on the remote system :
If you generate a virtual file system (disk image formatted HFS+J) on the
remote SMB file system. Then add a post hook which will mount this disk image
and a post hook which will unmount the disk image once the backup has finished
(example scripts are within the example LBackup configuration directory :
'/etc/lbackup/example_backup_config/resources/exmaple-scripts/'). Finally,
configure LBackup to backup to the virtual file system. This should work and
your backup files will be stored on the remote file system which is mounted
with SMB.
Approach #2 - Backup to a local sparse bundle and then backup to the remote
system :
Generate a local sparse bundle (virtual file system, disk image, formatted
HFS+J) and add in the pre and post hooks as briefly outline above in the
'Approach #1'. Once you have this locally mounting and un-mounting sparse
bundle ready, configure this virtual file system to be the as your backup
destination. Finally, add an additional post hook (which calls rsync to update
the image on your remote file system) or to start a backup chain (eg, another
instance of LBackup to update the remote images and keep previous versions as
well).
The advantage of 'Approach #2' is that you have a local copy of the data and a
remote copy. Using rsync to update the remote copy is normally quite fast as
only the updated bands will need to be synchronized. Essentially, once the
sparse bundle is on the remote file system you will be incrementally backing up
or updating the sparse bundle on the remote system from your local copy.
If you require assistance with putting together a post action script to update
/ backup the disk image to the SMB share then please let me know.
If you have ssh access and rsync on a remotly accessible system you could add a
third backup destination by utilizing the following script to update the remote
sparse bundle via SSH :
http://www.lbackup.org/synchronizing_disk_images_between_machines
The script listed at the link above could be easily modified so that it will
synchronize to a local SMB mount rather than via an SSH. The online script
could be modified even easier. Attached is an example script which will
synchronize a local sparse bundle to a locally accessible directory. If you
have any problems getting this to work then just let me know.
There have certainly been issues in the past using rsync from a ubuntu system
to a FAT, FAT32 or NTFS file system. I am unsure if this issue also exists with
Mac OS X. I would assume that it will also be problematic. As mentioned above
if you want to push your backups via SMB over the network then I think using a
sparse bundle is a good approach and the attached example post action script
will simplify the setup.
Links to related sites discussing rsync failing to set flags :
- http://ubuntuforums.org/showthread.php?t=290111
- http://tinyurl.com/rsync-failed-to-set-file-flags
There is another thread on the mailing list which explains some of the issues
with using an SMB mount as a backup destination directly. Quoted below is
related question from this thread. Following the quotation is a link to the
archived thread.
> 3. symlinks and samba
> ---------------------
> My destination for the backup happens to be a mounted samba drive which lacks
> support of symbolic links. These occur in some situations of my source to be
> backed up.
> Is there a standard way to deal with this situation?
> (I think none of rsync's options satisfactorily handle this particular case:
> I would like to reproduce the exact same state from my backup. --links: With
> the target filesystem's lack of support for symbolic links, simple copying is
> not available.
> --copy-links: Collapsing of links is not the same as keeping them verbatim)
http://tinyurl.com/lbackup-discussion-smb-issue
If you require assistance with implementing this or just have questions about
the approaches mentioned above then please let me know.
I hope this information is helpful.
BACKUP-750-Sync-Sparse-Image-to-Locally-Accessible-Directory.bash
Description: Binary data
_______________________________________________ lbackup-discussion mailing list http://www.lbackup.org Change options or unsubscribe : http://lbackup.org/mailing_lists
