Best Practice for backing-up local database

[ts678]

@kenkendk

In the past, there has been complaints that the recreate database was really slow, and in some cases failed, requiring the use of the recovery tool to get data out.

I haven’t heard of RecoveryTool use in a really long time, but not all are reported.

More common is the slow or failed path, then it’s a fight to get back into business.

I use “business” for all users’ routines, but actual businesses may prefer to spend resources to reduce risk of downtime (they should have multiple backups though).

Personal backups might have a different tradeoff about predictability of recoveries.

@kenkendk

Happily corrected, but I do not believe any of these concerns are valid anymore.

In addition to that posted situation, there’s my own recent situation where 2.1.0.107 Canary made a mess that took a long time to find a working path to a DB recovery.

Granted, Canary is a test release, but some of these same bugs landed in the Beta and first 2.1.0.4 Stable release, leading to fast 2.1.0.5 Stable and low broad impact.

Database Restore Takes Over 5 Days/Looking for Alternatives hasn’t concluded yet.

recreate database failing

is another Canary case that hasn’t even been started on. Concerns remain valid.

Situation seems to be generally improving (ignoring Canary risk), but isn’t solved.