There have been some upgrades recently (D-Bus) . I am watching it the
next couple of days if it works now. First test looked good :-)
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/
Question #139746 on Simple Backup changed:
https://answers.launchpad.net/sbackup/+question/139746
Fabio Marzocca posted a new comment:
I can confirm this also on my side. I need to download the Natty package 1.25-3
and replace the buggy maverick tar package.
Now it works back again.
--
You rece
Jean-Peer,
new tar v.1.25-3 did fix the problem! Thank you
Fabio
On Sun, Jan 2, 2011 at 5:56 PM, Jean-Peer Lorenz
<670...@bugs.launchpad.net>wrote:
> @Fabio: Please have a look at this similar question:
> https://answers.launchpad.net/sbackup/+question/139746
> Maybe this helps you. Seems like
** Changed in: sbackup
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/670671
Title:
Tar teminated with errors
__
>This option is included in version 0.10.5
I don't think that the general option to purge (as currently included in
sbackup) meets the described feature request. Therefore, I reopen this bug.
Remarks and patches are welcome.
--
You received this bug notification because you are a member of Simp
Basically, I like the idea though I see following issues:
* how to delete snapshots (what order, latest first, newest first...)?
* how to cope these cases where defined requierements (e.g. keep 5GB free)
cannot be met
* it's not possible to retrieve free disk space on some targets (ftp)
** Descr
Since development of nssbackup and sbackup has merged this won't fix in
nssbackup. Please take a look at sbackup's project site at
https://launchpad.net/sbackup
** Changed in: nssbackup/0.3
Status: In Progress => Won't Fix
** Changed in: nssbackup/devel
Status: Confirmed => Won't Fi
Question #138633 on Simple Backup changed:
https://answers.launchpad.net/sbackup/+question/138633
Jean-Peer Lorenz proposed the following answer:
Snapshots get only purged (logarithmic plan or simple cut-off) in the
case they are _standalone_ (i.e. other snapshots do not depend on them).
Purpose i
Question #138633 on Simple Backup changed:
https://answers.launchpad.net/sbackup/+question/138633
Related FAQ set to:
How does the purge feature work?
https://answers.launchpad.net/sbackup/+faq/1428
Jean-Peer Lorenz proposed the following answer:
Jean-Peer Lorenz suggests this article
I've just received following email from the center of excellence in free
software Castilla La Mancha (Spain):
I contact from the center of excellence in free software Castilla La
Mancha (Spain) to inform you that SBackup has been analyzed by our
technicians and obtained a seal of quality (in parti
On 03/01/11 15:18, Jean-Peer Lorenz wrote:
>> This option is included in version 0.10.5
> I don't think that the general option to purge (as currently included in
> sbackup) meets the described feature request. Therefore, I reopen this bug.
> Remarks and patches are welcome.
Ideally, to free up
Question #138633 on Simple Backup changed:
https://answers.launchpad.net/sbackup/+question/138633
Status: Answered => Solved
max confirmed that the question is solved:
Dear Jean-Peer,
Many thanks for your answer and creating the FAQ, that's excellent, it
all makes sense now.
Thanks again :-
Hi Jean-Peer,
Thanks for your taking care of this report.
I was aware of the 580952 bug you indicated and I have now reported that
if affects me also.
* Is the bug reproducible; does it happen every time?
The bug I reported happens every time,
however back in mid December, the 19th exactly, sba
also i did try using SFTP instead of SSH and got the same errors:
2011-01-03 14:57:55,105 - WARNING: Unable to query available space on target:
Operation not supported
2011-01-03 14:57:55,368 - INFO: Snapshot is being committed
2011-01-03 14:57:58,164 - ERROR: An error occurred during the backup:
Well i DID answer most of this in my initial report.
* Is the bug reproducible; does it happen every time?
yes, i tried several times and got the same errors.
* is your backup destination on a local drive or remote?
It's a remote drive, accessed thru ssh
* do you run sbackup as superuser (root)
15 matches
Mail list logo
