Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
HP BladeSystem with
Symantec NetBackup and
HP StoreOnce
Reference architecture and best practices for backup and recovery
Table of contents
Executive summary ..............................................................................................................................................................3
Solution overview..................................................................................................................................................................4
Technology overview ............................................................................................................................................................5
HP BladeSystem ................................................................................................................................................................5
HP BladeSystem c7000 Enclosure .....................................................................................................................................6
HP Onboard Administrator...............................................................................................................................................7
HP Virtual Connect ............................................................................................................................................................7
HP ProLiant BL460c Gen9 Server Blade.........................................................................................................................8
HP OneView .......................................................................................................................................................................9
HP 3PAR StoreServ 7450 All-flash Storage array ..................................................................................................... 11
HP StoreOncekey features and benefits ................................................................................................................ 12
HP StoreOnce 4700 ....................................................................................................................................................... 13
HP StoreOnce integration with Symantec NetBackup via OST................................................................................. 15
Symantec NetBackup anatomy .................................................................................................................................... 17
Installation and configuration of Symantec NetBackup 7.6 ......................................................................................... 19
Configuring Catalyst stores on HP StoreOnce 4700 and then integrating them into NetBackup ....................... 20
Contents of a Catalyst store explained ....................................................................................................................... 27
Catalyst stores configured in this investigation ......................................................................................................... 28
Symantec NetBackup Oracle RAC 12c integration ......................................................................................................... 29
Test Bed architecture overview ........................................................................................................................................ 29
Solution components .................................................................................................................................................... 30
Optimizing backup and recovery for Oracle RAC 12c on HP BladeSystem with Symantec NetBackup.............. 32
NetBackup tuning guidelines ........................................................................................................................................ 34
Backup configuration..................................................................................................................................................... 35
Executive summary
Applications that are core to the success of your business are often classified as mission critical or business critical. Their
requirement for zero-downtime operations results in stringent service-level agreements (SLAs) to achieve and maintain
high levels of performance, availability, reliability, and serviceability. Normally, addressing these requirements requires the
application to be deployed upon bare-metal operating environments, but advancements in hypervisor technologies now let
you deploy these applications as virtualized workloads, for added scalability and rapid deployment.
Many organizations rely on virtualization to improve security and meet compliance requirements, increase data center
flexibility, simplify deployment and management, improve operational efficiencies, and lower the total cost of ownership
(TCO). To fully embrace and reap these benefits, adopting an integrated end-to-end solution can deliver the agility needed
to accommodate the current needs and future growth requirements that mission-critical applications demand. Equally
important, an integrated technology stack can enable you to expand, contract, scale up, scale down, scale out, or scale in to
address infrastructure allocation requirements as workloads change. To meet these needs, HP has created a converged
infrastructure platform using HP BladeSystem and HP OneView. Together it delivers a single infrastructure and single
management platform with automation for rapid delivery of service and rock-solid reliability with federated intelligence.
HP BladeSystem is a modular infrastructure platform that converges compute, storage, fabric, management and
virtualization to accelerate operations and speeds delivery of applications and services running in physical, virtual, and
cloud-computing environments.
When it comes to mission-critical transactional and analytical workloads, Oracle databases are chief among the applications
driving these workloads. More importantly, many major applications rely on Oracle database architectures within the
application stack. Deploying a solid database architecture, virtually or physically, is a key success indicator that can mean
the difference between leading and following your competition.
A solid database architecture can make the difference between competitive differentiation and simple comparative parity.
Competitive organizations establish aggressive recovery-point objectives (RPOs) and recovery-time objectives (RTOs) to
minimize data loss and ensure application recovery and reliability. They choose primary infrastructure and data protection
strategies that must deliver application-consistent backups, application-restartable recoveries, user-defined service levels,
single-point-of-failure eliminations, along with the ability to maximize resource utilization. Finding these requirements in a
non-integrated solution is possible, but the long-term application lifecycle costs are often much greater in the end.
In this paper, we will examine both a mission-critical application-streaming backup and recovery as well as a virtual machine
(VM)-based backup and recovery leveraging the Symantec NetBackup features such as, Traditional Oracle RMAN scripting
integrated with NetBackup scheduling and catalogs, Full VADP integration with VMware, and Symantec NetBackup
Accelerator to speed up File system and VMware backups. All of these advanced data protection features can be supported
on HP StoreOnce using HP StoreOnce Catalyst backup targets.
Solution overview
A well-designed data management strategy does not use a one-size-fits-all approach to data protection. A combination of
tactics tailored to the target application provides the best protection and SLA adherence. Following that principle, the
environment described below takes different approaches for critical and generalized workloads. Critical applications, such as
Oracle database needing deep integration with the data management system are protected using the Symantec NetBackup
RMAN scripting integration. This technique relies on a process of linking the Oracle Server software with the NetBackup API
library installed by NetBackup for Oracle. Oracle uses this library when it needs to write to or read from the devices that
NetBackup media manager supports. For generalized virtualized workload, the Symantec integration with VMware vSphere
Storage APIs for Data Protection (VADP) along with Symantec NetBackup Accelerator provides a fast/unified protection and
recovery vehicle for all VMs, with fast recovery times. None of this would be possible if it were not for the tight integration of
HP StoreOnce with the advanced features offered by Symantec OpenStorage interface (OST) and the HP StoreOnce Catalyst
backup target type. Using this technology, HP StoreOnce can offer:
Source side deduplication
NetBackup controlled replication between HP StoreOnce targets using Storage Lifecycle policies
Asynchronous expiry dates of different copies of data on different HP StoreOnce units
Support for Symantec Granular recovery technologyrecovery options can be browsed directly on the HP StoreOnce unit
before recovery
Support for Symantec Targeted AIR (auto image replication) on HP StoreOncea must for improved disaster
recovery (DR)
Support for NetBackup Accelerator on StoreOnce for VMware virtual machines and OS file systems Full backups at the
speed of incrementals
Improved StoreOnce backup target device reporting through the OST interface
For more details on Symantec NetBackup Integration with Oracle, see NetBackup integration with Oracle.
For more details on Symantec NetBackup integration with VMware including NetBackup Accelerator, see NetBackup
Integration with VMware.
Figure 1. Schematic overview of the solution
The diagram on page 4 shows the overall solution set up, all the VMs are configured in the highly scalable HP BladeSystem,
the datastores for these VMs utilize an HP 3PAR disk array. The set up simulates a typical mid-range customer with Oracle
databases and other applications running on several Windows VMs. The NetBackup Master server and media server are also
virtualized. The real world transaction load capability of the two Oracle databases is simulated using the HammerDB Utility.
On the StoreOnce 4700 backup appliance, we have created three backup targets, one each for the two Oracle databases
and another one for the Windows 2012 VMs 813 backups. This follows the best practice of a backup target for different
data types. We also utilize the source and target side deduplication capabilities of HP StoreOncefor the Oracle databases,
we found the additional CPU load of performing deduplication on the database server itself increased the CPU load, and this
would affect transactional performance, so instead the deduplication is performed on the StoreOnce unit itself (target-based
deduplication). With the Windows 2012 VM backups, we are using Symantec NetBackup Accelerator on VMs, which greatly
reduces the volume of data transferred in the backup and then goes on to produce a synthesized full, in this case the
deduplication is performed on the Windows 2012 VMs (source-side based deduplication)this then reduces the load on the
HP StoreOnce unitso we can architect the best of both worlds.
Technology overview
HP BladeSystem
HP BladeSystem is a modular infrastructure platform that converges compute, storage, fabric, management and
virtualization to accelerate operations and speeds delivery of applications and services running in physical, virtual, and
cloud-computing environments. The unique design of the HP BladeSystem c-Class helps reduce cost and complexity while
delivering better, more effective IT services to end users and customers.
Only HP BladeSystem delivers a whole new experience for IT with the Power of Oneone infrastructure, one management
platform to help customer reduce the need for multiple management tools, streamline processes and eliminate common
sources of errors to speed the delivery of services. As the single software-defined management platform, HP OneView
delivers industry leading innovation such as proactive health monitoring built on a federated architecture to streamline
operations and maximize availability while delivering 23 percent lower TCO over other bladed architectures.
HP BladeSystem with HP OneView delivers the Power of Oneone infrastructure, one management platform. Only the
Power of One provides leading infrastructure convergence, the security of federation, and agility through data center
automation to transform business economics by accelerating service delivery while reducing data center costs. As a single
software-defined platform, HP OneView transforms how you manage your infrastructure across servers, storage, and
networking in both physical and virtual environments.
The HP BladeSystem brings together the best HP innovations and latest industry standards into one design to address
some of the toughest challenges of todays data centersefficiency, availability, and speed of service delivery. The
HP BladeSystem offers unique differentiators versus other blade choices that can improve efficiency for customer at a
data center level.
HP Onboard Administrator
The Onboard Administrator centralizes c-Class infrastructure management. Together with the enclosures HP Insight Display,
the Onboard Administrator has been designed for both local and remote administration of HP BladeSystem c-Class
components and provides the following capabilities:
Wizards for simple, fast setup, and configuration
Highly available and secure access to the HP BladeSystem infrastructure
Security roles for server, network, and storage administrators
Automated power and cooling of the HP BladeSystem infrastructure
Agent-less device health and status
Thermal Logic power and cooling information and control
Figure 3. HP Onboard Administrator for the BladeSystem c7000 chassis
HP Virtual Connect
HP Virtual Connect technology provides wire-once, change-ready connectivity that is simple, flexible, and secure. This
technology is a key element of HP Converged Infrastructure, providing a better way to connect your virtualized environment
to the network core. Rather than tying profiles to specific server blades, you create a profile for each of the bays in the
c7000 enclosure; Virtual Connect then maps physical LAN or SAN connections to these profiles, allowing you to manage
connectivity without involving LAN or SAN administrators. In addition, if a server blade were to fail, you could move its
associated profile to a bay containing a spare blade, thus restoring availability without needing to wait for assistance.
HP Virtual Connect FlexFabric technology supports the convergence of traffic based on different network protocols, allowing
you to split a 20 Gb network connection into four variable partitions. The benefits of FlexFabric technology include the ability
to replace multiple low-bandwidth physical NIC ports with a single port, lower management burden, fewer NICs and
interconnect modules, and lower power and operational costs.
Key benefits of Virtual Connect:
Servers are change-ready. Move, add or change servers without affecting the LAN and SAN
Reduce cables without adding switches to manage
Standards-based compatibility with other brands of Data Center networking infrastructure
Pre-configure network connections for blade enclosure bays before servers are installed for easy, drop-in installation
Figure 4. HP Virtual Connect FlexFabric-20/40 F8
HP Virtual Connect FlexFabric 20/40 F8 Modules are the simplest, most flexible way to connect virtualized server blades to
data or storage networks, HP Virtual Connect FlexFabric 20/40 F8 Modules eliminate up to 95 percent 1 of network sprawl at
the server edge using one device that converges traffic inside enclosures and directly connects to external LANs and SANs.
Utilizing Flex-20 technology with Fibre Channel over Ethernet (FCoE) and accelerated iSCSI, these modules converge traffic
over the industrys first high-speed 20 Gb connections to servers with HP FlexFabric Adapters (HP FlexFabric 20 Gb 2-port
630FLB and 630M Adapters). Each redundant pair of Virtual Connect FlexFabric modules provides eight adjustable downlink
connections (six Ethernet and two Fibre Channel, or six Ethernet and two iSCSI, or eight Ethernet) to dual-port 20 Gb
FlexFabric Adapters on servers. Up to eight uplinks are available for connection to upstream Ethernet (up to 40GbE) and
Fibre Channel switches. Virtual Connect FlexFabric modules avoid the confusion of traditional and other converged network
solutions by eliminating the need for multiple Ethernet and Fibre Channel switches, extension modules, cables, and
software licenses. In addition, Virtual Connect wire-once connection management is built-in enabling server adds, moves,
and replacements in minutes instead of days or weeks.
all managed by HP OneView the converged management platform that accelerates IT service delivery and boosts
business performance.
HP internal calculations comparing the number of hardware components of traditional infrastructure vs. HP BladeSystem with two Virtual Connect FlexFabric
modules, June 2013.
deployment versatility.
Transforming business economics by accelerating service delivery:
HP OneView provides the Power of One a single comprehensive view of the data center, managing hardware, software,
firmware, and drivers.
HP Integrated Lights-out (iLO) software features server lifecycle management advancements including iLO Federation,
which remotely manages groups of servers at scale with built-in rapid discovery of all iLOs, group configurations, group
health status, and ability to determine iLO licenses.
HP Smart Update Manager powered by iLO Federation technology for faster firmware updates.
HP OneView
HP OneView is converged management that eliminates infrastructure complexity with automation simplicity. This modern
management architecture is designed to accelerate your IT operations for managing servers, storage, and network
resources.
The HP OneView design is:
Converged, with an innovative architecture that delivers a unified and consistent management experience across servers,
storage, and networking.
Software-defined, providing software-based control, infrastructure mapping, and a user-centric approach to ensure rapid,
repeatable, and reliable operations at lower costs.
Automated, working as an intelligent hub to streamline the delivery of IT services and to speed the transition to
IT-as-a-Service and to the hybrid cloud.
Convergence cuts in half the number of tools required to learn, manage, deploy, and integrate infrastructure. The
innovative architecture delivers simplified and consistent management across servers, storage, and networking. A single,
open management platform supports multiple generations of HP DL servers, HP BladeSystem, HP 3PAR storage, and
HP ConvergedSystem. Integration solutions also allow you to provision and manage lifecycles within familiar consoles like
VMware vCenter Server and Operations Manager, Microsoft System Center, and Red Hat Enterprise Virtualization.
Software-defined approaches to systems management create get it right repeatability every time to help you prevent
unplanned outages caused by human error or device failure. Profiles and groups capture your best practices and policies to
help you increase productivity and enable compliance and consistency. You can also manage this infrastructure
programmatically using powerful APIs build on industry standards such as REST. These APIs are easily accessible from any
programming language and SDKs are provided for interfaces, Windows PowerShell, and Python scripts.
Automation can streamline your delivery of IT services and speed your transition to Infrastructure-as-a-Service (IaaS) and
hybrid cloud delivery. Using HP OneView as an intelligent hub provides you a closed-loop automation with consistent APIs,
data model, and state-change message bus. Your virtualization administrators can automate control of HP compute,
storage, and networking resources using VMware vCenter or Microsoft System Center without having detailed knowledge of
each device. The result: tasks, processes, and projects are accomplished faster and with more consistency than the older
patchwork approaches to management.
These innovations in HP OneView can reduce your OPEX and improve your business agility. HP OneView is your converged
management foundation to free your resources for new business initiatives, whether that is lights-out automation or
enabling infrastructure for a hybrid, heterogeneous cloud. Efficiently transition from your current HP and third party
infrastructure, tools, and processes to your vision of IT-as-a-Service using HP OneView.
HP OneView simplification through convergence
Leveraging the power of HP management through one interface
Intelligent Provisioning
Array Configuration Utility
Integrated Lights-Out 4 (iLO 4)
HP Smart Update Manager
HP Systems Insight Manager
Virtual Connect Manager/VCEM
Onboard Administrator
HP 3PAR array management
10
chunks.
A unique suite of persistent technologies power HP 3PAR StoreServ 7450 Storage in delivering high availability and tier-1
resiliency to performance-critical applications including:
HP 3PAR Persistent Cache: Preserves service levels, so they are not impacted by unplanned component failures.
HP 3PAR Persistent Ports: Allows non-disruptive upgrades without relying on multi-pathing software and without
initiating failover.
HP 3PAR Peer Persistence: Ability to federate storage across data centers without being constrained by physical
boundaries.
HP 3PAR StoreServ Data at Rest Encryption: Protects data from both internal and external security breaches.
Flash-based media failure reconstruction: This enables the system to provide consistent performance levels even under
across systems.
HP 3PAR StoreServ storage is also backed by the Get 6-Nines Guarantee, which stands behind the ability of all quad-node
and larger HP 3PAR StoreServ Storage systems to deliver 99.9999 percent data availability. 2
Figure 7. Front view of the HP 3PAR StoreServ 7450 All-flash
Subject to qualification and compliance with the HP 3PAR Get 6-Nines Guarantee Program Terms and Conditions, which will be provided by your HP Sales or
Channel Partner representative.
11
12
HP StoreOnce provides virtual tape (VT), network-attached storage (NAS), or StoreOnce Catalyst target devices for data
protection applications. Interfaces can be via a network connection or FC. Figure 6 shows the basic components of the
StoreOnce appliance. The actual storage medium is hard disk and these are arranged in a RAID 6 configuration with an
enterprise-class HP-designed RAID controller. Data is written across all disks in the RAID. RAID 6 prevents data loss in case of
two hard disk failures. RAID disks in current StoreOnce appliances are either 2 TB or 4 TB serial-attached SCSI (SAS) disk drives.
HP StoreOnce deduplication is also used to move backups to other HP StoreOnce appliances in a bandwidth-efficient
manner. This enables customers to move backups to another physical location often using a WAN connection with no
human intervention. In the event of a total site loss, the data is still safe at the DR site and systems can be quickly restored.
Because of the tight OpenStorage Technology (OST) interaction with NetBackup using the HP StoreOnce Catalyst backup
target type, this replication to another site can be actually controlled by NetBackup itself using Storage Lifecycle policies.
Replication to another NetBackup domain is further enhanced through the use of targeted Auto Image Replication (AIR)
integration, which allows automated catalog imports that drastically reduce DR recovery times.
Figure 8. StoreOnce Architecture overview
HP StoreOnce 4700
HP StoreOnce has been designed to cater to the needs of all types of customers from entry level to large scale enterprises.
HP StoreOnce Backup systems deliver scale-out capacity and performance to keep pace with shrinking backup windows,
reliable DR, simplified protection of remote offices, and rapid file restore to meet todays SLAs. The models vary by capacity
and connectivity protocol and customers can start out by purchasing a single HP StoreOnce base unit/couplet, and then
expand with additional couplets and expansion shelves.
Note
In all cases, actual backup performance is dependent upon configuration, data set type, data change rate, compression
levels, number of data streams, number of devices emulated and number of concurrent tasks, such as housekeeping or
replication.
13
4U scalable rack
Up to 192 TB 4
Up to 160 TB4
3.2 PB4
50
7.6 TB/hr4
9.0 TB/hr4
Catalyst performance
22 TB/hr4
Device interfaces
Disk drives
50
204, 800
Replication
To provide sizing assistance for which HP StoreOnce model to choose, use the HP Storage Sizer.
Key parameters required for accurate sizing are data volumes, retention periods required, and an assessment of data
change rates.
14
These values assume infinite performance hosts and measure maximum ingest rate. Deduplication ratios assumes small data change rate and long
retention period.
2.
3.
4.
All copies of data are known to NBUAllows secondary copies to be promoted to primary copies in DR scenarios
5.
Much better DR recovery times(No need to import) if using Symantec AIR (Automated Image Replication)
6.
Supports Federated Catalyst stores on StoreOnce 6500 (large teamed Catalyst stores for easier management)
7.
Support for Symantec Granular Recovery Technology (GRT)Single item recovery from a snapshot
8.
All the configurations that are supported, including under what OSs can be found in the compatibility guide at
hp.com/go/ebs. We will use Catalyst over IP in this scenario.
HP StoreOnce supports different backup target types.
1.
2.
3.
HP StoreOnce Catalysta new intelligent API-based backup target capable of integrating much more tightly with
Symantec NetBackup. The HP StoreOnce plugin for Symantec NetBackup is an OST (OpenStorage Technology) plugin
that is installed on the NetBackup Media Server and the plugin is freely downloadable from hp.com at the following
URL: h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=StoreOnce
4.
The integration allows innovative features such as distributing deduplication media server and StoreOnce backup
target appliance for enhanced performance, Catalog replication between domains for faster DR, Symantec Granular
Recovery Technology (GRT) support for individual file recovery and Symantec NetBackup Accelerator support for
superior incremental backup
In this HP BladeSystem solution, we have chosen to use catalyst because we want to offer customers the option of media
server based deduplication (on the Oracle RAC nodes) and we also want to take advantage of NetBackup Accelerator for
VMware VMs. Symantec media server code is installed on the Oracle RAC nodes and a media server dedicated to the VM
backups, along with the HP OST Plug-in v3.1 Symantec NetBackup Client software is installed on the VMs 17. Let us now
look at the HP StoreOnce Catalyst implementations in this investigation.
On the Oracle RAC servers, we have enabled catalyst in high bandwidth mode. Which means the deduplication load is
performance on the StoreOnce unit itselfbecause we do not want to add additional CPU load to these Oracle RAC servers
that could potentially impact the transactional throughput during backup.
On the Windows VM backups using the media server mediawe have implemented Low Bandwidth Catalyst
backupwhere the correctly sized media server performs the deduplication processthis along with using Symantec
NetBackup Acceleratorreduces the network traffic for these backups to an absolute minimum, reduces data storage
requirements and speeds up overall throughput.
15
Figure 9. Oracle RAC backups use high bandwidth catalyst implementation in this investigation
In the above scenario, a high bandwidth catalyst store is provisioned which means all the deduplication is taking place on the
StoreOnce 4700allowing for more Oracle transactions during backup. HammerDB is a commercially available tool for
creating transaction loads on Oracle databases so we can simulate the typical backup performance under real-world load
conditions.
The diagram below shows the Low Bandwidth Catalyst implementation used in this investigation along with NetBackup
Accelerator. The NetBackup Accelerator functionality is included in the NetBackup client software installed on each of the
Windows 2012 VMs and seeks to intelligently map which blocks have changed between backups. The media server media
contains the HP StoreOnce OST Plugin and the HP StoreOnce Catalyst store on the StoreOnce 4700 that has been configured in
Low Bandwidth Catalyst mode. This means the deduplication work is done mainly on the Windows 2012 Media Server VM,
which has been sized correctly to accommodate this load. This usage model is sometimes known as source side deduplication
and the deduplication load on the StoreOnce unit is reduced because it is taking place on the media server instead.
Figure 10. Windows VM backups use Low Bandwidth Catalyst implementation along with Symantec NetBackup Accelerator
16
17
The screenshot below shows how all the VMs are distributed across different ESXi hosts and the virtualized NetBackup
Master server and media server were installed (NetBackup-0, NetBackup-1) along with various HP management software
for virtualized environments.
This screenshot below is a visual through vSphere Client of the virtualized environment we are backing up.
4 node RAC clusterBender 14RH Linuxalso NetBackup media servers with HP OST plugin installed.
3 node RAC clusterRAC1node 13RH Linuxalso NetBackup media servers with HP OST plugin installedno
particular reason for 3 nodesjust convenience.
NetBackup 0 master serverVirtualized on Windows 2012 R2.
NetBackup 1 media server (virtualized)Used to backup VMs windows 16 using NetBackup Accelerator.
Windows 16Windows 2012 Virtualized servers with NetBackup Client loaded.
The Minimum revision of NetBackup to support Windows 2012 R2 as a master/media server is v7.6.0.3 which is what was
used in this investigation.
18
On the master server, add the new media server to the additional servers list of the master server
3.
Install the Linux media server software on RAC Cluster called Bender nodes 1, 2, 3, 4 and RAC cluster called
RAC1node 1, 2, 3
4.
Before writing to a storage unit, link the Oracle Server software with the NetBackup API library installed by NetBackup
for Oracle. Oracle uses this library when it needs to write to or read from the devices that NetBackup media manager
supports. Link the Oracle RMAN using the linking script that NetBackup provides. e.g., for Linux run
/usr/openv/netbackup/bin/oracle_link. Consult Symantec NetBackup for Oracle Administrators Guide for more details
symantec.com/business/support/index?page=content&id=DOC6481
5.
Install HP OST Plugin Version 3.1 to all media servers (Windows and Linux)no cost download from
h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=StoreOnce
6.
Install the latest device mapping files from Symantecthese enable the advanced functionality such as NetBackup
Accelerator. These are no cost and downloadable from:
For UNIX: symantec.com/docs/TECH216417
For Windows: symantec.com/docs/TECH216416
7.
On all the VMware VMs we installed the NetBackup Client because we wanted the ability to be able to restore single
files directly to the VM
8.
Symantec NetBackup offers various tuning parameters by means of creating touch files; the complete list is shown
below. For catalyst implementation, the two parameters of interest are:
SIZE_DATA_BUFFERS_DISK
NUMBER_DATA_BUFFERS_DISK
Set:
SIZE_DATA_BUFFERS_DISK and NUMBER_DATA_BUFFERS_DISK to 262144 (256K) and 30 respectively (Default) on the
Oracle servers.
But on media server called media that is doing all the VM backups set:
SIZE_DATA_BUFFERS_DISK and NUMBER_DATA_BUFFERS_DISK to 512 and 262144 (256K) and found we obtained better
throughput.
You have to be careful because the Oracle media servers are the Oracle application servers as wellso wed not want to
starve the application of resources during backup. The media server however is dedicated just to backup of the Windows
VMs and we can use more and larger size buffers.
19
Configuring Catalyst stores on HP StoreOnce 4700 and then integrating them into
NetBackup
Below are the steps to configure StoreOnce Catalyst store to operate in a low or a high bandwidth mode.
1.
20
Login to the HP StoreOnce GUI and navigate to the StoreOnce Catalyst/storeshere you can see all the stores we
created for this investigationlets create one more to show the integration process. Click Create in the top right hand
corner.
We will create a Catalyst store called TEST and will make it Low Bandwidth by setting both transfer policies to Low
Bandwidth (if we wanted High Bandwidth, we would set both transfer policies to High Bandwidth).
We will need the IP address of the Catalyst store to configure it into NetBackupthis 4700 has 3 IP address, the 10GbE
address is 172.28.6.10 and can be found as shown below in the StoreOnce GUI.
21
Now let us turn to NetBackupNetBackup has a construct as shown in Figure 12the Catalyst store we have created
interfaces through a construct known as a Storage server in NetBackup, the storage server can be split into several Disk
Pools which in turn can create different Storage units which are then accessible via a backup policy.
Figure 12. Symantec OST stack
We first created and added the Storage server, from credentials in the left hand navigation. Right-click new on the
Storage servers in the Left Hand Navigation pane to create a new storage server as shown below.
22
Click Next and select OpenStorage from the drop down list of NetBackup supported disk-based backup targets, click Next.
The next screen is importanthere we enter the IP address of the 10GbE data network on our StoreOnce unit along with
the unique Storage server type (as installed via the OST plugin)note the syntax hp-StoreOnceCatalyst. Then we select a
media server that can initially access this storage server (we can add more later) and finally we must enter some credentials.
If we are using Client access permission checking, these must align with the Clients and passwords we have created on the
StoreOnce. In this example, we did not enable Client access permission checking on StoreOnce. Click Next.
23
We can now select other media servers, which are allowed to access this storage server. In this TEST example case, it is all
the RAC Cluster nodes in both Bender and RAC1. Click Next and the Storage server is created and we are automatically
sent to the Disk Pool creation Wizard.
24
Click Next and choose the type of Disk Pool to createin our case hp-StoreOnceCatalyst, click Next.
The Disk Pool Wizard has discovered all the Logical Storage Units (LSUs) on the Storage serverwe can see the new one
TEST, which we have created. Click Next and give the Disk Pool a name as shown below.
25
In this example, we have decided to limit the number of streams to this Disk Pool to 24, as this was determined as the
sweetspot for maximum throughput. Click Next and Disk Pool is created and the Storage Unit Wizard is automatically
enabled.
26
Provide a name for the storage unit and again set a value for the maximum number of concurrent streams allowed to
access this Storage unit. Click Next and the Storage Pool is created successfully and can be used in Backup Policies as
seen below.
The above example has shown the creation of a TESTSTORAGEUNIT for demonstration purposes. In the main investigation,
we created separate Catalyst stores for the Bender and RAC1 Oracle clusters as well as separate Storage unit for the redo
transaction logs. The Storage units are then referenced in the Policies, which control the backup Scheduling and advanced
features.
27
items that have come from the different media servers as part of our load balanced backup. The Client identifier is also
clearly listed as an attribute as well as the throughput being achieved and data volumes written.
Click on an individual item and more information is displayed in the bottom pane. In the highlighted item, a deduplication
ratio of 64.8 is being achieved. Bandwidth saving is 0 percent because this is a high bandwidth store we have createdto
reduce the deduplication load on the Oracle application servers/media servers.
Usage
Comments
BenderBackupHB
BenderBackupLB
BenderRedoLogsHB
RAC1BackupHB
N/A
RAC1BackupLB
N/A
RAC1RedoLogsHB
N/A
Accelerator
You can also view the deduplication ratios through this GUI; for our Oracle RAC databases we were getting typically 8:1 and
for our Windows VM backups with NetBackup Accelerator, the deduplication ratio was around 10:1 over a period of a week
of full backups with either HammerDB creating data change on the Oracle servers or HP Create Data creating data
change on the Windows VM machines. Deduplication ratios vary according to the data change rate and retention period.
28
The Test Bed consisted of one HP BladeSystem connected to HP 3PAR StoreServ 7450 and HP StoreOnce 4700 connected
via a 10GbE network. Two 10GbE links were bonded to provide redundancy and a large pipe. Nine VMs were created on four
of the HP BladeSystem blades. Seven VMs were dedicated to the two Oracle clusters; across the four ESXi hosts on the
HP BladeSystem. Each Oracle VM has 16 virtual CPU (vCPU) and 96 GB of memory. One VM is used for Symantec NetBackup
Master server and another for NetBackup media server for VM backups and these NetBackup servers have 16 vCPU and
32 GB of memory provisioned. The two Oracle databases and VMware datastores reside on the HP 3PAR StoreServ 7450.
29
Solution components
This solution includes the following key components:
HP BladeSystem tested configuration
Table 3. HP BladeSystem hardware for the Test Bed
Component
Purpose
Server blade to host two Oracle RAC 12c 4-node clusters, Simpana application,
and HammerDB application running as VMs
HP StoreOnce 4700
Software configuration
Oracle RAC 12c configured on VM running Red Hat Enterprise Linux 6.5
Oracle Automated Storage Management (ASM)
Oracle Recovery Manager (RMAN)
Symantec NetBackup 7.6.0.3 Master server configured on Windows 2012 R2
Symantec NetBackup 7.6.0.3 Media server configured on Windows 2012 R2
Symantec Media server installed on All Bender and RAC1 nodes so they could act as media servers
Symantec Client software installed on all VM machines to be backed up
HammerDB 2.16 configured on VM running Red Hat Enterprise Linux 6.5
HP 3PAR OS version must be 3.1.3 and later
HP StoreOnce 4700 release 3.12 featuring reporting central and phone home capabilities
Symantec NetBackup Ops Center (reporting add on) was also installed to prove it works in a fully virtualized environment
30
Size
Provisioning
Notes
1 TB
Thick
RAID 5
500 GB
Thick
RAID 5
VM OS, binaries
specifications
150 GB
Thick
200 GB
Thick
Windows 2012 R2
HammerDB
50 GB
Thick
Workload
HammerDB is an open source database load testing and benchmarking tool for Oracle and other databases.
HammerDB is used to load the data into the two Oracle databases. Transactions were run against the databases during
backup to simulate a customer production environment. The load on the system would be qualified as medium and would
consume 45 percent of the CPU. The daily data change rate is estimated between 1.8 percent and 2 percent.
Figure 14. Database data load using HammerDB
31
Optimizing backup and recovery for Oracle RAC 12c on HP BladeSystem with Symantec
NetBackup
StoreOnce tuning guidelines
Make use of the HP StoreOnce Sizing tool to size your StoreOnce solution. It is available at:
h30144.www3.hp.com/SWDSizerWeb/default.htm.
Always ensure that the appliance software in your HP StoreOnce Backup System is fully up-to-date. Software upgrades
usedThis mainly depends on the CPU capabilities of the application servers and/or dedicated media servers.
Run multiple backup streams in parallel to improve aggregate throughput for a StoreOnce appliance.
Use blackout windows and replication windows to ensure that the appliance is not concurrently performing backup,
replication, housekeeping, and offload to tape operations. This can keep system performance consistent throughout the
backup period.
Configure multiple Ethernet ports in a network bond to achieve increased available network throughput.
Identify and resolve other performance bottlenecks in your backup environment such as slow clients and media agents.
Experiment with the ISV tuning parameters (in this case, the number and size of data buffers) to obtain best throughput
being mindful of application resources that also may be required from the same server.
32
Networking
The recommendation is to configure the StoreOnce with bonded 10GbE connections where possible to allow increased throughput.
Multiple Clients and Media Agents can write to the StoreOnce simultaneously reducing the total backup window required.
The number of streams required to get best throughput really depends on the performance of the hosts supplying the
data. Maximum ingest can be reached and a fairly low stream counts if the host can supply data fastotherwise the
stream count increase to attain the maximum ingest rate on the StoreOnce unit. Table 5 shows some best case
throughput rates.
Table 5. Maximum supported streams and devices
StoreOnce
Devices
Streams
VSA
16
600 GB/hr
2700
48
2.63 TB/hr
4500
32
128
10.8 TB/hr
4700
50
192
15.2 TB/hr
4900
50
320
17.05 TB/hr
6500
50
320/node
Replication
When using StoreOnce Catalyst with replication, you can configure NetBackup to actually replicate the Catalyst stores to
another site for DR purposes. This is achieved through the Symantec NetBackup concept of Storage Lifecycle policies. See
symantec.com/business/support/index?page=content&id=HOWTO73205.
More information on StoreOnce replication and its configuration is available at: hp.com/go/storage/docs.
An example of Symantec NetBackup controlling StoreOnce replication is shown belowthe first operation is the backup
and the second operation is the Duplication (Catalyst copy) between NetBackup systems in the same NetBackup
Domain to another StoreOnce unitall this is controlled by Symantec NetBackup itselfso it is aware of all copies of the
backupsthis makes for much more efficient recovery from disasters because there is no need for time consuming import
operations. To replicate catalyst stores between StoreOnce devices in different NetBackup domains and additional
NetBackup feature (also supported on HP StoreOnce) called Targeted Auto Image Replication (AIR) is required.
5
6
These figures are correct at the time of publication, but are subject to change with differing software versions.
These figures are headline performance figures, generated with extremely high performance clients to show raw StoreOnce ingest performance.
33
34
Backup configuration
For the test configuration, a cycle of full (weekly) and incremental (daily) backups were scheduled. Each cycle represents a
week and day of transactions and growth in the Oracle database. The daily data rate change was between 2 percent and
3 percent.
Full backups were scheduled weekly during low activity. Nightly incremental backups were scheduled to run in between the
full backups. Oracle Block Change Tracking was enabled for an optimized incremental backup. Oracle archive redo log
backups were configured to run automatically with the full and incremental backups to enable point-in-time recovery.
Because of the way Symantec NetBackup uses RMAN scripts, the incremental backups were configured as shown below:
Configured to run daily (under Schedule tab)
Uses a modified script/bender-full-archive-inc.sh, which uses the new RMAN Parameter INCREMENTAL=1 to set up the
backup as an incremental
Under these circumstances, only the data file blocks that have changed and archive redo logs generated under HammerDB
load are backed up instead of the whole database.
35
On the Schedules tab, we can set the window when the Oracle intelligent policy could run along with the type of backup;
media multiplexing should be set to 1 (only used on physical tape).
Selecting Instances tab, we can select instance or instance groups or select Clients for use with scripts or templates.
Selecting instances or instance groups forces this to become an Oracle Intelligent Policy type.
Once the instance is selected, the Oracle Intelligent policies causes the Backup Selections tab to be populated as shown
below to select different components for backup.
36
And also for Oracle Intelligent policies, the final Oracle tab controls various backup settings.
These parameters input through the GUI are used to populate the RMAN script that Symantec Intelligent Oracle Policies will
use. Below is an explanation of the various parameters. In the manual scripting method, we will move all these parameters
into the RMAN scripts.
Number of parallel channelsControls the number of streams sent to the StoreOnce unit. This is calculated by taking
total number of data files and dividing by the Files per set value. In this example, Bender 1 consists of approx. 120 data
files.
Number of open filesThis is the number of files open in memory at any one time for NetBackup/RMAN to access. This is
a compromiseif filesperset = 1 the database is backed up with data files in the exact same order every time meaning
we get a good dedupe ratio, but we starve the NetBackup/RMAN backup engine of data so the performance is slower.
A compromise value of five is chosen to keep the backup engine supplied with data whilst not decreasing the dedupe ratio
too much. The five files in memory can be picked out in any order so the pattern of sent to StoreOnce is not guaranteed to
be the same every time.
Files per backup setHow many database files are packaged into a backup piece.
Archived redo logsGenerally these are backed up well to enable a complete or point-in-time (incomplete) database
recovery. The archive logs backup can take a long time to backup if only a single channel is enabled, so we have enabled
16 channels for archive redo log backups. With Oracle Intelligent policies, the archive redo logs and database files are sent
to the same storage unitwhich means dedupe ratio could be reduced. A better practice is to send database files to one
Catalyst storage unit and archive redo log files to a different Catalyst storage unit (this can be done in the Legacy scripting
method described later).
User specified file formatsThese again are translated into an RMAN scripting command that names the various Oracle
files to suit the customers requirements.
37
A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. Typically,
you store the catalog in a dedicated database. A recovery catalog provides the following benefits:
A recovery catalog creates redundancy for the RMAN repository stored in the control file of each target database. The
recovery catalog serves as a secondary metadata repository. If the target control file and all backups are lost, then the
RMAN metadata still exists in the recovery catalog.
A recovery catalog centralizes metadata for all your target databases. Storing the metadata in a single place makes
a recovery that goes further back in time than the history in the control file. The added complexity of managing a recovery
catalog database can be offset by the convenience of having the extended backup history available.
Some RMAN features function only when you use a recovery catalog. For example, you can store RMAN scripts in a
recovery catalog. The chief advantage of a stored script is that it is available to any RMAN client that can connect to the
target database and recovery catalog. Command files are only available if the RMAN client has access to the file system
on which they are stored.
A recovery catalog is required when you use RMAN in a Data Guard environment. By storing backup metadata for all
primary and standby databases, the catalog enables you to offload backup tasks to one standby database while enabling
you to restore backups on other databases in the environment.
Because RAC is an Enterprise implementation of Oracle, we decided to use a Recovery Catalog in our data protection
strategy for the reasons shown above. If we had chosen not to use Recovery Catalog, we would have added an extra line to
the RMAN scripts in Appendix A.
Add line
RMAN> backup current controlfile;
Removed the reference to RECOVERY_CATALOG_STR=rman/cat@cat
Oracle Intelligent policies are not RAC Aware and with the Bender & RAC1 RAC Clusters, we decided to use the more
traditional Legacy Oracle RMAN scripting methodfavored by Oracle DBAs the world over.
With the Oracle Legacy backup scripted method supported in NetBackup, we can script the solution using RMAN to have
every node in the RAC cluster contributing to the backup (so called load balanced backup)which means the backups will
run fasterbut transactions may run slower whilst the backup is proceeding. Using Oracle Intelligent policies, the number
of parallel channels option is basically the number of streams the database is delivered to the backup target in, for instance.
The Legacy scripting method utilizes the NetBackup process bphdb to run the script as root on the database node. From this
node the script connects to all of the nodes in the cluster through Oracle Network Services and the progress is reported
through the Symantec Activity monitor. For Restore using the Legacy method or Oracle Intelligent Policiesthere is no
invocation from the Symantec GUI, instead the restore script has to be run from one of the RAC nodesbut again the
progress is reported through the Symantec Activity monitor.
38
Below, we see the Policy tabs for the Oracle Legacy scripted method for Oracle RAC backups using a two policy approach.
Policy 1bender-full-archive-run starts the RMAN script which in turn calls the Bender_2nd_Policy using the
NB_ORA_POLICY feature in RMAN that allows Symantec NetBackup parameters to be passed into the RMAN script. See
Appendix A for details. We will now work through the GUI/RMAN script process for Legacy scripted backups, which are the
best way of backing up Oracle RAC Clusters with Symantec NetBackup. On the Attributes tab we select the Oracle Policy type
and BenderBackupHBSU storage unit.
The Schedules tab in Policy bender-full-archive-run is standard but is split into AUTOMATIC and Default-Application
backups. This is normal and cannot be changed for this Policy type. When your schedule runs, it activates what is in effect a
user backup on the client which then runs its script and that script uses the default application backup schedule to actually
run. Without it, the backup will not run/work. Note that the job also takes its retention period from the default application
schedule and not your schedule.
39
In the Clients tab for bender-full-archive-runinstead of selecting instances as we would for an Oracle Intelligent Policy
backup, select Select Clients for use with scripts or templates and we enter the vip hostname (failover address) of the RAC
clusterin this example bender 1-vip as shown below.
On the Backup Selections tab, we point to an RMAN script location as shown below (the script is derived from templates
supplied by Symantec).
At this point, it is advisable to look at the highlighted parts of the sample scripts in Appendix A for this solutionthey are
the actual scripts used.
Note in particular the references in the scripts in Appendix A to Bender_2nd_Policy, which is passed into the RMAN script
through the tight integration or Oracle API and Symantec Librariesthis is a key part of the installation process.
Bender_2nd_Policy has been defined through NetBackup but linked to bender-full-archive-run via the RMAN script itself.
40
In the Schedules tabwe have integrated both aspects of our RMAN script, which runs both Database backup and archive
redo log backups under the titles of BENDER_FULL and BENDER_LOGSwhich have to match what is in the RMAN script.
The benefit of doing this (using two different schedules) is that we can also override the policy storage unit and use a
different one for this schedule. If we click on BENDER_LOGS, we can see for the archive redo logs we are using Policy
Storage BenderRedoLogsHBSU.
In the Clients tab of Bender_2nd_Policy, we select select clients for use with scripts and templates we want a load
balanced backup across all four bender RAC nodesso all are specified as clients in Bender_2nd_Policy.
41
Finally in Bender_2nd_Policy, there is nothing in the Backup selections tab because the RMAN Script is being called by
Bender-full-archive-run policy and Bender_2nd_Policy is only receiving the backup data.
And so that is how we configure Legacy Oracle Backups in Symantec NetBackup. The screenshot below shows a completed
job.
Note
How each client (RAC node) is acting as its own media server and backing up six streams of data with the six streams of
redo logs.
How although we started the job by running policy bender-full-archive-runthe policy doing all the work is
Bender_2nd_Policy, which is called from within the RMAN script shown in Appendix A.
The BENDER_FULL and BENDER_LOGS schedules both running one after the other.
Note
In the above screenshot, the two policies which are linked together by the RMAN script those are Bender-full-archive-run
and Bender_2nd_Policy. Also, note all four bender nodes partaking in the backup (load balanced) supplying six streams of
data each to the BenderBackupHBSU Catalyst target. The same process was used for the RAC1 Cluster.
You can also see in the above screenshot that schedule BENDER_LOGS also runs on each nodethis is because Oracle redo
logs are produced on all nodes whereas the Oracle database can be run only on selected nodes as the database files are
accessible for all the nodes.
42
Investigation results
Backup use cases
Three Oracle backup use cases were investigated whilst the HammerDB loading was runningto simulate the real world.
The backups also included the archive redo logsas is also typical in the real world. The throughput values below were
calculated by Total Data Transferred divided by Total time taken as reported by NetBackup. Because not all data files are
the same size and the archive logs are small and single stream, the throughput values do not reflect the Peak sustained
throughput observed using the Reporting central feature in HP StoreOnce. These values are shown in brackets (). Each
Database had its own catalyst High Bandwidth store created on StoreOnce.
1.
An online streaming full backup was taken utilizing a single Oracle RAC node with 24 RMAN channels allocated for the
backup. The average throughput for this case was 1.43 TB/hr (3.96 TB/hr peak sustained).
2.
Spreading the workload over all four Oracle RAC nodes for Bender database, increased the average throughput to
2.2 TB/hr (6.84 TB/hr sustained), while also spreading the CPU demands of the backup across all four Oracle RAC
nodes.
3.
Finally, two parallel database backups (Bender and RAC1) were run to the StoreOnce, with 12 RMAN channels allocated
for each database. The average throughput for both databases was 2.5 TB/hr (7.92 TB/hr) peak sustained.
Streams
Average throughput
24
1.43 TB/hr
Multi-node backup
24
2.2 TB/hr
2.5 TB/hr
43
Streams
Average throughput
24
1.85 TB/hr
24
1.75 TB/hr
1.9 TB/hr
but are shown in RMAN window that started the recovery. What is shown in the Activity monitor is the redo logs being
restored.
44
We have selected Job ID 5619, which is redo log restorelooking in the details (see below) we can see it is an Archive log
restore.
2.
The NetBackup media server (VMware backup host) initiates the VMware snapshot of the VM
3.
4.
5.
NetBackup Client (backup host) reads the snapshot from the datastore and writes the data to the NetBackup storage
unit
6.
45
Figure 17. Overview of the VMware VADP backup process and its integration with Symantec NetBackup
In this example the master server, media server, and Backup host are all the same machine for clarity. In the actual
investigation they were separate servers. Symantec NetBackup interfaces with the VMware VADP API, add to that the
NetBackup Accelerator functionality and that is what makes this Symantec solution so powerful.
Understanding NetBackup Accelerator
HP StoreOnce supports Symantec NetBackup Accelerator with all file system types and VMware VMs. This clever Symantec
IP is advertised as Full backups at the speed of incrementals and an explanation of the concept is shown below. The best
usage models for NetBackup Accelerator are:
46
1.
Traditional NDMP backup of filer dataMount volumes on NetBackup clients which can use accelerator, this is much
faster than the traditional NDMP backup method used on file servers.
2.
File systems with large number of small files with a small daily change rateThe changed block detection is much
faster than the tradition tree walk of such nested file systems.
3.
Remote Office Branch Office backup from multiple sites to a single StoreOnce applianceThe best of both worlds
minimal data transferred across the WAN link and it is deduplicated and a synthetic (accelerated full) is always available
for restore.
4.
Installed base where customers are not able to satisfy backup SLAs with existing backup policy typesNormal Full,
Flash Backup, and Synthetic Full etc. Symantec themselves promote accelerated backup as the best/preferred option
of all their synthetic full techniques.
The above diagram shows accelerator support today (Any file system + VMware VMs). The Media server plays a key role in
deciding what data it knows of already and produces an inline synthesis set of commands for StoreOncedata that is
unchanged is cloned (using pointers) and the New data detected is writtenas shown belowthis all happens inside
the StoreOnce appliance.
Figure 19. Real time synthetic full creation on StoreOnce using NetBackup Accelerator
Synthesis relies on the dedupe appliances ability to support Clone Extent OST system calls to clone large and small
volumes of data during the synthesis of the full backup on the dedupe appliance itself.
The real intellectual property in this solution is the Symantec Change track log file for file systems and VMware VMs. Change
tracking kicks in during a backup job to record the info about files present in the backup selection only, not the entire file
system; one tracking file for each policy. Change track log:
Intelligently tracks info about segments within files rather than at a file levelSymantec IP.
It eliminates the need to do a tree walk of the entire file system.
If customers already use NTFS journaling, they can co-exist with the same but the presence of either is not mutually
exclusive. Using NTFS change journal can actually speed up the changed block discovery process. The changed block
information is only present in the NetBackup Changed Block tracking file.
47
NetBackup Client agent works, with the help of NetBackup change track log to send only the Changed Blocks along with
the Backup ID, backup extents and offsets for the unchanged data to the Synthesis Engine in the Media Server, which
creates a NetBackup InlineAcceleratedSynthesized full backup.
The Change Track Logs size depends on the number of files and the size of the files in the file system and is not dependent
on the rate of change.
Symantec NetBackup Accelerator detects changed blocks in file systems, an extension of this for VMware VMs is to use the
change block tracking (CBT) feature of VMware to register changed blocks for VMs. NetBackup Accelerator only works with
HP StoreOnce Catalyst backup targets.
Unlike previous generations of synthetic backupswhich happened post backupNetBackup Accelerator happens real
time as the backup is progressing with a series of write and clone commands onto the StoreOnce unit depending on if
the data is new (writes) or unchanged (cloned) from the previous backup.
Symantec NetBackup and VMware VADP integration features
Automatic selection of VMs for backup
Block level incremental (BLIB)Changed block tracking (CBT) supported
Windows uses VSS provider in VM ToolsOptional Symantec VSS provide for feature of truncating Exchange logs
Supports NetBackup AcceleratorMaking use of the CBT tracking capability of VMware
Linux VMs require additional SYMCquiesce utility to be loaded for file system backup consistency
48
Next, add the vCenter server to the Virtual Machine Servers section in the NetBackup console as shown below.
49
In these scenarios, we are going to use the media server media as the data mover, which will take the VADP snapshots,
process them through NetBackup Accelerator on the Windows 16 clients, and then deduplicate them before sending them
to StoreOnce to a Catalyst store we have called Accelerator (see below). To enable accelerator, simply tick the use
accelerator in the Attributes screen of the VMware Policy screen as shown below.
On the Clients tab, only one client is shown below for clarity but the final policy had all the six Windows VMs configured as
clients.
By default, all local drives are chosen for the Backup Selection.
50
Then we have the choice of specific options and transport unique to VMware, notice we have ticked the enable file recovery
from VM backup which allows us to restore a full vmdk file or just a single file from the same backup.
Average throughput
Size of data
Initial Full
10.04 GB
190 sec
10.4 GB
300 sec
10.4 GB
199 sec
Notes on performance:
Job time is not limited to data transfer duration but also includes snapshot time, transport time, and snapshot deletion
time
Snapshots tend to use only one streamso in this policy, we will be sending six streams in total to the StoreOnce unit
51
52
Then click File on the top toolbar then click Specify NetBackup Machines and Policy types to get the dialog box to specify
restore configuration.
For restores, always use the Client name that is in the NetBackup Catalog entry e.g., windows3.
Click search VM clients to browse the Symantec catalog to find the latest version of the VM to restore.
Only master server has access to Catalog infoso set master server as server to use for restores in the restore wizard.
53
2.
VMs recovery
To restore FULL VM, click Restore from Virtual Machine backup as shown below.
54
Both methods then walk you through a restore wizard as shown below. Choose original or alternate location for restore.
Choose the recovery host (data mover) and transport method. We have dedicated media server media to VM backups and
restores in this environment.
55
56
Click Start Recovery..Monitor restore in Activity monitor. The full VM restore takes only 31 sec.
57
Click Start Restore of Marked Files icon and then select options presented before hitting Start restore.
58
Table 9. VMware recovery performance results in single VMFull VM restore and single file restore.
VMware recovery performance
Use case
Average throughput
Size of data
Full VM recovery
50 MB/sec
10425 MB
204 sec
20 MB/sec
691 MB
35 sec
Summary
With HP BladeSystem, you get a modular solution design that can scale with the demands and growth of your workloads.
This provides you with a simplified and consistent approach to key processes for Oracle databases: data protection,
recovery, disaster recovery, provisioning, cloning, replication, migration, etc. In conclusion, the key takeaways from this joint
HP and Symantec NetBackup could be defined as follow:
Symantec NetBackup combined with HP StoreOnce deduplication capability provide the good RPOs/RTOs for virtualized
Catalyst technology that accelerates time to deployment, and reduces risk and costs while maintaining overall application
service-level objectives.
NetBackup licensing
Symantec NetBackup deploys two licensing methods:
Traditional (a la carte) paying for each component usedMedia/master server licensing is CPU socket based.
Capacity Front End Terabyte (FETB) licensingWhere nearly all the advanced features are included per TB. The capacity
59
For this virtualized environment, the licensing is based on Platform Base license for around 6 FETB and the DPOO license
(add on functionality for OST [Catalyst] and NetBackup Accelerator) priced for around 6 FETB.
In addition, for Oracle integration, the Symantec NetBackup Application and DB pack is required.
StoreOnce licensing
For StoreOnce, the only licensing required is for the use of the Catalyst (OST) backup target type. This is not capacity based
but covers the whole StoreOnce 4700 from base capacity to max capacity. Additional licensing on a replication target device
would be required if we wanted to replicate the Catalyst stores to another site for DR purposes. DR is particularly well
supported with Symantec using Storage Lifecycle policies, which control the replication and Targeted AIR, which can
automatically update the catalogs across different NetBackup domains.
60
In the example below, we have 24 backup streams (6 per node); filesperset = 5, maxopenfiles = 5, to optimize performance
and deduplication ratio. Then we have the Main BACKUP command, this is followed by the archive logs where we still use
24 streams but filesperset = 20 so that the archive logs (which are not very dedupable) are backed up faster. This
configuration is to make the backup as fast as possible.
NB_ORA_XXXX files are a way of passing NetBackup parameters into RMAN and vice versa, such as BENDER_FULL as the
whole database backup policy directive and BENDER_LOGS as the archive log policy directive. The BENDER_FULL policy
sends data files to one Catalysts store whereas the BENDER_LOGS policy sends the archive redo logs to a separate Catalyst
store.
This same script can be modified for incrementals by changing the incremental level from 0 to 1.
BACKUP
INCREMENTAL LEVEL=0
Dual policy approach with separate policy storage for data files and archive redo logs
Each Allocate string in the RMAN script example below has to have a login to the relevant RAC node identified in the allocate
command.
From policies, we start policy.
Bender-full-archive, which in turn calls Bender_2nd_Policy as shown in the script below.
Recovery Catalog is also being used.
#!/bin/sh
ORACLE_HOME=/home/oracle/app/oracle/product/12.1.0/dbhome_1
export ORACLE_HOME
ORACLE_SID=borcl
export ORACLE_SID
RMAN=$ORACLE_HOME/bin/rman
TARGET_CONNECT_STR=sys/oracle@borcl
RECOVERY_CATALOG_STR=rman/cat@cat
RMAN_LOG=/usr/bharth/rman-out.log
export RMAN
export TARGET_CONNECT_STR
export RECOVERY_CATALOG_STR
export RMAN_LOG
CMD_STR="
$RMAN target $TARGET_CONNECT_STR rcvcat $RECOVERY_CATALOG_STR log $RMAN_LOG append
<< EOF
#$RMAN target $TARGET_CONNECT_STR rcvcat $RECOVERY_CATALOG_STR << EOF
RUN
{
ALLOCATE CHANNEL T1 TYPE SBT_TAPE CONNECT='sys/oracle@borcl1'
PARMS='ENV=(NB_ORA_CLIENT=bender1.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender1_channel1_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T2 TYPE SBT_TAPE CONNECT='sys/oracle@borcl1'
PARMS='ENV=(NB_ORA_CLIENT=bender1.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender1_channel2_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T3 TYPE SBT_TAPE CONNECT='sys/oracle@borcl1'
PARMS='ENV=(NB_ORA_CLIENT=bender1.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender1_channel3_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
61
62
PARMS='ENV=(NB_ORA_CLIENT=bender3.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender3_channel18_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T19 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender4_channel19_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T20 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender4_channel20_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T21 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender4_channel21_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T22 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender4_channel22_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T23 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender4_channel23_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
ALLOCATE CHANNEL T24 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_FULL)' FORMAT
'Bender4_channel24_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 5 ;
BACKUP
INCREMENTAL LEVEL=0
FILESPERSET 5
DATABASE;
63
64
PARMS='ENV=(NB_ORA_CLIENT=bender3.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender3_channel15_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A16 TYPE SBT_TAPE CONNECT='sys/oracle@borcl2'
PARMS='ENV=(NB_ORA_CLIENT=bender3.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender3_channel16_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A17 TYPE SBT_TAPE CONNECT='sys/oracle@borcl2'
PARMS='ENV=(NB_ORA_CLIENT=bender3.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender3_channel17_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1;
ALLOCATE CHANNEL A18 TYPE SBT_TAPE CONNECT='sys/oracle@borcl2'
PARMS='ENV=(NB_ORA_CLIENT=bender3.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender3_channel18_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A19 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender4_channel19_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A20 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender4_channel20_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A21 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender4_channel21_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A22 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender4_channel22_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A23 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender4_channel23_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
ALLOCATE CHANNEL A24 TYPE SBT_TAPE CONNECT='sys/oracle@borcl4'
PARMS='ENV=(NB_ORA_CLIENT=bender4.sdnsdomain.net,NB_ORA_POLICY=Bender_2nd_Policy,
NB_ORA_SERV=master.sdnsdomain.net,NB_ORA_SCHED=BENDER_LOGS)' FORMAT
'Bender4_channel24_Arch_Log_D%d_I%I_P%p_S%s_T%t ' maxopenfiles 1 ;
BACKUP
filesperset 20
ARCHIVELOG ALL
skip inaccessible
DELETE INPUT;
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
A1;
A2;
A3;
A4;
A5;
A6;
A7;
A8;
A9;
A10;
A11;
A12;
A13;
A14;
65
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
T1;
T2;
T3;
T4;
T5;
T6;
T7;
T8;
T9;
T10;
T11;
T12;
T13;
T14;
T15;
T16;
T17;
T18;
67
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
RELEASE
}
EOF
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
CHANNEL
T19;
T20;
T21;
T22;
T23;
T24;
For point in time recovery, you can use the RMAN restore Syntax
RMAN>
RMAN>
RMAN>
RMAN>
startup mount;
restore database until time 'sysdate 1';
recover database;
alter database open;
Resources
HP StoreOnce Backup System user guide
HP StorageWorks D2D Backup System
Symantec NetBackup 7.6 Admin Guide
Symantec NetBackup Oracle Admin Guide
Symantec NetBackup VMware Admin Guide
HP Storage
HP BladeSystem
HP OneView
HP 3PAR StoreServ Storage
VMware
Learn more at
hp.com/go/StoreOnce
hp.com/go/burasolutions
Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for
HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Intel Xeon is a trademark of Intel Corporation in the U.S. and other countries. Microsoft, Windows, and Windows Server are trademarks of the Microsoft group
of companies. Oracle is a registered trademark of Oracle and/or its affiliates. Red Hat is a registered trademark of Red Hat, Inc. in the United States and other
countries. UNIX is a registered trademark of The Open Group. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. microSD is a
trademark or registered trademark of SD-3C in the United States and other countries or both. VMware is a registered trademark or trademark of VMware, Inc.
in the United States and/or other jurisdictions.
4AA5-8661ENW, May 2015