This Site Is Depreciated
  • This is the depreciated Version of Veeam Backup & Replication Best Practices
  • Contacting Veeam Software
  • DNS Resolution
  • Veeam Backup Server
    • Deployment Method
    • Backup Server Placement
    • Sizing and System Requirements
    • Veeam Backup & Replication Database
    • Protecting Veeam Backup & Replication Configuration
  • Veeam Enterprise Manager
    • vCloud Director Self Service Portal
  • Search Server and Indexing
  • Proxy Servers - Introduction
    • Proxy - VMware vSphere
      • Transport Modes
        • Direct Storage Access
        • Virtual Appliance Mode
        • Network Mode
        • Backup from Storage Snapshots
          • NetApp Data ONTAP integration
          • Nimble Storage integration
        • Selecting a Transport Mode
      • Sizing a Backup Proxy
    • Proxy - Microsoft Hyper-V
    • Proxy - Nutanix AHV
  • Primary and secondary Storage BPs
    • HPE 3PAR VMs disks considerations
    • DellEMC Data Domain advanced scalability
  • Backup Repository
    • Repository Types
      • SMB
      • Deduplication Appliances
      • Integration specifics
      • Windows Server Deduplication
      • Object Storage
    • Repository Planning
      • Sizing
      • Per VM Backup Files
      • Scale-out Backup Repository
        • Capacity Tier
    • Repository HA
  • WAN Acceleration
    • Analyzing Wan Acceleration Workload
    • Comparing WAN Acceleration Modes
    • Sizing For WAN Acceleration
    • Sizing Targets for WAN Accereration Relationship
    • Deployments For WAN Acceleration
    • Is WAN Acceleration Right For me
  • Tape Support
    • Tape Deployments
    • Tape Media Information
    • Tape Config Requirements
    • Tape Parallel Processing
    • Tape Virtual Full
    • Tape Writing to Tape
    • Tape Restores
  • Veeam Explorers
  • Interaction with VMware vSphere
  • Interaction with Microsoft Hyper-V
  • Job Configuration
    • Backup Methods
    • Encryption
    • Deduplication and Compression
    • Backup Job
    • Backup Copy Job
    • Replication Job
    • Application-Aware Image Processing
  • Data Verification Using Virtual Labs
  • Overview of Applications Support
    • Active Directory
    • Microsoft Exchange
    • Microsoft SQL Server
    • Microsoft SharePoint Server
    • Oracle Database
    • MySQL
    • IBM Notes/Domino
    • SAP HANA
  • POC Guide
    • Assessment
    • Accelerated Evaluation
    • Enhanced Evaluation
      • Workshop Example
      • Preparation
      • Automation
  • Infrastructure Hardening
    • Segmentation using Zones
    • Hardening Backup Repository - Linux
    • Hardening Backup Repository - Windows
  • Backup & Replication Anatomy
    • Backup
    • VM Restore
    • Instant VM Recovery
    • Windows File-Level Restore
    • Replication
  • Networking Diagrams
    • Backup Server
    • Proxy Server
    • Repository Server
    • Storage Integration
    • Data Validation
  • Application-aware Image Processing
  • Enterprise Manager
  • Sizing Summary
Powered by GitBook
On this page
  • Storage array configuration
  • Snapshot only jobs
  • Snapshot replication
  • Backup from secondary storage

Was this helpful?

  1. Proxy Servers - Introduction
  2. Proxy - VMware vSphere
  3. Transport Modes
  4. Backup from Storage Snapshots

Nimble Storage integration

PreviousNetApp Data ONTAP integrationNextSelecting a Transport Mode

Last updated 4 years ago

Was this helpful?

This section contains integration specific information for configuring orchestration of snapshot creation and replication between Nimble Storage arrays.

Storage array configuration

  1. Browse the NimbleOS web GUI: Manage -- Protection -- Volume Collections

  2. Add a new volume by clicking on New Volume Collection

  3. Add the Volume Collection Name on the Introduction.

    Be careful with the naming to stay within the limits of 80 characters.

  4. Select None on the Synchronization tab.

    Veeam will orchestrate the creation of a volume snapshot, and initiate replication to the secondary Nimble array before the backup job starts.

  5. Set the scheduling for Nimble Storage snapshots.

    Note that Veeam Backup & Replication uses its own engine to initiate the creation and replication of snapshots.

    Nimble configuration will not allow empty scheduling. Therefore you can choose Weeks or Repeat Every Week and Replicate to set to "2" as the minimum - or any desired configuration, as these configurations will not be used by Veeam.

  6. Associate the desired volume for replication on the Volumes Tab

Snapshot only jobs

When a job is configured for using "Nimble snapshot" as the backup repository, Veeam will not copy any data from the source storage to a target repository. Instead Veeam will orchestrate the creation of a storage snapshot, and can entirely skip VMware snapshot creation, in case application-aware image processing is left disabled.

Note: It is recommended by the vendor that volumes should be in individual Volume Collections. Please verify Nimble Volume Collections configuration before running the snapshot-only job, otherwise it may not operate properly - for example, replicate more data than expected.

Snapshot replication

When configuring backups using the "snapshot only" repository, or regular repositories, it is possible to configure orchestration of replication to a secondary Nimble Storage array by checking the Configure secondary destinations for this job.

By clicking Add / Nimble Snapshot Replicated Copy, it is possible to configure how many snapshots should be retained at the target Nimble Storage array. During the job run, Veeam will search for replication settings configured on the Volume Collection for the source volume being snapshotted. Please see the initial paragraph of this chapter for details on configuring Volume Collections.

Backup from secondary storage

When performing backups to a backup repository, it is possible to configure using the replicated copy at the target Nimble Storage array as the source for the repository based backup.

It is not recommended to rely on storage snapshots as backups, as it violates the . It is however a great complement to traditional backups to achieve lower RPO, in case the primary storage array is still available, when a restore is needed.

3-2-1 rule
Nimble Snapshot
Nimble Storage secondary destination
Nimble Storage secondary source