{"id":2530,"date":"2022-04-22T14:32:07","date_gmt":"2022-04-22T11:32:07","guid":{"rendered":"https:\/\/upcloud.com\/global\/us\/resources\/docs\/managed-databases\/"},"modified":"2022-04-22T14:32:07","modified_gmt":"2022-04-22T11:32:07","slug":"managed-databases","status":"publish","type":"documentation","link":"https:\/\/upcloud.com\/global\/resources\/docs\/managed-databases\/","title":{"rendered":"Managed Databases"},"content":{"rendered":"\n

UpCloud Managed Database<\/a> is a database-as-a-service offering a carefree option for running well-known open-source databases in the cloud. It is deployable via the users’ UpCloud Control Panel with configuration options including the choice of database management systems, clustered or single-node systems, and a number of resource plans. Managed Databases are available in every UpCloud data centre location.<\/p>\n\n\n\n

Available databases<\/h2>\n\n\n\n

Currently, available database systems include the following.<\/p>\n\n\n\n

MySQL<\/h3>\n\n\n\n

MySQL is the world\u2019s most popular enterprise-grade open-source relational database management system. Managed Databases utilise MySQL Community Edition<\/a>, supported by a huge and active community of open-source developers.<\/p>\n\n\n\n

Customisable database properties<\/strong><\/p>\n\n\n\n

The following MySQL database properties can be set by the user via the UpCloud API<\/a>.<\/p>\n\n\n\n

admin_password<\/td>innodb_lock_wait_timeout<\/td>net_read_timeout<\/td><\/tr>
admin_username<\/td>innodb_log_buffer_size<\/td>net_write_timeout<\/td><\/tr>
automatic_utility_network_ip_filter<\/td>innodb_online_alter_log_max_size<\/td>public_access<\/td><\/tr>
backup_hour<\/td>innodb_print_all_deadlocks<\/td>slow_query_log<\/td><\/tr>
backup_minute<\/td>innodb_rollback_on_timeout<\/td>sort_buffer_size<\/td><\/tr>
binlog_retention_period<\/td>interactive_timeout<\/td>sql_mode<\/td><\/tr>
connect_timeout<\/td>internal_tmp_mem_storage_engine<\/td>sql_require_primary_key<\/td><\/tr>
default_time_zone<\/td>ip_filter<\/td>tmp_table_size<\/td><\/tr>
group_concat_max_len<\/td>long_query_time<\/td>version<\/td><\/tr>
information_schema_stats_expiry<\/td>max_allowed_packet<\/td>wait_timeout<\/td><\/tr>
innodb_ft_min_token_size<\/td>max_heap_table_size<\/td><\/td><\/tr>
innodb_ft_server_stopword_table<\/td>migration<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

PostgreSQL<\/h3>\n\n\n\n

PostgreSQL<\/a>, also known as Postgres, is a free and open-source relational database management system emphasizing extensibility and SQL compliance.<\/p>\n\n\n\n

Customisable database properties<\/strong><\/p>\n\n\n\n

The following PostgreSQL database properties can be set by the user via the UpCloud API<\/a>.<\/p>\n\n\n\n

admin_password<\/td>ip_filter<\/td>pg_partman_bgw.role<\/td><\/tr>
admin_username<\/td>jit<\/td>pg_read_replica<\/td><\/tr>
automatic_utility_network_ip_filter<\/td>log_autovacuum_min_duration<\/td>pg_service_to_fork_from<\/td><\/tr>
autovacuum_analyze_scale_factor<\/td>log_error_verbosity<\/td>pg_stat_statements.track<\/td><\/tr>
autovacuum_analyze_threshold<\/td>log_line_prefix<\/td>pgbouncer<\/td><\/tr>
autovacuum_freeze_max_age<\/td>log_min_duration_statement<\/td>pglookout<\/td><\/tr>
autovacuum_max_workers<\/td>max_files_per_process<\/td>public_access<\/td><\/tr>
autovacuum_naptime<\/td>max_locks_per_transaction<\/td>shared_buffers_percentage<\/td><\/tr>
autovacuum_vacuum_cost_delay<\/td>max_logical_replication_workers<\/td>synchronous_replication<\/td><\/tr>
autovacuum_vacuum_cost_limit<\/td>max_parallel_workers<\/td>temp_file_limit<\/td><\/tr>
autovacuum_vacuum_scale_factor<\/td>max_parallel_workers_per_gather<\/td>timescaledb<\/td><\/tr>
autovacuum_vacuum_threshold<\/td>max_pred_locks_per_transaction<\/td>timezone<\/td><\/tr>
backup_hour<\/td>max_prepared_transactions<\/td>track_activity_query_size<\/td><\/tr>
backup_minute<\/td>max_replication_slots<\/td>track_commit_timestamp<\/td><\/tr>
bgwriter_delay<\/td>max_slot_wal_keep_size<\/td>track_functions<\/td><\/tr>
bgwriter_flush_after<\/td>max_stack_depth<\/td>track_io_timing<\/td><\/tr>
bgwriter_lru_maxpages<\/td>max_standby_archive_delay<\/td>variant<\/td><\/tr>
bgwriter_lru_multiplier<\/td>max_standby_streaming_delay<\/td>version<\/td><\/tr>
deadlock_timeout<\/td>max_wal_senders<\/td>wal_sender_timeout<\/td><\/tr>
default_toast_compression<\/td>max_worker_processes<\/td>wal_writer_delay<\/td><\/tr>
enable_ipv6<\/td>migration<\/td>work_mem<\/td><\/tr>
idle_in_transaction_session_timeout<\/td>pg_partman_bgw.interval<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Supported extensions<\/strong><\/p>\n\n\n\n

Managed Database using PostgreSQL supports the following extensions.<\/p>\n\n\n\n

address_standardizer<\/td>hstore<\/td>pgrouting<\/td>postgres_fdw<\/td><\/tr>
address_standardizer_data_us<\/td>intagg<\/td>pgrowlocks<\/td>promscale<\/td><\/tr>
aiven_extras<\/td>intarray<\/td>pgstattuple<\/td>rum<\/td><\/tr>
bloom<\/td>isn<\/td>plcoffee<\/td>sslinfo<\/td><\/tr>
btree_gin<\/td>ltree<\/td>plls<\/td>tablefunc<\/td><\/tr>
btree_gist<\/td>pg_buffercache<\/td>plperl<\/td>timescale_analytics<\/td><\/tr>
chkpass<\/td>pg_cron<\/td>plpgsql<\/td>timescaledb<\/td><\/tr>
citext<\/td>pg_partman<\/td>plv8<\/td>tsearch2<\/td><\/tr>
cube<\/td>pg_prometheus<\/td>postgis<\/td>tsm_system_rows<\/td><\/tr>
dblink<\/td>pg_repack<\/td>postgis_legacy<\/td>unaccent<\/td><\/tr>
dict_int<\/td>pg_similarity<\/td>postgis_raster<\/td>unit<\/td><\/tr>
earthdistance<\/td>pg_stat_statements<\/td>postgis_sfcgal<\/td>uuid-ossp<\/td><\/tr>
fuzzystrmatch<\/td>pg_trgm<\/td>postgis_tiger_geocoder<\/td><\/td><\/tr>
hll<\/td>pgcrypto<\/td>postgis_topology<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Redis<\/h3>\n\n\n\n

Redis<\/a> is an open-source, in-memory data store commonly used as a database, cache, streaming engine, or message broker. It offers sub-millisecond response times, enabling millions of requests per second for real-time applications.<\/p>\n\n\n\n

OpenSearch<\/h3>\n\n\n\n

OpenSearch<\/a> is an open-source distributed search and analytics suite. Powered by the Apache Lucene search library, OpenSearch offers a vendor-agnostic toolset you can use to build secure, high-performance, cost-efficient applications, from real-time application monitoring to website search functionality.<\/p>\n\n\n\n

Database plans<\/h2>\n\n\n\n

Managed Databases are offered with 2 and 3-node clustered solutions as well as single-node unclustered options. The nodes can be configured with the required resources by selecting from the available plans. Each plan includes a set number of CPU cores, system memory, storage and backups. The Managed Database plans are priced according to the number of nodes and the resources allocated to each node.<\/p>\n\n\n\n

Database clusters are billed hourly according to the selected configuration plan until the instance is deleted, including while stopped.<\/p>\n\n\n\n

1 node – MySQL & PostgreSQL<\/h3>\n\n\n\n
Memory<\/th>CPU cores<\/strong><\/th>Storage<\/strong><\/th>Backups<\/strong><\/th>Price<\/th><\/th><\/tr><\/thead>
2 GB<\/td>1<\/td>25 GB<\/td>24 hours<\/td>\u20ac0.0417\/h<\/td>\u20ac30\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>50 GB<\/td>24 hours<\/td>\u20ac0.0833\/h<\/td>\u20ac60\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>100 GB<\/td>24 hours<\/td>\u20ac0.1042\/h<\/td>\u20ac75\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

2 nodes<\/strong> – MySQL & PostgreSQL<\/h3>\n\n\n\n
Memory<\/strong><\/th>CPU cores<\/strong><\/th>Storage<\/strong><\/th>Backups<\/strong><\/th>Price<\/th><\/th><\/tr><\/thead>
4 GB<\/td>2<\/td>50 GB<\/td>7 days<\/td>\u20ac0.1389\/h<\/td>\u20ac100\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>100 GB<\/td>7 days<\/td>\u20ac0.2083\/h<\/td>\u20ac150\/mo<\/td><\/tr>
8 GB<\/td>4<\/td>50 GB<\/td>7 days<\/td>\u20ac0.2431\/h<\/td>\u20ac175\/mo<\/td><\/tr>
8 GB<\/td>4<\/td>100 GB<\/td>7 days<\/td>\u20ac0.2778\/h<\/td>\u20ac200\/mo<\/td><\/tr>
16 GB<\/td>6<\/td>100 GB<\/td>7 days<\/td>\u20ac0.5556\/h<\/td>\u20ac400\/mo<\/td><\/tr>
16 GB<\/td>6<\/td>250 GB<\/td>7 days<\/td>\u20ac0.7778\/h<\/td>\u20ac560\/mo<\/td><\/tr>
32 GB<\/td>8<\/td>100 GB<\/td>7 days<\/td>\u20ac1.0417\/h<\/td>\u20ac750\/mo<\/td><\/tr>
32 GB<\/td>8<\/td>250 GB<\/td>7 days<\/td>\u20ac1.1111\/h<\/td>\u20ac800\/mo<\/td><\/tr>
32 GB<\/td>8<\/td>500 GB<\/td>7 days<\/td>\u20ac1.2222\/h<\/td>\u20ac880\/mo<\/td><\/tr>
64 GB<\/td>16<\/td>1 TB<\/td>7 days<\/td>\u20ac2.2222\/h<\/td>\u20ac1600\/mo<\/td><\/tr>
64 GB<\/td>16<\/td>1.5 TB<\/td>7 days<\/td>\u20ac2.5000\/h<\/td>\u20ac1800\/mo<\/td><\/tr>
128 GB<\/td>20<\/td>2 TB<\/td>7 days<\/td>\u20ac3.8889\/h<\/td>\u20ac2800\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

3 nodes<\/strong> – MySQL & PostgreSQL<\/h3>\n\n\n\n
Memory<\/strong><\/th>CPU cores<\/strong><\/th>Backups<\/strong><\/th>Price<\/th><\/th><\/tr><\/thead>
2 GB<\/td>1<\/td>2 days<\/td>\u20ac0.069\/h<\/td>\u20ac50\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>2 days<\/td>\u20ac0.125\/h<\/td>\u20ac90\/mo<\/td><\/tr>
8 GB<\/td>2<\/td>2 days<\/td>\u20ac0.153\/h<\/td>\u20ac110\/mo<\/td><\/tr>
14 GB<\/td>2<\/td>2 days<\/td>\u20ac0.222\/h<\/td>\u20ac160\/mo<\/td><\/tr>
28 GB<\/td>4<\/td>2 days<\/td>\u20ac0.417\/h<\/td>\u20ac300\/mo<\/td><\/tr>
56 GB<\/td>8<\/td>2 days<\/td>\u20ac0.806\/h<\/td>\u20ac580\/mo<\/td><\/tr>
112 GB<\/td>16<\/td>2 days<\/td>\u20ac1.611\/h<\/td>\u20ac1160\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

1 node – Redis<\/h3>\n\n\n\n
Memory<\/strong><\/th>CPU cores<\/strong><\/th>Storage<\/strong><\/th>Backups<\/strong><\/th>Price<\/th><\/th><\/tr><\/thead>
4 GB<\/td>2<\/td>100 GB<\/td>14 days<\/td>\u20ac0.2431\/h<\/td>\u20ac175\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>200 GB<\/td>14 days<\/td>\u20ac0.3125\/h<\/td>\u20ac225\/mo<\/td><\/tr>
8 GB<\/td>4<\/td>100 GB<\/td>14 days<\/td>\u20ac0.3889\/h<\/td>\u20ac280\/mo<\/td><\/tr>
8 GB<\/td>4<\/td>200 GB<\/td>14 days<\/td>\u20ac0.4514\/h<\/td>\u20ac325\/mo<\/td><\/tr>
16 GB<\/td>6<\/td>200 GB<\/td>14 days<\/td>\u20ac0.8333\/h<\/td>\u20ac600\/mo<\/td><\/tr>
16 GB<\/td>6<\/td>500 GB<\/td>14 days<\/td>\u20ac0.9028\/h<\/td>\u20ac650\/mo<\/td><\/tr>
32 GB<\/td>8<\/td>200 GB<\/td>14 days<\/td>\u20ac1.5556\/h<\/td>\u20ac1120\/mo<\/td><\/tr>
32 GB<\/td>8<\/td>500 GB<\/td>14 days<\/td>\u20ac1.6944\/h<\/td>\u20ac1220\/mo<\/td><\/tr>
32 GB<\/td>8<\/td>1 TB<\/td>14 days<\/td>\u20ac1.9722\/h<\/td>\u20ac1420\/mo<\/td><\/tr>
64 GB<\/td>16<\/td>1 TB<\/td>14 days<\/td>\u20ac3.1111\/h<\/td>\u20ac2240\/mo<\/td><\/tr>
64 GB<\/td>16<\/td>2 TB<\/td>14 days<\/td>\u20ac3.6667\/h<\/td>\u20ac2640\/mo<\/td><\/tr>
128 GB<\/td>20<\/td>2 TB<\/td>14 days<\/td>\u20ac5.5278\/h<\/td>\u20ac3980\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

2 nodes – Redis<\/h3>\n\n\n\n
Memory<\/strong><\/th>CPU cores<\/strong><\/th>Backups<\/strong><\/th>Price<\/th><\/th><\/tr><\/thead>
2 GB<\/td>1<\/td>3 days<\/td>\u20ac0.139\/h<\/td>\u20ac100\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>3 days<\/td>\u20ac0.236\/h<\/td>\u20ac170\/mo<\/td><\/tr>
8 GB<\/td>2<\/td>3 days<\/td>\u20ac0.319\/h<\/td>\u20ac230\/mo<\/td><\/tr>
14 GB<\/td>2<\/td>3 days<\/td>\u20ac0.431\/h<\/td>\u20ac310\/mo<\/td><\/tr>
28 GB<\/td>4<\/td>3 days<\/td>\u20ac0.819\/h<\/td>\u20ac590\/mo<\/td><\/tr>
56 GB<\/td>8<\/td>3 days<\/td>\u20ac1.611\/h<\/td>\u20ac1160\/mo<\/td><\/tr>
112 GB<\/td>16<\/td>3 days<\/td>\u20ac3.194\/h<\/td>\u20ac2300\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

3 nodes – Redis<\/h3>\n\n\n\n
Memory<\/strong><\/th>CPU cores<\/strong><\/th>Backups<\/strong><\/th>Price<\/th><\/th><\/tr><\/thead>
2 GB<\/td>1<\/td>7 days<\/td>\u20ac0.208\/h<\/td>\u20ac150\/mo<\/td><\/tr>
4 GB<\/td>2<\/td>7 days<\/td>\u20ac0.361\/h<\/td>\u20ac260\/mo<\/td><\/tr>
8 GB<\/td>2<\/td>7 days<\/td>\u20ac0.472\/h<\/td>\u20ac340\/mo<\/td><\/tr>
14 GB<\/td>2<\/td>7 days<\/td>\u20ac0.653\/h<\/td>\u20ac470\/mo<\/td><\/tr>
28 GB<\/td>4<\/td>7 days<\/td>\u20ac1.250\/h<\/td>\u20ac900\/mo<\/td><\/tr>
56 GB<\/td>8<\/td>7 days<\/td>\u20ac2.444\/h<\/td>\u20ac1760\/mo<\/td><\/tr>
112 GB<\/td>16<\/td>7 days<\/td>\u20ac4.833\/h<\/td>\u20ac3480\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

1-day backups – OpenSearch<\/h3>\n\n\n\n
Nodes<\/th>Memory<\/th>Cores<\/th>Backup days<\/th>Storage<\/th>Price<\/th><\/th><\/tr><\/thead>
1<\/td>4 GB<\/td>2<\/td>1<\/td>80<\/td> \u20ac0.1389\/h<\/td>\u20ac100\/mo<\/td><\/tr>
1<\/td>8 GB<\/td>2<\/td>1<\/td>160<\/td>\u20ac0.2083\/h<\/td>\u20ac150\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

3-day backups – OpenSearch<\/h3>\n\n\n\n
Nodes<\/th>Memory<\/th>Cores<\/th>Backup days<\/th>Storage<\/th>Price<\/th><\/th><\/tr><\/thead>
3<\/td>4 GB<\/td>2<\/td>3<\/td>120<\/td> \u20ac0.3889\/h<\/td>\u20ac280\/mo<\/td><\/tr>
3<\/td>8 GB<\/td>2<\/td>3<\/td>240<\/td> \u20ac0.5556\/h<\/td>\u20ac400\/mo<\/td><\/tr>
3<\/td>14 GB<\/td>2<\/td>3<\/td>420<\/td> \u20ac0.8056\/h<\/td>\u20ac580\/mo<\/td><\/tr>
6<\/td>14 GB<\/td>2<\/td>3<\/td>840<\/td> \u20ac1.6111\/h<\/td>\u20ac1160\/mo<\/td><\/tr>
9<\/td>14 GB<\/td>2<\/td>3<\/td>1260<\/td> \u20ac2.4028\/h<\/td>\u20ac1730\/mo<\/td><\/tr>
12<\/td>14 GB<\/td>2<\/td>3<\/td>1680<\/td> \u20ac3.2083\/h<\/td>\u20ac2310\/mo<\/td><\/tr>
15<\/td>14 GB<\/td>2<\/td>3<\/td>2100<\/td> \u20ac4.0139\/h<\/td>\u20ac2890\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

7-day backups – OpenSearch<\/h3>\n\n\n\n
Nodes<\/th>Memory<\/th>Cores<\/th>Backup days<\/th>Storage<\/th>Price<\/th><\/th><\/tr><\/thead>
3<\/td>4 GB<\/td>2<\/td>7<\/td>600<\/td> \u20ac0.8056\/h<\/td>\u20ac580\/mo<\/td><\/tr>
3<\/td>8 GB<\/td>2<\/td>7<\/td>1200<\/td> \u20ac1.3889\/h<\/td>\u20ac1000\/mo<\/td><\/tr>
3<\/td>14 GB<\/td>2<\/td>7<\/td>2100<\/td> \u20ac2.2500\/h<\/td>\u20ac1620\/mo<\/td><\/tr>
6<\/td>14 GB<\/td>2<\/td>7<\/td>4200<\/td> \u20ac4.5000\/h<\/td>\u20ac3240\/mo<\/td><\/tr>
9<\/td>14 GB<\/td>2<\/td>7<\/td>6300<\/td> \u20ac6.7500\/h<\/td>\u20ac4860\/mo<\/td><\/tr>
12<\/td>14 GB<\/td>2<\/td>7<\/td>8400<\/td> \u20ac9.0000\/h<\/td>\u20ac6480\/mo<\/td><\/tr>
15<\/td>14 GB<\/td>2<\/td>7<\/td>10500<\/td> \u20ac11.2500\/h<\/td>\u20ac8100\/mo<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Note that the database management system and host operating system use a small portion of the allocated storage capacity, typically 1 – 2 GB.<\/p>\n\n\n\n

Database features<\/h2>\n\n\n\n

High availability<\/h3>\n\n\n\n

In clustered database deployments, nodes are created on physically separated backend hosts to ensure redundancy in case of hardware failure.<\/p>\n\n\n\n

In normal operation, the DNS entry of the database points to a primary node. One of the replicas will be promoted automatically in case of a primary failure.<\/p>\n\n\n\n

Scalability<\/h3>\n\n\n\n

Users are able to scale their Managed Database services both vertically and horizontally by increasing or decreasing the number of nodes in the cluster or the resources allocated to each node.<\/p>\n\n\n\n

Changes to the Managed Database configuration are handled seamlessly in the background with minimal interruption to the services.<\/p>\n\n\n\n

Connectivity<\/h3>\n\n\n\n

Managed Databases can be reached via the user\u2019s private UpCloud Utility network or optionally through the public network connection. A private connection is enabled by default. This makes the database accessible for all the user\u2019s Cloud Servers within the same data centre as the Managed Database.<\/p>\n\n\n\n

At the configuration settings, users can set a preferred hostname. The hostname is used to automatically create DNS entries using a unique subdomain name. Each Managed Database can have up to four DNS entries, one for private and another for public access, as well as read-only access for each.<\/p>\n\n\n\n

Private:<\/strong> example-mctapmghasah.db.upclouddatabases.com <\/em>Private read-only:<\/strong> replica-example-mctapmghasah.db.upclouddatabases.com<\/em>
Public:<\/strong> public.example-mctapmghasah.db.upclouddatabases.com <\/em>Public read-only:<\/strong> public-replica-example-mctapmghasah.db.upclouddatabases.com<\/em><\/p>\n\n\n\n

Maximum connections<\/h3>\n\n\n\n

To ensure a consistent experience, concurrent database connections are limited based on the node resources.<\/p>\n\n\n\n

Memory<\/strong><\/th>MySQL<\/strong><\/th>PostgreSQL<\/strong><\/th>Redis<\/th><\/tr><\/thead>
2 GB<\/td>150<\/td>25<\/td>8192<\/td><\/tr>
4 GB<\/td>400<\/td>100<\/td>16384<\/td><\/tr>
8 GB<\/td>800<\/td>200<\/td>32768<\/td><\/tr>
14 GB<\/td><\/td><\/td>57344<\/td><\/tr>
16 GB<\/td>1600<\/td>400<\/td><\/td><\/tr>
28 GB<\/td><\/td><\/td>114688<\/td><\/tr>
32 GB<\/td>3200<\/td>800<\/td><\/td><\/tr>
56 GB<\/td><\/td><\/td>229376<\/td><\/tr>
64 GB<\/td>6400<\/td>1000<\/td><\/td><\/tr>
112 GB<\/td><\/td><\/td>458752<\/td><\/tr>
128 GB<\/td>12800<\/td>1000<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Data metering<\/h3>\n\n\n\n

Both inbound and outbound network transfer is unmetered by the Managed Database. The database plans do not include a transfer quota nor will the Managed Databases benefit from the user\u2019s Network Transfer Pool. However, any network transfer via the public network is metered normally user’s Cloud Servers utilising the Network Transfer Pool.<\/p>\n\n\n\n

Data transfer via the Utility network is always free of charge.<\/p>\n\n\n\n

IP access control<\/h3>\n\n\n\n

Users can set connection permissions to specific IP addresses by selecting from the list of Cloud Servers on the user\u2019s account or manually entering IP addresses.<\/p>\n\n\n\n

By default, all Utility network IP addresses are allowed. Setting a permitted IP address will exclude connection from all other addresses unless \u201callow all\u201d is enabled for either public or Utility networks.<\/p>\n\n\n\n

Maintenance<\/h3>\n\n\n\n

Users can set their preferred maintenance windows at their UpCloud Control Panel.<\/p>\n\n\n\n

Normal version upgrades are performed in place. Users will be provided with the ability to opt in for any major upgrades.<\/p>\n\n\n\n

Backups<\/h3>\n\n\n\n

Each Managed Database plan includes automated backups. Backup retention is set to either 1, 7 or 14 days for 1, 2, and 3 node clusters respectively.<\/p>\n\n\n\n

The databases are backed up automatically with full backups daily and the write-ahead log (WAL) is recorded continuously. Full backups are version-specific binary backups, which when combined with WAL allow consistent recovery to a point in time (PITR).<\/p>\n\n\n\n

All backups are encrypted and stored off-site independently from the user\u2019s Managed Database without using the cluster\u2019s storage capacity.<\/p>\n\n\n\n

The 1-day backups allow the user to go back to any given minute within the last 24 hours. 2-node plans offer 7 days of backups and 3-node plans include 14 days.<\/p>\n","protected":false},"featured_media":0,"template":"","class_list":["post-2530","documentation","type-documentation","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/documentation\/2530","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/documentation"}],"about":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/types\/documentation"}],"version-history":[{"count":0,"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/documentation\/2530\/revisions"}],"wp:attachment":[{"href":"https:\/\/upcloud.com\/global\/wp-json\/wp\/v2\/media?parent=2530"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}