Snapshot and restore in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a snapshot repository named 'my_backup'.

Elasticsearch

PUT /_snapshot/[1]
{
  "type": "fs",
  "settings": {
    "location": "/mount/backups/my_backup"
  }
}

Drag options to blanks, or click blank then click option'

Abackup_repo

Bmy_backup

Csnapshot1

Drepo_backup

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different repository name in the URL and settings.

Misspelling the repository name.

The repository name must match the one used in the PUT request URL to create it.

2fill in blank

medium

Complete the code to create a snapshot named 'snapshot_1' in the 'my_backup' repository.

Elasticsearch

PUT /_snapshot/my_backup/[1]
{
  "indices": "index1,index2",
  "ignore_unavailable": true,
  "include_global_state": false
}

Drag options to blanks, or click blank then click option'

Abackup_1

Bsnap1

Csnapshot_1

Dbackup_snapshot

Attempts:

3 left

💡 Hint

Common Mistakes

Using the repository name instead of the snapshot name.

Using an invalid snapshot name.

The snapshot name is specified in the URL after the repository name.

3fill in blank

hard

Fix the error in the restore request to restore 'snapshot_1' from 'my_backup' repository.

Elasticsearch

POST /_snapshot/my_backup/[1]/_restore
{
  "indices": "index1",
  "rename_pattern": "index1",
  "rename_replacement": "restored_index1"
}

Drag options to blanks, or click blank then click option'

Asnapshot_1

Brestore_1

Cmy_backup

Dbackup_1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the repository name instead of the snapshot name in the URL.

Using a non-existent snapshot name.

The snapshot name must be used in the restore URL to specify which snapshot to restore.

4fill in blank

hard

Fill both blanks to create a snapshot that includes only 'logs-*' indices and excludes global state.

Elasticsearch

PUT /_snapshot/my_backup/[1]
{
  "indices": "[2]",
  "include_global_state": false
}

Drag options to blanks, or click blank then click option'

Asnapshot_logs

Blogs-*

Csnapshot_all

Dindex-*

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic snapshot name that doesn't match the indices.

Including global state when it should be excluded.

The snapshot name is 'snapshot_logs' and the indices pattern is 'logs-*' to include only log indices.

5fill in blank

hard

Fill all three blanks to restore 'snapshot_logs' from 'my_backup' repository, renaming 'logs-2023' to 'restored-logs-2023' and ignoring unavailable indices.

Elasticsearch

POST /_snapshot/my_backup/[1]/_restore
{
  "indices": "[2]",
  "rename_pattern": "[3]",
  "rename_replacement": "restored-logs-2023",
  "ignore_unavailable": true
}

Drag options to blanks, or click blank then click option'

Asnapshot_logs

Blogs-2023

Dsnapshot_all

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect snapshot or index names.

Not matching the rename pattern to the index name.

The snapshot name is 'snapshot_logs', the indices to restore is 'logs-2023', and the rename pattern matches the original index name.

Practice

1. What is the main purpose of taking a snapshot in Elasticsearch?

easy

A. To save a backup of your data for recovery later

B. To speed up search queries

C. To delete old indexes automatically

D. To create new indexes from templates

Solution

1. Step 1: Understand snapshot purpose

   A snapshot in Elasticsearch is used to save a backup of your data at a point in time.

2. Step 2: Compare options

   Options B, C, and D describe other Elasticsearch features, not snapshot backup.

3. Final Answer:

   To save a backup of your data for recovery later -> Option A

4. Quick Check:

   Snapshot = Backup [OK]

Hint: Snapshots save data backups for recovery [OK]

Common Mistakes:

• Confusing snapshots with index templates
• Thinking snapshots speed up searches
• Assuming snapshots delete data

2. Which of the following is the correct syntax to create a snapshot repository in Elasticsearch?

easy

A. POST /_snapshot/my_backup {"type": "fs", "settings": {"location": "/mount/backups"}}

B. PUT /_snapshot/my_backup {"type": "fs", "settings": {"location": "/mount/backups"}}

C. GET /_snapshot/my_backup {"type": "fs", "settings": {"location": "/mount/backups"}}

D. DELETE /_snapshot/my_backup {"type": "fs", "settings": {"location": "/mount/backups"}}

Solution

1. Step 1: Identify correct HTTP method for creating repository

   Creating a snapshot repository uses the PUT method to define or update it.

2. Step 2: Check other methods

   POST is for creating snapshots, GET is for retrieving info, DELETE is for removing repositories.

3. Final Answer:

   PUT /_snapshot/my_backup {"type": "fs", "settings": {"location": "/mount/backups"}} -> Option B

4. Quick Check:

   Repository creation = PUT [OK]

Hint: Use PUT to create or update snapshot repositories [OK]

Common Mistakes:

• Using POST instead of PUT for repository creation
• Confusing GET with creation commands
• Trying to delete instead of create repository

3. Given this snapshot restore request:

POST /_snapshot/my_backup/snapshot_1/_restore
{
  "indices": "index1,index2",
  "rename_pattern": "index(.*)",
  "rename_replacement": "restored_index$1"
}

What will be the name of the restored index originally named index2?

medium

A. restored_index2

B. restored_index_index2

C. index2

D. index_restored2

Solution

1. Step 1: Understand rename_pattern and rename_replacement

   The pattern "index(.*)" captures the part after "index". The replacement "restored_index$1" adds "restored_index" plus the captured part.

2. Step 2: Apply to index2

   For "index2", the captured part is "2", so the new name is "restored_index2".

3. Final Answer:

   restored_index2 -> Option A

4. Quick Check:

   Rename pattern + replacement = restored_index2 [OK]

Hint: Captured group $1 appends after renamed prefix [OK]

Common Mistakes:

• Ignoring rename_pattern and keeping original name
• Adding extra 'index' in the replacement
• Misplacing the captured group in new name

4. You try to restore a snapshot but get an error: repository_missing_exception. What is the most likely cause?

medium

A. The snapshot name is incorrect

B. The cluster is running an incompatible Elasticsearch version

C. The snapshot repository does not exist or is not registered

D. The indices in the snapshot are corrupted

Solution

1. Step 1: Understand repository_missing_exception meaning

   This error means Elasticsearch cannot find the snapshot repository to access snapshots.

2. Step 2: Check other options

   Snapshot name errors cause different exceptions; corrupted indices cause restore failures but not repository missing; version mismatch causes other errors.

3. Final Answer:

   The snapshot repository does not exist or is not registered -> Option C

4. Quick Check:

   repository_missing_exception = missing repository [OK]

Hint: Check repository registration if repository_missing_exception occurs [OK]

Common Mistakes:

• Assuming snapshot name typo causes repository_missing_exception
• Blaming corrupted indices for repository errors
• Ignoring repository setup before restore

5. You want to restore only specific indexes from a snapshot but rename them to avoid conflicts. Which JSON snippet correctly does this during restore?

{
  "indices": "logs-2023,metrics-2023",
  "rename_pattern": "(.*)-2023",
  "rename_replacement": "$1-restore"
}

hard

A. Restores only logs-restore and metrics-restore indexes from snapshot

B. Restores logs-2023 and metrics-2023 with original names

C. Restores all indexes in snapshot renamed with -restore suffix

D. Restores logs-2023 and metrics-2023 as logs-restore and metrics-restore

Solution

1. Step 1: Analyze indices and rename_pattern

   Indices "logs-2023" and "metrics-2023" match the pattern "(.*)-2023" capturing "logs" and "metrics".

2. Step 2: Apply rename_replacement

   Replacement "$1-restore" changes names to "logs-restore" and "metrics-restore".

3. Step 3: Confirm only specified indices restored

   Only indices listed in "indices" are restored, renamed as specified.

4. Final Answer:

   Restores logs-2023 and metrics-2023 as logs-restore and metrics-restore -> Option D

5. Quick Check:

   Indices filtered + renamed correctly = Restores logs-2023 and metrics-2023 as logs-restore and metrics-restore [OK]

Hint: Use indices + rename_pattern/replacement to rename on restore [OK]

Common Mistakes:

• Restoring all snapshot indices ignoring filter
• Not using rename_pattern correctly
• Expecting renamed indexes to exist before restore