Amazon Timestream for InfluxDB disaster recovery

Amazon Timestream for InfluxDB does indeed automatically take internal backups that are retained for 24 hours to support availability and durability. Additionally, snapshots are taken during delete operations and are retained for 30 days to support restores.

If you experience database corruption or a crash due to an application issue, the current procedure for restoring backed-up data would require you to create a case with AWS Support. The documentation indicates that to access or use these internal backups and snapshots, you need to file a ticket with AWS Support. There is no self-service option in the console to initiate a restore from these automatic backups.

Regarding control over which backup point is restored, the documentation doesn't explicitly mention whether you can select a specific backup point within the 24-hour window. Since the restore process requires AWS Support intervention, you would likely need to specify your desired restore point when creating the support case.

For more comprehensive disaster recovery planning, especially if you need to protect against complete AWS Region outages, you should consider setting up replication or writing to a different Region. However, it's important to understand the limitations of replication as mentioned in the InfluxDB documentation.

For Multi-AZ deployments, Timestream for InfluxDB provides automatic failover capabilities that help maintain availability during certain failure scenarios. Failover times typically range from 60-120 seconds, though this can be longer for large transactions with high-cardinality data or lengthy recovery processes.

The documentation doesn't mention specific plans to enhance backup options to match RDS capabilities, but AWS regularly updates its services based on customer feedback and requirements.
Sources
Resilience in Amazon Timestream for InfluxDB - Amazon Timestream
Reliability pillar - AWS Prescriptive Guidance
Amazon Timestream FAQs – Time-Series Database – AWS