Import file missing


#1

Hi,

When trying to migrate my Countly server to a new one I'm getting an "Import file missing" error on my source server (Step = Sending) and the whole process fails. Even if I try to export the file and then import I get this error.
Any idea what could be wrong? should I set an upload directory to the target's server nginx? (target server has enough disk space, and client_max_body_size is set to a big enough value.

Environment description:

  1. Source Server:

    • Countly 18.01
    • mongodb 3.6.9
    • Ubuntu 14
  2. Target Server:

    • Countly 18.08.1
    • mongodb 3.6.9
    • Ubuntu 16

Thanks in advanced,


#2

Hello,
You are second one to have this problem. I haven't found exactly why it was happening. As I tested it seems like source server wasn't adding file as attachment.

Can you please tell me what you mean by exporting and importing? Are you exporting and then pressing send? Or exporting, downloading and then importing.
Second one might work(if not - please let me know)

For this case definitely worked:
1)Exporting.
2) Sending file to target server.
3) Calling import via api.

Documentation for api call is here: https://resources.count.ly/reference#idatamigrationimport

https://yourserver/i/datamigration/import?auth_token=auth_token&existing_file=[FULL path to your file]
or using your API key

https://yourserver/i/datamigration/import?api_key=API_KEY&existing_file=[FULL path to your file]


#3

Hi Anna,

As I tested it seems like source server wasn't adding file as attachment.

As per my tests (mainly monitoring destination server disk space while the migration task is running), the compressed file is transferred but something happens when Countly tries to access it.
My data migration file is about 12GB so it takes long to finish all the process but it allows me to monitor space usage to be sure it's sent to the destination server.

Can you please tell me what you mean by exporting and importing? Are you exporting and then pressing
send? Or exporting, downloading and then importing.
Second one might work(if not - please let me know)

I tried both of them but neither worked for me.

For this case definitely worked:
1)Exporting.
2) Sending file to target server.
3) Calling import via api.

It worked (I got a lot of "duplicated key" messages but looks like the data was loaded)
My main concern about this approach is how much data is missed during the process since the compressed file is about 12GB, it takes a long time to export + transfer + import.

Regards,


#4

Hello,
Sorry for taking so long to write reply.
"duplicate key" messages means that you might be overwriting some data. (It might mean that you already had something partially imported)
Data during this process is lost. We are planning on improving it to deal with this issue.