◆ Apache Cassandra

Perform Cassandra backup and restore

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 taskInitiate a full backup of the 'customer_data' keyspace in the production Cassandra cluster to…+
Initiate a full backup of the 'customer_data' keyspace in the production Cassandra cluster to the designated S3 bucket.
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 schedule the upgrade for next month, outline the steps for performing a full backup of…+
Before I schedule the upgrade for next month, outline the steps for performing a full backup of the 'order_history' keyspace and then restoring it to a staging environment. Highlight any potential gotchas or dependencies that could cause issues during the restore process, so I can plan for them.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSomeone accidentally dropped the 'user_profiles' table in our production Cassandra cluster. We…+
A critical table was accidentally dropped in production, and we need to restore it quickly.
Someone accidentally dropped the 'user_profiles' table in our production Cassandra cluster. We have a backup from last night, but I'm worried about data loss between then and now, and the impact of a full keyspace restore on application availability. What's the fastest and safest way to restore just that table, minimizing downtime and data loss, and what should I communicate to the product owner about the recovery time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time we need to perform a database restore, it feels like a high-stress scramble, often…+
Our backup and restore process feels like a scramble every time we need it.
Every time we need to perform a database restore, it feels like a high-stress scramble, often revealing gaps in our documentation or tooling. This uncertainty erodes confidence in our disaster recovery plan. What regular practice can I adopt to ensure our backup and restore procedures are always well-understood, tested, and reliable, so we're prepared for any incident?
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 Apache Cassandra'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.