[Box Backup] Win32 Port - bbackupctl issue wit configuration file

[Nick Knight]

I haven't tested the backupctl much - and may have broken it! Let me
look into this and get back to you.

Regards

Nick

-----Original Message-----
From: boxbackup-admin@fluffy.co.uk [mailto:boxbackup-admin@fluffy.co.uk]
On Behalf Of Chris Hane
Sent: 06 November 2004 00:17
To: boxbackup@fluffy.co.uk
Subject: [Box Backup] Win32 Port - bbackupctl issue wit configuration
file


I am getting the following error when trying to test the Win32 client=20
(posted by Nick Knight) version 0.8f.

I have:
  - installed the server on a Linux box and have Linux clients backing
up to it
  - installed the client on Win32
  - can query the server with "bbackupquery -c bbackupd.conf"
  - can run the daemon "bbackupd -c bbackupd.conf"

When I run the client [bbackupctl -c bbackupd.conf] I get the following
error:
C:\Program Files\Box Backup>bbackupctl -c bbackupd.conf synch
Using configuration file
Exception: Common (1/2)

I'm probably doing something very simple wrong.  I just don't see what
is=20
wrong in the config file (or am I specifying the path incorrectly).  I
have=20
installed the win32 client in the default location of ("program
files\box=20
backup").  Also, I am running on Windows XP.

As a note, when I look in the PID directory below there is not a file
named=20
bbackupd.pid.  Could that be the issue?

Thanks in advance and I've included my config file below,
Chris....

[bbackupd.conf]
StoreHostname =3D bacchus.itsolut.com
AccountNumber =3D 0x75ab23c
KeysFile =3D C:\Program Files\Box Backup\75AB23C-FileEncKeys.raw

CertificateFile =3D C:\Program Files\Box Backup\75AB23C-cert.pem
PrivateKeyFile =3D C:\Program Files\Box Backup\75AB23C-key.pem
TrustedCAsFile =3D C:\Program Files\Box Backup\serverCA.pem

DataDirectory =3D 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 =3D NotifySysadmin.sh


# A scan of the local discs will be made once an hour (approximately).
# To avoid cycles of load on the server, this time is randomly adjusted
by=20
a small
# percentage as the daemon runs.

# UpdateStoreInterval =3D 3600
UpdateStoreInterval =3D 0
AutomaticBackup =3D no

# A file must have been modified at least 6 hours ago before it will be=20
uploaded.

#MinimumFileAge =3D 21600
MinimumFileAge =3D 0


# If a file is modified repeated, it won't be uploaded immediately in
case=20
it's modified again.
# However, it should be uploaded eventually. This is how long we should=20
wait after first noticing
# a change. (1 day)

#MaxUploadWait =3D 86400
MaxUploadWait =3D 0


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

FileTrackingSizeThreshold =3D 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 =3D 8192


# The limit on how much time is spent diffing files. Most files
shouldn't=20
take very long,
# but if you have really big files you can use this to limit the time
spent=20
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 =3D 20


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

  ExtendedLogging =3D yes


# Use this to temporarily stop bbackupd from syncronising or connecting
to=20
the store.
# This specifies a program or script script which is run just before
each=20
sync, and ideally
# the full path to the interpreter. It will be run as the same user=20
bbackupd is running as,
# usually root.
# The script prints either "now" or a number to STDOUT (and a
terminating=20
newline, no quotes).
# If the result was "now", then the sync will happen. If it's a number,=20
then the script will
# be asked again in that number of seconds.
# For example, you could use this on a laptop to only backup when on a=20
specific network.

# SyncAllowScript =3D /path/to/intepreter/or/exe script-name parameters
etc


# Where the command socket is created in the filesystem.

  CommandSocket =3D bbackupd/bbackupd.sock


Server
{
	PidFile =3D C:\Program Files\Box Backup\bbackupd\bbackupd.pid
}

#
# BackupLocations specifies which locations on disc should be backed up.
Each
# directory is in the format
#
# 	name
# 	{
# 		Path =3D /path/of/directory
# 		(optional exclude directives)
# 	}
#
# 'name' is derived from the Path by the config script, but should
merely be
# unique.
#
# The exclude directives are of the form
#
# 	[Exclude|AlwaysInclude][File|Dir][|sRegex] =3D regex or full
pathname
#
# (The regex suffix is shown as 'sRegex' to make File or Dir plural)
#
# For example:
#
# 	ExcludeDir =3D /home/guest-user
# 	ExcludeFilesRegex =3D *.(mp3|MP3)$
# 	AlwaysIncludeFile =3D /home/username/veryimportant.mp3
#
# This excludes the directory /home/guest-user from the backup along
with=20
all mp3
# files, except one MP3 file in particular.
#
# In general, Exclude excludes a file or directory, unless the directory
is
# explicitly mentioned in a AlwaysInclude directive.
#
# If a directive ends in Regex, then it is a regular expression rather
than a
# explicit full pathname. See
#
# 	man 7 re_format
#
# for the regex syntax on your platform.
#

BackupLocations
{
       TestData
	{
                 Path =3D C:\data\test\
	}
}