hi all,

here is the description of the "problem":

if my backuppc compresses the files in the pool and I archive an host
requiring that the archive is compressed, backuppc does the
decompression for extracting the data of the pool and then compress it
again for write it to the archive file.

and now the request:

it's possible to avoid this when the compress level of the cpool and the
compress level of the archive file is the same? something like: "I use
bzip in my cpool and the user requested an archive of that host in tar
+bzip format, so I do a simple tar cf on compressed files, and a tar czf
on uncompressed ones".

is it possibile?

thanks in advance

On Thu, 2009-03-26 at 18:23 -0500, Paul Mantz wrote:
> 2009/3/26 o...@jltechinc.com <o...@jltechinc.com>:
> > We are all currently using: Version *3.1.0* released on November 25th, 2007
> >
> > Any idea when we can expect the next release of BackupPC?
> >
> > -obj
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > BackupPC-users mailing list
> > BackupPC-users@lists.sourceforge.net
> > List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
> > Wiki:    http://backuppc.wiki.sourceforge.net
> > Project: http://backuppc.sourceforge.net/
> >
> 
> Hello Obj,
> 
> We are working on changes for a 3.2.0 release.  In fact, 3.2.0beta0
> was uploaded to the CVS repository on Wednesday.  You can expect a new
> version soon.
> 
> 
> Adios,
> 


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to