Azure NetApp Files is an enterprise-class, high-performance, metered file storage service. The service supports the most demanding enterprise file workloads in the cloud: databases, SAP, and high-performance computing applications, with no code changes. For more information on Azure NetApp files, see the Azure NetApp Files documentation.
By using NFS datastores backed by Azure NetApp Files, you can expand your storage instead of scaling the clusters.
Note: You can also Attach Azure NetApp Files to Azure VMware Solution VMs directly via NFS or SMB.
Azure VMware Solution provides you with private clouds that contain VMware vSphere clusters built from dedicated bare-metal Azure infrastructure. Azure VMware Solution supports attaching Network File System (NFS) datastores as a persistent storage option. You can create NFS datastores with Azure NetApp Files volumes and attach them to clusters of your choice. For more information on Azure VMware Solution, see the Azure VMware Solution documentation.
Cloud Backup for Vitual Machines is a plug-in installed in the Azure VMware Solution and enables you to back up and restore Azure NetApp Files datastores and virtual machines (VMs). Use Cloud Backup for VMs to: - Build and securely connect both legacy and cloud-native workloads across environments and unify operations - Provision and resize datastore volumes right from the Azure portal - Take VM consistent snapshots for quick checkpoints - Quickly recover VMs
In this VMware hands-on lab, you'll begin with a provisioned Azure VMware Solution (AVS) private cloud and cluster to complete the following exercises:
- Create an Azure NetApp Files (ANF) volume
- Attach your new ANF volume to your AVS private cloud as a datastore
- Migrate a running virtual machine to your new ANF datastore
- Protect your virtual machine using NetApp's Cloud Backup for Virtual Machines
- Restore your virtual machine using NetApp's Cloud Backup for Virtual Machines
- Navigate to
Azure NetApp Files
in the Azure portal - Select the Azure NetApp Files
NetApp account
that was assigned - Click on
Volumes
- Click on
Add volume
- Basics tab
- For
Volume name
, use the name that was assigned - For
Capacity pool
, select the capacity pool that was assigned - For
Quota
, enter1024
GiB - For
Virtual network
, select the virtual network that was assigned - For
Delegated subnet
, selectanf-subnet
- For
Network features
, selectStandard
- Click
Next: Protocol >
- For
- Protocol tab
- Basics tab
- Navigate to
Azure VMware Solution
in the Azure portal - Select the
AVS Private cloud
that was assigned - Click
Storage (preview)
- Click
Connect Azure NetApp Files volume
- For
NetApp account
, select the NetApp account that was assigned - For
Capacity pool
, select the capacity pool that was assigned - For
Volume
, select the Azure NetApp Files volume you created in the previous step - For
Client cluster
, selectCluster-1
- For
Datastore name
, use the datastore name that was assigned - Click
Connect
- For
- Navigate back to
Azure VMware Solution
in the Azure portal - Select the
AVS Private cloud
that was assigned - Click
Storage (preview)
- Verify your new Azure NetApp Files datastore
- Launch the vSphere Client and login using the address and credentials provided
- Right-click on your virtual machine and select
Migrate...
from the context menu - Within the
Migrate
dialog window, selectChange storage only
- Click
Next
- On the next page, confirm
Batch Configure
is selected, change theVM Storage Policy
toDatastore Default
, and select the ANF datastore you created in the previous step - Click
Next
- Click
Finish
- You can monitor the progress of the migration using the
Recents Tasks
pane at the bottom of your screen. - Once the migration is complete, select the
Datastores
tab from your virtual machine's information pane to confirm your virtual machine is now on your ANF datastore.
Now that your virtual machine is stored on an Azure NetApp Files datastore, we can use NetApp's Cloud Backup for Virtual Machines to create a snapshot-based backup that will be virtual machine consistent.
- Click on the hamburger menu in the top left corner and select
Cloud Backup for Virtual Machines
- Click
Resource Groups
- Click
+ Create
- Give your Resource Group the same name as the datastore you created in the previous step
- Click
Next
- Find your datastore in the list on the left and click the single arrow pointing to the right
- Click
Next
- In the
Spanning disks
pane, leave the first/default option selected - Click
Next
- In the
Policies
pane, selectOnDemandPolicy
- Click
Next
- In the
Schedules
pane, leave everything as is - Click
Next
- Review the
Summary
and clickFinish
- Click
OK
- You should now see your Resource Group listed (you may need to click the refresh button within the vSphere client)
- Select/highlight your Resource Group
- Click
Run Now
- Click
OK
to dismiss the pop-up - Click
Dashboard
to view theRecent Job Activites
and verify your backup was successful, you may need to wait a minute and refresh the vSphere client.
You have now created an Azure NetApp Files snapshot that is 'virtual machine consistent' using NetApp's Cloud Backup for Virtual Machines
Once your virtual machine has been deleted, you can restore it using NetApp's Cloud Backup for Virtual Machines
- From the vSphere client, navigate back to your Inventory
- Select
Datastores
- Select your datastore from the list on the left
- Click the
Configure
tab - Click
Backups
under theCloud Backup for Virtual Machines
sub-heading - In the 'Backups' list, click the blue link associated with your backup
- Highlight your virtual machine in the list
- Click the
Restore
button - In the
Restore
dialog window, check theRestart VM
checkbox and leave theRestore Location
set toOriginal Location
- Click
Next
- In the
Select location
pane, confirm that your ANF datastore is selected - Click
Next
- Review the
Summary
and clickFinish
- Click
OK
in theRestore
warning pop-up window - You can view the status of the restore process in the
Recent Tasks
pane at the bottom of the window. - Once the restore is complete, navigate back to the vSphere Inventory and confirm your virtual machine is running.