[Box Backup-dev] Testing Boxi 0.1.1

[E.W. Peter Jalajas]

Hi Chris,

I put some replies in the sourceforge bug tracker:
http://sourceforge.net/tracker/?group_id=135105&atid=731482

and some notes below.

Thanks,
Pete

--- Chris Wilson <chris@qwirx.com> wrote:

> Hi Pete,
> 
<snip>
> Nope. The red X means that you excluded the directory explicitly.
> There 
> should have been a yellow tick on "boxitext.txt" within that
> directory 
> though, which means that the exclude was overridden.

OK, thanks, a couple of confusions on my part.  The red X at the parent
directory made me think that _nothing_ below it was going to be backed
up.  (The higher-level parents in Backup Files, Basic, that is, My
Computer, Local Disk C:, and Program Files, had green checks, so my
confusion is reasonably warranted, no?)  

Also, I had just the filename boxitest.txt in the AlwaysIncludeFile
setting; it MUST be the full path C:\P F\Box Backup\boxitest.txt.  When
you select that single file via boxi's nav system, it populates that
full path correctly, you get the yellow + in Backup Files, Basic dir
tree, and the backup works fine.  Using AlwaysIncludeFilesRegex =
.+boxitest.txt$ seemed to work fine, too, as it should. 
AlwaysIncludeFilesRegex = boxitest.txt also seems to work fine, too,
somewhat surprisingly (I heretofore thought the leading .+ construct
was required; that .+ construct is probably better though in that it
is, or can be made to be, more precise, depending upon your intent and
risk averse-ness). 

> > The Backup Progress panel, Statistics, Files, Elapsed "24" seemed 
> > correct; Bytes said "51 (null)" -- not sure what that means.
> 
> 51 (null) is a bug, it should have shown something like 51 bytes or
> 51 kB. 
> I thought I had fixed that already. Is the file 51 bytes long?

The backup of the new boxitest.txt showed "42 (null)" and that new file
did have 42 bytes (per right-click, Properties).   I then modified that
file, and it backed up correctly, 1 file, 52 (null)...

BUG?:  Continuing to hit Start Backup on the Backup panel showed the
same result, eventhough, I think, that file should not be being backed
up because it hasn't changed.  To rephrase, nowhere does it say how
many files (and bytes) were actually backed up during a "Start Backup"
run.  
 
> > BUG:  That newly created C:\PF\Box Backup\test\ directory never
> appeared 
> > in the Backup Files or Restore Files panels after further Backup
> runs, 
> > until I restarted Boxi, then they showed up fine.
> 
> Did you try closing and opening the node above (C:\PF\Box Backup)?
> That 
> should re-read the directory listing. Newly added files do not show
> up on 
> their own, I'm not sure how to make that happen on Windows.

OK, thanks, double clicking the -/+ sign in the dir tree under Backup
Files, Basic does re-read that local directory.  

BUG?:  New related issue, though:  I set it up to backup a few more
files, which appeared to backup correctly, but I couldn't see them
under Restore Files until restarting Boxi.  

<snip>

By the way, the Backup Files, "Exclusions" tab uses the "Exclu*" words
about 5 times as a bit of a misnomer, because it includes "Includes". 
I don't have a better name yet though, except "Exclusions/Inclusions"
("Exceptions" would cause confusion with the error states, I would
think.).  Maybe "Modifications"?  

Also, by the way, I wanted to say that, all the above minor things
notwithstanding, boxi is working quite nicely.  The worst "bug" is that
crashing bug I reported, but now that I use it more, I'm sure that I
had just gotten it and myself in a twisted odd-ball state, and as long
as I behave it is performing my first simple backup and restore tests
perfectly.  (I'm sure that "bug" will go away when the old "5 redundant
locations in root directory found" are deleted in 172800 seconds.)