[Box Backup] Boxwin On Server 2003

Mike Bydalek boxbackup at fluffy.co.uk
Fri Jun 3 15:33:29 BST 2005

Quoting Nick Knight <nick at omniis.com>:

> There is no difference in the way it works on 2003 and XP - I have it
> working on both.

That's what I was thinking, so it's odd that I'm having problems.

> Instead of running it from a service as a test run it from the command
> line - this can give useful info
> bbackupd -c bbackupd.conf

This gives me:

C:\Program Files\Box Backup>bbackupd -c bbackupd.conf
No random device -- additional seeding of random number generator not 

Box Backup Client v0.09hWin32, (c) Ben Summers 2003, 2004
Starting daemon (config: bbackupd.conf) (version 0.09hWin32)
Requested store object info file 'C:\Program Files\Box 
dat' does not exist, not accessible, or inconsistent: no harm done, 
will re-cach
e from store
Parameter = 4593244.Connection from command socket
Connection from command socket  <-- Starting here is when I initiated the sync
Beginning scan of local files
Opening connection to server compunetconsulting.com...
Send Version(0x1)
Receive Version(0x1)
Send Login(0x1001,0x0)
Receive LoginConfirmed(0x3f89729319f40,0x5,0x80000,0x96000)
Connection made, login successful
Send ListDirectory(0x1,0x2,0xc,false)
Receive Success(0x1)
Receiving stream, size 232
2 redundant locations in root directory found, will delete from store 
after 1728
00 seconds.
Unused location in root: Shares
Unused location in root: Home
Send SetClientStoreMarker(0x3f8a4270388c0)
Receive Success(0x3f8a4270388c0)
Send Finished()
Receive Finished()
Exception caught (1/9), reset state and waiting to retry...

There really isn't much there except for my original error.  But what is
interesting is that the .dat file never gets created.  I've checked all paths
and everything looks good.

Per Ben's request, below is the config file that I am using (which is exactly
idential to my XP one, minus the account number).

Also, I'm using Boxwin 0.09h - which seems to be the latest.


StoreHostname = compunetconsulting.com
AccountNumber = 0x1001
KeysFile = C:\Program Files\Box Backup\1001-FileEncKeys.raw

CertificateFile = C:\Program Files\Box Backup\1001-cert.pem
PrivateKeyFile = C:\Program Files\Box Backup\1001-key.pem
TrustedCAsFile = C:\Program Files\Box Backup\serverCA.pem

DataDirectory = C:\Program Files\Box Backup\bbackupd

# If you do not install it in the default location - also do not forget to
# change the pid file location (below)

# This script is run whenever bbackupd encounters a problem which requires
# the system administrator to assist:
# 1) The store is full, and no more data can be uploaded.
# 2) Some files or directories were not readable.
# The default script emails the system administrator.

# NotifyScript = NotifySysadmin.sh

# This configuration file is written for snapshot mode.
# You will need to run bbackupctl to instruct the daemon to upload files.

AutomaticBackup = no
UpdateStoreInterval = 0
MinimumFileAge = 0
MaxUploadWait = 0

# Files above this size (in bytes) are tracked, and if they are renamed they
will simply be
# renamed on the server, rather than being uploaded again. (64k - 1)

FileTrackingSizeThreshold = 65535

# The daemon does "changes only" uploads for files above this size (in bytes).
# Files less than it are uploaded whole without this extra processing.

DiffingUploadSizeThreshold = 8192

# The limit on how much time is spent diffing files. Most files shouldn't take
very long,
# but if you have really big files you can use this to limit the time spent
diffing them.
# * Reduce if you are having problems with processor usage.
# * Increase if you have large files, and think the upload of changes is too
large and want
#   to spend more time searching for unchanged blocks.

MaximumDiffingTime = 20
KeepAliveTime = 250

# Uncomment this line to see exactly what the daemon is going when it's
connected to the server.

ExtendedLogging = yes

# Where the command socket is created in the filesystem.

# CommandSocket = bbackupd/bbackupd.sock

	PidFile = C:\Program Files\Box Backup\bbackupd\bbackupd.pid

StoreObjectInfoFile = C:\Program Files\Box Backup\bbackupd\bbackupd.dat

                Path = C:\test2\
                Path = C:\test1\

> -----Original Message-----
> From: boxbackup-admin at fluffy.co.uk [mailto:boxbackup-admin at fluffy.co.uk]
> On Behalf Of Ben Summers
> Sent: 03 June 2005 08:59
> To: boxbackup at fluffy.co.uk
> Subject: Re: [Box Backup] Boxwin On Server 2003
> On 2 Jun 2005, at 23:37, Mike Bydalek wrote:
>> Hello.
>> Let me start off by saying nice work on the Boxwin, and I hope this
>> is the
>> correct place to ask questions about it since I can't find for the
>> life of me a
>> mailing list for it, and have seen it mentioned here.
>> As for the reason of my post, I've been using Box Backup on my
>> Linux clients for
>> a good amount of time.  Recently, a client wanted a Windows server,
>> so I decided
>> to give Boxwin a try.
>> To test it, I used my local Windows XP machine and had absolutely
>> no problem
>> whatsoever with it (hence my cheers ;).  But, when I went to
>> implement it on
>> their server, Windows Server 2003, it didn't work properly.  All
>> that would
>> happen is that the top level locations would be created, nothing more.
>> In looking through the application log, when I do an initiate
>> backup, boxbackupd
>> throws this, which I've read means it can't access the file, or
>> file doesn't
>> exist, etc.:
>> Exception caught (1/9), reset state and waiting to retry....
>> The next event in the application log is that the backup finished
>> transferring 0
>> files and 0 bytes (duh).
>> Well, I then decided to have the service run as the Administrator,
>> and then
>> added an "everyone" to the directories and gave full perms (I'm
>> doing 2 simple
>> test directories for now).  After granting the world access to my test
>> directories, I still received that error and am now stuck.
>> Is there something special in 2003 that needs to be done that
>> doesn't need to be
>> done in XP?
> From the information you've given, it sounds more likely that there
> is something wrong with your configuration. First, check that all the
> files and directories mentioned in it actually exist, and once you're
> sure it's correct, post the config file here for comments.
> Ben
> _______________________________________________
> boxbackup mailing list
> boxbackup at fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
> _______________________________________________
> boxbackup mailing list
> boxbackup at fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup

More information about the Boxbackup mailing list