•  Welcome
  • About product terminology
  • About document conventions
  • About documentation and release notes
  • Contacting Riverbed
•  About Branch Converged Infrastructure
  • About the product family
  • About system components
  • About blockstore prefetch and prepopulation
•  Deploying Core and Edge as a System
  • Providings LUNs on the storage array
  • Installing appliances
  • Pinning and prepopulating LUNs in the Core
  • Configuring snapshot and data protection functionality
  • About crash and application consistency
  • Single-appliance versus high-availability deployments
  • Connecting product components
  • Adding Edges to the Core configuration
  • Configuring LUNs
  • Configuring Edges for specific LUNs
  • About Riverbed Turbo Boot
•  Deploying Core
  • About Ports
  • About interface routing
  • Configuring additional routes
  • Configuring Core for jumbo frames
  •  Configuring the iSCSI initiator
    • Exposing LUNs
    • Resizing LUNs
    • Configuring Fibre Channel LUNs
    • Offlining LUNs
  • Removing LUNs
  •  About redundant connectivity with MPIO
    • MPIO in Core
  • About Core MPIO settings
  • About pool management
  • About pool management architecture
  •  Configuring pool management
    • Generating REST access codes
    • Adding pool members
    • Changing pool management structure
  • About high availability in pool management
  • Cloud storage gateway support
•  Deploying the Edge
  • Configuring Edge for jumbo frames
  • Configuring Ethernet interfaces for jumbo frames
  • Moving an Edge to a new location
  • About Edge ports
  • Configuring product storage
•  About High Availability
  • About Core high availability
  • Cabling and connectivity for clustered Cores
  • Configuring failover peers
  • Accessing failover peers
  • Failover states and sequences
  • Recovering from failure of both Cores in HA configuration
  • Removing Cores from an HA configuration
  • Edge high availability
  • Using the correct interfaces for Edge deployment
  • Choosing the correct cables
  • Overview of Edge HA
  • Edge HA using blockstore synchronization
  • Edge HA peer communication
  • Recovering from split-brain scenarios involving Edge HA
  • Testing HA failover deployments
  • Configuring WAN redundancy
  • Configuring WAN redundancy with no Core HA
  • Configuring WAN redundancy in an HA environment
•  About Data Protection and Snapshots
  • Setting up application-consistent snapshots
  • Configuring snapshots for LUNs
  • About Volume Snapshot Service support
  • About RHSP and VSS
  • Riverbed Host Tools installation and configuration
  • Configuring the proxy host for backup
  • Configuring the storage array for proxy backup
  • About server-level backups
  • Creating policies on Core
  • About migrating from LUN protection to server-level backup
  • About protection groups and policy customization
  • About the product snapshot framework
  • About data recovery
  • About branch recovery
  • Branch recovery configuration
  • Branch recovery CLI configuration example
•  About Data Replication
  • About replication design
  •  About failover scenarios
    • Secondary site is down
    • Replication is suspended at the secondary site
    • Primary site is down (suspended)
  • FusionSync high-availability considerations
  • FusionSync and Core HA
  • Replication HA failover scenarios
  • Product replication metrics
  • Journal LUN metrics
  • Edge local LUNs and product replication
•  About Data Resilience and Security
  • Recovering a single Core
  • Replacing the Edge
  •  Disaster recovery scenarios
    • Product appliance failure—failover
    • Product appliance failure—failback
  • Rolling back the LUN snapshot
  •  Using CHAP to secure iSCSI connectivity
    • Configuring one-way CHAP in a Core deployment
    • Configuring mutual CHAP in a Core deployment
  •  At-rest and in-flight data security
    • Enabling data at-rest blockstore encryption
    • Enabling data in-flight secure peering encryption
  • Clearing the blockstore contents
  • Edge network communication
  • Additional security best practices
•  Upgrading the Appliance
  • Planning software upgrades
  • About the upgrade sequence
  • Minimizing risk during upgrading
  •  Performing the upgrade
    • Upgrading the Edge
    • Upgrading the Core
  • Related information
•  About Network Quality of Service
  • Rdisk protocol overview
  • QoS for replication traffic
  • QoS for unpinned LUNs
  • QoS for pinned LUNs
  • QoS for branch offices that mainly read data from the data center
  • QoS for branch offices booting virtual machines from the data center
  • Time-based QoS rules example
•  Deployment Best Practices
  •  Core best practices
    • Deploy on gigabit Ethernet networks
    • Use CHAP
    • Configure initiators and storage groups or LUN masking
    • Segregate storage traffic from management traffic
    • When to pin and prepopulate the LUN
    • Core configuration export
    • Core in HA configuration replacement
    • Hardware upgrade of Core appliances in HA configuration
    • LUN-based data protection limits
    • WAN usage consumption for a Core to Edge VMDK data migration
    • Reserve memory and CPU resources when deploying Core
  •  Edge best practices
    • Segregate traffic
    • Pin the LUN and prepopulate the blockstore
    • Segregate data onto multiple LUNs
    • Ports and type of traffic
    • iSCSI port bindings
    • Changing IP addresses on the Edge, ESXi host, and servers
    • Disk management
    • Rdisk traffic routing options
    • Deploying the product with third-party traffic optimization
    • Windows and ESX server storage layout—product-protected LUNs vs. local LUNs
    • VMFS datastores deployment on product LUNs
    • Enable Windows persistent bindings for mounted iSCSI LUNs
    • Set up memory reservation for ESXi virtual machines
    • Boot from an unpinned iSCSI LUN
    • Running antivirus software
    • Running disk defragmentation software
    • Running data deduplication features
    • Running backup software
    • Configure jumbo frames
    • Removing Core from Edge and readding Core
  • Microsoft and ESX iSCSI initiator timeouts
  • Operating system patching at the branch office or data center for virtual servers installed on iSCSI LUNs
  • Related information
•  Product Appliance Sizing
  • General sizing considerations
  • Core sizing guidelines
  • Edge sizing guidelines
•  About Licensing, Upgrading, and Image Signing
  • About Riverbed licensing methods
  • About automatic licensing
  • About the Riverbed Licensing Portal
  • Installing licenses using the Management Console
  • Installing licenses using the CLI
  • About software upgrades and image signing
  • About software image signing certificates
  • Importing image signing certificates
  • About software upgrades
  • Using an image located on the network
  • Using an image located on the Riverbed Support site
  • Using an image located on the local system
  • Switching to the backup software version
  • Restarting and shutting down the appliance

SteelHead Resilient Storage Design Guide

Restarting and shutting down the appliance