# Duplicating ElasticSearch Content from Scroll Data

**URL:** <https://discuss.elastic.co/t/duplicating-elasticsearch-content-from-scroll-data/92292>\
**Category:** Elasticsearch\
**Created:** [July 7, 2017, 3:05pm UTC](https://discuss.elastic.co/t/duplicating-elasticsearch-content-from-scroll-data/92292 "2017-07-07T15:05:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pma07pg](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@pma07pg](https://discuss.elastic.co/u/pma07pg)\
**Post date:** [July 7, 2017, 3:05pm UTC](https://discuss.elastic.co/t/duplicating-elasticsearch-content-from-scroll-data/92292/1 "2017-07-07T15:05:50Z")

</div>

Hello,

This may sound like a backwards way of doing things but unfortunately my hands are very much tied.

There is a remote ElasticSearch server which is being populated with log data. I need to mirror the content of that server onto my local ElasticSearch server. I only have read access to this server and have been using the Scroll API to gather all log data within a certain time frame. Obtaining this has been straightforward enough, but when it comes to uploading it to my local server I am having some issues.

Is it possible for the response data I have to be read into my ElasticSearch server and have it properly indexed etc? The current response data looks like so:

```
{
	"_index" : "A_TEST",
"_type" : "010",
"_id" : "6122049e1be05b23138fd7df2a1905a20cfcd39b",
"_score" : 1.0,
"_source" : {
  "hostname" : "00000000d38406e7",
  "date_timestamp" : "2016-11-24T12:08:27.174",
  "tx-time" : "2017-06-13T07:51:33+02:00",
  "message" : "1479989307 174000000 -16.1811089 6.42675947 -3.0798585 6.61311561 1.63192656 
  "data_time" : 1479989307174,
  "data" : {
	"AngleA" : 2.0694754,
	"AngleB" : -1.70794374,
	"AngleC" : 3.2744498,
	"AngleD" : 277.993374,
	"AngleE" : 1.01377407
    }
}
}

```

I want to be able to have ElasticSearch/LogStash read this and set up the correct indices and field names as on the other server.

If anyone can recommend a different way of doing this or explain how it can be done then I'd be very grateful. I would have thought it could be read into ElasticSearch pretty easily but I am inexperienced with it.

Many thanks,  
Peter

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [July 7, 2017, 3:43pm UTC](https://discuss.elastic.co/t/duplicating-elasticsearch-content-from-scroll-data/92292/2 "2017-07-07T15:43:52Z")

</div>

See [https://www.elastic.co/guide/en/elasticsearch/reference/master/docs-reindex.html#reindex-from-remote](https://www.elastic.co/guide/en/elasticsearch/reference/master/docs-reindex.html#reindex-from-remote)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 4, 2017, 3:44pm UTC](https://discuss.elastic.co/t/duplicating-elasticsearch-content-from-scroll-data/92292/3 "2017-08-04T15:44:52Z")

</div>

Closed on August 4, 2017, 3:44pm UTC

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