# Elasticsearch 7.10.2 backup

**URL:** <https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [May 5, 2023, 11:03am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642 "2023-05-05T11:03:50Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 5, 2023, 11:03am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/1 "2023-05-05T11:03:50Z")

</div>

Hi everyone

My name is José Manuel and I am trying to make a back from elasticsearch 7.10.2, but show me the next error

```auto
# curl -X PUT localhost:9200/_snapshot/my_backup?pretty -H 'Content-Type: application/json' -d '{ "type": "fs", "settings": { "location": "/backup" } }'
<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Access Denied (authentication_failed)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>

```

Can anyone help me?

Best regards. Thanks a lot.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 5, 2023, 11:05am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/2 "2023-05-05T11:05:23Z")

</div>

If someone needs the elasticsearch.yml or something more please call me.  
the linus is a Debian 11, graylog 4.3, elasticsearch 7.10.2

Best regards.

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [May 5, 2023, 11:11am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/3 "2023-05-05T11:11:09Z")

</div>

Hi José,

It looks like you are missing credentials in your request. Can you try adding credentials similar to the [curl example here in the documentation](https://www.elastic.co/guide/en/kibana/master/api-keys.html#:~:text=Create%20an%20API%20keyedit,API%20Keys%20%3E%20Create%20API%20key.&text=API%20keys%20are%20intended%20for%20programmatic%20access%20to%20Kibana%20and%20Elasticsearch) and see if that resolves your issue?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 8, 2023, 3:20am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/4 "2023-05-08T03:20:19Z")

</div>

It looks like you have something in front of Elasticsearch that is proxying requests, as that is not something that Elasticsearch will respond with.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 6:21am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/5 "2023-05-08T06:21:30Z")

</div>

Hi Mister

Now I did this simple comand and nothing

```auto
curl -X GET "http://localhost:9200?pretty"
<HTML><HEAD>
<TITLE>Redirect</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Redirect (authentication_redirect_to_virtual_host)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
You are being redirected to the authentication virtual host.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">

</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>

```

Why can not I use this comand?

Best regards.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 6:24am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/6 "2023-05-08T06:24:30Z")

</div>

Hi Carly.richmond

I am not using kibana, I am using graylog with elasticsearch and mongod , if you know another way to make backups please tell me about that.

Best regards.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 7:22am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/7 "2023-05-08T07:22:36Z")

</div>

You need to use the snapshot/restore API to backup Elasticsearch, and this will require you to have direct access to Elasticsearch and also potentially to update the configuration files directly. At the moment you are not accessing Elasticsearch directly as the HTML formatted error is not generated by Elasticsearch.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 8:14am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/8 "2023-05-08T08:14:09Z")

</div>

Hi mister

I am making the same in the phisical elastic with the same result, What am I doing wrong?

```auto
root@GRAYLOGDEBIANSERVER:/var/log/graylog-server# curl -X GET "http://localhost:9200?pretty"
<HTML><HEAD>
<TITLE>Redirect</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Redirect (authentication_redirect_to_virtual_host)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
You are being redirected to the authentication virtual host.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">

</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>
root@GRAYLOGDEBIANSERVER:/var/log/graylog-server#

```

Best regards.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 8:26am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/9 "2023-05-08T08:26:39Z")

</div>

You must have a proxy or third party plugin installed, which seems to be what is causing problems. Log into the host and check whether a proxy is in place and which interface and port Elasticsearch is configured to use.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 8:30am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/10 "2023-05-08T08:30:29Z")

</div>

Hi again

I edited the elasticsearch.yml  
this is the elasticsearch.yml file

```auto
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: graylog
#
#action.auto_create_index: false
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
path.repo: ["/backup"]
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 192.168.222.243
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: elasticsearch.local
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
#action.auto_create_index: false

```

the result of the comand is the next:

```auto
root@GRAYLOGDEBIANSERVER:/var/log/graylog-server# curl -X GET "http://192.168.222.243:9200?pretty"
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (tcp_error)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
A communication error occurred: "Operation timed out"
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>
root@GRAYLOGDEBIANSERVER:/var/log/graylog-server#

```

I am executing all in the phisical machine whre is installed elasticsearch.  
What is happening?

Best regards. Thanks a lot.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 8:54am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/11 "2023-05-08T08:54:31Z")

</div>

I suspect you may have some third-party security plugin installed as there does not seem to be any external proxy. Did you install Elasticsearch yourself or was this done through Graylog? If the latter you may need to contact them.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 9:22am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/12 "2023-05-08T09:22:31Z")

</div>

Hi Christian\_Dahlqvist

I installed elasticsearch by myself using the graylog instructions but graylog put the Elastic manual to install elasticsearch so, What´s going on?

Best regards. Thanks a lot.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 9:34am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/13 "2023-05-08T09:34:32Z")

</div>

Did you install any third-party plugins?

Did you download the offical distribution of Elasticsearch?

> [@jomaguca](#):
>
> What´s going on?

I do not know. I have never seen the Graylog instructions so am not sure what they contain.

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 9:43am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/14 "2023-05-08T09:43:23Z")

</div>

Hi again

No plugins.  
yes the elasticsearch is from elastic web page.  
the correct version is 7.9.3 but is the same, don´t?

Best regards. Thanks a lot. Sorry to make many questions.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 10:06am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/15 "2023-05-08T10:06:35Z")

</div>

Can you run `netstat -pln | grep 9200` (think that should work) on the host where Elasticsearch is running and show the output here?

Can you verify that Elasticsearch is running?

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 10:16am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/16 "2023-05-08T10:16:54Z")

</div>

Hi again Mr Christian\_Dahlqvist  
The commando you send me doen´t work but systemctl status woks so here we go

```auto
root@GRAYLOGDEBIANSERVER:/etc/elasticsearch# netstat -pln | grep 9200
bash: netstat: command not found
root@GRAYLOGDEBIANSERVER:/etc/elasticsearch# systemctl status elasticsearch
● elasticsearch.service - Elasticsearch
     Loaded: loaded (/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-05-08 10:18:27 CEST; 1h 56min ago
       Docs: https://www.elastic.co
   Main PID: 4441 (java)
      Tasks: 68 (limit: 7071)
     Memory: 1.2G
        CPU: 1min 20.791s
     CGroup: /system.slice/elasticsearch.service
             ├─4441 /usr/lib/jvm/java-17-openjdk-amd64/bin/java -Xshare:auto -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encod>
             └─4631 /usr/share/elasticsearch/modules/x-pack-ml/platform/linux-x86_64/bin/controller

May 08 10:18:17 GRAYLOGDEBIANSERVER systemd[1]: Starting Elasticsearch...
May 08 10:18:19 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: A terminally deprecated method in java.lang.System has been called
May 08 10:18:19 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: System::setSecurityManager has been called by org.elasticsearch.bootstrap.Elasticsearch (file:/usr/share/elasticsearch/lib/elasticsearch-7.9.3.ja>
May 08 10:18:19 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: Please consider reporting this to the maintainers of org.elasticsearch.bootstrap.Elasticsearch
May 08 10:18:19 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: System::setSecurityManager will be removed in a future release
May 08 10:18:20 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: A terminally deprecated method in java.lang.System has been called
May 08 10:18:20 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: System::setSecurityManager has been called by org.elasticsearch.bootstrap.Security (file:/usr/share/elasticsearch/lib/elasticsearch-7.9.3.jar)
May 08 10:18:20 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: Please consider reporting this to the maintainers of org.elasticsearch.bootstrap.Security
May 08 10:18:20 GRAYLOGDEBIANSERVER systemd-entrypoint[4441]: WARNING: System::setSecurityManager will be removed in a future release
May 08 10:18:27 GRAYLOGDEBIANSERVER systemd[1]: Started Elasticsearch.
lines 1-22/22 (END)

```

Thanks man, very pleased to help me.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 10:18am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/17 "2023-05-08T10:18:43Z")

</div>

Can you please show the full logs from the point where you restarted Elasticsearch?

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 10:22am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/18 "2023-05-08T10:22:35Z")

</div>

netstat is repared, this is the result:

```auto
root@GRAYLOGDEBIANSERVER:/etc/elasticsearch# netstat -pln | grep 9200
tcp6 0 0 192.168.222.243:9200 :::* LISTEN 4441/java
root@GRAYLOGDEBIANSERVER:/etc/elasticsearch#

```

the directory /var/log/elasticsearh has all of this log files, What do you need? OH my GOD

```auto
root@GRAYLOGDEBIANSERVER:/var/log/elasticsearch# ls
elasticsearch_audit.json gc.log.07 gc.log.24 graylog-2023-01-12-1.log.gz graylog-2023-01-25-1.json.gz graylog-2023-02-07-1.log.gz graylog-2023-05-04-1.json.gz
elasticsearch_deprecation.json gc.log.08 gc.log.25 graylog-2023-01-13-1.json.gz graylog-2023-01-25-1.log.gz graylog-2023-02-22-1.json.gz graylog-2023-05-04-1.log.gz
elasticsearch_deprecation.log gc.log.09 gc.log.26 graylog-2023-01-13-1.log.gz graylog-2023-01-26-1.json.gz graylog-2023-02-22-1.log.gz graylog-2023-05-05-1.json.gz
elasticsearch_index_indexing_slowlog.json gc.log.10 gc.log.27 graylog-2023-01-16-1.json.gz graylog-2023-01-26-1.log.gz graylog-2023-03-01-1.json.gz graylog-2023-05-05-1.log.gz
elasticsearch_index_indexing_slowlog.log gc.log.11 gc.log.28 graylog-2023-01-16-1.log.gz graylog-2023-01-27-1.json.gz graylog-2023-03-01-1.log.gz graylog-2023-05-06-1.json.gz
elasticsearch_index_search_slowlog.json gc.log.12 gc.log.29 graylog-2023-01-17-1.json.gz graylog-2023-01-27-1.log.gz graylog-2023-03-02-1.json.gz graylog-2023-05-06-1.log.gz
elasticsearch_index_search_slowlog.log gc.log.13 gc.log.30 graylog-2023-01-17-1.log.gz graylog-2023-01-30-1.json.gz graylog-2023-03-02-1.log.gz graylog_audit.json
elasticsearch.log gc.log.14 gc.log.31 graylog-2023-01-18-1.json.gz graylog-2023-01-30-1.log.gz graylog-2023-03-03-1.json.gz graylog_deprecation.json
elasticsearch_server.json gc.log.15 graylog-2022-12-22-1.json.gz graylog-2023-01-18-1.log.gz graylog-2023-01-31-1.json.gz graylog-2023-03-03-1.log.gz graylog_deprecation.log
gc.log gc.log.16 graylog-2022-12-22-1.log.gz graylog-2023-01-19-1.json.gz graylog-2023-01-31-1.log.gz graylog-2023-03-27-1.json.gz graylog_index_indexing_slowlog.json
gc.log.00 gc.log.17 graylog-2022-12-27-1.json.gz graylog-2023-01-19-1.log.gz graylog-2023-02-01-1.json.gz graylog-2023-03-27-1.log.gz graylog_index_indexing_slowlog.log
gc.log.01 gc.log.18 graylog-2022-12-27-1.log.gz graylog-2023-01-20-1.json.gz graylog-2023-02-01-1.log.gz graylog-2023-03-28-1.json.gz graylog_index_search_slowlog.json
gc.log.02 gc.log.19 graylog-2023-01-10-1.json.gz graylog-2023-01-20-1.log.gz graylog-2023-02-02-1.json.gz graylog-2023-03-28-1.log.gz graylog_index_search_slowlog.log
gc.log.03 gc.log.20 graylog-2023-01-10-1.log.gz graylog-2023-01-23-1.json.gz graylog-2023-02-02-1.log.gz graylog-2023-03-29-1.json.gz graylog.log
gc.log.04 gc.log.21 graylog-2023-01-11-1.json.gz graylog-2023-01-23-1.log.gz graylog-2023-02-03-1.json.gz graylog-2023-03-29-1.log.gz graylog_server.json
gc.log.05 gc.log.22 graylog-2023-01-11-1.log.gz graylog-2023-01-24-1.json.gz graylog-2023-02-03-1.log.gz graylog-2023-05-03-1.json.gz
gc.log.06 gc.log.23 graylog-2023-01-12-1.json.gz graylog-2023-01-24-1.log.gz graylog-2023-02-07-1.json.gz graylog-2023-05-03-1.log.gz
root@GRAYLOGDEBIANSERVER:/var/log/elasticsearch#

```

Sorry again...

---

<div class="post-metadata">

**Author:** ![jomaguca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jomaguca/32/117583_2.png) [@jomaguca](https://discuss.elastic.co/u/jomaguca)\
**Post date:** [May 8, 2023, 10:42am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/19 "2023-05-08T10:42:49Z")

</div>

I putted in a browser [http://192.168.222.243:9200](http://192.168.222.243:9200) and the result is

```auto
{
  "name" : "GRAYLOGDEBIANSERVER",
  "cluster_name" : "graylog",
  "cluster_uuid" : "orXEkVScRG-hU88wODz7Kg",
  "version" : {
    "number" : "7.9.3",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "c4138e51121ef06a6404866cddc601906fe5c868",
    "build_date" : "2020-10-16T10:36:16.141335Z",
    "build_snapshot" : false,
    "lucene_version" : "8.6.2",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

```

it is the same result that putting.  
curl -X GET "[http://192.168.222.243:9200](http://192.168.222.243:9200)"  
Am I in right?

Best regards.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 8, 2023, 10:53am UTC](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642/20 "2023-05-08T10:53:36Z")

</div>

Yes, that is what I would expect and the url command should give the same response.

[Next page](https://discuss.elastic.co/t/elasticsearch-7-10-2-backup/332642.md?page=2)