RumataDatabase operations and recovery controls
Understand database sleep, capacity, access, backup, and recovery before applying a change.
Step-by-step guidance.
Before you start
- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.
Database Operations
Open System Explorer → Database → Operations. The capacity and idle-hibernation controls also appear in the extended Overview.
| Control | What it does |
|---|---|
| About Database operations / About Capacity & recovery | Open an explanation of the panel and the meaning of its measurements. |
| Idle hibernation | Open the sleep-timer settings for an on-demand database. These settings are saved separately from capacity. |
| Manage capacity | Review allocated storage, actual data size, and your plan maximum before applying resources. |
| Manage access | Open access management for the database resource. |
| Status and recovery indicators | Show readiness, whether writes are allowed, plan retention, and verified recovery availability. Waiting or unavailable information is not a measured zero. |
Database idle hibernation dialog
A sleeping database wakes automatically on the next connection. This sleep timer is different from your development machine’s idle timer.
| Control | What it does |
|---|---|
| Quick sleep timer choices | Select a preset duration within the account’s allowed range. The default is marked; available choices depend on the plan. |
| Days / Hours / Minutes | Enter a custom whole-minute duration. Read the minimum and maximum shown in the dialog. |
| Database will sleep after | Preview the total duration you are about to save. |
| Save sleep timer | Save a valid changed duration. Disabled when the value is unchanged, invalid, unavailable, or already being saved. |
| Cancel / Close | Leave without applying the pending duration. |
Update hosted database capacity dialog
Choose the total usable storage you need. Enter the full amount, not just the increase. You can increase capacity but cannot shrink it here.
| Control | What it does |
|---|---|
| RAM & compute / Storage | Choose whether to adjust compute size or usable storage; they consume separate allowances. |
| Database RAM / Apply RAM size | Review the displayed consumption multiplier and estimated remaining running hours, then apply the selected size. A change may restart the database and briefly disconnect queries. |
| New database capacity number / slider | Choose a whole-MiB value between the current allocation and plan maximum. A slider appears only when capacity can be increased. |
| Increase capacity to … | Request the selected larger total capacity. Expansion may wait for platform storage and continue automatically. |
| Apply current plan resources | Reapply the plan’s CPU, memory, and connection limits even when storage is already at its maximum. |
| Switch database to always on | Apply always-on operation when a plan upgrade makes it available. The database wakes if necessary and stays running. |
| Switch to always on and increase to … | Apply both the available always-on entitlement and your larger storage selection. |
| Close | Dismiss the dialog without requesting a capacity change. |
Export current schema and data
This factory’s SQL export is separate from CSV query results, diagram JSON and point-in-time recovery.
| Control | What it does |
|---|---|
| Download SQL export | Start a compressed .sql.gz export of the factory schema and current rows. Keep the page open until it finishes. The database must be ready; compressed download bytes consume download allowance. |
| Cancel export | Abort the in-progress export. A partial download is not a completed backup. |
| Read-only export period | Read the displayed recovery-access period after paid subscription access ends. The standard notice describes seven days; scheduling cancellation alone does not start it. Data and backups can become eligible for permanent deletion afterward. |
PostgreSQL extensions
Extensions are shared by factories using the project’s database. Check dependent applications before changing them.
| Control | What it does |
|---|---|
| Enable / Disable extension | Request the selected extension change with project-write permission. Wait for the asynchronous state to finish; a submitted request is not proof of completion. |
| Extension status / error / Docs | Inspect the current state, any error and the extension’s documentation before using it or retrying. |
Data protection and recovery
Recovery replaces the current database with its state at a selected time. Changes after that time will be discarded. Review the account scope and selected time before starting.
| Control | What it does |
|---|---|
| Create backup | Start an on-demand backup while the database remains online. Disabled until the database is ready or while another backup/recovery operation is active. |
| Recover database | Open the recovery form. Available only with a verified recovery window and no active operation. |
| Recovery point / date-time picker | Choose a time inside the displayed verified window. Dates use the timezone named on the screen. |
| Confirmation | Type RESTORE exactly to acknowledge that later changes will be discarded. |
| Start recovery | Start preparing and validating a replacement database. Connections switch after validation; the old database is then removed. The button stays disabled until the time and confirmation are valid. |
| Cancel / Close | Dismiss the form without initiating recovery. |
| Operation history | Follow pending, running, completed, or failed operations. This is a status list rather than another action. |