Managing your Database on Galaxy

This document serves as a comprehensive guide for advanced users to navigate and utilize the full suite of features available for supported databases within the Galaxy Dashboard. It details the functionality of the database dashboard, from the initial overview to advanced monitoring and critical settings.

Creating a New Database

To create a new database, click the Create Database button on the main dashboard. The process typically involves:

1. Selecting the Database Engine: Choose between one of the supported databases.
2. Naming the Cluster: Provide a unique name for your instance.
3. Selecting a Region: Choose the geographical location for deployment.
4. Selecting a Plan/Size: Choose the appropriate resource allocation (RAM, CPU, Storage) based on your application's needs.
5. Configuration: Specify the database version and deployment type (e.g., Standalone or ReplicaSet).

The Databases Dashboard Overview

The main Databases view provides a centralized location for monitoring and managing all your database instances. This screen offers a quick summary of your provisioned resources and their current status.

Database List and Status

The primary table lists all your database clusters, providing essential information at a glance.

You can use the built-in filters to quickly locate databases by Status, Database Type, or search by Cluster name.

Database Instance Details

Clicking on a database with a Running status will navigate you to its dedicated management interface, which is structured into several key sections accessible via the sidebar: Overview, Metrics, Logs, and Settings.

Overview

The Overview section provides the core information and credentials required to connect to your database.

Instance Information

This area summarizes the database's resource allocation and configuration:

• Status: Current operational state.
• Database: Engine and version.
• Region: Deployment geographical location.
• Type: Deployment model.
• Containers: Number of containers running the instance.
• Storage: Total maximum allocated disk space.
• Instance Size: The chosen plan tier.
• Instance Details: Allocated RAM and CPU.

Credentials

This section provides the necessary information for external connection. It is crucial to handle these credentials securely.

• Username: The administrative username (e.g., admin for MongoDB, postgres for PostgreSQL, default for Redis).
• Password: The administrative password.
• Connection String: The full URI required to connect to the database from your application or a management tool.
• • MongoDB Example: mongodb://<username>:<password>@<host>/admin
  • PostgreSQL Example: postgres://<username>:<password>@<host>/postgres
  • Redis Example: redis://username:<password>@<host>/0

Metrics

The Metrics section offers deep, real-time insights into your database's performance and resource consumption. Monitoring these metrics is essential for capacity planning and troubleshooting performance bottlenecks.

Logs

The Logs section provides direct access to the database engine's output, which is invaluable for debugging, auditing, and understanding the internal state of the instance.

• Functionality: View time-stamped log entries, search logs for specific events or errors, and enable Live Mode for real-time log tailing.
• Usage: Look for error messages to diagnose issues, or track specific operations and connections.

Settings

The Settings section is where you manage critical configurations for your database instance.

Backups

This tab details your database's backup schedule and history.

• Backup Schedule: Displays the automated backup time (e.g., 05:00 UTC) and the default Retention Period (e.g., 4 days).
• Backup History: A table listing past backups with their Status (Completed, Failed, Deletion), Type (Scheduled, Manual), Size, Started At, and Duration.
• Actions:
• • Create Manual Backup: Initiate an immediate, on-demand backup.
  • Edit Schedule: Modify the automated backup time and retention policy.
• Extended Retention: For retention periods longer than the default, contact Galaxy Support.

Danger Zone

This area contains critical, irreversible actions. Proceed with extreme caution.

• Delete Database: This action will permanently remove the database and all of its data.
• • Pre-deletion Backup: A backup will be automatically created with 30-day retention before the deletion process begins.
  • Notifications: Email notifications will be sent when the deletion process starts and completes.

By following this guide, you can effectively manage and monitor your database instances on the Galaxy platform, ensuring optimal performance and reliability for your applications.

Updated on: 19/10/2025