Forum Discussion

rogerv111's avatar
rogerv111
Level 2
9 years ago

Which version of Backup Exec ? - V-ray or other

We have a client who needs a backup solution for a two host hyper-v (not clustered). Each host as a 2 socket cpu with a total of 4 cores each (so 8 cores in total). Each host runs two guest servers (all windows 2008 R2). There are two sql servers and one exchange server plus a file server.

The total capacity for backup will be about 4 TB, this capacity is likley to grow in the future by a few TB's more.

The backup server would either be a dedicated hardware server OR potentially an additional guest server on one of the hosts.

Can anybody offer advice on a cost effective Backup Exec solution ?. I’m not sure if an edition of Veritas Backup Exec v-ray is the best way or a standard Veritas  Backup Exec server with agents (or perhaps other). I've tried talking to sales but they seem quite reluctant to give a definitive answer and just point me to PDF's outlining what each version can do.

The only requirement would be a backup system.

 

  • There is no difference in terms of functionality when choosing different licensing models.

    It depends upon you which of the 3 following models are cost-effective and better suited to your environment -

    1) Ala carte mode : The BE server license, number/type of agents & options are purchased according to your environment.

    2) V-Ray edition: Licensed per socket basis & includes certain agents/options for virtual environments such as DeDupe option, VMware & Hyper-V agent.

    3) Capacity edition: Includes all agents & options and is licensed per TB of data.

  • The licensing guide has (very) recently recieved some updates (which may help with understanding) - it certainly has a the details of Capacity Lite vs Capacity in a table, although I don't think it does a direct comprison of Capacity vs V-Ray

    http://www.veritas.com/docs/000024885?

    Also there is some info on how capacity is calculated in this next document (you need to understand the concept of Front End Terabyte as this is not the same as total bytes used by all backup sets unless you only ever keep one full backup set of any specific resource.)

    http://www.veritas.com/docs/000025717?

     

    V_ray is sold per CPU and in two tiers

    Tier A - Per CPU (2-6 cores)

    Tier B - Per CPU (8+ cores)

    As such there is no costing model that includes the exact count of cores - just whether or not you have CPU's with less than 8 or 8+ cores

     

    BTW don't buy Tier B  if you only have Tier A systems this will trigger license alerts for invalid licenses.

     

     

     

     

14 Replies

  • VJware & Colin

     

    Many thanks, i think that has pretty much answered my questions. Only really a couple of queries, so

    Capacity Edition Lite - are there versions that will do more than 1 TB or is it just set at 1 TB

    Capacity Edition Lite - can it use disk storage as a target for backups

    Thanks

    Roger
     

  • Capacity Lite can use disk and tape - just no deduplication and no multi-tape libraries only 1 tape drive.

    Capacity Lite also has the multi-terabyte discounted tier capability is the same way as full

  • Yes, you can use basic disk, but not advanced disk such as (DeDupe) with Capacity Lite.

    Have a look @ this link for the comparison matrix - http://static.symanteccloud.com/estore/resources/en/be-2015-licensing-guide.pdf

    No restrictions on data apply as both editions allow adding increments of TB. In fact, Capacity Lite edition can be upgraded to Capacity Edition as well if needed.

  • The up to date (Veritas)  version of the comparison  matrix is inside the licensing guide I posted earlier -  I would recommend not using the one hosted on the obsolete Symantec pages as it is already out of date - to see what I mean compare the one in the Veritas technote I posted ealier with the one in the link from VJware.

     

    Note I have already asked for us to get the Symanteec one unpublished (especially as it shows up early in Google searches) and someone is currently trying to track down how to get old documentation on the wrong side of the corporate split removed.