TimescaleDB

Managing backup environments can be complex, and, in case of failure, it’s important to reduce downtime and loss of data as much as possible. Full, differential and incremental backups are good options, they also help reduce the disk space usage. There are other important features like backup verification, uploading to remote systems or cloud, and compression, to complete our backup strategy. In this blog, we’ll see how we can use pgBackRest for backing up PostgreSQL and TimescaleDB and how we can manage all of these features from the same system.

TimescaleDB uses a stream of write-ahead log (WAL) records to keep the standby databases synchronized. In this blog, we’ll review some concepts related to Streaming Replication and how ClusterControl can help us configure it in an easy way.

How do you scale TimescaleDB? How do you convert a single TimescaleDB instance to cluster with no downtime? How does the application know which database node to access? This blog post provides an overview of how to use ClusterControl to scale your time-series data with minimal effort.

Failover is the process of moving to a healthy standby component, during a failure or maintenance event. The quicker it can be done, the faster you can be back online. If you’re looking at minimizing downtime and meet your SLAs through an automated approach for TimescaleDB, then this blog is for you.

Doing a performance monitoring in TimescaleDB is always a challenging task, especially for a very huge time-series data. ClusterControl offers a way to help a DBA or a developer to make things feasible and productive with the aid of the different features integrated within ClusterControl. Check out this blog as we showcases what are these and how you can leverage ClusterControl to monitor your TimescaleDB cluster.

Managing backup environments can be complex, and there are a number of options to consider - full, differential, incremental, point in time recovery, automatic restores for backup verification, uploading to remote systems or cloud, and so on. So how can we backup TimescaleDB? In this blog, we’ll see how ClusterControl can help us implement our backup management strategy for TimescaleDB.

TimescaleDB is based on PostgreSQL, and therefore, supports streaming replication as the primary method of replication. However, PostgreSQL does not come with automatic failover. This can be a problem in a high availability production environment, as manual failover implies prolonged downtime.

The good news is that failover in TimescaleDB can be completely automated in ClusterControl 1.7.2. This blog shows us how to deploy such a setup.

Included in the 1.7.2 release of ClusterControl we are proud to announce an expansion of the databases we support to include TimescaleDB, a revolutionary new time-series that leverages the stability, maturity and power of PostgreSQL.

ClusterControl 1.7.2 includes support for TimescaleDB, MySQL 8.0 and Maxscale 2.2 as well as improved support for PostgreSQL monitoring & backups. It also launches two new features, CC Spotlight (a new search tool) and CMON HA (distributed fault-tolerant controllers).

Time-series data is becoming more and more present, as we capture and analyze data at a faster rate. This increases the demand for complex queries and scalable database solutions. This blog provides a high-level overview of the new database system “TimescaleDB”, and a quick hands-on to get you going.