TimescaleDB

Advanced failover is very important - it might even be necessary when you have a very complex database setup. When dealing with disasters that can happen in unanticipated events, pre/post scripts can be very helpful to determine how feasible and how true is the alarm that was triggered. Proceeding on a failover after a false positive is a waste of money, resources, and waste of time. ClusterControl has these features and this blog demonstrates how you can take advantage of them dedicated for advanced failover.

ClusterControl offers you a different approach of managing databases which can not be observed and experienced in other platforms. It can be deployed on-prem, on the cloud, or on a containerized type of environment. It can be deployed flexibly and has a massive feature that offers rich and powerful operations that makes it easier to manage your database and without requiring you to create your automated scripts. ClusterControl will handle this for you as shown by this blog. This blog showcases how it is feasible to manage multiple database technologies with ClusterControl.

Data governance defines a set of principles to ensure data quality in a company. It describes the processes, roles, policies or responsibilities, and metrics to ensure accountability and ownership of data assets across the enterprise. This blog discusses the six critical components to successful data governance for better data quality.

In this blog post, we are going to focus on SNMP traps and alerting. SNMP Traps are the most frequently used alert messages sent from a remote SNMP-enabled device (an agent) to a central collector, the “SNMP manager.” In the case of ClusterControl, a trap could be an alert after the critical alarm for a cluster is not 0, indicating something bad is happening.

In this blog series, we are going to showcase a proof-of-concept (PoC) on how to integrate ClusterControl with SNMP protocol. At the end of the blog series, we would ultimately be able to send an SNMP trap to an SNMP manager (Nagios, Zabbix, etc). In this first part, we are going to cover the MIB and SNMP agent.

Managing a very large database incurs huge challenges and fears in case of data loss, disasters, or lack of experience of the database to use. However, knowing the basics that could help you determine beforehand to prepare things and make it efficient is the most important thing to have. This blog covers these things on how to manage a very large database and what are the things you have to know.

In this blog post, we are going to look into the new user management system introduced in ClusterControl 1.8.2, and to see how it is different from the previous ones. Just for clarification, the old user management system will still work side-by-side with the new user authentication and management system until Q1 2022. From now on, all new installations for ClusterControl 1.8.2 and later will be configured with the new user management system.

Configuration check and tuning are an important part of the DBA and SysAdmin routine to ensure a critical system like database and reverse proxies are always relevant and optimal as your workloads grow. Our focus in this blog post is to automate the database configuration check and validation process.

This blog provides a brief guide on how to start with database automation. It will walk you through the main points and essentials of database automation, such as what can be and what should not be automated, and discusses some useful automation tools.

Role-Based Access Control (RBAC) in ClusterControl allows super administrators to provide fine-grained restrictive access based on a role.  This blog guides you in using RBAC, teaching you the differences among available roles and how to use roles and their privileges to achieve a desired level of security.

Hybrid Cloud vs Full Public Cloud dares how organizations and companies have to decide and design the infrastructure to achieve high availability, scalability but with tightened security. In this blog, we showcase how both differ and how you are going to utilize them whenever you engage with these infrastructure solutions for your business requirements.

Object storage in the cloud is inexpensive, reliable and durable, and is a great way of archiving backup data. In this blog, we will share some tips on how to store TimescaleDB backups on AWS S3 and Google Cloud Storage.

If you need to handle time-series data in your current PostgreSQL installation, you should consider enabling TimescaleDB there to manage it in a more performant way. In this blog, we will see how to enable TimescaleDB in an existing PostgreSQL installation both manually and using ClusterControl.

In this blog post, we look deeper into one of the most advanced features offered by ClusterControl called automatic database recovery and failover. ClusterControl is able to recover clusters, nodes and database-related processes to ensure you achieve the best database uptime possible.

PostgreSQL and its underlying platform solutions can help you cut down the high costs associated with an Oracle Database license; all with small to moderate changes. This blog walks you through some of the advantages of migrating from Oracle to PostgreSQL for your SQL database needs.

While setting up a single instance of Timescale on a Docker container is a pretty straight-forward task, deploying a replication cluster to achieve high availability is not. Customizing something from the OS side, or choosing a different OS image altogether makes it even harder. In this blog, we’ll deploy TimescaleDB on Docker and discuss a way to make it easier to configure a replication with ClusterControl using a clean OS image.

In the new time-series database world, TimescaleDB and InfluxDB are two popular options with fundamentally different architectures. One is based off a relational database, PostgreSQL, the other build as a NoSQL engine. In this blog, we’ll give you a short description of those two, and how they stack against each other.

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.