NSS API vs NBU API Use Cases and

NSS API vs NBU API

Use Cases and Personas

3 Core Baa. S (aka NSS) Use Cases Use Case 1 – Baa. S for end-users / Use Case 2 - As Use Case 1 with machines provisioning integration (v. Realize) Use Case 3 - Baa. S integration with existing Portal / Process, + End-user self-service to accommodate “backup services” As Use case 1 & automate new machines to backup policies Add Baa. S to existing services Portal NSS ✔ NSSAPI ✔ NBU API ✖ NSS ✔ NSSAPI ✔ (NBU API ✔) 3 Copyright © 2015 Symantec Corporation

Baa. S Personas Who are they? Persona End User/Consumer Use Case(s) 1 What are their Challenges? Convenience, Simplification, Personalization, Assurance Backup/Systems/Virtual/Cloud… Administrator Operations Team 1&2 More Automation, Secure Transaction, Ease of Integration, Off-Load Repetitive Work, Policy Management, Assurance Architects/Developers – New! 2&3 Time to Value, Total Cost of Ownership, Open Standards, Risk Reduction, More Agile, 4 Copyright © 2016 Veritas Technologies LLC

What are some notable (out-of-box) Baa. S capabilities? 5 Baa. S Application Function NSS API NBU API Prebuilt Services Backup Now Protect Machine Unprotect Machine Restore VM Restore File Yes No (Must be built) Policy Management Group polices of the same client Grouping by organizational tenant Policy lifecycle management Yes No Commercially Supported Yes (Both Baa. S & API) No (API only) Multi Master Server Aggregation Yes (NSS manages comms across unlimited Masters) No (Developer manages comms across each Master Server) Legacy NBU Version Support for NBU 7. 6. 1 and above NBU 8. 0 and above Copyright © 2016 Veritas Technologies LLC

Baa. S capabilities – continued… 6 Baa. S Application Function NSS API NBU API Broad Policy Type Support Physical Machines Virtual Machines Cloud Policy Types Virtual Machines Only Role-based Security and Auditing Yes No Multi-tenancy Yes (Native support & centrally managed) No (via RBAC on every master server through code) Availability Yes (3 rd Major Release) No (Version 1 release Q 2 2017 earliest) Utilization and Status Reporting Yes No Copyright © 2016 Veritas Technologies LLC

Understanding the Difference Choosing the right one for the job

Net. Backup vs NSS API’s Net. Backup • • We give you the pieces and the instructions Customers would manually use functions they want End result is up to the customer Will drive Veritas integration strategy Net. Backup Self Service • • We give you a complete Baa. S Application plus API Customers are up and running after install End result is fully functional Backup as a Service environment Offers features that focus on end user self service

“Do I need NSS after the release of NBU API’s? ” Yes = Leveraging means tapping prebuilt Baa. S Application capabilities thru the NSS API (NSS is built on top of NBU API) 9 Copyright © 2016 Veritas Technologies LLC No = Building Baa. S w/o NSS means building/coding and maintaining Baa. S capabilities – thru NBU API