Re: [Burp-users] Protocol 1 vs Protocol 2

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

On Tue, October 6, 2015 8:19 am, Damien Hull wrote:
> Graham,
>
> Just read some of your burp 2 paper. While I don't understand most of it,
> I do like inline deduplication. I'm assuming this will speed up my backup
> process a lot.
>
> Is there a process for switching from protocol 1 to protocol 2?
>
> If not I'll have to come up with a process or workaround for this.

Hello,

All you do is run a burp-2 server, and a burp-2 client.
If you do not have protocol=1 set in the server or client config, they will
use protocol 2. You may also set protocol=2 on either side to make it
explicit.
See the 'protocol=[0|1|2]' section in the man page.

If you have upgraded from burp-1, you may need to set 'dedup_group = global'
in the server config as it won't exist yet.

When the client starts backing up, it will do so using this directory
structure
on the server:
/var/spool/burp/<dedup_group>/clients/<client>
/var/spool/burp/<dedup_group>/data

Clients in the same dedup_group share the dedup_group directory.
Backup data goes in the data directory, which is referenced by the manifests
in the dedup_group's client directories.
The <client> directory is equivalent to protocol 1 storage directories.

Since protocol 2 goes to <dedup_group>, it will preserve the protocol 1
storage directory at /var/spool/burp/<client> when you switch the client to
protocol 2. So you can switch back to protocol 1 whenever you like and get
your
old backups back.