need suggestions for replacing current PBR with new one

[markf1301]

Hello.

I currently have a pve/pbr server. The current pbr side has over a year of data which I'd like to keep, as its current with my current backups.
I ordered and should receive the new box today and will be building it over the weekend in preparation to replace the current pve/pbr mess I currently have.

Both the units will be 'remote' but the sync is working now in that the remote side, does the pull from the corp side and the pbr is my offside backups.

I'd like to sync 'all' data from the current (old) box to the new one and then, somewhere in between, stop the pull process from the old box and start pulling the new backups from the corp side, to the new pbr box.

I'd thought of setting up a 'push' from the old pbr, to the new pbr box and then after the 'sync' process - start the pull on the new box, hoping this will only try to pull 'new' backup information across to the new server. The backup schedule would be the same once the new pbr is in place but don't want to 'pull' all data (old data already there) across the site-2-site connection as that'll take days, if not more. If I create a connection between the old pbr and the new pbr and push the data over, and then initiate a pull from the corp side (to the new pbr server) - will the data be correct as far as the checksums and validation of the data? I presume even after pushing the data to the new box that I need to run a 'verify' job but i'm not sure if the data that is verified - would be from hash info coming from the corp side or residing on the data that has been pushed and stored on the old box.

Looking for suggestions for the easiest way to manage this task. I'm probably over thinking this, huh?
Also, wishing I had more than 1-g connectivity at the remote side as that'd make the process of 16TB transfer faster between the 2 pbr boxes.

thanks in advance,

 

[Chris]

Hi,

I'd like to sync 'all' data from the current (old) box to the new one and then, somewhere in between, stop the pull process from the old box and start pulling the new backups from the corp side, to the new pbr box.

Yes, this will work. You can e.g. pull sync snapshots from the old host to the new host, and then reconfigure the new host to pull from the corporate PBS instance. This will only transfer the new snapshots, not already known to the PBS.

I'd thought of setting up a 'push' from the old pbr, to the new pbr box and then after the 'sync' process - start the pull on the new box, hoping this will only try to pull 'new' backup information across to the new server. The backup schedule would be the same once the new pbr is in place but don't want to 'pull' all data (old data already there) across the site-2-site connection as that'll take days, if not more. If I create a connection between the old pbr and the new pbr and push the data over, and then initiate a pull from the corp side (to the new pbr server) - will the data be correct as far as the checksums and validation of the data?

Yes, new data being synced will be verified by the sync job, however pre-existing chunks will not. But since you pulled in also the other chunks freshly from the old host, these chunks are verified already.

Regarding the data transfer: You also have the option to use removable datastores for the sync if that works out better.

I presume even after pushing the data to the new box that I need to run a 'verify' job but i'm not sure if the data that is verified - would be from hash info coming from the corp side or residing on the data that has been pushed and stored on the old box.

A full datastore verification is not really needed if you do a fresh sync. However, you can do a full verification on the source (old host) and only pull in snapshots which were successful verified.

Looking for suggestions for the easiest way to manage this task. I'm probably over thinking this, huh?
Also, wishing I had more than 1-g connectivity at the remote side as that'd make the process of 16TB transfer faster between the 2 pbr boxes.

As stated, depending on what you have at your disposal, syncing the data to a removable datastore and physically transport that over to the new location and add it as removable datastore there for a final sync might also be an option.