Databases

Managed databases explained

A managed database gives you a database engine that Gewape Cloud runs, patches, monitors and backs up. You look after your data and your queries; we look after the server, the operating system, and the engine underneath. You manage these under Databases in the console. Why use one Running a database well means installing the engine, tuning it, keeping it patched, and setting up reliable backups. A managed database does all of that, so you get a ready endpoint to connect to and can focus on your application. You choose the engine, the version, the size, and the storage; we handle the rest. Managed or self-run? - Managed (this): least maintenance. Good for almost everyone. Backups, patching and monitoring are built in. - Self-run: install an engine yourself on a Cloud Server with an attached volume. Full control, but every bit of maintenance is yours. Choose this only when you need something the managed option does not offer. The pieces - An instance is the running database server, with its engine, size, storage and a connection endpoint. - Databases and users live inside an instance. - Backups are saved copies you can restore from. How to - Create a managed database - Back up and restore a database - Trouble connecting? Cannot connect to a managed database

Create a managed database

A managed database gives you an engine that Gewape Cloud runs and backs up. This walks through creating one. Create the instance 1. Open Databases and start a new instance. 2. Fill in: - Name: for example app-db. - Datastore (engine and version): choose the engine, such as MySQL or PostgreSQL, and its version. - Flavor (Server Plan): the size of the database host. g1.small or g1.medium suits a small app; a busy database wants more memory. - Volume size (GiB): how much storage the data gets. You can grow this later. - Network: the private network the database sits on. Keep it on the same network as the app that will use it. - Initial database and user (optional): create a database name and a user with a password so your app has something to connect to immediately. 3. Create it. It provisions in a few minutes and then shows a connection endpoint. Connect your app Point your application at the instance's endpoint, port, and the user you created. Make sure the app can reach the database port through your security rules. If it will not connect, see Cannot connect to a managed database. Turn on backups for anything you care about. See Back up and restore a database.

Back up and restore a managed database

A managed database can back itself up so you can recover from a mistake or a failure. This is the most important thing to set up on any database that holds real data. Take a backup 1. Open your instance under Databases. 2. Choose the backup action and give it a Name. 3. Create it. You can take one on demand before a risky change. Schedule automatic backups In the instance's backup settings, turn on a schedule (for example daily) and set how many days of backups to keep. Automatic backups run quietly and expire on the schedule you set. Restore Restoring creates a new database instance from a backup rather than overwriting the current one. This is deliberate and safe: 1. Choose a backup and restore it to a new instance. 2. Check the restored copy has what you expect. 3. Point your application at whichever instance you want to keep, then remove the other. Backups use storage, so keep enough history to undo the mistakes you might realistically need to (a week or two is common) and let older ones expire. If your app cannot reach the restored instance, see Cannot connect to a managed database.