Re: [Burp-users] multiple client backup profiles

[Graham K. <gr...@gr...>]

On Mon, Dec 29, 2014 at 10:33:06AM +0000, Graham Keeling wrote:
> On Mon, Dec 29, 2014 at 03:58:51PM +1100, Neil Renfrey wrote:
> > Hi
> > 
> > Is there any way to have the same client have more than one client profile
> > on the server. I'm trying to achieve backing up very large files overnight
> > and smaller files backed up in the manner of Time Machine on a Mac during
> > the day, say every couple of hours. If I modify the include filter and have
> > different settings for day and overnight, I assume the large file would be
> > backed up in its entirety each time it re-appeared in the list. 
> > 
> > I have to back up many small files and a single file of 30Gb of which 1Gb
> > may have changed with minimal impact to the user.  The only way I can think
> > of at present is to try to have 2 client profiles on the server, but when I
> > tried this I ran into trouble with the SSL settings not being recognised for
> > each profile
> > 
> > Any ideas would be appreciated
> 
> Hello,
> 
> Librsync isn't very good at backing up very large files that change, and
> therefore burp-1 isn't either - unless you turn librsync off. If you turn
> librsync off, it means that the whole 30Gb will get backed up each time.
> 
> If you want to try having two different 'profiles' for a client...
> 
> It is possible, but not necessarily the easiest thing to set up.
> You have to treat the two profiles as two separate clients, which means
> setting up an alternative burp.conf on the client.
> Here is how I did it, calling the two clients 'win64' and 'win64-alt':
> 
> 
> First, I set up win64 and win64-alt in /etc/burp/clientconfdir on the server.
> You will probably make your life easier if you put the 'includes =' lines in
> these files on the server instead of burp.conf on the client.
> 
> Then, I configured burp.conf on the client, and had the client connect using it:
> 
> burp -a l
> 
> Then, I copied it to burp-alt.conf, and changed the following lines in
> burp-alt.conf:
> 
> cname = win64-alt
> ssl_cert_ca = C:/Program Files/Burp/ssl_cert_ca-alt.pem
> ssl_cert = C:/Program Files/Burp/ssl_cert-client-alt.pem
> ssl_key = C:/Program Files/Burp/ssl_cert-client-alt.key
> 
> And then had the client connect using burp-alt.conf:
> burp -a l -c "C:\Program Files\Burp\burp-alt.conf"
> 
> You can then set up two different timed jobs on the client to run
> burp -a b
> and
> burp -a b -c "C:\Program Files\Burp\burp-alt.conf"
> 
> 
> If you have tried this already, and some SSL problem was happening,
> you have probably messed up the client certificates in some way - maybe
> because both files have the same ssl_cert and ssl_key.
> You don't need to touch the ca_burp_ca and ca_csr_dir settings.
> 
> You can fix it by doing this on the server (I tested this too, and know it
> works):
> cd /etc/burp/CA
> rm win64.crt win64.csr
> rm win64-alt.crt win64-alt.csr
> 
> And deleting these on the client:
> C:\Program Files\Burp\ssl*
> C:\Program Files\Burp\CA\*
> 
> Then copy burp.conf to burp-alt.conf, change the lines above, and run
> burp -a l
> and
> burp -a l -c "C:\Program Files\Burp\burp-alt.conf"


>From Ziirish's post, it looks like you don't need to change ssl_cert_ca.

Also, his post reminded me that the Windows burp doesn't do any local locking
(though it is OK in normal operation because the timed jobs won't overlap, and
if they did, the server does its own locking on forked children anyway).
So, if you are using a Windows client, you might want to put the two commands
in the same timed job so that they don't overlap.
Something like this, or whatever the Windows equivalent is:
burp -a l ; burp -a l -c "C:\Program Files\Burp\burp-alt.conf"

On Linux, you may or may not want to change the pidfile setting depending on
whether you do or do not want the jobs to overlap.