Both to the same network drive, sorry.

On Thu, Oct 17, 2019 at 10:05 AM Koen De Groote <koen.degro...@limecraft.com>
wrote:

> Yes, both servers back up to a network drive.
>
> However, that is not the point of my question.
>
> The point of my question is: If I execute the curl command, that contacts
> the collections API, to perform the backup, does it matter that the leader
> is on a different host from the one where the backup command was executed?
>
>
>
> On Thu, Oct 17, 2019 at 9:30 AM Jon Kjær Amundsen <j...@udbudsvagten.dk>
> wrote:
>
>> Hi Koen
>>
>> A quick sanity check:
>> Do you use a network drive accessible from both servers to make the backup
>> to?
>> If you've backed up server2's collection to a local disk, then when you're
>> trying to restore it via server1 it does not know anything about the
>> backup.
>>
>> Venlig hilsen/Best regards
>>
>> *Jon Kjær Amundsen*
>> Developer
>>
>>
>> Phone: +45 7023 9080
>> E-mail: j...@udbudsvagten.dk
>> Web: www.udbudsvagten.dk
>> Parken - Tårn D - 5. Sal
>> Øster Allé 48 | DK - 2100 København
>>
>> <http://dk.linkedin.com/in/JonKjaerAmundsen/>
>>
>> Intelligent Offentlig Samhandel
>> *Før, under og efter udbud*
>>
>> *Følg UdbudsVagten og markedet her Linkedin
>> <http://www.linkedin.com/groups?groupDashboard=&gid=1862353> *
>>
>>
>> Den ons. 16. okt. 2019 kl. 17.42 skrev Koen De Groote <
>> koen.degro...@limecraft.com>:
>>
>> > I'm trying to restore a couple of collections, and 1 keeps feeling. This
>> > happens to be the only one who's leader isn't on the host that the
>> backup
>> > was taken from.
>> >
>> >
>> > The backup was done on server1, for all collections.
>> >
>> > For this collection that is failing, the Leader was on server2. All
>> other
>> > collections had their leader on server1. All collections had 1 replica,
>> on
>> > the other server.
>> >
>> > I would think that having the replica there would be enough to perform a
>> > restore.
>> >
>> > Or does the backup need to happen on the actual leader?
>> >
>> > Kind regards,
>> > Koen De Groote
>> >
>>
>

Reply via email to