Setting up STaaS

💡 TIPS TO TAKE FLIGHT
Don't have an existing DataMiner System yet? Watch this short video to see how to install a self-managed DataMiner System with STaaS from scratch.

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

Note

• This setup is not needed for DataMiner as a Service (DaaS) systems, as these automatically use STaaS.
• If you want to add a DMA to an existing DMS that uses STaaS, refer to Adding a DataMiner Agent to a DMS running STaaS.

Prerequisites

• DataMiner 10.4.0 [CU0]/10.4.1 or higher (preferably the latest available version). See Upgrading a DataMiner Agent.

  Tip

  We recommend always upgrading DataMiner to the latest available version to get the latest features and performance updates. To be able to use non-indexed logger tables, the minimum supported version is DataMiner 10.4.0 [CU5]/10.4.8.

• Your system must be connected to dataminer.services. See Connecting your DataMiner System to dataminer.services.

• All Agents in your DataMiner System must have internet access, either directly or through a proxy.

  If a firewall restricts outbound traffic, you can whitelist STaaS based on hostnames or based on IP addresses. See Hostnames and IP addresses to whitelist.

  Note

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

• DataMiner CloudGateway version 2.8.0 or higher. See Upgrading nodes to the latest DxM versions.

Hostnames and IP addresses to whitelist

If a firewall restricts outbound traffic from your DataMiner Agents, make sure STaaS traffic is allowed. You can whitelist this traffic either based on hostnames or based on IP addresses. In both cases, what you need to whitelist depends on your DataMiner version.

Tip

From DataMiner 10.6.12/10.7.0 onwards, the whitelisting configuration is much simpler, as no additional hostnames or Microsoft Azure IP addresses need to be requested from support. We therefore recommend upgrading DataMiner to version 10.6.12/10.7.0 or higher.

Whitelisting based on hostnames

The hostnames to whitelist depend on your DataMiner version:

DataMiner version	Hostnames to whitelist
DataMiner 10.6.12/10.7.0 or higher	Only https://*.dataminer.services/. No other hostnames are needed.
Earlier DataMiner versions	https://*.dataminer.services/, and in addition some extra hostnames, which depend on the region your system is registered for (and, for a geo-replicated (GRS) setup, its geo-redundancy pair region). These additional hostnames are not listed in this documentation. To get them, contact support@dataminer.services.

Note

https://*.dataminer.services/ is also required to connect your system to dataminer.services, so you may already have whitelisted it.

Whitelisting based on IP addresses

The IP addresses to whitelist depend on your DataMiner version:

DataMiner version	IP addresses to whitelist
DataMiner 10.6.12/10.7.0 or higher	Only the region IP address(es) listed below. No other IP addresses are needed.
Earlier DataMiner versions	The region IP address(es) listed below, and in addition the Microsoft Azure IP addresses for your region (and, for a GRS setup, its geo-redundancy pair region). These Microsoft Azure IP addresses are not listed in this documentation. To get them, contact support@dataminer.services.

The region IP address is determined by the region your system is registered for. For a geo-replicated (GRS) setup, you must whitelist two region IP addresses: the IP address of the primary region and the IP address of its geo-redundancy pair region.

In the table below, you can find the region IP address corresponding with each region:

Region	Region IP address
West Europe	20.76.71.123
UK South	20.162.131.128
Central US	64.236.64.187
Southeast Asia	20.247.192.226
Australia East	4.147.198.192

If the IP address for your region or geo-redundancy pair region is not listed above, contact support@dataminer.services.

Configuring STaaS

1. Register your system to use STaaS:

   1. Go to the Admin app.

   2. In the sidebar on the left, go to Organization > Overview.

   3. In the DataMiner Systems section, click the system you want to register.

   4. At the top of the page, in the Storage as a Service box, click the button Get Started with STaaS.

   5. Fill in your preferred region and click Initialize.

   Note

   Only owners of a DataMiner System can register their system.

2. Optionally, migrate your existing data to STaaS.

   If you do so, wait until the migration has been completed and verified before continuing with this procedure.

3. 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="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.skyline.be/config/db">
         <DataBase active="true" local="true" search="true" cloud="true" type="CloudStorage"/>
     </DataBases>
     

   • 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="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.skyline.be/config/db">
         <DataBase active="true" local="true" search="true" cloud="true" type="CloudStorage">
            <Proxy>
               <Address>[Enter Address Here]</Address>
               <Port>[Enter Port Here]</Port>
               <UserName>[Enter UserName Here]</UserName>
               <Password>[Enter Password Here]</Password>
            </Proxy>
         </DataBase>
     </DataBases>
     

     Note

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

4. Restart DataMiner to begin using STaaS.

Note

If you experience any issues during setup or while using Storage as a Service, refer to Troubleshooting - STaaS.