◆ Apache Cassandra

Perform point-in-time 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 taskRestore the `transaction_logs` keyspace to its state as of 2:30 PM UTC yesterday, October 26,…+
Restore the `transaction_logs` keyspace to its state as of 2:30 PM UTC yesterday, October 26, 2023. Use the latest available incremental backups and ensure all data up to that specific timestamp is recovered. Confirm the restore operation completed successfully.
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 perform a point-in-time restore of the `user_activity` keyspace to recover from the…+
Before I perform a point-in-time restore of the `user_activity` keyspace to recover from the data corruption incident at 10:15 AM this morning, analyze the backup strategy and suggest if there's a more granular way to restore only the affected tables, or if a full keyspace restore is the only reliable option given our current setup. Also, identify any potential data loss window.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm performing a point-in-time restore of the `customer_orders` keyspace to 9 AM this morning…+
A point-in-time restore is taking too long, and the business is pressing for data availability.
I'm performing a point-in-time restore of the `customer_orders` keyspace to 9 AM this morning after a critical data deletion, but it's taking much longer than expected, and the sales team is demanding access to current order data. I can't tell if the restore is genuinely stuck, or if it's just processing a massive amount of data, and I'm afraid to cancel it and lose progress, but also afraid of missing the business recovery window. What's the most likely reason for the delay, and what's the best way to get a clear status update or accelerate the process without risking data integrity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur point-in-time restore operations for critical keyspaces consistently push us past our…+
Point-in-time restores are always stressful and often exceed our recovery time objectives.
Our point-in-time restore operations for critical keyspaces consistently push us past our recovery time objectives. We often find ourselves scrambling to identify the correct backup sets or dealing with unexpected dependencies, leading to prolonged downtime and high stress. What habit should I change to streamline our point-in-time recovery process, ensuring we can consistently meet RTOs and reduce the anxiety around data loss incidents?
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.