Nodeum Docs - Administration
Welcome to the Product Documentation for Nodeum.
Find information on the details of using tool through the browser interface, the ND Client and our own RESTful API.
The Console is available to access and manage the platform.
Nodeum provides a user-friendly graphical console and gives different monitoring options (email, SNMP, etc.) on storage activities, system activities and much more.
It is a Web Based Interface designed in HTML5, Nodeum provides the best of its capabilities in using Chrome or Firefox as browser.
A rich graphical user interface that provides similar functionality to the nd command line tool with additional features.
The Nodeum Console is available to handling administration tasks like Workflow Definition, Storages configuration, Reporting and Log Monitoring, or any overall system Configuration. This interface is embedded as part of the Nodeum Services.
The Administrator user has a global overview about the Data Management activities.
By default, several widgets are display with information about the files, volume and task report. You can add, remove or change the place of the widget.
Nodeum builds automatically a catalog of files and folders available across the different reachable storage systems.
Through this interface, the user can easily access any information or data in the storage spaces either if the storage technologies are NAS, S3 or Tape systems.
It allows a fast search and finds, using both embedded files and business metadata.
The catalog uses the end user access rights to provide an easy and secure self-service portal. Any end user is allowed to manage their data straight through the Nodeum Ecosystem.
An indexation engine is natively available for indexing all metadata information about contents, tasks, reports and data management statistics. This engine allows fast search in the overall solution because, instead of searching text, it searches an index.
The solution includes a Solr-indexed engine and Nodeum indexation engine service. This last service is designed for exporting all defined information from SQL and NoSQL databases to Solr for creating the index.
In the case where End-Users prefer to execute a data movement directly from the Catalog, they can use the basket to launch Data Archiving or Data Protection workflow from there. The benefit for the End-Users is to accelerate the operation in leverage the search and filtering of the Catalog.
Administrators needs to control the storage location of their data. This feature includes a system with dynamic reporting.
This feature provides reports & KPI showing what is the exact storage usage based on criteria such as: creation date, last access date and location of the data. In addition, it provides a more detailed overview by users, user groups, categories, data types and file sizes.
Also, it will give a deeper drill down into users and user groups, data type categories and file sizes.
Global overview about data stored on Storage and classify by type (NAS, Cloud, Tape).
Example: Information about Storage Management of Secondary Storage (NAS, Cloud/S3 and Tape)
Understand how is the effect of your Data Archiving (Active Archive) policies. What type of data do you have and on which type of Storage? This board presents insights about the “life” of your Data. Information based on the size and based on the type of your files are available.
Example : Information about Storage Management of Container with active archive Workflow.
Nodeum provides into the tape reporting feature some relevant information about tape . This board is very useful to see some information about tape. The objective is to improve the reliability of the data integrity when using magnetic tapes and to facilitate the overall tape management. The information are collected by Nodeum from the TapeAlert error reporting. This is an industry standard that provides a status monitoring and problem detection capability for tape devices and tape directly from the tape and the tape drive.
This report can be exported in pdf or csv.
This calculator helps enterprise to understand which data are often used or not and helps to build the best scenario for the data policy of your organization depending on the usage and the hardware you have or you want to buy. This calculator helps you to simulate different scenarios and to see directly the impact in terms of ROI.
3 types of workflows are available:
Automate secure migration of your data between your different storage systems. Individual file level reporting for audit purposes.
Move selected data to secondary storage tier ((NAS, Cloud, Tape) to decrease the capacity of expensive primary storage while keeping online access to your data. Individual file level search and access.
User keep the data accessible from a container by any authorized users.
User centric backup approach to eliminate disruption and ensure business continuity with a reliable and easily accessible offline archive. Individual file level search and retrieve.
For every workflow, you need to define your data Policy.
In this section, you retrieve all information about the system information and configuration of the platform.
In this section, you retrieve all information about the system information and configuration of the platform.
This section provides:
This panel provides a feature to handle a backup of Nodeum Configuration.
In case of failure of your server, reinstall Nodeum software and restore backup to continue data management activities.
The Backup includes all of these components :
|
Components |
Description |
|
|
All databases |
This includes SQL and NoSQL information : file catalog, metadata, task execution history. |
|
|
S3 - Swift API Keys |
Authentication Key Credentials of S3 and Swift storage provider. |
|
|
Data enrichment API Keys |
Authentication Key Credentials of Machine Learning provider. |
|
|
Tasks execution log reports |
History of each files processed per task. |
|
|
Licence Key |
Nodeum Encrypted License Key |
|
There are two different types of backup available :
|
Type |
Definition |
|
Full Backup |
Backup everything every time |
|
Incremental Backup |
Backup only the difference since the last backup |
A full backup is recommended to be executed once a week, others can be in incremental mode.
Different scheduling options are available :
|
Option |
Definition |
Comments |
|
Timezone |
The schedule can be defined based on a different timezone |
Defined by default, it will be current system timezone |
|
Recurrence |
Once |
Defined by default , there is no recurrence selected |
|
|
Every |
Minute - Day - Month - Year |
|
|
Expands |
Expand the scope of the recurrence |
|
|
Count Option |
Number of backup |
The network interface(s) and IP configuration(s) are managed directly in the Operating Systems.
Our solution deployment will use the configured interface configuration but will also allow different form of security hardening in term of firewall and network interfaces segregation.