Topology Service is only used to get the topology information at startup and in the background. Recovery If a Local Topology Service dies and is not recoverable, it can be wiped out. All the tablets in VStream (unified stream of events across shards and sharding events) • Support for Point in Time Recovery • Remove python dependency when running the testsuite (tests should be pure Go). • Reduce the time create and restore data backups with Vitess. Vitess uses backups for two purposes: • Provide a point-in-time backup of the data on a tablet. • Bootstrap new tablets in an existing shard. 176 Prerequisites

. . . . . 62 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Point in Time Recovery . . . . . . . . . . . . . . . Time Recovery Point in Time Recovery Supported Databases • MySQL 5.7 #### Believed to work, but untested • MySQL 8.0 Introduction The Point in Time Recovery feature in Vitess enables recovery of data data to a specific point time (timestamp). There can be multiple recovery requests active at the same time. It is possible to recover across sharding actions, i.e. you can recover to a time when there were

. . . . . 93 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Point in Time Recovery . . . . . . . . . . . . . . . Time Recovery Point in Time Recovery Supported Databases • MySQL 5.7 #### Believed to work, but untested • MySQL 8.0 93 Introduction The Point in Time Recovery feature in Vitess enables recovery of of data to a specific point time (timestamp). There can be multiple recovery requests active at the same time. It is possible to recover across sharding actions, i.e. you can recover to a time when there

. . . . . 113 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Point in Time Recovery . . . . . . . . . . . . . . In Time Recovery Point in Time Recovery Supported Databases • MySQL 5.7 Believed to work, but untested • MySQL 8.0 Introduction The Point in Time Recovery feature in Vitess enables recovery of data data to a specific point time (timestamp). There can be multiple recovery requests active at the same time. It is possible to recover across sharding actions, i.e. you can recover to a time when there were

. . . . . 103 Point In Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Point in Time Recovery . . . . . . . . . . . . . . Time Recovery Point in Time Recovery Supported Databases • MySQL 5.7 #### Believed to work, but untested • MySQL 8.0 Introduction The Point in Time Recovery feature in Vitess enables recovery of data data to a specific point time (timestamp). There can be multiple recovery requests active at the same time. It is possible to recover across sharding actions, i.e. you can recover to a time when there were

Point In Time Recovery ### Point in Time Recovery #### Supported Databases - MySQL 5.7 #### Believed to work, but untested - MySQL 8.0 138 #### Introduction The Point in Time Recovery feature in Vitess Vitess enables recovery of data to a specific point time (timestamp). There can be multiple recovery requests active at the same time. It is possible to recover across sharding actions , i.e. you can shards even though at present there are four. Point in Time Recovery leverages two Vitess features: 1. The use of `SNAPSHOT ` keyspaces for recovery of the last backup before a requested specific timestamp

Topology Service is only used to get the topology information at startup and in the background. Recovery If a Local Topology Service dies and is not recoverable, it can be wiped out. All the tablets in great place to interact with other users. {{< /info >}} Short Term • Support for Point in Time Recovery • Improve Documentation • Improve Usability • Support more MySQL Syntax (improve compatibility as replication topologies, including automated failover. It can detect master failure and initiate a recovery in a matter of seconds. For the most part, Vitess is agnostic to the actions of Orchestrator, which

Topology Service is only used to get the topology information at startup and in the background. 56 Recovery If a Local Topology Service dies and is not recoverable, it can be wiped out. All the tablets in place to interact with other users. {{< /info >}} 202 Short Term • Support for Point in Time Recovery • Improve Documentation • Improve Usability • Support more MySQL Syntax (improve compatibility as replication topologies, including automated failover. It can detect master failure and initiate a recovery in a matter of seconds. For the most part, Vitess is agnostic to the actions of Orchestrator, which