cedar-backup-users Mailing List for Cedar Backup
Brought to you by:
pronovic
Menu
▾
▴
cedar-backup-users — User-support mailing list
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(1) |
Mar
(15) |
Apr
(7) |
May
(4) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(2) |
| 2009 |
Jan
|
Feb
(3) |
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Kenneth P. <pro...@ie...> - 2015-07-26 08:37:48
|
Hi, Effective immediately, development of Cedar Backup has moved from SourceForge to BitBucket [1]. Although I have been considering this change for a while, the recent problems with SourceForge [2][3] have encouraged me to migrate now rather than waiting any longer. I moved all of my other software to BitBucket earlier this year when the shutdown of Google Code was announced, and it makes sense to have everything in one place and using one revision control system. The existing Subversion repository and file releases will stay at SourceForge indefinitely, but new file releases will happen at BitBucket. The entire Subversion history has been imported into the new Mercurial repository at BitBucket. As of this writing, there are 7 subscribers to this mailing list. Since 2009, there has been no traffic to the list other than my release announcements. BitBucket does not offer a mailing list or other collaboration mechanism, so I'm left either maintaining this list at SourceForge, or abandoning the list altogether. After some thought, I've decided to abandon the list unless someone speaks up to tell me that it's still useful to them (a private off-list message is fine). In other news, I released v2.24.3 a little while ago. There were no functional changes, just documentation updates to reflect the new BitBucket location. Debian packages will follow as usual. I am also beginning work on a conversion to Python 3. Cedar Backup v2.x will be supported for Python 2 only, while the new Cedar Backup v3.x will be supported for Python 3 only. The initial v3.0.0 release will be functionally equivalent to v2.24.3. I'll support both versions for a while, and eventually transition all new development to Cedar Backup v3.x once we get closer to the 2020 deadline, after which Python 2 will no longer be supported. I've been glad to have you all as users for the last 10 years. KEN [1] https://bitbucket.org/cedarsolutions [2] http://tech.slashdot.org/story/15/06/01/1241231/sourceforge-and-gimp-updated [3] http://sourceforge.net/blog/sourceforge-infrastructure-and-service-restoration/ -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2015-01-06 01:59:35
|
Cedar Backup v2.24.2 has been released. This release adds some configuration to the amazons3 extension. You can now configure the extension with a backup size limit. The backup will fail if the limit is exceeded. This helps minimize the chance that an unexpectedly-large backup will eat up a lot of bandwidth, S3 storage, or Amazon I/O (all of which could be expensive under some circumstances). You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.24.2.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/jessie/binary-i386/admin/cedar-backup2/cedar-backup2_2.24.2-1_all.deb http://cedar-solutions.com/ftp/debian/dists/jessie/binary-amd64/admin/cedar-backup2/cedar-backup2_2.24.2-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-i386/admin/cedar-backup2/cedar-backup2_2.24.2-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-amd64/admin/cedar-backup2/cedar-backup2_2.24.2-1_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2014-10-08 02:37:31
|
Cedar Backup v2.24.1 has been released. This release adds a new tool cback-amazons3-sync, used for synchronizing entire directories of files up to an Amazon S3 cloud storage bucket, outside of the normal Cedar Backup process. This can be useful for directories that change regularly, but for which the normal date-versioned (and encrypted) backup process isn't necessary. For instance, I'm using it to backup my Gallery v1 photo albums. A lifecyle rule immediately archives the photos into the lower-cost Glacier storage tier. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.24.1.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/jessie/binary-i386/admin/cedar-backup2/cedar-backup2_2.24.1-1_all.deb http://cedar-solutions.com/ftp/debian/dists/jessie/binary-amd64/admin/cedar-backup2/cedar-backup2_2.24.1-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-i386/admin/cedar-backup2/cedar-backup2_2.24.1-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-amd64/admin/cedar-backup2/cedar-backup2_2.24.1-1_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2014-10-03 19:20:17
|
Cedar Backup v2.23.3 has been released. This release adds the ability to store backup data to Amazon S3 cloud storage rather than physical media. The new functionality is implemented in the "amazons3" extension using the AWS CLI tooling. I have been using this functionality for a few days, and I believe it to be stable, but I would welcome feedback from any users who find it useful. Be sure to read the user manual for notes on how to install and configure AWS CLI. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.23.3.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/jessie/binary-i386/admin/cedar-backup2/cedar-backup2_2.23.3-1_all.deb http://cedar-solutions.com/ftp/debian/dists/jessie/binary-amd64/admin/cedar-backup2/cedar-backup2_2.23.3-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-i386/admin/cedar-backup2/cedar-backup2_2.23.3-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-amd64/admin/cedar-backup2/cedar-backup2_2.23.3-1_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2013-05-10 02:36:00
|
Cedar Backup v2.20.0 has been released. This release adds workarounds (kludges) for new eject behavior discovered in Debian 'wheezy' and kernel 3.2.0. There is a new config option eject_delay that adds an optional delay after opening the tray but before closing it. There's also new error-handling behavior to work around the way the tray is sometimes locked after writing media. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.22.0.tar.gz Debian packages are not yet complete, because I haven't had time to create a chroot build environment for 'jessie' yet. I'll hopefully get the packages built later this weekend. Once that task is complete, you can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/jessie/binary-i386/admin/cedar-backup2/cedar-backup2_2.22.0-1_all.deb http://cedar-solutions.com/ftp/debian/dists/jessie/binary-amd64/admin/cedar-backup2/cedar-backup2_2.22.0-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-i386/admin/cedar-backup2/cedar-backup2_2.22.0-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-amd64/admin/cedar-backup2/cedar-backup2_2.22.0-1_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2013-05-08 05:17:12
|
I've recently updated my home systems to Debian wheezy. So far, I've experienced a variety of problems with Cedar Backup when running under this new Debian version: open/close of drive tray often doesn't work as expected, and in a lot of cases growisofs can't successfully write an image to the disc. In some cases, Cedar Backup also has problems noticing that a disc is already initialized, possibly due to the time it takes for media to stabilize. Many of these problems appear to be tied to the new 3.2.0 kernel. I was able to get my backups to complete by falling back to my old kernel (2.6.32), although I did also have to change the refresh media delay in cback.conf. My main backup hardware is fairly old (motherboard circa 2001, with a somewhat newer LiteOn DVD writer), and that may also be contributing to the behavior. I've never before had problems like this when upgrading Debian or moving to a newer kernel, so I'm a little mystified. If any other Cedar Backup users are experiencing similar problems after upgrading to wheezy, I would appreciate hearing about it. I'd like to make sure I address whatever problems you're seeing. If I hear about other problems, that may make it easier to figure out what's going on. Thanks, KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2013-03-21 15:23:06
|
Cedar Backup v2.21.1 has been released. This release incorporates a few minor patches provided by Jan Medlock. There was a typo in the manpage, and the latest /usr/bin/split changed its output and broke the split extension. Jan's patches fix both problems. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.21.1.tar.gz<http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.21.0.tar.gz> You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-i386/admin/cedar-backup2/cedar-backup2_2.21.1-1_all.deb http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-amd64/admin/cedar-backup2/cedar-backup2_2.21.1-1_all.deb http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.21.1-1+squeeze_all.deb http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-amd64/admin/cedar-backup2/cedar-backup2_2.21.1-1+squeeze_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. Unfortunately, due to the state of the Debian freeze, version 2.21.1-1 will not make it into the Wheezy release. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2011-10-12 18:00:24
|
Cedar Backup v2.21.0 has been released. This release adds support for recursion in the collect action. By setting a non-zero recursion level in collect configuration, Cedar Backup will generate archive files at a more granular level. For instance, at recursion level 0 (the default), collecting /home will result in a single archive file home.tar.gz. At recursion level 1, collecting /home will result in one archive file for each actual home directory (i.e. home-user1.tar.gz, home-user2.tar.gz, etc.). This feature was contributed by Zoran Bosnjak, who also helped test it. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.21.0.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/wheezy/binary-i386/admin/cedar-backup2/cedar-backup2_2.21.0-1_all.deb http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.21.0-1+squeeze_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2010-11-06 18:56:15
|
Yes, you can set the no_eject option in store configuration. See: http://cedar-backup.sourceforge.net/docs/cedar-backup2/manual/ch05s02.html#cedar-config-configfile-store Keep in mind that this could cause problems. Cedar Backup ejects the disc after writing it because this step forces the drive to recognize the newly-added data. Without this step, a lot of drives don't see the new data and the consistency check fails. So, you'll just have to test it and see what happens. If it works, great. If not, the only alternative is usually to install a different drive. KEN 2010/11/6 Mário Costa <atr...@gm...> > Hello, > > I have a dvd drive that is simillar to those of a laptop, and it does not > close. > Is there any way to disable eject? would cedar be able to work > properly with eject disabled ? > > Thanks, > Mario > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > cedar-backup-users mailing list > ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedar-backup-users > > -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Mário C. <atr...@gm...> - 2010-11-06 17:08:25
|
Hello, I have a dvd drive that is simillar to those of a laptop, and it does not close. Is there any way to disable eject? would cedar be able to work properly with eject disabled ? Thanks, Mario |
|
From: Kenneth P. <pro...@ie...> - 2010-10-20 02:32:58
|
Cedar Backup v2.20.1 has been released. The main focus of this release was to support Python 2.7. I closed SF bug #3079930 and also fixed some other minor issues exposed by differences in Python 2.7. See the changelog for details. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.20.1.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/lenny/binary-i386/admin/cedar-backup2/cedar-backup2_2.20.1-1_all.deb http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.20.1-1_all.deb Users of the Debian unstable distribution can also install the latest Debian package from their favorite Debian mirror. I do not actively use Python 2.7 yet, because it's only available in Debian's experimental distribution and my development machine runs Debian stable. So, although I have done some limited testing, I won't necessarily notice if there are oddities specific to Python 2.7. Please write the list or file a bug if you notice any problems. KEN |
|
From: Kenneth P. <pro...@ie...> - 2010-07-07 23:39:43
|
Cedar Backup v2.20.0 has been released. This is a cleanup release. I took care of some organizational TODO items, fixed a variety of minor problems exposed by pylint, and changed the minimum interpreter version from Python 2.3 to Python 2.5. A lot of code was touched, but there were no functional enhancements or bug fixes. The move to Python 2.5 allowed me to simplify some utility code and will hopefully make Cedar Backup easier to maintain in the future. Since Python 2.5 was released almost 4 years ago and exists even in the current stable release of Debian, my expectation is that this will not cause problems for very many users (if any). If this is *not* the case and you still need to run Cedar Backup using a pre-2.5 interpreter, please let me know. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.20.0.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from one of these URLs: http://cedar-solutions.com/ftp/debian/dists/lenny/binary-i386/admin/cedar-backup2/cedar-backup2_2.20.0-1_all.deb http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.20.0-1_all.deb Users of the Debian 'unstable' distribution can also install the latest Debian package from their favorite Debian mirror. Please write the list or file a bug in the SourceForge issue tracker if you notice any problems with this release. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2010-05-22 17:45:42
|
Cedar Backup v2.19.6 has been released. This release adds a new store configuration option <refresh_media_delay>, which adds an optional delay after writing the backup to disc, but before running the consistency check. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.19.6.tar.gz<http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.19.4.tar.gz> You can get the latest Debian package from the Cedar Solutions APT source, or from this URL: http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.19.6-1_all.deb<http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.19.4-1_all.deb> Users of the Debian 'unstable' distribution can also install the latest Debian package from their favorite Debian mirror. Please write the list or file a bug in the SourceForge issue tracker if you notice any problems with this release. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2010-05-21 00:49:38
|
Hi Murray, I don't have enough information to diagnose the first set of problems writing to disc. Try re-running with: --stack --verbose --debug Hopefully, that will give us some more useful information. The "currently mounted" error just means that the media in the drive has been mounted as a filesystem. It would show up in a 'df -k' listing. This might be because you mounted the disc manually in order to read its contents. It's also possible that something (i.e. KDE, Gnome) is choosing to auto-mount any disc that has a filesystem on it. Another possibility is that Cedar Backup is leaving the disc mounted after running the consistency check, but I've never seen that happen. KEN On Thu, May 20, 2010 at 6:52 PM, Murray Collingwood < mu...@fo...> wrote: > Hi guys > > Just a few issues writing to the DVD drive (this is a Liteon dvd writer). > > tawa:/home/murray# cback all > Error executing backup: Error (150) executing command to write disc. > tawa:/home/murray# cback store > Error executing backup: Error (252) executing command to write disc. > tawa:/home/murray# cback store > Error executing backup: Error (150) executing command to write disc. > tawa:/home/murray# cback store > Error executing backup: Error (150) executing command to write disc. > tawa:/home/murray# cback --full store > Error executing backup: Error [32] mounting [/dev/dvd2] at > [/var/cedar/tmp/tmpAu59Ev] as [iso9660]. > tawa:/home/murray# > > Also I get this sometimes: > tawa:/etc# cback --full all > Error executing backup: Device [/dev/dvd2] is currently mounted. > > > Can anybody explain why these might be happening and what I should do to > fix them? > > From my conf file: > <store> > <source_dir>/var/cedar/stage</source_dir> > <media_type>dvd+rw</media_type> > <device_type>dvdwriter</device_type> > <target_device>/dev/dvd2</target_device> > <check_data>Y</check_data> > <check_media>N</check_media> > </store> > > > Cheers > mc > > -- > Murray Collingwood > Focus Computing > p +61 415 24 26 24 > http://www.focus-computing.com.au > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > cedar-backup-users mailing list > ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedar-backup-users > > -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Murray C. <mu...@fo...> - 2010-05-20 23:52:25
|
Hi guys
Just a few issues writing to the DVD drive (this is a Liteon dvd writer).
tawa:/home/murray# cback all
Error executing backup: Error (150) executing command to write disc.
tawa:/home/murray# cback store
Error executing backup: Error (252) executing command to write disc.
tawa:/home/murray# cback store
Error executing backup: Error (150) executing command to write disc.
tawa:/home/murray# cback store
Error executing backup: Error (150) executing command to write disc.
tawa:/home/murray# cback --full store
Error executing backup: Error [32] mounting [/dev/dvd2] at
[/var/cedar/tmp/tmpAu59Ev] as [iso9660].
tawa:/home/murray#
Also I get this sometimes:
tawa:/etc# cback --full all
Error executing backup: Device [/dev/dvd2] is currently mounted.
Can anybody explain why these might be happening and what I should do to fix
them?
>From my conf file:
<store>
<source_dir>/var/cedar/stage</source_dir>
<media_type>dvd+rw</media_type>
<device_type>dvdwriter</device_type>
<target_device>/dev/dvd2</target_device>
<check_data>Y</check_data>
<check_media>N</check_media>
</store>
Cheers
mc
--
Murray Collingwood
Focus Computing
p +61 415 24 26 24
http://www.focus-computing.com.au
|
|
From: Kenneth P. <pro...@ie...> - 2010-04-19 14:11:58
|
Hi Murray, I didn't see an error message in your other email, just the configuration file...? Cedar Backup only supports the dvd+rw format. I developed the DVD functionality with a Lite-On drive, so I don't think you'll have too many problems if you get the right kind of media. KEN On Mon, Apr 19, 2010 at 12:41 AM, Murray Collingwood < ce...@fo...> wrote: > Hi guys > > Just checking some more stuff, I checked my DVD disc and it's dvd-rw rather > than dvd+rw. The unit (Lite-on) I believe can read and write both formats. > I assume from comments in the manual that this is incompatible so I may need > to buy some dvd+rw discs. No major problem, but before I do it would be > nice to know if that was the cause of the problem. > > Cheers > mc > > -- > Murray Collingwood > Focus Computing > p +61 415 24 26 24 > http://www.focus-computing.com.au > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > cedar-backup-users mailing list > ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedar-backup-users > > -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Murray C. <ce...@fo...> - 2010-04-19 05:42:04
|
Hi guys Just checking some more stuff, I checked my DVD disc and it's dvd-rw rather than dvd+rw. The unit (Lite-on) I believe can read and write both formats. I assume from comments in the manual that this is incompatible so I may need to buy some dvd+rw discs. No major problem, but before I do it would be nice to know if that was the cause of the problem. Cheers mc -- Murray Collingwood Focus Computing p +61 415 24 26 24 http://www.focus-computing.com.au |
|
From: Murray C. <ce...@fo...> - 2010-04-19 04:55:23
|
Hello
>
> I went through a long hunt and arrived at 'Cedar Backup2' - I installed the
system from default Debian install and got this error. So I updated the apt
sources to Cedar Solutions, upgraded to 2.19.5-1 and I still get the same
error.
Have I specified the wrong device???
I'm on Debian 5.0.4 (lenny)
Below is my cback.conf file:
<?xml version="1.0"?>
<cb_config>
<reference>
<author>Kenneth J. Pronovici</author>
<revision>1.3</revision>
<description>Sample</description>
</reference>
<extensions>
<action>
<name>sysinfo</name>
<module>CedarBackup2.extend.sysinfo</module>
<function>executeAction</function>
<index>95</index>
</action>
<action>
<name>mysql</name>
<module>CedarBackup2.extend.mysql</module>
<function>executeAction</function>
<index>96</index>
</action>
</extensions>
<options>
<starting_day>monday</starting_day>
<working_dir>/var/cedar/tmp</working_dir>
<backup_user>backup</backup_user>
<backup_group>backup</backup_group>
<rcp_command>/usr/bin/scp -B</rcp_command>
<override>
<command>cdrecord</command>
<abs_path>/usr/bin/cdrecord</abs_path>
</override>
<override>
<command>mkisofs</command>
<abs_path>/usr/bin/mkisofs</abs_path>
</override>
<pre_action_hook>
<action>collect</action>
<command>mount -t cifs //ponga/dev -o
ro,username=murray,password=***** /pdev</command>
</pre_action_hook>
<post_action_hook>
<action>collect</action>
<command>umount /pdev</command>
</post_action_hook>
</options>
<collect>
<collect_dir>/var/cedar/collect</collect_dir>
<collect_mode>daily</collect_mode>
<archive_mode>targz</archive_mode>
<ignore_file>.cbignore</ignore_file>
<exclude>
<pattern>.*\.zip</pattern>
</exclude>
<dir>
<abs_path>/pdev</abs_path>
</dir>
</collect>
<stage>
<staging_dir>/var/cedar/stage</staging_dir>
<peer>
<name>tawa</name>
<type>local</type>
<collect_dir>/var/cedar/collect</collect_dir>
</peer>
</stage>
<store>
<source_dir>/var/cedar/stage</source_dir>
<media_type>dvd+rw</media_type>
<device_type>dvdwriter</device_type>
<target_device>/dev/dvdrw1</target_device>
<check_data>Y</check_data>
<check_media>N</check_media>
</store>
<purge>
<dir>
<abs_path>/var/cedar/stage</abs_path>
<retain_days>7</retain_days>
</dir>
<dir>
<abs_path>/var/cedar/collect</abs_path>
<retain_days>0</retain_days>
</dir>
</purge>
</cb_config>
Cheers
Murray
--
Murray Collingwood
Focus Computing
p +61 415 24 26 24
http://www.focus-computing.com.au
|
|
From: Kenneth P. <pro...@ie...> - 2010-01-11 01:27:14
|
Cedar Backup v2.19.5 has been released. This release fixes several minor bugs in cback-span and adds some basic support for platform customization. Building on the new customization support, the Debian package now uses wodim and genisoimage rather than cdrecord and mkisofs. This brings the Debian package back into compliance with Policy. The change should be transparent to users, since cdrecord and mkisofs are currently just soft links to wodim and genisofs anyway. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.19.5.tar.gz<http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.19.4.tar.gz> <http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.19.4.tar.gz> You can get the latest Debian package from the Cedar Solutions APT source, or from this URL: http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.19.5-1_all.deb<http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.19.4-1_all.deb> Users of the Debian 'unstable' distribution can also install the latest Debian package from their favorite Debian mirror. Please write the list or file a bug in the SourceForge issue tracker if you notice any problems with this release. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2009-10-13 03:51:39
|
I've written a script called gmailcontacts to back up gmail contacts into Google's own contacts CSV format. This is the same format that you can use to import contacts into a gmail account, so it makes a reasonably good backup. The backup will contain all of your "trusted" gmail contacts -- the ones that show up under "My Contacts" in the gmail user interface. Everything important is archived (email addreses, phone numbers, etc.), but only gdata "version 2" fields are supported. This means that certain newer gmail contacts fields like websites and relationships do not get backed up. The script is written in Python (requires 2.5 or better), and uses Google's gdata <http://code.google.com/p/gdata-python-client> Python library for connectivity (http://code.google.com/p/gdata-python-client). I haven't made this an official Cedar Backup extension, but it's very easy to integrate it into Cedar Backup using a pre- or post-action hook. Here's the hook that I'm currently using: <!-- This backs up Gmail contacts into a Google CSV file. --> <post_action_hook> <action>collect</action> <command>/opt/local/bin/gmailcontacts --output=/opt/backup/collect/gmailcontacts-pronovic.csv</command> </post_action_hook> Find the gmailcontacts script on my utilities page: http://cedar-solutions.com/software/utilities.html Feel free to write the list if you have any questions. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2009-08-16 21:02:42
|
Cedar Backup v2.19.4 has been released. This release adds support for the Python 2.6 interpreter, by fixing some deprecation warnings and changing the expected conditions for one test case. This should make it easier for Ubuntu users to run the latest release. You can get the latest Python source package from this URL: http://downloads.sourceforge.net/cedar-backup/CedarBackup2-2.19.4.tar.gz You can get the latest Debian package from the Cedar Solutions APT source, or from this URL: http://cedar-solutions.com/ftp/debian/dists/squeeze/binary-i386/admin/cedar-backup2/cedar-backup2_2.19.4-1_all.deb Users of the Debian 'unstable' distribution can also install the latest Debian package from their favorite Debian mirror. Please write the list or file a bug in the SourceForge issue tracker if you notice any problems with this release. KEN -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2009-05-11 15:14:22
|
This has now been filed (by 'kmos') as SF bug #2788118: https://sourceforge .net/tracker/?func=detail&atid=1013862&aid=2788118&group_id=210468 KEN |
|
From: Kenneth P. <pro...@ie...> - 2009-05-04 21:08:08
|
It should be safe to install multiple pythons alongside one another. You're not rolling back, because the default system interpreter will remain at 2.6. Basically, the existing /usr/bin/python will continue to point at /usr/bin/python2.6, but the new /usr/bin/python2.5 will also be available if you want to use it. (My Debian lenny box has both 2.4 and 2.5 installed, using the same mechanism.) KEN On Mon, May 4, 2009 at 3:47 PM, Scott Evans <sc...@vk...>wrote: > > No doubt that there has been internal changes with Python 2.6 but I too am > not too concerned about the depreciation warnings! > > As for rolling back to Pyton 2.5 this will possibly break Jaunty! as some > applications rely on that newer release! (I don't want that!) > > For one backup I also discovered that I had a faulty DVD/RW that just also > added some confusion as to what was at fault! (time to get some new media!) > > > -----Original Message----- > *From*: Kenneth Pronovici <pro...@ie...<Kenneth%20Pronovici%20%3cp...@ie...%3e> > > > *To*: cedar-backup-users <ced...@li...<cedar-backup-users%20%3cc...@li...%3e> > > > *Subject*: Re: [cedar-backup-users] Resultc from python util/test.py > (Ubutnu Jaunty 9.04) > *Date*: Mon, 4 May 2009 14:27:47 -0500 > > Just to follow up briefly: Python 2.6 is currently only available in > Debian's experimental distribution. I could install it from source, but I > would prefer not to. So, I will address these test failures at some point > in the future when I can more easily install the new interpreter. > > In the meantime, if you are concerned, you could install Ubuntu's python2.5 > package, and then change the cback script to use this: > > #!/usr/bin/python2.5 > > I wouldn't worry about it, though. > > KEN > > On Mon, May 4, 2009 at 7:56 AM, Kenneth Pronovici <pro...@ie...> > wrote: > > Hi Scott, > > Thanks for the report. > > I haven't tested with Python 2.6 previously, and it looks like that > explains most of the DeprecationWarning items you see. Deprecations > should be harmless (for now) so these are nothing to worry about. > > I'll take a look at testGenerateTarfile_002(); as you might surmise > from the comment, Python 2.5 behavior differs from 2.4 and 2.3, so > perhaps 2.6 changed again. I recall this being a test-only issue the > last time (something to do with how I detect the expected results), so > again I don't think it's anything to worry about. > > I'll reply again once I've had a chance to look at things in detail. > > KEN > > |
|
From: Kenneth P. <pro...@ie...> - 2009-05-04 19:27:53
|
Just to follow up briefly: Python 2.6 is currently only available in Debian's experimental distribution. I could install it from source, but I would prefer not to. So, I will address these test failures at some point in the future when I can more easily install the new interpreter. In the meantime, if you are concerned, you could install Ubuntu's python2.5 package, and then change the cback script to use this: #!/usr/bin/python2.5 I wouldn't worry about it, though. KEN On Mon, May 4, 2009 at 7:56 AM, Kenneth Pronovici <pro...@ie...> wrote: > Hi Scott, > > Thanks for the report. > > I haven't tested with Python 2.6 previously, and it looks like that > explains most of the DeprecationWarning items you see. Deprecations > should be harmless (for now) so these are nothing to worry about. > > I'll take a look at testGenerateTarfile_002(); as you might surmise > from the comment, Python 2.5 behavior differs from 2.4 and 2.3, so > perhaps 2.6 changed again. I recall this being a test-only issue the > last time (something to do with how I detect the expected results), so > again I don't think it's anything to worry about. > > I'll reply again once I've had a chance to look at things in detail. > > KEN > -- Kenneth J. Pronovici <pro...@ie...> http://www.cedar-solutions.com/ |
|
From: Kenneth P. <pro...@ie...> - 2009-05-04 12:56:24
|
Hi Scott, Thanks for the report. I haven't tested with Python 2.6 previously, and it looks like that explains most of the DeprecationWarning items you see. Deprecations should be harmless (for now) so these are nothing to worry about. I'll take a look at testGenerateTarfile_002(); as you might surmise from the comment, Python 2.5 behavior differs from 2.4 and 2.3, so perhaps 2.6 changed again. I recall this being a test-only issue the last time (something to do with how I detect the expected results), so again I don't think it's anything to worry about. I'll reply again once I've had a chance to look at things in detail. KEN |
4 messages has been excluded from this view by a project administrator.
