Issue while restoring snapshot in cluster environment

(Vinod Rao) #1

Hi Team,

Can any one help me on why we are getting the below error while restoring.

{"error":"RemoteTransportException[[goemtdbpgqa04][inet[/]][cluster:admin/repository/put]]; nested: RepositoryVerificationException[[director-services] path is not accessible on master node]; nested: FileNotFoundException[/gdbackup/GDIndexerBackups/director-services/tests-BNlmbKY6RfK8pk-o2FSMOA-master (Read-only file system)]; ","status":500}14:56 Check the status of the repository

(Mark Walkom) #2

Can you check that?

(Vinod Rao) #3

While restore also do we need to have the file system Read write. I am thinking that we can use readonly file system , may be i am wrong ?? The mount point shared NAS storage..

(Mark Walkom) #4

It needs to be read/write.
We haven't implemented read only repositories as yet.

(David Pilato) #5

We actually have the URL (read only) repo:

Also, you could try using readonly parameter from 2.1.0 when you create the Shared FS repo:

(Mark Walkom) #6

Oh, I was thinking more WORM style.

(Vinod Rao) #7

Thank you team, I have some doubt on this. Is it necessary to include shared repository path in elasticsearch.yml using path.repo ?

In the mentioned URL it says as below.

Assuming that the shared filesystem is mounted to /mount/backups/my_backup, the following setting should be added to elasticsearch.yml file:

path.repo: ["/mount/backups", "/mount/longterm_backups"]

Whey we added "/mount/longterm_backups" to path.repo?

And one more thing do we need to add " readonly : true " option during the repository setting for restore only or we can do it for both snapshot&restore repositories.

Vinodkumar Banda

(Vinod Rao) #8

Is this path.repo module work in elastic 1.4 version, if its not work what could be the best solution for read only file system.

(system) #9