Announcing Feature Pack 2 (FP2) for Veritas Backup Exec 16

I’m very excited to announce the general availability of the latest feature pack release for Veritas Backup Exec™ 16.

Over the last few years, Backup Exec has been evolving at a rapid pace, making more features and functionality available to our users on quarterly basis. Backup Exec 16 FP2 races forward to protect the cloud-ready organizations, with new features and enhancements suited for your multi-cloud needs, boost agility, and increase IT efficiency.

New capabilities:

  • S3 compatible cloud storage support - Backup Exec continues to expand its cloud capabilities, allowing customers flexible cloud options. You can now configure any S3 compatible cloud storage devices with Backup Exec.
  • Dedupe to cloud - Reduce total cost of ownership (TCO) with comprehensive dedupe to cloud that can save storage and infrastructure costs.
  • CloudConnect Optimizer - Automatically detects and corrects variations in the “Write Connections” setting so backups better utilize available network bandwidth.
  • Easy upgrades with Backup Exec™ Migration Assistant - The new Backup Exec Migration Assistant lets you easily migrate your data from one Backup Exec server (source) to another Backup Exec server (destination).

New platform support:

  • Expanded cloud integration with support for Microsoft Azure Government Cloud, Microsoft Azure China, and Microsoft Azure Germany
  • Improves accessibility of cloud storage data with support of the Regional storage class for Google cloud storage
  • AWS Government (Non-FIPS compliance)
  • NetApp FAS Series with Data ONTAP v 9.1
  • Exchange 2016 CU6
  • Exchange 2013 SP3 CU17 (KB4012114)

General fixes

A number of minor product issues and optimizations have been addressed in Backup Exec 16 FP2. For more information, click here to view the Backup Exec 16 FP2 Release Notes.

Accessing the Backup Exec 16 FP2 update

Customers with existing Backup Exec 16 deployments can download FP2 today using the link below. Availability via Live Update is expected to follow within the next 15 days.

Links and downloads:

Learn more about what’s new in Backup Exec 16 FP2

Download Backup Exec 16 FP2

Backup Exec Home Page

Just the beginning, more enhancements are in the works

Our goal is to make Backup Exec experience simple, fast, and efficient to enable you to achieve more easily what you need to get done while increasing features and functionality. We’ll be adding further enhancements in the near future, including:

  • GDPR compliance – One in particular that has been top of mind for me is the upcoming Information Map integration. Companies across the board are in the midst of preparing for the new General Data Protection Regulations (GDPR), which goes live in May of 2018. The direct integration between Backup Exec and Information Map will help organizations to stay compliant and quickly visualise data to understand who it belongs to, where it is and what type of data it is.
  • Office 365 backup – Organizations are increasingly looking to Microsoft to help power their digital transformation as they adopt Office 365. These same organizations look to Veritas to help protect their data. Veritas is working to integrate seamlessly with Microsoft Office 365 to make sure your Office 365 data is recoverable and protected.

The future of Backup Exec is bright, and we are excited to collaborate with you on our next steps, and to empower you, your teams and your organization to do more.

Your feedback really does make a difference

Would love to hear your thoughts, please feel free to post questions and comments below.

Thank you for choosing Veritas Backup Exec. We are working hard to bring you the most productive experience ever.

Simon Jelley, General Manager, Backup Exec

Forward-looking Statements: Any information regarding pre-release Veritas offerings, future updates or other planned modifications is subject to ongoing evaluation by Veritas and therefore subject to change. This information is provided without warranty of any kind, express or implied.  Customers who purchase Veritas offerings should make their purchase decision based upon features that are currently available.

7 Comments

Hi Smiley Happy

Can you talk about this "OpenDedup" support? 

What exactly was it?

Att,

Tiago Toledo

Hi @tiagotoledo 

Backup Exec 16 FP2 with OpenDedupe integration now supports customers that require deduplication to help them realize the cost savings that are commonly associated with a cloud centric environment.

The amount of data that must be sent over the Internet to the cloud as well as the data stored in the cloud is reduced, saving both time and costs. For more information about the OpenDedupe support, please refer to the following technote:  http://www.veritas.com/docs/000127295 or this nifty infographic: https://www.slideshare.net/VeritasTechLLC/deduplication-to-cloud-with-backup-exec-16-fp2

HTH!

BR
Varun

Hi @VarunVerma

I understood, thank you for the explanation.

Att,

Tiago Toledo

 Hello,

The PDF and all the infographics keep mentioning that these jobs "can be encrypted to the cloud" but what I am not seeing anywhere is an explanation and how-to regarding setting this feature up. 

Best I can guess is that technically Backup Exec can write this data to the cloud using Backup Exec managed keys and software encryption at the cost of no longer really deduplicating.

Basically if I create a job without software encryption keys it is very clear that it deduplicates without issue - but then the data in my Cloud storage (data at rest) is readable to anyone with Backup Exec and access to the storage correct?

I also tested the same jobs using software encryption (which gives me data encrypted at rest at my cloud provider) but then the deduplication ratio goes back to 1:1

Please let me know if there is some other method of encrypting this data at rest while still keeping intact the main feature: Deduplication.

Thanks,

OpenDedupe can perform the encryption by following the below steps (it is disabled by default). The data will be encrypted on local disk/cache, sent over SSL (regardless of setting), and remain encrypted at rest in the cloud storage.

  • First you need to unmount the volume
    • ~sdfs\sdfscli --nossl --shutdown --password <password> [--port <nnnn>]
    • If there is only one OpenDedupe volume no need to specify the port
  • Then set encryption to enabled
    • Edit in ~sdfs\etc\<volumename>-volume-cfg.xml change encrypt="false"  to encrypt=”true" and save
  • Then need to mount the volume again
    • ~sdfs\mountsdfs -v <volume name> -m <driveletter>
      • Make sure to specify the correct volume name and the same drive letter. If not sure, open the BE OpenDedupe config tool
    • Verify that it has been enabled
      • ~sdfs\logs\<volume name>-cfg.log
        • ################## Encryption is enabled ##################

David,

Thanks for your reply. I can certainly follow these steps so that you have provided. While it's a new feature I do hope Veritas creates a write-up/whitepaper on this new functionality. 

What I am not understanding is how this encryption is tied directly to my Backup Exec instance? Is it via the 8 character password we have to set up?

What happens if someone has access to the cloud storage bucket and their own Backup Exec 16 FP2 stood up? Can then attach, inventory, catalog, & sucessfully restore data?

I am sure this is not the case, or at least I hope it isn't but that then begs the question what do we need to "remember" or save in order to decrypt this data in the event where our original Backup Exec server became permanently unavailable?

Thanks,

Nick

Nick,

TechNotes are in work for OpenDedupe/Backup Exec best practices and functionality.

When using the OpenDedupe encryption, the key/password used when creating the OpenDedupe volume is used/required to encrypt/decrypt the data.