Requesting a cost estimation for STaaS
To request a cost estimation, follow the procedure below:
Follow the STaaS setup procedure, but only up to the point where your system is registered to use STaaS.
Deploy the STaaS Migration Script package from the Catalog.
In the Automation module in DataMiner Cube, locate the CloudStorageMigration script and execute the script.
Note
- When you run the Automation script and there are Failover pairs in the cluster, make sure the main Failover Agents (i.e. the first Agent in the Failover configuration) are the active ones. Otherwise, the Automation script will not function correctly.
- To do the cost estimation for a cluster, you only need to execute the script on one Agent.
Important
For a separate Cassandra setup (see storage options overview), cost estimation is supported from DataMiner 10.4.0 [CU17], 10.5.0 [CU5], and 10.5.8 onwards.
Initialize the test run:
Optionally, configure a proxy for the test run if necessary. This is supported from DataMiner 10.4.6 onwards.
Click Start Test Run to initialize the test run.
Let the script run for 24 hours without restarting the DataMiner System (DMS).
After the 24-hour period, stop the estimation process:
Locate the CloudStorageMigration script and execute the script.
Click Stop Migration/Replication to stop the test run.
Note
This 24-hour period is not mandatory, but we recommend this to be able to extrapolate the data from a daily consumption to a monthly consumption.
After this, at approximately 2 AM UTC, you will be able to view your cost estimation in the Admin app, under Overview > Usage for the relevant organization.
Note
You will only be able to see the Usage module if you are an Owner or Admin of the organization.
If you have any questions regarding this cost estimation, please contact support@dataminer.services.
Important
Cost estimations can currently only be performed for the West Europe, UK South, Southeast Asia, and Central US regions.
Tip
To optimize the cost efficiency of a STaaS solution, adhere to the best practices to prevent storing unnecessary data with Automation scripts or with connectors.