1. HPE Data Protector 9.06 What’s New
Mike Peebles, Product Manager
Uli Wallscheid, IM&G EMEA
April 2016

2. Agenda Introduction to DP (recap) VM backup options (recent changes)
What’s new in DP 9.06
Future releases in 2016
DP assets - where to find them
New assets
One slide – VM Explorer vs DP

3. Agenda DP 9.06 Feature Overview DP 9.06 Feature Detail
DP 9.06 Availability
Additional Resources

4. Data Protector 9.06 What’s New
Storage Integration:
HPE 3PAR InformOS 3.2.2
HPE 3PAR ZDB/IR support within a VMware VM
Catalyst support for CentOS & OL 7.x
Application Enhancements:
Exchange 2016 GRE on Windows 2012 and 2012R2
Support for Storage Optimizer 5.x (incl. stub files)
Oracle 12c on Solaris x64
EADR support for BTRFS sub volumes
Virtualization:
Support for VMware VDDK (SAN Backup/Restore)
VMware GRE support with Windows 2012 R2 Clustered Cell Managers
Hardening:
Update in front end capacity license calculation
Collection DP environment telemetry data
DP patch version display in client context

5. DP PAR Support Updates
Support for the latest InformOS version 3.2.2
Includes support for all MU versions
Support for the latest VSS hardware provider
Windows 2008 R2 and later with VSS Provider 2.5.x
Support for ZDB & IR from within a VM
SMI-S agent support

6. DP 9.06 VMware Updates Support for VDDK 6.0.2
Resolution for SAN transport for ESXi 5.5
Details from the VDDK Release Notes:
VMware GRE support with Windows 2012 R2 Clustered Cell Managers

7. DP 9.06 Application Enhancements
Platform update highlights
Exchange 2016 GRE on Windows 2012 and 2012R2
Backup of Exchange 2016 already supported
DP 9.06 enables GRE support for Exchange 2016
Support for Storage Optimizer 5.x (incl. stub files)
Option to either backup or skip stub files (OB2HSMBACKUPALL)
Adds to existing support for other HSM applications
Added support for Solaris (x64)
Disk Agent and Oracle 12c on Solaris 10 & 11 (x64) added
Support for other Oracle versions is in process
EADR support for BTRFS sub volumes
SAP HANA node disaster recovery is a key use model

8. DP 9.06 Capacity License Reporting
Update in front end capacity license calculation
Capacity is calculated per system
Previously this was done per backup specification
Data included in multiple backup specifications is no longer double counted
Limitations
Backup of the same database with multiple agents will be counted multiple times
Potential Objections
Permanent retention or decommissioned clients
The Capacity Based License (CBL) product structure is based on the volume of primary data protected by HPE Data Protector. The capacity is measured in "Front End Terabytes" or Front End TB. The total amount of Front End Terabytes is defined as the aggregate amount of source data being backed up from all systems. Per system it is measured as the largest full backup. That is, the total amount of source data backed up. The licensing in this product structure is perpetual and covers existing or new infrastructure and applications. Capacity calculation details:
For a full & incremental backup concept, only full are considered
For an incremental forever, a "synthetic" full is used
Only objects with a status of “completed” or “completed with errors” are included in the calculation
Only objects which are still under protection are included in the calculation
The capacity per system is calculated as an aggregation of the largest size of each unique object for that system still under protection
Limitations:
Backup of the same database with multiple agents will be counted multiple times. Some examples of scenarios where capacity will be counted multiple times:
A file system backup of a database using VSS and an application integration agent of the same database.
A virtual environment integration backup of a virtual machine and a file system backup of the same data within that virtual machine.
When an Oracle backup object name format is externally reconfigured in such a way that Data Protector is not be able to resolve the Oracle database name from the object name the unique capacity will be counted multiple times. To avoid this the reconfigured object name must include the Oracle database name and be in the format “<DBID_*.dbf”.

9. DP 9.06 Hardening Collection of DP environment telemetry data
High level information gathering
DP client OS
Scheduling
Device Info
Licensing Info
Packaged with debug logs
DP patch version display in client context
Update of feature introduced with DP 9.05

10. Tech Info: BTRFS

11. What is BTRFS?
BTRFS is a copy on write (CoW) filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance, repair and easy administration. Jointly developed by multiple companies, BTRFS is licensed under the GPL and open for contribution from anyone.
Some Features:
2^64 byte = 16 EiB maximum file size (practical limit is 8 EiB due to Linux VFS)
Space-efficient packing of small files, Space-efficient indexed directories
Writable snapshots, read-only snapshots
Subvolumes (separate internal filesystem roots)
Compression (zlib and LZO)
Integrated multiple device support:
File Striping, File Mirroring, File Striping+Mirroring, Striping with Single and Dual Parity implementations
Efficient incremental Backup
Background scrub process for finding and fixing errors on files with redundant copies
Online filesystem defragmentation
Batch, or out-of-band deduplication (happens after writes, not during)
BTRFS is also used with Docker Containers/Clouds

12. BTRFS Directory Structure
< Subvolumes showing like folders
By default DP will hides the BTRFS
structure making it easier to browse
and select through large file systems.
In this example almost half of the
folders are actually BTRFS mount
points or subvolumes.
In order to make EADR work the
process needs to see individual
mount points. This is why the option
exists to enable unhide those
mountpoints (see next page)

13. BTRFS Parameters and Options
To avoid confusion in backup configurations the BTRFS mount structure is hidden by default. Showing BTRFS mountpoints can be turned on with this parameter (/opt/omni/.omnirc):
OB2_SHOW_BTRFS_MOUNTS=0|1 (needs to be added manually ...)
Default
Option

14. BTRFS Backup and Restore Options
DP backs up and restores BTRFS and subvolume structure
Otherwise it behaves like with any other Linux-Type file system
A Disk Agent is needed since the BTRFS structure is invisible to hypervisors

15. DP with Storage Optimizer and stub files

16. New DP Parameter Supporting Stub File Backup/Restore
Data Protector 9.06 has been enhanced to support new versions of Storage Optimizer (5.0/5.1/5.2)
including their new file stubbing feature. A new omnirc variable has been implemented to take control.
This variable is also replacing the former „FSE variable“ used with File System Extender in the past.
OB2HSMBACKUPALL=1|0
Default:0
# By default, backup process skips all files with offline attribute.
# Use with caution. If set to 1, backup DA checks for offline attribute will
# be disabled. All files with offline bit will be backed up. In case of a file
# with a reparse point only a stub backup is performed. In case of files with
# offline attribute that do not have a reparse point it depends on the HSM
# product whether a data re-call and data re-hydration is performed. This can
# cause high I/O traffic and system overload.
# For more information refer to your HSM product documentation.
An NTFS reparse point is a type of NTFS file system object. Reparse points provide a way to extend the NTFS filesystem. A reparse point
contains a reparse tag and data that are interpreted by a filesystem filter identified by the tag. Microsoft includes several default tags
including NTFS symbolic links, directory junction points and volume mount points. Also, reparse points are used as placeholders for files
moved by Windows 2000's Hierarchical Storage System. They also can act as hard links, but aren't limited to point to files on the same
volume: they can point to directories on any local volume

17. Use Case: Backup Optimization
SO will analyze data first and
display optimization potential on
a dashboard
An archiving policy is set up to
move unwanted data out of the
primary storage pool into an
archiving target (i.e. share)
Files are replaced by stubs (pointer with „Offline“ flag) into
the archive and DP just backs up
those stub files without retreiving
their payload data. Same for
restores. Size on disk is reported
as 0 bytes.

18. Use Case: Backup Optimization
In the DataProtector restore context files
are shown like in their original format.
So no changes in procedures here.
After restore you‘ll just find the same
pointer files with 0 byte size on disk.
You can immediatly open and used them.

19. Other changes

20. Debug + Telemetry Info The admin can decide whether
or not to have Telemetry data
included with log files.
Telemetry data is:
DP, Client O/S and version
Scheduling Info
Device Info
Licensing info
To be found in a dedicated
directory \dlc\<client>\telemetry
as a zipped text file.

21. Availability & Resources

22. DP 9.06 Available on SSO
Patches are available from softwaresupport.hpe.com  Dashboards  Patches
Filter for product version you’re looking to patch

23. Product Documentation & Manuals
Latest product manuals are available from softwaresupport.hpe.com
“Dashboards”  “Manuals”
Filter on product = “Data Protector” and version = “9.0”

24. Support Matrices
Latest support matrices are available from softwaresupport.hpe.com
“Product Information”  “Matrices”
This will contain all of latest support matrices for DP product suite
Updated monthly

25. Data Protector Sales Portal
HPE Internal: swsalesportal.hpe.com
Partner: partner.hpe.com
Customer facing deck
DP 9.06 What’s New presentation
DP 9.06 What’s New Brainshark recording

26. Thank you