> On Jan 7, 2025, at 6:50 AM, kasem adel <kasemadel8@gmail.com> wrote:
>
> Kindly be informed that database size is 1.8 TB and we have an low network bandwidth between two node 10 mbps and to
transferthe data from scratch that will take from 21 day to 30 day for this we need solution in upgrade to prevent
loaddata from scratch .
So, best case, bzip before transfer might get you down to 3 days, maybe. That's one alternative. Others:
- Obviously, if you could get higher network bandwidth temporarily, that would help tremendously.
- Express ship DVD/NVMe/SSD with the backup.
- I assume that if 10Mbps keeps up with changes, most of this data is inactive, are there inactive tables/partitions?
- Move inactive data into a separate PG cluster, use foreign data wrappers to access it from active so that your
usersdon't see the split.
- Upgrade cluster with inactive data locally.
- Whatever the process is to move data from active to inactive, you'll have to suspend it for the duration.
- Whether it's a month or 3 days, transfer the base backup of inactive over the slow link (keeping WAL, all the
thingsyou have to do to make sure that a replica started against this backup will be in sync and stream when brought
up)
- Proceed with upgrade of cluster with active data (presuming that it is *much* smaller)
Regardless, managing TB+ databases over a 10Mbps link is a challenge.
