[Nssbackup-team] [Bug 696183] Re: Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

2011-01-03 Thread BlueLight
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/696183

Title:
  Failed to set GID to `admin`: 'getgrnam(): name not found: admin'

___
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] [Bug 670671] Re: Tar teminated with errors

2011-01-03 Thread Fabio Marzocca
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.netwrote:

 @Fabio: Please have a look at this similar question:
 https://answers.launchpad.net/sbackup/+question/139746
 Maybe this helps you. Seems like TAR in Maverick is somehow broken.

 ** Changed in: sbackup
   Status: New = Incomplete

 --
 You received this bug notification because you are a direct subscriber
 of the bug.
 https://bugs.launchpad.net/bugs/670671

 Title:
  Tar teminated with errors


-- 
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

___
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 670671] Re: Tar teminated with errors

2011-01-03 Thread Fabio Marzocca
** 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

___
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 294019] Re: (whishlist) Purging to free certain space

2011-01-03 Thread Jean-Peer Lorenz
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 Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/294019

Title:
  Purge to specified free disk space or backup size

___
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 294019] Re: (whishlist) Purging to free certain space

2011-01-03 Thread Jean-Peer Lorenz
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)

** Description changed:

- Since keeping enough free backup media space is the main purpose of
- backup purging and maximum single backup size can usually be estimated
- by the user (or even automatically as a total size all the files to be
- backed) it would be nice to have an option to purge backups until
- specified free space or total size of all the files to be backed is
- achieved.
+ Main purpose of backup purging is to keep enough free backup media
+ space. The actual backup size can be estimated by the user (or even
+ determined automatically as a total size all the files to be backed).
+ 
+ Please add an option to purge backups until a specified free space or total 
size of existing backup archives is achieved.
+ Example:
+ * Purge - keep 5GB disk space free
+ * Purge - max. size of backups (cumulated) 50GB

** Summary changed:

- (whishlist) Purging to free certain space
+ Purge to specified free disk space or backup size

** Changed in: sbackup
   Status: Fix Committed = Opinion

-- 
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/294019

Title:
  Purge to specified free disk space or backup size

___
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

2011-01-03 Thread Jean-Peer Lorenz
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 Fix

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to nssbackup.
https://bugs.launchpad.net/bugs/587911

Title:
  Logarithmic purge disabled/does not work

___
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] [Question #138633]: How does the purge feature work?

2011-01-03 Thread Jean-Peer Lorenz
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 is to keep incremental and full snapshots consistent. Rebasing
of incremental snapshots as in former releases (nssbackup before 0.2.0,
sbackup before 0.11) is completely dropped since it is a severe risk to
the backuped data.

Version SBackup 0.11 introduced a slight modification of the logarithmic purge 
plan:
* keep all from yesterday
* keep one per day from last week
* keep one per week from last month
* keep one per month from last year
* keep one per quarter from 2nd last year
* keep one per year further into past

Read 'keep one' as 'keep at least one'.

Example: making a full backup every 30 days means purging of snapshots
will be possible not before 30 days after the first snapshot because
every snapshot in your archive relies on the other (except the latest
but this one is also kept because it's the latest ;-) until you create
another full snapshot.

-- 
You received this question notification because you are a member of
Simple Backup Maintainers, which is an answer contact for Simple Backup.

___
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] [Question #138633]: How does the purge feature work?

2011-01-03 Thread Jean-Peer Lorenz
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 as an answer to your question:
FAQ #1428: “How does the purge feature work?”.

-- 
You received this question notification because you are a member of
Simple Backup Maintainers, which is an answer contact for Simple Backup.

___
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] sbackup quality seal

2011-01-03 Thread Jean-Peer Lorenz
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 particular the highest
level), we are very pleased that the project has not been abandoned and
we would provide them with the seal and certificate achieved, I hope it
is of interest and can reply to this email, I include two links where
you can find more information (the sites are in Spanish but if you want
I can send the translations).
Greetings

http://ceslcam.com/

http://ticos.ceslcam.com/informacion/aplicaciones.html



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] [Bug 294019] Re: (whishlist) Purging to free certain space

2011-01-03 Thread Anton
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 necessary diskspace in combination with logarithmic 
purge, it would be good if the purge could be incrementally 'thinned'.
The default is:
* keep all from yesterday
* keep one per day from last week
* keep one per week from last month
* keep one per month from last year
* keep one per quarter from 2nd last year
* keep one per year further into past

(Especially the last one, while growing slowly, will keep growing
forever!)

But, when tight on diskspace, one could 'thin' this to something like:
* keep last one from yesterday
* keep one per two days from last week
* keep one per two weeks from last two months
* keep one per two months from last year
* keep one per half year from 2nd last year
* keep one per 2^n years for the nth year into past (true logarithmic!)

Alternate to steering on free space, one might want to set a limit on 
total diskspace allocated to backups. This might even work when disk 
free cannot be determined (as with ftp).


Anton.

-- 
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/294019

Title:
  Purge to specified free disk space or backup size

___
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] [Question #138633]: How does the purge feature work?

2011-01-03 Thread max
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 :-)

-- 
You received this question notification because you are a member of
Simple Backup Maintainers, which is an answer contact for Simple Backup.

___
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 682436] Re: sbackup crashes before starting the backup archive on CIFS mounted NAS

2011-01-03 Thread Marc BENVENISTE
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, sbackup succeeded a full backup 
launched by cron as every week. I can't remember what updates were made between 
that successful backup and the next, that failed on December 26th. I'm newby so 
if you can direct me, I could clear up what was updated during that week.

* do you run sbackup as superuser (root) or as regular user?
I guess it is as superuser since it is launched by cron on a weekly basis with 
the default profile

* are you able to open your backup destination using Nautilus/command line?
Yes, although there are lot of CIFS related messages in the logs and sometimes 
copying files fails to terminate to or from this NAS drive.

* Is this bug still valid?
Yep, it is. sbackup craches when attempting to write the tar file.

Thanks for your support and don't hesitate to contact me if you require
further information.

Sincerely,

--Marc

-- 
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/682436

Title:
  sbackup crashes before starting the backup archive on CIFS mounted NAS

___
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 675644] Re: Error in stream protocol: End of stream

2011-01-03 Thread scar
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: Error in 
stream protocol: End of stream
2011-01-03 14:57:59,210 - ERROR: Uncaught exception: The specified location is 
not mounted
2011-01-03 14:57:59,211 - ERROR: Traceback (most recent call last):
  File /usr/bin/sbackup, line 42, in module
retc = main(sys.argv)
  File /usr/share/sbackup/sbackup/backupproc.py, line 586, in main
exitcode = sbackup_app.run()
  File /usr/share/sbackup/sbackup/backupproc.py, line 566, in run
self.__exitcode = self.__backupproc.run()
  File /usr/share/sbackup/sbackup/backupproc.py, line 288, in run
self.__on_backup_error(error)
  File /usr/share/sbackup/sbackup/backupproc.py, line 311, in 
__on_backup_error
self.__exitcode = self.__bprofilehdl.finish(error)
  File /usr/share/sbackup/sbackup/core/profile_handler.py, line 315, in finish
self.__copylogfile()
  File /usr/share/sbackup/sbackup/core/profile_handler.py, line 286, in 
__copylogfile
_op.copyfile(logf_src, logf_target)
  File /usr/share/sbackup/sbackup/fs_backend/_gio_utils.py, line 472, in 
copyfile
_src, _dest = cls._prepare_copy(_src, _dest)
  File /usr/share/sbackup/sbackup/fs_backend/_gio_utils.py, line 500, in 
_prepare_copy
if cls.__isdir(dst_gfile):
  File /usr/share/sbackup/sbackup/fs_backend/_gio_utils.py, line 651, in 
__isdir
_ftype = cls._query_file_type(gfile)
  File /usr/share/sbackup/sbackup/fs_backend/_gio_utils.py, line 670, in 
_query_file_type
cancellable = None)

-- 
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/675644

Title:
  Error in stream protocol: End of stream

___
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