No results found. Try different keywords.
Enter at least 3 characters to search...
Home » Network License » Veritas » Veritas NetBackup
Built for enterprise-scale data protection, Veritas NetBackup helps IT teams standardize backup and recovery across physical servers, virtual machines, databases, and cloud/SaaS workloads, with centralized policy control, resilient cataloging, and predictable restores for both everyday incidents and major recoveries.
The Veritas NetBackup license is the entitlement layer that determines what you can protect and how your usage is measured under your agreement. In many enterprise deployments, NetBackup is purchased using a capacity model that measures Front-End Terabytes (FETB), the amount of source data protected, so accurate sizing starts with your protected-data total (plus a realistic 12–24 month growth buffer). The commercial choice typically comes down to selecting the right edition/tier for your environment and aligning it to your scope: core infrastructure (VMs/physical), application and database workloads, and any cloud/SaaS protection you plan to include. After purchase, entitlements are delivered to your organization through the Veritas entitlement process (VEMS), where administrators can access downloads and generate the required licensing artifacts. Operationally, the goal is simple: match the entitlement meter to how you actually back up (capacity vs special scope), confirm term length, and ensure the right coverage for retention, security requirements, and restore expectations, so renewals remain predictable and you don’t discover gaps mid-incident.
At a high level, Veritas NetBackup is built around a centralized control plane and policy engine that coordinates backups, catalogs backup metadata, and executes recoveries across your estate.
If you’re selecting Veritas NetBackup, ordering is mainly driven by:
NetBackup is typically chosen for enterprise and multi-site environments that need scalable policy control and predictable recovery.
Protected TB (now + growth), workload types, retention targets, and storage destination.
Yes—licensing can be handled via offline file transfer workflows, and the platform can be operated within controlled environments (design dependent).
Protected capacity (FETB), workload scope, retention/compliance requirements, and term/support level.