Re: [Nssbackup-team] [Bug 622512] [NEW] Cannot backup to smb location
On 23/08/10 03:52, Gotit wrote: Public bug reported: Cannot use an smb location for backup destination as stated on the NSsbackup homepage: Some will do the backup on your hard drive while others will do on a remote location ( on a SSH, FTP, SMB server ... ) . NSsbackup is one of those software. I specified an smb location (smb://homenet/usb_storage/) but when I press the Test button I get a pop-up that states: No plugin could deal with that schema 'smb://homenet/usb_storage/' Running: NSsbackup v0.2.1 Ubuntu 9.04 This has been fixed on NSsbackup 0.3 or Sbackup 0.11 (they're identical now). -- Groetjes, Anton -- Cannot backup to smb location https://bugs.launchpad.net/bugs/622512 You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to nssbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 622496] Re: problem occurs if nssbackup is run with the destination drive not present. It looses the config info.
Thank you for using nssbackup and reporting this issue. I cannot confirm your described behavior. nssbackup works as follows: start the configuration, plug in your external harddrive and specify a directory on the external drive as backup destination. Save your configuration. When running a backup (scheduled or manual), it is checked for the presence of your custom backup destination and used. If the external disk (or whatever is specified) is not found, a message box appears which states: Destination not found. Please make sure the path exists (e.g. by mounting external disk). You can retry or cancel You can now plug in your external disk and proceed or the backup is canceled after 300 sec if you do nothing. I think this is what you expect, isn't it? Slightly different when opening the configuration. If you open the configuration again, without the external drive being present, another error message is showed: Destination path not found. It is set to the default value. Check the value before you save your configuration. That is, the destination value is not saved to disk/modified on disk unless you save your configuration again. Closing the configuration without saving will result in no modification of your previous configuration/specified destination. Purpose of this behavior is not to support a non-existing destination path when modifying the configuration. The user is forced to set the destination to an existing path when he/she sets up a backup. Does it work for you in this way? What I see here, is maybe a feature request. The error message (or choices) that are shown when opening the configuration while the destination is unavailable could be improved. A problem might arise when starting the configuration gui just for running a backup and not for modifying settings. P.S: As you might recognized, nssbackup and SBackup are finally re- merged. SBackup 0.11.x is identical with nssbackup 0.3.x. Development will take place in SBackup (to stop confusion) from now. So, you're invited to use SBackup from now. Thanks. -- problem occurs if nssbackup is run with the destination drive not present. It looses the config info. https://bugs.launchpad.net/bugs/622496 You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to nssbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 622512] Re: Cannot backup to smb location
@Gotit: Thank you for using nssbackup and reporting this issue. Currently there are no updated packages prepared for Ubuntu 9.04. I'll fix this and provide packages ASAP. As you might recognized, nssbackup and SBackup are finally re-merged. SBackup 0.11.x is identical with nssbackup 0.3.x. Development will take place in SBackup (to stop confusion) from now. So, you're invited to use SBackup from now. Thanks. ** Summary changed: - Cannot backup to smb location + No updated packages available for Ubuntu pre-Lucid ** Changed in: nssbackup Status: New = Confirmed ** Changed in: nssbackup Importance: Undecided = Low ** Description changed: Cannot use an smb location for backup destination as stated on the NSsbackup homepage: Some will do the backup on your hard drive while others will do on a remote location ( on a SSH, FTP, SMB server ... ) . NSsbackup is one of those software. I specified an smb location (smb://homenet/usb_storage/) but when I press the Test button I get a pop-up that states: - No plugin could deal with that schema 'smb://homenet/usb_storage/' + No plugin could deal with that schema 'smb://homenet/usb_storage/' Running: NSsbackup v0.2.1 Ubuntu 9.04 Installed the PPA from https://edge.launchpad.net/~nssbackup- team/+archive/ppa + + + - This is fixed in nssbackup 0.3.x. However, no updated packages are available for Ubuntu 8.04, 9.04, 9.10 -- No updated packages available for Ubuntu pre-Lucid https://bugs.launchpad.net/bugs/622512 You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to nssbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Fwd: Re: Logarithmic purge disabled]
Weitergeleitete Nachricht Von: Jean-Peer Lorenz peer@gmx.net An: Anton Feenstra feens...@few.vu.nl Betreff: Re: Logarithmic purge disabled Datum: Mon, 23 Aug 2010 10:54:16 +0200 Good morning Anton, Thank you for looking into SBackup and your bug tracking. Another maintainer able to fix minor flaws would be great. Software maintenance is really time consuming. I'm sorry to tell you, that I've already fixed the purge issue. I'll prepare an updated release within the next days. I've re-implemented it similar to the simple purge: only freestanding snapshots are removed and the removal process is repeated until no freestanding snapshot or at least 1 snapshot remain (within a certain period). The more I think about rebasing of snapshots, the more I dislike the whole idea. It is always dangerous to modify backuped data, even more if it stored in 'foreign' formats (here tar). Moreover, the current implementation of writing TAR snapshot files (snar files) contains errors and updating tarballs in only possible for uncompressed tars. So, I consider to cut rebasing completely. But that's another story... I don't get why it becomes so expensive? Because of the current implementation. Each path that is processed is compared to every stored path in sequential manner. Regards, Jean-Peer Am Montag, den 23.08.2010, 09:37 +0200 schrieb Anton Feenstra: Hi Jean-Peer, I'm considering what how to implement. It seems the rebase operations, although a nice idea, quickly become too costly. As an alternative, I'm considering changing the purge logic to purge incremental snapshots only when their base (full) snapshot is scheduled to purge as well. This is the easy part. More tricky is that we do not want to purge a full (base) snapshot when any of its incremental (child) snapshots should be retained (though I'm not sure when exactly this condition could apply). I'm thinking now on how to implement this (will come back on that). I think it would be best to add a config option for this, like: - purge incremental snapshots individually by re-basing (may be slow) *or* - purge incremental shapshots together with their base (full) snapshot As a sidenote, I think I understand the basic logic of the rebasing, however I don't get why it becomes so expensive? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
Re: [Nssbackup-team] [Fwd: Re: Logarithmic purge disabled]
On 23/08/10 10:55, Jean-Peer Lorenz wrote: Weitergeleitete Nachricht Von: Jean-Peer Lorenzpeer@gmx.net An: Anton Feenstrafeens...@few.vu.nl Betreff: Re: Logarithmic purge disabled Datum: Mon, 23 Aug 2010 10:54:16 +0200 Good morning Anton, Thank you for looking into SBackup and your bug tracking. Another maintainer able to fix minor flaws would be great. Software maintenance is really time consuming. You're welcome! I'm sorry to tell you, that I've already fixed the purge issue. I'll prepare an updated release within the next days. I've re-implemented it similar to the simple purge: only freestanding snapshots are removed and the removal process is repeated until no freestanding snapshot or at least 1 snapshot remain (within a certain period). Great to have this fixed, as this was keeping me back from using nssbackup. Basically, this is now again the old sbackup behaviour, is that right? The more I think about rebasing of snapshots, the more I dislike the whole idea. It is always dangerous to modify backuped data, even more if it stored in 'foreign' formats (here tar). Moreover, the current implementation of writing TAR snapshot files (snar files) contains errors and updating tarballs in only possible for uncompressed tars. So, I consider to cut rebasing completely. But that's another story... Yes, that was also my feeling when this rebasing was discussed on the nssbackup-team. -- Groetjes, Anton _ ___ | | | | _ _ ___,| K. Anton Feenstra | | / \ / \'| | | IBIVU/Bioinformatics - Free University Amsterdam | |( | )| | | De Boelelaan 1083A - 1081 HV Amsterdam - Netherlands | | \_/ \_/ | | | Tel +31 20 59 87783 - Fax +31 20 59 87653 - Room P136 | | | feens...@few.vu.nl - www.few.vu.nl/~feenstra/ | | | Interfacing Space and Beyond... (P. J. Harvey) | |_|___| ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 587911] Re: Logarithmic purge disabled/does not work
** Summary changed: - Logarithmic purge disabled in final release 0.2 + Logarithmic purge disabled/does not work ** Also affects: nssbackup/0.2 Importance: Undecided Status: New ** Also affects: nssbackup/0.3 Importance: Undecided Status: New ** Also affects: nssbackup/devel Importance: High Assignee: Jean-Peer Lorenz (peer.loz) Status: In Progress ** Changed in: nssbackup/devel Status: In Progress = Confirmed ** Changed in: nssbackup/0.2 Status: New = Won't Fix ** Changed in: nssbackup/0.3 Status: New = In Progress ** Changed in: nssbackup/devel Importance: High = Low ** Changed in: nssbackup/0.3 Importance: Undecided = Low ** Changed in: nssbackup/0.3 Assignee: (unassigned) = Jean-Peer Lorenz (peer.loz) ** Also affects: sbackup Importance: Undecided Status: New ** Also affects: sbackup/0.11 Importance: Undecided Status: New ** Also affects: sbackup/trunk Importance: Undecided Status: New ** Changed in: sbackup/0.11 Status: New = Confirmed ** Changed in: sbackup/trunk Status: New = Confirmed ** Changed in: sbackup/0.11 Importance: Undecided = Low ** Changed in: sbackup/trunk Importance: Undecided = Low ** Changed in: sbackup/0.11 Assignee: (unassigned) = Jean-Peer Lorenz (peer.loz) ** Changed in: sbackup/trunk Assignee: (unassigned) = Jean-Peer Lorenz (peer.loz) ** Changed in: sbackup/0.11 Status: Confirmed = Fix Committed -- Logarithmic purge disabled/does not work https://bugs.launchpad.net/bugs/587911 You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to nssbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
