Of course, not all Symantec products licensed per device are sold or branded per user. At this point, our discussion of Symantec licensing models really starts to get interesting.
Although this adds a layer of complexity to these licenses, just remember that the tiers are simply pricing tiers. So, the underlying license type still typically determines the actual entitlements, but the price for each license is determined by the hardware on which the software will operate. However, note that exceptions do exist that cannot be covered in this guide. As one example, the NetBackup client is often licensed per physical machine for virtual machine systems — but, clients installed on IBM zSeries are licensed per virtual machine.
The pricing tiers are generally arranged based on hardware performance characteristics, like the number of populated processor sockets on the machine. The platform, or operating system, on which a product is deployed, can be a factor in price as well and usually limits the license models available. Each physical server needs to be licensed according to the proper server hardware tier.
Tier assignments are not impacted by virtualization or partitioning. But, when licensing virtual environments a number of additional factors may come into play, like the specific platforms and packages deployed in each virtual machine. Many products licensed per tiered server are also available under a tiered processor license, covered a bit later, and it is important to weight the cost and value between these options to decide which is better for a particular situation. For example, Storage Foundation HA on some Sun Fire servers may cost just a small fraction of, or well above, the per server cost when licensed per processor.
It all depends on the number of processors. Perhaps that server is subdivided into secure independent domains, and the software is only deployed on a small number of those machines. Remember to factor in not just the current hardware platforms and configurations, but plans for change and growth as well. It may also make sense from a license management perspective to align license metrics across several products from different vendors.
Tiered Operating System licenses apply to storage products like Storage Foundation deployed in Windows operating system environments, but not all Windows platform products licensed using the tiered device model can be licensed using operating system tiers. Some must be licensed using other tiered methods.
For those products that can be acquired under this model, the pricing tiers correspond to the edition of the Windows Server operating system running on the server rather than according to the hardware. Licenses can also be downgraded across editions, i.
Besides the lack of hardware-based tiers, this model is also special because of unique virtual use rights that line up with those granted by Microsoft. Finally, the Tiered Processor license functions much the same as typical processor-based examples that are probably already familiar to most, but again with the added construct of pricing tiers. Similar to many other major publishers, Symantec counts multicore chips as a single processor.
So, to determine the number of licenses required to cover any single machine, just count up the number of occupied processor sockets. The tiered processor type, like other processor types, can seem expensive, but it offers greater license portability as well as greater deployment flexibility compared to the tiered server model. For instance, licensing per tiered processor may make more sense in situations where it is desirable to run a product on just a small part of a larger subdivided server, as already discussed.
And since there are far fewer processor tiers than sever tiers, it also has advantages in situations where it is important to have the option to transfer a license to a different server over time. The fourth tiered type, known as NProcessor , functions much like the tiered processor model but without the elaborate pricing tiers.
That is, products licensed this way are licensed on a per-processor basis. However, when it comes to the storage and high availability products typically licensed by tier, only certain platforms, e. Further, Symantec appears to be moving away from this model for many of those products. A front-end terabyte is essentially the actual amount of protected data, regardless of the size of the volume upon which that data resides.
When dealing with NetBackup that amount has certain exclusions, like data retained by NetBackup that has been removed from a client. Symantec recently introduced a simplified licensing model based entirely on a single front-end terabyte meter, called the NetBackup Platform. Showing results for. Search instead for. Did you mean:. Sign In. Backup Exec Licensing. Go to solution. Hello, I would like to clear the thing Licensing. What licenses should we exactly purchase to be able to backup , the server and the NAS.
Do you need an extra license for the NAS? Because we are going to buy licenses for many customers please only official answers. Kind Regards Spiros Solved! All forum topics Previous Topic Next Topic. Accepted Solutions. CraigV Level 6. Partner VIP Accredited. Hi, If you're going to mount LUNs from the NAS that store data on it from a server perspective, then you'd just need the media server license and any application agents.
Hi CraigV, thank you very much for your time. What do you mean with "any application agent"? Hello both, thank you very much for your time. Kind Regards, Spiros. Additionally, Backup Exec installation media also has a Remote Administrator feature which can be installed on a remote computer or workstation to administer the Backup Exec server remotely. Backup Exec installations can have one or more Backup Exec servers, which are responsible for moving data from one or more locations to a storage medium, including cloud, disk, tape, and OST device.
The data may be from the local system or from a remote system. A single Backup Exec server is assigned the standalone Backup Exec server role. Each server runs the Backup Exec software and the services that control backup and restore operations of multiple clients.
Each Backup Exec server maintains its own Backup Exec database, media catalogs, and device catalogs. Large environments may contain multiple Backup Exec servers responsible for backing up many different client systems. Backup Exec servers in large environments can run independently of each other if each server is managed separately. Separate server management may not be an issue if there are only two or three Backup Exec servers, but it can become unwieldy as the environment grows.
CASO ensures that everything throughout the network is protected by a single system that can be managed from one console [2] and also balances the workload across all Backup Exec servers in the environment. The CASO configuration simplifies the management and monitoring of enterprise-level environments. Backup Exec does not have support for sending data streams from multiple parallel backup jobs to a single tape drive, which Veritas refers to as multiplexing.
0コメント