Tyler J. Wagner wrote at about 11:58:00 +0100 on Friday, September 9, 2011:
 > On 2011-09-05 17:38, Jeffrey J. Kosowsky wrote:
 > > You probably want to read the documentation under --help (and also
 > > perhaps at the head of the executable). But you probably want to use
 > > the --fixlinks|-f option which will create links between any pc file
 > > that is not linked to the pool to either the appropriate existing pool
 > > element (if it's there but not linked) or it will create a new
 > > properly named pool element linked to the pc file if the pool element
 > > doesn't already exist.
 > 
 > Thanks for your help, Jeffrey. I think the problem is that the ipool wasn't
 > fully created on a previous run. I assumed that the ipool would be updated,
 > but it isn't. Does it have to be completely recreated with every run if the
 > pool has changed since the last run?

Yes - there is no other way to know since BackupPC_nightly can
renumber chains and since pool files can be added/deleted in between
which can reuse old inode numbers.

I modified the run-time warning to be more explicit that you need to
recreate the Ipool if the pool has changed. Also, I added a note to
this effect in the --help documentation.

 > 
 > Also, running the latest version produces this output:
 > 
 > Argument "0.4.0" isn't numeric in subroutine entry at
 > /usr/local/bin/BackupPC_copyPcPool.pl line 139.
 > 
 > This is on backuppc 3.2.0-3ubuntu4~maverick1 and also backuppc
 > 3.2.0-3ubuntu4~lucid1, with jLib 0.4.0.
 > 

Interesting, you must have a version of Perl that is more dogmatic
about how v-strings are specified. But I'm not sure why are first
encountering the problem now since the versioning code didn't change
from the previous version. I did make a change to specify it
explicitly as a v-string so hopefully that will help.

I will send you the code in a separate email.
I would appreciate it if you could test it out on your system to see
if the versioning now works...

------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT 
space for its ease of implementation, lower cost, and increased 
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/