Database Service home page
At the top of the database service home page, the status of the database service is displayed below the service name. Next to the status, you can view the following:
Snapshot
When a manual or automatic snapshot is in progress, a snapshot icon appears next to the status. Clicking this icon displays the details of the ongoing snapshot.
Patching
If a higher patch version is available from Tessell, Patch Available appears next to the status. Hover over Patch Available and click Patch Now to view the available versions.
Note: Tessell highly recommends taking a snapshot of the database before patching to prevent data loss.
A Patch Database Engine Version window appears where you can:
Choose a version of the database engine from the dropdown list.
Optionally, edit the number of instances to patch if the service has more than one instance. By default, all instances are patched. An estimated service downtime is displayed for patching.
Select the Patch Database Engine Version check box.
Click Start Patch.
The following steps are performed automatically:
Request is submitted to patch the software for database service instances.
New version of PostgreSQL binaries is installed.
Database service instance(s) are patched.
Service returns to Ready status and Tessell metadata is updated.
For HA services, Tessell follows Standby-First patching with rollover mode to minimize downtime.
Parameter Update
If a new version of the parameter profile is available for the database service, Parameter Update available is displayed. Hover over the parameter update to see which new parameter profiles are available. For more information, see Change Parameter Profile.
Upcoming schedules
Upcoming schedules such as start, stop, or delete are displayed next to the status. Hover over a schedule to view its details, including the scheduled actions.
More info
The more information icon provides a summary of the database service, including the following details:
Cloud details
Cloud
Region
Availability Zone(s)
Subscription
VPC or VNet
Private subnet
Storage details
Storage Provider — Displays the storage type selected as per your cloud provider.
Volume Size — Displays the storage size in GiB.
Max throughput — Displays the maximum throughput value in MiB/s.
IOPS — Displays the IOPS value specified for your storage.
Primary Server and Compute
Server name — Displays the server name where your database is deployed.
Compute shape — Displays the selected compute shape. Click the tooltip next to the shape to view compute shape details.
vCPUs — Displays the number of vCPUs allocated.
Memory — Displays the amount of memory allocated.
Software details
Software version — Displays the version of the database engine selected for your database service.
Parameter Profile — Displays the name of the parameter profile selected. Click the tooltip to view all parameters and their values.
Option Profile — Displays the name of the option profile selected for your database service. Click the tooltip to view all options and their values.
Edition — Displays the edition of the selected database engine for your database service.
Owner
Owner — Displays the username of the owner.
My Role — Displays your role for the database service. The possible values are Owner, Co-owner, or Read-only.
Date created — Displays the date and time when the database service was created.
Running since — Displays the date and time since the database has been up and running.
TRN — Displays the Tessell Resource Name, a globally unique ID that can be used to operate database services through Tessell REST APIs.
Observability
Alert policy — Displays the alert policy selected for the database service.
At the top-right of the database service home page, you see the following options:
Availability Machine
Click to access the Availability Machine home page for the database service.
Dataflix
Click to access the Dataflix home page for the database service.
Start Service
Click to start the database service. This option is available if the database service is stopped.
Stop Service
Click to stop the database service. This option is available if the database service is up and running.
Refresh Data
This option is available only for cloned database services.
The refresh feature enables you to update database clones with the most recent snapshot, eliminating the need to create new database service clones. This feature maintains data consistency and can be initiated either manually or automatically.
To perform cross-region database refreshes, you must first configure the DAP policy in the Availability Machines app. A single source can have multiple clones, and refresh can only happen from source to destination. Refresh between clones is not supported.
Click Refresh Data to refresh the cloned service data.
Select the date to which you wish to refresh from the Recovery Date box.
Note: The calendar shows only the dates that have data available based on the source instance's RPO policy.
Select whether to recover from snapshots or PITR in the Recovery Mode panel.
Available Snapshots displays available snapshots for the selected date.
PITR invokes a clock that allows you to select the exact time to recover.
Optionally, select pre and post scripts from the Custom Scripts panel. To use a custom script, ensure that you have uploaded scripts in the Script Library application under the DB Services app family.
Click Submit to initiate the refresh.
Click the ellipsis icon (︙) for the following actions:
Restore
Restore functionality restores a copy of data from a chosen point in time into a new VM of the same shape as the source. Most configurations are kept unchanged in the restore operation.
Select this option to restore the database service. The available option is out-of-place restore, which restores the database to the selected recovery point in a new VM.
Select the recovery point to which you want the service restored:
Snapshot
Select the snapshot option and click Next. This opens the Dataflix application, where you can view available snapshots with their corresponding timestamps, storage sizes, and number of regions.
Select a snapshot and review its details.
Click Select to Restore.
Choose your database and compute shape for either a new or existing server.
Specify the master username and master password.
Click Restore.
The following steps are performed automatically:
Request is submitted to restore the database service up to the given snapshot time.
Compute instance(s) are created.
Database is configured.
Availability Machine is set up.
First snapshot is triggered.
PITR
Select the PITR option and click Next. This opens the Dataflix application.
Pick a time to restore your service on the Regions and Availability Zones.
Click Select to Restore.
Specify the master username and master password.
Click Restore.
The following steps are performed automatically:
Request is submitted to restore the database service to the given point in time.
Compute instance(s) are created.
Database is configured.
Availability Machine is set up.
First snapshot is triggered.
Maximum Recoverability
Select to restore the database service to the last committed transaction. This option uses WAL (Write-Ahead Log) files from the source VM if they are available and accessible.
Edit Service
Select Edit Service to rename the database service, update the description, enable delete/stop protection, or enable auto minor version update. For more information, see Edit the service.
Resize
Tessell supports resizing of compute and storage for database services.
Note: Tessell highly recommends taking a snapshot of the database before resizing.
Select Resize to update the compute shape or storage.
Compute resize
Compute resize is a downtime operation. For HA database services, this is done in a rollover approach to minimize downtime.
Note: Before resizing compute, ensure that the new shape is available in that particular cloud region and zone.
For multi-instance databases, select the desired instance to modify under MODIFY COMPUTE on the Resize compute page. By default, all instances are selected. The primary and HA instance are modified together and cannot be deselected individually.
Choose the number of vCPUs from the No. of vCPUs dropdown list. The Select compute shape dropdown list updates to show the available shapes for the selected vCPU count.
Choose a compute shape from the Select compute shape dropdown list.
Optionally, choose a parameter profile from the dropdown list.
Select the I understand the consequences, resize the compute check box and click Save.
The following steps are performed automatically:
Request is submitted with new settings.
Databases are stopped.
New settings are applied.
Database is started.
Resize storage
Storage resize is a non-downtime operation. Storage can only be increased; reducing storage is not supported.
Specify Storage, IOPS, and Throughput values under MODIFY STORAGE on the Resize storage page. By default, all instances are selected. The storage value you specify is the total storage needed, that is, existing storage plus any additional storage required.
For multi-instance databases, specify the IOPS and Throughput value for each instance. Storage resizing applies to all instances and cannot be modified per individual instance.
Select the I understand the consequences, resize the storage check box and click Save.
The following steps are performed automatically:
Request is submitted with new settings.
New settings are applied.
Change Parameter Profile
Note: Tessell highly recommends taking a snapshot of the database before changing the parameter profile to prevent data loss.
Using this flow, you can either apply a new parameter profile to the database service, or apply changes from the existing parameter profile.
Select Change Parameter Profile. The Change Parameter Profile window opens.
Choose a new parameter profile from the dropdown list.
Select when to apply the changes:
Apply in maintenance window — Updates the parameter profile in the upcoming scheduled maintenance window.
Apply later — Schedules the update at a convenient time. This creates a custom, one-time maintenance window.
Apply immediately — Applies the changes immediately, regardless of the scheduled maintenance window.
Note: Applying immediately includes any other pending modifications and may lead to service downtime.
Select the I understand the consequences, apply changes immediately check box.
Click Apply.
Delete
Select to delete the service. For more information, see Delete the service.
To use code for operations like Restore, Resize, Refresh Data, and Change Parameter Profile:
Click the Code button in the top-right corner to view the code for the respective operation.
On the left-hand side, view the API, its type, and the payload.
On the right-hand side, view the code in Shell, Python, Go, Java, JavaScript, and PowerShell.
Use the copy or download buttons to save the code.
Click Close to return to the main window.
When you click a database service, the following tabs are displayed on the database service home page: Overview, Monitoring, Logs, Instances, Maintenance Window, Databases, Integrations, Events, Schedules, Sharing, and Settings.
Figure 1: Database Service home page
Last updated
Was this helpful?