DigitalOcean home
  • Droplets
  • Spaces
  • Kubernetes
  • Tools & Integrations
  • One-click Apps
  • API Documentation
  • Community
  • Tutorials
  • Q&A
  • Projects
  • Meetups
  • Customers
  • Pricing
  • Docs
  • Support
  • DigitalOcean home
  • Products
    • Droplets

      Scalable compute services.

    • Spaces

      Simple object storage.

    • Kubernetes

      Run managed Kubernetes clusters.

    • Tools & Integrations

      Automate your infrastructure.

    • One-click Apps

      Deploy pre-built applications.

    • API Documentation
  • Customers
  • Community
    • Community Overview

      Connect, share and learn

    • Tutorials

      DevOps and development guides

    • Questions & Answers

      Development and systems Q&A

    • Projects

      Community-built integrations

    Get Involved
    Write for DOnations
    Join us at a Meetup
    Featured Post
    An Introduction to Kubernetes

    by Justin Ellingwood

  • Pricing
  • Docs
  • Support
    • Documentation

    • Contact Support

    • Network Status

  • Home /
  • DBAAS-I-132 /
  • New idea
1 Vote

Better documentation of point in time recovery

Currently, the PITR mechanism on the managed DB is slightly broken in terms of the UI and the API.


On the UI, I'd expect when I select a HHMMSS for point in time recovery, for the DB to be recovered upto that point. But it turns out that this doesn't happen and only the latest backup before that time is used. This is unexpected and a wrong behaviour for the offering.


On the API, there seems to be a limitation of not being able to use uppercase characters in the name field. This returns a blank "422 unprocessable Entity" error without informed where exactly the problem is. It would be good to have more detailed errors in the API instead of having to reach to ask the customer support

  • Guest
  • Feb 25 2021
  • Needs review
Managed Databases
  • Comments (1)
  • Votes (1)
  • Attach files
  • Admin
    Mark Huber commented
    26 Feb 04:13pm

    The intended behavior is actual PITR; there's a UI bug that is causing it to fallback to the last backup, which we're in the process of fixing now.

    I'll take a look at the mentioned API issue.

    ×

    Attachments Open full size

Log in / Sign up

Identify yourself with your email address

Subscribe

You won't be notified about changes to this idea.

Related ideas

DigitalOcean home

© 2018 DigitalOcean, LLC. All rights reserved.
Proudly made in NY

  • Twitter
  • Facebook
  • Instagram
  • YouTube
  • LinkedIn
  • Glassdoor
Company
About
Leadership
Blog
Careers
Partner Network
Referral Program
Events
Press
Legal & Security
Products
Droplets
Spaces
Kubernetes
Tools & Integrations
One-click Apps
API
Pricing
Documentation
Release Notes
Community
Tutorials
Meetups
Q&A
Write for DOnations
Droplets for Demos
Hatch
Shop Swag
Research Program
Currents Research
Open Source
Support
Contact Support
FAQ
Network Status