Moving over snapshot to another system doesn't get added to registered repo

I am taking a snapshot on system 1 and transferring the index-X, index.latest, meta-... and snap-.... over to system 2 under the same registered repo. System 2 does not find snapshot for restore.

--> curl -X PUT "X.X.X.X:9200/_snapshot/es_backup?pretty" -H 'Content-Type: application/json' -d'{ "type":"fs", "settings": { "location": "/var/lib/backups/es-snapshots" } }' SUCCESS
--> curl -XPUT "http://X.X.X.X:9200/_snapshot/es_backup/testsnap?pretty" -H 'Content-Type: application/json' -d' { "indices": "filebeat-7.15.0-2022.03.28-000167", "ignore_unavailable": true, "include_global_state": true}' SUCCESS

--> SCP to SYSTEM2 under same path.repo path.
on System 2:
curl -X GET "XXXX:9200/_snapshot/es_backup/_all?pretty"
"snapshots" : ,
"total" : 0,
"remaining" : 0
How can I make system 2 aware of the snapshot?

Welcome to our community! :smiley:

What is the scp command you are running?
Also please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you :slight_smile:

See this note in the docs:

Don’t modify anything within the repository or run processes that might interfere with its contents. ... You may however safely restore a repository from a backup

It sounds like you are modifying the contents of a repository but you are not following the proper procedure for restoring a repository from a backup.

Sorry I meant I'm simply winscp'ing it over to the other machine.
I'm following these steps:

I'm not sure the steps in that article really work, at least not reliably. You should follow the instructions in the reference manual.

Thank you, the docs truly are the best reference if you read them carefully :).

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.