I did configure the repository.
I issue to capture Snapshot was resloved after removing proxy url and port.
Thanks for @warkolm.
However now I am not able to restore the snapshots. Following is the policy I have applied
curl -k -v -XPUT -u "es_account":"ES_ACCOUNT_PASSWORD" "https://localhost:9200/_slm/policy/night-snpsht1?pretty" -H 'Content-Type: application/json' -d'
{
"schedule": "0 30 1 * * ?",
"name": "<n-s1-{now/d}>",
"repository": "s3_backup",
"config": {
"indices": ["*"]
},
"retention": {
"expire_after": "15d",
"min_count": 5,
"max_count": 50
}
}'
Request -
After executing -
https://localhost:9200/_slm/policy/night-snpsht1/_execute
Response
{
"snapshot_name": "n-s1-2020.12.30-d52_0hv9qmsemma75yfqtw"
}
However when I run below
Request -
https://localhost:9200/_snapshot/s3_backup/n-s1-2020.12.30-d52_0hv9qmsemma75yfqtw/_restore
I get below response -
{
"error": {
"root_cause": [
{
"type": "snapshot_restore_exception",
"reason": "[s3_backup:n-s1-2020.12.30-d52_0hv9qmsemma75yfqtw/sZpqtI8_S7y-kbO28cSZ5Q] cannot restore index [.slm-history-1-000001] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name"
}
],
"type": "snapshot_restore_exception",
"reason": "[s3_backup:n-s1-2020.12.30-d52_0hv9qmsemma75yfqtw/sZpqtI8_S7y-kbO28cSZ5Q] cannot restore index [.slm-history-1-000001] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name"
},
"status": 500
}