Bulk Data Export

Bulk data export refers to the capability to export large volumes of data, files, or resources from your IONOS Cloud infrastructure. It enables the efficient retrieval of substantial amounts of stored data for your contract, streamlining your data management process.

Note: Bulk data export can be requested through IONOS Cloud Support. To export additional information, you can use the Cloud API provided by the respective product as mentioned in the FAQ.

Secure Data Export Request

To facilitate secure data export from your account, all export requests are initiated through IONOS Cloud Support, which enforces a rigorous encryption and verification protocol. This protocol utilizes Pretty Good Privacy (PGP) key encryption to safeguard data during transmission and requires the provision of authenticated access credentials for the Object Storage environment in your account to save the exported data.

Note:

  • Single Export per Contract: We can process only one export request per contract at a time. This limitation exists because data collection is a resource-intensive and time-consuming process.

  • Contract Owner Access Required: You must be a contract owner to initiate export requests. This ensures that data access is authorized correctly and aligned with organizational security and compliance policies.

The following procedure lists the steps for requesting a secure data export, from initial request submission to receipt of the encrypted data in the designated Object Storage bucket.

1

Initiate a data export from your account

To initiate a data export from your account, contact IONOS Cloud Support and provide the following information to ensure secure encryption of the exported data:

  • Contract Number and Support PIN: These are mandatory to authenticate your request.

  • Object Storage Details: Specify the Endpoint URL, Target Bucket Name, Access Key and the Secret Access Key.

  • PGP Public Key: Share your PGP public key, which will be used to encrypt the exported data before delivery to Object Storage. For more information about data encryption, see PGP key.

2

Information validation, data extraction, and delivery to Object Storage

After validating the necessary information received from you, the support team initiates an export request and uploads your data in an encrypted format to the designated Object Storage bucket in your account.

Info: For further information about specific file types and tools that can be used to self-extract bulk data for specific products or services, see Self-Export.

Products eligible for request-based data export

Data from the specific products listed below can only be exported in bulk by submitting a request to IONOS Cloud Support.

Product Categories

Products

Availability

Containers

Databases

Databases

Databases

Databases

Observability

Observability

Storage & Backup

Storage & Backup

Standardized file naming conventions for exported data files

  • Each exported file uses the corresponding product name as its filename prefix. The file extension reflects the original data format. Example: .json for a JSON file.

  • If the file is compressed before encryption, a .gz extension is appended to denote gzip compression.

  • All exported files are encrypted using a PGP key, and the .pgp extension is added as the final suffix. Examples:

    • example.json.gz.pgp: A JSON file that is compressed first and encrypted later.

    • example.tld.pgp: A TLD file that is encrypted without compression.

File types and tools used for products or services

1. If you have requested your data using the automated bulk data export option, we extract your data, compress it into a .gz archive, and encrypt it using your PGP key.

2. You can decrypt your compressed file and extract the data using appropriate tools. The following table lists the supported tools for data export, along with the relevant formats and structures.

Product Categories

Products

Format or Structure

Supported Tools

Containers

"velero style"

You can manually export using find /export -name "*.json" -print0 | xargs -0 kubectl apply -f.

Containers

Copy of the registry storage filesystem

docker compose

Data Analytics

PGP-encrypted and a gzipped tarball containing a JSON array file for each Kafka topic

Continuously read JSON messages from the stream and write them to the corresponding Kafka topics.

Databases

RDB file, including ACL, and configuration

Move the files to the default directories used by a standard Redis installation.

Databases

SQL files with grants, data, and configuration

mariadb

Databases

binary dump (via mongodump)

mongorestore. Ensure you use the --archive option.

Databases

SQL dump (via pg_dump)

psql

Network Services

JSON export

You can manually export using JSON export.

Observability

Loki streams are Pipe (|) -delimited, Zstandard compressed CSV

zstd - https://facebook.github.io/zstd/

Storage & Backup

Raw images with Linux Raid-Header

Linux command line tool dd

Storage & Backup

tar - ball

Linux command line tool tar.

FAQ

Does the exported data include metadata?

The exported data does not contain any associated metadata. To access metadata, use the provided API in self-export mode. For more information, see Self-Export.

Last updated

Was this helpful?