For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/account-and-service-management/reversibility/idb-reversibility-policy.md.
Skip to content

Reversibility Policy for the Managed In-Memory Database product

View as Markdown

Objective

This document describes the reversibility policy for the Managed In-Memory Database product covering the OVHcloud Valkey offer.

This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.

List of features

Features of the product line fall into three categories:

  1. Core features for which we guarantee migration capacity.
  2. OVHcloud implementations that require adaptation to a new migration environment.
  3. Specific features that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.

1. Core features

FunctionDescriptionAvailable formatsMigration modelAvailable documentation
In-memory key-value storageHigh-performance storage of key-value pairs entirely in memoryRDB (serialisation format of the DUMP command)Inbound: import data with a Valkey client (valkey-cli or a client library), by writing the keys or by restoring values serialised with DUMP using the RESTORE command
Outbound: read the data with a Valkey client, for example by iterating over the keys with SCAN and exporting them with DUMP
Valkey - Capabilities and limits

Valkey - Connect with CLI
High availabilityAutomatic failover to a replica node on the Production plan (2 nodes)NAInbound: select the Production plan when creating the service, or change the plan of an existing service
Outbound: take note of the configurations and reproduce them in the target infrastructure
Valkey - Capabilities and limits

Update the plan
PersistenceData persisted to disk via RDB snapshots, used for automated backupsRDBInbound: keep the valkey_persistence advanced parameter set to rdb
Outbound: restore a backup to a new service (fork), then export its data with a Valkey client (see above)
Valkey - Capabilities and limits

Automated backups

Restore a backup
ScalabilityVertical scaling by changing the node flavor or the plan (cluster mode and sharding are not supported)NAInbound: change the flavor or the plan via the Control Panel or the API
Outbound: size the target infrastructure according to the memory used by the data
Update the flavor

Update the plan

2. OVHcloud Implementations

FunctionDescriptionAvailable formatsMigration modelAvailable documentation
Network Security (ACL)Access control by IP listIPv4, JSONInbound: IP configuration authorised via the web interface (Control Panel) or API
Outbound: export the configuration and adapt it to the target architecture
Valkey - Configure incoming connections
vRackThe vRack, or virtual rack, is a private VLAN technology that enables the connection between OVHcloud servicesNAInbound: enable and configure network connection
Outbound: take note of the network architecture and reproduce it with VLANs
Creating Public Cloud Databases V(x)LANs

3. Specific features

FunctionDescriptionAvailable formatsMigration modelAvailable documentation
Infrastructure as codeAutomated deployment via Terraform modules specific to OVHcloudNAInbound: scripts to be adapted for other providers
Outbound: Terraform configurations need to be rewritten
Terraform
Anti-DDoS protectionAnti-DDoS is a set of tools and mechanisms designed to absorb denial of service attacks. It includes traffic analysis, "clean-up" via a specialised network, and mitigation using VAC technology developed by OVHcloud.N/AInbound: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required
Outbound: Order and configure an anti-DDoS solution from the new provider
OVHcloud DDoS protection

List of architectures

The product is based on an in-memory architecture. On the Discovery plan, the service runs on a single node. On the Production plan, it runs on a primary node and a replica node, with automatic failover to the replica. Data is persisted to disk via RDB snapshots and backed up in two regions.

Partner services

The OVHcloud partners concerned are listed in the OVHcloud partners directory under the "Data center expansion and Migration" keywords.

OVHcloud also has a dedicated service: OVHcloud Professional Services.

Cost and fees

The features described in the tables are available at no cost, unless otherwise specified, and are freely usable by the customer. Pricing is Pay-as-you-go and depends on the memory capacity and instance type. No additional egress fee is applied, but it is essential to export all data before termination, as it will be permanently deleted.

Data retention after contract termination

Once the service has been cancelled, all of the data stored in the Valkey instances is irreversibly deleted. It is the customer’s responsibility to carry out a full backup before termination.

OVHcloud does not guarantee the operation and availability of backups to perform restores of customer data after the service cancellation.

OVHcloud backups of customer databases are stored for a period ranging from 2 days to one month after the contract is terminated.

Was this page helpful?