Hmm... I see... > > >> Depending on when you took the base backup and how many changes have >> occurred at your source (slave1) database cluster, the rsync execution time >> may or may not take as long as a new base backup if is only only shipping >> deltas (changed files). > > I could stop the slave then.... But I'm afraid getting it back online and get some other errors hehehehe =\
Lucas Possamai kinghost.co.nz <http://forum.kinghost.co.nz/memberlist.php?mode=viewprofile&u=2&sid=e999f8370385657a65d41d5ff60b0b38> On 10 January 2016 at 10:59, bricklen <brick...@gmail.com> wrote: > On Sat, Jan 9, 2016 at 1:54 PM, drum.lu...@gmail.com <drum.lu...@gmail.com > > wrote: > >> Hi, >> >> If you are able to stop Postgres on the slave you are taking the base >>> backup from, you could do this: >> >> >> I'm not... the data base is 2 TB. >> So, a RSYNC would take DAYS..... And I'm not able to stop the SLAVE for >> that long time >> > > Depending on when you took the base backup and how many changes have > occurred at your source (slave1) database cluster, the rsync execution time > may or may not take as long as a new base backup if is only only shipping > deltas (changed files). >
