Automatic time-set sbackup on smb share is not working while manual backup is working

Bug #212015 reported by mb
4
Affects Status Importance Assigned to Milestone
sbackup
Invalid
Undecided
Unassigned
sbackup (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hello,

I have Problems with sbackup 0.10.4 and samba shares using it on ubuntu 8.04 hardy with recent updates.

Reproduce this by:
1. install sbackup from the hardy repos
2. open Backup Properties program
3. choose “use recommended backup settings”
4. switch to “use custom backup settings”
5. modify Tab Destination: use a remote directory. Past an address to a samba share (e.g. smb://buero-server/fileserver/backups/sbackup/max-notebook)
6. run the “Test” button on the right side of the editfield
7. get a green ball on the left: “Target dir is writable”
8. klick on the Button “Safe” and than “Backup Now!”
9. it will work and create a .ful backup on your smb share

however, time-set automated backup will not work:
10. choose Tab “Time”, set Do backups to hourly, press Safe
11. wait an hour or previously set a precise time to not wait so long
12. nothing will happen on your smb share, not even a folder will be created

Setting destination to /var/backup or any other folder or mount the smb share with smbfs or cifs will work.

I am wondering, why manual backups on the Samba share is working an automated backups do not.

My sbackup.conf is attached. If you need more information about this problem, let me know.

Regards
Maximilian

Revision history for this message
mb (maxbloemer) wrote :
Revision history for this message
Dan Lea (danlea) wrote :

This is also an issue for me, but it's more of a wishlist entry than a bug since samba shares don't appear to be explicitly supported. My share requires a password, and it doesn't seem to be saved (despite selecting remember forever), so I expect this would be a problem.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thank you for taking the time reporting this bug.

At the moment I am unable to confirm this issue with sbackup 0.10.x due to the lack of a configured SAMBA share.

Moreover, please note, that most development work takes place on the forked project NSsbackup. It would help a lot if one of you could test the usecase described above with NSsbackup - but I really don't know whether it works or not. So, please just give it a try and help making it better. You can use it as usual software including installing via package manager.

Have a look at the project's site at https://launchpad.net/nssbackup and the at the FAQs: https://answers.edge.launchpad.net/nssbackup/+faqs.

Thank you.

Jean-Peer

Revision history for this message
Nathan Williams (nathwill-deactivatedaccount-deactivatedaccount) wrote :

just reading the bug notes of OP, the cause seems to pretty clearly be that the sbackup doesn't mount smb share if it's not already mounted; definitely sounds like wishlist as per OP sbackup automated backup works if share is mounted.

possible fixes would be to modify the cron-job for scheduled backups to mount the smb share, or mount it at boot via cifs in /etc/fstab.

wishlist item would be to add a feature to sbackup to check prior to backing up and mount the designated location if not already mounted.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Please re-test with our latest release which can be found at https://edge.launchpad.net/~nssbackup-team/+archive/ppa and post log output etc. if the error is still alive. Thanks.

Changed in sbackup (Ubuntu):
status: New → Incomplete
Changed in sbackup:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for sbackup (Ubuntu) because there has been no activity for 60 days.]

Changed in sbackup (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Setting to invalid because there has been no activity for long time.

Changed in sbackup:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.