Cisco HyperFlex with Veeam Availability Suite for Multisite Deployments

Deployment Guide for Data Protection of Multisite Cisco HyperFlex Deployments through Veeam Availability Suite 9.5 Update 2 and Cisco UCS S3260 Storage Server

NOTE: Works with document’s Advanced Properties “First Published” property. Click File | Properties | Advanced Properties | Custom.

Last Updated: March 6, 2018

NOTE: Works with document’s Advanced Properties “Last Updated” property. Click File | Properties | Advanced Properties | Custom.

About the Cisco Validated Design Program

The Cisco Validated Design (CVD) program consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. For more information visit

http://www.cisco.com/go/designzone.

ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, "DESIGNS") IN THIS MANUAL ARE PRESENTED "AS IS," WITH ALL FAULTS.  CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.  IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE.  USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS.  THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS.  USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS.  RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unified Computing System (Cisco UCS), Cisco UCS B-Series Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS Management Software, Cisco Unified Fabric, Cisco Application Centric Infrastructure, Cisco Nexus 9000 Series, Cisco Nexus 7000 Series. Cisco Prime Data Center Network Manager, Cisco NX-OS Software, Cisco MDS Series, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study,  LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)

© 2017 Cisco Systems, Inc. All rights reserved.

 

Table of Contents

Executive Summary. 7

Solution Overview.. 8

Introduction. 8

Audience. 8

Purpose of this Document 8

Solution Summary. 9

Technology Overview.. 11

Cisco Unified Computing System... 12

Cisco Unified Computing System Components. 13

Cisco Fabric Interconnects. 13

Cisco UCS S3260 Storage Server 14

Cisco HyperFlex HX-Series Nodes. 16

Cisco VIC 1227 MLOM Interface Card. 17

Cisco HyperFlex Converged Data Platform Software. 17

Data Operations and Distribution. 19

Cisco HyperFlex Storage Integration with Veeam... 22

Veeam Availability Suite. 22

Backup. 22

Restore. 23

Veeam Explorer 24

Replication. 25

Deployment Types. 25

Failover and Failback. 28

Backup Server 29

Components. 29

Backup Proxy. 34

Veeam Repository Sizing. 34

Solution Design. 36

Remote Office - Branch Office Replication for Cisco HyperFlex. 37

Deployment Architecture. 38

Multisite Backup and Replication for Cisco HyperFlex. 40

Deployment Architecture. 41

Design Considerations. 44

Unified Management 44

Network. 45

WAN Acceleration for Backup and Replica. 46

Veeam Backup Enterprise Manager Console. 46

Veeam Transport Mode for HX Cluster 47

Veeam Proxy Server Distribution. 48

Proxy Distribution for HyperFlex ROBO Replication. 48

Proxy Distribution for Multisite HyperFlex Deployments. 48

Veeam Backup Copy Jobs. 50

Deployment Hardware and Software. 51

Software Versions. 51

Configuration Guidelines. 52

Network Switch Configuration. 55

Physical Connectivity. 55

Cisco Nexus Base. 55

Set Up Initial Configuration. 55

Cisco Nexus Switch Configuration. 57

Enable Licenses. 57

Set Global Configurations. 58

Create VLANs. 58

Add NTP Distribution Interface. 59

Create Port Channels. 59

Configure Port Channel Parameters. 60

Configure Virtual Port Channels. 61

Uplink into Existing Network Infrastructure. 63

Cisco UCS S3260 Storage Server and HyperFlex Configuration. 64

Cisco UCS Base Configuration. 64

Perform Initial Setup of Cisco UCS 6248UP Fabric Interconnects. 64

Cisco UCS Setup. 66

Log in to Cisco UCS Manager 66

Upgrade Cisco UCS Manager Software to Version 3.1(3c) 66

Anonymous Reporting. 67

Add Block IP Addresses for KVM Access. 67

Synchronize Cisco UCS to NTP.. 68

Uplink Ports. 69

Uplink Port Channels. 70

Edit Chassis Discovery Policy. 71

Server Ports. 72

Server Discovery. 73

HyperFlex Installation. 75

Cisco UCS S3260 Configuration. 76

Create Sub-Organization. 77

Create Chassis Firmware Packages. 77

Create Disk Zoning Policy. 78

Setting S3260 Disk to Unconfigured Good. 81

Create MAC Address Pools. 81

Create UUID Suffix Pool 83

Create Server Pool 84

Create VLANs. 85

Create Host Firmware Package. 86

QoS Policy. 86

Create Network Control Policy for Cisco Discovery Protocol 88

Create Power Control Policy. 89

Create Server BIOS Policy. 90

Create Maintenance Policy. 91

Create Adaptor Policy. 92

Create vNIC Templates. 93

Create Disk Group Policy. 103

Create Storage Profile. 113

Create Chassis  Profile Template. 116

Create Service Profile Template. 117

Create Chassis Profile. 125

Associate Chassis Profile to S3260 Chassis. 126

Create Service Profiles. 129

Associate Service Profile to Server Node of S3260 Chassis. 129

Veeam Availability Suite 9.5 Installation. 133

Install and Configure Windows 2016. 133

Load Driver for S3260 RAID Controller 134

Update Cisco VIC Driver for Windows 2016. 137

Update Intel ChipSet Driver for Windows 2016. 142

Configure Network for Veeam Backup Server 145

Create Disk Volume for Veeam Repository. 145

Install Veeam Availability Suite 9.5. 146

Configure Veeam Availability Suite 9.5. 154

Configure HX Storage Infrastructure with Veeam... 161

Cisco HyperFlex Remote Site Protection. 162

Configure Remote Veeam Proxy to Replicate VM on Cisco HyperFlex Primary Site. 163

Add Remote VCenter to the Veeam Console. 168

Cisco HyperFlex Multisite Protection. 172

Validation. 175

Backup VM on HX Cluster with HyperFlex and Veeam Storage Integration. 175

Remote Office / Branch Office VM Replication. 181

Backup Copy Jobs Across Data Centers. 188

Restore Backup Copy Job VM to DR Site. 190

Validated Hardware and Software. 204

Bill of Materials. 206

References. 209

About the Authors. 210

Acknowledgements. 210

 

 

The Cisco HyperFlex™ Systems solution together with Veeam Availability Suite gives customers a flexible, agile, and scalable infrastructure that is protected and easy to deploy. Building on top of the Cisco HyperFlex HX Data Platform’s built-in protection tools, Veeam Availability Suite expands the protection of your data with local and remote backups, VM-level replication and Backup Copy jobs. Today’s data centers are heterogeneous, and most administrators want to avoid siloed data protection for each application or infrastructure stack. Customers need data protection to work across the enterprise and for recovery to be self-service, easy, and fast—whether the data is local or remote.

Cisco and Veeam have partnered to deliver a joint solution which enables backup, restore and replicate, virtualized workloads running on Cisco HyperFlex , utilizing Veeam Availability Suite deployed on Cisco UCS S3260 Storage Server and Cisco UCS C240 LFF Rack Server. Ensure fast, reliable backup and recovery of virtual machines, critical data and applications with a data protection solution that provides enterprise availability, business agility, and operational efficiency. Veeam and Cisco's solution helps customers realize the full potential of virtualization and converged infrastructures by simplifying management to minimize risk, decrease downtime, and easily adapt to business demands. IT administrators can leverage policy-based controls for smarter data protection to recover the data they want, when they want it, enabling organizations to confidently deploy a high performance, compatible solution that has been tested and validated by Cisco and Veeam experts.

The Veeam Availability Solution for Cisco UCS is a best-of-breed solution that is the perfect answer for customers requiring an advanced, enterprise-class data availability solution for their virtual environments that is simple to order, deploy and manage. In addition, it can easily expand over time as the need increases. It provides fast, flexible and reliable recovery of virtualized applications and data bringing virtual machine backup and replication together in a single solution with award-winning support.

This Cisco Validated Design (CVD), Data Protection for Multisite Cisco HyperFlex with Veeam Availability Suite, is a certified solution built on a modern architecture that delivers fast, reliable recovery, reduced total cost of ownership (TCO) and a better user experience, and addresses the challenge of delivering agile protection for Cisco HyperFlex platform. This solution utilizes Cisco components such as Cisco UCS Manager, Cisco Fabric Interconnect 6248UP, Cisco HyperFlex Data Platform, Cisco HyperFlex HX220c and HX240c nodes, Cisco Nexus 9000 series networking and Cisco UCS S3260 Storage Server.

This document, details on protection of Multisite Cisco HyperFlex deployments with Veeam Availability Suite and Cisco UCS S3260 Storage Server, is in continuation of Deployment Guide for Cisco HyperFlex with Veeam Availability Suite which details on the protection of HyperFlex Cluster in a single site deployment.

A Cisco Validated Design (CVD) and pre-validated reference architectures facilitate faster, more reliable, and more predictable customer deployments:

·         Each CVD has been extensively tested, validated, and documented by Cisco and partner experts

·         CVD's minimize both integration and performance risks to ensure always-on availability in the enterprise

From design to configuration, instructions to bill of materials (BOMs), CVDs provide everything businesses need to deploy the solutions in the most efficient manner; everything is clearly and precisely laid out.

Introduction

Designed specifically for virtual environments, Data Protection for Cisco HyperFlex with Veeam Availability Suite is integrated with VMware vSphere, helping ensure consistent and reliable virtual machine recovery.

The Cisco HyperFlex solution delivers next-generation hyperconvergence in a data platform to offer end-to-end simplicity for faster IT deployments, unifying computing, networking, and storage resources. The Cisco HyperFlex solution is built on the Cisco Unified Computing System™ (Cisco UCS®) platform and adheres to a data center architecture supporting traditional, converged, and hyperconverged systems with common policies and infrastructure management. The Cisco HyperFlex HX Data Platform is a purpose-built, high-performance, distributed file system delivering a wide range of enterprise-class data management and optimization services. This platform redefines distributed storage technology, expanding the boundaries of hyperconverged infrastructure with its independent scaling, continuous data optimization, simplified data management, and dynamic data distribution for increased data availability. This agile system is easy to deploy and manage, scales as your business needs change, and provides the first level of data availability. However, as with most systems, a second layer of protection that is equally agile is recommended.  Veeam Availability Suite can meet this need.

Veeam is an industry leader within the data protection market. In the era of Digital Transformation, Veeam recognizes the new challenges companies across the globe face in enabling the Always-On Enterprise™, a business that must operate 24.7.365. To address this, Veeam has pioneered a new market of Availability for the Always-On Enterprise by helping organizations meet today’s service-level objectives, enabling recovery of any IT service and related applications and data within seconds and minutes. Veeam consistently pushes the envelope in bringing sophisticated backup and disaster recovery functionality to enterprises and cloud providers

Veeam delivers efficient virtual machine (VM) backup and replication to dramatically lower the recovery time objective (RTO) and recovery point objective (RPO), for RTPO™ of <15 minutes for ALL applications and data. Veeam replication between HyperFlex clusters, both local and distributed, provides site-level DR. Veeam also provides backup and recovery at the VM- and item-level for instant recovery from more common, day-to-day problems. These isolated Veeam managed backups, stored on secondary storage, cloud or tape, allow organizations to meet both internal and external data protection and recovery requirements.

Audience

The intended audience for this document includes, but is not limited to, sales engineers, field consultants, professional services, IT managers, partner engineering, and customers looking to provision backup and recovery of virtualized application on Cisco HyperFlex Clusters deployed across data centers or in several Remote Offices, across different geographies.   

Purpose of this Document

This document elaborates on design ,deployment and configuration procedures for protecting multisite Cisco HyperFlex deployments with Veeam Availability Suite and Cisco UCS S3260 Storage Server.

Solution Summary

This solution for Cisco HyperFlex and Cisco UCS S3260 Storage Server with Veeam Availability Suite delivers reliable and fast Backup and Replication of application VMs residing on multisite Cisco HyperFlex Clusters. The solution extends across the following:

·         HyperFlex clusters deployed in Remote Office/Branch Office (ROBO)

·         HyperFlex Cluster deployed in multiple Data Center with each Data Center having local repository to backup application VM through Veeam Availability Suite and Cisco UCS S3260 Storage Server

This solution can be accurately sized in accordance with present demands of enterprise deployments and thereafter can be scaled as per the future growth projections.

Veeam Availability Suite comprises of Veeam Repository, Veeam Proxy and Veeam Backup Server all reside on a single Cisco UCS S3260 Storage Server which provides up to 600 TB of raw storage capacity. Replication of application VM is executed to a separate Cisco HyperFlex Cluster.

Application VM deployed on HyperFlex ROBO Clusters are replicated through Cisco UCS C240 M4 LFF Rack Server to HyperFlex cluster on Primary Data Center using Veeam Availability Suite.

Figure 1 provides a high-level view of Cisco HyperFlex with Cisco S3260 Storage Server and Veeam Availability Suite and elaborates on the following:

·         Replication of application VMs across Cisco HyperFlex Clusters through Veeam Availability Suite

·         Backup of application VMs on Cisco S3260 Storage Server

·         Protection of Backups with Backup copy jobs across Data Center through Veeam Availability Suite

·         Management end points for Cisco HyperFlex, Cisco UCS S3260 Storage Server and Veeam Availability Suite

 

Figure 1  Cisco HyperFlex with Veeam Availability Suite and Cisco UCS S3260 Storage Server

This CVD for Cisco HyperFlex with Veeam Availability Suite for Multisite Deployments, uses the following infrastructure and software components:

·         Cisco Unified Computing System (Cisco UCS)

·         Cisco HyperFlex Data Platform

·         Cisco Nexus 9000

·         Veeam Availability Suite 9.5 Update 2

·         Windows 2016  Datacenter Edition for Veeam Availability Suite

This deployment guide uses the following models of above mentioned infrastructure components:

·         Cisco UCS S3260 Storage Server

·         Cisco UCS C240 M4 LFF Rack Server

·         Cisco UCS HX220c M4 Node

·         Cisco UCS HX240c M4 Node

·         Cisco UCS 6200 Series Fabric Interconnects (FI)

·         Cisco Nexus 9300 Series Platform Switches

The other optional software and hardware components of this deployment solution are:

·         Cisco UCS Central provides a scalable management platform for managing multiple, globally distributed Cisco UCS domains with consistency by integrating with Cisco UCS Manager (USCM) to provide global configuration capabilities for pools, policies, and firmware. Cisco UCS Central platform eliminates disparate management environments. It supports up to 10,000 Cisco UCS servers (blade, rack, and Mini) and Cisco HyperFlex Systems. You can manage multiple Cisco UCS instances or domains across globally-distributed locations.

·         Veeam Enterprise Manager provides a single “pane of glass” management for a globally dispersed Backup and Replication environment.  It collects data from the backup servers and enables you to run backup and replication jobs across the entire back-up infrastructure and edit and clone jobs using a single job as a template. It also provides reporting data for various areas (for example, all jobs performed within the last 24 hours or 7 days, all VMs engaged in these jobs, and so on). Using indexing data consolidated on one server, Veeam Backup Enterprise Manager provides advanced capabilities to search for VM guest OS files in VM backups created on all backup server (even if they are stored in repositories on different sites), and recover them in a single click. Search for VM guest OS files is enabled through Veeam Backup Enterprise Manager itself; to streamline the search process, you can optionally deploy a Veeam Backup Search server in your backup infrastructure.

·         Veeam WAN Accelerator is a dedicated component of the backup infrastructure responsible for global data caching and data deduplication. On each WAN accelerator, Veeam Backup and Replication installs the Veeam WAN Accelerator Service responsible for WAN acceleration tasks.

The above components are integrated using component and design best practices to deliver an integrated infrastructure for Enterprise and cloud data centers.

The next section provides a technical overview of the hardware and software components of the present solution design. 

Cisco Unified Computing System

Cisco brings 30 years of breadth, leadership, and vision to guide businesses through networking and infrastructure challenges. Cisco’s Unified Computing System (UCS) continues Cisco's long history of innovation in delivering integrated systems that deliver business results. Cisco UCS integrated infrastructure solutions speed up IT operations today and create the modern technology foundation needed for the critical business initiatives of tomorrow.

The Cisco Unified Computing System is a next-generation data center platform that unites compute, network, and storage access. The platform, optimized for virtual environments, is designed using open industry-standard technologies and aims to reduce total cost of ownership (TCO) and increase business agility. The system integrates a low-latency, lossless 10 Gigabit Ethernet unified network fabric with enterprise-class, x86-architecture servers. It is an integrated, scalable, multi chassis platform in which all resources participate in a unified management domain.

The main components of Cisco Unified Computing System are:

·         Computing—The system is based on an entirely new class of computing system that incorporates rack-mount and blade servers based on Intel Xeon Processors.

·         Network—The system is integrated onto a low-latency, lossless, 10-Gbps unified network fabric. This network foundation consolidates LANs, SANs, and high-performance computing networks which are separate networks today. The unified fabric lowers costs by reducing the number of network adapters, switches, and cables, and by decreasing the power and cooling requirements.

·         Virtualization—The system unleashes the full potential of virtualization by enhancing the scalability, performance, and operational control of virtual environments. Cisco security, policy enforcement, and diagnostic features are now extended into virtualized environments to better support changing business and IT requirements.

·         Storage access—The system provides consolidated access to both (Storage Area Network) SAN storage and Network Attached Storage (NAS) over the unified fabric. By unifying the storage access the Cisco Unified Computing System can access storage over Ethernet, Fibre Channel, Fibre Channel over Ethernet (FCoE), and iSCSI. This provides customers with choice for storage access and investment protection. In addition, the server administrators can pre-assign storage-access policies for system connectivity to storage resources, simplifying storage connectivity, and management for increased productivity.

·         Management—The system uniquely integrates all system components which enable the entire solution to be managed as a single entity by the Cisco UCS Manager (UCSM). The Cisco UCS Manager has an intuitive graphical user interface (GUI), a command-line interface (CLI), and a robust application programming interface (API) to manage all system configuration and operations.

The Cisco Unified Computing System is designed to deliver:

·         A reduced Total Cost of Ownership and increased business agility.

·         Increased IT staff productivity through just-in-time provisioning and mobility support.

·         A cohesive, integrated system which unifies the technology in the data center. The system is managed, serviced and tested as a whole.

·         Scalability through a design for hundreds of discrete servers and thousands of virtual machines and the capability to scale I/O bandwidth to match demand.

·         Industry standards supported by a partner ecosystem of industry leaders

Cisco Unified Computing System Components

Cisco Fabric Interconnects

The Cisco UCS 6200 Series Fabric Interconnect is a core part of the Cisco Unified Computing System, providing both network connectivity and management capabilities for the system. The Cisco UCS 6200 Series offers line-rate, low-latency, lossless 10 Gigabit Ethernet, Fibre Channel over Ethernet (FCoE) and Fibre Channel functions.

The Cisco UCS 6200 Series provides the management and communication backbone for the Cisco UCS C-Series and HX-Series rack-mount servers, Cisco UCS B-Series Blade Servers and Cisco UCS 5100 Series Blade Server Chassis. All servers and chassis, and therefore all blades, attached to the Cisco UCS 6200 Series Fabric Interconnects become part of a single, highly available management domain. In addition, by supporting unified fabric, the Cisco UCS 6200 Series provides both the LAN and SAN connectivity for all blades within its domain.

From a networking perspective, the Cisco UCS 6200 Series uses a cut-through architecture, supporting deterministic, low-latency, line-rate 10 Gigabit Ethernet on all ports, 1Tb switching capacity, 160 Gbps bandwidth per chassis, independent of packet size and enabled services. The product family supports Cisco low-latency, lossless 10 Gigabit Ethernet unified network fabric capabilities, which increase the reliability, efficiency, and scalability of Ethernet networks. The Fabric Interconnect supports multiple traffic classes over a lossless Ethernet fabric from a server through an interconnect. Significant TCO savings come from an FCoE-optimized server design in which network interface cards (NICs), host bus adapters (HBAs), cables, and switches can be consolidated.

Cisco UCS 6248UP Fabric Interconnect

The Cisco UCS 6248UP 48-Port Fabric Interconnect is a one rack unit (1 RU) 10 Gigabit Ethernet, FCoE and Fiber Channel switch offering up to 960-Gbps throughput and up to 48 ports. The switch has 32 1/10-Gbps fixed Ethernet, FCoE and FC ports and one expansion slot.

 

Figure 2 Cisco UCS 6248UP Fabric Interconnect

Cisco UCS S3260 Storage Server

The Cisco UCS® S3260 Storage Server, is a modular, high-density, high-availability dual-node rack server well suited for service providers, enterprises, and industry-specific environments. It provides dense, cost-effective storage to address your ever-growing data needs. Designed for a new class of data-intensive workloads, it is simple to deploy and excellent for applications for big data, data protection, software-defined storage environments, scale-out unstructured data repositories, media streaming, and content distribution.

Some of the key features of Cisco UCS S3260 Storage Server are:

·         Dual 2-socket server nodes based on Intel Xeon processor E5-2600 v2 or v4 CPUs with up to 36 cores per server node

·         Up to 512 GB of DDR3 or DDR4 memory per server node (1 TB total)

·         Support for high-performance Non-Volatile Memory Express (NVMe) and flash memory

·         Massive 600-TB data storage capacity that easily scales to petabytes with Cisco UCS Manager

·         Policy-based storage management framework for zero-touch capacity on demand

·         Dual-port 40-Gbps system I/O controllers with Cisco UCS Virtual Interface Card (VIC) 1300 platform embedded chip

·         Unified I/O for Ethernet or Fibre Channel to existing NAS or SAN storage environments

·         Support for Cisco bidirectional (BiDi) transceivers, with 40-Gbps connectivity over existing 10-Gbps cabling infrastructure

For more information, see: http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/datasheet-c78-735611.html

 

Figure 3  Cisco UCS C3260 M4 Rack Server

The S3260 can be CIMC managed, or Cisco UCS Manager managed as a registered Chassis with the Cisco UCS Fabric Interconnects.  When the S3260 is Cisco UCS Manager managed, the Chassis will use a Chassis Profile can be generated from template, and will contain specifications for Firmware and Maintenance policies as well as the Disk Zoning Policy.  The Disk Zoning Policy will be used to set how disk slot allocation occurs between server nodes.

Figure 4 Cisco UCS S3260 Chassis Profile Association

Server Nodes in a Cisco UCS Manager managed S3260 are configured in nearly the same manner as standard Cisco UCS B-Series and Cisco UCS Manager managed Cisco UCS C-Series servers.  The Server Nodes will use Service Profiles that can be provisioned from template, but will need to have a Storage Profile set within the Service Profile to be able to access the disk slots made available to it by the Disk Zoning Policy set within the Chassis Profile of the Chassis the Node is hosted within.

 

Figure 5  Cisco UCS S3260 Server Node Service Profile Association

Within the Storage Profile there are two main functions, Local LUN creation that will be specified by Disk Group Policies, which are set within the Storage Profile.  The LUNs created from the Disk Group Policies will have options of RAID 0, 1, 5, 6, 10, 50, or 60 and will allow the selection of type, quantity, or manual specification of slot the disk should be used from, as well as drive configuration policies of the LUN.  S3260 M3 server nodes will use a Controller Definition, which will set how the PCH Controller should handle the rear facing SSDs of the S3260 Chassis.  The Controller Definition is specific to the SSD drives allocated to the node by the PCH Controller and will have valid settings of RAID 0, 1, or no RAID.

Cisco HyperFlex HX-Series Nodes

A HyperFlex cluster requires a minimum of three HX-Series nodes. Data is replicated across at least two of these nodes, and a third node is required for continuous operation in the event of a single-node failure. The HX-Series nodes combine the CPU and RAM resources for hosting guest virtual machines, with the physical storage resources used by the HyperFlex software. Each HX-Series node is equipped with one high-performance SSD drive for data caching and rapid acknowledgment of write requests and is also is equipped with up to the platform’s physical capacity of spinning disks for maximum data capacity.

Cisco HyperFlex HX220c-M4S Node

The Cisco HyperFlex HX220c-M4S rackmount server is one rack unit (1 RU) high and can mount in an industry-standard 19-inch rack. This small footprint configuration contains a minimum of three nodes with six 1.2 terabyte (TB) SAS drives that contribute to cluster storage capacity, a 120 GB SSD housekeeping drive, a 480 GB SSD caching drive, and two Cisco Flexible Flash (FlexFlash) Secure Digital (SD) cards that act as mirrored boot drives.

Figure 6 HX220c-M4S Node

Cisco HyperFlex HX240c-M4SX Node

The Cisco HyperFlex HX240c-M4S rackmount server is two rack unit (2 RU) high and can mount in an industry-standard 19-inch rack. This capacity optimized configuration contains a minimum of three nodes, a minimum of fifteen and up to twenty-three 1.2 TB SAS drives that contribute to cluster storage, a single 120 GB SSD housekeeping drive, a single 1.6 TB SSD caching drive, and two FlexFlash SD cards that act as mirrored boot drives.

Figure 7  HX240c-M4SX Node

Cisco VIC 1227 MLOM Interface Card

The Cisco UCS Virtual Interface Card (VIC) 1227 is a dual-port Enhanced Small Form-Factor Pluggable (SFP+) 10-Gbps Ethernet and Fibre Channel over Ethernet (FCoE)-capable PCI Express (PCIe) modular LAN-on-motherboard (mLOM) adapter installed in the Cisco UCS HX-Series Rack Servers (Error! Reference source not found.). The mLOM slot can be used to install a Cisco VIC without consuming a PCIe slot, which provides greater I/O expandability. It incorporates next-generation converged network adapter (CNA) technology from Cisco, enabling a policy-based, stateless, agile server infrastructure that can present up to 256 PCIe standards-compliant interfaces to the host that can be dynamically configured as either network interface cards (NICs) or host bus adapters (HBAs). The personality of the card is determined dynamically at boot time using the service profile associated with the server. The number, type (NIC or HBA), identity (MAC address and World Wide Name [WWN]), failover policy, and quality-of-service (QoS) policies of the PCIe interfaces are all determined using the service profile.

Figure 8 Cisco VIC 1227 mLOM Card

Cisco HyperFlex Converged Data Platform Software

The Cisco HyperFlex HX Data Platform is a purpose-built, high-performance, distributed file system with a wide array of enterprise-class data management services. The data platform’s innovations redefine distributed storage technology, exceeding the boundaries of first-generation hyperconverged infrastructures. The data platform has all the features that you would expect of an enterprise shared storage system, eliminating the need to configure and maintain complex Fibre Channel storage networks and devices. The platform simplifies operations and helps ensure data availability. Enterprise-class storage features include the following:

·         Replication of all written data across the cluster so that data availability is not affected if single or multiple components fail (depending on the replication factor configured).

·         Deduplication is always on, helping reduce storage requirements in which multiple operating system instances in client virtual machines result in large amounts of duplicate data.

·         Compression further reduces storage requirements, reducing costs, and the log- structured file system is designed to store variable-sized blocks, reducing internal fragmentation.

·         Thin provisioning allows large volumes to be created without requiring storage to support them until the need arises, simplifying data volume growth and making storage a “pay as you grow” proposition.

·         Fast, space-efficient clones rapidly replicate virtual machines simply through metadata operations.

·         Snapshots help facilitate backup and remote-replication operations: needed in enterprises that require always-on data availability.

Cisco HyperFlex HX Data Platform Administration Plug-in

The Cisco HyperFlex HX Data Platform is administered through a VMware vSphere web client plug-in. Through this centralized point of control for the cluster, administrators can create datastores, monitor the data platform health, and manage resource use. Administrators can also use this data to predict when the cluster will need to be scaled.

Figure 9 vCenter HyperFlex Web Client Plugin

Cisco HyperFlex HX Data Platform Controller

A Cisco HyperFlex HX Data Platform controller resides on each node and implements the Cisco HyperFlex HX Distributed Filesystem. The storage controller runs in user space within a virtual machine intercepting and handling  all I/O from guest virtual machines. The storage controller VM uses the VMDirectPath I/O feature to provide PCI pass-through control of the physical server’s SAS disk controller. This method gives the controller VM full control of the physical disk resources, utilizing the SSD drives as a read/write caching layer, and the HDDs as a capacity layer for distributed storage. The controller integrates the data platform into VMware software through two preinstalled VMware ESXi vSphere Installation Bundles (VIBs):

·         IOvisor:  The IOvisor is deployed on each node of the cluster and acts as a stateless NFS proxy that looks at each IO request and determines which cache vNode it belongs to and routes the IO to the physical node that owns that cache vNode. In the event of a failure, the IOvisor transparently handles it and will retry the same request to another copy of the data based on new information it receives. Decoupling the IOvisor from the controller VM enables access to the distributed filesystem and prevents hotspots. Compute-only nodes, and VMs continue to perform storage IO in the event of a disk, SSD, or even a storage controller failure.

·         VMware API for Array Integration (VAAI): This storage offload API allows vSphere to request advanced file system operations such as snapshots and cloning. The controller implements these operations through the manipulation of metadata rather than actual data copying, providing rapid response, and thus rapid deployment of new environments.

Data Operations and Distribution

The Cisco HyperFlex HX Data Platform controllers handle all read and write operation requests from the guest VMs to their virtual disks (VMDK) stored in the distributed datastores in the cluster. The data platform distributes the data across multiple nodes of the cluster, and across multiple capacity disks of each node, per the replication level policy selected during the cluster setup. This method avoids storage hotspots on specific nodes, and on specific disks of the nodes, and thereby also avoids networking hotspots or congestion from accessing more data on some nodes versus others.

Replication Factor

Enterprise class hyperconverged solutions should have three copies of data blocks across any three data nodes. This helps to ensure high availability during rare failure events such as single node failure and disk failure or during software and firmware upgrades, performed on a HX System. Thus three copies, or a replication factor of 3 (RF=3), is a default setting and also  a recommended best practice for HyperFlex systems.

·         Replication Factor 3: For every I/O write committed to the storage layer, 2 additional copies of the blocks written will be created and stored in separate locations, for a total of 3 copies of the blocks. Blocks are distributed in such a way as to ensure multiple copies of the blocks are not stored on the same disks, nor on the same nodes of the cluster. This setting can tolerate simultaneous failures of 2 disks, or 2 entire nodes without losing data and resorting to restore from backup or other recovery processes.

·         Replication Factor 2: For every I/O write committed to the storage layer, 1 additional copy of the blocks written will be created and stored in separate locations, for a total of 2 copies of the blocks. Blocks are distributed in such a way as to ensure multiple copies of the blocks are not stored on the same disks, nor on the same nodes of the cluster. This setting can tolerate a failure of 1 disk, or 1 entire node without losing data and resorting to restore from backup or other recovery processes.

Data Write Operations

For each write operation, data is written to the local caching SSD on the node where the write originated, and replica copies of that write are written to the caching SSD of the remote nodes in the cluster, per the replication factor setting. For example, at RF=3 a write will be written locally where the VM originated the write, and two additional writes will be committed in parallel on two other nodes. The write operation will not be acknowledged until all three copies are written to the caching layer SSDs. Written data is also cached in a write log area resident in memory in the controller VM, along with the write log on the caching SSDs (Figure 10). This process speeds up read requests when reads are requested of data that has recently been written.

Data Destaging, Deduplication and Compression

The Cisco HyperFlex HX Data Platform constructs multiple write caching segments on the caching SSDs of each node in the distributed cluster. As write cache segments become full, and based on policies accounting for I/O load and access patterns, those write cache segments are locked and new writes roll over to a new write cache segment. The data in the now locked cache segment is destaged to the HDD capacity layer of the node. During the destaging process, data is deduplicated and compressed before being written to the HDD capacity layer. The resulting data after deduplication and compression can now be written in a single sequential operation to the HDDs of the server, avoiding disk head seek thrashing and accomplishing the task in the minimal amount of time (Figure 10). Since the data is already deduplicated and compressed before being written, the platform avoids additional I/O overhead often seen on competing systems, which must later do a read/dedupe/compress/write cycle.

 

Figure 10          HyperFlex HX Data Platform Data Movement

Data Read Operations

For data read operations, data may be read from multiple locations. For data that was very recently written, the data is likely to still exist in the write log of the local platform controller memory, or the write log of the local caching SSD. If local write logs do not contain the data, the distributed filesystem metadata will be queried to see if the data is cached elsewhere, either in write logs of remote nodes, or in the dedicated read cache area of the local and remote SSDs. Finally, if the data has not been accessed in a significant amount of time, the filesystem will retrieve the data requested from the HDD capacity layer. As requests for reads are made to the distributed filesystem and the data is retrieved from the HDD capacity layer, the caching SSDs populate their dedicated read cache area to speed up subsequent requests for the same data. This multi-tiered distributed system with several layers of caching techniques, insures that data is served at the highest possible speed, leveraging the caching SSDs of the nodes fully and equally.

Cisco HyperFlex Storage Integration with Veeam

Veeam Backup & Replication integrates with HyperFlex by calling Cisco’s native snapshot APIs which improve the performance of backup and replication of VMware vSphere VMs hosted on Cisco HyperFlex. HyperFlex snapshots leverage VMware vSphere Storage APIs Array Integration (VAAI), which enables VMware vSphere ESXi hosts to communicate with storage devices and offload storage operations such as snapshot creation and cloning to the storage controller. Veeam Backup & Replication can use HyperFlex Snapshots for VM data processing, which helps speed up backup and replication operations, reduce impact of backup and replication activities on the production environment and improve Recovery Point Objectives (RPO). During the Backup or Replication process, Veeam processes application aware consistency with the Agentless VM Ingest processing and uses the HyperFlex Snapshots to preserve this stage for backup. Cisco’s integration into VMware allow Veeam to completely avoid the usage of VMware VM Snapshots. For more details, please visit Cisco HyperFlex Data Platform Backup Integration Guide.

Veeam Availability Suite

Veeam is an industry leader within the data protection market. In the era of Digital Transformation, Veeam recognizes the new challenges companies across the globe face in enabling the Always-On Enterprise™, a business that must operate 24.7.365. To address this, Veeam has pioneered a new market of Availability for the Always-On Enterprise by helping organizations meet today’s service-level objectives, enabling recovery of any IT service and related applications and data within seconds and minutes. Veeam consistently pushes the envelope in bringing sophisticated backup and disaster recovery functionality to enterprises and cloud providers.

Backup

Veeam Backup & Replication operates at the virtualization layer and uses an image-based approach for VM backup. To retrieve VM data, no agent software needs to be installed inside the guest OS. Instead, Veeam Backup & Replication leverages vSphere snapshot capabilities and Application Aware Processing. When a new backup session starts, a snapshot is taken to create a cohesive point-in-time copy of a VM including its configuration, OS, applications, associated data, system state and so on. Veeam Backup & Replication uses this point-in-time copy to retrieve VM data. Image-based backups can be used for different types of recovery, including full VM recovery, VM file recovery, Instant VM Recovery, file-level recovery and application item recovery.

Use of the image-based approach allows Veeam Backup & Replication to overcome shortfalls and limitations of traditional backup. It also helps streamline recovery verification and the restore process — to recover a single VM, there is no need to perform multiple restore operations. Veeam Backup & Replication uses a cohesive VM image from the backup to restore a VM to the required state without the necessity for manual reconfiguration and adjustment. In Veeam Backup & Replication, backup is a job-driven process where one backup job can be used to process one or more VMs. A job is a configuration unit of the backup activity. Essentially, the job defines when, what, how and where to back up. It indicates what VMs should be processed, what components should be used for retrieving and processing VM data, what backup options should be enabled and where to save the resulting backup file. Jobs can be started manually by the user or scheduled to run automatically. The resulting backup file stores compressed and deduplicated VM data. Compression and Deduplication is done by the Veeam Proxy server.

Regardless of the Backup method you use, the first run of a job creates a full backup of VM image. Subsequent job runs are incremental — Veeam Backup & Replication copies only those data blocks that have changed since the last backup job run. To keep track of changed data blocks, Veeam Backup & Replication uses different approaches, including VMware’s Changed Block Tracking (CBT) technology.

Changed Block Tracking

To perform incremental backup, Veeam Backup & Replication needs to know which data blocks have changed since the previous job run.

Figure 11           Change Block Tracking

For VMware VMs with hardware version 7 or later, Veeam Backup & Replication employs VMware vSphere Changed Block Tracking (CBT) — a native VMware feature. Instead of scanning VMFS, Veeam Backup & Replication queries CBT on vSphere through VADP and gets the list of blocks that have changed since the last run of this particular job. Use of CBT increases the speed and efficiency of block-level incremental backups. CBT is enabled by default; if necessary, you can disable it in the settings of a specific backup job.

Restore

Veeam Backup & Replication offers a number of recovery options for various disaster recovery scenarios:

·         Veeam Explorer enables you to restore Single Application specific items

·         Instant VM Recovery enables you to instantly start a VM directly from a backup file

·         Full VM recovery enables you to recover a VM from a backup file to its original or another location

·         VM file recovery enables you to recover separate VM files (virtual disks, configuration files and so on)

·         Virtual drive restore enables you to recover a specific hard drive of a VM from the backup file, and attach it to the original VM or to a new VM

·         Windows file-level recovery enables you to recover individual Windows guest OS files (from FAT, NTFS and ReFS file systems)

·         Multi-OS file-level recovery enables you to recover files from 15 different guest OS file systems

Veeam Backup & Replication uses the same image-level backup for all data recovery operations. You can restore VMs, VM files and drives, application objects and individual guest OS files to the most recent state or to any available restore point.

Veeam Explorer

Veeam Explorers are tools included in all editions of Veeam Backup & Replication. As of v9 and restore application items directly from VM backups and replicas. It provides fast and effortless Active Directory, Exchange, SharePoint, SQL Server and Oracle recovery without needing to provision extra storage, deploy agents, restore an entire virtual machine (VM) for granular recovery or spin anything up in an isolated network. This includes powerful, easy-to-use and affordable eDiscovery and granular recovery for:

·         Microsoft Active Directory: Search and restore all Active Directory object types (e.g., users, groups, computer accounts, contacts, expiring links), Group Policy Objects (GPOs), Active Directory-integrated Microsoft DNS records and Configuration Partition objects.

·         Microsoft Exchange: Get instant visibility into Exchange 2010, 2013 and 2016 backups, advanced search capabilities and quick recovery of individual Exchange items (e.g., emails, contacts, notes, etc.), Online Archive mailboxes, Purges folder support and hard-deleted (i.e., permanently deleted) items; eDiscovery features include detailed export reports and export size estimation based on query search criteria.

·         Microsoft SharePoint: Get instant visibility into SharePoint 2010, 2013 and 2016 backups, search for and quickly restore full SharePoint sites, item permissions and specific files. Export recovered items directly to their original SharePoint server or send them as an email attachment.

·         Microsoft SQL Server: Get fast transaction- and table-level recovery of SQL databases, including agentless transaction log backup and replay, so you can restore your SQL databases to a precise point in time and achieve low RTPO.

·         Oracle: Get transaction-level recovery of Oracle databases including agentless transaction log backup, so you can restore your Oracle databases to a precise point in time, self-service restore and restore via PowerShell.

Instant VM Recovery

With instant VM recovery, you can immediately restore a VM into your production environment by running it directly from the backup file. Instant VM recovery helps improve recovery time objectives (RTO), minimize disruption and downtime of production VMs. It is like having a "temporary spare" for a VM; users remain productive while you can troubleshoot an issue with the failed VM.

When instant VM recovery is performed, Veeam Backup & Replication uses the Veeam vPower technology to mount a VM image to an ESX(i) host directly from a compressed and deduplicated backup file. Since there is no need to extract the VM from the backup file and copy it to production storage, you can restart a VM from any restore point (incremental or full) in a matter of minutes.

After the VM is back online you can use VMware storage vMotion to migrate the VM back to production storage.

VM Object Recovery

Veeam Backup & Replication can help you to restore specific VM files (.vmdk, .vmx and others) if any of these files are deleted or the datastore is corrupted. This option provides a great alternative to full VM restore, for example, when your VM configuration file is missing and you need to restore it. Instead of restoring the whole VM image to the production storage, you can restore the specific VM file only. Another data recovery option provided by Veeam Backup & Replication is restore of a specific hard drive of a VM. If a VM hard drive becomes corrupted for some reason (for example, with a virus), you can restore it from the image-based backup to any good-to-know point in time.

Replication

To help ensure efficient and reliable data protection in your virtual environment, Veeam Backup & Replication complements image-based backup with image-based replication. Replication is the process of copying a VM from its primary location (source host) to a destination location (redundant target host). Veeam Backup & Replication creates an exact copy of the VM (replica), registers it on the target host and maintains it in sync with the original VM.

Replication provides the best recovery time objective (RTO) and recovery point objective (RPO) values, as you actually have a copy of your VM in a ready-to-start state. That is why replication is commonly recommended for the most critical VMs that need minimum RTOs. Veeam Backup & Replication provides means to perform both onsite replication for high availability (HA) scenarios and remote (offsite) replication for disaster recovery (DR) scenarios. To facilitate replication over WAN or slow connections, Veeam Backup & Replication optimizes traffic transmission — it filters out unnecessary data blocks (such as, duplicate data blocks, zero data blocks or blocks of swap files) and compresses replica traffic. Veeam Backup & Replication also allows you to apply network throttling rules to prevent replication jobs from consuming the entire bandwidth available in your environment.

Replication is a job-driven process with one replication job used to process one or more VMs. You can start the job manually every time you need to copy VM data or, if you want to run replication unattended, create a schedule to start the job automatically. Scheduling options for replication jobs are similar to those for backup jobs.

WAN Acceleration

WAN accelerators are optional components in the replication infrastructure. You can use WAN accelerators if you replicate VMs over a slow connection or over the WAN.

In the replication process, WAN accelerators are responsible for global data caching and deduplication. To use WAN acceleration, you must deploy two WAN accelerators in the following manner:

·         The source WAN accelerator must be deployed in the source side, close to the backup proxy running the source-side Data Mover Service.

·         The target WAN accelerator must be deployed in the target side, close to the backup proxy running the target-side Data Mover Service.

Deployment Types

Veeam Backup & Replication supports a number of replication scenarios that depend on the location of the target host and the data transport path.

Onsite Replication

If the source host and the target host are located in the same site, you can perform onsite replication.

Onsite replication requires the following replication infrastructure components:

·         Backup proxy. In the onsite replication scenario, the source-side Data Mover Service and the target-side Data Mover Service are started on the same backup proxy. The backup proxy must have access to the backup server, source host, target host and backup repository holding replica metadata.

·         Backup repository for storing replica metadata

Figure 12          Veeam Backup & Replication Components and Data Movement

In the onsite replication scenario, Veeam Backup & Replication does not perform data compression. Replication traffic is transferred uncompressed between the two Data Mover Services started on the same backup proxy.

Offsite Replication

If the source host is located in the primary site and the target host is located in the DR site, you can perform offsite replication.

Offsite replication can run over two data paths:

·         Direct data path

·         Through a pair of WAN accelerators

Direct Data Path

The common requirement for offsite replication is that one Data Mover Service runs in the production site, closer to the source host, and another Data Mover Service runs in the remote DR site, closer to the target host. During backup, the Data Mover Services maintain a stable connection, which allows for uninterrupted operation over the WAN or slow links.

 

Figure 13           Veeam Direct path replication

WAN Accelerators

If you have a high latency WAN link, you can replicate VM data through a pair of WAN accelerators. WAN accelerators provide advanced technologies to optimize VM data transfer:

·         Global data caching and deduplication

·         Resume on disconnect for uninterrupted data transfer

WAN accelerators add a new layer in the backup infrastructure — a layer between the source-side Data Mover Service and the target-side Data Mover Service. The data flow goes from the source backup proxy via a pair of WAN accelerators to the target backup proxy that, finally, transports VM data to the target host.

 

Figure 14          Veeam Replication through WAN Accelerators

Failover and Failback

In case of software or hardware malfunction, you can quickly recover a corrupted VM by failing over to its replica. When you perform failover, a replicated VM takes over the role of the original VM. You can fail over to the latest state of a replica or to any of its good known restore points.

In Veeam Backup & Replication, failover is a temporary intermediate step that should be further finalized. Veeam Backup & Replication offers the following options for different disaster recovery scenarios:

·         You can perform permanent failover to leave the workload on the target host and let the replica VM act as the original VM. Permanent failover is suitable if the source and target hosts are nearly equal in terms of resources and are located on the same HA site.

·         You can perform failback to recover the original VM on the source host or in a new location. Failback is used in case you failed over to a DR site that is not intended for continuous operations and would like to move the operations back to the production site when the consequences of a disaster are eliminated.

Veeam Backup & Replication supports failover and failback operations for one VM and for several VMs. In case one or several hosts fail, you can use failover plans to restore operations with minimum downtime.

Failover-Plans

If you have a number of VMs running interdependent applications, you need to failover them one by one, as a group. To do this automatically, you can prepare a failover plan.

In a failover plan, you set the order in which VMs must be processed and time delays for VMs. The time delay is an interval of time for which Veeam Backup & Replication must wait before starting the failover operation for the next VM in the list. It helps to ensure that some VMs, such as a DNS server, are already running at the time the dependent VMs start. The failover plan must be created in advance. In case the primary VM group goes offline, you can start the corresponding failover plan manually. When you start the procedure, you can choose to fail over to the latest state of a VM replica or to any of its good known restore points.

Planned Failover

If you know that your primary VMs are about to go offline, you can proactively switch the workload to their replicas. A planned failover is smooth manual switching from a primary VM to its replica with minimum interrupting in operation. You can use the planned failover, for example, if you plan to perform datacenter migration, maintenance or software upgrade of the primary VMs. You can also perform planned failover if you have an advance notice of a disaster approaching that will require taking the primary servers offline.

Failback

If you want to resume operation of a production VM, you can fail back to it from a VM replica. When you perform failback, you get back from the VM replica to the original VM, shift your I/O and processes from the target host to the production host and return to the normal operation mode.

If you managed to restore operation of the source host, you can switch from the VM replica to the original VM on the source host. If the source host is not available, you can restore the original VM to a new location and switch back to it.

Backup Server

Components

Veeam Availability Suite combines the backup, restore and replication capabilities of Veeam Backup & Replication™ with the advanced monitoring, reporting and capacity planning functionality of Veeam ONE™. Veeam Availability Suite delivers everything you need to reliably protect and manage your Cisco HyperFlex VMware environment. Veeam Backup & Replication is a modular solution that lets you build a scalable backup infrastructure for environments of different sizes and configuration. The installation package of Veeam Backup & Replication includes a set of components that you can use to configure the backup infrastructure. Some components are mandatory and provide core functionality; some components are optional and can be installed to provide additional functionality for your business and deployment needs. You can co-install all Veeam Backup & Replication components on the same machine, physical or virtual, or you can set them up separately for a more scalable approach.

Figure 15 shows an overview on the main Veeam components.

 

Figure 15           Veeam Backup & Replication Components

Backup Server

The backup server is a Windows-based physical or virtual machine on which Veeam Backup & Replication is installed. It is the core component in the backup infrastructure that fills the role of the “configuration and control center”. The backup server performs all types of administrative activities:

·         Coordinates backup, replication, recovery verification and restore tasks

·         Controls job scheduling and resource allocation

·         Manages all Proxy and Repository servers and other components of the backup infrastructure

The backup server is used to set up and manage backup infrastructure components as well as specify global settings for the backup infrastructure.

Figure 16          Veeam Backup Server Management

In addition to its primary functions, a newly deployed backup server also performs the roles of the default backup proxy and the backup repository.

The backup server uses the following services and components:

·         Veeam Backup Service is a Windows service that coordinates all operations performed by Veeam Backup & Replication such as backup, replication, recovery verification and restore tasks. The Veeam Backup Service runs under the Local System account or account that has the Local Administrator permissions on the backup server.

·         Veeam Backup Shell provides the application user interface and allows user access to the application's functionality.

·         Veeam Guest Catalog Service is a Windows service that manages guest OS file system indexing for VMs and replicates system index data files to enable search through guest OS files. Index data is stored in the Veeam Backup Catalog — a folder on the backup server. The Veeam Guest Catalog Service running on the backup server works in conjunction with search components installed on Veeam Backup Enterprise Manager and (optionally) a dedicated Microsoft Search Server.

·         Veeam Backup SQL Database is used by Veeam Backup Service, Veeam Backup Shell and Veeam Guest Catalog Service to store data about the backup infrastructure, jobs, sessions and so on. The database instance can be located on a SQL Server installed either locally (on the same machine where the backup server is running) or remotely.

·         Veeam Backup PowerShell Snap-In is an extension for Microsoft Windows PowerShell 2.0. Veeam Backup PowerShell adds a set of cmdlets to allow users to perform backup, replication and recovery tasks through the command-line interface of PowerShell or run custom scripts to fully automate operation of Veeam Backup & Replication.

·         Backup Proxy Services. In addition to dedicated services, the backup server runs a set of data mover services.

Backup Proxy

The backup proxy is an architecture component that sits between data source and target and is used to process jobs and deliver backup traffic. In particular, the backup proxy tasks include retrieving VM data from the production storage, compressing, deduplicating and sending it to the backup repository (for example, if you run a backup job) or another backup proxy (for example, if you run a replication job). As the data handling task is assigned to the backup proxy, the backup server becomes the “point of control” for dispatching jobs to proxy servers.

The role of a backup proxy can be assigned to a dedicated Windows server (physical or virtual) in your environment. You can deploy backup proxies both in the primary site and in remote sites. To optimize performance of several concurrent jobs, you can use a number of backup proxies. In this case, Veeam Backup & Replication will distribute the backup workload between available backup proxies.

 

Figure 17           Veeam Distributed Proxy Server Deployment

Use of backup proxies lets you easily scale your backup infrastructure up and down based on your demands. Backup proxies run light-weight services that take a few seconds to deploy. The primary role of the backup proxy is to provide an optimal route for backup traffic and enable efficient data transfer.

The backup proxy uses the following services and components:

·         Veeam Installer Service is an auxiliary service that is installed and started on any Windows server once it is added to the list of managed servers in the Veeam Backup & Replication console. This service analyses the system, installs and upgrades necessary components and services depending on the role selected for the server.

·         Veeam Data Mover Service is responsible for deploying and coordinating executable modules that act as "data movers" and perform main job activities on behalf of Veeam Backup & Replication, such as communicating with VMware Tools, copying VM files, performing data deduplication and compression and so on.

Backup Repository

A backup repository is a location used by Veeam Backup & Replication jobs to store backup files, copies of VMs and metadata for replicated VMs. By assigning different repositories to jobs and limiting the number of parallel jobs for each one, you can balance the load across your backup infrastructure.

You can configure one of the following types of backup repositories:

·         Microsoft Windows server with local or directly attached storage. The storage can be a local disk, directly attached disk-based storage (such as a USB hard drive), or iSCSI/FC SAN LUN in case the server is connected into the SAN fabric.

·         Linux server with local, directly attached storage or mounted NFS. The storage can be a local disk, directly attached disk-based storage (such as a USB hard drive), NFS share, or iSCSI/FC SAN LUN in case the server is connected into the SAN fabric.

·         CIFS (SMB) share. SMB share cannot host Veeam Data Mover Services. For this reason, data to the SMB share is written from the gateway server. By default, this role performed by a backup proxy that is used by the job for data transport.

·         Deduplicating storage appliance. Veeam Backup & Replication supports different deduplicating storage appliances.

Backup & Replication Console

The Veeam Backup & Replication console is a separate client-side component that provides access to the backup server. The console is installed locally on the backup server by default. You can also use it in a standalone mode — install the console on a dedicated machine and access Veeam Backup & Replication remotely over the network. The console lets you log into Veeam Backup & Replication and perform all kinds of data protection and disaster recovery operations as if you are working on the backup server.

Figure 18          Veeam Backup & Replication Console

You can install as many remote consoles as you need so that multiple users can access Veeam Backup & Replication simultaneously. Veeam Backup & Replication prevents concurrent modifications on the backup server.

Backup Proxy

Transport Modes

Job efficiency and time required for job completion greatly depends on the transport mode. The transport mode is a method that is used by the Veeam Data Mover Service to retrieve VM data from the source and write VM data to the target.

For data retrieval, Veeam Backup & Replication offers the following modes:

·         Direct storage access

·         Virtual appliance

·         Network

Figure 19          Veeam Backup & Replication Transport Modes

In the Direct storage access mode, Veeam Backup & Replication reads/writes data directly from/to the storage system where VM data or backups are located. With the Direct NFS access mode for Cisco HyperFlex, Veeam Backup & Replication bypasses the ESX(i) host and reads/writes data directly from/to NFS datastores. To do this, Veeam Backup & Replication deploys its native NFS client on the backup proxy and uses it for VM data transport. VM data still travels over the LAN but there is no load on the ESX(i) host.

The Virtual appliance mode is recommended if the role of a backup proxy is assigned to a VM. In the Virtual appliance mode, Veeam Backup & Replication uses the VMware SCSI HotAdd capability that allows attaching devices to a VM while the VM is running. During backup, replication or restore disks of the processed VM are attached to the backup proxy. VM data is retrieved or written directly from/to the datastore, instead of going through the network.

The Network mode can be used with any infrastructure configuration. In this mode, data is retrieved via the ESX(i) host over the LAN using the Network Block Device protocol (NBD). The Network mode is the recommended data transport mode to be used with Cisco HyperFlex in combination with Native HX Snapshots. To take the full advantage of the mode a 10Gbit/s Ethernet is mandatory.

Veeam Repository Sizing

When estimating the amount of required disk space, you should know the following:

·         Number of backup VMs

·         Total size of VMs and the data change rate

·         Frequency of backups

·         Retention period for backups

·         Will jobs use forward or reverse incremental

·         Frequency of active and synthetic fulls

Also, when testing is not possible beforehand, you should make assumptions on compression and deduplication ratios, change rates, and other factors. The following figures are typical for most deployments; however, it is important to understand the specific environment to find out possible exceptions:

·         Data reduction thanks to Compression and Deduplication is usually 2:1 or more; it is common to see 3:1 or better, but you should always be conservative when estimating required space.

·         Typical daily change rate is between 2 and 5% in a mid-size or enterprise environment; this can greatly vary among servers; some servers show much higher values. If possible, run monitoring tools like Veeam ONE to have a better understanding of the real change rate values.

·         Include additional space for one-off full backups.

·         Include additional space for backup chain transformation (forward forever incremental, reverse incremental) – at least the size of a full backup multiplied by 1.25x.

·         Using the numbers above, you can estimate required disk space for any job. Besides, always leave plenty of extra headroom for future growth, additional full backups, moving VMs, restoring VMs from tape.

Data Protection for Cisco HyperFlex with Veeam Availability Suite is designed to deliver reliable backup and recovery solution with low recovery time objectives (RTOs) and recovery point objectives (RPOs) for all applications and data residing in virtual machines within the HyperFlex environment.

In addition to reliable backup and recovery of application data and VMs the solution provides the following:

·         Granular recovery of virtual machines and files

·         Ability to automatically verify every backup, VM and replica

·         Instant VM recovery of failed VM in less than two minutes

·         Multiple backup end points such as tape drives, on cloud or on local repository  

·         SureBackup and SureReplica for Backup and Replication verification

·         Storage Integration of Cisco HyperFlex with Veeam Backup & Replication

This section elaborates on the deployment architecture and design considerations to protect application data through Veeam Availability Suite. The application VMs can reside, across multiple HyperFlex across Data Centers  or HyperFlex Clusters deployed in a Remote Office Branch Office (ROBO)

The key deployment scenarios to protect Cisco HyperFlex cluster with Veeam Availability Suite are listed as below

·         Cisco HyperFlex Single Site Backup and Replication

·         Cisco HyperFlex Remote office - Branch Office Replication

·         Cisco HyperFlex multisite Backup and Replication

Figure 20 illustrates the end-to-end deployment scenarios for Cisco HyperFlex with Veeam Availability Suite.

 

Figure 20          Deployment Overview: Multisite and Remote Office deployment of Cisco HyperFlex with Veeam Availability Suite

Remote Office - Branch Office Replication for Cisco HyperFlex

Several organizations today have Remote office and Branch offices (ROBO) spread across geographies, which provide localized data availability and allow businesses to execute critical workloads locally. ROBO deployments typically require fewer compute and storage resources with just few servers running workloads to support local needs. Organizations have several ROBO deployments spread across regions and a major challenge faced by these deployments is provisioning of application availability, deployed remotely.

The present design overcomes these challenges, by providing Replication of application VMs deployment in Remote Offices through Veeam Availability Suite. Application VMs in ROBO deployments are replicated to the primary Data Center and hence provide Failover and Fail Back at all times. This requires minimal infrastructure requirements and the replication is executed by Veeam Proxy installed just in a Virtual Machine. Moreover, it allows ensuring remote sites are in compliance, and reducing IT management time at remote offices.

 The key deployment features of ROBO Replication for Cisco HyperFlex are:

·         Veeam Application Server, Veeam Proxy and Veeam Repository reside on either Cisco UCS S3260 or Cisco UCS C240 M4 server located in the Primary Data Center.

·         Backup of HyperFlex Cluster VMs in Primary Data Center through Veeam Proxy and Veeam Backup Server.

·         Replication of application VMs on Cisco HyperFlex Cluster located in Remote Office is executed on Veeam Availability Suite located in Primary Data Center.

·         A Veeam Proxy Server is installed in the Remote Office. This could be installed either on a bare metal server or on a Virtual Machine. In present design, Veeam Proxy Server is installed in a Cisco UCS C240 M4 Server located in Remote Office. The choice of either a virtual machine or physical server for Veeam Proxy is dependent on several factors such as:

-        Number of Replication jobs executed on ROBO deployment.

-        Deployment of Veeam WAN Accelerator on the Remote Site. Customers can deploy Veeam WAN Accelerator, which allows faster replication and backup of application VMs. It is required to deploy Veeam WAN Accelerator on a Cisco UCS C240 M4 LFF with SSDs for WAN Accelerator Cache. 

Figure 21 illustrates the use case for Replication of application VM on ROBO site to the Primary Data Center.

Figure 21          Remote Office - Branch Office Replication for Cisco HyperFlex

Deployment Architecture

This section elaborates on the reference architecture for Veeam AS with Cisco HyperFlex exiting in Remote Office locations. Figure 22 details the physical topology of the present deployment.

 

Figure 22          Deployment Architecture: Remote Office Branch Office Replication for Cisco HyperFlex

The solution detailed in the figure above includes Primary HyperFlex Cluster and Hyper Flex Cluster deployed in Remote Office. The application VMs are replicated through Veeam Availability Suite on Cisco UCS S3260 Storage server located in the Primary Data Center.

The details on the deployment are as follows:

·         Primary HyperFlex Cluster

·         Veeam Application Suite 9.5 Update 2 deployed on Cisco UCS S3260 Storage Server. This includes Veeam Repository, Veeam Backup Server and the Veeam Proxy Server.

·         Cisco UCS S3260 Storage Server is directly attached to a pair of Cisco UCS 6200 Series Fabric Interconnects (FI)

·         Cisco HX Cluster with Cisco HX Data Platform 2.5 (1b) and VMWare Hypervisor 6.0 update 3. This is the primary HX Cluster wherein the application VMs reside.

·         Cisco HX Cluster and Cisco UCS S3260 Storage server are connected to the same pair of Fabric Interconnects

·         The backup of the application VMs are created on UCS S3260 repository through Veeam AS

·         Cisco Nexus 9300 switches

·         Remote Office Branch Office deployment (ROBO)

·         Cisco HX Cluster with Cisco HX Data Platform 2.5 (1b) and VMWare Hypervisor 6.0 update 3. This cluster provisions application VMs deployed in Remote Office location. 

·         Replication of the application VM on Remote Office are created on HX Cluster located in Primary Data Center

·         Cisco UCS 6200 Series Fabric Interconnects

·         Veeam Proxy Server and Veeam WAN Accelerator are deployed on Cisco UCS C240 M4 LFF Rack Server. As mentioned, Veeam Proxy Server can be deployed on a VM, but it is recommended to have Veeam Proxy Server deployed on a bare metal server

Multisite Backup and Replication for Cisco HyperFlex

Multisite Backup and Replication comprises of distributed deployment scenarios for large geographically dispersed virtual environments with multiple backup servers installed across different sites. These backup servers can be federated under Veeam Backup Enterprise Manager; an optional component that provides centralized management and reporting for these servers through a web interface. Veeam Availability Suite for large multi-site Data Centers allows customers to more efficiently execute VM Backup Copy jobs across the WAN network.

The key deployment features for Multisite Backup and Replication for Cisco HyperFlex are:

·         Application VMs residing either on the Primary Data Center or on Remote Data Centers are backed up and replicated through Veeam Availability Suite deployed on Cisco S3260 Storage Server

·         The distributed deployment environment is spread across geographies and can be managed through Veeam Backup Enterprise Manager — an optional component that provides centralized management and reporting for distributed Veeam Backup servers through a web interface

·         The backup repository is replicated from remote Data Center repository to Primary Data Center repository through Veeam Availability Suite utilizing Veeam backup copy jobs

·         Application VMs can be replicated either to HyperFlex cluster within the same Data Center or to HyperFlex cluster in the Primary Data Center.

·         Backup Copy jobs can be executed across S3260 storage server. This allows high availability of backups during backup server failures in either of the Data Center.

·         Veeam WAN Accelerators are deployed in Primary and Remote sites, which reduce the amount of data that needs to flow back and forth across the WAN by using caching and data compression techniques. This allows reduction in the bandwidth required for transferring backups and replicas over the WAN. Built-in WAN Acceleration dramatically reduces the bandwidth required for transferring backups and replicas over the WAN. A WAN accelerator reduces the amount of data that needs to flow back and forth across by caching duplicate files (or parts of files) so they can be referenced in global cache instead of having to be sent across the WAN again

Figure 23 illustrates the key uses cases for Backup and Replication for application VMs residing in multisite HyperFlex deployment.

Figure 23          Multisite Backup and Replication for Cisco HyperFlex

 

Deployment Architecture

This section describes the reference architecture for Veeam AS with in a multisite Cisco Hyper Flex deployment. Figure 24 details the reference architecture.

 

Figure 24          Deployment Architecture: Multisite backup and replication for Cisco HyperFlex

The solution detailed in the figure above includes Primary and Remote Data Centers running virtualized applications on either Converged Infrastructure or Cisco HyperFlex Clusters. This deployment supports a combination of Converged and Cisco Hyper Flex Data Clusters with replication and backup on Cisco UCS S3260 Storage Server.

The infrastructure components remain same for both Primary and Remote Data Center. The details about the key infrastructure components deployed to validate this setup are as follows:

·         Veeam Availability Suite 9.5 Update 2 is deployed on Cisco UCS S3260 Storage Server. This includes Veeam Repository as the primary repository for all backup jobs across distributed data centers. Veeam Repository and Veeam Backup Server are installed on Cisco UCS S3260 servers.

·         Veeam Proxy Server and Veeam WAN Accelerator are deployed on a separate Cisco UCS C220 M4 server.

·         Cisco HX Cluster with Cisco HX Data Platform 2.5 (1b) and VMWare Hypervisor 6.0 update 3. This is the primary HX Cluster wherein all the application VMs reside.

·         Cisco HX Cluster and Cisco UCS S3260 Storage server are connected to the same pair of Fabric Interconnects

·         The backup of the application VMs are created on Cisco UCS S3260 repository through Veeam AS

·         Application VMs are replicated either to standalone ESXI Cluster or the Secondary HX Cluster residing in the same Data Center or Campus

·         Cisco Nexus 9300 switches

 

 

This section elaborates on the design considerations for Backup and Replication of Application VM on HyperFlex with Veeam Availability Suite and Cisco S3260 Storage Server

Unified Management

Cisco UCS Manager can manage B-series blade servers, C-series rack servers and S3260 Stroage Servers under the same Cisco UCS domain. This feature, along with stateless computing makes compute resources truly hardware agnostic.

Moreover, Cisco UCS Central Software extends the policy-based functions and concepts of Cisco UCS Manager across multiple Cisco Unified Computing System (Cisco UCS) domains in one or more physical locations. This allows hardware configuration from a single UCS Central window, across multiple UCS domains, either in same Data Center or across Data Centers.

Cisco Unified Computing System™ (Cisco UCS) management helps significantly reduce management and administration expenses by automating routine tasks to increase operational agility. Cisco UCS management provides enhanced storage management functions for the Cisco UCS S3260 and all Cisco UCS servers. Cisco UCS Manager supports Storage profiles give you flexibility in defining the number of storage disks and the roles and uses of these disks and other storage parameters.

Figure below, elaborates om the single management window through UCS Central.

Figure 25          Unified Management across Data Centers

 

Network

The network design is shown in the figure below.

Figure 26          Network Design for Primary Data Center

The LAN network provides network reachability to the applications hosted on Cisco UCS servers in the data center. The infrastructure consists of a pair of Cisco Nexus 9372 PX switches deployed in NX-OS standalone mode. Redundant 10Gbps links from each Cisco Nexus switch are connected to ports on each FI and provide 20Gbps of bandwidth through each Cisco Nexus. Virtual PortChannels (vPCs) are used on the Cisco Nexus links going to each FI. Jumbo Frames are also enabled in the LAN network to support backup and replication of application VMs on Veeam Server.

The design also uses the following best practices:

·         Jumbo frames on unified fabric links between Cisco UCS and fabric interconnects

·         QoS policy for traffic prioritization on the unified fabric

·         Port-channels with multiple links are used in the unified fabric for higher aggregate bandwidth and redundancy

The Veeam AS is deployed on Cisco UCS 3260 Storage Server and provides an aggregated bandwidth of 80 Gbps for VM backup and Replication. The present deployment supports Veeam AS on Cisco UCS C240 M4 LFF server connected to common pair of Fabric interconnects and provides network throughput of up to 40 Gbps.

WAN Acceleration for Backup and Replica

Remote Site Backup and Replication always involves moving large volumes of data between remote sites. The most common problems that backup administrators encounter during Remote Site Backup and Replication are:

·         Insufficient network bandwidth to support VM data traffic

·         Transmission of redundant data

Veeam Backup and Replication offers the WAN acceleration technology that helps optimize data transfer over WAN. Built-in WAN Acceleration utilizes global caching, variable block length data fingerprinting and traffic compression to significantly reduce bandwidth requirements, while multiple WAN optimization ensures that available bandwidth is leveraged to its fullest potential.

Figure below elaborates on the WAN Acceleration for faster Backup and Replication jobs across distributed Data Centers.

Figure 27          WAN Accelerators on Backup Infrastructure

In the present design, Veeam WAN Acceleration is utilized for Remote Site Backup and Replication. It is recommended to have a caching layer such as SSD to create global cache across the Primary and Remote Site; WAN Accelerator is installed on a Cisco UCS S3260 Storage Server.  

Veeam Backup Enterprise Manager Console

Veeam Enterprise Manager is intended for centralized reporting and management of multiple backup servers. It provides delegated restore and self-service capabilities as well as the ability for users to request Virtual Labs from backup administrators. It provides a central management point for multiple backup servers from a single interface. Enterprise Manager is also a part of the data encryption and decryption processes implemented in the Veeam solution. For best practices, Veeam recommends deploying Enterprise Manager in the following scenarios:

·         It is recommended to deploy Enterprise Manager if you are using encryption for backup or backup copy jobs. If you have enabled password loss protection (http://helpcenter.veeam.com/backup/em/index.html?em_manage_keys.html) for the connected backup servers backup files will be encrypted with an additional private key which is unique for each instance of Enterprise Manager. This will allow Enterprise Manager administrators to unlock backup files using a challenge/response mechanism effectively acting as a Public Key Infrastructure (PKI).

·         If an organization has Remote Office/Branch Office (ROBO) deployments, then leverage Enterprise Manager to provide site administrators with granular restore access via web UI (rather than providing access to the Backup and Replication console).

·         In enterprise deployments, delegation capabilities can be used to elevate the first line support to perform in-place restores without administrative access.

·         For deployments spanning multiple locations with stand-alone instances of Veeam Backup and Replication, Veeam Enterprise Manager will be helpful in managing licenses across these instances to ensure compliance.

·         Enterprise Manager is required when automation is essential to delivering IT services — to provide access to the Veeam RESTful API.

Veeam Transport Mode for HX Cluster

The best practice is to utilize the HyperFlex and Veeam Storage integration which enables VMware vSphere ESXi hosts to communicate with storage devices and offload storage operations such as snapshot creation and cloning to the HyperFlex storage controller. This allows space efficient and nearly instant snapshots without performance impact.

Customers can allow Veeam Backup & Replication to read data from Cisco HyperFlex snapshots in the following transport modes

·         Direct Storage access

·         Virtual appliance

·         Network.

The recommended mode is Direct Storage access which uses the NFS protocol to directly connect to the HyperFlex data store. It provides the best performance and the lowest overhead on ESXi hosts. In this mode, Veeam Backup & Replication bypasses the ESXi host and reads/writes data directly from/to the HyperFlex data store over the “Storage Controller Data Network”.

The present design utilizes Veeam and HyperFlex Stroage Integration feature. The validation of Backup with Direct Storage Access is detailed in section Backup VM on HX Cluster with HyperFlex and Veeam Storage Integration.

For Further details on implementation of HyperFlex and Veeam Integration, refer to  Cisco HyperFlex Data Platform Backup Integration Guide.

 

Veeam Proxy Server Distribution

This section elaborates on the recommendations for placement of Veeam proxy servers across Remote Offices and multi site for backup and replication jobs. Customers should be cautious on selecting a Veeam Proxy as a virtual or baremetal, as having several virtual proxies on a single site may lead to excessive Windows licensing and high manageability cost but may provide high availability of backup and replication jobs  as compared to a single baremetal server proxy. Veeam proxy deployed in a physical sever would provide several physical cores for parallel processing of Backup and Replication jobs , few  Veeam proxies to manage, less Windows licensing cost but in the event of failed single server proxy, it would lead to single point of failure.

Proxy Distribution for HyperFlex ROBO Replication

Veeam Backup and Replication provides replication of application VM on HyperFlex Cluster deployed on a Remote Office to the Primary HyperFlex Cluster. The Solution Design is elaborated in the previous section Remote Office - Branch Office Replication for Cisco HyperFlex.

In this design the Veeam Proxy Server can be selected as a virtual proxy or a baremtal proxy. Customer should consider following recommendations for the Veema proxy Selection.

·         In the event , customers want to utilize Veeam WAN accelarators , it is recommended to have a Veeam Proxy as a baremetal C240 M4 LFF server. This allows caching tier through the boot SSDs on the server. The replication job does require minimal local storage , hence The C240 M4 LFF server for Replication is equipped with two 4 TB SATA drives.

·         With the selection of Bare metal Proxy on Remote Site,  customers can  enable local Backups on the Remote Office ,C240 M4 LFF server can be expanded upto 12 X 6 TB SATA drives which provides optimum storage for Remote Office Backups. Pls note, to protect the Backups on Remote Office, customers should execute Backup Copy jobs to the Primary Data Center, thus allowing restoration of application VM on the primary Data Center.

·         With several Remotes offices and very few VMs on each office being replicated to the Pirmary Site, customers can choose to have a virtual proxy deployed on the HX Cluster. Administrators should be cautious on the utilization of HX Cluster by application VMs. The performance of replication jobs may degrade during high utilization of HX Cluster by application workloads.

The validation for the Replication of Remote Office HyperFlex deployed with baremetal proxy is detailed in section Remote Office / Branch Office VM Replication.

Proxy Distribution for Multisite HyperFlex Deployments

Veeam Backup and Replication provides backup replication of application VM on HyperFlex Cluster deployed on a HyperFlex Cluster deployed across Data Centers. The Solution Design is elaborated in the previous section Multisite Backup and Replication for Cisco HyperFlex.

In this deployment, each of the Veeam Backup servers across the data center are deployed on a physical Cisco UCS C240 M4 LFF or S3260 Storage server. The Veeam Proxy is deployed on the same backup server. Some of the important design consideration for the location of Veeam Proxy in multisite HyperfFlex deployments are

·         Backup through Veeam for application VM residing on HyperFlex cluster utilizes Veeam and HyperFlex Storage Integration which enables HX native snapshot and backup through HyperFlex storage network. This provides offloading of overhead for snapshot from ESXi Host to HyperFlex Storage Controler. It also enables distribution of Backup traffic to each of HyperFlex storage networks on ESXi nodes. One of the requirements for this feature is Veeam Proxy should have access to private HyperFlex Storage network.

·         In cases where the Proxy Server is connected to the same Fabric Interconnect of HyperFlex Cluster, customers can easily create vNIC on Proxy server which has same VLAN as that of the HyperFlex Storage Network. The configuration details are describes in section Cisco UCS S3260 Configuration. The selection of proxy and Backup server on same baremetal server, connected to Fabric Interconnect of HyperFlex Cluster allows ease of deployment, scalability of parallel backup with up to 36 jobs (maximum number of physical cores on Cisco UCS C240 M4 LFF) and faster backup time, as having Backup and Proxy server on same physical server, allows minimal latencies between proxy and Backup Server.

·         For scenarios where Veeam Proxy is unable to access the HyperFlex Storage network, Veeam will fall back to the VMWare REDO log based snapshots. To avoid this, make sure that the first snapshot of VM is a HX native snapshot. Customers can easily add all the application VMs to a VM folder and execute a HX based snapshot with a single-click through HX Plugin for VSphere web client. The process is illustrated in Figure 28.

 

Figure 28          Adding Application Virtual Machines to a VM Folder and Execute a Cisco HX Data Platform Snapshot Now

The validation of Backup and Replication for application VMs in multisite HyperFlex deployments are detailed in section Backup VM on HX Cluster with HyperFlex and Veeam Storage Integration.

Veeam Backup Copy Jobs

You should protect your backups on either the Primary data center or Remote data center through Veeam Backup Copy jobs, executed across backup locations. In this design, Backup Copy jobs are executed across two data centers, making sure you can always restore your backups during  complete failure of backups in either of the data centers.

·         See section Backup Copy Jobs Across Data Centers for Backup copy job configuration and validation details.

·         The configuration and validation of restoration of Backup copies during failure of either Data Center is detailed in section Restore Backup Copy Job VM to DR Site.

Table 1  lists the software revisions used throughout this document.

Software Versions

Table 1     Software Revisions

Configuration Guidelines

This CVD provides the details to configure a Cisco UCS S3260 Storage Server setup with Veeam 9.5, providing backup, restore and replication of a VM deployed in a Cisco HyperFlex infrastructure.  

Figure 29 illustrates the high-level procedures and steps for this installation.

Figure 29          Installation Workflow

Cisco Nexus A and Cisco Nexus B identifies the pair of Cisco Nexus switches that are configured. The Cisco UCS Fabric Interconnects are similarly configured. Additionally, this document details the steps for provisioning.

To indicate that you should include information pertinent to your environment in a given step, <text> appears as part of the command structure. See the following example for the network port vlan create command:

Usage:

Example:

Table 2 describes the VLANs necessary for deployment as outlined in this guide. Table 3 lists the configuration variables that are used throughout this document. This table can be completed based on the specific site variables and used in implementing the document configuration steps.

Table 2     Necessary VLANs

Table 3     Configuration Variables

This section provides detailed steps to configure the Cisco Nexus 9000s to use in a Veeam environment.

For detailed configuration details, refer to Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide.

Physical Connectivity

Follow the physical connectivity guidelines as covered in section Deployment Architecture.

Cisco Nexus Base

This section describes how to configure the Cisco Nexus switches to use in a base Veeam environment.  This procedure assumes that you are using Cisco Nexus 9000 7.0(3)I4(2).

Set Up Initial Configuration

Cisco Nexus 9372PX A

To set up the initial configuration for the Cisco Nexus A switch on <<var_nexus_A_hostname>>, complete the following steps:

Configure the Switch

1.       Abort Power on Auto Provisioning and continue with normal setup? (yes/no) [n]: yes

2.       Do you want to enforce secure password standard (yes/no): yes

3.       Enter the password for "admin": <<var_password>>

4.       Confirm the password for "admin": <<var_password>>

5.       Would you like to enter the basic configuration dialog (yes/no): yes

6.       Create another login account (yes/no) [n]: Enter

7.       Configure read-only SNMP community string (yes/no) [n]: Enter

8.       Configure read-write SNMP community string (yes/no) [n]: Enter

9.       Enter the switch name: <<var_nexus_A_hostname>>

10.    Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: Enter

11.    Mgmt0 IPv4 address: <<var_nexus_A_mgmt0_ip>>

12.    Mgmt0 IPv4 netmask: <<var_nexus_A_mgmt0_netmask>>

13.    Configure the default gateway? (yes/no) [y]: Enter

14.    IPv4 address of the default gateway: <<var_nexus_A_mgmt0_gw>>

15.    Configure advanced IP options? (yes/no) [n]: Enter

16.    Enable the telnet service? (yes/no) [n]: Enter

17.    Enable the ssh service? (yes/no) [y]: Enter

18.    Type of ssh key you would like to generate (dsa/rsa) [rsa]: Enter

19.    Number of rsa key bits <1024-2048> [1024]: Enter

20.   Configure the ntp server? (yes/no) [n]: y

21.    NTP server IPv4 address: <<var_global_ntp_server_ip>>

22.   Configure default interface layer (L3/L2) [L2]: Enter

23.    Configure default switchport interface state (shut/noshut) [noshut]: shut

24.   Configure CoPP system profile (strict/moderate/lenient/dense/skip) [strict]: Enter

25.     Would you like to edit the configuration? (yes/no) [n]: Enter

26.   Review the configuration summary before enabling the configuration.

27.    Use this configuration and save it? (yes/no) [y]: Enter

Cisco Nexus 9372PX B

To set up the initial configuration for the Cisco Nexus B switch on <<var_nexus_B_hostname>>, complete the following steps:

Configure the Switch

1.       Abort Power on Auto Provisioning and continue with normal setup? (yes/no) [n]: yes

2.       Do you want to enforce secure password standard (yes/no): yes

3.       Enter the password for "admin": <<var_password>>

4.       Confirm the password for "admin": <<var_password>>

5.       Would you like to enter the basic configuration dialog (yes/no): yes

6.       Create another login account (yes/no) [n]: Enter

7.       Configure read-only SNMP community string (yes/no) [n]: Enter

8.       Configure read-write SNMP community string (yes/no) [n]: Enter

9.       Enter the switch name: <<var_nexus_B_hostname>>

10.    Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: Enter

11.    Mgmt0 IPv4 address: <<var_nexus_B_mgmt0_ip>>

12.    Mgmt0 IPv4 netmask: <<var_nexus_B_mgmt0_netmask>>

13.    Configure the default gateway? (yes/no) [y]: Enter

14.    IPv4 address of the default gateway: <<var_nexus_B_mgmt0_gw>>

15.    Configure advanced IP options? (yes/no) [n]: Enter

16.    Enable the telnet service? (yes/no) [n]: Enter

17.    Enable the ssh service? (yes/no) [y]: Enter

18.    Type of ssh key you would like to generate (dsa/rsa) [rsa]: Enter

19.    Number of rsa key bits <1024-2048> [1024]: Enter

20.   Configure the ntp server? (yes/no) [n]: y

21.    NTP server IPv4 address: <<var_global_ntp_server_ip>>

22.   Configure default interface layer (L3/L2) [L2]: Enter

23.    Configure default switchport interface state (shut/noshut) [noshut]: shut

24.   Configure CoPP system profile (strict/moderate/lenient/dense/skip) [strict]: Enter

25.    Would you like to edit the configuration? (yes/no) [n]: Enter

26.   Review the configuration summary before enabling the configuration.

27.    Use this configuration and save it? (yes/no) [y]: Enter

Cisco Nexus Switch Configuration

Enable Licenses

Cisco Nexus 9372PX A and Cisco Nexus 9372PX B

To license the Cisco Nexus switches, complete the following steps:

1.       Log in as admin.

2.       Run the following commands:

config t

feature interface-vlan

feature lacp

feature vpc

feature lldp

Set Global Configurations

Cisco Nexus 9372PX A and Cisco Nexus 9372PX B

To set global configurations, complete the following step on both switches:

1.       Run the following commands to set global configurations:

spanning-tree port type network default

spanning-tree port type edge bpduguard default

spanning-tree port type edge bpdufilter default

port-channel load-balance src-dst l4port

ntp server <<var_global_ntp_server_ip>> use-vrf management

ntp master 3

ip route 0.0.0.0/0 <<var_ib-mgmt-vlan_gateway>>

copy run start

Create VLANs

Cisco Nexus 9372PX A and Cisco Nexus 9372PX B

To create the necessary virtual local area networks (VLANs), complete the following step on both switches:

1.       From the global configuration mode, run the following commands:

vlan <<var_veeam-network>>

name hx-inband-mgmt

exit

vlan <<native_vlan>>

name Native-VLAN

exit

vlan <<hx-storage-data>>

name hx-storage-data exit

vlan << hx-vm-data>>

name hx-vm-data

exit

vlan << hx-vmotion>>

name hx-vmotion

exit

vlan << Multisite-VLAN>>

name Multisite-VLAN

exit

Add NTP Distribution Interface

Cisco Nexus 9372PX A

1.       From the global configuration mode, run the following commands:

ntp source <<var_switch_a_ntp_ip>>

interface Vlan <<var_ib-mgmt_vlan_id>>

ip address <<var_switch_a_ntp_ip>>/<<var_ib-mgmt_vlan_netmask_length>>

no shutdown

exit

Cisco Nexus 9372PX B

1.       From the global configuration mode, run the following commands:

ntp source <<var_switch_b_ntp_ip>>

interface Vlan<<var_ib-mgmt_vlan_id>>

ip address <<var_switch_ib_ntp_ip>>/<<var_ib-mgmt_vlan_netmask_length>>

no shutdown

exit

Create Port Channels

Cisco Nexus 9372PX A and Cisco Nexus 9372PX B

To create the necessary port channels between devices, complete the following step on both switches:

1.       From the global configuration mode, run the following commands:

interface Po10

description vPC peer-link

exit

interface Eth1/51-52

channel-group 10 mode active

no shutdown

exit

interface Po13

description <<var_ucs_6248_clustername>>-a

exit

interface Eth1/25

channel-group 13 mode active

no shutdown

exit

interface Po14

description <<var_ucs_6248_clustername>>-b

exit

interface Eth1/26

channel-group 14 mode active

no shutdown

exit

copy run start

Configure Port Channel Parameters

Cisco Nexus 9372PX A and Cisco Nexus 9372PX B

To configure port channel parameters, complete the following step on both switches:

1.       From the global configuration mode, run the following commands:

interface Po10

switchport mode trunk

switchport trunk native vlan 2

switchport trunk allowed vlan << var_veeam-network >>

spanning-tree port type network

exit

interface Po13

switchport mode trunk

switchport trunk native vlan 2

switchport trunk allowed vlan << var_veeam-network

spanning-tree port type edge trunk

mtu 9216

exit

interface Po14

switchport mode trunk

switchport trunk native vlan 2

switchport trunk allowed vlan << var_veeam-network

spanning-tree port type edge trunk

mtu 9216

exit

copy run start

Configure Virtual Port Channels

Cisco Nexus 9372PX A

To configure virtual port channels (vPCs) for switch A, complete the following step:

1.       From the global configuration mode, run the following commands:

vpc domain <<var_nexus_vpc_domain_id>>

role priority 10

peer-keepalive destination <<var_nexus_B_mgmt0_ip>> source <<var_nexus_A_mgmt0_ip>>

peer-switch

peer-gateway

auto-recovery

delay restore 150

exit

interface Po10

vpc peer-link

exit

interface Po13

vpc 13

exit

interface Po14

vpc 14

exit

copy run start

Cisco Nexus 9372PX B

To configure vPCs for switch B, complete the following step:

1.       From the global configuration mode, run the following commands.

vpc domain <<var_nexus_vpc_domain_id>>

role priority 20

peer-keepalive destination <<var_nexus_A_mgmt0_ip>> source <<var_nexus_B_mgmt0_ip>>

peer-switch

peer-gateway

auto-recovery

delay restore 150

exit

interface Po10

vpc peer-link

exit

interface Po13

vpc 13

exit

interface Po14

vpc 14

exit

copy run start

Uplink into Existing Network Infrastructure

Depending on the available network infrastructure, several methods and features can be used to uplink the environment. If an existing Cisco Nexus environment is present, it is recommended to use vPCs to uplink the Cisco Nexus 9372PX switches included in the present environment into the infrastructure. The previously described procedures can be used to create an uplink vPC to the existing environment. Make sure to run copy run start to save the configuration on each switch after the configuration is completed.

Cisco UCS Base Configuration

This deployment details the configuration steps for the Cisco UCS 6248UP Fabric Interconnects (FI) in a design that supports both HyperFlex (HX) Cluster and Cisco UCS S3260 Storage Server. The base configuration of Cisco UCS will remain similar for both Cisco HX and Cisco UCS S3260 Storage Server.  

Perform Initial Setup of Cisco UCS 6248UP Fabric Interconnects

This section describes the steps to configure the Cisco Unified Computing System (Cisco UCS) to use in a HyperFlex environment. These steps are necessary to provision the Cisco HyperFlex and Cisco UCS S3260 Storage Server and should be followed precisely to avoid improper configuration.

Cisco UCS 6248UP Fabric Interconnect A

To configure Fabric Interconnect A, complete the following steps:

1.       Make sure the Fabric Interconnect cabling is properly connected, including the L1 and L2 cluster links, and power the Fabric Interconnects on by inserting the power cords.

2.       Connect to the console port on the first Fabric Interconnect, which will be designated as the A fabric device. Use the supplied Cisco console cable (CAB-CONSOLE-RJ45=), and connect it to a built-in DB9 serial port, or use a USB to DB9 serial port adapter.

3.       Start your terminal emulator software.

4.       Create a connection to the COM port of the computer’s DB9 port, or the USB to serial adapter. Set the terminal emulation to VT100, and the settings to 9600 baud, 8 data bits, no parity, 1 stop bit.

5.       Open the connection just created. You may have to press ENTER to see the first prompt.

6.       Configure the first Fabric Interconnect, using the following example as a guideline:

           ---- Basic System Configuration Dialog ----

 

  This setup utility will guide you through the basic configuration of

  the system. Only minimal configuration including IP connectivity to

  the Fabric interconnect and its clustering mode is performed through these steps.

 

  Type Ctrl-C at any time to abort configuration and reboot system.

  To back track or make modifications to already entered values,

  complete input till end of section and answer no when prompted

  to apply configuration.

 

 

  Enter the configuration method. (console/gui) ? console

 

  Enter the setup mode; setup newly or restore from backup. (setup/restore) ? setup

 

  You have chosen to setup a new Fabric interconnect. Continue? (y/n): y

 

  Enforce strong password? (y/n) [y]: y

 

  Enter the password for "admin":

  Confirm the password for "admin":

 

  Is this Fabric interconnect part of a cluster(select 'no' for standalone)? (yes/no) [n]: yes

 

  Enter the switch fabric (A/B) []: A

 

  Enter the system name:  FI-HX1

 

  Physical Switch Mgmt0 IP address : 10.29.149.98

 

  Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0

 

  IPv4 address of the default gateway : 10.29.149.1

 

  Cluster IPv4 address : 10.29.149.100

 

  Configure the DNS Server IP address? (yes/no) [n]: yes

 

    DNS IP address : 171.70.168.183

 

  Configure the default domain name? (yes/no) [n]: yes

 

    Default domain name : hx1.lab.cisco.com

 

  Join centralized management environment (UCS Central)? (yes/no) [n]: no

 

  Following configurations will be applied:

 

    Switch Fabric=A

    System Name=FI-HX1

    Enforced Strong Password=no

    Physical Switch Mgmt0 IP Address=192.168.20.13

    Physical Switch Mgmt0 IP Netmask=255.255.255.0

    Default Gateway=192.168.20.1

    Ipv6 value=0

    DNS Server=171.70.168.183

    Domain Name=hx1.lab.cisco.com

 

    Cluster Enabled=yes

    Cluster IP Address=12.168.20.15

    NOTE: Cluster IP will be configured only after both Fabric Interconnects are initialized

 

  Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no): yes

  Applying configuration. Please wait.

 

  Configuration file – Ok

Cisco UCS 6248UP Fabric Interconnect B

 

To configure Fabric Interconnect B, complete the following steps:

1.       Connect to the console port on the first Fabric Interconnect, which will be designated as the B fabric device. Use the supplied Cisco console cable (CAB-CONSOLE-RJ45=), and connect it to a built-in DB9 serial port, or use a USB to DB9 serial port adapter.

2.       Start your terminal emulator software.

3.       Create a connection to the COM port of the computer’s DB9 port, or the USB to serial adapter. Set the terminal emulation to VT100, and the settings to 9600 baud, 8 data bits, no parity, 1 stop bit.

4.       Open the connection just created. You may have to press ENTER to see the first prompt.

5.       Configure the second Fabric Interconnect, using the following example as a guideline:

           ---- Basic System Configuration Dialog ----

 

  This setup utility will guide you through the basic configuration of

  the system. Only minimal configuration including IP connectivity to

  the Fabric interconnect and its clustering mode is performed through these steps.

 

  Type Ctrl-C at any time to abort configuration and reboot system.

  To back track or make modifications to already entered values,

  complete input till end of section and answer no when prompted

  to apply configuration.

 

 

  Enter the configuration method. (console/gui) ? console

 

  Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ? y

 

  Enter the admin password of the peer Fabric interconnect:

    Connecting to peer Fabric interconnect... done

    Retrieving config from peer Fabric interconnect... done

    Peer Fabric interconnect Mgmt0 IPv4 Address: 192.168.20.13

    Peer Fabric interconnect Mgmt0 IPv4 Netmask: 255.255.255.0

    Cluster IPv4 address          : 192.168.20.15

 

    Peer FI is IPv4 Cluster enabled. Please Provide Local Fabric Interconnect Mgmt0 IPv4 Address

 

  Physical Switch Mgmt0 IP address : 192.168.20.14

 

 

  Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no): yes

  Applying configuration. Please wait.

 

Configuration file – Ok

Cisco UCS Setup

Log in to Cisco UCS Manager

To log in to the Cisco Unified Computing System (UCS) environment, complete the following steps:

1.       Open a web browser and navigate to the Cisco UCS fabric interconnect cluster address.

2.       Click the Launch UCS Manager link to download the Cisco UCS Manager software.

3.       If prompted to accept security certificates, accept as necessary.

4.       When prompted, enter admin as the user name and enter the administrative password.

5.       Click Login to log in to Cisco UCS Manager.

Upgrade Cisco UCS Manager Software to Version 3.1(3c)

This document assumes you are using Cisco UCS 3.1(3c). To upgrade the Cisco UCS Manager software and the Cisco UCS Fabric Interconnect software to version 3.1(3c), refer to Cisco UCS Manager Install and Upgrade Guides.

Anonymous Reporting

To create anonymous reporting, complete the following step:

1.       In the Anonymous Reporting window, select whether to send anonymous data to Cisco for improving future products:

Add Block IP Addresses for KVM Access

To create a block of IP addresses for in band server Keyboard, Video, Mouse (KVM) access in the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.       Select Pools > root > IP Pools.

3.       Right-click IP Pool ext-mgmt and select Create Block of IPv4 Addresses.

4.       Enter the starting IP address of the block, the number of IP addresses required, and the subnet and gateway information.

5.       Click OK to create.

6.       Click OK in the confirmation message.

Synchronize Cisco UCS to NTP

To synchronize the Cisco UCS environment to the NTP server, complete the following steps:

1.       In Cisco UCS Manager, click the Admin tab in the navigation pane.

2.       Select All > Timezone Management.

3.       In the Properties pane, select the appropriate time zone in the Timezone menu.

4.       Click Save Changes and then click OK.

5.       Click Add NTP Server.

6.       Enter <<var_switch_a_ntp_ip>> and click OK.

7.       Click Add NTP Server.

8.       Enter <<var_switch_b_ntp_ip>> and click OK.

9.       Click OK.

Uplink Ports

The Ethernet ports of a Cisco UCS 6248UP Fabric Interconnect are all capable of performing several functions, such as network uplinks or server ports, and more. By default, all ports are unconfigured, and their function must be defined by the administrator. To define the specified ports to be used as network uplinks to the upstream network, complete the following steps:

1.       In Cisco UCS Manager, click the Equipment tab in the navigation pane.

2.       Select Fabric Interconnects > Fabric Interconnect A > Fixed Module or Expansion Module 2 as appropriate > Ethernet Ports.

3.       Select the ports that are to be uplink ports, right click them, and click Configure as Uplink Port.

4.       Click Yes to confirm the configuration and click OK.

5.       Select Fabric Interconnects > Fabric Interconnect B > Fixed Module or Expansion Module 2 as appropriate > Ethernet Ports.

6.       Select the ports that are to be uplink ports, right-click them, and click Configure as Uplink Port.

7.       Click Yes to confirm the configuration and click OK.

8.       Verify all the necessary ports are now configured as uplink ports.

Uplink Port Channels

If the Cisco UCS uplinks from one Fabric Interconnect are to be combined into a port channel or vPC, you must separately configure the port channels using the previously configured uplink ports. To configure the necessary port channels in the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane. 



2.       Under LAN > LAN Cloud, click to expand the Fabric A tree. 


3.       Right-click Port Channels underneath Fabric A and select Create Port Channel. 


4.       Enter the port channel ID number as the unique ID of the port channel. 


5.       Enter the name of the port channel. 


6.       Click Next.

7.       Click each port from Fabric Interconnect A that will participate in the port channel, and click the >> button to add them to the port channel.

8.       Click Finish.

9.       Click OK.

10.    Under LAN > LAN Cloud, click to expand the Fabric B tree. 


11.    Right-click Port Channels underneath Fabric B and select Create Port Channel. 


12.    Enter the port channel ID number as the unique ID of the port channel. 


13.    Enter the name of the port channel. 


14.    Click Next.

15.    Click each port from Fabric Interconnect B that will participate in the port channel, and click the >> button to add them to the port channel.

16.    Click Finish.

17.    Click OK.


18.    Verify the necessary port channels have been created. It can take a few minutes for the newly formed port channels to converge and come online.

Edit Chassis Discovery Policy

Setting the discovery policy simplifies the addition of Cisco UCS B-Series chassis and of additional fabric extenders for further C-Series connectivity. To modify the chassis discovery policy, complete the following steps:

1.       In Cisco UCS Manager, click the Equipment tab in the navigation pane and select Equipment in the list on the left.

2.       In the right pane, click the Policies tab.

3.       Under Global Policies, set the Chassis/FEX Discovery Policy to match the number of uplink ports that are cabled between the chassis or fabric extenders (FEXes) and the fabric interconnects.

4.       Set the Link Grouping Preference to Port Channel.

5.       Click Save Changes.

6.       Click OK.

Server Ports

The Ethernet ports of a Cisco UCS Fabric Interconnect connected to the rack-mount servers, or to the blade chassis or to Cisco UCS S3260 Storage Server must be defined as server ports. When a server port is activated, the connected server or chassis will begin the discovery process shortly afterwards. Rack-mount servers, blade chassis, and S3260 chassis are automatically numbered in the order which they are first discovered. For this reason, it is important to configure the server ports sequentially in the order you wish the physical servers and/or chassis to appear within Cisco UCS Manager. For example, if you installed your servers in a cabinet or rack with server #1 on the bottom, counting up as you go higher in the cabinet or rack, then you need to enable the server ports to the bottom-most server first, and enable them one-by-one as you move upward. You must wait until the server appears in the Equipment tab of Cisco UCS Manager before configuring the ports for the next server. The same numbering procedure applies to blade server chassis.

To define the specified ports to be used as server ports, complete the following steps:

1.       In Cisco UCS Manager, click the Equipment tab in the navigation pane.

2.       Select Fabric Interconnects > Fabric Interconnect A > Fixed Module or Expansion Module 2 as appropriate > Ethernet Ports.

3.       Select the first port that is to be a server port, right-click it, and click Configure as Server Port.

4.       Click Yes to confirm the configuration and click OK.

5.       Select Fabric Interconnects > Fabric Interconnect B > Fixed Module or Expansion Module 2 as appropriate > Ethernet Ports.

6.       Select the matching four ports as chosen for Fabric Interconnect A which would be configured as Server Port.

7.       Click Yes to confirm the configuration and click OK.

8.       Repeat step 6-7 for Fabric Interconnect B

9.       Wait for a brief period, until the rack-mount server appears in the Equipment tab underneath Equipment > Rack Mounts > Servers, or the chassis appears underneath Equipment > Chassis.

Server Discovery

As previously described, when the server ports of the Fabric Interconnects are configured and active, the servers connected to those ports will begin a discovery process. During discovery the servers’ internal hardware inventories are collected, along with their current firmware revisions. Before continuing with the HyperFlex and Cisco UCS S3260 storage server installation processes, wait for all of the servers to finish their discovery process and show as unassociated servers that are powered off, with no errors. To view the servers’ discovery status, complete the following steps:

1.       In Cisco UCS Manager, click the Equipment tab in the navigation pane and click Equipment in the top of the navigation tree on the left. 


2.       In the properties pane, click the Servers tab. 


3.       Click the Chassis > Chassis1 Tab and view the Chassis status in the Overall Status column.

4.       When the chassis is discovered, the S3260 storage server is displayed as shown below:

5.       Click the Rack-Mount Servers or Storage Server sub-tab as appropriate, and view the servers’ status in the Overall Status column. Below are HX Servers for four node HyperFlex Cluster:

HyperFlex Installation

The Cisco HyperFlex software is distributed as a deployable virtual machine, contained in an Open Virtual Appliance (OVA) file format. The HyperFlex OVA file is available for download at www.cisco.com.

When the OVA is installed, the HyperFlex installer is accessed via a webpage using your local computer and a web browser. The HyperFlex Installer configures Cisco UCS and deploys the HyperFlex Data Platform on a Cisco UCS Cluster. To configure Cisco UCS for HyperFlex and then install HyperFlex Data Platform, refer to Cisco HyperFlex Deployment Guide.

As shown in Figure 30, the present setup is deployed with four node HyperFlex Cluster with HX220C-M4 nodes.

 

Figure 30          Cisco UCS Manager Summary for a Four Node HX Cluster

Figure 31 details the HyperFlex Cluster summary through the HX vCenter Plugin.

Figure 31           HX Cluster Summary

Cisco UCS S3260 Configuration

This section details the steps for the Cisco UCS configuration for the S3260 Storage Server. These steps are independent of the Cisco UCS configuration for HX Cluster.

Create Sub-Organization

In this setup, there are two sub-organizations under the root, each for HX and Veeam Infrastucture. Sub-organizations help to restrict user access to logical pools and objects in order to facility security and to provide easier user interaction. For Veeam Backup infrastructure, create a sub-organization as "Veeam." To create a sub-organization, complete the following steps:

1.       In the Navigation pane, click the Servers tab.

2.       In the Servers tab, expand Service Profiles > root. You can also access the Sub-Organizations node under the Policies or Pools nodes.

3.       Right-click Sub-Organizations and choose Create Organization.

Create Chassis Firmware Packages

To create S3260 Chassis Firmware packages, complete the following steps:

1.       In the Navigation pane, click the Chassis tab.

2.       In the Chassis tab, expand Policies > root > sub-Organizations > Veeam.

3.       Right-click Chassis Firmware Packages and select Create Chassis Firmware Packages.

4.       Enter S3260_FW_Package as the Package name.

5.       Select 3.1(3c)C from the Chassis Package drop-down.

6.       Click OK.

Create Disk Zoning Policy

You can assign disk drives to the server nodes using disk zoning. Disk zoning can be performed on the controllers in the same server or on the controllers on different servers.

To create S3260 Disk Zoning Policy, complete the following steps:

1.       In the Navigation pane, click Chassis.

2.       Expand Policies > root > Sub-Organizations > Veeam.

3.       Right-click Disk Zoning Policies and choose Create Disk Zoning Policy.

4.       Enter S3260_DiskZone as the Disk Zone Name.

5.       In the Disk Zoning Information Area, click Add.

6.       Select Ownership as Dedicated.

7.       Select Server as 1 (disk is assigned to node 1 of the S3260 Storage server).

8.       Select Controller as 1.

9.       Slot range as 1-28 (in the present setup there are 28 X6 TB SAS drives).

10.    Click OK.

11.    Click OK again to complete the Disk Zoning Configuration Policy.

Setting S3260 Disk to Unconfigured Good

To prepare all disks from the S3260 Storage Servers for storage profiles, the disks have to be converted from JBOD to Unconfigured Good. To convert the disks, complete the following steps:

1.        Select the Equipment tab in the left pane of the Cisco UCS Manager GUI.

2.       Go to Equipment >Chassis > Chassis 1 > Storage Enclosures > Enclosure1.

3.       Select disks and right-click Set JBOD to Unconfigured Good.

Create MAC Address Pools

To configure the necessary MAC address pools for the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.       Select Pools > root > Sub-organizations > Veeam.

3.       Right-click MAC Pools under the root organization.

4.       Select Create MAC Pool to create the MAC address pool.

5.       Enter MAC_Pool_A as the name of the MAC pool.

6.       Optional: Enter a description for the MAC pool.

7.       Select Sequential as the option for Assignment Order.

8.       Click Next.

9.       Click Add.

10.    Specify a starting MAC address.

11.    Specify a size for the MAC address pool that is sufficient to support the available blade or server resources.

12.    Click OK.

13.    Click Finish.

Create UUID Suffix Pool

To configure the necessary universally unique identifier (UUID) suffix pool for the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Pools > root > Sub-Organizations >Veeam.

3.       Right-click UUID Suffix Pools.

4.       Select Create UUID Suffix Pool.

5.       Enter UUID_Pool as the name of the UUID suffix pool.

6.       Optional: Enter a description for the UUID suffix pool.

7.       Keep the prefix at the derived option.

8.       Select Sequential for the Assignment Order.

9.       Click Next.

10.    Click Add to add a block of UUIDs.

11.    Keep the From field at the default setting.

12.    Specify a size for the UUID block that is sufficient to support the available server resources.

13.    Click OK.

14.    Click Finish.

15.    Click OK.

Create Server Pool

To configure the necessary server pool for the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Pools > root.

3.       Right-click Server Pools.

4.       Select Create Server Pool.

5.       Enter Infra_Pool as the name of the server pool.

6.       Optional: Enter a description for the server pool.

7.       Click Next.

8.       Select S3260 server node to be used for and click >> to add them to the Infra_Pool server pool.

9.       Click Finish.

10.    Click OK.

Create VLANs

To configure the necessary virtual local area networks (VLANs) for the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.       Select LAN > LAN Cloud.

3.       Right-click VLANs.

4.       Select Create VLANs.

5.       Enter hx-inband-mgmt as the name of the VLAN to be used as the native VLAN.

6.       Keep the Common/Global option selected for the scope of the VLAN.

7.       Keep the Sharing Type as None.

8.       Click OK and then click OK again.

9.       Repeat Step 3-8 to add backup VLAN as shown in the figure below:

Create Host Firmware Package

Firmware management policies allow the administrator to select the corresponding packages for a given server configuration. These policies often include packages for adapter, BIOS, board controller, FC adapters, host bus adapter (HBA) option ROM, and storage controller properties.

To create a firmware management policy for a given server configuration in the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Policies > root >Sub-Organizations > Veeam.

3.       Expand Host Firmware Packages.

4.       Right-click and Select Create Host Firmware Package.

5.       Select the version 3.1(3c)B for Blade and 3.1(3c)C for Rack Packages.

6.       Click OK to add the host firmware package.

QoS Policy

To enable quality of service and create QoS policy in the Cisco UCS fabric, complete the following steps:

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.       Select LAN > LAN Cloud > QoS System Class.

3.       In the right pane, click the General tab.

4.       Make sure the Class of Service is configured as shown below. This is already created through the HyperFlex installer.

5.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

6.       Select LAN > Policies > root > Sub-Organizations> Veeam >QoS Policies.

7.       Right-click QoS Policies and select Create QoS Policy.

8.       Enter the name as ‘Silver’ and select Silver in the priority.

9.       Click OK.

Create Network Control Policy for Cisco Discovery Protocol

To create a network control policy that enables Cisco Discovery Protocol (CDP) on virtual network ports, complete the following steps:

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.       Select Policies > root >Sub-Organization > Veeam.

3.       Right-click Network Control Policies.

4.       Select Create Network Control Policy.

5.       Enter Veeam_NCP as the policy name.

6.       For CDP, select the Enabled option.

7.       Click OK to create the network control policy.

 

8.       Click OK.

Create Power Control Policy

To create a power control policy for the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Policies > root >Sub-Organizations >Veeam.

3.       Right-click Power Control Policies.

4.       Select Create Power Control Policy.

5.       Enter No-Power-Cap as the power control policy name.

6.       Change the power capping setting to No Cap.

7.       Click OK to create the power control policy.

8.       Click OK.

Create Server BIOS Policy

To create a server BIOS policy for the Cisco UCS environment, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Policies > root > sub-Organizations >Veeam.

3.       Right-click BIOS Policies.

4.       Select Create BIOS Policy.

5.       Enter S3260-BIOS as the BIOS policy name.

6.       Change the Quiet Boot setting to disabled.

7.       Change Consistent Device Naming to enabled.

8.       Click Finish to create the BIOS policy.

9.       Click OK.

Create Maintenance Policy

To update the default Maintenance Policy, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Policies > root.

3.       Right-click Maintenance Policies and Select Create Maintenance Policy.

4.       Change the Reboot Policy to User Ack.

5.       Optional: Click “On Next Boot” to delegate maintenance windows to server owners.

6.       Click Save Changes.

7.       Click OK to accept the change.

Create Adaptor Policy

To create adaptor policy, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Policies > root > Sub-Organizations > Veeam.

3.       Right-click Adaptor Policies and Select Ethernet Adaptor Policy.

4.       Enter name as veeam_adaptorpol.

5.       Enter Transmit Queues = Receive Queues = 8 , Ring Size = 4096.

6.       Enter Completion Queues = 16 and Interrupts = 32.

7.       Under Options, make sure Receive Side Scaling (RSS) is enabled.

8.       Click OK.

Create vNIC Templates

To create multiple virtual network interface card (vNIC) templates for the Cisco UCS environment, complete the following steps. A total of 3 vNIC Templates will be created.

·         vNIC_veeam_mgmt – Veeam Management vNIC. This has the same VLAN as HX Management VLAN

·         vNIC_intersite. This vNIC provides communication across DataCenter. The HX Management VLAN can communicate across data center; this vNIC is not required

·         vNIC_storage. This vNIC provides communication for S3260 with HX Storage network. This is required for Cisco HyperFlex storage integration with Veeam

Create Data vNICs

1.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

2.       Select Policies > root > Sub-Organizations > Veeam.

3.       Right-click vNIC Templates.

4.       Select Create vNIC Template.

5.       Enter vNIC_veeam_mgmt as the vNIC template name.

6.       Keep Fabric A selected.

7.       Select the Enable Failover checkbox.

8.       Select Updating Template as the Template Type.

9.       Select Redundancy Type as No Redundancy

10.    Under VLANs, select the checkbox for hx-inband-mgmt VLAN.

11.    Set  hx-inband-mgmt as the native VLAN.

12.    For MTU, enter 1500.

13.    In the MAC Pool list, select MAC_Pool_A.

14.    Make sure that vNIC_veeam_mgmt is pinned to Fabric A

15.    In the Network Control Policy list, select Veeam_NCP.

16.    Select QoS Policy as Silver.

17.    Click OK to create the vNIC template.

18.    Click OK.

Repeat these steps for multisite VLAN template:

1.       In the navigation pane, select the LAN tab.

2.       Select Policies > root.

3.       Right-click vNIC Templates.

4.       Select Create vNIC Template

5.       Enter vNIC_veeam_multisite as the vNIC template name.

6.       Select Fabric A.

7.       Select the Enable Failover checkbox.

8.       Under Target, make sure the VM checkbox is not selected.

9.       Select Redundancy Type as No Redundancy.

10.    Select Updating Template as the template type.

11.    Under VLANs, select the checkboxes for Backup_VLAN.

12.    Set Backup_VLAN as the native VLAN.

13.    Select vNIC Name for the CDN Source.

14.    For MTU, enter 9000.

15.    Select QoS Policy as Bronze.

16.    In the MAC Pool list, select MAC_Pool_A.

17.    In the Network Control Policy list, select Veeam_NCP.

18.    Click OK to create the vNIC template.

19.    Click OK.

Repeat these similar steps for HXStorage vNIC template:

1.       In the navigation pane, select the LAN tab.

2.       Select Policies > root.

3.       Right-click vNIC Templates.

4.       Select Create vNIC Template

5.       Enter vNIC_veeam_strge as the vNIC template name.

6.       Make sure vNIC_veeam_strge is pinned to Fabric B. This is required as the HyperFlex storage network traffic is pinned to Fabric B. This avoids backup traffic on HX Storage VLAN traverse upstream switch.

7.       Select the Enable Failover checkbox.

8.       Under Target, make sure the VM checkbox is not selected.

9.       Select Redundancy Type as No Redundancy.

10.    Select Updating Template as the template type.

11.    Under VLANs, select the checkboxes for hx-storage-data.

12.    Set hx-storage-Data as the native VLAN.

13.    Select vNIC Name for the CDN Source.

14.    For MTU, enter 9000.

15.    Select QoS Policy as Bronze.

16.    In the MAC Pool list, select MAC_Pool_A.

17.    In the Network Control Policy list, select Veeam_NCP

18.    Click OK to create the vNIC template.

19.    Click OK.

Create Disk Group Policy

A storage profile encapsulates the storage requirements for one or more service profiles. LUNs configured in a storage profile can be used as boot LUNs or data LUNs, and can be dedicated to a specific server. You can also specify a local LUN as a boot device. The introduction of storage profiles allows you to do the following:

·         Configure multiple virtual drives and select the physical drives that are used by a virtual drive. You can also configure the storage capacity of a virtual drive.

·         Configure the number, type and role of disks in a disk group.

·         Associate a storage profile with a service profile

Cisco UCS Manager's Storage Profile and Disk Group Policies are utilized to define storage disks; disk allocation and management in the Cisco UCS S3260 system. You will create two disk Group Policies as follows:

·         RAID 1 from two Rear SSDs for OS Boot

·         RAID60 from 28 HDD as defined under Disk Zoning Policy

To create a Disk Group Policy, complete the following steps:

1.       In Cisco UCS Manager, click the Storage tab in the navigation pane.

2.       Select Storage Policies > root >Sub-Organizations > Veeam >Disk Group Policies.

3.       Right-click Disk Group Policy and Select Create Disk Group Policy.

4.       Enter the name as RAID1_OS.

5.       Select RAID Level as RAID1 Mirrored.

6.       Number of drives as 2 and Drive Type as SSD.

7.       Click OK.

8.       Create a second Disk Group Policy with RAID60.

9.       Create a RAID60 with 28 HDDs.

10.    For 28 DISK configuration of RAID60, you should have 2 SPANs and each SPAN should have 13 disks, including 1 DISK as Dedicated Hot Spare.

11.    The remianing 2 DISK are allocated for Global Hot Spares.

12.    Enter the name as S3260-RAID60, Select RAID60 from RAID Level and opt for Manual Disk Group Configuration.

13.    Click Add, enter the Slot Number as 1, Role as Normal, and Span ID as 0.

 

14.    Repeat step 11 for Slot numbers 2 through 12 with Span ID 0.

15.    For Slot 13, select Role as Dedicated Hot Spare and Span Id as 0 and for Slot 14 select Role as Global Hot Spare and Span Id as ‘unspecified’.

16.    Repeat Step 1 for Slot 15 through Slot 26 and enter Span ID as 1.

17.    For Slot 27, select Role as Dedicated Hot Spare and SPAN ID as 1.

18.    For Slot 28, select Role as Global Hot Spare and leave the Span ID as ‘unspecified’.

19.    When you have configured all 28 Disk with 2 Spans, select Strip Size as 64KB,

20.   Access Policy as ReadWrite.

21.    Read Policy as Read Ahead.

22.   Write Cache Policy as Write Back Good Bbu.

23.    IO Policy as Direct.

24.   Drive Cache Policy as Platform Default

The screenshot below shows the RAID60 configuration with 28 Disk and the suggested Virtual Drive Configuration:

RAID Configuration for a different disk arrangement on Cisco UCS S3260 and Cisco UCS C240 M4 LFF servers are detail in the table below:

Table 4     RAID Configuration for Cisco UCS S3260 and C240 M4 LFF Server

 

Create Storage Profile

To create Storage Profile for S3260, complete the following steps:

1.       In Cisco UCS Manager, click the Storage tab in the navigation pane.

2.       Select Storage Policies > root >Sub-Organizations >Veeam.

3.       Right-click and Select Create Storage Profile.

4.       Enter name as S3260_Str_Prf_1.

5.       Under Local Lun Selection, click Add.

6.       Enter Name as OS_Boot.

7.       Check Expand to Available, this creates a single lun with maximum space available.

8.       Select Disk Group Selection as ‘RAID1_OS’ and click OK.

9.       Click Add under Local LUN.

10.    Enter Name as Veeam_Rep; this is the LUN used by Veeam Repository.

11.    Check Expand to Available and Select Disk Group Configuration as ‘S3260-RAID60’.

12.    Click OK.

13.    In Create Storage Profile, click OK.

Create Chassis  Profile Template

A chassis profile defines the storage, firmware and maintenance characteristics of a chassis. You can create a chassis profile for the Cisco UCS S3260 Storage Server. When a chassis profile is associated to a chassis, Cisco UCS Central automatically configures the chassis to match the configuration specified in the chassis profile.

A chassis profile includes four types of information:

·         Chassis definition—Defines the specific chassis to which the profile is assigned.

·         Maintenance policy—Includes the maintenance policy to be applied to the profile.

·         Firmware specifications—Defines the chassis firmware package that can be applied to a chassis through this profile.

·         Disk zoning policy—Includes the zoning policy to be applied to the storage disks.

To create Chassis Profile Template for Cisco UCS S3260 storage server, complete the following steps:

1.       In Cisco UCS Manager, click the Chassis tab in the navigation pane.

2.       Select Chassis Profile Templates > root > Sub-Organizations > Veeam.

3.       Right-click and select Create Chassis Profile Template.

4.       Enter name as Chassis_Template.

5.       Select Type as Updating Template.

6.       Select default as the Maintenance Policy and click Next.

7.       Select Chassis Firmware Package as ‘S3260_FW_Package’.

8.       Select Disk Zoning Policy as ‘S3260_DiskZone” and click Finish.

Create Service Profile Template

With a service profile template, you can quickly create several service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with identity information drawn from the same pools.

For example, if you need several service profiles with similar values to configure servers to host database software, you can create a service profile template, either manually or from an existing service profile. You then use the template to create the service profiles.

Cisco UCS supports the following types of service profile templates:

·         Initial template: Service profiles created from an initial template inherit all the properties of the template. However, after you create the profile, it is no longer connected to the template. If you need to make changes to one or more profiles created from this template, you must change each profile individually.

·         Updating template: Service profiles created from an updating template inherit all the properties of the template and remain connected to the template. Any changes to the template automatically update the service profiles created from the template.

To create the service profile template, complete the following steps:

1.       In Cisco UCS Manager, click the Servers tab in the navigation pane.

2.       Select Service Profile Templates > root >Sub-Organizations > Veeam.

3.       Right-click Veeam.

4.       Select Create Service Profile Template to open the Create Service Profile Template wizard.

5.       Enter S3260_SP_Template as the name of the service profile template.

6.       Select the “Updating Template” option.

7.       Under UUID, select UUID_Pool as the UUID pool.

8.       Click Next.

Configure Storage Provisioning

1.       Click Storage Profile Policy Tab and select S3260_Str_Prf_1 ( as created under Storage Profile section).

2.       Click Next.

Configure Networking Options

1.       Keep the default setting for Dynamic vNIC Connection Policy.

2.       Under ‘How would you like to configure LAN connectivity’, select Expert Mode.

3.       Select the “Use Connectivity Policy” option to configure the LAN connectivity.

4.       Click Add.

5.       Under Create vNIC option, enter name as vnic_Mgmt.

6.       Select use vNIC Template and choose vNIC_veeam_mgmt.

7.       Under Adaptor Policy Select ‘veeam_adaptorpol’ and click OK.

8.       Repeat Step 1 to 7 and name the vNIC as vnic_Storage, vNIC Template as vNIC_veeam_strge and adaptor policy as Veeam_adaptorpol.

9.       Repeat Step 1 to 7 and name the vNIC as vnic_intersite, vNIC Template as vNIC_veeam_site and adaptor policy as Veeam_adaptorpol.

10.    Click Next.

Table 5  lists the details of each vNIC.

Table 5     vNIC Configured for HX Multisite Backup and Replication

Configure Storage Options

Configure Zoning Options

1.       Set no Zoning options and click Next.

Configure vNIC/HBA Placement

1.       In the “Select Placement” list, leave the placement policy as “Let System Perform Placement”.

2.       Click Next.

Configure vMedia Policy

1.       From the vMedia Policy, leave as default.

2.       Click Next.

Configure Server Boot Order

1.       Choose Default Boot Policy.

Configure Maintenance Policy

1.       Change the Maintenance Policy to userAck.

2.       Click Next.

Configure Server Assignment

To configure server assignment, complete the following steps:

1.       In the Pool Assignment list, select Assign Later.

2.       Firmware Management at the bottom of the page select S3260Firmware as created in the previous section.

3.       Click Next.

Configure Operational Policies

To configure the operational policies, complete the following steps:

1.       In the BIOS Policy list, select S3260-BIOS.

2.       Expand Power Control Policy Configuration and select No-Power-Cap in the Power Control Policy list.

3.       Click Finish to create the service profile template.

4.       Click OK in the confirmation message.

Create Chassis Profile

To create chassis profile from the chassis profile template, complete the following steps:

1.       Click the Chassis tab in the navigation pane.

2.       Select Chassis Profile Templates > root > Sub-Organizations > Veeam > Chassis Profile Template Chassis_Template.

3.       Right-click Chassis Profile Template Chassis_Template and Select Create Chassis Profiles from Template

4.       Enter S3260_Chassis_SP as the Chassis profile prefix.

5.       Enter 1 as “Name Suffix Starting Number and 1 as Number of Instances.

6.       The screenshot below displays S3260_ChassisSP1 under Chassis > root > Sub_organizations > Veeam > Chassis Profile.

Associate Chassis Profile to S3260 Chassis

To Associate Chassis Profile to S3260 Chassis, complete the following steps:

1.       Click the Chassis tab in the navigation pane.

2.       Select Chassis Profiles > root > Sub-Organizations > Veeam.

3.       Right-click ‘S3260_Chassis_SP1’ and select Change Chassis Profile Association.

4.       In the Assignment tab, Select Existing Chassis.

5.       Thereafter select the existing chassis.

6.       Click OK.

7.       Since you have selected User Ack for the Maintenance Policy, you need to acknowledge Chassis Reboot for Chassis Profile Association.

8.       On FSM Tab you will see the Association Status.

9.       When the chassis is associated you will see the assigned status as Assigned.

Create Service Profiles

This section describes how to associate the Compute Node on S3260 Storage server to a Service Profile.

To create service profiles from the service profile template, complete the following steps:

1.       On Servers tab in the navigation pane.

2.       Select Service Profile Templates > root > Sub-Organizations > Veeam > Service Template. S3260_SP_Template.

3.       Right-click S3260_SP_Template and select Create Service Profiles from Template.

4.       Enter SP_S3260_node as the service profile prefix.

5.       Enter 1 as “Name Suffix Starting Number.”

6.       Enter 1 as the “Number of Instances.”

7.       Click OK to create the service profile.

8.       Click OK in the confirmation message.

Associate Service Profile to Server Node of S3260 Chassis

To Associate Service Profile to server node of S3260 Chassis, complete the following steps:

1.       Click the Chassis tab in the navigation pane.

2.       Select Service Profiles > root > Sub-Organizations > Veeam.

3.       Right-click ‘SP_S3260_node1” and select Change Service Profile Association.

4.       In the Assignment tab, Select Existing Chassis.

5.       In the Associate Service Profile Window, select the M4 node for S3260 Chassis.

6.       Click OK.

7.       A warning displays, click Yes.  

8.       When Service Profile Association is complete, confirm that the overall status is OK.

9.       Verify the Boot LUN and Veeam Repository LUN under Storage tab of Service Profile.

10.    Verify Service Profile has 3 vNICs.

                                                                                                                                                                                              

This section details the installation and configuration of Veeam Availability Suite 9.5 on Cisco UCS S3260 storage server node. The important high-level steps are as follows:

·         Install and configure Windows 2016 on S3260 server node

·         Install Veeam Availability Suite 9.5

·         Configure Backup Infrastructure for Veeam Availability Suite

Install and Configure Windows 2016

To install and configure Windows 2016, complete the following steps:

1.       In the Navigation pane, select Server tab.

2.       In the Servers tab, expand Service Profiles > root > Sub-Organizations > Veeam >SP_S3260_node1.

3.       Click KVM console and open the *.jnlp with java webstart.

4.       In KVM Console, go to the Virtual Media tab and select Activate Virtual Devices.

5.       On the Virtual Media tab, select MAP CD/DVD and browse to Windows 2016 Installer and Map Device.

6.       Reset the server and wait for the ISO image to load.

7.       Install Windows 2016.

Load Driver for S3260 RAID Controller

To load the RAID Controller driver S3260, complete the following steps:  

1.       On the Screen ‘Where do you want to install Windows?’ click Load Driver.

2.       In Cisco UCS Manager, click the LAN tab in the navigation pane.

3.       In Virtual Media, un-map the Windows installer ISO and map the S3260 drivers ISO. The drivers for S3260 can be downloaded from www.cisco.com at location > Downloads Home Products Servers > Unified Computing > UCS C-Series Rack-Mount UCS-Managed Server Software > Unified Computing System (UCS) Drivers-3.0(1a).

4.       Click Browse and navigate to the location of the driver as shown in screenshot below:

5.       Click Rescan and view the correct RAID Controller driver in the "Select the driver to install" window.

6.       Click Next to install the driver.

7.       Return to ‘Where do you want to install Windows’ screen, uncheck the driver ISO image and re-map the Windows Installer Image.

8.       Click Refresh.

9.       Select the Drive2. This drive is RAID1 config created from the two SSD in the rear of S3260 chassis for OS installation through Storage Profile in the Cisco UCS Service Profile. Drive3 is the RAID60 configuration created from the top load SAS drives for Veeam Repository.

10.    Click Next.

11.    When the installation completes, proceed to the following section, Update Cisco VIC Driver for Windows 2016.

Update Cisco VIC Driver for Windows 2016

To update the Cisco VIC driver for Windows 2016, complete the following steps:

1.       Open the UCS KVM Console and login to Windows 2016 installed on S3260 Storage Server.

2.       Map the S3260 drivers through Map CD/DVD option under the Virtual Media tab in the KVM Console.

3.       The S3260 drivers are located in the section ‘Load Drivers for S3260 RAID Controller.’

4.       In Windows 2016, go to Control Panel > Device Manager.

5.       Select Ethernet Controller and Select Update Driver.

6.       Select for ‘Browse for Driver in My Computer.’

7.       Select DVD Driver as mapped through Virtual Media in  KVM Console and browse to \Network\Cisco\VIC\W2K16\x64.

8.       Click Next to install the Cisco VIC Ethernet Interface driver.

9.       Follow steps 5 through 8 to install the driver for the other two VIC Ethernet interface.

Update Intel ChipSet Driver for Windows 2016

To update Intel ChipSet driver for Windows 2016, complete the following steps:

1.       Update Driver for S3260 Intel Chip Set.

2.       Under the S3260 Driver ISO mounted through Virtual Media of KVM Console, browse to \ChipSet\Intel\C3260\W2K16.

3.       Execute SetupChipset.exe. When it is installed, click Restart Now.

4.       After Reboot, verify that all the drivers are updated and you have 3 vNIC on the Windows 2016 OS.

Configure Network for Veeam Backup Server

The Cisco S3260 storage server configured as the Veeam Backup Server has three networks:

1.       Configure vNIC_intersite with IP Address on VLAN which can access Remote HX VCenter and Remote Proxy Server. Remote Proxy Server allows Replication of HyperFlex Remote Site. vNIC_intersite configuration is only required if HX Management network cannot be accessed outside the Primary Data Center.

2.       Configure vNIC_Mgmt with IP Address on HX Management VLAN.

3.       Configure vNIC_Storage with IP Address on HX Storage VLAN. This is required for Cisco HyperFlex and Veeam Storage Integration.

Create Disk Volume for Veeam Repository

To create a disk volume for Veeam repository, complete the following steps:

1.       Go to Server Manager > File and Storage Services.

2.       Navigate to Volumes > Disks and select the volume with Partition type as ‘Unknown.’

3.       Create a New Volume.

4.       Click Next until you reach the ‘Select File System settings’ window.

5.       Create a Volume Label, select File system to ‘ReFS’, Allocation unit size to ‘64k’, Volume label to 'VeeamRep.'

6.       Click Next.

7.       Confirm the File System Settings and click Create.

Install Veeam Availability Suite 9.5

To install Veeam Availability Suite 9.5, complete the following steps:

1.       Download the Veeam software from https://www.veeam.com/data-center-availability-suite-vcp-download.html. Download a free 30-day trial license key or obtain license key from Veeam.

2.       Execute Veeam 9.5 setup file.

3.       Click Install Link.

4.       Accept the License Agreement.

5.       Browse to the license file and click Next.

6.       Click Next on Program features.

7.       During System Check, Veeam verifies the SQL Server Installation and prerequisite software components. Click Install.

 

8.       This will install all the required dependencies. When the system Check passes, click Next.

9.       Accept the default Installer locations and click Install.

10.    Click Finish when the installation completes.

Configure Veeam Availability Suite 9.5

To configure Veeam Availability Suite 9.5, complete the following steps:

1.       From the desktop, Open the Veeam Backup & Replication Console.

2.       Click Connect on local host.

3.       By default, Veeam uses the D: drive as the Veeam Repository. This is the repository created through Disk Volume.

4.       Right-click Managed Server and click ‘Add Server.’

5.       Select VMWare VSphere and add the vCenter URL of HyperFlex Cluster, click Next.

6.       Enter the vCenter credentials and click Next.

7.       When Veeam Console collects all the deployment details from vCenter, click Finish.

8.       Click Backup Proxies in the right navigation windows, choose VMware Backup Proxy and edit Properties.

9.       Edit Max Concurrent Task to be equal to Number of physical cores in S3260 minus 2. In the present deployment, there is a dual 18-core Intel  processor and therefore you can increase the Max Concurrent Task to 34.

10.    Under Transport Mode, click Choose and make sure that “failover to network mode, if primary mode fails, or is unavailable” is checked. This option is checked by default.

11.    Click Finish.

12.    Click Backup Repository in the right navigation window, select the Default Backup Repository and edit Properties.

13.    Click Next until you reach the Repository Windows.

14.    Increase the ‘Limit Max Concurrent Task’ to be 34 (Number of physical cores in S3260 minus 2).

 

15.     Click Finish.

16.    Add the MaxSnapshotsPerDatastore parameter in Registry.

17.    Using the Registry key Editor, go to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\; add a RegDWord with the name ‘MaxSnapshotsPerDatastore’ value greater than 4.

18.    Restart the Windows 2016 Server for Registry Settings to be applied.

Configure HX Storage Infrastructure with Veeam

To Configure Cisco HyperFlex Storage with Veeam, complete the following steps:

1.       Refer to the Cisco HyperFlex Storage Integration Guide to successfully configure the storage infrastructure integration of HyperFlex with Veeam.

2.       Go to Veeam Backup and Replication Console on S3260 storage server.

3.       Click Storage Infrastructure > Cisco HyperFlex and Rescan Storage.

4.       Ensure NFS IP are properly scanned by Veeam Server, as detailed in the screenshot below.

Cisco HyperFlex Remote Site Protection

Veeam allows the protection of Cisco HyperFlex Remote Site by replication of Application VM to the Primary Site. The high-level workflow is detailed in figure below:

 

Figure 32          Remote Office Deployment Components

In the present design, the Veeam Proxy Server is installed in a Cisco UCS C240 M4 Server located in HX Cluster on Remote Office. Windows 2016 is installed on Cisco UCS C240 M4 LFF server. The choice of either a virtual machine or physical server for Veeam Proxy is dependent on several factors such as:

·         Number of Replication jobs executed on ROBO deployment.

·         Deployment of Veeam WAN Accelerator on the Remote Site. Customers can deploy Veeam WAN Accelerator, which allows faster replication and backup of application VMs. It is required to deploy Veeam WAN Accelerator on a Cisco UCS C240 M4 LFF with SSDs for WAN Accelerator Cache. 

Configure Remote Veeam Proxy to Replicate VM on Cisco HyperFlex Primary Site

To Add Remote Proxy to Veeam Server, complete the following steps:

1.       On the left pane of Veeam Console, go to Backup Infrastructure

2.       Right-click Backup Proxy and Select Add VMWare Backup Proxy.

3.       Select defaults (Automatic Selection ) for transport mode and Connected datastore.

4.       Add Remote Proxy details (Server IP Address & Credentials).

 

5.       Click OK and then click Next; Veeam Console will connect to remote Proxy and configure the server.

 

6.       Select default for the subsequent screens and verify that the Proxy is successfully added.

7.       Verify the Veeam Console is configured with two proxies:

-        Local Veeam proxy deployed on same S3260 storage server

-        Remote Veeam proxy deployed on C240 M4 LFF Rack Server

Add Remote VCenter to the Veeam Console

When the Remote Proxy is successfully added, you need to add the Remote VCenter managing the Remote HX Cluster.

To add the Remote VCenter, complete the following steps:

1.       In the left pane of Veeam Console, Under Backup Infrastructure, right-click Managed Server and Select Add Server.

2.       Add Remote VCenter Details.

 

3.       Verify VCenter is successfully added.

4.       Verify there are two VCenter configured on Veeam Console:

a.     Local VCenter configured for Local HyperFlex Cluster

b.    Remote VCenter with Remote HyperFlex Cluster

This completes the deployment of Veeam Availability Suite 9.5 on Cisco UCS S3260 Storage server with Primary HyperFlex Cluster and Remote Office HyperFlex Cluster.

Cisco HyperFlex Multisite Protection

As detailed in section Multisite Backup and Replication for Cisco HyperFlex, Multisite Backup and Replication is configured with Cisco UCS S3260 Server on each of the data center. Both the proxy and Repository are configured on same the S3260 server.

Backup copy jobs can be executed across S3260 storage server. This allows high availability of backups during backup server failures in the Data Center.

Figure 33 illustrates the HyperFlex Multisite Backup components.

 

Figure 33           Multisite Backup Components

As detailed in Figure 34:

·         Veeam Repository and Veeam Proxy are locally configured on the Cisco UCS SS3260 storage server existing on each of the data center. In cases wherein, the Remote Data Center requires lower storage capacity, Cisco UCS C240 M4 LFF server can be configured.

·         Veeam Backup console is deployed on the S3260 storage server existing on the primary Data Center. Veeam Console can be also be configured as a VM on existing Primary Data Center ESXi environment.

·         Veeam Console manages all the Veeam repositories and proxies existing across data centers.

Figure 34          Details of the Local and Remote Proxy Configured on Veeam Console

 

Figure 35           Details of the Local and Remote Repositories Configured on Veeam

Figure 36          Details of the Remote and Local VCenters Added to Veeam Console

This section describes the test executed to validate the Veeam Backup and Recovery Solution on the Cisco HyperFlex platform. This solution and its scenarios are validated with high-level backup, Replication, Failover and Failback task between HyperFlex Cluster and Cisco UCS S3260 Storage Server.

Some of the important test executed are as follows:

·         Backup VM on HX Cluster with HyperFlex and Veeam Storage Integration

·         Remote Office / Branch Office VM Replication

·         Backup Copy jobs across Data Centers

·         Restoration of VM from Backup Copy job to HyperFlex Cluster on DR Site

Backup VM on HX Cluster with HyperFlex and Veeam Storage Integration

The validation detailed below displays a successful backup of several VM on HX cluster to Cisco UCS S3260 target repository utilizing HyperFlex and Veeam Storage Integration.

To backup the VM on HX Cluster, complete the following steps:

1.       Verify HX Cluster is configured through Veeam Storage Integration. As detailed in previous sections, refer to Cisco HyperFlex Storage Integration Guide, to successfully configure Strorage Infrastucture Integration of HyperFlex with Veeam.

2.       Identify the VMs on HyperFlex Cluster for Backup through Veeam.

3.       Go to Veeam Backup and Replication Console and Create Backup job.

4.       Make sure that Enable Backup from Storage Snapshot is checked.

5.       During Backup make sure Veeam executes HyperFlex Snapshot.

6.       During Execute Backup job and monitor progress.

7.       Validate the successful completion of Backup job.

Remote Office / Branch Office VM Replication

The validation detailed below displays a successful backup of several VM on HX cluster to Cisco UCS S3260 target repository utilizing HyperFlex and Veeam Storage Integration.

To replicate the VM for the Remote/Branch office, complete the following steps:

1.       Identify the VM to be replicate on Remote Site. Make sure the Remote VCenter and Remote Veeam Proxy is configured through Veeam Backup Server.

 

2.       Create a Replication Job and Add VM for Replication.

3.       Configure Destination. This would is the HX Cluster on the Primary Site.

4.       Configure Source and Target Proxy.

5.       Execute the Replication Job and monitor progress.

6.       When the job completes, you can execute a Failover and verify that the VM has failed over to the Primary HX Cluster.

 

Backup Copy Jobs Across Data Centers

The validation detailed below describes a successful Backup Copy jobs across HX Multi Data Center. To Backup Copy, complete the following steps:

1.       Identify the Backup on Remote Site which is copied to Primary site.

2.       Create a Backup Copy job.

3.       Execute the backup copy.

4.       When completed, you will have a copy of Backup to the secondary S3260 Storage server. This provides protection for Backups executed on the S3260 storage sever during Secondary or Primary Site Failure.

Restore Backup Copy Job VM to DR Site

The validation detailed below describes the restoration of VM from Backup Copy job to HX Cluster on DR Site. You will restore the HXSecondarySiteVM from the backup copy job executed in the previous section. To restore the backup copy job VM, complete the following steps:

1.       Launch Restoration from the Restore tab from the Main menu.

2.       Select Entire VM option.

3.       Add the VM from the Backup Copy job executed in the previous section.

 

4.       Select Restore to new Location; the location is HX Cluster on the site where you created the Backup Copy Job.

5.       Select Proxy existing on the DR Site.

6.       Add Host; this the HX Cluster where you want to restore the VM from Backup Copy job.

  

7.       Select the default Datastore on HX Cluster.

8.       Select default for the other screens.

9.       Confirm the Restoration Summary.

 

10.    Execute the job.

11.    Post Restoration; power on the VM and confirm that it is restored on the DR Site.

Validated Hardware and Software

Table 6 lists all the software and hardware components deployed to validate the design for Cisco HyperFlex with Veeam Backup and Replication.

Table 6     Software and Hardware Components Deployed in this CVD

The BOM below lists the major components validated, but it is not intended to be a comprehensive list.

 

Design Guide for Cisco HyperFlex with Veeam Availability Suite

Cisco HyperFlex with Veeam Availability Suite

Cisco HyperFlex Data Platform Backup Integration Guide

Cisco HyperFlex HX220c M4 Node Installation Guide 

Cisco HyperFlex HX240c M4 Node Installation Guide 

Design and Deployment Guide for Cisco HyperFlex Systems

HyperFlex Hardware and Software Interoperability Matrix

Veeam Availability Suite v9 Installation and Deployment Guide

Anil Dhiman, Technical Marketing Engineer, Cisco Unified Computing Systems, Cisco Systems, Inc.

Anil Dhiman has over 16 years of experience specializing in Data Center solutions on Cisco UCS servers, and Performance Engineering of large-scale enterprise applications. Over the past 6 years, Anil has authored several Cisco Validated Designs for Enterprise Solutions on Cisco Data Center Technologies. Currently, Anil's focus is on Cisco’s portfolio of Hyperconverged Infrastructure and Backup Solutions.

Acknowledgements

For their support and contribution to the design, validation, and creation of this Cisco Validated Design, we would like to acknowledge the significant contribution and expertise that resulted in developing this document:

·         Ulrich Kleidon, Principal Engineer, Cisco Systems, Inc.

·         Shawn Lieu, Solutions Architect with the Global Alliances Team, Veeam Software

·         Stefan Renner, EMEA Alliance Systems Engineer, Veeam Software