Backup and Recovery solution for HPE … · with Commvault Data Platform and HPE StoreOnce ....

Backup and Recovery solution for HPE ConvergedSystem 700 with Commvault Data Platform and HPE StoreOnce Reference architecture and best practices for Backup and Recovery

Reference Architecture

http://www.hpe.com


Contents Executive summary ................................................................................................................................................................................................................................................................................................................................ 4 Introduction to HPE ConvergedSystem 700 2.0 ........................................................................................................................................................................................................................................................ 5 Solution overview ..................................................................................................................................................................................................................................................................................................................................... 6 Technology overview ........................................................................................................................................................................................................................................................................................................................... 6

HPE ConvergedSystem 700 solution overview .................................................................................................................................................................................................................................................... 6 HPE Converged Architecture 700 overview ........................................................................................................................................................................................................................................................ 12 HPE 3PAR StoreServ 7400c – key features and benefits....................................................................................................................................................................................................................... 12 HPE StoreOnce – key features and benefits ........................................................................................................................................................................................................................................................ 12 Commvault Data Platform – key features and benefits ............................................................................................................................................................................................................................... 15 Commvault CommCell Anatomy ..................................................................................................................................................................................................................................................................................... 15

Backup definition.................................................................................................................................................................................................................................................................................................................................. 16 Data pipeline ...................................................................................................................................................................................................................................................................................................................................... 17 Benefits of deploying HPE StoreOnce with Commvault software .................................................................................................................................................................................................... 17

Installation and configuration of Commvault software ........................................................................................................................................................................................................................................ 17 Commvault Backup and Recovery infrastructure components .......................................................................................................................................................................................................... 17 Configuring Commvault software with HPE StoreOnce .............................................................................................................................................................................................................................. 19 Configuring Commvault software with HPE 3PAR StoreServ 7400c Storage ........................................................................................................................................................................ 21

Commvault Oracle RAC 12c integration ........................................................................................................................................................................................................................................................................ 22 Test bed architecture overview ............................................................................................................................................................................................................................................................................................... 28 Solution components ........................................................................................................................................................................................................................................................................................................................ 29

HPE ConvergedSystem 700 tested configuration ......................................................................................................................................................................................................................................... 29 Software configuration ............................................................................................................................................................................................................................................................................................................. 29 Storage configuration ................................................................................................................................................................................................................................................................................................................ 30 HPE StoreOnce 4700 configuration............................................................................................................................................................................................................................................................................ 30 Networking .......................................................................................................................................................................................................................................................................................................................................... 31 Workload ............................................................................................................................................................................................................................................................................................................................................... 31

Commvault tuning guidelines ................................................................................................................................................................................................................................................................................................... 33 Number of clients .......................................................................................................................................................................................................................................................................................................................... 33 MediaAgent sizing ........................................................................................................................................................................................................................................................................................................................ 33 Backup types ..................................................................................................................................................................................................................................................................................................................................... 33

IntelliSnap .................................................................................................................................................................................................................................................................................................................................................... 33 Backup configuration ....................................................................................................................................................................................................................................................................................................................... 33

Backup from snapshot .............................................................................................................................................................................................................................................................................................................. 34 Oracle Database backup procedure ................................................................................................................................................................................................................................................................................... 34

Backup use cases ........................................................................................................................................................................................................................................................................................................................... 36 Backup best practices for virtualized Oracle RAC 12c................................................................................................................................................................................................................................ 36


Oracle Database recovery procedure ................................................................................................................................................................................................................................................................................ 36 Restore from HPE StoreOnce Backup ........................................................................................................................................................................................................................................................................ 41 Recovery use cases...................................................................................................................................................................................................................................................................................................................... 41 Recovery best practices for virtualized Oracle RAC 12c ............................................................................................................................................................................................................................ 41

Commvault and VMware integration ................................................................................................................................................................................................................................................................................. 41 Key features ........................................................................................................................................................................................................................................................................................................................................ 42 Backup best practices for VMware-generalized workloads ...................................................................................................................................................................................................................... 43 Configuring Commvault software with VMware ................................................................................................................................................................................................................................................. 43 Backup configuration .................................................................................................................................................................................................................................................................................................................. 45 Backup use cases........................................................................................................................................................................................................................................................................................................................... 45 Recovery use cases...................................................................................................................................................................................................................................................................................................................... 46

Commvault licensing ......................................................................................................................................................................................................................................................................................................................... 49 Summary ...................................................................................................................................................................................................................................................................................................................................................... 49 Appendix A: Bill of materials ...................................................................................................................................................................................................................................................................................................... 49 Appendix B: Solution hardware configuration and components .............................................................................................................................................................................................................. 51

Components ....................................................................................................................................................................................................................................................................................................................................... 52 Resources and additional links ................................................................................................................................................................................................................................................................................................ 55


Executive summary When it comes to protecting business and mission critical applications and databases, it is not just about protecting and recovering data but more about restoring business services. Hewlett Packard Enterprise Backup and Recovery Solutions provide data protection and meet aggressive service level objectives while delivering more control and visibility to application owners.

Applications that are core to the success of your business are often classified as mission critical or business critical. Their tolerance 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 on a very complex set of hardware and software. But advancements in hypervisor technology now lets you deploy these applications as virtualized workloads, for added scalability and rapid deployment. Many organizations rely on virtualization to improve security and compliance requirements, increase data center flexibility, simplify deployment and management, improve operational efficiencies, and achieve lower total cost of ownership (TCO) goals. 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/down/out/in to address infrastructure allocation requirements as workloads change. To meet these needs, HPE has created ConvergedSystem 700 (CS700) and Converged Architecture 700 (CA700). The solution is proven, tested, and optimized to help you meet long-term data center needs for a variety of mixed application workloads.

Advances in technology are lowering barriers to entry, while consumerization is driving change from the outside in. In the new idea economy, success will be determined by your ability to transform IT to meet the new expectations of consumers and business customers and to grow your business in new ways. HPE ConvergedSystem and HPE Converged Architecture can help you achieve this. Hewlett Packard Enterprise can help you build your next-generation data center on a converged system architecture that will improve IT agility and drive speed, efficiency, and simplicity, all while reducing risk. Your business transformation starts with simplifying and automating as much of your server, storage, and networking infrastructure as possible, creating a software-defined environment that frees up resources for new and innovative projects.

Achieve real business benefits with integrated solutions using HPE CS700 and HPE CA700. These allow you to have the efficient building blocks for providing hybrid IT, enabling you to adapt quickly to market and customer needs. And it maximizes the hybrid infrastructure speed, efficiency, and simplicity of your core infrastructure and operations.

HPE Converged Architectures are modular, repeatable and scalable building blocks designed for your workloads. It is infrastructure your way, delivered as one integrated stack by your choice of HPE Authorized Channel Partner. These validated reference architecture designs are thoroughly tested by HPE engineering to reduce risk, save you time and resources. Designed for speed and efficiency they provide an ideal infrastructure to run your common workloads and applications. New workloads and business demands are forcing customers to reevaluate the way they purchase and manage infrastructure. Do-it-yourself and integrated systems assembled from components provided by multiple vendors often cause increases in cost, time, and effort as well as create complexity with interoperability challenges. Both HPE ConvergedSystem 700 and HPE Converged Architecture 700 address these new requirements with tightly integrated components that are optimized to support on-demand IT infrastructure, private cloud, and mixed workloads. Preconfigured to meet a range of business needs, HPE ConvergedSystem 700 and HPE Converged Architecture 700 can be deployed easily and rapidly to support a variety of virtualized application environments. HPE engineering has done the testing and validation so that IT professionals can focus their time on critical activities. Specific technology has been included in the system that addresses critical business objectives such as lower costs, increased performance, and high availability. Each system ships with factory-integrated compute, storage, networking, and management components, all preconfigured to address the most demanding workloads. Converged management and automation capabilities are built into the HPE ConvergedSystem 700 that allow customers to simplify everyday tasks through single pane of glass management. Compute and storage can be scaled independently so customers can easily adapt to new requirements and enable the solution to grow as business needs change. One-stop support from the HPE Center of Excellence (CoE) provides a single point of accountability with faster problem resolution.

HPE ConvergedSystem and HPE Converged Architecture solutions along with HPE StoreOnce and Commvault software acts as a single solution to protect all of your data assets. This solution provides support for multiple databases, and applications in the enterprise today. Enterprise class data protection is offered by HPE ConvergedSystem 700 and HPE Converged Architecture 700 using HPE StoreOnce technologies and Commvault capabilities. 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 Commvault Virtual Server Agent.

Target audience: This document is intended for solution architects, data center administrators, and user, wishing to learn more about backup and recovery solutions on HPE ConvergedSystem 700. A working knowledge of Linux®, Oracle Databases and virtualization is recommended.


Document purpose: The purpose of this document is to describe a recommended architecture/solution, highlighting recognizable benefits to technical audiences.

This white paper describes a project developed by Hewlett Packard Enterprise in March 2016.

Disclaimer: Products sold prior to the separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. on November 1, 2015 may have a product name and model number that differ from current models.

Introduction to HPE ConvergedSystem 700 2.0 HPE ConvergedSystem 700 2.0 with HPE StoreOnce and Commvault Data Platform can provide an excellent backup and recovery solution for Oracle Databases. HPE ConvergedSystem 700, with its seamless computing, virtualization and mobilization, is well suited for the Oracle Database application. Each system ships with factory-integrated compute, storage, networking, and management components, all preconfigured to address the most demanding workloads. Converged management and automation capabilities are built into the HPE ConvergedSystem 700 that allow customers to simplify everyday tasks through single pane of glass management. Compute and storage can be scaled independently so customers can easily adapt to new requirements and enable the solution to grow as business needs change. One-stop support from the HPE Center of Excellence (CoE) provides a single point of accountability with faster problem resolution.

HPE ConvergedSystem 700 can be extended to support a variety of application workloads through validated reference architectures (RAs). HPE RAs allow customers to deploy applications with confidence by reducing risk and accelerating application deployment through a proven and tested methodology. These RAs provide recommendations for workload-specific configurations for deploying applications such as Citrix® XenDesktop®, Microsoft® Exchange/SharePoint mixed workloads, and Database Consolidation with SQL Server and Oracle Database. For more information visit: hpe.com/info/ra.

HPE ConvergedSystem 700 helps customers drive business agility with solutions that enable them to adapt to the market and customer needs quickly. It delivers a broad range of benefits, including:

• Fast: HPE ConvergedSystem 700 enables you to reduce the time to insight and action through automated deployment, provisioning, and predictive analytics. It allows you to provision infrastructure in a matter of minutes while being able to identify and respond to hot spots more quickly.

• Efficient: HPE ConvergedSystem 700 features automated converged management that radically simplifies everyday tasks to reduce operating expenses and improve operational agility. It features templates that eliminate many manual operations and device-focused processes enable you to refocus your investment on innovation, not operations, by lowering the TCO of your general purpose infrastructure. It provides true business transformation, via a solution lifecycle management, to increase IT operational efficiency and a reduction in administration time.

• Simple: Easily stand up and manage new services for your business partners. Fewer management tools are required through converged management. Software-defined templates make on-demand IT infrastructure services deployment faster and easier.

Understanding the needs of organizations when it comes to disaster recovery and providing the technology to ensure business continuity to operate with minimal interruption are two key elements for a successful customer experience. Commvault Disaster Recovery Solutions address both the physical and virtual environments ensuring critical data, applications, and complete systems are protected. This reduces the complexity of managing heterogeneous server and storage platforms, reduces the costs of building and managing the disaster recovery infrastructure, and provides a single console to recover from in the event of a disaster.

In this paper, we will examine backup and recovery for both mission-critical applications and generalized virtual machine workloads.

• Oracle RAC represents the mission critical application, managed with the Commvault Oracle Database iDataAgent.

• Recovery of generalized virtual machine workloads, managed by the Commvault Live Sync feature.

All of these advanced data management features can be supported on HPE StoreOnce.

This configuration was tested and validated on the HPE ConvergedSystem 700 2.0. The solution is also applicable on HPE Converged Architecture 700 platforms.

http://www.hpe.com/info/ra


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, that need deep integration with the data management system are protected using the Commvault iDataAgent. For generalized workloads, Commvault Virtual Server Agent for VMware® provides a unified protection and recovery vehicle for all virtual machines.

Technology overview HPE ConvergedSystem 700 solution overview While many data centers use virtualization, decision-makers still need to address a broad range of challenges, including:

• Time, resources, and effort required to deploy a complete solution

• Proliferation of management tools

• Security issues

• Difficulties in scaling

• Difficulties in extending to the cloud

HPE ConvergedSystem 700 is designed to address these challenges through a precision-tuned system that helps deliver the fastest path to agile, efficient virtualized application solutions. HPE ConvergedSystem 700 offerings can be easily and rapidly deployed to support a variety of virtualized application environments. HPE does all the work, using balanced building blocks of servers, storage, and networking, along with integrated management software and bundled support.

HPE ConvergedSystem 700 delivers proven virtualized infrastructure, with integrated software, hardware, services, and support – all delivered as a single, proven solution that can support multiple hypervisors and is enabled for cloud management.

Much of the hardware and software contained in the solution stack is partner-integrated. Close engineering links between HPE and VMware have resulted in application programming interfaces (APIs) and other cross-intellectual property offerings, designed to help minimize complexity and simplify management and interaction.

Key benefits of HPE ConvergedSystem 700 • A pre-engineered and validated system that is optimized for today’s most challenging workloads.

• One infrastructure management platform to simplify everyday tasks and free up IT resources.

• Reduces risk by preventing issues proactively and maintaining peak performance.

• Cloud compatibility allows customers to upgrade easily to cloud with confidence.

HPE ConvergedSystem 700 is extremely agile, with a broad range of configurations available. Based on a common, scale-out architecture, it starts with as few as two workload servers and can scale up to 128 servers with multiple storage options. Compute and storage can be customized and scaled individually, providing the ability to deliver the right mix of performance for unique customer requirements.

This section provides more detail on the hardware components used in HPE ConvergedSystem 700 and presents views of a representative range of recommended HPE ConvergedSystem 700 solutions.

Minimum configurations: • Multi-rack with one HPE BladeSystem c7000 enclosure and HPE 3PAR StoreServ 74x0c 2-node Storage (Figure 1)

• Single-rack with one HPE BladeSystem c7000 enclosure and HPE 3PAR StoreServ 7440c 2-node Storage (Figure 2)

Sample configuration: • Compute and storage racks with two HPE BladeSystem c7000 enclosures and HPE 3PAR StoreServ 7400c 4-node Storage (Figure 3)


Maximum configuration: • Three compute racks with eight HPE BladeSystem c7000 enclosures and two storage racks with HPE 3PAR StoreServ 74xxc Storage

(Figure 4)

Note HPE 3PAR StoreServ component racking locations may vary due to customized configurations.

Note The HPE 3PAR StoreServ Storage configuration may vary depending on customer configuration and options. Each HPE 3PAR StoreServ array may include expansion racks (not pictured in Figure 4) as an option.

To help size an appropriate HPE ConvergedSystem 700 solution, Hewlett Packard Enterprise recommends a range of configurations as shown in Table 1.

Table 1. Recommended configurations for HPE ConvergedSystem 7001

Storage Raw capacity Workload servers Physical cores2 SAN ports3

HPE 3PAR StoreServ Array

7200c 26 TB 12 192 24

7200c/7400c/7440c 2N 51 TB 16 256 24

7440c/7450c 2N 41 TB 16 256 24

7400c/7440c 2N/4N 118 TB 32 512 32/44

7440c/7450c 2N 83 TB 32 512 32

7400c/7440c 4N 211 TB 48 768 76

7440c/7450c 4N 110 TB 48 768 76

7400c/7440c 4N 235 TB 64 1,024 84

7440c/7450c 4N 138 TB 64 1,024 84

For more information on HPE ConvergedSystem 700 (CS700), refer to the HPE ConvergedSystem 700 2.0 QuickSpecs, available at: http://h20195.www2.hpe.com/V2/GetHtml.aspx?docname=c04505387.

High availability Designed for high availability, HPE ConvergedSystem 700 minimizes single points of failure by including:

• Multiple workload servers

• Clustered management servers with shared SAN storage to support the solution-specific management software stack

• Dedicated networks to allow the migration of VMs without impacting users

• Redundant network switches, HPE Virtual Connect FlexFabric modules and Onboard Administrator modules

1 These configurations assume that no deduplication is being used. Deduplication is available only for SSDs. 2 Assuming eight-core processors are used. 3 Available ports on HPE StoreFabric SAN switches; not all ports consumed in each configuration.

http://h20195.www2.hpe.com/V2/GetHtml.aspx?docname=c04505387


• Redundant power design with redundant HPE Power Distribution Units

• Redundant SAN switches with Dynamic Path Selection (DPS) capability, to dynamically route Fibre Channel traffic across multiple links between HPE 3PAR StoreServ Storage and hosts

• Automatic storage failover and failback; multiple RAID protection levels

• Multiple copies of data optimized within the storage array, eliminating any single point of failure in the SAN while providing very fast access; applications have continuous data availability in the event of a disk controller or storage node failure

Converged Management At the heart of HPE ConvergedSystem 700 is HPE OneView, which provides converged management to eliminate the complexity of managing infrastructure through automation. HPE OneView architecture delivers a unified and consistent management experience across the infrastructure in the system, including the workload servers contained in HPE BladeSystem, HPE 3PAR StoreServ Storage and HPE Networking. It uses a software-defined approach to system management enabling you to capture and standardize the best practices from your IT team. For example, it utilizes profiles to capture the entire configuration for a resource and stores them in a single place for easy management. HPE OneView capabilities can be extended through integration into VMware vCenter Operations Manager. This provides administrators with increased visibility and control over performance and capabilities, while ensuring service levels and operational efficiency in dynamic virtualized environments, all through a single pane of glass.

Preintegration HPE ConvergedSystem 700 is preintegrated in the factory based on extensively tested configuration guidelines. All of the components prescribed are prebuilt, racked and cabled prior to being delivered at the customer site. This process ensures an integrated hardware solution, a consistent and repeatable initialization and a known end state when it arrives at the customer site. If the HPE ConvergedSystem 700 for VMware is being deployed, the system will be ready to deploy production virtual machines. Each virtualization host has VMware vSphere 5.5 preinstalled through automation capabilities, customized to a predefined network and storage infrastructure, and preregistered to the vCenter server that is installed on the management VM.

Simplified lifecycle HPE ConvergedSystem 700 provides customers with a solution support experience with a single point of accountability. HPE offers Proactive Care with Personalized Support Option as well as Proactive Select to support the entire solution including HPE hardware, software, VMware and Microsoft OS software. This support experience is part of the HPE ConvergedSystem Center of Excellence (CoE). When a support call is placed with HPE for this system, it is initially recognized as being related to a ConvergedSystem and routed to a specialist who understands and will support the entire solution. This specialist will also own the issue until it is closed resulting in faster problem resolution. The HPE CoE provides the customer with:

• Global Support Team

• 24/7 coverage

• Support of the end-to-end solution stack

• End-to-end case/customer ownership

• Integrated escalation function

• Orchestration of service delivery

• Active collaboration with other support parties (e.g., VMware)

Accelerated path from virtualization to cloud If you wish to accelerate the path from virtualization to cloud, HPE ConvergedSystem 700 has been architected to support the use of HPE CloudSystem functionality in a virtual environment. Alternatively, if you have standardized on the VMware platform for cloud automation, you can add VMware vCloud Suite to extend the capabilities of HPE ConvergedSystem 700.

Note Because management and virtualization layers are preintegrated and optimized, the turnkey HPE ConvergedSystem 700 solution is ready to work with the specific virtualization technologies you use. For example, HPE OneView is tightly integrated with VMware vSphere 5.5.


Minimum configuration with multi-rack, one c7000 enclosure and HPE 3PAR StoreServ Storage

Figure 1. Front view of an HPE ConvergedSystem 700 solution featuring two workload servers and HPE 3PAR StoreServ Storage

Note The HPE 3PAR StoreServ Storage configuration may vary depending on the customer order.


Minimum configuration with single rack, one c7000 enclosure and HPE 3PAR StoreServ Storage

Figure 2. Front view of an HPE ConvergedSystem 700 single rack solution featuring two workload servers and HPE 3PAR StoreServ Storage 2-node array in the default racking location

Note The HPE 3PAR StoreServ Storage configuration may vary depending on the customer configurations and options.


Sample configuration with compute and storage racks, two c7000 enclosures and HPE 3PAR StoreServ Storage

Figure 3. Front and rear views of the compute and storage resources for HPE ConvergedSystem 700 solution featuring two c7000 enclosures and HPE 3PAR StoreServ 7400c 4-node Storage

Example of maximum configuration with eight c7000 enclosures and HPE 3PAR StoreServ Storage

Figure 4. Front view of an HPE ConvergedSystem 700 solution featuring 128 workload servers and HPE 3PAR StoreServ Storage


HPE Converged Architecture 700 overview The HPE Converged Architecture 700 is delivered as a flexible and validated reference architecture. It provides configuration, sizing and deployment details that reduce your risk and TCO. Based on a full HPE stack of HPE BladeSystem, HPE 3PAR Storage, HPE Networking and HPE OneView infrastructure management software, the HPE Converged Architecture 700 can be easily modified to fit within your existing networking requirements to accommodate the tools you use and support multi-generational HPE ProLiant Server Blades, including ProLiant Gen9. This architecture delivers interoperability with a choice of third-party top-of-rack network switches and hypervisors from leading industry vendors. The HPE Converged Architecture 700 provides an easy upgrade path to HPE Helion CloudSystem. You can deploy at your site with your Channel Partner who can provide value add services tailored to fit your needs. Rounding out the solution is a variety of lifecycle support options that are also available.

Table 2. Variety of life cycle support options

Fast

From faster time to value to faster problem resolution

Simple

Easy to buy, manage and support

Efficient

Increased IT operational efficiency, performance and SLA while reducing infrastructure costs

• Converged Architecture is based on purpose-built, repeatable building blocks designed for speed and efficiency

• Deploy with trusted HPE partners who can provide value added services to address your needs.

• Accelerate enterprise workload deployment such as virtualization and cloud computing up to 66X faster

• Design delivers openness, choice in 3rd party networking to fit your workloads, protection for your investments

• A variety of lifecycle support options tailored to fit your needs

• Validated reference architecture designs for your most common workloads

• Simplify IT operations with leading management and support

• Channel delivery provides increased choice and flexible integration, either on-site at customer or through channel partner

• Validated and designed for enterprise scalability

• Tuned for your trusted channel partner via integration

• Delivers business agility and provides an easy upgrade path to HPE Helion CloudSystem

HPE 3PAR StoreServ 7400c – key features and benefits HPE 3PAR StoreServ Storage offers the performance and flexibility that you need to accelerate new application deployments and support server virtualization, cloud, IT as a Service (ITaaS), and your future technology initiatives. It is a storage platform that allows you to spend less time on management, gives you technically advanced features for less money, and allows you to eliminate tradeoffs that require you to sacrifice critical capabilities such as performance and scalability. With HPE 3PAR StoreServ Storage, you can serve unpredictable and mixed workloads, support unstructured and structured data growth, and meet both file and block storage needs.

The modular HPE 3PAR StoreServ Architecture can be scaled from 1.2 TB to 1.2 PB, making the system deployable as a small, or very large centralized system. Until now, enterprise customers were often required to purchase and manage at least two distinct architectures to span their range of cost and scalability requirements. HPE 3PAR StoreServ Storage is the ideal platform for virtualization and cloud computing environments. The high performance and scalability of the HPE 3PAR StoreServ Architecture is well suited for large or high-growth projects and consolidation of mission-critical information, demanding performance-based applications and data lifecycle management.

For more details on product ranges, visit: hpe.com/storage.

HPE StoreOnce – key features and benefits HPE StoreOnce is a dedicated backup appliance with deduplication available in a range of models from 1 TB to 2240 TB. Some models are available as VMs and others are available as physical hardware appliances. HPE StoreOnce offers significant savings in storage costs because of deduplication and allows customers to keep pace with increasing data growth. A further advantage of deduplication is that it enables low-bandwidth replication allowing for off-siting of data in a very cost-effective and efficient way. Each HPE StoreOnce unit can support any mix of VTL NAS (CIFS and NFS) and HPE StoreOnce Catalyst stores – to allow it to function in the widest range of environments/usage models and with the widest range of software.

For more details on product ranges and compatibility, see HPE StoreOnce overview, hpe.com/storage/storeonce, and HPE StoreOnce Compatibility Guide, hpe.com/info/ebs.

Industry-leading, scale-out architecture to meet enterprise requirements The scale-out architecture allows you to grow as your business needs dictate and not be limited by technology or vendor constraints. Choose capacity points available through virtual backup solutions or dedicated appliances that start small and allow you to add in virtual capacity, shelves, or nodes as needed.

http://www.hpe.com/storage

http://hpe.com/storage/storeonce

http://www.hpe.com/info/ebs


With a range of capacity points from 1 TB to 2240 TB, HPE StoreOnce Backup suits all requirements from small remote offices to enterprise data centers with centralized monitoring through HPE Reporting Central.

HPE StoreOnce deduplication Deduplication works by examining the data stream as it arrives at the storage appliance, checking for small blocks of data that are identical and removing redundant copies. If duplicate data is found, a pointer is established to the original set of data as opposed to actually storing the duplicate blocks, thus removing, or “deduplicating” the redundant data. The key here is that deduplication of redundant data is being done at the block level to remove far more redundant data than deduplication done at the file level where only duplicate files are removed. HPE StoreOnce uses data compression prior to storing data. What makes HPE StoreOnce deduplication technology unique is its variable length “chunking algorithm” – which accommodates minor changes in the backup stream layout and the fast “matching” algorithm using HPE Sparse Index technology developed by HPE Labs.

Data deduplication is especially powerful when it is applied to backup, since most backup data sets have a great deal of redundancy. The amount of redundancy will depend on the type of data being backed up, the backup methodology, and the length of time the data is retained.

HPE StoreOnce provides a Virtual Tape Library (VTL), network-attached storage (NAS), or HPE StoreOnce Catalyst target devices for data protection applications. Interfaces can be via a network connection or FC. Figure 5 shows the basic components of the HPE StoreOnce appliance. The actual storage medium is hard disk and these are arranged in a RAID 6 configuration with an enterprise-class HPE-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 HPE StoreOnce appliances are either 2 TB or 4 TB serial-attached SCSI (SAS) disk drives.

HPE StoreOnce deduplication is also used to move backups to other HPE StoreOnce appliances in a bandwidth-efficient manner. This efficiency 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. Commvault awareness of HPE StoreOnce replication lets customers access replicated data with no additional administrative tasks within the Commvault software, and Commvault will automatically use the best available HPE StoreOnce source during recovery operations.

FC Interface NIC

Virtual Tape/NAS/Catalyst Emulations

HPE StoreOnce Deduplication “Engine”

HPE File System

RAID Control and Disks

ManagementSystem OS

CPU/MEM

HPE StoreOnce Appliance

Figure 5. HPE StoreOnce Architecture overview


HPE StoreOnce 4700 HPE StoreOnce has been designed to cater to the needs of all types of customers from entry level to large-scale enterprises. HPE StoreOnce Backup systems deliver scale-out capacity and performance to keep pace with shrinking backup windows, reliable disaster recovery, simplified protection of remote offices, and rapid file restore to meet today’s SLAs. The models vary by capacity and connectivity protocol, and customers, like you, can start out by purchasing a single HPE StoreOnce base unit or couplet, and then expand with additional couplets as well as expansion shelves. We have used HPE StoreOnce 4700 in this reference architecture. These units deliver cost-effective, scalable disk-based backup with deduplication for long-term, onsite data retention for the CS700 single rack configuration. It also provides a replication target device for up to 50 remote or branch offices.

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.

Table 3. HPE StoreOnce configuration – options and features

HPE StoreOnce 4700 specification

Form factor 4U scalable rack

Total capacity (raw) Up to 192 TB4

Total capacity (usable) Up to 160 TB4

Data retention with deduplication (20:1) 3.2 PB4

Maximum number of source appliances per target appliance (fan in)

50

Write performance (aggregated VTL) 7.6 TB/hr4

Read performance (aggregated VTL) 9.0 TB/hr4

Catalyst performance 22 TB/hr4

Targets for backup applications HPE StoreOnce Catalyst, VTL, and NAS

Device interfaces 4x 8 Gb FC, 2x 10GbE, 4x 1GbE

Disk drives 2 TB, SAS 7200 rpm, 3.5-inch

Number of disk drives 12 (min), 12 x 8 (max), hardware RAID 6

Maximum number of HPE StoreOnce Catalyst, VTLs, and NAS backup targets (combined) on HPE StoreOnce 4700

50

Maximum number of cartridges emulated 204,800

Replication Supports data replication – Replication is automatic and appliances may function as both replication targets and sources simultaneously with licensing only being required for appliances acting as a target. Replication of data can occur between VTL and NAS devices created on HPE StoreOnce appliances and HPE StoreOnce VSA appliances.

To provide sizing assistance for which HPE StoreOnce model to choose, use the HPE Storage Sizer, hpe.com/storage/sizer.

Key parameters required for accurate sizing are data volumes, retention periods required, and an assessment of data change rates.

4 These values assume infinite performance hosts and measure “maximum ingest” rate. Deduplication ratios assume small data change rate and long retention period.

http://www.hpe.com/storage/sizer


Commvault Data Platform – key features and benefits The Commvault Data Platform is an enterprise level, integrated data and information management solution, built from the ground up on a single platform and unified code base. All functions share the same back-end technologies to deliver the unparalleled advantages and benefits of a truly holistic approach to protecting, managing, and accessing data. The software contains modules to protect and archive, analyze, replicate, and search data, all of which share a common set of back-end services and advanced capabilities, seamlessly interacting with one another. This addresses all aspects of data management in the enterprise, while providing infinite scalability and unprecedented control of data and information.

Key features of the Commvault Data Platform:

• Complete data protection solution supporting all major operating systems, applications, and databases on virtual and physical servers, NAS shares, cloud-based infrastructures, and mobile devices.

• Simplified management through a single console – view, manage, and access all functions, data and information across the enterprise.

• Multiple protection methods including backup and archive, snapshot management, replication, and content indexing for eDiscovery.

• Efficient storage management using deduplication for disk and tape.

• Integrated with the industry’s top storage arrays to automate the creation of indexed, application-aware hardware snapshot copies across multi-vendor storage environments.

• Complete virtual infrastructure management supporting both VMware and Microsoft Hyper-V.

• Advanced security capabilities to limit access to critical data, provide granular management capabilities, and provide single sign on access for Active Directory users.

• Policy based data management, transcending limitations of legacy backup products by managing data based on business needs and not physical location.

• Cutting edge end-user experience empowering them to protect, find and recover their own data using common tools such as web browsers, Microsoft Outlook and File Explorer.

Commvault CommCell Anatomy Figure 6 shows the overall logical architecture of a Commvault CommCell. Required components are a CommServe, which must be running Microsoft Windows Server®, at least one MediaAgent and one Client, which are both available for various Windows® and Linux platforms.


Figure 6. Commvault CommCell overview

The CommServe runs a Microsoft SQL database (included) and orchestrates all Clients and MediaAgents within the CommCell.

The Clients are servers that run the customer applications. A small software component called an iDataAgent communicates with the CommCell and streams backup data to the MediaAgent.

The MediaAgent is a server that connects to target devices. For this scenario, the target device is HPE StoreOnce. HPE StoreEver and HPE StoreAll can also be used as part of an offload or archive solution.

Backup definition Various components make up the Commvault data management operation, each of which controls a specific part of the process. These components are available to all jobs in any combination, allowing administrators to build on existing policies and processes.

Figure 7. Commvault backup definition

Schedule Policy contains the time, date, and frequency of a job, and the operation type. For example, run incremental backup every evening, and run a full backup over the weekend.


Storage Policy controls where data is stored, for how long, what paths it can take to and from the storage, and any optional transformations such as compression and encryption. These options are contained in Copies, with independent options for each destination. A Storage Policy contains one or more Copies. Defining multiple copies allows the Commvault administrator to define tiered data protection.

The Client and Subclient components define the source of the backup data. A Client is the host or platform on which the data resides, and a Subclient is a selection of data with common protection and retention properties. You may, for example, have one Subclient for business critical data requiring long retention and a separate one for more transient data.

Data pipeline The data flows from source to target using varying transport methods. It is read using the iDataAgent on the application server consuming local system resources for each configured reader. Network threads are then used to transfer this data to the MediaAgent. Finally, data is written to the HPE StoreOnce device, using a pre-defined number of writers. Further detail is available in the Commvault documentation at: http://documentation.commvault.com/commvault/v10/article?p=features/streams/streams.htm.

Further detail on sizing Commvault components is available at: http://documentation.commvault.com/commvault/v10/article?p=system_requirements/common/requirements_overview.htm.

Benefits of deploying HPE StoreOnce with Commvault software The sole purpose of backup is to ensure data can be recovered quickly when it is needed. But it is not just about data recovery. Business-critical applications need to be restored quickly as well. With HPE StoreOnce, data restores are almost as fast as backups, and Commvault software enables application-aware recoveries to further reduce downtime. For disaster protection of backup copies, the solution enables you to replicate backups to an HPE StoreOnce Backup at a secondary location using low bandwidth replication, saving precious network bandwidth and costs associated with it. Once replicated, Commvault software enables you to restore data from either local or remote backup copies on HPE StoreOnce.

The following are benefits of deploying HPE StoreOnce with Commvault software:

• It is easy to protect, manage, and access data.

• HPE StoreOnce Backup is optimized for Commvault backup streams, yielding considerable reduction in backup footprint.

• It improves functionality, performance, and TCO, while migrating data protection environments from disparate small systems to scalable HPE StoreOnce Backup systems.

• HPE StoreOnce Backup systems used with Commvault software can be scaled out by adding MediaAgents and NAS backup devices.

• HPE StoreOnce NAS shares are recommended for use with Commvault software.

Installation and configuration of Commvault software Commvault Backup and Recovery infrastructure components Table 4 describes the components of Commvault Data Platform components

Table 4. Commvault Data Platform components

Component Description

CommServe server It communicates with all Clients and MediaAgents and co-ordinates all operations such as backup, restore, copy, media management, and so on within a CommCell. We have used two CommServe servers, one at the primary site and another at the secondary site, and the CommServe database is replicated using the log shipping method.

CommCell It consists of CommServe server, MediaAgents, and Clients.

CommCell Console It is a GUI that allows you to control and manage the operation of CommCell.

MediaAgent It manages the transmission of data between Client and backup media.

Client It is any computer whose data must be backed up. The CommServe server and MediaAgents are also Clients.

http://documentation.commvault.com/commvault/v10/article?p=features/streams/streams.htm

http://documentation.commvault.com/commvault/v10/article?p=system_requirements/common/requirements_overview.htm


To protect and manage the data in your environment, the Commvault software must be installed across the computers that you want to protect, such as servers, desktops, and laptops. The group of protected computers is referred to as your CommCell environment, while each protected computer is referred to as a Client. A Client is a uniquely addressable (TCP/IP) device.

Commvault components in a CommCell environment The main operations in a CommCell environment are handled by the following components.

• CommServe

This component creates a SQL database that communicates with all Clients, including Clients at a secondary site. It coordinates all operations within the CommCell environment, such as backups, restores, copies, and media management operations. The CommServe component is installed on a Windows Server.

• CommCell Console

This console is a GUI that allows you to control and manage CommCell operations.

• File System

The File System component enables backup and restore of files and folders residing on the CommServe computer.

• Web Server and Web Console

If Internet Information Services (IIS) is enabled on the computer, the Web Server component is installed along with the Web Console component. The Web Console is a Web-based application that allows end users to manage their data.

• Workflow

Workflow is a tool that allows you to automate business processes by putting together a set of tasks in a specific order.

• MediaAgent

This component manages the transmission of data between Clients and backup media. The MediaAgent component is installed on a Windows or UNIX® computer that is configured with the backup media. The backup media is a storage device where backup data is stored.

• iDataAgent

Commvault software provides a range of installable components that support the type of data that you want to protect. These components are referred to as iDataAgents, or just agents. Agents allow you to protect file systems, applications, and databases on a Client computer. For example, to back up and restore data from an Oracle Database, you need to install the Oracle Database component.

Installation methods You can use one of the following methods to install Commvault components:

• Remote installation

• Interactive installation

For additional information on installation methods, visit, http://documentation.commvault.com/commvault/v10/article?p=deployment/common_install/install_overview.htm

http://documentation.commvault.com/commvault/v10/article?p=deployment/common_install/install_overview.htm


Configuring Commvault software with HPE StoreOnce Commvault compression and deduplication HPE StoreOnce contains enhancements that improve HPE StoreOnce deduplication and throughput when used in conjunction with Commvault software. To take advantage of the enhancements, HPE StoreOnce should be configured using NAS shares. For a better deduplication ratio, disable software compression in Commvault software. Figure 8 describes how to disable the software compression.

Note Backup performance may be positively or negatively impacted depending on the application and data. Commvault deduplication is not enabled by default and should not be used for data written to HPE StoreOnce. Compression can be disabled on a per-subclient or per-storage policy basis.

Figure 8. Commvault compression option (storage policy)

Disk library configuration HPE StoreOnce NAS shares are configured in Commvault software as shared disk devices, so Commvault recognizes and relates all the available paths to each share. On a Linux MediaAgent, the HPE StoreOnce NFS export must be mounted to the file system. The mount path is then configured in the shared disk device using the Library and Drive Configuration Tool from the CommCell GUI.

Figure 9 shows how to add a shared folder under Library and Drive Configuration Tool


Figure 9. Adding a shared folder under Library and Drive Configuration Tool

On a Windows MediaAgent, the HPE StoreOnce Common Internet File System (CIFS) share is added directly, along with credentials that can access the share.

Figure 10. HPE StoreOnce CIFS share


The shared disk devices are added to disk libraries that can be associated to storage policies.

Figure 11. HPE StoreOnce libraries tab

Configuring Commvault software with HPE 3PAR StoreServ 7400c Storage HPE 3PAR StoreServ 7400c Storage integrates with Commvault IntelliSnap to enable robust, simple snapshot management, providing short RPO and rapid RTO. In an HPE ConvergedSystem virtualized environment, IntelliSnap can be used with the Commvault Virtual Server Agent (VSA) for generalized workloads. On HPE ConvergedSystem 700, with agent-based data management within virtual machines, IntelliSnap can offload backup processing for ultra-critical applications that cannot tolerate the additional overhead of backup to a proxy server.

For streaming protection only, no additional configuration is required in Commvault software.

To enable IntelliSnap integration, Commvault software needs to be made aware of the HPE 3PAR StoreServ array. This is performed in the Commvault Array Management interface.

Figure 12. Configuring Commvault software with HPE 3PAR StoreServ

For detailed information on configuring Commvault IntelliSnap with HPE 3PAR StoreServ Storage, refer to the Commvault documentation, http://documentation.commvault.com/commvault/v10/article?p=features/snap_backup/3par/overview.htm.

For detailed information on configuring HPE 3PAR StoreServ Storage, refer to the HPE documentation, hpe.com/storage/3par

http://documentation.commvault.com/commvault/v10/article?p=features/snap_backup/3par/overview.htm

http://www.hpe.com/storage/3par


For detailed information on configuring Oracle Real Application Clusters (RAC) 12c, refer to the Commvault documentation, http://documentation.commvault.com/commvault/v10/article?p=system_requirements/oracle_rac.htm.

Commvault Oracle RAC 12c integration The Oracle RAC iDataAgent provides a simplified end-to-end backup and recovery solution for Oracle Databases in your enterprise without using multiple subclients and storage policies. It also allows you to distribute Oracle backups and restores across multiple database nodes to improve throughput. The product can be used to perform both full system rebuilds and granular recovery of data and logs. Commvault integration with Oracle RAC 12c offers a full range of backup and recovery options. The Oracle RAC iDataAgent provides a single management point for backups and recoveries across all the nodes in a RAC cluster. The RAC client provides the flexibility to back up and recover the Oracle Database across one or more of the nodes, while providing control of the number of Oracle streams allocated to each node. You can perform a full or incremental backup of the entire database or individual datafiles/tablespaces, and archive logs at any point in time.

In configurations where there is no Oracle Recovery Manager (RMAN) catalog, the Oracle control file can be used as an alternative.

Figure 13 shows the Commvault Oracle integration architecture, which contains MediaAgent, Storage device, CommServe and Oracle nodes/Dataagents.

Figure 13. Commvault and Oracle RAC Architecture overview

The following sections describe the backups that can be performed in different environments.

Offline backup When the database is shut down and not available for use, perform a full backup of the database without logs. Use offline backup when data is consistent and there are no transactions in the database.

Online backup When you cannot bring down the database to perform an offline backup, use the online backup method. Perform full or incremental backups when the database is online and in ARCHIVELOG mode. Use online backups when you want to perform a point-in-time restore of the database.

You can also backup the archive logs only when the database is online. These logs can be applied to an online backup to recover the database to the current point in time. Archive log management is also configurable during backup. Archive logs can be retained on disk or deleted after backup, as desired, freeing up disk space in the archive log area.

You can also protect the non-database files and profiles using the appropriate File System iDataAgent.

http://documentation.commvault.com/commvault/v10/article?p=system_requirements/oracle_rac.htm


Selective online full backup You can backup and store copies of valid data from a source copy of a specific storage policy to all or one active secondary copy within a storage policy to provide a better tape rotation. An online full backup job is copied to a selective copy if the full backup job cycle completes successfully. This allows you to select, store, and protect data on a secondary copy for future restores.

Backup and recovery considerations when virtualizing Oracle RAC 12c In a virtualized environment, Oracle can be protected using the Commvault or the Oracle iDataAgent. For the maximum backup and recovery flexibility, install the Oracle iDataAgent on the virtual machines and leverage Commvault integration with Oracle protection and recovery.

Configuring Commvault software with Oracle RAC 12c Oracle iDataAgent can be installed manually from each Oracle node, or it can be installed remotely from the CommCell GUI. When installing it from the CommCell GUI, HPE recommends following these steps:

1. From the Add/Remove Software in the CommCell GUI, deploy to all nodes in parallel by entering all of the hostnames as targets.

Figure 14. Deploying iDataAgent


2. Install the MediaAgent and Oracle agents to allow the nodes to write directly to HPE StoreOnce.

Figure 15. Deploying MediaAgent

3. Select the option to Reboot (if required), and restart Oracle services.

Figure 16. Additional installer options


4. Specify a Unix Group to limit the permissions on the Commvault installation paths. Database administrators (DBAs) who need permission to run Commvault software commands must belong to this group.

Figure 17. Unix Advanced installer options

For additional information on installing the Commvault Oracle RAC iDataAgent, visit, http://documentation.commvault.com/commvault/v10/article?p=products/oracle_rac/deployment_unix.htm.

Note Follow the same procedure when installing Oracle iDataAgent on Oracle Database single instance nodes.

http://documentation.commvault.com/commvault/v10/article?p=products/oracle_rac/deployment_unix.htm


Configuring Oracle iDataAgent on RAC nodes Database instances participating in the RAC cluster must be discovered on the individual nodes. If Oracle Automated Storage Management (ASM) is in use, it must also be discovered. The instance SIDs on each node must be unique across the cluster.

When configuring an instance manually, provide ORACLE_SID, ORACLE_USER, and ORACLE_HOME details. Optionally, you can enter the RMAN catalog connect string details and RMAN parameters:

Figure 18. Creating the new Oracle instance

If the environment uses ASM, the ASM instance on each node must be manually configured under the client for that node, not in the RAC client.

Note Follow the same procedure when creating Oracle single instance database.

For more details on configuring Oracle instances, refer to: http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_config_oracle_instances.htm.

Creating a RAC client Once the Oracle iDataAgent is installed on all the RAC database nodes, create a new Oracle RAC pseudo-client. A RAC pseudo-client is a logical grouping of Oracle instances within a RAC instance.

http://documentation.commvault.com/commvault/v10/article?p=products/oracle/c_ora_config_oracle_instances.htm


On the CommCell Console, right-click Client Computers, navigate to New Client, Application, and then click RAC.

Figure 19. Creating RAC clients

Every node instance is added to the RAC client, along with credentials and ORACLE_HOME details, to give Commvault software the knowledge of the RAC topology.

Figure 20. Listing the existing Oracle RAC clients


For complete installation, instructions, and advanced options, for Oracle RAC, refer to, http://documentation.commvault.com/commvault/v10/article?p=products/oracle_rac/config_basic.htm.

Test bed architecture overview The test bed infrastructure consists of HPE ConvergedSystem 700 and HPE StoreOnce 4700 connected via a 10GbE network.

Eight VMs are created for Oracle RAC. Another two VMs are created, one for Oracle Single Instance database and one for Oracle Catalog database. Each Oracle VM has the capacity of 16 virtual CPUs (vCPUs) and 96 GB of memory. An additional VM with 16 vCPUs and 32 GB capacity is created for the CommServe database server. The storage space for all the VMs has been allocated using HPE 3PAR StoreServ 7400c Storage by creating the datastore.

Figure 21. HPE CS700, Oracle RAC, and Commvault Disaster Recovery Test Bed architecture overview

http://documentation.commvault.com/commvault/v10/article?p=products/oracle_rac/config_basic.htm


Commvault software architecture overview with HPE StoreOnce Each RAC node has Commvault Oracle iDataAgent and MediaAgent software installed. This enables the nodes to send data directly to HPE StoreOnce to increase throughput and distribute resource utilization across the ESXi hosts.

An HPE StoreOnce share is provisioned for each RAC instance, and all nodes for that instance write and read from the same share. This configuration enhances deduplication while allowing high, parallel stream counts for high throughput.

Figure 22. Commvault architecture overview with HPE StoreOnce

Solution components This solution includes the following key components:

HPE ConvergedSystem 700 tested configuration Table 5. HPE CS700 hardware for the test bed

Component Description

One HPE BladeSystem c7000 Enclosure Enclosure to host blades and Virtual Connect modules

Two HPE Virtual Connect FlexFabric 10Gb/24-Port Modules Virtual Connect module for Ethernet and SAN connectivity

Eight HPE ProLiant BL460c Gen9 Server Blades Server blades to host one Oracle RAC 12c 4-node cluster, two single Instance Oracle Database, Commvault Oracle Database agent, HammerDB application running as VMs and two VMs for Live Sync testing

One HPE 3PAR StoreServ 7400c Storage Storage for Oracle Database and data stores for VM

Two HPE 5900AF-48XG-4QSFP+ Network Switches

Two HPE 5900AF-48G-4XG-2QSFP+ Network Switches

Network switches for LAN traffic.

Network switches for management traffic

Two HPE StoreFabric SN6000B 24-port SAN Switches Fibre Channel switches for SAN connectivity between servers and HPE 3PAR StoreServ Storage.

HPE StoreOnce 4700 Target for Oracle Database backup

Software configuration • Oracle RAC 12c configured on virtual machines running Red Hat® Enterprise Linux 6.5

• Oracle Automated Storage Management (ASM)

• Oracle Recovery Manager (RMAN)


• Commvault software version 10 with Service Pack 12 configured on Windows Server 2012 R2

• HammerDB 2.16 configured on a virtual machine running Red Hat Enterprise Linux 6.5

• HPE 3PAR OS version must be 3.2.1

• HPE StoreOnce 4700 release 3.12.0

Storage configuration The HPE 3PAR StoreServ 7400c Storage hosted the two Oracle Databases of 500 GB each.

To accomplish this layout, the HPE 3PAR StoreServ primary storage array is used to allocate and present storage pools as described in Table 6.

Table 6. Storage configuration for the test bed

Contents Size Provisioning Disk type Notes

Oracle Data Files 500 GB Thick 15k SAS RAID 5

Oracle Temp Files 500 GB Thick 15k SAS RAID 5

Oracle Redo logs 500 GB Thick 15k SAS RAID 5

Oracle Control Files 500 GB Thick 15k SAS RAID 5

Virtual Machine OS, Binaries specifications

150 GB Thin 15k SAS RHEL 6.5, Oracle 12c (16 core and 96 GB memory)

CommServe server, Commvault specifications

200 GB Thin 15k SAS Windows Server 2012 R2,

Commvault software version 10 (16 core and 32 GB memory)

HammerDB 50 GB Thin 15k SAS RHEL 6.5,

HammerDB 2.16

Once allocated, the storage objects are presented to the VMware vSphere environment. The storage is allocated and provisioned using a thick format to enhance I/O performance during the workload-testing phase of this solution.

HPE StoreOnce 4700 configuration The HPE StoreOnce 4700 for this evaluation was configured with two disk shelves. Each disk shelf has fourteen 2 TB disk drives. The maximum throughput of a fully configured HPE StoreOnce 4700 without Catalyst is 7.6 TB/hr. The unit we tested had lesser throughput due to the limited number of disk drives. Performance is affected by parallel stream count; more streams gives higher performance. The HPE StoreOnce unit included the following:

• 2x 10GbE bonded – Catalyst backup target

• 4x 1GbE – Management

• 2x 8 Gb FC – Unused

• HPE StoreOnce software version 3.12 featuring “reporting central” and “phone home” capabilities

HPE StoreOnce tuning guidelines • Make use of the HPE StoreOnce Sizing tool to size your HPE StoreOnce solution. It is available at, hpe.com/storage/sizer.

• Always ensure that the appliance software in your HPE StoreOnce Backup system is fully up-to-date. Software upgrades also contain all the necessary component firmware upgrades.

• Where possible, group backups of like data types to the same destination device (Share/VTL/Store) – this can help optimize deduplication ratios.

http://www.hpe.com/storage/sizer


• Use separate HPE StoreOnce shares and Commvault storage policies for different data types, e.g., separate file system and database backups from each other.

• Run multiple backups in parallel to improve aggregate throughput for an HPE StoreOnce appliance. Table 7 shows the maximum number of simultaneous streams per configured device.

• 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.

HPE StoreOnce – maximum supported streams and devices5 Table 7. Maximum supported streams and devices

HPE StoreOnce Devices Streams Non-catalyst maximum

throughput

VSA 4 16 300 GB/hr

2700 8 48 1.3 TB/hr

4500 32 128 5.4 TB/hr

4700 50 192 7.6 TB/hr

4900 50 320 8.5 TB/hr

6500 50 320/node 63.2 TB/hr

Networking The recommendation is to configure the HPE StoreOnce with bonded 10GbE connections where possible to allow increased throughput. Multiple Clients and MediaAgents can write to the HPE StoreOnce simultaneously reducing the total backup window required.

• Adhere to the suggested maximum number of concurrent operations per share/appliance, as shown in Table 7. Be aware that there is a limit of 48 concurrent writes to NAS shares on HPE StoreOnce; if more streams are required, use multiple shares.

• For NFS shares, use the correct mount options to help ensure in-order delivery and improve deduplication ratios. See the “HPE StoreOnce Backup System Linux and UNIX Configuration Guide” for specific details at: hpe.com/info/storeonce/docs

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 Oracle Databases in the primary site. Transactions were run against the databases during backup to simulate a customer production environment. The load on the system was qualified as medium and consumed 45 percent of the CPU. The daily data change rate was estimated between 1.8 percent and 2 percent. Once the disaster recovery procedure was completed at the secondary site, HammerDB was used again to verify the database consistency by running the transactions against the database. Figure 23 shows the TPCC schema built for Oracle Database using HammerDB. After the schema has built, Figure 24 shows the transactions running on the schema.

5 These figures are correct at the time of initial publication, but are subject to change with differing software versions.

http://www.hpe.com/info/storeonce/docs


Figure 23. Database data load using HammerDB

Figure 24. HammerDB transaction running against the Oracle Database


Commvault tuning guidelines Number of clients A larger number of clients allows for a greater aggregate throughput to HPE StoreOnce, shrinking the backup window required. See Table 7 for supported streams and total throughput on each HPE StoreOnce platform; this should be considered during the sizing exercise.

MediaAgent sizing The MediaAgent is involved in all data operations between the clients and HPE StoreOnce. It needs to be capable of supporting sufficient concurrent operations. Use the Commvault system requirements table to help ensure you meet the requirements for the MediaAgent, including scope for future growth. It is available at: http://documentation.commvault.com/commvault/v10/article?p=system_requirements/ma.htm

Backup types Commvault software can run various backup types to protect data: Full, Incremental, and Synthetic Full. When using HPE StoreOnce, Synthetic Full backups are discouraged; there is a serious impact on the deduplication ratio and performance. Regular Full backups can deduplicate very efficiently and allow immediate restores. However, they place a significant load on the client as it streams the entire dataset for each backup.

A Schedule policy containing regular incremental backups and less frequent full backups can often result in excellent balance of performance, HPE StoreOnce disk use, and client load. The downside to such a policy is that restoring may require the restore of a full backup and subsequently several incremental restores in sequence, depending on the application.

IntelliSnap IntelliSnap is a Commvault feature that allows the management of snapshots on primary storage arrays, such as HPE 3PAR StoreServ Storage. These snapshots can be mounted directly to the MediaAgent and backed up while the production server continues to service clients. Additionally, restores can be done almost instantaneously by reverting the snapshot as long as the array is fully functional; this is ideal for recovering from data corruption or user error scenarios. For more information on IntelliSnap requirements, visit: http://documentation.commvault.com/commvault/v10/article?p=features/snap_backup/support_snapbackup.htm.

Backup configuration For the test configuration, a cycle of full and incremental backups was scheduled to run 3 times daily. Each cycle represents a day of transactions and growth in the Oracle Database. Full backups were scheduled to run every eight hours. Hourly incremental backups were scheduled to run in between the full backups. Streaming log backups were configured to run automatically with the snapshot backups.

Figure 25. Backup scheduler

http://documentation.commvault.com/commvault/v10/article?p=system_requirements/ma.htm

http://documentation.commvault.com/commvault/v10/article?p=features/snap_backup/support_snapbackup.htm


Backup from snapshot For ultra-critical workloads that cannot take the additional load from backups, hardware snapshots can be created, and then streaming backups can be taken from the snapshot using a physical proxy server. During testing, snapshot creation completed in 3 minutes or less, regardless of backup type. This represents the complete execution time and includes processes to place Oracle in hot backup mode and release it, as well as storing Commvault’s index information.

The streaming backup of the snapshot to HPE StoreOnce via the proxy system averaged between 1,100 GB and 1,200 GB per hour with 24 streams. Peak speed was observed at upwards of 1,400 GB per hour. Maximizing throughput with HPE StoreOnce depends on high bandwidth and high parallelism. For off-host IntelliSnap backup copy, 24 streams provided excellent balance of throughput and proxy system utilization.

Oracle Database backup procedure Once the Commvault and Oracle configurations have been completed as explained in previous sections, we can use the procedure below to backup the Oracle Database.

Go to the CommCell Console and double-click on bender RAC. In the right side window right-click on RAC and select Backup as shown in Figure 26.

Figure 26. Shows Oracle RAC Subclient backup option for Bender Instance


On the new window, select the backup type as Full and job initiation as Immediate and click OK as shown in Figure 27.

Figure 27. Shows Oracle RAC Subclient backup window

The backup will be initiated and you can monitor it in the Job Controller tab in the CommCell Console as shown in the Figure 28.

Figure 28. Backup status from Job Controller tab


Backup use cases Three Oracle backup use cases were investigated. An online streaming full backup was taken utilizing a single node of the RAC with 24 RMAN channels allocated for the backup. The average throughput for this case was 1.3 TB/hour; spreading the workload over all four nodes of the RAC, increased the average throughput to 1.4 TB/hr, while also spreading the CPU demands of the backup across all four RAC nodes. Finally, two parallel database backups were run to the HPE StoreOnce, with 12 RMAN channels allocated for each database. The average throughput for each database was 1.3 TB/hr. Table 8 shows the performance results for the streaming backup.

Please note that the HPE StoreOnce configuration used for the testing was only capable of 1.5 TB/hr due to the limited number of disk drives. The number of streams may vary based on your configuration. In our testing, we evaluated different number of streams and 24 was the optimum value for both backup and restore.

Table 8. Database backup results

Use case Streams Average throughput Size of data Total job time

Single node backup 24 1.3 TB/hr 7.3 TB 5.5 hr

Multi-node backup 24 1.4 TB/hr 8.1 TB 6 hr

Multi-node parallel backup (2 databases)

24 (12 per database)

1.3 TB/hr 14.6 TB 11.25 hr

Backup best practices for virtualized Oracle RAC 12c • An application agent for Oracle Database provides an excellent level of protection and recovery. Commvault software provides RAC awareness

to simplify protection and recovery processes.

• To leverage hardware snapshots in a virtual Oracle environment, you must present database logical unit numbers (LUNs) directly to the Oracle guests. Environments using FC connectivity must use physical mode RDMs. Environments with iSCSI may present LUNs directly to the virtual guests using the initiator within the guest.

• When using snapshots, several factors affect the retention strategy. RPOs and RTOs must be balanced against the cost of maintaining snapshots. For many databases, the value of the recovery copies diminishes rapidly with time. Superior strategy retains enough frequent snapshot copies to meet recovery time and recovery point objectives, with less frequent streaming copies for disaster recovery, testing and reporting refresh, and other uses.

• For environments not leveraging snapshots, dedicate a virtual RAC node to backups to reduce the impact on the other nodes in the cluster.

• For outstanding performance, streaming backups to HPE StoreOnce should use as many streams as the Oracle instance can support. This applies to both direct streaming and IntelliSnap backup copy operations.

• Streaming log backups should be performed on a regular schedule, at a frequency based on RPOs and RTOs.

• Virtual machines performing data movement, whether RAC nodes or IntelliSnap proxies, should have dedicated CPU and memory resources allocated. Backup traffic should be segregated where possible using separate VLANs and adapters.

For additional configuration options with VMware, visit http://documentation.commvault.com/commvault/v10/article?p=landing_pages/c_virtualization.htm.

Oracle Database recovery procedure In the case of disaster and if CommServe is also not available then it needs to be rebuilt. To rebuild the CommServe, refer to the CommCell documentation. After rebuild is complete, application recoveries can be started.

Commvault software provides the ability to recover Oracle Databases to a specific point in time using the archived redo logs. Recovery can be to the source Oracle Database or a separate instance or server, which is ideal for disaster recovery scenarios. In addition, databases can be recovered to a mounted state to allow replay of further archived redo logs, allowing scheduled recovery to maintain database synchronization and shorten disaster recovery times.

All recoveries are initiated through the same browse and recover interface. Simply select the time range to search, and then select the database content to restore. The recovery options selected will determine what database and archive log backups will be used for restore and recovery.

http://documentation.commvault.com/commvault/v10/article?p=landing_pages/c_virtualization.htm


Once the instance is started, go to the CommCell Console and click the instance. Right-click on rac and select Browse and Restore.

Figure 29. Browse and Restore option for bender Instance.

Select Latest Backup and click the View Content button.

Figure 30. Time Range for the instance


Select all the tablespaces by clicking on bender as shown in Figure 31. After selecting the tablespaces, click Recover All Selected.

Figure 31. Restore options through the Commvault Console


Figure 32. Oracle RAC Restore options for Bender – General Tab


Click the Advanced button in the Figure 32 to select from different recovery options, such as recover to Current Time, a specific Point In Time, or a System Change Number (SCN) as shown from the selection dialog box in Figure 33.

Figure 33. Commvault software Advanced Restore/Recover options

Ensure that the appropriate number of streams to be used for the restore procedure, then click OK to start the recovery procedure.

You can monitor it in the Job Controller tab in the CommCell Console as shown in Figure 34.

Figure 34. Job Controller tab in the CommCell Console

After the database is restored successfully, register the database and add the instance names.


Restore from HPE StoreOnce Backup Commvault integration with HPE StoreOnce provides streaming recovery from deduplicated storage. Performance scales with the number of streams used. Applications such as an Oracle Database that can perform multi-streamed restores see the biggest benefit from the appliance.

Commvault software uses a local recovery path, if available. Setting up access from the Oracle RAC nodes directly to HPE StoreOnce NAS shares yields outstanding performance during restore operations. This requires Commvault MediaAgents to be installed on the RAC nodes.

Recovery use cases In each database restore scenario, archive logs were applied to bring the database back to the current time. The first scenario was to restore from a full backup with archive logs applied to bring the database to current time. The average throughput was 1.5 TB/hr.

In the second scenario, a full backup was restored, followed by four sets of incremental backups, and again followed by archive logs to roll the database forward to the current time once again. The aggregate throughput in this case dropped to an average of 1.1 TB/hr.

Finally, two databases were restored and recovered in parallel from the HPE StoreOnce. Both databases restore full backups, followed by incremental and archive logs. The average throughput for both databases was 1.1 TB/hr. Table 9 shows the performance results for database restore and recovery.

Table 9. Database restore and recovery results

Use case Streams Average throughput Size of data Total job time

Entire database restore from Full

24 11.5 TB/hr 8.08 TB 5.5 hr

Entire DB recovery from Full + 4 Incremental + logs

24 1.1 TB/hr 8.4 TB 7.75 hr

Parallel DB recovery from Full + 4 Incremental + logs

24 (12 per database)

1.1 TB/hr 15.2 TB 13.8 hr

Recovery best practices for virtualized Oracle RAC 12c For outstanding performance, recovery should be configured to use streams on all RAC nodes. In our testing, 24 was the optimum number of streams. This may vary based on your configuration.

Commvault and VMware integration VM platforms make disaster recovery appear simpler, but the end goal remains elusive, and rising costs and complexity seem unavoidable. Commvault’s solutions for VM platforms help you streamline disaster recovery and DR test procedures without breaking your budget. With a single software solution, you can bring disaster recovery capabilities to workloads with an unprecedented level of protection.

The Commvault Virtual Server Agent for VMware provides a unified protection and recovery vehicle for all virtual machine data in your vCenter. In addition to complete protection of entire virtual machines for disaster recovery, the Virtual Server Agent provides more granular backup and recovery options. Options such as customized automatic discovery, deduplication, and reporting help ensure all your virtual machine data is easily traceable and retrievable whenever the need arises. This paper discusses backup and recovery for virtual machines.

For information on granular backup and recovery options, refer to: http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=4AA5-5137ENW, and http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/overview.htm.

http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=4AA5-5137ENW

http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=4AA5-5137ENW

http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/overview.htm


Figure 35. Commvault Virtual Server Agent for VMware architecture overview

Key features Single administration point The virtualization client serves as a single point of administration for all proxies. The proxy computer can be any computer where the Commvault Virtual Server Agent is installed. All administration activities such as backups, restores, schedules, and reports can be performed from the virtualization client.

The virtualization client also enables proxy teaming. The proxy teaming ensures the fault tolerant backup. It can be useful when you want to perform the backup for a large number of virtual machines in a limited backup window.

Automatic protection for all virtual machines in a vCenter Once you configure the Virtual Server Agent for a vCenter, all the virtual machines in the vCenter are automatically selected for backup. This behavior is designed to ensure that all virtual machines are backed up.

Customized discovery If you want to backup only specific virtual machines in a vCenter, you can set criteria to search the virtual machines and automatically select them for backup. This is useful in environments where virtual machines are frequently added or removed. You can easily browse and select vCenter objects such as hosts, datastores, resource pool, etc. to set criteria for automatic discovery.

Customized filters You can exclude specific virtual machines or disks on the virtual machines from the backup. You can add filters for the virtual machines or disks.

Detailed reporting for each virtual machine backup You can view a detailed report about each backed up virtual machine. It contains information such as name of the proxy, which performed the backup of the virtual machine, size of the backup data, type of backup, etc. You can view all this information from the CommCell Console when the backup job is running. It appears on the Client status tab of the view job details dialog box.

vCloud backup and restore You can protect the vCloud-specific attributes of a virtual machine and restore it back to a vCloud.


Point-in-time snapshots of virtual machines IntelliSnap backup enables you to create a point-in-time snapshot of a virtual machine by temporarily quiescing the data, taking a snapshot, and resuming live operations. IntelliSnap backups work in conjunction with hardware snapshot engines.

Changed block tracking Changed block tracking (CBT) is a VMware feature that can be used to help optimize backups of virtual machines by reading only the allocated and modified portions of a virtual disk. CBT is automatically enabled for virtual machines running on hardware version 7 or later.

Virtual Machine Lifecycle Management Commvault software enables policy-based management of virtual machine lifecycle, from creation, through power-down and archive, to deletion. Administrators set policies around allowed VM configurations and lifespans, recovery, and access. End users can provision VMs, and view and recover VM content through a self-service web interface.

Backup best practices for VMware-generalized workloads Commvault software provides a default subclient that automatically discovers new VM guests and adds them to protection operations. Scheduling backup jobs with this subclient ensures all VMs are protected.

Changed block tracking significantly improves performance of incremental backups.

Subclients should generally align to ESXi clusters. Commvault software will attempt to load balance backups across datastores within the subclient.

Guest applications that do not support Volume Shadow Copy Service (VSS) should have freeze or thaw scripts configured to ensure application consistency at the time of backup.

Configure separate virtual clients for vCenter and vCloud Director to ensure vCloud metadata is collected properly.

IntelliSnap should only be used for large- or high-I/O VMs. Generally, streaming backups are faster overall for smaller, less busy VMs. VMs protected with IntelliSnap should be placed in separate datastores from streaming VMs. IntelliSnap subclients should align to datastores to avoid creating excessive hardware snapshots.

For more detail on Commvault best practices with VMware, visit, http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/best_practices.htm

VMware tuning guidelines • Ensure sufficient resources are allocated to the CommServe, Virtual Server Agent, and MediaAgents. Resource contention will result in

performance degradation.

• Segregate HPE StoreOnce traffic from other networks to help ensure throughput is not affected by traffic fluctuations.

• Test the impact of compression on the backup, Virtual Server Agent CPU load. But depending on the data, the increase may be more than offset by a reduction in backup time. In the test environment, compression added 30% CPU load but negligible difference in backup performance.6

Configuring Commvault software with VMware Installing the Virtual Server Agent The Commvault Virtual Server Agent must be installed on a Windows Server 2008 R2 or later system. The Virtual Server Agent system can be physical or virtual. For more efficient performance on a physical system, it must have direct access to the storage hosting the virtual machine datastores. The Virtual Server Agent can be installed manually on the target system, or it can be pushed remotely using the CommCell GUI.

For details on installing the Virtual Server Agent, visit, http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/deployment.htm

6 HPE and Commvault Internal test, 2014

http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/best_practices.htm

http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/deployment.htm


Configuring virtualization client A virtualization client allows Commvault software to interface with VMware vCenter and vCloud Director to identify and manage vSphere host and datastore resources. Configuring a virtualization client simply requires the name or address of the vCenter or vCloud Director Instance and credentials with appropriate access privileges.

As mentioned previously, the default subclient by default will detect and protect all virtual machines managed by vCenter or vCloud Director. Additional subclients can be created to meet different protection needs for targeted sets of VMs, such as longer retention or IntelliSnap. Content for subclients can be explicit or rule-based and targeted at hosts, clusters, VMs, and datastores.

Figure 36. Commvault software Virtual Server Agent explicit content selection

Figure 37. Commvault software Virtual Server Agent rule-based content selection

For more detail on configuring VMware protection with the Virtual Server Agent, visit, http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/config_basic.htm

http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/config_basic.htm


Backup configuration For the test configuration, five virtual machines running Windows Server 2012 were configured as the content for a Commvault software Server Agent subclient. A sequence of backups and data changes was run to simulate daily file changes and protection operations. The sequence consisted of six incremental backups and one full backup, with a roughly 1% change rate between jobs.

Backup use cases Five backup use cases were investigated with VMware. Full VM backups were performed with and without metadata collection enabled. Incremental VM backups were performed with metadata collection enabled. In addition, IntelliSnap full and incremental backups of the VMs were performed, with out-of-band streaming backup copy and metadata collection enabled. The table below shows the performance results for VMware backup. Incremental results are averaged across five jobs.

Table 10. Commvault software Virtual Server Agent backup results

Use case Average throughput Size of data Total job time

Full with metadata 290 GB/hr 39.37 GB 9.75 min

Incremental with metadata 11.2 GB/hr (average) 888 MB (average) 5.5 min (average)

Parallel DB recovery from Full + 4 Incremental + logs

1.1 TB/hr 15.2 TB 13.8 hr

Full without metadata 283 GB/hr 40.37 GB 9.5 min

IntelliSnap full 295 GB/hr (backup copy) 40.27 GB 2.1 min (snapshot)

11.1 min (backup copy)

IntelliSnap incremental 13.6 GB/hr (average) 906.47 MB (average) 2.4 min (snapshot average)

6.5 min (backup copy average)

Notes on performance • Job time is not limited to data transfer duration.

• Throughput incorporates metadata collection in addition to data transfer.

HPE StoreOnce performance scales with stream count and disk shelves. More parallel jobs from additional Commvault software Virtual Server Agents can result in higher throughput.

Recovery Commvault software provides a number of recovery options for VMware. Full VMs can be restored either in place or out of place. Virtual machine files, such as configuration and Virtual Machine Disk (VMDK) files, can be restored to the Commvault software Virtual Server Agent system. VMDK files can be restored to a datastore and attached to an existing VM to allow manual browsing. And granular files from within the VMDKs can be recovered to any Commvault client or even to a VM without a Commvault agent installed.

Figure 38. Commvault software Virtual Server Agent restore options


Recovery use cases Three recovery use cases were investigated. Out-of-place full VM recovery simulates a disaster recovery operation. Granular guest file recovery illustrates restoration of individual files from within a VM guest, with no agent required in the guest. Live Browse and Recovery from Snapshot showcases the ability of the Commvault software to recover VM content, including individual files, without indexing the VM content beforehand.

Out-of-place full VM recovery The virtual machine was recovered to a different VM name on a different datastore. Commvault software includes a wide variety of options to customize the restore, including changing hosts, datastores, powering on the VMs, and changing disk provisioning, among others. Select the first option from Figure 39.

Figure 39. Commvault software Virtual Server Agent VM restoration in a different ESXi host


Granular, agentless guest file recovery to VM Browsing from the Commvault software Virtual Server Agent allows drilling down into the file system of the protected VMs. Individual files and folders can be selected. Select the files, which you want to restore, as shown in Figure 40.

Figure 40. Commvault software Virtual Server Agent content for granular restoration

Content can be recovered to any file system agent or to a virtual machine.

Figure 41. Commvault software Virtual Server Agent granular restoration to virtual machine


After recovery, the files are available in the target location.

Figure 42. Files available after restoration

Live browse and granular restore from snapshot Browsing for granular file content from an unindexed snapshot starts a live browse, which is a real-time indexing operation. This is most efficient when using a hardware snapshot as a recovery source. The process starts automatically when a snapshot is the most appropriate recovery source.

Figure 43. Commvault software Virtual Server Agent browse request

The live browse returns identical content to an indexed browse. Restore options are identical to an indexed browse.

During the live browse, the hardware snapshot is mounted to an ESX proxy host as a datastore to present the VMs for indexing.

Figure 44. Commvault software Virtual Agent snapshots listing

For detailed information on VM recovery options, visit, http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/restore_adv.htm.

http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/restore_adv.htm


Table 11. Commvault software Virtual Server Agent backup results

Use case Average throughput Size of data Total job time

Out-of-place full VM recovery 224 GB/hr 16.01 GB 4.25 min

Granular, agentless guest file recovery to VM

1.11 GB/hr 16 MB 0.9 min

Live browse and granular restore from snapshot

0.41 GB/hr 10 MB 1.5 min

Commvault licensing The environment described in this document used Commvault’s capacity licensing model. Under this model, license usage is measured based on front-end data, or the size of the data being protected, during full backup. Capacity is purchased in terabyte increments. The number of copies being stored does not affect license measurement.

For Commvault’s Virtual Server Agents, alternative license models are available that can be mixed with the capacity. Under the alternative models, licenses are based on the number of CPU sockets or the number of VMs being protected.

Summary Organizations invest in converged technology stacks to reap the benefits of a single pre-tested and validated solution platform that can help reduce risk, increase operational efficiencies, and deploy workloads upon a predictable infrastructure set. With a converged approach, 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. The HPE solution built upon the HPE ConvergedSystem 700, HPE StoreOnce, and Commvault software removes the burdens of a build-it-yourself model. In conclusion, the key takeaways from this joint HPE and Commvault project could be defined as follows:

• HPE ConvergedSystem 700 is an optimized infrastructure platform for protecting virtualized mission-critical applications against disasters.

• Commvault software combined with HPE StoreOnce deduplication capability provides good RPOs and RTOs for virtualized mission-critical applications, as well as backup storage efficiencies.

• Commvault software provides a comprehensive data protection solution for HPE ConvergedSystem 700 that accelerates time to deployment, and reduces risk and costs while maintaining overall application service-level objectives.

Appendix A: Bill of materials The HPE ConvergedSystem 700 (CS700) is a pre-defined solution with the ability to vary key components to meet a customer’s needs. The product ordering information is defined in detail in the CS700 QuickSpecs in the “How to order” section of that document. This list notes the key customizations used for testing this solution.

Note Part numbers are at time of testing and subject to change. The bill of materials does not include complete support options or other rack and power requirements. If you have questions regarding ordering, please consult with your HPE Reseller or HPE Sales Representative for more details. hpe.com/us/en/services/consulting.html

Red Hat Entitlements With the Red Hat Enterprise Linux unlimited VM entitlement, users have the right to run an unlimited number of desktop or server VMs on each entitled Red Enterprise Virtualization Hypervisor node. As each environment is unique and may not run Red Hat Enterprise Linux exclusively, this entitlement is not included in the parts list for the reference architecture. Licensing of the virtual machines is the responsibility of the customer.

http://www.hpe.com/us/en/services/consulting.html


(Per Site) HPE ConvergedSystem 700 (CS700) consisting of:

• 8 x HPE ProLiant BL460c Gen9 server blades, each with:

– 2 x Intel Xeon E5-2690 v3 12-core CPUs @ 2.60 GHz

– 256 GB Memory

– HPE FlexFabric 20 Gb 2-port 650FLB FIO Adapter

• 2 x HPE ProLiant DL360 Gen9 (management servers), each with:

– 2 x Intel Xeon E5-2680 v3 12-core CPUs @ 2.50 GHz

– 256 GB Memory

• HPE BladeSystem c7000 enclosure

– 2 x HPE Virtual Connect FlexFabric-20/40 F8 Module

– 2 x HPE Onboard Administrator

• HPE 3PAR StoreServ 7400c 4-node

– 120 x 300 GB SFF Fast Class (FC) in 10 SFF Drive enclosures

• Switches

– 2 x HPE SN6000B Fibre Channel Switches

– 2 x HPE FlexFabric 5900AF-48XG-4QSFP+ Network Switches

– 2 x HPE FlexFabric 5900AF-48G-4XG-2QSFP+ Network Switches

– Optional Cisco Nexus series network switches:

2 x Cisco Nexus 56128P Network Switches

2 x Cisco Nexus 3048TP-1GE Network Switches

2 x Cisco Nexus 2248PQ Network Switches

HPE StoreOnce 4700 24 TB Backup

HPE 3PAR StoreServ 7400c Storage Base

The CS700 QuickSpecs can be viewed as HTML at: http://h20195.www2.hpe.com/V2/GetHtml.aspx?docname=c04505387

The HPE StoreOnce QuickSpecs can be viewed as HTML at: http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=c04328820

http://h20195.www2.hpe.com/V2/GetHtml.aspx?docname=c04505387

http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=c04328820


Appendix B: Solution hardware configuration and components Table 12 outlines the hardware configurations deployed in HPE ConvergedSystem 700 based on the number of workload servers and the particular storage solution selected.

Table 12. Hardware and software configurations

Component Quantity Description

Workload server 2–16 per c7000 enclosure

HPE ProLiant BL460c Gen9 server blade each with:

• 2 x Intel Xeon processor

E5-2690 v3 (2.66 GHz/12-core), E5-2680 v3 (2.5 GHz/12-core), E5-2670 v3 (2.3 GHz/12-core), E5-2660 v3 (2.6 GHz/10 core), E5-2650 v3 (2.3 GHz/10-core), E5-2640 v3 (2.6 GHz/8 core), E5-2683 v3 (2 GHz/14 core), E5-2630 v3 (2.4 GHz/8 core), E5-2620 v3 (2.4 GHz/6 core), E5-2623 v3 (3 GHz/4 core), E5-2609 v3 (1.9 GHz/6 core), E5-2685 v3 (2.6 GHz/12 core), E5-2603 v3 (1.6 GHz/6 core), E5-2650L v3 (1.8 GHz/12 core), E5-2698 v3 (2.3 GHz/16 core), E5-2630L v3 (1.8 GHz/8 core), E5-2695 v3 (2.3 GHz/14 core), E5-2637 v3 (3.5 GHz/4 core), E5-2697 v3 (2.6 GHz/14 core), E5-2667 v3 (3.2 GHz/8 core), E5-2643 v3 (3.4 GHz/6 core), E5-2699 v3 (2.3 GHz/18 core)

• 64 GB–512 GB

• HPE Smart Array P244br controller and 1G FBWC

• Optional 2 x SAS hard drives (300 GB/15,000 rpm, 450 GB/10,000 rpm, or 600 GB/10,000 rpm)

• 1 x HPE FlexFabric 20Gb 2-port 650FLB FIO Adapter

2-8 per c7000 enclosure

HPE ProLiant WS460c Gen9 server blade

• NVIDIA® GRID K1 or K2 Graphics accelerator options

• Mixed blade environment supported

Management server 2 or 4 (See Note) HPE ProLiant DL360 Gen9 server, each with:

• 2 x Intel Xeon Processor E5-2680 v3 (2.5 GHz/12-core)

• 256 GB RAM

• HPE Smart Array P440ar controller with 2 GB FBWC

• 8 x SAS hard drives (600 GB/10,000 rpm)

• HPE FlexFabric 10Gb 2-port 556FLR-SFP+ Adapter

Note: CloudSystem SW option will add an additional 10Gb NIC to each DL360 Gen9 management server on the order.

• HPE 82Q 8Gb Dual Port PCIe Fibre Channel Host Bus Adapter

• Optional PCI Card:

HPE StoreFabric CN1200E 10Gb CNA

• SATA DVD-RW optical drive

Note: CloudSystem SW install option will include DL360 Gen9 server and additional 10Gb NICs for each management server.

HPE 3PAR StoreServ Storage

7200c 2N HPE 3PAR StoreServ 7200c Storage in a 42U HPE i–Series rack

7400c 2N or 4N HPE 3PAR StoreServ 7400c Storage in a 42U HPE i–Series rack



Network switches (HPE option)

2 (4 when greater than 4 enclosures)

HPE FlexFabric 5900AF-48XG-4QSFP+ Switches

2 HPE FlexFabric 5900AF-48G-4XG-2QSFP+ Switches (multi-rack only)

Network switches (Cisco option)

2 (4 when greater than 4 enclosures)

Cisco Nexus 2248PQ and 3048TP

2 Cisco Nexus 56128P (multi-rack only)

SAN switches 2 (4 when greater than 4 enclosures)

HPE SN6000B 16Gb 48/24 Fibre Channel Switches (with an optional upgrade to activate 24 additional ports) or HPE SN6000B 16Gb 48/48 Fibre Channel Switches (multi-rack only)

Flat SAN Single-rack only


Component Quantity Description

Infrastructure 1–8 HPE BladeSystem c7000 Platinum enclosure, each with:

• 2 x HPE Virtual Connect FlexFabric 20/40 F8 Modules

• 2 x HPE Onboard Administrator for the HPE BladeSystem c7000 enclosure

1 (1 or 2 c7000 enclosures) or

2 (3, 4, or 5 c7000 enclosures) or

3 (6, 7, or 8 c7000 enclosures)

HPE i–Series rack – 42U compute rack

1–2 (Array 1 rack + Optional Array 1 extension rack)

3–4 (Optional Array 2 Rack + Array 2 extension rack)

HPE i–Series rack – 42U storage rack

Components Depending on the configuration chosen, HPE ConvergedSystem 700 can deliver the following key components:

• Hardware

– HPE Intelligent Infrastructure for intelligent rack and power infrastructure management

– HPE BladeSystem c7000 Platinum enclosures

– HPE Virtual Connect FlexFabric 20/40 F8 Modules

– HPE ProLiant BL460c Gen9 servers blades with Intel Xeon E5-v3 series processors (workload servers)

– HPE ProLiant WS460c Gen9 workstation blades with NVIDIA K1 or K2 Graphic accelerator options

– HPE ProLiant DL360 Gen9 servers with Intel Xeon E5-2680 v3 (management servers)

– HPE 3PAR StoreServ 7200c, 7400c, 7440c, 7450c, or 8000 (multi-rack only) Storage

– HPE FlexFabric 5900AF or Cisco Nexus series Switches

– HPE SN6000B SAN Switches for multi-rack solutions

– HPE Virtual Connect for 3PAR with Flat SAN technology for single rack solutions

• Software

– HPE OneView

– HPE Insight Remote Support

– HPE 3PAR StoreServ Software (Note: While any HPE 3PAR software option can be added to an HPE ConvergedSystem 700 [CS700] configuration, only the Operating System Software suite is added by default.):

HPE 3PAR Operating System Software Suite

o HPE 3PAR Operating System

o HPE 3PAR Thin Provisioning

o HPE 3PAR Thin Conversion

o HPE 3PAR Thin Persistence

o HPE 3PAR Thin Copy Reclamation


o HPE 3PAR Thin Deduplication

o HPE 3PAR Thin Clones

o HPE 3PAR Autonomic Rebalance

o HPE 3PAR System Tuner

o HPE 3PAR Management Console

o HPE 3PAR SmartStart

o HPE 3PAR Host Explorer

Note Below are additional HPE 3PAR software options that can be added to a CS700 configuration:

• HPE 3PAR Virtual Copy Software

• HPE 3PAR System Reporter (Note: comes with 3PAR 8000)

• HPE 3PARInfo

• HPE 3PAR Adaptive Optimization

• HPE 3PAR Dynamic Optimization

• HPE 3PAR Priority Optimization

• HPE 3PAR Remote Copy Software

• HPE 3PAR Peer Persistence

• HPE 3PAR Virtual Domains

• HPE 3PAR Virtual Lock

• HPE 3PAR Peer Motion

• HPE 3PAR Online Import Software

• For HPE ConvergedSystem 700 for VMware, the following additional software components are included:

– HPE OneView for VMware vCenter Server

HPE OneView for vCenter Server Module

HPE OneView for vCenter Storage Module

HPE 3PAR Management Plug-in and Recovery Manager for VMware vSphere Web Services

– HPE OneView for vRealize Operations Manager

– HPE Insight Control Server Provisioning

– Microsoft Windows Server® 2012 R2 Standard Edition

– HPE VSR1000 Virtual Services Router

– VMware vSphere with Operations Management (vSOM)

VMware vSphere Enterprise Plus

VMware vRealize Operations Standard

– VMware vCenter Server


– HPE 3PAR Application Software Suite for VMware vSphere

HPE 3PAR Recovery Manager for VMware vSphere

HPE 3PAR Management Plug-in for VMware vCenter

HPE 3PAR vSphere APIs for Storage Awareness (VASA) support

HPE 3PAR VAAI Plug-in

HPE 3PAR Host Explorer for VMware vSphere

• Services

– HPE Factory Express services

– Onsite installation and start-up service

– Solution-level support services, including selectable HPE Care Pack service


Sign up for updates

© Copyright 2016-2018 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Intel and Xeon are trademarks of Intel Corporation in the U.S. and other countries. Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. 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. Citrix and XenDesktop are registered trademarks of Citrix Systems, Inc. and/or one more of its subsidiaries and may be registered in the United States Patent and Trademark Office and in other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. NVIDIA is a trademark and/or registered trademark of NVIDIA Corporation in the U.S. and other countries.

4AA5-5137ENW, June 2018, Rev. 1

Resources and additional links HPE StoreOnce Backup System user guide, hpe.com/storage/storeonce

HPE StoreOnce Backup System Linux and UNIX Configuration Guide, https://support.hpe.com/hpsc/doc/public/display?docId=c02299831

Commvault backup and recovery documentation, http://documentation.commvault.com

Commvault certified backup and recovery hardware compatibility matrix, http://documentation.commvault.com/hardwarematrix

HPE Storage, hpe.com/storage

HPE ConvergedSystem 700, hpe.com/info/cs700

HPE Reference Architectures, hpe.com/info/ra

To help us improve our documents, please provide feedback at hpe.com/contact/feedback.

http://www.hpe.com/info/getupdated

http://www.facebook.com/sharer.php?u=http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=4AA5-5137ENW

http://twitter.com/home/?status=Backup%20and%20Recovery%20solution%20for%20HPE%20ConvergedSystem%20700%20with%20Commvault%20Data%20Platform%20and%20HPE%20StoreOnce+@+http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=4AA5-5137ENW

http://www.linkedin.com/shareArticle?mini=true&ro=true&url=http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=4AA5-5137ENW&title=Backup%20and%20Recovery%20solution%20for%20HPE%20ConvergedSystem%20700%20with%20Commvault%20Data%20Platform%20and%20HPE%20StoreOnce+&armin=armin

http://www.hpe.com

http://www.hpe.com/storage/storeonce

https://support.hpe.com/hpsc/doc/public/display?docId=c02299831

http://documentation.commvault.com/

http://documentation.commvault.com/hardwarematrix

http://www.hpe.com/storage

http://www.hpe.com/info/cs700

http://www.hpe.com/info/ra

http://www.hpe.com/contact/feedback

Backup and Recovery solution for HPE … · with Commvault Data Platform and HPE StoreOnce ....

Documents

Transcript of Backup and Recovery solution for HPE … · with Commvault Data Platform and HPE StoreOnce ....