Answer
BRMS excels at what it was built for: media management policies, retention classes, and save/restore orchestration across libraries, IFS objects, and system state within the IBM i environment itself. Where it typically falls short is at the edges, moving that data reliably off the physical system to a cloud target with proper encryption in transit, enforcing write-once retention that a compromised administrator account cannot shorten or delete, and rolling IBM i backup status into a single dashboard alongside Windows, Linux, or SQL Server backups the same IT team is also responsible for.
The practical pattern most shops land on is keeping BRMS as the policy engine on the IBM i side, since replacing it means rebuilding years of tuned media policies and retention classes, and layering a third-party product on top specifically for cloud offsite delivery, immutability, and cross-platform reporting. Buyers evaluating this combination should ask candidate vendors how cleanly their product reads BRMS-managed save files or hooks BRMS exit points, since a bolt-on tool that requires parallel, duplicate backup jobs adds cost and administrative burden without adding protection. The right integration should extend BRMS's reach rather than compete with it for the same save window.