On Mon, Apr 20, 2020 at 6:55 PM Frank Crawford
wrote:
> Lance,
>
> Just to add a bit more on some of Kevin's comments, this does not break
> any of your backups and existing backups are both readable and writable
> with both versions. What is broken is the backup process in some cases, as
> a
Lance,
Just to add a bit more on some of Kevin's comments, this does not break
any of your backups and existing backups are both readable and writable
with both versions. What is broken is the backup process in some
cases, as a Python3 master cannot talk to a Python2 slave, and visa-
versa.
It
On Mon, Apr 20, 2020 at 09:59:17AM -0700, Lance Albertson wrote:
> What does the upgrade path look like from if folks are currently creating
> backups using 1.x and they suddenly switch to 2.x? Is there an upgrade
> path? Is there a way in EPEL to allow for both versions to exist to ease
>
What does the upgrade path look like from if folks are currently creating
backups using 1.x and they suddenly switch to 2.x? Is there an upgrade
path? Is there a way in EPEL to allow for both versions to exist to ease
migration? i.e. maybe by creating rdiff-backup2 which
supercedes rdiff-backup.
