Client updates stored locally on hub server

IBM Storage Protect Operations Center should provide the ability to deploy Backup-Archive client updates from a local repository or from packages manually imported into the IBM Storage Protect environment. The current dependency on Internet-accessible catalogs and external download sources can prevent customers with restrictive security policies from using the automated client deployment functionality.

This limitation is especially relevant for the banking and financial sector. Most banking organizations do not allow critical infrastructure components to access external resources directly. Backup servers are often placed in restricted network segments because they contain or provide access to business-critical recovery data. Allowing these systems to connect to public Internet sources may increase the attack surface and may not be accepted by internal security, risk, compliance, or audit teams.

The proposed solution should support a controlled offline workflow:

1. Client update packages and catalog metadata are downloaded on an authorized Internet-connected system.

The packages are verified using checksums, digital signatures, or another authenticity validation mechanism.

The approved files are transferred into the restricted environment according to the customer’s security procedures.

An administrator imports the packages into a local IBM Storage Protect repository.

Operations Center recognizes the locally available versions and allows administrators to schedule their deployment to selected clients.

No direct Internet connection is required from the hub server, spoke servers, Operations Center, or protected client systems.

Ideally, the local repository should support both a fully disconnected model and an internal HTTP or HTTPS mirror. Customers should also be able to control which client versions are published internally, retain multiple approved versions, and remove packages that are no longer authorized for deployment.

This enhancement would provide several benefits:

• support for air-gapped and restricted environments;

compliance with banking-sector security policies;

lower exposure of backup infrastructure to external networks;

full customer control over package validation and release approval;

predictable and repeatable deployments across large client estates;

clear separation between package acquisition and package deployment;

better alignment with formal change-management and audit processes.

Without local package support, customers may be forced to update Backup-Archive clients manually or build custom software-distribution processes. This reduces the value of the centralized deployment functionality available in Operations Center and introduces additional administrative effort and inconsistency. A supported offline deployment model would make the feature practical for a much broader group of enterprise customers.