This page provides details of the database engines supported by Redgate Clone and the Using the CLI commands that can be executed for each.

Contents

Supported database engines

Redgate Clone currently supports the following database engines

Engine	Version	Backup Type
		Uncompressed	Compressed
MSSQL	2019 Developer Edition,  2019 Express Edition,  2022 Developer Edition,  2022 Express Edition
PostgreSQL	11, 12, 13, 14, 15
MySQL	8
Oracle	19.3 (standard and enterprise)

For more information on how to specify which engine and version to use in your data images, please check the Data image page.

Supported features per database engine

CLI command [reference]	MSSQL	PostgreSQL	MySQL	Oracle
rgclone create data-image empty
rgclone create data-image backup
rgclone delete data-image
rgclone get data-image
rgclone create data-container
rgclone delete data-container
rgclone get data-container
rgclone save data-container
rgclone reset data-container
rgclone load data-container

System requirements

If you follow the recommended specification for your setup (Step 1 - Installation requirements) then memory usage will be the primary limiting factor for running data containers , outside of data storage .

Data containers have different memory requirements based on the database engine being used. See the sections for specific database engines below.

In addition to data containers, data image creation also involves a temporary database instance that can have slightly higher resource usage (mostly RAM), because of a resource intense backup restore process. This instance is cleared up at the end of the data image creation operation, so memory usage is not persistent.

In terms of values, these are slightly higher than for data containers but remember that this is a burst usage only during data image creation that gets freed immediately afterwards.

You can increase your data container capacity by adding disks to the cluster or by increasing the storage/memory of your existing nodes.

Tables below shows the default CPU and RAM requirements per action per database type. If required, these can be configured within the Admin Console.