Restore 3

v2.0-12. Snapshot and Restore changes

File-system repositories must be whitelistededitLocations of the shared file system repositories and the URL repositories with file: URLs now have to be registered before starting Elasticsearch using the path.repo setting. The path.repo setting can contain one or more repository locations:shared file system repository와 file: 로 시작되는 URL repository의 위치의 URL은 Elasticsearch가 시작되기 전에 path.repo 설정에 등록..

6-4-09. Retiring Data

As time-based data ages, it becomes less relevant. It’s possible that we will want to see what happened last week, last month, or even last year, but for the most part, we’re interested in only the here and now.시간 기반의 데이터는 오래 될수록, 관련성이 적어진다. 지난 주, 지난 달, 심지어 지난해에 무슨 일이 있었는지 알고 싶을 수도 있지만, 대부분의 경우, 지금, 여기에만 관심이 있다.The nice thing about an index per time frame is that it enables us to easily delete o..

7-3-7. Restoring from a Snapshot

Once you’ve backed up some data, restoring it is easy: simply add _restore to the ID of the snapshot you wish to restore into your cluster:어떤 데이터를 백업했다면, restore은 매우 쉽다. 단순히, cluster에 restore하려는 snapshot의 ID에 _restore 를 추가하면 된다.POST _snapshot/my_backup/snapshot_1/_restoreThe default behavior is to restore all indices that exist in that snapshot. If snapshot_1 contains five indices, all five will..