Start, stop or reboot a MariaDB database in Blesta
As the hosting operator, you choose which PD AWS MariaDB power controls your customers can use. The client-area steps below cover a temporary database interruption. These controls operate on the RDS database linked to the service; stopping the database does not cancel the billing service or retire the resource.
Prepare for the interruption
Check the intended power controls in the offering’s module settings and the actions available on the affected service. Confirm the database and AWS region. Coordinate with your customer or application owner: stopping or rebooting interrupts active connections. Your customer then uses the controls available on that service’s Overview. If a control is missing, check the offering and current database state before treating it as a failed action.
Customer steps: request one action
- Open the service’s Overview.
- Choose Stop for a running database, Start for a stopped one, or Reboot for a restart.
- Read and confirm the interruption message where one is shown.
- Follow the request under Activity.
- Wait for the resulting database state before reconnecting the application or asking for another action.
Work can be queued while AWS completes an earlier operation. A Done entry can mean AWS accepted the operation, rather than that the database has already reached its final state. Repeated clicks are not a useful way to shorten a provider transition.
Understand temporary stopping
Amazon RDS automatically restarts a database after seven consecutive stopped days. Stopping is not permanent retirement and should not be treated as cancelling all provider charges. Keep required recovery points independently of a temporary stop.
Check an unfinished power operation
As the hosting operator, compare the recorded Activity result with the database state visible in your AWS account. Record whether the request is queued, failed or accepted while AWS is still changing the database state. Follow an existing transition before requesting another action. If AWS reports a specific refusal, review that requirement with your AWS administrator.
See the PD AWS MariaDB Blesta guide for related tasks, or explore PD AWS MariaDB.
