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 corresponding to your setup:

    • For setups without proxy, use the following configuration:

      <?xml version="1.0"?>
      <DataBases xmlns:xsi="" xmlns:xsd="" xmlns="">
          <DataBase active="true" local="true" search="true" cloud="true" type="CloudStorage"/>
    • For setups with proxy (this requires DataMiner 10.4.5 or higher), use the following configuration, filling in the fields as required:

      <?xml version="1.0"?>
      <DataBases xmlns:xsi="" xmlns:xsd="" xmlns="">
          <DataBase active="true" local="true" search="true" cloud="true" type="CloudStorage">
                <Address>[Enter Address Here]</Address>
                <Port>[Enter Port Here]</Port>
                <UserName>[Enter UserName Here]</UserName>
                <Password>[Enter Password Here]</Password>

      If the proxy does not require authentication, you can leave the UserName and Password fields blank or remove them.

  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.


DataMiner STaaS's standard supported regions are West Europe (The Netherlands), UK South, North Central US, UAE North, Southeast Asia (Singapore), and Australia East. Choosing regions outside this standard list will incur additional charges.

  • 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. GRS is available upon request, but will result in additional charges. 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


It is not yet possible to configure time-to-live (TTL) values for STaaS. In the table below, you can find the default TTL values for each data type.

Data type TTL
Real-time trending 7 days
Average trending (short) 3 months
Average trending (medium) 2 years
Average trending (long) 10 years
State changes 5 years
Spectrum traces 1 year


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

  • Migration is supported in 10.4.0 and the latest available 10.4.x feature release.

  • Migration of a setup with multiple OpenSearch/Elasticsearch clusters is not yet supported.

  • Migration from a MySQL setup is not yet supported.

  • Migration using a proxy is supported from DataMiner 10.4.6 onwards.

  • If you start the migration while an element with a logger table is stopped, the data of that element will not be migrated.

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.

  • Custom configuration of TTL values is not yet supported.

  • 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.

  • 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.


For troubleshooting information related to STaaS, see Troubleshooting STaaS issues.


If you experience any issues during setup or while using Storage as a Service, and you cannot resolve these using the available troubleshooting information, contact