Glossary
This glossary provides definitions for key terms and concepts used throughout the Superna 5.x documentation.
General Terms
| Term | Definition | Additional Information |
|---|---|---|
| Alarms | Notifications that alert administrators about system events requiring attention | Help identify and respond to issues promptly |
| Auditing Devices | Storage systems configured for security monitoring and data protection | After adding devices to inventory, you can configure security monitoring and auditing features to protect your data and meet compliance requirements |
| Jobs | Scheduled or on-demand tasks that perform specific operations in the system | Jobs automate routine operations, provide system maintenance, and run administrative tasks |
| Notifications | Messages that inform users about system events, updates, or actions | Keep users informed about relevant activities |
Threat Detection & Security (DSE) Terms
| Term | Definition | Additional Information |
|---|---|---|
| Events/Incidents | Occurrences of security-related activities that may require investigation | Provide details about security-related actions and their impacts |
| Snapshots (Files) | Point-in-time copies of files used to recover data after a security incident | Supported on Vast, Qumulo, PowerScale, Pure FB FA systems |
| Threat Detections | Identified suspicious activities that may pose security risks | Used to track and respond to potential security incidents |
| Versioning (Objects) | Feature that maintains multiple versions of objects for recovery purposes | Supported on AWS, VAST, Pure FB, S3, Qumulo, PowerScale, ObjectScale |
Disaster Recovery (DR) Terms
| Term | Definition | Additional Information |
|---|---|---|
| Disaster Recovery | A set of policies, tools, and procedures to enable the recovery or continuation of vital technology infrastructure and systems following a natural or human-induced disaster | Ensures business continuity and minimizes downtime during disruptive events |
| Failover | The process of switching to a redundant or standby computer server, system, or network upon the failure or abnormal termination of the previously active application, server, system, or network | Provides high availability and reliability by automatically or manually transferring control to a backup system |
| Readiness | The state of being prepared for disaster recovery operations | Indicates system preparedness for failover |
| RPO (Recovery Point Objective) | The maximum acceptable amount of data loss measured in time | Defines how much data loss is acceptable in a disaster |
| RTO (Recovery Time Objective) | The maximum acceptable time to restore system functionality after a disaster | Defines the time window within which services must be restored |
| Source | The primary system or data source in a replication relationship | Contains the original data to be protected |
| Target | The secondary system or destination in a replication relationship | Receives replicated data from the source for disaster recovery |
PowerScale Specific Terms
| Term | Definition | Additional Information |
|---|---|---|
| Access Zone | Logical containers within a PowerScale cluster that provide a secure, multi-tenant storage environment by isolating users, groups, directories, and authentication providers | Enables granular control over data access and ensures compliance with security and regulatory requirements |
| DFS Namespace | Distributed File System (DFS) namespace allows the aggregation of shared folders located on different servers into a logically structured hierarchy | Simplifies access to shared data by providing a unified directory tree, enhancing data organization and accessibility |
| IP Pool | A collection of IP addresses assigned to nodes within a PowerScale cluster, allowing for network traffic management and failover capabilities | Ensures network connectivity and load balancing, and facilitates failover by dynamically assigning IP addresses to available nodes in case of a failure |
| SyncIQ Policy | A data replication policy used in PowerScale systems to replicate data between clusters for disaster recovery purposes | Ensures that data is continuously synchronized between primary and secondary systems to maintain data availability during failover |
Qumulo Specific Terms
| Term | Definition | Additional Information |
|---|---|---|
| Replication Relationship | A configuration in Qumulo systems that manages the replication of data across different clusters to ensure data availability and integrity in disaster recovery scenarios | Ensures continuous data synchronization and quick recovery by maintaining consistent copies of data across multiple locations |
VAST Specific Terms
| Term | Definition | Additional Information |
|---|---|---|
| Protected Path | A configuration in VAST Data systems that specifies the data paths to be protected and replicated for disaster recovery purposes | Ensures critical data paths are continuously monitored and replicated, enabling quick recovery in case of failures |
| Tenant | A logical segmentation within VAST Data systems that allows for multi-tenancy by isolating data, users, and policies | Provides secure and isolated environments for different departments or customers within the same storage infrastructure |
| Virtual IP Pool (VIP) | A set of IP addresses used by VAST Data systems to manage network traffic and failover between nodes | Facilitates high availability and network redundancy by enabling dynamic IP address assignment during failover events |