NetApp United – APPLY NOW

NetAppUnited_Crest_2_Black and White Version.png
For me it’s a real honor to be part of one of the best of not the best influence programs in IT industry – NetApp United.
Over the last years I had the pleasure to attend countless industry events and also became part of several influencer programs, meet IT subject matter experts and chat with other influencer in different programs.

Today I like to tell you a bit more about the NetApp United program. The information’s below can also be found on the official NetApp United team page.

The best thing is that you can apply till March 9th to become a member of the program here: APPLY NOW

The NetApp United program is for influencers who are curious about NetApp technologies and want an organized way to learn more.

It’s a way for passionate technologists to stay engaged, receive exclusive access to NetApp information and experts, and share their knowledge, expertise, and thoughts across their personal channels, as well as NetApp channels.

We are looking for technology enthusiasts, NetApp Partners and Customers who:

  • Have a social media presence
  • Have overall expertise within the technology industry
  • Are a member of the technical community in good standing
  • Are interested in learning more about NetApp product and service

NetApp United Member Benefits:

  • Exclusive Access
    • As a NetApp United member, you will receive exclusive access to NetApp information and experts.
  • Engage and Get Your Voice Heard
    • Membership will provide you the opportunity to engage and get your voice heard through our corporate channels–included but not limited to social channels, blogs, video, podcasts, etc.
  • Expand your Network
    • Build relationships and connect with other NetApp United Members from around the world.

How are potential NetApp United candidates identified?
Potential candidates are identified in two ways:

  • Candidates can nominate themselves for consideration in the program using the link and I recommend you to: APPLY NOW
  • NetApp identifies and nominates potential candidates that meet the criteria outlined above.

How long does the NetApp United Program membership last?
Once selected, membership lasts for one year. Membership confirmation is announced on or around March 31st of each year. At the end of the year, members can choose to continue by reapplying or end their membership. Additional opportunities to join the NetApp A-Team are also available if A-Team criteria has been met.

What are the requirements for maintaining NetApp United membership?
NetApp United members are encouraged to stay engaged in the program through activities such as, but not limited to:

  • Contributing NetApp or industry expertise through blog posts, social channels, etc.
  • Engaging and attending exclusive NetApp events, sessions, webinars, and more
  • As the program evolves, engagement opportunities will evolve as well

Have additional questions?
Please feel free to contact us at


How to: NetApp ONTAP reverse SnapMirror (CDOT)

I recently researched the ONTAP functionality to reverse a SnapMirror and as I didn’t found any useful blog post or even user guide explaining how to perform it on CLI I thought it’s worth to share on my own blog. In this post you will see two ONTAP systems where CDOT01 is the primary and CDOT02 is the secondary. My source volume here is called “datalunwindows” on the source SVM “SVMSRC” and my destination volume is named “SVMSRC_datalunwindows_mirror” on the destionation SVM “SVMDST”. Everything was tested with ONTAP 9.2.

What means reverse SnapMirror?
By that I mean changing the direction of the SnapMirror. The most likely best example is if you want to failback from a secondary ONTAP to the primary after a disaster.

Normal replication:
CDOT01/volumesource -> CDOT02/volumesdestination
Needed replication after a disaster:
CDOT02/volumesdestination -> CDOT01/volumesource

The change includes different steps an pre-requirements such as a broken SnapMirror relationship and that the source volume is still available and not completely lost. If you primary system is completeley lost you need to re-initialize to a new volume/system.

How do I perfrom a reverse SnapMirror?
The first and maybe easiest way would be to use the system manager as the latest version have the option to reverse a SnapMirror. But in my case I was looking for the way to do it on CLI as I was building some scripting around it.

1. Make sure your SnapMirror from CDOT01 to CDOT02 is broken and your data on CDOT02 is online.

##Check if mirror is broken
snapmirror show -destination-path SVMDST:SVMSRC_datalunwindows_mirror -fields state
##Check if volume is now in RW status (DP before)
volume show -volume SVMSRC_datalunwindows_mirror -fields type
##Check if volume is now online
volume show -volume SVMSRC_datalunwindows_mirror -fields status

2. Be aware that changing the direction will overwrite the current source data on the volume so don’t execute the commands without knowing what you do. To sucessfully execute a reverse, there needs to be at least one common Snapshot on the source and destionation volume which will be used as the baseline Snapshot. If there is no common Snapshot the command will fail.

3. Execute the resync command on the source ONTAP (CDOT01) to get data from the secondary. Yes you see right, the reverse is simply done by using the rescny command but on the source (new destionation) instead of the destionation (now source).

snapmirror resync -destination-path SVMSRC:datalunwindows -source-path SVMDST:SVMSRC_datalunwindows_mirror -force true

4. Check if the SnapMirror is now reversed. You should see that CDOT01 now has an active SnapMirror relation and CDOT02 is a source.


snapmirror show


snapmirror list-destinations

5. The reverse is already done now.
Optional: Ususally customers now want to make the source the primary now again and reverse the SnapMirror again to have the initial CDOT01->CDOT02 relation in place again. Therefore follow the steps below:

##Quiesce the relation on the source cluster (CDOT01)
snapmirror quiesce -destination-path SVMSRC:datalunwindows

##Break the snapmirror on the source cluster (CDOT01)
snapmirror break -destination-path SVMSRC:datalunwindows

##Mount the data back to your environment

##Resync the relation back from CDOT01 to CDOT02
snapmirror resync -destination-path SVMDST:SVMSRC_datalunwindows_mirror -source-path SVMSRC:datalunwindows -force true

##Cleanup the Snapmirror resync on source CDOT01
snapmirror delete -destination-path SVMSRC:datalunwindows

##Cleanup the Snapmirror resync on destination CDOT02
snapmirror release -destination-path SVMSRC:datalunwindows -force true


That’s it for this post. I hope it was useful for some of you. Feel free to comment or share on any channel.

See u next time.

How to: Upgrade NetApp ONTAP Simulator 9.1 to 9.2

For my tests and lab activities it’s always important to work with the latest version of software products. As the NetApp ONTAP simulator usually comes some times after the GA I decided to upgrade the simulator with the regular GA package and want to share here how to do it.

Before you start you need to:
– download the latest ONTAP 9.2 build
– make sure your root aggregate and root volume has enough free space
– disable snapshot scheduling and reserve on vol0 (yes, the vol0 on the node)
– The guide is for a single-node simulator

Read More »

FlexPod goes SolidFire: FlexPod SF

Being at Cisco Live in Las Vegas last week I was glad that I had the chance to join the FlexPod SF launch happening on June 22nd. Unfortunately, I forgot to make some pictures but I want to tell you some details on the new FlexPod.


According to IDC, FlexPod® is the #1 worldwide fastest growing integrated infrastructure and certified reference (source: IDC Worldwide Quarterly Converged Systems Tracker 2017 Q1) with a revenue growth rate of 26.1%. The other two vendors in the top three of market share saw their revenues decline. FlexPod SF is the first scale-out converged infrastructure solution in the industry, allowing customers to incrementally add storage as they consume it.

Since FlexPod was started in 2010 the validated Cisco + NetApp solution had great success and shows some amazing numbers:
2017-06-30 04_33_27-FlexPod_SF_Winnning Together June 15 PARTNER WEBCAST.pdf - Adobe Acrobat Reader .jpg

In 2015 NetApp then acquired SolidFire to grow their All-Flash Leadership and to offer a Scale-out storage system for the Next-Generation, Application-Centric data center.

And now, 2 years later FlexPod & SolidFire get together and the FlexPod SF is born.

2017-06-30 04_38_55-FlexPod SF partner deck_Final.pptx [Schreibgeschützt] - PowerPoint.jpg

The new FlexPod comes with Cisco UCS B-Series M4 Blades and Nexus 9k switching and contains the SF9608 storage nodes which can get up to 300000 IOPS in a 4-node cluster.
The design is fully validated and can be implemented like the regular FlexPod installations. 2017-06-30 04_41_56-FlexPod SF partner deck_Final.pptx [Schreibgeschützt] - PowerPoint.jpgLooking at the high-level design picture it is similar to what we already see and install since years so there won’t be a big need to learn everything from scratch again which is another plus point here.
The backend runs end-to-end iSCSI and depending on the B-Series Blade configuration you can run a 10G or 40G environment.
2017-06-30 04_45_43-FlexPod SF partner deck_Final.pptx [Schreibgeschützt] - PowerPoint
The SF9608 Node itself runs on Cisco UCS C220 M4 Hardware and comes with the following hardware:
– CPU: 2 x 2.6GHz CPU (E5-2640v3)
– Memory: 256 GB RAM
– 8 x 960GB SSD drives (non-SED)
– 7.6TB raw capacity (per node)
2017-06-30 04_51_42-FlexPod SF partner deck_Final.pptx [Schreibgeschützt] - PowerPoint
As mentioned before the solution runs iSCSI all the way and offers all benefits and features SolidFire had build-in. Esp. the QoS policies to define min. as well as max. performance for dedicated data streams is one of my favorite feature. It also helps to avoid “Noisy Neighbors” by setting limits for these workloads. Below you can find a performance chart before SolidFire QoS was enabled and after it was enabled:
QoS disabled:
Bild2QoS enabled:

Overall I like the fact that the FlexPod Family is growing, not only in revenue but also with new family members. I’m looking forward to see the FlexPod SF in action (ok I saw it at Cisco Live already) and to talk to customers using it to get some feedback.
2017-06-30 04_53_14-FlexPod SF partner deck_Final.pptx [Schreibgeschützt] - PowerPoint.jpg

That’s me done for now, need to board the flight back home. I hope you like the post and look forward to see u again on my blog or receive your feedback.


NetApp goes HyperConverged-isch with NetApp HCI

On June 5th NetApp decided to disrupt the IT market and came out with several announcements around the Data Fabric, ONTAP 9 and finally their own HyperConverged solution. In this blogpost, I’d like to look a little bit deeper in how the HCI solution looks like and what we can expect when it is GA.
2017-06-14 20_11_26-Final Data Fabric Partner Webcast Slides-052617.pptx [Geschützte Ansicht] - Powe
According to IDC, the global HCI (hyper converged infrastructure) market is at $3 billion in annual revenue, and it’s expected to grow to $7 billion by 2020. NetApp HCI enables the customers to gain additional market opportunity and differentiation by selling an enterprise-scale hyper converged infrastructure into the most demanding data centers. Our IT market and industry is heading into the “Next Generation Data Center” and HCI is for sure one of the players in this area. To achieve consolidation and still maintain flexibility on the journey to the cloud customers need to look for new was on how to build their environments.

2017-06-14 20_10_46-New notification

Read More »

How-To ONTAP 9.1: root volume damaged

Recently I had two power outages on my lab. And after the second one my ONTAP 9.1 simulator came up with the error:
“root volume damaged”
“please contact NetApp support”
“The contents of the root volume may have changed and the local management
configuration … This node is not fully operational.
Contact support personnel …”

But as it is an simulator I tried to fix by myself. And after a while I found a solution that fixed it for me. If you see the same error the how to below can may help you out.

IMPORTANT: The following how to was used for a ONTAP 9.1 simulator in a NON-Production environment. No warranty and don’t use it in production clusters.
You are performing everything on your own risk so please always involve NetApp Support.

Read More »

How-to: NetApp ONTAP 9.1 simulator deployment

This post will show you how to deploy the new NetApp ONTAP 9.1 simulator on a VMware vSphere 6.5 host.

After releasing a post on how to run the setup with Data ONTAP 8.3 (please find here) I thought its worth to write another one as NetApp really changed the simulator in terms of capacity as well as the setup process.

Getting the required Software

  1. Login to with your credentials
  2. Go to “Download – Software” and click on “Data ONTAP Simulator”
    2017-04-01 19_54_19-Settings
  3. Accept the license agreements and terms and conditions.
    2017-04-01 19_54_06-New notification
  4. Download your required OVF template for VMware Workstation or VMware ESX
    as well as the license file.
    2017-04-01 19_53_25-Settings

Read More »

Veeam 9.5 and NetApp: Enterprise performance and scalability for NetApp storage with

Veeam just released version 9.5 of Veeam Backup & Replication. In this blog post, I would like to share some of the new capabilities that 9.5 delivers with our NetApp ONTAP storage integration.

As this is not a major version release, we didn’t add any specific new features, however, there are several improvements with respect towards backup resource scalability, which is of particular importance in enterprise data center environments.

1. Automatic NetApp LIF selection for data traffic

With 9.5, we implemented an advanced way for the Veeam backup server to identify the correct Data LIF for the backup process.
img01-1-700x427In the above example, the VM is stored on an aggregate located on Node 4. With 9.5, we made sure that data LIF4, of node 4, is used to access and backup the VM, instead of using data LIF1 on node 1 and transferring the data over the back-end cluster network. With this new implementation, we avoid the potential for node 1, or the back-end cluster network, to run out of resources during a Veeam backup.

The new cluster aware LIF selection also follows the data in case it is moved to another aggregate on another node, thereby ensuring the optimized path is utilized by the Veeam proxy server to perform data movement.

This functionality is enabled by default and does not require any action from your side to utilize this new capability.

2. Proxy affinity rules for storage access

The second enhancement is a new way to define proxy affinity between your NetApp ONTAP systems and the Veeam proxy server.
img02-1-700x204By using proxy affinity rules, you can easily define Veeam proxy server assignments for each NetApp ONTAP system. If there are multiple NetApp systems and Veeam proxy servers in the same environment, it is recommended to assign affinity relationships to avoid situations where a Veeam proxy server is misaligned with an ONTAP system. This capability saves time in the job initialization process and optimizes proxy resource utilization in larger environments, enabling you to ensure that specific proxy servers are available for specific backup jobs. img03-1-700x275This also ensures that local proxies are only accessing local NetApp ONTAP systems when using network based access protocols like NFS or iSCSI. img04To configure the proxy affinity, simply go to “Storage Infrastructure” within your Veeam Backup & Replication console and select the NetApp cluster you want to modify. Open the advanced settings and select the backup proxies Veeam should use.

3. Protocol selection to optimize proxy data access

One very common user request that we have addressed with 9.5 is the option to assign a different protocol to the Veeam proxy server than the one being used by the VMware server. Before 9.5, you could use different REG-Keys to force the Veeam proxy to use a different protocol. img05-1-700x466Now with 9.5, you can easily deploy a configuration where VMware is accessing the ONTAP cluster by FC, while the Veeam proxy uses iSCSI for backup and replication and all of the other Veeam features. Since the LUN is the same block device, it can be accessed via FC, iSCSI or both, enabling you to leverage your existing 10 GB network to back up the data via FC or iSCSI (or vice versa).

Besides the benefit of defining a different access protocol, you can also reduce the time that the Veeam proxy needs to scan and access your NetApp data and start a job, as the overhead required to check all available protocols is eliminated. In short, it’s a very simple way to optimize your existing Veeam and NetApp installation. img06To configure the protocol selection, simply go to “Storage Infrastructure” within your Veeam Backup & Replication console and select the NetApp cluster you want to modify. Open the advanced settings and select the protocol to be used by the Veeam proxy host. As shown in the above example, only the licensed ONTAP protocol is available to use.

In summary, the enterprise enhancements available in 9.5 make the Veeam integration with ONTAP more flexible and scalable. This is another great example of Veeam product development implementing feature enhancements based on the direct feedback from our customers and partners.

For additional Veeam and NetApp best practices, I highly recommend the following documents and articles:

Must see sessions at NetApp Insight Berlin


After attending NetApp Insight in Berlin I’d like to give you an overview on the sessions I would highly recommend to attend.

46322-2 – Flash to Disk to Cloud: VM Data Protection with Veeam, AltaVault and StorageGRID Webscale
Virtual machine data is often the largest and most critical data companies can have. It also tends to be the most laborious and difficult to properly protect. This breakout will explain and demonstrate how to simply configure a protection policy to migrate your virtual machine data from flash to a disk archive, and finally to a cloud repository. We will also discuss how to keep the right data on the right tier of storage.
Monday, Nov 14, 11:00 AM – 12:00 PM
Tuesday, Nov 15, 1:00 PM – 2:00 PM

60615-3 – NetApp SolidFire Technical Deep Dive
Understand the NetApp® SolidFire® architecture? Know how the product can be operated and managed? Ready for the firehose? Come listen to SolidFire developers and engineers dig deeply into the magic of the SolidFire storage software. Slice services, node elections, quality of service algorithms, data pathing, failure scenarios and more — nothing will be out of bounds. Time will be left to take questions from the audience, so no stone will be left unturned.
Tuesday, Nov 15, 10:30 AM – 12:30 PM
Thursday, Nov 17, 10:30 AM – 12:30 PM

94567-2 – Veeam: The best thing you didn’t know Veeam & NetApp can do for you
Attend this breakout session to see how Veeam and NetApp can: · Powerful recovery techniques with Veeam Explorer for NetApp Storage Snapshots: Recover individual items or entire VMs quickly and efficiently from NetApp Snapshot, SnapMirror and SnapVault. · Avoid data loss with Backup from NetApp SnapMirror and SnapVault: Protect your environment’s high performance by completely eliminating backup impact on your production storage. · Leverage NetApp data with On-Demand Sandbox for Storage Snapshots: See how Veeam’s On-Demand Sandbox can easily create isolated copies of your environment.
Tuesday, Nov 15, 2:15 PM – 3:15 PM

47573-1 – Hands-On Lab: VMware vSphere 6 on MetroCluster
This lab demonstrates the high availability of a stretched VMware® DRS cluster infrastructure built on the synchronous mirroring of NetApp® MetroCluster™. The lab also offers a few basic failure scenarios, and highlights survivability using MetroCluster to provide continuous access to storage across geographically separated datacenters. To create a lab reservation on your schedule, please search for the session ID starting with “Lab-10XX” and reserve your seat in the Hands-On Labs area.

52600-2 – NetApp MetroCluster: New Features in ONTAP 9 and Basics of Building a Zero-Downtime Infrastructure
In this session, you will learn about the new NetApp® MetroCluster® features in ONTAP® 9. We’ll also consider the implications of distance and bandwidth between MetroCluster sites and the maximum performance figures in a MetroCluster infrastructure. Finally, we’ll look at what benefits All Flash FAS provides and which minimum configurations are supported.

94568-2 – The Veeam 3-2-1 Data Protection Rule in NetApp’s Data Fabric
In today’s Enterprise Data Centers Availability is key for success. It’s very important to have a valid and proven Data Protection Design that delivers the required business RTO’s and RPO’s. Learn how to lower RTO’s and RPO’s and enhance application Availability by applying the 3-2-1 backup rule. You will learn how to deliver Availability for the Always-On Enterprise by combining NetApp ONTAP, FlexPod, AltaVault and the Veeam Availability Suite.
Wednesday, Nov 16, 2:00 PM – 2:30 PM

Of course there are much more sessions to attend.
Don’t miss to reserve your seat soon before they are getting full.
The session scheduler can be found here Session Builder.

I will be around at NetApp Insight in Berlin as well and deliver session 94568-2 as well as 94567-2.

Let me know when you’re coming an we can meet up. Just ping me on Twitter under @rennerstefan.

See u there.

Enterprise datacenter Availability with NetApp cascaded SnapMirror and Veeam

Data Availability has become more and more important for today’s businesses. The NetApp Data ONTAP and Veeam combination provides a high Availability level for the Always-On Enterprise. By leveraging NetApp data protection features like snapshots, SnapMirror and SnapVault, Veeam is able to enhance recovery time and recovery point objectives, otherwise known as RTPO, for VMs and applications residing on NFS-, FC-, FCoE- and iSCSI-based arrays.

Some enterprise data centers are leveraging NetApp’s ability to cascade ONTAP systems to maximize Availability. In this blogpost, I explain the benefits of leveraging an ONTAP cascaded design with Veeam.

The environment

Let’s assume the customer has the following data center design and requirements:

  1. In the primary data center, a NetApp ONTAP system named RLPEDGE01, with a source volume called NFSVAULT
  2. On the secondary side, a NetApp ONTAP system RLPEDGE02, with a SnapVault destination Volume RLPNFS01_NFSVAULT_vault
  3. At the third side, a NetApp ONTAP system RLPEDGE03, with a SnapMirror destination volume RLPNFS03_NFSVAULT_mirror

The requirements include using SnapVault between RLPEDGE01 and RLPEDGE02, combined with application-consistent snapshots. Furthermore, the customer wants to use SnapMirror to replicate the SnapVault data to RLPEDGE03, which is in a co-location facility.

Veeam orchestration combined with NetApp protection policies

To build this configuration, NetApp ONTAP protection policies are combined with Veeam’s advanced storage integration and orchestration capabilities.

  1. Veeam creates an application-consistent backup of VMs. This includes the optional log truncation and snapshot creation within the VMware environment.
  2. Next, Veeam instructs the primary NetApp system (RLPEDGE01) to perform an array-based snapshot and subsequent orchestration.
  3. Next, the primary NetApp system will manage the SnapVault update to the secondary (RLPEDGE02) and retention policies of these snapshots within both primary and secondary systems.
  4. The NetApp ONTAP built-in protection engine handles the SnapMirror update between the secondary and the tertiary (RLPEDGE03) NetApp systems. Through this process, all snapshots on RLPEDGE02 will be mirrored to RLPEDGE03 and made available for restores.

The customer benefits here by being able to leverage Veeam’s native restore capabilities on any NetApp ONTAP platform in the environment. This includes the third NetApp system, RLPEDGE03, which is not part of the Veeam snapshot orchestration process. The restore functionality permits granular restores using Veeam Explorers for Storage Snapshots to perform file, item or VM image-based recoveries for Microsoft Active Directory, Exchange, SharePoint, SQL and Oracle. Veeam OnDemand Sandbox capabilities can also leverage NetApp snapshots to create isolated test environments for testing application updates, patches and other changes, without impacting the production environment.

Let’s get it done

To set up this configuration, follow these steps:

  1. Add all NetApp ONTAP systems to your Veeam Backup & Replication console
  2. Create the SnapVault relationship between primary and secondary NetApp systems
  3. Create a Veeam job to protect your VMs:
    1. Within the Veeam job set the desired SnapVault retention policies
    2. If required, enable Application-Aware Processing
    3. Define a schedule for the job that meets the RPO of applications being protected

If you require any assistance creating a Veeam/NetApp backup job, you can find additional detail in the Best Practices Guide.

After Veeam Backup and NetApp SnapVault are configured and running, we can now set up the SnapMirror relationship to the third NetApp system. However, you should pair NetApp 2 and NetApp 3 and ensure that the proper SnapVault Mirrors (SVMs) are available and paired as well. In addition, create a DP Volume on the NetApp 3 SVM, which will be used as the destination target for the SnapMirror volume.

NOTE: Veeam assumes no warranty for any command. These commands should only be used as a reference. Exercise CAUTION when working in any production environment. All commands should be modified (cluster, volume, vservernames, etc.) to fit in your environment.

After the volume is created, you can create the SnapMirror policy and the SnapMirror relationship:

To create the SnapMirror policy run:

snapmirror policy create -vserver SVMNFS03 -policy VeeamSM -tries 8 -transfer-priority normal -ignore-atime false -restart always -type async-mirror

Add the rule to mirror all source snapshots: all_source_snapshots. This is mandatory, otherwise you will get an error that the SnapMirror label was not found:

snapmirror policy add-rule -vserver SVMNFS03 -policy VeeamSM -snapmirror-label all_source_snapshots -keep 1
snapmirror policy show

SnapMirror relation creation and initialization:

snapmirror create -source-path RLPNFS02:RLPNFS01_NFSVAULT_vault -destination-path SVMNFS03:RLPNFS03_NFSVAULT_mirror -type DP -throttle unlimited -identity-preserve false -vserver SVMNFS03 -policy VeeamMirror

snapmirror initialize -destination-path SVMNFS03:RLPNFS03_NFSVAULT_mirror

snapmirror modify -destination-path SVMNFS03:RLPNFS03_NFSVAULT_mirror -schedule 5min

snapmirror show

You can also check the SnapMirror relationship within the NetApp System Manager on the third NetApp to get the following screen view:
6Now that the SnapMirror relation has been initialized and running (in our case, every 5 minutes), check the Veeam interface to verify that snapshots on the third NetApp platform are available for restores.

Your Veeam interface should look similar to this:
7As you can see, all three NetApp systems are available, as well as the three volumes. When browsing the volumes on RLPEDGE02 and RLPEDGE03, we see the same number of available snapshots (one snapshot is the baseline image).
8With the configuration complete, we now have a cascaded SnapVault to SnapMirror relationship from which all Veeam restore capabilities can be used. One of the benefits of the direct integration Veeam provides is the ability to directly restore from array-based snapshots.

In the example below, we illustrate how an administrator can browse our NetApp system RLPEDGE03, view the VMs within that snapshot and perform all of the great recovery options that Veeam has available. In summary, this scenario illustrates how we’ve executed a single NetApp snapshot, which has been cascaded down to our tertiary device where we’re able to perform recovery. This process drastically reduces the load placed on the production environment during backup and recovery operations, which in turn, increases the RTPO for our applications and services.

What about Veeam Backup from Storage Snapshots?

Veeam Backup from Storage Snapshots is a unique technology that optimizes VM backup by leveraging Storage Snapshots as a source for the Veeam data stream. In the scenario that was just explained, you can fully leverage Veeam Backup from Storage Snapshots from the primary or secondary NetApp ONTAP storage device. Veeam orchestrates all the snapshots processes across these two storage systems.
10To complete the cascade process, and as mentioned earlier, the SnapMirror relation toward the third NetApp ONTAP system is handled by the data protection engine of ONTAP, and is not a part of Veeam orchestration.