◆ Elasticsearch

Back up Elasticsearch indexes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskBack up all indices in the 'payments' cluster to the 'daily-backups' repository. Get it done…+
Back up all indices in the 'payments' cluster to the 'daily-backups' repository. Get it done before the end-of-day report runs at 5 PM.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I back up the 'payments' cluster, we need to ensure we can actually restore from this.…+
Before I back up the 'payments' cluster, we need to ensure we can actually restore from this. Last time, a crucial index was corrupted during the backup process itself. Flag any indices that look unhealthy or might cause a restore failure.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'inventory' cluster just went red, and I need to start a restore. I'm afraid the automated…+
The 'inventory' cluster just went red, and I'm not sure if the last automated backup actually completed successfully, or if it was just a partial.
The 'inventory' cluster just went red, and I need to start a restore. I'm afraid the automated backup from 3 AM might have failed or only partially completed, as I saw some disk space warnings earlier. What's the quickest way to verify the integrity and completeness of that last snapshot before I attempt a full restore, and what's the safest fallback if it's compromised?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe're constantly questioning the reliability and completeness of our automated backups,…+
We frequently find ourselves questioning the reliability of our automated backups, especially after incidents, which delays recovery.
We're constantly questioning the reliability and completeness of our automated backups, especially when we're under pressure to restore after an incident. This uncertainty always adds significant stress and time to recovery efforts. What habit should I change in how we monitor or validate our backups to build consistent confidence in their integrity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Elasticsearch's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.