Table of Contents

Storage as a Service (STaaS)

With DataMiner Storage as a Service, you can connect your DataMiner System to a scalable, easy-to-use cloud-native storage platform, without the effort of setting up and managing your own storage databases.


Advantages of DataMiner Storage as a Service (STaaS) include:

  • Fast, secure, and reliable storage

  • Easy and flexible configuration

  • Outstanding performance, scalability, and redundancy

  • Cost-effectiveness

  • Safe and secure data


If you have any questions or need support with the STaaS feature, contact

Setting up STaaS

For a self-hosted DataMiner System, follow the steps below to set up STaaS.

  1. Upgrade your DataMiner System to version 10.3.10 [CU1] or higher.


    We recommend always upgrading DataMiner to the latest available version to get the latest features and performance updates.

  2. Make sure your DataMiner System is connected to

  3. Make sure that all Agents in your DataMiner System have internet access.


    All communication for STaaS happens through HTTPS. The DataMiner System initiates all outbound connections.

  4. Make sure you have at least DataMiner CloudGateway 2.8.0 installed on the system. See Upgrading nodes to the latest DxM versions.

  5. Contact your Skyline representative or to register your system to use STaaS.


    If you have a specific preference with respect to the data location and redundancy setup, let us know when you register your system.

  6. Wait until you receive confirmation that the registration is completed.

  7. Optionally, contact your Skyline representative or to migrate your existing data to STaaS.

  8. On each DataMiner Agent in the cluster, in the C:\Skyline DataMiner folder, open DB.xml and edit it to look like this:

    <?xml version="1.0"?>
    <DataBases xmlns:xsi="" xmlns:xsd="" xmlns="">
       <DataBase active="true" local="true" search="true" cloud="true" type="CloudStorage"/>
  9. Restart DataMiner to begin using STaaS.

Data location and redundancy

DataMiner STaaS relies on Azure Storage, which stores multiple copies of your data to make sure it is always available even in case outages or disasters occur. Different storage redundancy setups are possible. STaaS supports zone-redundant storage and geo-redundant storage. When you contact Skyline to register your system to use STaaS, you can include your preferences as to the region(s) where your data should be stored and the type of storage redundancy that should be used.

  • Zone-redundant storage (ZRS) copies your data synchronously across three Azure availability zones in one region. Each availability zone is a separate physical location with independent power, cooling, and networking. By default, DataMiner STaaS uses ZRS.

  • Geo-redundant storage (GRS) copies your data synchronously three times within a single physical location in the primary region and then also copies your data asynchronously to a single physical location in the secondary region. Only specific regions can be combined in such a setup, e.g. if the primary region is Switzerland North, the secondary region can only be Switzerland West. For an overview of the supported regions, see Azure paired regions. If you wish to use DataMiner STaaS with GRS, contact


For detailed information, see Azure Storage redundancy on

Data resilience and backups

To ensure data resilience for potential recovery scenarios, protecting against user errors and accidental changes, your data is backed up with a granularity of 1 day. Backups are stored for 30 days.

  • Daily backups: STaaS performs backups with a granularity of 1 day and maintains a 30-day rolling snapshot of your data.

  • Data restoration and support: In the event a rollback is necessary, our support team will assist you. To submit a rollback request, contact the support team by sending an email to They will guide you through the necessary steps to ensure a successful data restoration.

Data security and availability

With STaaS, the data for a specific DMS is isolated in a logical partition. You can only ever access the logical partition dedicated to your own DMS, and all partitions are strictly isolated from each other.

To access your data, you use a connection authenticated with a Service Principal. With this connection, you can only access the logical partition dedicated to a specific DMS, which means that all data of a DMS is strictly isolated.

The data is encrypted both at rest and in transit.

If ZRS is used, STaaS has an expected availability of 99.90%. With GRS, it has an expected availability of 99.95%. For more information, please contact


To migrate existing data to STaaS, the following limitations apply:

  • Migrating logger tables is supported from DataMiner 10.3.11 onwards for systems using a dedicated clustered storage setup, and from DataMiner 10.3.12 onwards for systems using a Cassandra database per DMA.
  • Migration of a setup with multiple OpenSearch/Elasticsearch clusters is not yet supported.
  • Migration from a MySQL setup is not yet supported.

In addition, the following other limitations currently apply:

  • Jobs, Ticketing, and API Deployment data are not supported.

  • The following indexing engine functionality is not supported: Alarm Console search tab, search suggestions in the Alarm Console, aliases, and aggregation.

  • Direct queries from DataMiner Cube to the database are not supported.

  • The SLReset tool is not supported.

  • Exporting trend data to a .dmimport file is not supported.

  • Proxy and DMZ setups are currently not supported.

  • The autoincrement tag on logger tables is not supported.

  • DOM queries can be slower depending on the number of DOM records and the complexity of the query. This limitation will be removed in the near future.



If you experience any issues during setup or while using Storage as a Service, and you cannot resolve these with the procedures below, contact

Cloud connection lost

Under normal circumstances, CloudGateway refreshes the cloud session automatically. However, if CloudGateway is down for longer than three days, for example because the server is down, the cloud session will become invalid. This will cause DataMiner startup to fail.

When you encounter this issue, you will find entries similar to the examples below in the SLDBConnection.txt log file:

2023/10/02 14:04:23.458|SLDBConnection|SLCloudStorage|INF|0|6|2023-10-02T14:04:23.442|FATAL|DataGateway.CloudStorage.CloudStorage|CloudSettings could not be retrieved from the cloud. Retrying in 00:00:05. Exception: SLCloudStorage.Repositories.Exceptions.CloudSettingsRepositoryException: Failed to do GetCloudAccessTokenRequest. Received the following error messages: { "message": "The Service Principal of this DMS is expired (3/14/2023 8:09:51 AM +00:00) but should soon be refreshed automatically." }

2023/10/02 14:05:33.981|SLDBConnection|SLCloudStorage|INF|0|6|2023-10-02T14:05:33.980|FATAL|DataGateway.CloudStorage.CloudStorage|CloudSettings could not be retrieved from the cloud. Retrying in 00:00:05. Exception: SLCloudStorage.Repositories.Exceptions.CloudSettingsRepositoryException: Exception while doing GetCcaGatewayConfigRequest. ---> System.AggregateException: One or more errors occurred. ---> DataMinerMessageBroker.API.Exceptions.SubscriptionException: No responders are available for the request. ---> NATS.Client.NATSNoRespondersException: No responders are available for the request.

To resolve this issue, use the following workaround:

  1. Open SLNetClientTest tool.

  2. Connect to the DMA with SLNetClientTest tool

  3. Select Offline Tools > CcaGateway (offline) > Renew cloud session and complete the renew process.


    As the renewal of the Service Principal (SP) token is managed by a cloud service, it can take a few minutes before the renewal is fully synced.

  4. Wait a few minutes and then restart the DMA.The issue should be resolved now.


If you have a DataMiner System consisting of multiple DMAs, it is sufficient to do this on one of the DMAs.

API Deployment Manager failed to initialize

When the APIDeployment option is still enabled in SoftLaunchOptions.xml, the following alarm will be shown in Cube:

APIDeploymentManager failed to initialize, retrying. Check SLAPIDeploymentManager.txt for additional information.

In the SLDBConnection.txt log file, the error will look like this:

2023/10/10 20:30:18.308|SLDBConnection|SLDataGateway.Repositories|INF|0|354|2023-10-10T20:30:18.302|ERROR|Repository.RepositoryStorageProvider.DeployerToken|Refreshing storage [failed]: SLDataGateway.API.Types.Exceptions.StorageTypeNotFoundException: No storage type found for DataType: DeployerToken

To resolve this issue, remove the APIDeployment option from SoftLaunchOptions.xml.

Connector-specific issues

Some connector versions may contain a bug that causes a lot of parameter sets to be saved to the database. In the interest of saving cost and reducing load, we therefore recommend using the latest version available for most connectors.

This issue is known to occur with the following connector versions: