1. Run the aws configure command in a terminal.

2. AWS Access Key ID [None]: Insert the Access Key. In the DCD, go to Menu > Storage > IONOS Object Storage > Key management and check the Access keys section to find the essential details.

3. AWS Secret Access Key [None]: Paste the Secret Key. In the DCD, go to Menu > Storage > IONOS Object Storage > Key management and check the Access keys section to find the essential details.

4. Default region name [None]: de.

5. Default output format [None]: json.

Using AWS CLI with IONOS Object Storage

Test if you set up AWS CLI correctly by running a command to list buckets; use any endpoints for testing purposes.

aws s3 ls --endpoint-url https://s3.eu-central-1.ionoscloud.com

If the setup works correctly, you may proceed with the other commands.

For each command, be sure to include one of the endpoints in the endpoint-url parameter:

--endpoint-url https://s3.eu-central-2.ionoscloud.com

For information on the supported IONOS Object Storage Service endpoints, see Endpoints.

There are two sets of commands:

• S3: Offers high-level commands for managing buckets and moving, copying, and synchronizing objects.

• S3api: Allows you to work with specific features such as ACL, CORS, and Versioning.

For additional information, see the official AWS CLI Command Reference.

IONOS Object Storage is compatible with the S3 protocol, which means that it can be used to manage buckets and objects with existing S3 clients once properly configured.

Amazon Web Services (AWS) Command-line Interface (CLI) is unique in offering a wide range of commands for comprehensive management of buckets and objects which is ideal for scripting and automation. IONOS Object Storage supports using AWS CLI for Windows, macOS, and Linux.

Use IONOS Object Storage with AWS CLI

• Configure AWS CLI

• Standard Commands

• Object Lock

• Replication

• Versioning

• Lifecycle

• Bucket Policy

• ACL for Buckets

• ACL for Objects

• Logging

• CORS

• Static Website Hosting

This document provides instructions to manage Replication using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Commands

Create the file replication_configuration.json with the following content:

    "Role": "this field is ignored",
    "Rules": [
        {
            "Status": "Enabled",
            "Prefix": "",
            "Destination": {
                "Bucket": "arn:aws:s3:::my-destination-bucket"
            }
        }
    ]

Enable replication from my-source-bucket to my-destination-bucket (use the endpoint of the source bucket):

aws s3api put-bucket-replication --bucket my-source-bucket --replication-configuration file://replication_configuration.json --endpoint-url https://s3.eu-central-2.ionoscloud.com

Retrieve the replication configuration:

aws s3api get-bucket-replication --bucket my-source-bucket  --endpoint-url https://s3.eu-central-2.ionoscloud.com

Delete the replication configuration:

aws s3api delete-bucket-replication --bucket my-source-bucket  --endpoint-url https://s3.eu-central-2.ionoscloud.com

This document provides instructions for managing IONOS Object Storage using the AWS CLI. Additionally, this task can also be performed through the DCD DCD and API.

Examples

List buckets

• Option 1: Using s3 set of commands:

  Copy

  aws s3 ls --endpoint-url https://s3.eu-central-2.ionoscloud.com

• Option 2: Using s3api set of commands:

  Copy

  aws s3api list-buckets --endpoint-url https://s3.eu-central-2.ionoscloud.com

• Create a bucket in the eu-central-2 region (Berlin, Germany):

  • Option 1: Using s3 set of commands:

    Copy

    aws s3 mb s3://my-bucket --region eu-central-2 --endpoint-url https://s3.eu-central-2.ionoscloud.com

  • Option 2: Using s3api set of commands:

    Copy

    aws s3api create-bucket --bucket my-bucket --region=eu-central-2 --create-bucket-configuration LocationConstraint=eu-central-2 --endpoint-url https://s3.eu-central-2.ionoscloud.com

• Create a bucket in the de region (Frankfurt, Germany) with Object Lock enabled:

  Copy

  aws s3api create-bucket --bucket my-bucket --object-lock-enabled-for-bucket --region=de --create-bucket-configuration LocationConstraint=de --endpoint-url https://s3.eu-central-1.ionoscloud.com

Upload and download objects

• Upload an object from the current directory to a bucket:

  Copy

  aws s3 cp filename.txt s3://my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com
  

• Download all the objects from the my-bucket bucket to the local directory my-dir:

  Copy

  aws s3 cp s3://my-bucket my-dir --recursive --endpoint-url https://s3.eu-central-2.ionoscloud.com
  

Copy and sync objects

• Copy the object to the bucket:

  Copy

  aws s3 cp my-dir s3://my-bucket/ --recursive --endpoint-url https://s3.eu-central-2.ionoscloud.com

• Copy the contents of the local directory my-dir to the bucket my-bucket:

  Copy

  aws s3 cp my-dir s3://my-bucket/ --recursive --endpoint-url https://s3.eu-central-2.ionoscloud.com

  For more information, see the cp command reference.

• Copy all objects from my-source-bucket to my-dest-bucket excluding .zip files. The command does not support cross-region copying for IONOS Object Storage:

  Copy

  aws s3 cp s3://my-source-bucket/ s3://my-dest-bucket/ --recursive --exclude "*.zip" --endpoint-url https://s3.eu-central-2.ionoscloud.com`

• Sync the bucket my-bucket with the contents of the local directory my-dir:

  Copy

  aws s3 sync my-dir s3://my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com

For more information, see sync command reference.

This document provides instructions to manage Versioning using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Commands

Get the versioning state of the bucket:

aws s3api get-bucket-versioning --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com

Enable versioning for the bucket:

aws s3api put-bucket-versioning --bucket my-bucket --versioning-configuration Status=Enabled --endpoint-url https://s3.eu-central-2.ionoscloud.com

List object versions for the bucket:

aws s3api list-object-versions --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com

List object versions for the object my-object.txt:

aws s3api list-object-versions --bucket my-bucket --prefix my-object.txt --endpoint-url https://s3.eu-central-2.ionoscloud.com

This document provides instructions to manage Bucket Policy using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Commands

To create a file policy.json with the JSON policy, see Examples.

Apply a bucket policy to a bucket:

aws s3api put-bucket-policy --bucket my-bucket --policy file://policy.json --endpoint-url https://s3.eu-central-2.ionoscloud.com

Save a bucket policy to file:

aws s3api get-bucket-policy --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com > policy.json

Delete the bucket policy:

aws s3api delete-bucket-policy --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com

This document provides instructions to Manage ACL for Buckets using the AWS CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Use the following keys to define access permissions:

• --grant-read: Grants read-only access.

• --grant-write: Grants write-only access.

• --grant-read-acp: Grants permission to read the Access Control List.

• --grant-write-acp: Grants permission to modify the Access Control List.

• --grant-full-control: Grants full access, encompassing the permissions listed above (read, write, read ACL, and write ACL).

Grant access permission to another user

Grant full control of my-bucket to a user with a specific Canonical user ID:

aws s3api put-bucket-acl --bucket MY-BUCKET --grant-full-control id=CANONICAL_USER_ID --endpoint-url https://s3.eu-central-2.ionoscloud.com

Separate grants with a comma if you want to specify multiple Canonical user IDs:

aws s3api put-bucket-acl --bucket MY-BUCKET --grant-full-control id=CANONICAL_USER_ID_1,id=CANONICAL_USER_ID_2 --endpoint-url https://s3.eu-central-2.ionoscloud.com

Grant full control of my-bucket to multiple users using their Canonical user IDs:

aws s3api put-bucket-acl --bucket MY-BUCKET --grant-full-control id=CANONICAL_USER_ID_1,id=CANONICAL_USER_ID_2 --endpoint-url https://s3.eu-central-2.ionoscloud.com

Grant full control of my-bucket by using an email address instead of a Canonical User ID:

aws s3api put-bucket-acl --bucket MY-BUCKET --grant-full-control emailaddress=some@email.com --endpoint-url https://s3.eu-central-2.ionoscloud.com

Retrieve the ACL of a bucket and save it to the file acl.json:

aws s3api get-bucket-acl --bucket MY-BUCKET --endpoint-url https://s3.eu-central-2.ionoscloud.com > acl.json

Edit the file. For example, remove or add some grants and apply the updated ACL to the bucket:

aws s3api put-bucket-acl --bucket MY-BUCKET --access-control-policy file://acl.json --endpoint-url https://s3.eu-central-2.ionoscloud.com

Use the following values for the --acl key:

• private removes public access.

• public-read allows public read-only access.

• public-read-write allows public read/write access.

• authenticated-read allows read-only access to all authenticated users of IONOS Object storage (including ones out of your contract).

Public access

Allow public read-only access to the bucket:

aws s3api put-bucket-acl --bucket MY-BUCKET --acl public-read --endpoint-url https://s3.eu-central-2.ionoscloud.com

Remove public access to the bucket:

aws s3api put-bucket-acl --bucket MY-BUCKET --acl private --endpoint-url https://s3.eu-central-2.ionoscloud.com

Grant access permission to Log Delivery Group

Set WRITE and READ_ACP permissions for the Log Delivery Group, which is required before enabling the Logging feature for a bucket:

aws s3api put-bucket-acl --bucket MY-BUCKET --acl log-delivery-write --endpoint-url https://s3.eu-central-2.ionoscloud.com

This document provides instructions to Manage ACL for Objects using the AWS CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Use the following keys to define access permissions:

• --grant-read: Grants read-only access.

• --grant-write: Grants write-only access.

• --grant-read-acp: Grants permission to read the Access Control List.

• --grant-write-acp: Grants permission to modify the Access Control List.

• --grant-full-control: Grants full access, encompassing the permissions listed above (read, write, read ACL, and write ACL).

Use --key to specify the object for granting access:

aws s3api put-object-acl --bucket MY-BUCKET --key my-object.txt --grant-full-control id=CANONICAL_USER_ID --endpoint-url https://s3.eu-central-2.ionoscloud.com

Use the following values for the --acl key:

• private removes public access.

• public-read allows public read-only access.

• public-read-write allows public read/write access.

• authenticated-read allows read-only access to all authenticated users of IONOS Object storage (including ones out of your contract).

Allow public read-only access to the object:

aws s3api put-object-acl --bucket MY-BUCKET --acl public-read --endpoint-url https://s3.eu-central-2.ionoscloud.com

Remove public access from the object:

aws s3api put-object-acl --bucket MY-BUCKET --acl private --endpoint-url https://s3.eu-central-2.ionoscloud.com

S3cmd is a free command line tool and client for loading, retrieving, and managing data in S3. It has over 60 command line options, including multipart uploads, encryption, incremental backup, S3 sync, ACL and metadata management, bucket size, and bucket policies (Linux, macOS).

Configuration

Install 3cmd for your distribution:

• on CentOS/RHEL and Fedora: sudo dnf install s3cmd

• on Ubuntu/Debian: sudo apt-get install s3cmd

• on macOS using Brew: brew install s3cmd

You can also install the latest version from SourceForge.

Configuration steps

Run the following command in a terminal: s3cmd --configure. This will guide you through the interactive installation process:

1. Enter your Access Key and Secret key. To get them, log in to the DCD, go to Menu > Storage > IONOS Object Storage > Key management.

1. Specify the region of your bucket for Default Region. Example: eu-central-2. Please refer to the list of available regions.

2. Specify the endpoint for the selected region for Endpoint from the same list. For example, s3-eu-central-2.ionoscloud.com.

3. Insert the same endpoint again for DNS-style bucket+hostname:port template.

4. Specify or skip password (press Enter) for Encryption password.

5. Press Enter for Path to GPG program.

6. Press Enter for Use HTTPS protocol.

7. Press Enter for HTTP Proxy server name.

8. Press Enter for Test access with supplied credentials? [Y/n].

9. S3cmd will try to test the connection. If everything went well, save the configuration by typing y and pressing Enter. The configuration will be saved in the .s3cfg file.

If you need to work with more than one region or with different providers, there is a way to set up multiple configurations. Use s3cmd -configure --config=ionos-fra to save the configuration for a specific location or provider. Run s3cmd with the -c option to override the default configuration file. For example, list the object in the bucket:

s3cmd -c ionos-fra ls s3://my-bucket

You can also specify an endpoint directly on the command line to override the default setting. The Access Key and Secret key are region-independent, so s3cmd can take them from the default configuration:

s3cmd --host s3-eu-south-2.ionoscloud.com ls s3://my-bucket

Or even specify it with an Access Key and the Secret Key:

s3cmd  --access_key=YOUR_ACCESS_KEY --secret_key=SECRET_KEY --host s3-eu-south-2.ionoscloud.com ls s3://my-bucket

Using s3cmd with IONOS Object Storage

Please refer to the list of available endpoints for the --host option. You can skip this option if you are only using the region from the configuration file.

Sample usage

• List buckets (even buckets from other regions will be listed):

  Copy

  s3cmd ls

• Create a bucket (the name must be unique for the whole IONOS Object Storage). You need to explicitly use the --region option, otherwise a bucket will be created in the default de region:

  • Create the bucket my-bucket in the region de (Frankfurt, Germany):

  Copy

  s3cmd --host s3-eu-cental-1.ionoscloud.com --region=de mb s3://my-bucket

  • Create the bucket my-bucket in the region eu-cental-2 (Berlin, Germany):

  Copy

  s3cmd --host s3-eu-cental-2.ionoscloud.com --region=eu-central-2 mb s3://my-bucket

  • Create the bucket my-bucket in the region eu-south-2 (Logrono, Spain):

  Copy

  s3cmd --host s3-eu-south-2.ionoscloud.com --region=eu-south-2 mb s3://my-bucket

• List objects of the bucket my-bucket:

  Copy

  s3cmd ls s3://my-bucket

• Upload filename.txt from the current directory to the bucket my-bucket:

  Copy

  s3cmd put filename.txt s3://my-bucket

• Copy the contents of local directory my-dir to the bucket my-bucket with prefix my-dir:

  Copy

  s3cmd my-dir s3://my-bucket --recursive

• Copy all objects from my-source-bucket to my-dest-bucket excluding .zip files (or use mv to move objects). The command doesn’t support cross-region copying for IONOS Object Storage, use rclone utility for cross-region copying:

  Copy

  s3cmd cp s3://my-source-bucket s3://my-dest-bucket --recursive

• Download all the objects from the my-bucket bucket to the local directory my-dir (the directory should exist):

  Copy

  s3cmd get s3://my-bucket my-dir --recursive

• Synchronize a directory to S3 (checks files using size and md5 checksum):

  Copy

  s3cmd sync my-dir s3://my-bucket/

• Get Cross-Origin Resource Sharing (CORS) configuration:

  Copy

  s3cmd info s3://my-bucket

• Set up Cross-Origin Resource Sharing (CORS) configuration:

  Copy

  s3cmd cors_rules.xml s3://my-bucket

  cors_rules.xml:

  Copy

  <CORSConfiguration>
  <CORSRule>
      <AllowedOrigin>http://www.MY-DOMAIN.com</AllowedOrigin>
      <AllowedOrigin>http://MY-DOMAIN.COM</AllowedOrigin>
      <AllowedMethod>PUT</AllowedMethod>
      <AllowedMethod>POST</AllowedMethod>
      <AllowedMethod>DELETE</AllowedMethod>
      <AllowedHeader>*</AllowedHeader>
      <MaxAgeSeconds>3000</MaxAgeSeconds>
      <ExposeHeader>ETag</ExposeHeader>
  </CORSRule>

• Delete CORS from the bucket:

  Copy

  s3cmd delcors s3://my-bucket

• Get information about buckets or objects:

  • s3cmd info s3://my-bucket

  • s3cmd info s3://my-bucket/my-object

• Generate a public URL for download that will be available for 10 minutes (600 seconds):

  Copy

  s3cmd signurl s3://my-bucket/filename.txt +600

• Set up a lifetime policy for a bucket (delete objects older than 1 day):

  Copy

  s3cmd setlifecycle detete-after-one-day.xml s3://my-bucket

  detete-after-one-day.xml:

  Copy

  <?xml version="1.0" ?>
  <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
  	<Rule>
  		<ID>Delete older than 1 day</ID>
  		<Prefix/>
  		<Status>Enabled</Status>
  		<Expiration>
  			<Days>1</Days>
  		</Expiration>
  	</Rule>
  </LifecycleConfiguration>

• Encrypt and upload files. This option allows you to encrypt files before uploading, but in order to use it, you have to run s3cmd --configure and fill out the path to the GPG utility and the encryption password. There is no need to use special parameters to decrypt the file on downloading with get option as this is done automatically using the data from the configuration file.

• Add or modify user-defined metadata. Use headers starting with x-amz-meta- and store data in the set of key-value pairs. The user-defined metadata is limited to 2 KB in size. The size of the user-defined metadata is measured by taking the sum of the number of bytes in the UTF-8 encoding of each key and value.

  • s3cmd modify --add-header x-amz-meta-my_key:my_value s3://my-bucket/prefix/filename.txt

  • Check the changes:

  Copy

  s3cmd info s3://my-bucket/prefix/filename.txt

  • Delete metadata:

  Copy

  s3cmd modify --remove-header x-amz-meta-my_key s3://my-bucket/prefix/filename.txt

For more information, visit S3cmd usage and S3cmd FAQ.

This document provides instructions for managing Static Website Hosting using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Commands

Make the bucket public for static website hosting using Bucket Policy:

aws s3api put-bucket-policy --bucket my-bucket \
   --policy file://policy.json \
   --endpoint-url https://s3.eu-central-2.ionoscloud.com

Contents of policy.json:

{
    "Version": "2012-10-17",
    "Statement":
    [
        {
            "Sid": "PublicRead",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::example-bucket/*"
        }
    ]
}

Enable static website hosting for my-bucket:

aws s3 website s3://my-bucket \
    --index-document index.html \
    --error-document error.htm \
    --endpoint-url https://s3.eu-central-2.ionoscloud.com

Disable static website hosting for my-bucket:

aws s3api delete-bucket-website --bucket my-bucket \
    --endpoint-url https://s3.eu-central-2.ionoscloud.com

S3 Browser is a free, feature-rich Windows client for IONOS Object Storage.

Steps

1. Download and install the S3 Browser.

2. Add a new account and select:

   • Display name: Enter a name for the connection.

   • Account type: Select S3 Compatible Storage from the drop-down list.

   • REST Endpoint: If you already have a bucket, select the endpoint URL from the list. Otherwise, you can select s3-eu-central-2.ionoscloud.com, which corresponds to the location in Berlin, Germany.

   • To get the Access Key and Secret Key, log in to the DCD, go to Menu > Storage > IONOS Object Storage > Key management.

   • Click Advanced S3-compatible storage settings in the lower-left corner of the form.

3. Storage settings:

   • Signature version: Select Signature V4 from the drop-down list.

   • Addressing model: Leave Path style.

   • Override storage regions: Paste the following text into the text area:

     Copy

     Frankfurt, Germany=eu-central-1
     Berlin, Germany=eu-central-2
     Logrono, Spain=eu-south-2

   • Region-specific endpoint: Insert the following text: s3-{region-code}.ionoscloud.com
4. Save the details.

5. Try creating your first bucket. The bucket name must be unique across the entire IONOS Object store. That's why S3 Browser will offer to add random text to the bucket name. But you can still try to come up with your unique name.

IONOS Object Storage supports using Cyberduck, a Cloud Storage browser with SFTP, WebDAV, and S3 support for Windows, macOS, and Linux.

For the installation instructions, see Cyberduck.

Configuration steps

1. Once inside Cyberduck, select Cyberduck > Preferences… from the menu.

1. Select Profiles to open the Connection Profiles page.

2. Select the IONOS Cloud Object Storage (Berlin) connection profile or IONOS Cloud Object Storage (Frankfurt), or IONOS Cloud Object Storage (Logrono) from the list of available connection profiles, or best use the search option to search for it.

1. Close the Preferences window and restart Cyberduck to install the selected connection profiles.

2. Open Cyberduck and select File > Open Connection… You will see the connection dialog.

3. At the top, click the dropdown menu and select the IONOS Cloud Object Storage (Berlin) profile that corresponds with the data center you want to use.

4. Enter key values in the Access Key and Secret Key fields.

To access the Object Storage keys:

• Log in to the DCD, go to Menu > Storage > IONOS Object Storage > Key management.

• Choose "Generate a key" and confirm the action by clicking Generate. The object storage key will be generated automatically.

1. Click Connect.

Sample usage

• -c FILE, --config=FILE - Config file name. Defaults to $HOME/.s3cfg.

• -e, --encrypt - Encrypt files before uploading to S3.

• --upload-id=UPLOAD_ID - UploadId for Multipart Upload, in case you want to continue an existing upload (equivalent to --continue-put) and there are multiple partial uploads. Use s3cmd multipart [URI] to see what UploadIds are associated with the given URI.

This document provides instructions to manage Logging using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Commands

aws s3api put-bucket-acl \
    --bucket MY-BUCKET-FOR-LOGS \
    --grant-write URI=http://acs.amazonaws.com/groups/s3/LogDelivery \
    --grant-read-acp URI=http://acs.amazonaws.com/groups/s3/LogDelivery \
    --endpoint-url https://s3.eu-central-2.ionoscloud.com

After that, you can enable Logging for a bucket:

aws s3api put-bucket-logging \
    --bucket MY-BUCKET \
    --bucket-logging-status file://logs-acl.json \
    --endpoint-url https://s3.eu-central-2.ionoscloud.com

Contents of logs-acl.json:

Retrieve bucket logging settings:

aws s3api get-bucket-logging \
   --bucket MY-BUCKET \
   --endpoint-url https://s3.eu-central-2.ionoscloud.com

Disable logging for a bucket:

aws s3api put-bucket-logging \
   --bucket MY-BUCKET \
   --bucket-logging-status '{}' \
   --endpoint-url https://s3.eu-central-2.ionoscloud.com

Postman is a free tool for conveniently working with APIs in a graphical interface. It is available for Windows, macOS, and Linux.

You can follow the installation instructions described on Postman.

Steps

1. In the Authorization tab for a request, select AWS Signature from the Type dropdown list. Specify where Postman should append your authorization data using the Add authorization data to drop-down menu.

• If you select Request Headers, Postman populates the Headers tab with Authorization and X-Amz- prefixed fields.

• If you select the Request URL, Postman populates the Params tab with authentication details prefixed with X-Amz-.

1. To get the Access Key and Secret Key, log in to the DCD, go to Menu > Storage > IONOS Object Storage > Key management.

Advanced fields are optional, but Postman will attempt to generate them automatically if necessary.

1. For AWS Region, leave the field blank as the region from the endpoint will be used.

2. For Service Name, enter s3. The name of the service that receives the requests.

3. For Session Token, leave the field blank. This is only required when temporary security credentials are used.

4. Setup completed. Now check the API description to get the right endpoint to call.

IONOS Object Storage is fully compatible with S3, which means that it can be used to manage buckets and objects with existing S3 clients once properly configured. We suggest a list of popular tools for working with IONOS Object Storage, as well as instructions for configuring them:

GUI

• : Tool for API development and testing. Its unique feature is a graphical interface for sending API requests to object storage endpoints, facilitating testing and development.

• : An open-source GUI client supporting object storage among other protocols, presenting storage objects as local files for easy browsing, upload, and download.

• : Freeware Windows client for object storage, providing an easy way to manage buckets and objects, including file permissions and access control lists, through a visual interface.

CLI

• : Unique in offering a wide range of commands for comprehensive management of buckets and objects. Ideal for scripting and automation.

• : Offers direct, scriptable control over object storage buckets and objects. However, it lacks certain features like versioning and replication management.

• : A CLI program for syncing files between local and cloud storage, distinguishing itself with powerful synchronization capabilities, specifically functional when handling large data quantities and complex sync setups.

SDK

: Provides high-level object-oriented API as well as low-level direct service access.

Backup

: Comprehensive backup and disaster recovery solution for virtual, physical, and cloud-based workloads. Supports creating an Object Storage repository for backing up to one or multiple buckets.

Terraform

is the official AWS SDK for Python. It allows you to create, update, and configure IONOS Object Storage objects from within your Python scripts.

Configuration

Install the latest Boto3 release via pip: pip install boto3

There are several ways to , e.g. passing credentials as parameters to the boto.client() method, via environment variables, or with a generic credential file (~/.aws/credentials).

An example of passing credentials as parameters when creating a Session object:

To get the Access Key and Secret Key, , and go to Menu > Storage > IONOS Object Storage > Key management.

NOTE: Your credentials are not tied to a specific region or bucket.

Sample usage

• List buckets:
• Create bucket my-bucket at the region eu-central-1:
• Upload filename.txt to the bucket my-bucket:
• Download the file filename.txt from the my-bucket:
• List objects of the bucket my-bucket
• Copy the filename.txt from the bucket my-source-bucket to the bucket my-dest-bucket and add the prefix uploaded/. Instead of the client() method, we use the resource() method here. It provides a higher level of abstraction than the low-level calls made by service clients.

This document provides instructions to manage Lifecycle using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Commands

Create a file lifecycle.json with the JSON policy:

{
  "Rules": [
    {
      "ID": "Delete objects with data/ prefix after 30 days with size",
      "Status": "Enabled",
      "Expiration": {
        "Days": 30
      },
      "Filter": {
        "Prefix": "data/"
      }
    },
    {
      "ID": "Delete objects 60 days after becoming non-current for bucket with Versioning enabled",
      "Status": "Enabled",
      "Filter": {
        "Prefix": "temp/"
      },
      "NoncurrentVersionExpiration": {
        "NoncurrentDays": 45
      }
    },
    {
      "ID": "Delete 2022 logs in 2024.",
      "Status": "Enabled",
      "Expiration": {
          "Date": "2024-01-01T00:00:00.000Z"
      },  
      "Filter": {  
        "Prefix": "logs/2022/"
      }
    },
    {
      "ID": "Delete incomplete multipart uploads",
      "Status": "Enabled",
      "AbortIncompleteMultipartUpload": {
        "DaysAfterInitiation": 5
      },
      "Filter": {}
    }  
  ]
}

Apply the lifecycle configuration to a bucket:

aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-configuration  file://lifecycle.json  --endpoint-url https://s3.eu-central-2.ionoscloud.com

Save the bucket’s lifecycle configuration to a file:

aws s3api get-bucket-lifecycle-configuration --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com > lifecycle.json

Delete the Lifecyle configuration:

aws s3api delete-bucket-lifecycle --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com

Rclone is a command line tool for managing files in the cloud. It is available for Windows, macOS, and Linux. Rclone also has a built-in HTTP server that can be used to remotely control rclone using its API and a web GUI (graphical user interface).

rclone helps:

• backing up (and encrypting) files to cloud storage

• restoring (and decrypting) files from cloud storage

• mirroring cloud data to other cloud services or locally

• transferring data to the cloud or between cloud storage providers

• mounting multiple encrypted, cached, or diverse cloud storages in the form of a disk

• analyzing and taking into account data stored in cloud storage using lsf, ljson, size, and ncdu

Configuration

Download the latest version of rclone from rclone.org. The official Ubuntu, Debian, Fedora, Brew, and Chocolatey repositories include rclone.

You can find the configuration example here.

Using rclone with IONOS Object Storage

Configurations configured with the rclone config command are called remotes. If you already have or plan to use buckets in different IONOS Object Storage regions, you will need to set up a separate remote for each region you use.

Please refer to the list of commands at the rclone website.

Sample Usage

• List remotes:

  Copy

  rclone listremotes

• List buckets of "ionos1" remote:

  Copy

  rclone lsd ionos1:

• Create bucket my-bucket at the remote ionos1:

  Copy

  rclone mkdir ionos1:my-bucket

• List objects of the bucket my-bucket:

  Copy

  rclone lsf ionos1:my-bucket

  For more information, see lsf command reference.

• Upload filename.txt from the current directory to the bucket my-bucket:

  Copy

  rclone copy --progress filename.txt ionos1:my-bucket

• Copy the contents of local directory my-dir to the bucket my-bucket:

  Copy

  rclone copy --progress my-dir ionos1:my-bucket/my-dir/

• Copy all objects with the prefix my-dir from the bucket my-source-bucket to my-dest-bucket:

  Copy

  rclone copy --progress ionos1:my-bucket/my-dir/ ionos2:my-bucket/my-dir/

  The buckets could be located in different regions and even at different providers. Unless buckets are located within the same region, the data is not copied directly from the source to the destination. For cross-regional copying, the data is downloaded to you from the source bucket and then uploaded to the destination.

• Download all the objects from the my-bucket bucket to the local directory my-dir:

  Copy

  rclone copy --progress ionos1:my-bucket my-dir/

• Sync the bucket my-bucket with the contents of the local directory my-dir. The destination is updated to match the source, including deleting files if necessary:

  Copy

  rclone sync --progress my-dir/ ionos1:my-bucket

• Get the total size and number of objects in remote:path:

  Copy

  rclone size ionos1:my-bucket/path

• Check if the files in the local directory and destination match:

  Copy

  rclone check my-dir/ ionos1:my-bucket

• Produce an md5sum file for all the objects in the path:

  Copy

  rclone md5sum ionos1:my-bucket/path

This document provides instructions to manage CORS using the CLI. Additionally, these tasks can also be performed using the DCD and API.

Commands

Get the CORS configuration for the bucket my-bucket:

aws s3api get-bucket-cors --bucket my-bucket --endpoint-url https://s3.eu-central-2.ionoscloud.com

Set up CORS configuration for the bucket my-bucket:

aws s3api put-bucket-cors --bucket my-bucket --cors-configuration file://cors.json --endpoint-url https://s3.eu-central-2.ionoscloud.com

Sample CORS request

{
 "CORSRules": [
 {
 "AllowedOrigins": ["http://www.example.com"],
 "AllowedHeaders": ["*"],
 "AllowedMethods": ["PUT", "POST", "DELETE"],
 "MaxAgeSeconds": 3000,
 "ExposeHeaders": ["x-amz-server-side-encryption"]
 },
 {
 "AllowedOrigins": ["*"],
 "AllowedHeaders": ["Authorization"],
 "AllowedMethods": ["GET"],
 "MaxAgeSeconds": 3000
 }
 ]
}

For more information, see put-bucket-cors command reference.

This document provides instructions to manage Object Lock using the CLI. Additionally, these tasks can also be performed using the DCD and IONOS Object Storage API.

Create a bucket with an Object Lock

Create a bucket my-bucket in the de region (Frankfurt, Germany) with Object Lock:

aws s3api create-bucket \
  --bucket my-bucket \
  --object-lock-enabled-for-bucket \
  --region=de --create-bucket-configuration \
  LocationConstraint=de \
  --endpoint-url https://s3.eu-central-1.ionoscloud.com

Object Lock with Governance mode

An Object Lock with Governance mode on a bucket provides the bucket owner with better flexibility compared to the Compliance mode. It permits the removal of the Object Lock before the designated retention period has expired, allowing for subsequent replacements or deletions of the object.

Apply Governance mode configuration to the bucket my-bucket-with-object-lock with a default retention period equal to 15 days (or use the PutObjectLockConfiguration API Call):

aws s3api put-object-lock-configuration \
    --bucket my-bucket-with-object-lock \
    --object-lock-configuration '{ "ObjectLockEnabled": "Enabled", "Rule": { "DefaultRetention": { "Mode": "GOVERNANCE", "Days": 15 }}}' \
    --endpoint-url https://s3.eu-central-1.ionoscloud.com

On applying this configuration, the newly uploaded objects adhere to this retention setting.

Object Lock with Compliance mode

An Object Lock with Compliance mode on a bucket ensures strict control by enforcing a stringent retention policy on objects. Once this mode is set, the retention period for an object cannot be shortened or modified. It provides immutable protection by preventing objects from being deleted or overwritten during their retention period.

This mode is particularly suited for meeting regulatory requirements as it guarantees that objects remain unaltered. It does not allow locks to be removed before the retention period concludes, ensuring consistent data protection.

Apply Compliance mode configuration to the bucket my-bucket-with-object-lock with a default retention period equal to 15 days:

aws s3api put-object-lock-configuration \
    --bucket my-bucket-with-object-lock \
    --object-lock-configuration '{ "ObjectLockEnabled": "Enabled", "Rule": { "DefaultRetention": { "Mode": "COMPLIANCE", "Days": 15 }}}' \
    --endpoint-url https://s3.eu-central-1.ionoscloud.com

On applying this configuration, the newly uploaded objects adhere to this retention setting.

Retrieve Object Lock configuration

Retrieve Object Lock configuration of a bucket (the same could be achieved with the GetObjectLockConfiguration API Call):

aws s3api get-object-lock-configuration \
  --bucket my-bucket-with-object-lock \
  --endpoint-url https://s3.eu-central-1.ionoscloud.com 

Sample response

{
    "ObjectLockConfiguration": {
        "ObjectLockEnabled": "Enabled",
        "Rule": {
            "DefaultRetention": {
                "Mode": "GOVERNANCE",
                "Days": 15
            }
        }
    }
}

aws s3api put-object-lock-configuration \
    --bucket my-bucket-with-object-lock \
    --object-lock-configuration '{ "ObjectLockEnabled": "Enabled", "Rule": { "DefaultRetention": { "Mode": "COMPLIANCE", "Days": 15 }}}' \
    --endpoint-url https://s3.eu-central-1.ionoscloud.com

Upload objects to a bucket with an Object Lock

Upload my-object.pdf to the bucket my-bucket-with-object-lock:

aws s3api put-object \
   --bucket my-bucket-with-object-lock \
   --key my-object.pdf \
   --endpoint-url https://s3.eu-central-1.ionoscloud.com

Sample response

{
    "ETag": "\"d41d8cd98f00b204e9800998ecf8427e\"",
    "VersionId": "fe11c94b-d120-723f-b907-1070fde7f794"
}

This task could also be achieved by using the PutObject API call.

Upload my-object.pdf to the bucket my-bucket-with-object-lock and override the bucket’s default Object Lock configuration:

aws s3api put-object \
      --bucket my-bucket-with-object-lock \
      --key my-object.pdf \
      --object-lock-mode GOVERNANCE \
      --object-lock-retain-until-date 2023-08-09T09:01:01Z \
      --endpoint-url https://s3.eu-central-1.ionoscloud.com

Delete objects with Object Lock

The permanent deletion of the object’s version is prohibited, and the system only creates a deletion marker for the object. But it makes IONOS Object Storage behave in most ways as though the object has been deleted. You can only list the delete markers and other versions of an object by using the ListObjectVersions API call.

aws s3api list-object-versions --bucket my-bucket-with-object-lock --endpoint-url https://s3.eu-central-1.ionoscloud.com

Legal Hold

Apply legal-hold status to my-object.pdf in the bucket my-bucket-with-object-lock:

aws s3api put-object-legal-hold \
    --bucket my-bucket-with-object-lock \
    --key my-object.pdf \
    --legal-hold Status=ON \
    --endpoint-url https://s3.eu-central-1.ionoscloud.com

Use Status=OFF to turn off the legal-hold status.

View lock information for an object

To check the Object Lock status for a particular version of an object, you can utilize either the GET Object or the HEAD Object commands. Both commands will provide information about the retention mode, the designated 'Retain Until Date' and the status of the legal hold for the chosen object version.

Set retention limits

When multiple users have permission to upload objects to your bucket, there is a risk of overly extended retention periods being set. This can lead to increased storage costs and data management challenges. While the system allows for up to 100 years using the s3:object-lock-remaining-retention-days condition key, implementing limitations can be particularly beneficial in multi-user environments.

Establish a 10-day maximum retention limit:

{
    "Version": "2012-10-17",
    "Id": "Set Retention Limits",
    "Statement": [
        {
            "Sid": "Set Retention Period",
            "Effect": "Deny",
            "Principal": "*",
            "Action": [
                "s3:PutObjectRetention"
            ],
            "Resource": "arn:aws:s3:::my-bucket-with-object-lock/*",
            "Condition": {
                "NumericGreaterThan": {
                    "s3:object-lock-remaining-retention-days": "10"
                }
            }
        }
    ]
}

Save it to the policy.json file and apply using the following command:

aws s3api put-bucket-policy --bucket my-bucket-with-object-lock --policy file://policy.json

IONOS Object Storage is fully compatible with the S3 protocol, and once properly configured, it can be used to manage buckets and objects with existing S3 clients. Terraform is HashiCorp's infrastructure-as-code tool. It lets you define resources and infrastructure in human-readable format, declarative configuration files and manages your infrastructure's lifecycle. Using Terraform has several advantages over manually managing your infrastructure.

To use IONOS Object Storage with AWS Terraform Provider, Configure AWS Terraform Provider. For more information, see Examples.

Basic Object Storage Bucket Examples

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.50.0"
    }
  }
}

provider "aws" {
  region                      = "de"
  access_key                  = "access_key_here"
  secret_key                  = "secret_key_here"
  # all these checks need to be skipped for an s3 external provider
  skip_credentials_validation = true
  skip_requesting_account_id  = true
  skip_region_validation      = true
  endpoints {
     s3 = "https://s3-eu-central-1.ionoscloud.com"
  }
}

resource "aws_s3_bucket" "tf_bucket_name_here" {
  bucket = "unique_name_here"
  tags = {
    Name        = "my bucket name tag"
    Environment = "dev"
  }
}

Object Storage bucket with Object Lock enabled

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.50.0"
    }
  }
}

provider "aws" {
  region                      = "de"
  access_key                  = "access_key_here"
  secret_key                  = "secret_key_here"
  # all these checks need to be skipped for an s3 external provider
  skip_credentials_validation = true
  skip_requesting_account_id  = true
  skip_region_validation      = true
  endpoints {
     s3 = "https://s3-eu-central-1.ionoscloud.com"
  }
}

resource "aws_s3_bucket" "backup_bucket" {
  bucket = "unique_name_here"
  tags = {
    Name        = "backup bucket"
    Environment = "dev"
  }
 object_lock_configuration {
    object_lock_enabled = "Enabled"
    rule {
        default_retention {
            days  = 10
            mode  = "COMPLIANCE"
          }
      }
  }
}

Object Storage bucket with Versioning enabled

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.50.0"
    }
  }
}

provider "aws" {
  region                      = "de"
  access_key                  = "access_key_here"
  secret_key                  = "secret_key_here"
  # all these checks need to be skipped for an s3 external provider
  skip_credentials_validation = true
  skip_requesting_account_id  = true
  skip_region_validation      = true
  endpoints {
     s3 = "https://s3.eu-central-1.ionoscloud.com"
  }
}
resource "aws_s3_bucket" "example" {
  bucket = "unique_name_here"
}

resource "aws_s3_bucket_versioning" "example" {
  bucket = aws_s3_bucket.example.id

  versioning_configuration {
    status = "Enabled"
  }
}

The following information must be specified in your Terraform provider configuration hcl:

1. AWS Access Key ID: Insert the Access Key. In the DCD, go to Menu > Storage > IONOS Object Storage > Key management and check the Access keys section to find the essential details.

2. AWS Secret Access Key: Paste the Secret Key. In the DCD, go to Menu > Storage > IONOS Object Storage > Key management and check the Access keys section to find the essential details.

3. skip_credentials_validation: When set to true, it skips Security Token Service validation.

4. skip_requesting_account_id: The account ID is not requested when set to true. It is useful for AWS API implementations that do not have the IAM, STS API, or metadata API.

5. skip_region_validation: The region name is not validated when set to true. It is useful for WS-like implementations that use their own region names.

6. endpoints: For the list of IONOS Object Storage Service endpoints, see Endpoints.

provider "aws" {
  region                      = "de"
  access_key                  = "access_key_here"
  secret_key                  = "secret_key_here"
  # all these checks need to be skipped for an s3 external provider
  skip_credentials_validation = true
  skip_requesting_account_id  = true
  skip_region_validation      = true
  endpoints {
     s3 = "https://s3-eu-central-1.ionoscloud.com"
  }
}

Veeam Backup & Replication offers two options for backup to the Object Storage:

1. Direct backup to Object Storage

2. Backup to Object Storage as a capacity tier in the Scale-out Backup Repository (SOBR).

Direct backup to Object Storage

Follow these steps to configure direct backup:

1. Add Object Storage Repository: In Veeam Backup & Replication, navigate to the backup infrastructure and add a new object storage repository, selecting S3 compatible and providing your IONOS Object Storage credentials. We recommend using the eu-central-3 region for Veeam backups.

2. Configure Backup Jobs: Set up or modify backup jobs to target the newly added IONOS Object Storage repository.

For more information, see Add Backup Repository.

Backup using SOBR

SOBR in Veeam enables you to create a highly flexible and scalable backup storage solution by combining multiple storage resources into a single repository. It allows moving data from performance to capacity tiers automatically to optimize storage usage and cost.

Follow these steps to configure SOBR with Object Storage:

1. Create Performance Tier: Add your primary, fast storage devices (local or network) as the performance tier in Veeam Backup & Replication.

2. Add Capacity Tier: Integrate IONOS Object Storage as the capacity tier, allowing Veeam to offload older backup files to cost-effective object storage.

3. Policy Configuration: Configure policies to define how and when data should be moved between the performance and capacity tiers.

In Veeam 12, both Performance and Capacity Tiers support multiple buckets without any limit and apply to users as follows:

• Existing users upgrading to v12 should consider setting up a new SOBR with multiple buckets, as Veeam does not redistribute existing VM backups across newly added buckets.

• For new users planning to integrate IONOS Object Storage in the Capacity Tier with a traditional SOBR configuration, it is advisable to start with multiple buckets.

Veeam automatically allocates VM backups across these buckets. While adding new buckets is possible later as well, Veeam does not reallocate existing VM backups to these new buckets; only new VM backups will utilize them. Utilizing multiple buckets in the Capacity Tier removes the necessity for multiple SOBRs.

Recommended settings

For more information, see Recommended Settings.

Veeam Version

The minimum version is Veeam 11a CP4 (11.0.1.126120220302,) which brings an important special fix when using Object Lock.

Object Storage

In May 2024, we introduced the eu-central-3 Object Storage region in Berlin, Germany. This region features contract-owned buckets, which provide enhanced performance and resilience. This new bucket type creates an easier opportunity for user management, since the bucket list is visible for all users of the contract, and the contract owner or administrators can assign permissions to view bucket contents. For more information, see Bucket Types and Endpoints.

Limit concurrent tasks

• This setting is available during the addition of the new Object Storage repository. For more information, see Configure repository details in Create Object Storage as an object repository in Veeam.

• You can also update the concurrent tasks limit for an existing Object Storage repository by following these steps:

  • Go to the Backup Infrastructure tab.

  • Click Backup Repositories.

  • Right-click on your Object Storage repository and choose Properties.

  • Select the checkbox Limit concurrent tasks to and set the value as follows:

    • Up to 10—for eu-south-2 region.

    • Up to 20—for all other regions.

Apply 8 MB blocks in the storage optimization setting

Veeam Backup & Replication allows you to configure block sizes for each backup job, which can significantly impact deduplication efficiency and incremental backup size. By default, blocks are compressed, typically achieving a compression ratio of about 50%.

• Smaller blocks can enhance deduplication; they increase the number of calls to the object storage, potentially affecting performance.

• Larger blocks reduce the number of storage calls and can increase throughput to and from IONOS Object Storage, improving overall backup performance.

Enable 8 MB blocks

For optimal performance with IONOS Object Storage, we recommend using 8 MB blocks. These blocks are unavailable in the interface by default and must be enabled via a registry key by following these steps:

1. Open the Registry Editor.

2. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication.

3. Add a new DWORD (32-bit) value named UIShowLegacyBlockSize.

4. Set the value of UIShowLegacyBlockSize to 1.

Change the storage optimization setting

To change the storage optimization setting, follow these steps:

1. Click the Backup section under Jobs.

2. Select the required backup job, right-click on it, and choose Edit in the menu.

3. Click Storage > Advanced and change the tab to Storage.

4. In the Storage optimization drop-down list, choose 8 MB marked as "not recommended”. Disregard this mark as it is the correct choice. This option must be there if you modify the registry setting as described in the previous section. Do not use a block size less than 4 MB.

5. Click Save as default at the bottom of the Advanced Settings screen.

Set the immutability retention period

The immutability retention period of the Object Storage Repository must be less or equal to the backup retention period of the backup job.

To check the immutability retention period, follow these steps:

1. Go to the Backup Infrastructure tab.

2. Click Backup Repositories.

3. Right-click Object Storage Repository and choose Properties.

4. Click Next upon seeing the Name setting and Account setting.

5. Set the number to 30 to Make recent backups immutable for setting.

Check the backup retention period

To check the backup retention period, follow these steps:

1. Click the Backup section under Jobs.

2. Select the required backup job, right-click on it, and choose Edit in the menu. You will see the Job Mode screen.

3. Click Storage in the left menu and check the number in the Retention policy setting.

Scaling scale-out backup repositories

Create a bucket for every 100 virtual machines or 200 TB of data to be backed up; Performance or Capacity Tier, depending on the use case.

In May 2024, we introduced the eu-central-3 Object Storage region in Berlin, Germany. This region features contract-owned buckets, providing enhanced performance and resilience. A new 92-character access key is required for this region.

To add a backup repository, follow these steps:

1. Create a new access key: Check your access key length in the Key Management. If it is 20 characters long, you need to create a new 92-character key compatible with all regions. For more information, see Generate a Key.

2. Create a new contract-owned bucket with an Object Lock: Create a new contract-owned bucket in the eu-central-3 region with Object Lock enabled. For more information, see Create a Bucket and refer to the "contract-owned buckets" section.

3. Create backup repository: Create an Object Storage as an object repository in Veeam. To do so, follow the steps in Create Object Storage as an object repository in Veeam.

Create Object Storage as an object repository in Veeam

To add a new object storage repository on Veeam Backup & Replication, follow these steps:

1. Navigate to the backup repositories. To do so, go to the Backup Infrastructure tab, and click Backup Repositories > Add Repository to open the wizard for adding new backup repositories.

2. Select repository type by following these steps:

• Enter a name and an optional description for the object storage repository.

• Select the Limit concurrent tasks to checkbox and set the values as follows:

  • Up to 10 – for the eu-south-2 region

  • Up to 20 – for all other regions

• Click Next.

3. Input the endpoint details as follows:

• Service endpoint: https://s3.eu-central-3.ionoscloud.com

• Region: eu-central-3

• Click Add to input the access and secret keys.

• Click Next.

4. Configure bucket and folders by following these steps:

• Enter the bucket name or browse and select from the list.

• Click Browse to create a new folder where backups will be stored.

• (Optional) Set the limit for used storage and enable backup immutability. The immutability retention period of the Object Storage Repository must be less or equal to the backup retention period of the backup job. For more information, see Set the immutability retention period.

• Click Next.

5. In the Mount server tab, keep the default values and click Next.

6. In the Review tab, click Apply and then click Next to continue.

7. Finalize the repository creation by reviewing the Summary and clicking Finish.

Next steps

Continue to Create a Backup Job.

In May 2024, we introduced the eu-central-3 Object Storage region in Berlin, Germany. This region features contract-owned buckets, providing enhanced performance and resilience. Note that a new 92-character access key is required for this region.

To move a backup repository to the eu-central-3 region, follow these steps:

1. Create a new access key: Check your access key length in the Key Management. If it is 20 characters long, you need to create a new 92-character key compatible with all regions. For more information, see Generate a Key.

2. Create a new contract-owned bucket with an Object Lock: Create a new contract-owned bucket in the eu-central-3 region with Object Lock enabled. For more information, see Create a Bucket and refer to the "contract-owned buckets" section.

3. Set up Veeam storage optimization: To do so, follow the steps in Set up Veam storage optimization.

4. Create backup repository: Creta an Object Storage as an object repository in Veeam. To do so, follow the steps in Create Object Storage as an object repository in Veeam.

5. Move the backup repository: You need to move the backup repository to the new Object Storage region. To do so, follow these steps:

• Right-click on the Backup Jobs name in the Object Storage section of the Backup tab and select Move backup.

• Specify the target repository to move backups to and click OK. The migration of your backup repository will start. The data will be transferred directly from one region to another.

Set up Veeam storage optimization

1. Click the Backup section under Jobs.

2. Select the required backup job, right-click on it, and choose Edit in the menu.

3. Click Storage, go to Advanced Settings and change the tab to Storage.

4. In the Storage optimization dropdown list, choose 4 MB or 8 MB (marked as "not recommended"). Disregard this "not recommended" mark that you see in the web interface.

5. (Optional) If you want to benefit from better performance, follow the instructions to enable 8 MB blocks:

• Open the Registry Editor.

• Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

• Add a new DWORD (32-bit) value named UIShowLegacyBlockSize.

• Set the value of UIShowLegacyBlockSize to 1. Now, the 8 MB block option will be available in the interface.

• To apply the new storage configuration as the default for all future backup jobs, click Save as Default at the bottom of the Advanced Settings screen. This will ensure the settings are automatically used for any new backup jobs created.

To create a backup job, follow these steps:

1. Click the Backup Job button and choose your workload type. For example, Windows computer.

2. Choose the Job Mode type as Workstation or Server and click Next.

3. Name the backup job and add an optional description. For example, back up to Object Storage eu-central-3and click Next.

4. Choose computers for backing up. Click Add and choose Individual computer.

5. Enter the computer’s IP address. Click the Add button to enter the Username and password. Click OK and Next.

6. Choose backup mode from the following options: Entire computer, Volume level backup, or File level backup and click Next.

7. Choose a backup repository from the drop-down menu. Update the Retention policy setting and click Next.

8. In the Guest Processing, keep the default settings and click Next.

9. Choose a Schedule for your backup and click Apply.

10. Check the Summary and click Finish.

Veeam Backup & Replication provides a comprehensive solution for data management, encompassing backup, recovery, and replication capabilities.

Quick Links