[ Applies to ] StorageGuard 9.x and later / All supported target systems / Windows and Linux
A StorageGuard deployment is made up of a master server, a database, the IT infrastructure being scanned, and two optional components: collector servers and the StorageGuard MCP server. This article describes what each component does, how data moves between them, and what software each one needs.
In this article
Deployment components
| Component | What it does | Status |
|---|---|---|
| Master server | A Windows or Linux server that runs the core StorageGuard services: the user interface, data processing, the risk detection engine, the API, and more. You access the user interface from a web browser over HTTPS. The master server can also act as a collector. | Required |
| Database | A PostgreSQL or Oracle database that stores system configuration and the data collected from your IT systems. You can install it locally on the master server or on a separate remote host. | Required |
| Collector server(s) | A Windows or Linux server that connects remotely to target IT systems and gathers the configuration data needed for analysis. Every collector reports back to the master server, which processes the data and runs risk detection. | Optional |
| StorageGuard MCP server | Connects StorageGuard to your organization's approved enterprise AI platform, such as OpenAI GPT, Microsoft Copilot, Anthropic Claude, or Google Gemini. It powers the StorageGuard AI Assistant, a chat panel in the user interface where authorized users can ask questions about StorageGuard data in natural language. Available in StorageGuard 10 and later. | Optional |
| Scanned IT infrastructure | The storage systems, backup systems, management servers, and SAN switches in your data centers that StorageGuard scans and analyzes. | Your systems |
Note: Because the master server can also act as a collector, a separate collector server isn't required for every deployment.
Tip: If your environment spans multiple locations, consider deploying one or more collector servers to gather data from each location.
Architecture diagram
The following diagram shows how the StorageGuard components connect to each other and to your infrastructure.
Figure 1: StorageGuard deployment architecture
How data flows
- The collectors (or the master server, acting as a collector) connect remotely to the scanned IT infrastructure and gather configuration data.
- Collectors send the gathered data to the master server.
- The master server stores the data in the database, processes it, and runs the risk detection engine.
- You review the results in the StorageGuard user interface from your browser, over HTTP or HTTPS.
Software requirements by component
| Component | Operating system | Required software |
|---|---|---|
| Master server | Windows or Linux | Apache Tomcat AdoptOpenJDK JRE (or a supported JRE) Database client software for your selected DBMS |
| Collector server | Windows or Linux | AdoptOpenJDK JRE (or a supported JRE) |
| Database | Master server or a remote host | PostgreSQL or Oracle |
|
StorageGuard MCP server StorageGuard 10 and later |
StorageGuard server | Node.js 22 or later An API key for your AI provider |
Note: Apache Tomcat and the JRE can be installed on the master server as part of the StorageGuard installation process.
Related articles
- StorageGuard system requirements
- Integrating the StorageGuard MCP server with an AI Assistant
- Installing StorageGuard on Windows
- Installing StorageGuard on Linux with Docker
[ Still need help? ]
Our support team is here for you. Submit a request and we'll get back to you.
Comments
0 comments
Please sign in to leave a comment.